Monster: Quasit (auto effects submission)

On the claws, I checked the midi flag for full dam save at bottom, then added an active effect for poisoned and an overtime to save it off.  The overtime is:
turn=end,
saveAbility=con,
<EMAIL_ADDRESS>label=Poisoned Claws

On scare, The only thing I tweaked from the original was I added magic effect to the flags at bottom and cleaned up the overtime just incase it was buggy, cause theres an errant page return in your version.  You may want to consider checking that on any monster overtimes on items with a "(something something)" in their names.  For some reason the spaces got turned into page returns/line breaks.  Its probably a non issue but I'm OCD and wanted a clean overtime appearance.  The overtime is:
turn=end,
label=Scare,
saveRemove=true,
<EMAIL_ADDRESS>saveAbility=wis

For invisibility, I added an action type of Other, so I could gain access to the bottom third of the item sheet, where I checked the box for "Don't apply CE" and then checked the midi box for "Concentration".  Then I added an active effect.  First tab(details) changes are check the box for always show effect icon.  Second Tab(Duration) set it up with no duration in seconds or turns, instead lean on Times Up here and add 3 special durations, 1 action, 1 spell, 1 attack.  Finally third tab(effects) add the key "macro.CE | Custom | Invisibility".
If you need a visual guide to what to change I've submitted them in the showcase on posney's discord also, but they have no descriptions there.
https://discord.com/channels/915186263609454632/1139995478549876737/1139995478549876737

Have added claws and invis. I think RAW the Scare effect is not magical, so not going to add that as I think it's more a dm choice.

The overtime in scare was really weird looking I think theres extra characters in what you put in it and it causes line breaks, not sure if that adversely affects it but I just cleaned up the spaces.  I think its caused by that setting that puts details in the title of an ability in the muncher.

The overtime in scare was really weird looking I think theres extra characters in what you put in it and it causes line breaks, not sure if that adversely affects it but I just cleaned up the spaces. I think its caused by that setting that puts details in the title of an ability in the muncher.

I don't see this

Disregard, its user error, the dae UI confused me.


Implemented separation of content and print ui

Short description explaining the high-level reason for the pull request
Additions

Created a series of components that take content in JavaScript JSON format and renders it on the FinalPrintPage.js

Testing

npm run build
Make sure to fill out the first 2 criterion on the Content criterion

All three have been started in the content_data folder
The idea is to create a JSON file in the content_data folder

I recommend creating the content for each Dimension in a separate file

Use the existing FinalPrintPage.js as a guide
NOTE: the Content has a switcher component that swaps out for the correct one

Notes

I had to use dangerouslySetInnerHTML for styling in some of the content

TODO

I still need to come up with an option for the Quality text fields (actually the dangerslySetInnerHTML might work since that will show on the print page as plain text

Review

@dcmouyard @rrstoll

Preview this PR without the whitespace changes

Rebased with new changes in the master branch.


There's a definition, but I can't jump or preview it

Describe the bug

It seems to happen only in the test directory, and I'm not sure if it's because LSP doesn't return enough data.
Steps to reproduce
this is the log data:
[DEBUG][2023-03-06 15:36:16] .../vim/lsp/rpc.lua:284	"rpc.send"	{  id = 52,  jsonrpc = "2.0",  method = "textDocument/definition",  params = {    position = {      character = 4,      line = 12    },    textDocument = {      uri = "file:///Users/scottming/Code/recode/test/fixtures/rename/exp/import_no_change.ex"    }  }}
[DEBUG][2023-03-06 15:36:16] .../vim/lsp/rpc.lua:387	"rpc.receive"	{  id = 52,  jsonrpc = "2.0",  result = {    range = {      ["end"] = {        character = 6,        line = 1      },      start = {        character = 6,        line = 1      }    },    uri = "file:///Users/scottming/Code/recode/test/fixtures/rename/exp/import_no_change.ex"  }}

But I don't see how this is different from normal results.
Here is an example of a normal result(not in the test folder):
{  id = 73,  jsonrpc = "2.0",  result = {    range = {      ["end"] = {        character = 7,        line = 39      },      start = {        character = 7,        line = 39      }    },    uri = "file:///Users/scottming/Code/recode/lib/recode/config.ex"  }}

Expected behavior
`
Neovim version (nvim -v)
0.9
lspsaga commit
63b35723d0a1ae01446e1645d567fb4d9f1831f4
Terminal name/version
alacritty

quickly fix is disable beacon beacon.enable = false  . can you test it ?

the response looks right something wrong in beacon looks like. you can do the debug print . i need this result .
  git diff
Found existing alias for "git". You should use: "g"
diff --git a/lua/lspsaga/libs.lua b/lua/lspsaga/libs.lua
index 41577a9..d4c30b1 100644
--- a/lua/lspsaga/libs.lua
+++ b/lua/lspsaga/libs.lua
@@ -313,6 +313,7 @@ function libs.jump_beacon(bufpos, width)
   }

   local window = require('lspsaga.window')
+  print(vim.inspect(opts))
   local _, winid = window.create_win_with_border({
     contents = { '' },
     noborder = true,

First, disable doesn't report errors anymore, but it still doesn't preview and jump
Then the log doesn't have valuable information.

can you post this  exli repo ? then i can test it .

sure, this is the repo: https://github.com/hrzndhrn/recode.git
and the code is the baz of this line: https://github.com/hrzndhrn/recode/blob/114ca9ac7c90dded88769ae9c0d2f73b902190c1/test/fixtures/rename/lib/import_no_change.ex#L13

And I think after cloning that repo, you should run asdf install  first(to install erlang and elixir).

what is the asdf a pacakge manager of elixir ?

emm do you have a min repo of elixir can reproduce this ?

A smaller repo may have limited benefits, as it is already a small repository. And all elixir code runs on  the erlang VM, so both erlang and elixir are required.

I've been doing some lsp work recently and we're getting it more consistent.
And the goto definition is migrated by me, haha, I just returned Location, I think I've already followed the spec: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_definition
the spec said we can return: result: Location | Location[] | LocationLink[] | null

can you update and test ? on my local it works.

it works, thank you.

glad to hear that .

If you don't mind, I'd be happy to add some unit tests to lspsaga, I think it would be great for easing your maintenance burden and for the long-term development of the project.
I may not be very familiar with Lua, but I am familiar with unit testing, and I enjoy doing it, and I have the time these days.
I know lsp has a lot of state dependencies, but there's also a lot of decision logic in there, so we can start with that part, similar to my neotest example in this PR, where I only tested the core decision logic.
But I'm not really familiar with the details of the lspsaga implementation, so it might take some time to explain it to me first.


Write direct messages to several users

I confirm (by marking "x" in the [ ] below):

[x] This is not a troubleshooting question. Troubleshooting questions go here: http://www.mattermost.org/troubleshoot/.
[ ] This doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
[x] I have read contributing guidelines.

Summary

It would be great to write direct messages to several users. This feature is really missing.

Thanks @viveris-villeurbanne, agree it would be nice to have feature!
Mattermost has an existing feature idea for group messaging here, I encourage you to upvote the feature so it can be discussed and prioritized along with the community.
Everyone gets 10 votes on the feature idea forum, influencing the future of Mattermost.

Closing the issue, we'll track it through the feature idea on the server side.
Thanks again for the feedback!


Log profiling async jobs

Add profiling for:

Sync Catalog Skill Definition async job
Report Catalog Skill async job

PR: https://github.com/NationalSecurityAgency/skills-service/pull/1286


Update AAD provider to include PIM for Groups data in JSON

💡 Summary
Update the AAD provider source code to get privileged user data based on PIM for Groups. The source code already includes PIM for Roles, so the could should be augmented to include PIM for Groups.
Implementation notes

[ ] Refer to the Cmdlets documented in the #756
[ ] Update the AAD provider code to add the PIM for Groups data to the provider export JSON

This is blocked on the completion of #756


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1200 ms

Resolved: Bofrost.lu performance has improved in c4e8464.


Update 3270 font to version 2.0.0

I hope you enjoy it as much as I do.

Thank you for putting my font to good use.


Can't restart because 'no datagram socket'

Hi!
In CentOS 6, when we restart sensu by puppet recipe (after configs changed), sensu-client can't start with error in log:
/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:868:in open_udp_socket': no datagram socket (RuntimeError) 	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:868:in open_datagram_socket'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.16.0/lib/sensu/client.rb:226:in setup_sockets' 	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.16.0/lib/sensu/client.rb:255:in start'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.16.0/lib/sensu/client.rb:13:in block in run' 	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in call'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in run_machine' 	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in run'
from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.16.0/lib/sensu/client.rb:12:in run' 	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.16.0/bin/sensu-client:10:in <top (required)>'
from /opt/sensu/bin/sensu-client:23:in load' 	from /opt/sensu/bin/sensu-client:23:in

:+1: Just hit this in our F20 infrastructure. It appears that Sensu leaked a file descriptor for the 3030 UDP listen socket to one of the child processes, which wasn't reaped during a restart of the parent, which prevented the new process from starting. cc/ @joemiller

I think we ran into this today as well, and I think we know why.
In our case, we have a very long-running sensu check (5-20mins, depending on host.. not ideal). We happened to hit a moment today when our chef procs issued a sensu-client restart, but that long-running check was underway and ignored the TERM signal. sensu-client eventually exited but when the new process tried to fork it could not bind to UDP :3030 because the long-running check had it open.
I think the fix might be to close fd's and not leak them to children?
Here are some relevant cut n pastes from our observation today:
[root@endpoint6f44e9c7 ~]# systemctl status sensu-client
sensu-client.service - sensu client
   Loaded: loaded (/etc/systemd/system/sensu-client.service; enabled)
   Active: activating (auto-restart) (Result: exit-code) since Tue 2015-02-17 23:16:32 UTC; 13s ago
  Process: 24749 ExecStart=/opt/sensu/bin/sensu-client -c /etc/sensu/config.json -d /etc/sensu/conf.d -e /etc/sensu/extensions -l /var/log/sensu/sensu-client.log (code=exited, status=1/FAILURE)
 Main PID: 24749 (code=exited, status=1/FAILURE)
   CGroup: /system.slice/sensu-client.service
           ├─16009 sudo /etc/sensu/plugins/check-rpm-verify.rb
           ├─16010 /usr/bin/ruby-mri /etc/sensu/plugins/check-rpm-verify.rb
           ├─16012 sh -c rpm -V --all 2>&1
           └─16013 rpm -V --all

^C

[root@endpoint6f44e9c7 ~]# tail -f /var/log/sensu/sensu-client.log
	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.16.0/lib/sensu/client.rb:226:in `setup_sockets'
	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.16.0/lib/sensu/client.rb:255:in `start'
	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.16.0/lib/sensu/client.rb:13:in `block in run'
	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `call'
	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `run_machine'
	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-em-2.4.0/lib/eventmachine.rb:187:in `run'
	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.16.0/lib/sensu/client.rb:12:in `run'
	from /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-0.16.0/bin/sensu-client:10:in `<top (required)>'
	from /opt/sensu/bin/sensu-client:23:in `load'
	from /opt/sensu/bin/sensu-client:23:in `<main>'

^C
[root@endpoint6f44e9c7 ~]# ps aux | grep sensu
root     16009  0.0  0.0 187108  2656 ?        S    23:06   0:00 sudo /etc/sensu/plugins/check-rpm-verify.rb
root     16010  0.1  0.1 138276  9368 ?        Sl   23:06   0:00 /usr/bin/ruby-mri /etc/sensu/plugins/check-rpm-verify.rb

[root@endpoint6f44e9c7 ~]# lsof -n -P | grep 3030
sudo      16009                                   root   11u     IPv4          642838877       0t0        UDP <IP_ADDRESS>:3030

[root@endpoint6f44e9c7 ~]# rpm -q sensu
sensu-0.16.0-1.x86_64

Also written up here: https://github.com/sensu/sensu-build/issues/95

Same/similar issue as https://github.com/sensu/sensu/issues/759
The socket close() was never added to the client stop(), or was lost during refactoring https://github.com/sensu/sensu/blob/master/lib/sensu/client/process.rb#L413 I can put together a PR for this shortly, as it should help.
I do not believe EM supports SO_REUSEADDR and SO_REUSEPORT :-1: Will investigate further.
Sean.

@robx interesting EM patch, we could test it w/ https://github.com/sensu/sensu-em unclear if we are sticking w/ the fork, as upstream has seen several improvements, just not the ones we needed.

https://github.com/sensu/sensu/pull/928

@portertech I ported the patch to the sensu em fork, thanks for the heads-up. Upstream eventmachine seems to be... resting.

Oh hey, I just noticed your fork of EM. Let's see what we can do to avoid the need for that for too long? That said, I'm not sure if this is an appropriate change in all cases - discuss on eventmachine/eventmachine#591 ?

Closing due to inactivity, and because it looks like all the related PRs have been merged. Please feel free to create a new issue if this matter is not resolved. #monitoringlove


How To Print Barcode with characters ?

How to print barcode with characters
need to Print A12345

@mjafartp this is easily done within your ticket with the following code:
// ...
  ticket.barcode(Barcode.code39(['A', 1, 2, 3, 4, 5]));
// ...

Note, that code39 is not the only applicable type of barcodes. You can find more, with explanation under the following link:
Types of Barcodes: Choosing the Right Barcode
So, if your Barcode will be in the fixed format "A12345", then you can use code39, and give it the List of data to be printed as parameter.
If you have any further Questions, don't hesitate to answer in this issue.
Otherwise it would be cool to close this (@andrey-ushakov).
Best Regards
Dsv

I think this could be closed then? @mjafartp


testing: TestTRun failing on the plan9/arm builder since CL 21504

Since CL 21504, TestTRun is failing on the plan9/arm builder.
--- FAIL: TestTRun (0.06s)
	sub_test.go:373: failnow skips future sequential and parallel tests at same level:ouput:
		got:
		--- FAIL: failnow skips future sequential and parallel tests at same level (0.01s)
		    --- FAIL: failnow skips future sequential and parallel tests at same level/#00 (0.00s)
		want:
		--- FAIL: failnow skips future sequential and parallel tests at same level (0.00s)
		    --- FAIL: failnow skips future sequential and parallel tests at same level/#00 (0.00s)
FAIL
FAIL	testing	3.440s

See http://build.golang.org/log/41d221b5accf16216bb6d9f1a767cbfff7c8e6f1
The plan9/arm builder is running on a Raspberry Pi 3, which is a slow machine. The output comparison is failing because the test executes slightly slower than expected.
Perhaps we should ignore the time when comparing the string. What do you think?
CC: @mpvl @bradfitz @millerresearch

Perhaps we should ignore the time when comparing the string. What do you think?

Yes, either sanitizeLog could remove the duration (N.NNs) from the end of lines, or the comparison between want: and got: could be done as a regular expression match (and sanitizeLog would not be needed).


Implementing LevelDB in QT

Hello I just compiled the level DB like it was told in the readme.md.
I obtain a dll and I put it into a folder with his includes.
I want integrate this db into a Qt Project so I open a .pro file and I do :
INCLUDEPATH += C:\Users\User\Documents\Project\leveldb
LIBS += -LC:\Users\User\Documents\Project\leveldb\lib -lleveldb
Then, I want test, so I saw the doc.
And I put exactly the same thing to test if it works but it isn't.
I can't use the lib I don't know why but I've this error :
error: undefined reference to leveldb::Options::Options()' In function qMain(int, char**)': undefined reference to `leveldb::Options::Options()'
error: undefined reference to `leveldb::DB::Open(leveldb::Options const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, leveldb::DB**)'.
But I include files like the doc.
Can you help me to solve this problem.
Cordially, L.

This is better suited for StackOverflow. This forum is for bugs in the LevelDB code.


loading: false hotfix

Codecov Report

Merging #3634 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #3634   +/-   ##
=======================================
  Coverage   99.19%   99.19%
=======================================
  Files          18       18
  Lines        1120     1120
  Branches      302      302
=======================================
  Hits         1111     1111
  Misses          9        9

Continue to review full report at Codecov.

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

Indeed, some test cases are necessary for consistency :)

@clarkdo good call :) I opened a separate PR with a e2e test fix.
https://github.com/nuxt/nuxt.js/pull/3635/files


[FEATURE] Support for I-JEPA

Hey Ross and @jph00,
I'm not sure if the issue tracker is the right place to ask or the forums (if not please close the issue).
I was mindblown by the performace of I-JEPA on low-shot image classification (12 images per class for SOTA Imagenet).
And was curious if timm is planning a support for I-JEPA
The model weights for imagenet are published too.
It looks like Attribution-NonCommercial 4.0 CC license.
Also happy to look into contributing myself, if support is planned.

Faster than light! Thanks for the response. Will close this issue for now.


Update graphql-core

graphql-core-next is being renamed to graphql-core and has had a few alpha releases. See https://github.com/graphql-python/graphql-core-next/releases/tag/v3.0.0a2 as well as https://github.com/graphql-python/graphene/blob/master/setup.py#L83.
At the very least, this would require a minor version bump because it may break things if users are relying on older versions of graphql-core-next. Please let me know if you'd like me to bump the version in the pyproject.toml file as well.

Hi, thanks for contributing to Strawberry 🍓!
We noticed that this PR is missing a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!
So as soon as this PR is merged, a release will be made 🚀.
Here's an example of RELEASE.md:
Release type: patch

Description of the changes, ideally with some examples, if adding a new feature.

Release type can be one of patch, minor or major. We use semver,so make sure to pick the appropriate type. If in doubt feel free to ask :)


@types/jquery fail my compilation

Hi all,
I'm not sure it's the good place for this ticket...
Today, I ran nom update and my compilation fail.
ERROR in /*****/node_modules/ng2-materialize/dist/textarea/textarea.directive.d.ts (21,27): Generic type 'JQuery<TElement, HTMLElement>' requires 2 type argument(s).
I found this: https://github.com/DefinitelyTyped/DefinitelyTyped/issues/17239.
With this in my package.json "@types/jquery": "^2.0.47",, I fix the build process.
Maybe you can add it in your package.json?

Hi!,
I had the same problem, I fixed it making a new project "ng new [project]" and loading the plugins again with npm.
My package.json
{   "name": "calendar-club",   "version": "0.0.0",   "license": "MIT",   "scripts": {     "ng": "ng",     "start": "ng serve",     "build": "ng build",     "test": "ng test",     "lint": "ng lint",     "e2e": "ng e2e"   },   "private": true,   "dependencies": {     "@angular/animations": "^4.0.0",     "@angular/common": "^4.0.0",     "@angular/compiler": "^4.0.0",     "@angular/core": "^4.0.0",     "@angular/forms": "^4.0.0",     "@angular/http": "^4.0.0",     "@angular/platform-browser": "^4.0.0",     "@angular/platform-browser-dynamic": "^4.0.0",     "@angular/router": "^4.0.0",     "core-js": "^2.4.1",     "mdi": "^1.9.33",     "ng2-materialize": "^1.4.2",     "rxjs": "^5.1.0",     "zone.js": "^0.8.4"   },   "devDependencies": {     "@angular/cli": "1.1.2",     "@angular/compiler-cli": "^4.0.0",     "@angular/language-service": "^4.0.0",     "@types/jasmine": "2.5.45",     "@types/node": "~6.0.60",     "codelyzer": "~3.0.1",     "jasmine-core": "~2.6.2",     "jasmine-spec-reporter": "~4.1.0",     "karma": "~1.7.0",     "karma-chrome-launcher": "~2.1.1",     "karma-cli": "~1.0.1",     "karma-coverage-istanbul-reporter": "^1.2.1",     "karma-jasmine": "~1.1.0",     "karma-jasmine-html-reporter": "^0.2.2",     "node-sass": "^4.5.3",     "protractor": "~5.1.2",     "ts-node": "~3.0.4",     "tslint": "~5.3.2",     "typescript": "~2.3.3"   } }
And angular-cli
{     "$schema"<EMAIL_ADDRESS>    "project": {         "name": "calendar-club"     },     "apps": [         {             "root": "src",             "outDir": "dist",             "assets": [                 "assets",                 "favicon.ico"             ],             "index": "index.html",             "main": "main.ts",             "polyfills": "polyfills.ts",             "test": "test.ts",             "tsconfig": "tsconfig.app.json",             "testTsconfig": "tsconfig.spec.json",             "prefix": "app",                 "styles": [                     "styles.scss",                     "../node_modules/materialize-css/dist/css/materialize.css",                     "../node_modules/mdi/css/materialdesignicons.css"                 ],                 "scripts": [                     "../node_modules/jquery/dist/jquery.js",                     "../node_modules/materialize-css/dist/js/materialize.js"                     ],             "environmentSource": "environments/environment.ts",             "environments": {                 "dev": "environments/environment.ts",                 "prod": "environments/environment.prod.ts"             }         }     ],     "e2e": {         "protractor": {           "config": "./protractor.conf.js"         }     },     "lint": [         {             "project": "src/tsconfig.app.json"         },         {             "project": "src/tsconfig.spec.json"         },         {             "project": "e2e/tsconfig.e2e.json"         }     ],     "test": {         "karma": {             "config": "./karma.conf.js"         }     },     "defaults": {         "styleExt": "scss",         "component": {}     } }

Hi @DarkIsDude,
When creating a new project there is actually a problem with the version of @types/jquery that is pulled via @types/materialize-css as it pull on the latest type version which is made for JQuery 3.
This will be fix in 1.5.0 but in the meanwhile the workaround is exactly what you did, install manually the right version of @types/jquery
Using yarn
yarn install<EMAIL_ADDRESS>--save-dev

Or plain npm
npm install<EMAIL_ADDRESS>--save-dev

I' m having this issue after upgrading to the latest version of ng2-materialize.
running npm install<EMAIL_ADDRESS>--save-dev doesn't help.
@jfcere

Hi @rsaf,
Since v1.6.0 of ng2-materialize it needs @types/jQuery v3.2.12 or higher so no npm install<EMAIL_ADDRESS>--save-dev won't help.
Can you try to delete your node_modules folder, run npm cache clean and/or yarn cache clean and reinstall your packages?
If this does not fix the issue, please post your package.json file here so we can take a look at your dependencies.

@jfcere Thanks for your quick response. It's working now.

@jfcere Don't know how related this issue is, but I'm getting:
"../node_modules/ng2-materialize/dist/select/select.directive.d.ts (22,29): Generic type 'JQuery<TElement, HTMLElement>' requires 2 type argument(s)." Even after installing @types/jquery v3.2.12 .
Here's my package.json:
{
  "name": "data-jitsu",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular/common": "^4.0.0",
    "@angular/compiler": "^4.0.0",
    "@angular/core": "^4.0.0",
    "@angular/forms": "^4.0.0",
    "@angular/http": "^4.0.0",
    "@angular/platform-browser": "^4.0.0",
    "@angular/platform-browser-dynamic": "^4.0.0",
    "@angular/router": "^4.0.0",
    "@types/youtube": "0.0.29",
    "angular-froala-wysiwyg": "^2.7.2-1",
    "angular2-materialize": "^15.1.10",
    "core-js": "^2.4.1",
    "hammerjs": "^2.0.8",
    "jquery": "^2.2.4",
    "materialize-css": "^0.100.2",
    "ng2-materialize": "^1.7.2",
    "ngx-youtube-player": "0.0.41",
    "rxjs": "^5.1.0",
    "zone.js": "^0.8.4"
  },
  "devDependencies": {
    "@angular/cli": "1.0.0",
    "@angular/compiler-cli": "^4.0.0",
    "@types/bootstrap": "^3.3.36",
    "@types/jasmine": "2.5.38",
    "@types/jquery": "^3.2.12",
    "@types/node": "~6.0.60",
    "codelyzer": "~2.0.0",
    "jasmine-core": "~2.5.2",
    "jasmine-spec-reporter": "~3.2.0",
    "karma": "~1.4.1",
    "karma-chrome-launcher": "~2.0.0",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "^0.2.0",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "~5.1.0",
    "ts-node": "~2.0.0",
    "tslint": "~4.5.0",
    "typescript": "~2.2.0"
  }
}

I don't know how important it is that jquery in dependencies and @types/jquery in devDependencies be the same, but when I tried to make them the same, npm protested, telling me, "npm ERR! notarget No matching version found for<EMAIL_ADDRESS>Any suggestions welcome!

Also, how dangerout is npm cache clean --force?

@types/jquery requires typescript to be 2.3.0 at least... see jquery.d.ts reference here.


Cannot find name '__renew'.

code following
const myClassInstance= JSON.parse(jsonString)
then i exec  npm run asbuild
it reports error following:
`ERROR TS2304: Cannot find name '__new'.
 this.buffer = changetype<ArrayBuffer>(__new(
                                       ~~~~~

in ~lib/as-string-sink/index.ts(21,43)
ERROR TS2304: Cannot find name '__renew'.
   this.buffer = changetype<ArrayBuffer>(__renew(
                                         ~~~~~~~

in ~lib/as-string-sink/index.ts(146,45)
ERROR TS2304: Cannot find name '__new'.
 let out = changetype<string>(__new(size, idof<string>()));
                              ~~~~~

in ~lib/as-string-sink/index.ts(136,34)`

Seems like something related to as-string-sink. Are you using the latest version of the AssemblyScript loader and language?
If it persists, ask in the AssemblyScript Discord

Closing this because it isn't directly related with as-json


Phase 2 Integration

PR for full phase 2 support for the Espero trusted setup. Tested by running e2e/e2ephase2.sh to completion. Loads precomputed circuits for testing with parameter --circuit-filename. Circuits can be generated for testing using https://github.com/celo-org/celo-bls-snark-rs/blob/mrsmkl/serialize-circuit/crates/epoch-snark/examples/constraints.rs

Overall looks very good.
The biggest point of friction I see is that we now, as users, have to enter the phase manually rather than receive it from the server. I think it will be preferable if it's sent from the server if possible.

Any thoughts about this @mstraka100 ?

Overall looks very good.
The biggest point of friction I see is that we now, as users, have to enter the phase manually rather than receive it from the server. I think it will be preferable if it's sent from the server if possible.

Any thoughts about this @mstraka100 ?

I think it would be easier to just use conditional compilation to choose the default phase, as in:
#[options(help = "phase to be run. Must be either phase1 or phase2", default = "phase1")]
pub phase: String,
#[cfg(feature = "phase_2")]
#[options(help = "phase to be run. Must be either phase1 or phase2", default = "phase2")]
pub phase: String,
#[options(help = "phase to be run. Must be either phase1 or phase2")]
pub phase: String,
    Thoughts? The only trade-off I see here is that participants from phase 1 won't be able to reuse the same contribute binary, or might use theirs on accident. But this throws a pretty obvious error and shouldn't interfere with the ceremony:

    [00:00:00] [--------------------] 0/256 Contributing to chunk 201 (Download)...

{"level":50,"time":1622240258383,"pid":95209,"hostname":"C02Z28CMLVCF","name":"coordinator-service","msg":"participant 0xc31130dc73f078f99fac28e250535cbc3407608d reported error for chunk 201: Failed running contribute: The size of challenge file should be 1024, but it's 395060, so something isn't right

I disagree. The changes needed to make this a server side decision are so
small that I believe the effort is worth it. We should strive for Espero to
be usable for other groups as well ideally. If your point is that it’s hard
to do, then sure, let’s delay it.
On Sat, 29 May 2021 at 1:29 Michael Straka @.***> wrote:

Overall looks very good.
The biggest point of friction I see is that we now, as users, have to
enter the phase manually rather than receive it from the server. I think it
will be preferable if it's sent from the server if possible.
Any thoughts about this @mstraka100 https://github.com/mstraka100 ?
I think it would be easier to just use conditional compilation to choose
the default phase, as in:
#[options(help = "phase to be run. Must be either phase1 or phase2",
default = "phase1")]
pub phase: String,
#[cfg(feature = "phase_2")]
#[options(help = "phase to be run. Must be either phase1 or phase2",
default = "phase2")]
pub phase: String,
#[options(help = "phase to be run. Must be either phase1 or phase2")]
pub phase: String,
Thoughts? The only trade-off I see here is that participants from phase 1 won't be able to reuse the same contribute binary, or might use theirs on accident. But this throws a pretty obvious error and shouldn't interfere with the ceremony:

[00:00:00] [--------------------] 0/256 Contributing to chunk 201 (Download)...

{"level":50,"time":1622240258383,"pid":95209,"hostname":"C02Z28CMLVCF","name":"coordinator-service","msg":"participant
0xc31130dc73f078f99fac28e250535cbc3407608d reported error for chunk 201:
Failed running contribute: The size of challenge file should be 1024, but
it's 395060, so something isn't right
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/celo-org/snark-setup-operator/pull/62#issuecomment-850704371,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA23MGDV5ULNTBC7JPOEBCLTQAKMRANCNFSM443LYQXQ
.

I disagree. The changes needed to make this a server side decision are so small that I believe the effort is worth it. We should strive for Espero to be usable for other groups as well ideally. If your point is that it’s hard to do, then sure, let’s delay it.
…
On Sat, 29 May 2021 at 1:29 Michael Straka @.***> wrote: Overall looks very good. The biggest point of friction I see is that we now, as users, have to enter the phase manually rather than receive it from the server. I think it will be preferable if it's sent from the server if possible. Any thoughts about this @mstraka100 https://github.com/mstraka100 ? I think it would be easier to just use conditional compilation to choose the default phase, as in: #[options(help = "phase to be run. Must be either phase1 or phase2", default = "phase1")] pub phase: String, #[cfg(feature = "phase_2")] #[options(help = "phase to be run. Must be either phase1 or phase2", default = "phase2")] pub phase: String, #[options(help = "phase to be run. Must be either phase1 or phase2")] pub phase: String, Thoughts? The only trade-off I see here is that participants from phase 1 won't be able to reuse the same contribute binary, or might use theirs on accident. But this throws a pretty obvious error and shouldn't interfere with the ceremony: [00:00:00] [--------------------] 0/256 Contributing to chunk 201 (Download)... {"level":50,"time":1622240258383,"pid":95209,"hostname":"C02Z28CMLVCF","name":"coordinator-service","msg":"participant 0xc31130dc73f078f99fac28e250535cbc3407608d reported error for chunk 201: Failed running contribute: The size of challenge file should be 1024, but it's 395060, so something isn't right — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#62 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA23MGDV5ULNTBC7JPOEBCLTQAKMRANCNFSM443LYQXQ .

I don't think the server-side solution would be hard to do, just that it's better on principle to minimize moving parts in the code when there's no downside to doing so. What is the benefit you have in mind for the server solution over conditional compilation?

Off the top of my head - less room for deployment mistakes or user errors
in downloading wrong binaries, less to verify as a user, less knowledge
needed if compiling from source, less complexity in the build process.
But happy to talk more hehe
On Sat, 29 May 2021 at 2:15 Michael Straka @.***> wrote:

I disagree. The changes needed to make this a server side decision are so
small that I believe the effort is worth it. We should strive for Espero to
be usable for other groups as well ideally. If your point is that it’s hard
to do, then sure, let’s delay it.
… <#m_-5272591981309996232_>
On Sat, 29 May 2021 at 1:29 Michael Straka @.***> wrote: Overall looks
very good. The biggest point of friction I see is that we now, as users,
have to enter the phase manually rather than receive it from the server. I
think it will be preferable if it's sent from the server if possible. Any
thoughts about this @mstraka100 https://github.com/mstraka100
https://github.com/mstraka100 ? I think it would be easier to just use
conditional compilation to choose the default phase, as in: #[options(help
= "phase to be run. Must be either phase1 or phase2", default = "phase1")]
pub phase: String, #[cfg(feature = "phase_2")] #[options(help = "phase to
be run. Must be either phase1 or phase2", default = "phase2")] pub phase:
String, #[options(help = "phase to be run. Must be either phase1 or
phase2")] pub phase: String, Thoughts? The only trade-off I see here is
that participants from phase 1 won't be able to reuse the same contribute
binary, or might use theirs on accident. But this throws a pretty obvious
error and shouldn't interfere with the ceremony: [00:00:00]
[--------------------] 0/256 Contributing to chunk 201 (Download)...
{"level":50,"time":1622240258383,"pid":95209,"hostname":"C02Z28CMLVCF","name":"coordinator-service","msg":"participant
0xc31130dc73f078f99fac28e250535cbc3407608d reported error for chunk 201:
Failed running contribute: The size of challenge file should be 1024, but
it's 395060, so something isn't right — You are receiving this because your
review was requested. Reply to this email directly, view it on GitHub <#62
(comment)
https://github.com/celo-org/snark-setup-operator/pull/62#issuecomment-850704371>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA23MGDV5ULNTBC7JPOEBCLTQAKMRANCNFSM443LYQXQ
.
I don't think the server-side solution would be hard to do, just that it's
better on principle to minimize moving parts in the code when there's no
downside to doing so. What is the benefit you have in mind for the server
solution over conditional compilation?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/celo-org/snark-setup-operator/pull/62#issuecomment-850716198,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA23MGGBWCDXBRVQH7EJ223TQAPZZANCNFSM443LYQXQ
.

Off the top of my head - less room for deployment mistakes or user errors in downloading wrong binaries, less to verify as a user, less knowledge needed if compiling from source, less complexity in the build process. But happy to talk more hehe

Not entirely convinced since I think it's more opaque if you're working with the code, and introduces the possibility of server-side errors which would be more complicated to debug. But I'm convinced now the tradeoffs are close enough that I'm fine with implementing phases server-side, probably just as a chunk field

@kobigurk Thoughts on having phase be an optional parameter, where leaving it empty defaults to downloading the phase from the server and passing it in manually has the current behavior (overrides the server choice)? This would give the UI/build simplicity we want while also maintaining flexibility in debugging server-side issues

Love it
On Sun, 30 May 2021 at 6:34 Michael Straka @.***> wrote:

@kobigurk https://github.com/kobigurk Thoughts on having phase be an
optional parameter, where leaving it empty defaults to downloading the
phase from the server and passing it in manually has the current behavior
(overrides the server choice)? This would give the UI/build simplicity we
want while also maintaining flexibility in debugging server-side issues
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/celo-org/snark-setup-operator/pull/62#issuecomment-850934058,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA23MGBW3SJTDURPRLOVEIDTQGW6BANCNFSM443LYQXQ
.


added format argument to specify alternative output format

The reason I've added this is because the default format dictates that there should be spaces between the components, i.e. "4 weeks ago". But since I'm using the localization to replace "weeks" with "w", I want it to appear as "4w ago", for which I need to change the format.
This would also be useful in locales that might print it differently, for example, "depuis 4 semaines" (http://bit.ly/1GtxGwX)

awesome idea


Create pip installer

This will not be used for the modeling framework, but can be useful for other projects and for wider distribution.

Published pip installer (source dist only, at the moment). Seems conceptually simpler to distribute it with everything, so I included the modeling framework.
https://pypi.python.org/pypi?:action=display&name=Fathom-Workloads
The name "Fathom" was taken so the package name is "Fathom-Workloads" instead.


adopted and modified P4-14 description on parser value set to P4-16

P4-14 spec has a section about parser value set that is still applicable to P4-16 with some modifications. I added that section in this PR

I think that the match_type is really very target-specific; as a proof, v1model.p4 contains the definition of match_type range. Probably this should really be an annotation:
@implement(ternary)
value_set<S> set;

@mbudiu-bfn ,
I think that the significance of match_type in value_sets is no different than the one in tables and thus we need to use a very similar mechanism. It should be a part of the language, IMHO.

Regarding match_kind for value sets, do you think for multi-field value sets, e.g. that match on a struct, that it should be possible to specify a different match_kind for each field, like you can in a table?
If so, it seems we are inching our way towards a value set specified much like a P4 table, except with no list of actions.

Attempted to write down what Vlad is saying,
    value_set pvs {
        key = { p.data.da : exact; }
    }

    state start {
        b.extract(p.data);
        transition select(p.data.da) {
            pvs: accept;
            0x810: foo;
        }
    }

Here is a link to the solution that the P4runtime working group came up to solve the naming problem for field list which is not part of P4-16.
https://github.com/p4lang/PI/blob/master/proto/docs/p4runtime_type_serialization.md
The associated proto file for p4types.
https://github.com/p4lang/PI/blob/master/proto/p4/p4types.proto

@hanw This might work, but will limit the ability to use the same value_set in multiple parser states. I would suggest using names that are not bound to anything, more like formal parameters for a function.

@hanw ,

Here is a link to the solution that the P4runtime working group came up to solve the naming problem for field list which is not part of P4-16. https://github.com/p4lang/PI/blob/master/proto/docs/p4runtime_type_serialization.md

I might be wrong but I do not see a solution for naming individual members of an unnamed field list there. If these are just numbers, this is not a good API solution for value_sets.

I updated p4c frontend to allow struct type for the value set https://github.com/p4lang/p4c/pull/1271
to address the issue of the naming objects in the value set in runtime API.
We (Vlad, Calin and I) had an offline discussion on the PR. To summarize the discussion, the proposal for value_set must satisfy the following constraints:

it must have a ‘size’.
it must have a ‘name’.
it must support simple datatypes, such as BitType and TupleType.
it must be able to generate meaningful API.
it must support more complex datatype, such as StructType(to be able to name the fields)
it must support sharing between parser states.
it must support multiple match_kind: exact, ternary, range.

The current proposal of
value_set<T> name (size);

satisfies all 7 requirements, but needs an annotation on the value_set instance to specify the match_kind. An option was proposed to integrate the match_kind in the struct as:
struct vsk_t {
    bit<16> field : ternary;
}

But the discussion on this proposal can happen in a different thread as part of the modularity discussion.
We suggest the working group to accept this PR.

You should then use annotations on struct fields:
struct vsk_t {
    @match(ternary)
    bit<16> field;
}

@mbudiu-vmw can we merge this PR?

I would appreciate if @vgurevich and @jafingerhut would take a look as well.

@mbudiu-vmw I have added my review comments.

@hanw It would also be good to edit Appendix D "Restrictions on compile time and run time calls" to mention value_set's and their proposed restrictions, everywhere that a P4 table is mentioned already.  value_set's might not have identical restrictions to tables, but they are a new stateful element that is very similar to them, and people might look to that section for ideas on where they need to support it, vs. need not.

@hanw : I think we are close to merging this; @jafingerhut makes some good points that maybe you can address.

I modified Appendix D to specify the restrictions on value-set, please take a look at to make sure the text is accurate.

make sense, I fixed that column.


Resize / drag and text select

Looks like react-draggable and react-resizable attempt to prevent text select. While the mouse is pressed and moving, -webkit-user-select: none; is added to <body>. Despite all this, I am still able to observe this unwanted effect.
The following workaround partially solves the problem, with not for all cases:
// New method for component that contains the grid
  _preventTextSelect(a, b, c, d, event) {
    event.preventDefault();
  },

// In render()
      <MyReactGridLayout
        layout={ layout }
        onDrag={ this._preventTextSelect }
        onResize={ this._preventTextSelect }
        onResizeStop={ this._preventTextSelect }
        {...this.props}
      >

Attaching preventTextSelect() to the three events does not help when the size of a grid item has reached some allowed limit and so mouse movements temporary do not change it. Because event.preventDefault(); is not called under such conditions, text selection stats to appear and change.
The above was observed in Chrome Version 50.0.2661.86 (64-bit) os OSX (not only in my project, but the examples too).
Anyone else with the same issue? Any thoughts?

I can't replicate this on Chrome 51.0.2704.22 beta (64-bit) - OSX.
Could you try Beta/Canary or Firefox and see if you still have the issue there? I noticed a few Chrome regressions in 50, perhaps you're running into another one of them.

Unfortunately I could observe this in FF 45 on Mac as well:
.

Interestingly, my hack does not even work in FF

@kachkaev did you manage to solve this problem? I am experiencing the same with Chrome 53.0.2785.116 (64-bit)

@AmirMeirbekov no I'm afraid :–( Haven't been using this grid for a while.

remember that:
Include the following stylesheets in your application:
/node_modules/react-grid-layout/css/styles.css
/node_modules/react-resizable/css/styles.css

I'm getting this on Chrome Version 76.0.3809.87 (Official Build) (64-bit)
I've included the stylesheets files in my project:
/node_modules/react-grid-layout/css/styles.css
/node_modules/react-resizable/css/styles.css

My fix was to add user-select: none to the react-grid-layout DOM container.

For firefox and safari, adding user-select and its relevant vendor prefixes prevents selection while dragging, but it creates another problem wherein the scrolling up/down behaviour when an item is dragged up to the edges stops working...

I fixed by add
.react-draggable-transparent-selection {   user-select: none; }

For me, the highlighting was happening while using react's strict mode.  DraggableCore appears to add the react-draggable-transparent-selection class to the body el on drag start and then removes it either on drag stop or component will unmount.  When in strict mode, react does an extra mount/unmount/mount cycle.  So, I could see the class getting added on drag start, but then it would disappear when actually dragging the item...presumably due to extra unmounts during rendering. Since the class only gets added on drag start, it would stay removed during dragging and the highlighting issues would ensue.
Disabling strict mode and/or using a production build removed the issue. Hopefully this saves someone else some time.

你好，邮件已收到，谢谢。。

I do this approach inside a Nextjs app using tailwind:
onDragStart={() => {
	if (isBrowser) {
		document.querySelector('body').classList.add('select-none')
	}
}}
onDragStop={() => {
	if (isBrowser) {
		document.querySelector('body').classList.remove('select-none')
	}
}}

你好，邮件已收到，谢谢。。

For firefox and safari, adding user-select and its relevant vendor prefixes prevents selection while dragging, but it creates another problem wherein the scrolling up/down behaviour when an item is dragged up to the edges stops working...

is there any solution to the auto-scroll issue?

For me, the highlighting was happening while using react's strict mode. DraggableCore appears to add the react-draggable-transparent-selection class to the body el on drag start and then removes it either on drag stop or component will unmount. When in strict mode, react does an extra mount/unmount/mount cycle. So, I could see the class getting added on drag start, but then it would disappear when actually dragging the item...presumably due to extra unmounts during rendering. Since the class only gets added on drag start, it would stay removed during dragging and the highlighting issues would ensue.
Disabling strict mode and/or using a production build removed the issue. Hopefully this saves someone else some time.

This helped for me, thank you so much 🙏🏻 🙌🏻

你好，邮件已收到，谢谢。。


D-Bus adapter tests in GitHub Actions

The current dev version has integration tests for D-Bus adapter(s), which run without errors locally. In the GitHub Actions these tests fail because the environment variable DBUS_SESSION_BUS_ADDRESS is not set, and jeepney tries to use that for getting the bus address of the session bus.
The current py37 test (running on Ubuntu 20.04) has only system bus running:
$ ps -ef | grep dbus | grep -v grep
     672       1  0 18:16 ?        00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

and the py310 tests (running on Ubuntu 22.04.3 LTS) actually has session bus running:
$ ps -ef | grep dbus | grep -v grep
      578       1  0 18:20 ?        00:00:00 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
      1499     768  0 18:20 ?        00:00:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

but the session bus has not been advertized on DBUS_SESSION_BUS_ADDRESS.
Task:

Make the dbus adapter tests work in the GitHub Actions.

Fixed in https://github.com/fohrloop/wakepy/pull/159


Hard to tell when new interaction points are added while watching.

A first solution could be to add numbers to interaction points, in order that they appear in time

@Kristof-Heyndels @lg188 Is it possible to test the code in pull request on VR headsets?


Proposal: (no-unused-modules) Restrict report to the identifier on named exports.

First of all thanks for the tool. I would like to propose a change in the reporting behavior for the rule no-unused-modules:
Currently the rule "flags" all the ExportNamedDeclaration body for unused exports, but when using tools like vscode-eslint the editor gets pretty convoluted with all lines being painted when you are working on a new exported function. This behavior also creates a misleading situation when exporting multiple variables within a unique export keyword, if one of the variables is unused, all the variables in the block gets flagged.
The new behavior is consistent with rules like "@typescript-eslint/no-unused-vars" where only the identifier is flagged if the variable is unused. I attached 2 images showing the current and the new behavior on my IDE.

I think the challenge here is that it's not warning on the value being unused, it's warning on the export itself being unused.
In other words, it might still be used in the same file - just not outside the file. Can we target the export as well as the identifier, or can you only target a single node?

Coverage increased (+1.6%) to 71.142% when pulling 30aaac82c4546c700ca378549be138c7376cedaa on edupsousa:edupsousa/unused-export-identifier into e871a9a2e18fd4d67a5a237789131b44cc705b5b on benmosher:master.

Coverage increased (+1.6%) to 71.142% when pulling 30aaac82c4546c700ca378549be138c7376cedaa on edupsousa:edupsousa/unused-export-identifier into e871a9a2e18fd4d67a5a237789131b44cc705b5b on benmosher:master.

Coverage increased (+1.6%) to 71.142% when pulling 30aaac82c4546c700ca378549be138c7376cedaa on edupsousa:edupsousa/unused-export-identifier into e871a9a2e18fd4d67a5a237789131b44cc705b5b on benmosher:master.

@ljharb i agree with you that targeting the export would show better what the rule means, but the context.report() method expects a single loc parameter continuous from start to end, so if you have something in between the export and the identifier (like the lines 6-7 of the screenshots) this behavior will not work. :-(

I'm all for making the targeted node more useful! I'm not sure this actually achieves that, though - it just makes it less noisy, which isn't always better.


Template.layout is undefined

I'm having an issue:

clean install
packages and versions:

accounts-password         1.5.1  Password support for accounts
accounts-ui               1.3.0  Simple templates to add login widgets to an app
alanning:roles            1.2.16  Authorization package for Meteor
blaze-html-templates      1.1.2  Compile HTML templates into reactive UI with Meteor Blaze
cultofcoders:grapher      1.3.7  Grapher is a data fetching layer on top of Meteor
ecmascript                0.11.1  Compiler plugin that supports ES2015+ in all .js files
es5-shim                  4.8.0  Shims and polyfills to improve ECMAScript 5 support
jquery                    1.11.11  Manipulate the DOM using CSS selectors
juliancwirko:postcss      2.0.3  Minifier for Meteor with PostCSS processing - use Autoprefixer and others with ease
less                      2.7.12  Leaner CSS language
meteor-base               1.4.0  Packages that every Meteor app needs
mobile-experience         1.0.5  Packages for a great mobile user experience
mongo                     1.5.1  Adaptor for using MongoDB and Minimongo over DDP
msavin:mongol             7.0.1  In-App MongoDB Editor.. now supports Meteor 1.7 and Collection 2 3.0
ostrio:flow-router-extra  3.5.0  Carefully extended flow-router with waitOn and template context
reactive-var              1.0.11  Reactive variable
semantic:ui               2.3.1  Official Semantic UI Integration for Meteor
semantic:ui-data          2.3.1  Data package for Semantic UI Meteor
shell-server              0.3.1  Server-side component of the `meteor shell` command.
standard-minifier-js      2.3.4  Standard javascript minifiers used with Meteor apps by default.
tracker                   1.2.0  Dependency tracker to allow reactive callbacks

set up initial page according to your instructions
error message in console on loading a page:

TypeError: Template.layout is undefined default.js:6
where default.js is:
import { Template } from 'meteor/templating';
import './default.html';

// As example all available Template's callbacks
// layout should be considered as a regular template
Template.layout.onCreated(function () { /* ... */ });
Template.layout.onRendered(function () { /* ... */ });
Template.layout.onDestroyed(function () { /* ... */ });
Template.layout.helpers({ /* ... */ });
Template.layout.events({ /* ... */ });

missing a dependency, maybe?

my mistake, or something that could be made more clear in the documentation.
solution:
Template.default.onCreated(function () { /* ... */ });
Template.default.onRendered(function () { /* ... */ });
Template.default.onDestroyed(function () { /* ... */ });
Template.default.helpers({ /* ... */ });
Template.default.events({ /* ... */ });

must use the name of the template. I wrongly assumed that "layout" is a built-in function.

Hello @tvogt ,
I'm glad you've figured it out on your own.
Our Templating docs starts with create layout.


[Snyk] Upgrade react-query from 3.39.1 to 3.39.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade react-query from 3.39.1 to 3.39.2.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2022-07-15.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report

Merging #312 (86eef37) into main (96992d4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #312   +/-   ##
=======================================
  Coverage   82.82%   82.82%
=======================================
  Files          29       29
  Lines         396      396
  Branches       59       59
=======================================
  Hits          328      328
  Misses         62       62
  Partials        6        6

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Styles do not get applied using Styled Components library

Is your feature request related to a problem? Please describe.
When using the styling library Styled Components  the styling does not get applied.
Describe the solution you'd like
Documented steps on how to get it working or a basic working example.
Describe alternatives you've considered
I have considered using Tailwind and might default to that if I can not find a solution.

Can you provide some example?
E.g here: https://codesandbox.io/p/sandbox/react-new

Hi, I have created a repo with a basic example of a styled component. It is a content page.
https://github.com/OwenSamuel/chrome-extension-boilerplate-react-vite

Can you provide some example?
E.g here: https://codesandbox.io/p/sandbox/react-new

Hi, I have created a repo with a basic example of a styled component. It is a content page. You can see the content is there but the styling does not get pulled through.
https://github.com/OwenSamuel/chrome-extension-boilerplate-react-vite

Now i remeber sth, i probably have the same problem on my project, but this is not issue with template i think, but i will take a look on that, and let you know, stay tuned 😉

@OwenSamuel
Consider emotion with an almost identical interface?
Here's an example built with emotion. Check it out if you like!

https://github.com/Jonghakseo/drag-gpt-extension
https://github.com/Jonghakseo/drag-gpt-extension/tree/main/src/pages/content/src/ContentScriptApp/emotion

I'm closing the issue, please reopen if necessary.


trigger beacon sync error: beacon syncer reorging

What we should do  once facing this error
Process new L1 blocks error              error="trigger beacon sync error: beacon syncer reorging"

This is normal. You can ignore this and your node will work as fine


Option to select which element to wrap around the highlighted text

current default is strong

Yes, please!


TestWorkflowEnvironment should surface errors and respect failure signal surfaced by underlying mock

Expected Behavior
Say I expect testWorkflow to invoke testActivity twice with certain arguments
env.OnActivity(testActivity, mock.Anything, testActivityParams{...}).Return(...).Times(2)
req := testWorkflowRequest{...}

// Workflow actually invokes testActivity three times. Expect to see a test failure here due to the extra unexpected invocation.
env.ExecuteWorkflow(testWorkflow, req)

Actual Behavior

Test passes, but seeing the following error message from test output:

assert: mock: The method has been called over 2 times.
	Either do one more Mock.On(testActivity).Return(...), or remove extra call.
	This call was unexpected: ...

env.AssertExpectations doesn't catch the extra invocation, as it delegates to testify's mock.AssertExpectations, which only verifies that all configured invocations have been satisfied.
env.AssertNumberOfCalls doesn't catch the extra invocation either. Instead this happens:

env.OnActivity(testActivity, mock.Anything, testActivityParams{...}).Return(...).Times(2)
req := testWorkflowRequest{...}

// Workflow actually invokes testActivity three times but test doesn't fail
env.ExecuteWorkflow(testWorkflow, req)

// Expect this assertion to fail but it passes
env.AssertNumberOfCalls("testActivity", 2)
// Expect this assertion to succeed but it fails
env.AssertNumberOfCalls("testActivity", 3)

I think this behavior has to do with the fact that env.AssertNumberOfCalls delegates to testify's mock.AssertNumberOfCalls. However, testify expects the test to have already failed early when the extra invocation occurred, and therefore does not increment its invocation counter. As a result, when the test unexpectedly continued on, the actual invocation counter remains at 2 even though there have been 3 calls to the activity.
testify's behavior seems correct and reasonable in this case. However, I'd expect TestWorkflowEnvironment to surface and respect the error and failure surfaced by testfify and mark the test case as failed.
Steps to Reproduce the Problem
See above
Specifications

Version: v1.18.1
Platform: macOS Ventura 13.3.1

I admit to not looking into this, but just curious if you can confirm that env.GetWorkflowError() is nil?

Yes. I assert env.GetWorkflowError() is nil in all my test cases, and invoke AssertExpectations as part of AfterTest.


Move context out from info and expose it as a parameter

Being able to request info (and root) only when needed is a nice feature, but considering we haven't exposed a type for info yet, it might be nice to all to request for context as well
So, from this:
@strawberry.federation.type(extend=True)
class Query:
    @strawberry.field
    def strawberry(self, info) -> str:
        return info.context.strawberry_repo.get_one()

to this:
@strawberry.federation.type(extend=True)
class Query:
    @strawberry.field
    def strawberry(self, context: MyContextType) -> str:
        return context.strawberry_repo.get_one()

Upvote & Fund

We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

Ah this would be awesome!
It would solve the problem with PyCharm not autocompleting custom contextes without the mypy plugin also!


update copyright

minor update
Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
All new code requires tests to ensure against regressions

Description of the Change

Alternate Designs

Why Should This Be In The Gem?

Benefits

Possible Drawbacks

Verification Process

Applicable Issues (Optional)

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


Improve handling if the same repository is cloned multiple times

If git-repo or Git submodules are used, it is possible that the same repository is cloned multiple times in the directory tree passed to the analyzer. Currently that causes the analyzer to create errors like this:

Multiple projects with the same id 'Gradle:com.example:lib:1.0-SNAPSHOT' found. Not adding the project defined in<EMAIL_ADDRESS>to the analyzer results as it duplicates the project defined in<EMAIL_ADDRESS>
If each clone of the repository uses the same revision, the analyze could detekt that and not try to analyze it multiple times. To correctly capture this in the analyzer result it would be required to allow multiple definition file paths for a project.
Another fix would be to allow multiple projects with the same id in an analyzer result, but this would require many code changes, as a lot of code is currently expecting that ids are unique.

Yet another option would be to assign an artificial unique project id for the second project, like by using the parent directory name / path to the VCS root as a prefix, similar to like we do already for Pip (IIRC) to be able to distunguish multiple requirements.txt-based projects in the tree.

Basically yes, but it's more complex. For the scanner we can clone and scan the repositories separately, but for the analyzer it is possible that a project depends on the submodules to be there to function correctly, so we cannot assume that cloning and analyzing the repositories separately would work.

@mnonnenmacher, this is still an issue despite https://github.com/oss-review-toolkit/ort/pull/4660 being merged, correct?

I wonder whether the WorkingTreeCache could somehow be used to detect such cases and analyze "duplicate" repos only once.

Closed as part of backlog grooming. Feel free to comment if you would like to contribute to this.


BasicTasks.cls and CollectionsTasks.cls are updated

The previous PR was to main branch, so I closed it

@baksale could you please check this PR again? ^_^

Task accepted.


Doesn't execute the scheduled work after rebooting the device on Android 10 if targetSdkVersion = 29

I have an issue when I set targetSdkVersion 29 and start my periodic work on Android 10 and reboot my device, then after rebooting the Worker doesn't execute at the scheduled time (the Worker is executed only after the application starts). With targetSdkVersion 28, everything works well.

I found a workaround to this issue, it is to have BootReceiver, which will restart the application after reboot. It will be great if WorkManager will work as expected without any workarounds.

Thanks for reporting this.
That behavior seems really strange.
Can you please open a bug on the WorkManager public issue tracker: https://issuetracker.google.com/issues/new?component=409906&template=1094197
With some additional information like if this is happening on the emulator or on a specific device?
Thanks

Yes, I created an issue there https://issuetracker.google.com/issues/140611845,
but the behavior looks very strange, because WorkManager began to reschedule work after a few reboots, and my colleague also had the same problem on Pixel 3a (Android 10), and it was also fixed after a few reboots

I experienced this on Huawei P30/Lite devices, opened a separate issue for it already

Closing. Please continue the discussion on the public issuetraker bug.


Toyota: use radar in place of abs for platform code ECU

Looking at the non-zero TTFF list, this would have solved a fair amount of the Toyota cases in the last few months. Will need to do some verification to ensure that nothing regresses.
The reason we chose abs over fwdRadar was because it nicely split ICE and hybrid cars, before we combined them. However, this means that it is too sensitive to minor differences within the same model year and generation (it shows trim and engine differences sometimes).
If we switch to fwdRadar, we need to combine the rest of the hybrid platforms, but this means that we need to detect some sng related features relying on the hybrid/ICE split. More on that here

From 2023-10-10 to 2024-01-17:

Dongle
Platform
Gain FP?

c3f88a5035764f65
TOYOTA PRIUS TSS2 2021
Gain

7525f320bb0420f0
TOYOTA RAV4 2023
Gain

9d09cc205c254c4b
TOYOTA RAV4 2022 (or 2023)
No (unseen RAV4 in EU region)

404d0b3326346d5a
TOYOTA RAV4 2023
Gain

061932dac503c0f7
TOYOTA RAV4 2023
No (2024 with new major version)

007f1416e7b53998
TOYOTA RAV4 2023
Gain

69e4f202ff8a7c3e
TOYOTA COROLLA TSS2 2019
Gain

ad087a7655bd6039
TOYOTA CAMRY 2021
Both fuzzy FP (Gain when removing all its FW)

d90d60569fa8bfe0
TOYOTA CAMRY 2021
Gain

9993ef6cfe3613bf
TOYOTA RAV4 2023
Gain

8d1efe1f449e4386
TOYOTA HIGHLANDER 2020
Gain (with hybrid combination)

bff212aa671150d5
TOYOTA COROLLA TSS2 2019
No

9bf4af979ddee563
LEXUS IS 2023
No (base vs F-Sport trim, EPS also shows a difference)

01762a5235a24145
LEXUS RC 2020
No - significantly new MY (2018, added here without FW or source, expected: https://github.com/commaai/openpilot/pull/25134)

Considering using just camera and eps, so far no mock routes mismatch:
for cat, _ecus in (
    ('abs', (Ecu.fwdCamera, Ecu.abs, Ecu.eps)),
    ('fwdRadar', (Ecu.fwdCamera, Ecu.fwdRadar, Ecu.eps)),
    ('neither', (Ecu.fwdCamera, Ecu.eps)),
  ):

I checked a random segment from each dongle for the last year + all mock routes, I also ignored any mock routes that didn't have a majority of Toyota FW responses -- a good heuristic for whether the car is a Toyota/Lexus or not:
Total checked dongles: 3871
Total checked platforms: 32

Here's all the dongles that didn't gain a fingerprint with this PR, they're all mostly unsupportable cars, so this is good!
View
Dongles stayed same (no gain) 17

no gain! c5a2f0d514baa01c|2023-04-08--14-34-34--12 mock vin car name: TOYOTA Sienna Hybrid 2021 5TDKRKEC2........
no gain! c35915933c1bc687|2023-03-04--12-23-23--2 mock vin car name: TOYOTA Sienna Hybrid 2022 5TDKRKEC7........
no gain! bfd59919af7a9183|2023-03-02--20-00-56--32 mock vin car name: TOYOTA Venza Hybrid 2023 JTEAAAAH8........
no gain! 45d332ef56466d87|2023-03-04--20-56-32--0 mock vin car name: TOYOTA RAV4 Prime Plug-in Hybrid 2021 JTMAB3FV0........
no gain! 524cd60e4f7afcdd|2023-04-22--12-50-08--11 mock vin car name: TOYOTA Sienna Hybrid 2023 5TDCSKFC2........
no gain! c7e296b914b21642|2023-02-26--19-40-20--0 mock vin car name: TOYOTA RAV4 Prime Plug-in Hybrid 2021 JTMAB3FV2........
no gain! c27e776f2a552b38|2023-12-27--14-48-58--0 mock vin car name: TOYOTA Prius Prime Plug-in Hybrid 2022 JTDKAMFP1........
no gain! 9d09cc205c254c4b|2024-01-20--15-39-13--0 mock vin car name: TOYOTA   JTDAGNAC5........
no gain! 1547f5d12a3942eb|2024-01-08--15-55-40--0 mock vin car name:    000000000........
no gain! f60772e6acef55c4|2023-12-12--15-33-10--0 mock vin car name: TOYOTA RAV4 Hybrid 2022 4T3RWRFV5........  # missing EPS? recent routes are good
no gain! 0b54d0594d924cd9|2023-12-23--14-58-53--0 mock vin car name:    000000000........  # unseen platform code in Japan
no gain! 787a897ec84996e7|2023-12-03--14-30-24--0 mock vin car name: TOYOTA Corolla Hybrid 2022 JTDEAMDE0........  # missing EPS? recent routes are good
no gain! a2c30de116fe186d|2023-06-24--21-29-58--12 mock vin car name: TOYOTA RAV4 Hybrid 2023 2T3RWRFV9........  # missing EPS? recent routes are good
no gain! 5f847404b2508ce0|2023-05-08--11-27-40--7 mock vin car name: TOYOTA Land Cruiser  JTEBR3FJ1........
no gain! 9bf4af979ddee563|2023-12-14--04-57-32--0 mock vin car name: LEXUS IS 2023 JTHAP1D26........  # new EPS version, we only have 1 in DB
no gain! 817df76359225baa|2023-12-28--20-19-48--0 mock vin car name: TOYOTA RAV4 Prime Plug-in Hybrid 2022 JTMEB3FV4........
no gain! 519cd5cb1bd7f6f5|2023-10-17--14-19-35--0 mock vin car name: TOYOTA RAV4 Prime Plug-in Hybrid 2023 JTMEB3FV6........


Error: Compute CTC targets failed!

Environment

Tesseract Version:tesseract 4.1.1
Commit Number:
Platform: Ubuntu 16.04 64 bit

Current Behavior:
Loaded file ./100_verygood_preprocessed/training/eng.lstm, unpacking...
Warning: LSTMTrainer deserialized an LSTMRecognizer!
Continuing from /home/petpooja/Downloads/100_verygood_preprocessed/training/eng.lstm
Appending a new network to an old one!!Warning: given outputs 111 not equal to unicharset of 105.
Num outputs,weights in Series:
Lfx256:256, 394240
Fc105:105, 26985
Total weights = 421225
Built network:[1,0,0,1[C5,5Ft16]Mp3,3Lfys64Lfx128Lrx128Lfx256Fc105] from request [Lfx256 O1c111]
Training parameters:
Debug interval = 0, weights = 0.1, learning rate = 0.001, momentum=0.5
null char=104
Loaded 1751/1751 lines (1-1751) of document /home/petpooja/Downloads/100_verygood_preprocessed/training/rough_1.lstmf
Loaded 1751/1751 lines (1-1751) of document /home/petpooja/Downloads/100_verygood_preprocessed/training/rough_1.lstmf
Compute CTC targets failed!
Compute CTC targets failed!
Compute CTC targets failed!
Blank transcription:
At iteration 100/100/104, Mean rms=5.606%, delta=39.451%, char train=118.761%, word train=100%, skip ratio=4%,  New worst char error = 118.761 wrote checkpoint.
Blank transcription:
Compute CTC targets failed!
Compute CTC targets failed!
Compute CTC targets failed!
Blank transcription:
At iteration 200/200/209, Mean rms=5.412%, delta=36.192%, char train=109.469%, word train=100%, skip ratio=4.5%,  New worst char error = 109.469 wrote checkpoint.
Blank transcription:
Blank transcription:
Compute CTC targets failed!
Compute CTC targets failed!
Compute CTC targets failed!
Compute CTC targets failed!
Compute CTC targets failed!
Blank transcription:
Blank transcription:
Compute CTC targets failed!
Blank transcription:
At iteration 300/300/320, Mean rms=5.305%, delta=33.814%, char train=106.337%, word train=100%, skip ratio=6.667%,  New worst char error = 106.337 wrote checkpoint.
Compute CTC targets failed!
Compute CTC targets failed!
Compute CTC targets failed!
Compute CTC targets failed!
Blank transcription:
Compute CTC targets failed!
Blank transcription:
At iteration 400/400/427, Mean rms=5.286%, delta=33.704%, char train=104.733%, word train=100%, skip ratio=6.75%,  New worst char error = 104.733 wrote checkpoint.
Compute CTC targets failed!
Blank transcription:
At iteration 499/500/529, Mean rms=5.287%, delta=33.733%, char train=103.889%, word train=100%, skip ratio=5.8%,  New worst char error = 103.889 wrote checkpoint.
Finished! Error rate = 100
Expected Behavior:
How can I remove such error?
Suggested Fix:

There exist already several identical issue reports which explain this. Typically those messages indicate bad training data, for example multi-line images instead of single-line images or vertical instead of horizontal text. The latest Tesseract reports the files which cause the problem. The training process will simply ignore that data, in your case 5.8 % of your data are skipped.

Thank you for your reply.
I also want to know, how did you get to know that I have 5.8% of such data?
On Thu, 18 Mar 2021 at 18:09, Stefan Weil @.***> wrote:

There exist already several identical issue reports which explain this.
Typically those messages indicate bad training data, for example multi-line
images instead of single-line images or vertical instead of horizontal
text. The latest Tesseract reports the files which cause the problem. The
training process will simply ignore that data, in your case 5.8 % of your
data are skipped.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/3339#issuecomment-801892072,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIDF22NSR7W6GH6PMJLIXCLTEHYARANCNFSM4ZMNYYBQ
.

That's only an estimate, see skip ratio in the log messages:
 At iteration 499/500/529, Mean rms=5.287%, delta=33.733%, char train=103.889%, word train=100%, skip ratio=5.8%, New worst char error = 103.889 wrote checkpoint.

Got it
Thanks a lot.
On Thu, 18 Mar 2021 at 20:08, Stefan Weil @.***> wrote:

That's only an estimate, see skip ratio in the log messages:
At iteration 499/500/529, Mean rms=5.287%, delta=33.733%, char train=103.889%, word train=100%, skip ratio=5.8%, New worst char error = 103.889 wrote checkpoint.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/3339#issuecomment-801981903,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIDF22PP3W4HRYWUQJCDUOTTEIF6FANCNFSM4ZMNYYBQ
.


Some color settings make some text invisible

Hi.
When the background color set to 12, 12, 12(the first color) and text color set to 59, 120, 255(the 10th color), text in string will be invisible. PS5 doesn't have this problem because it changes the line's backgroud color.
In PS6:

In PS5:

I have searched issues but English isn't my native language so it's hard for me to find whether there are dups. If there were, please close this one, thanks.
Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.1.0
PSEdition                      Core
GitCommitId                    6.1.0
OS                             Microsoft Windows 10.0.17134
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

There is a similar complaint here, so further discussion can take place in that issue.
For now, your best bet is probably to customize the color, see an example.


docs: Add nginx restart reference.

This adds reference for restarting nginx when
the certificates are replaced so that the server
works with the new certificates instead of the
old ones.
Fixes: #4849.

Testing Plan:
GIFs or Screenshots:

Merged, after tweaking this to use service nginx reload instead -- we don't need a full restart.  Thanks @bistaastha!


Add support for URLs without scheme/protocol

linkify 0.8.0 was just released with an exciting new feature:

New option url_must_have_scheme on LinkFinder that can be set to false to allow URLs without scheme/protocol such as example.com.

Changelog here.
This would allow us to check even more links. 😃
We should add support for that behind a feature flag:

[x] Add flag --no-scheme, which is off by default.
[x] If --no-scheme is enabled, create linkify with the new feature:let mut link_finder = LinkFinder::new();
link_finder.url_must_have_scheme(!no_scheme);

[x] Add tests

We could eventually even make this the default, although we have to do a lot of thorough testing before that.
Thanks to @robinst and @timvisee for working on this on the linkify side.

I made some attempts to integrate this, but I hit too many false-positives unfortunately. Closing.


How to use ginzame via Python

Hello!
I want to use ginza/ginzame for Japanese corpus's preprocessing like MeCab.
But I have a question.
I think you only showed the example of using ginza. I'd not found the example of using ginzame.
Can you add the example of using ginzame?

Hi @MokkeMeguru ,
Thank you for asking the mecab mode.
I'd like to add an introduction to run only the morphological analysis part and the parallelizing method used in ginzame command.
Please read the souce code of ginza.command_line right now.
https://github.com/megagonlabs/ginza/blob/develop/ginza/command_line.py

OK, I'll read the code.
Can I keep opening the issue because I'd not already write the code?
If I have any question, I'll add the comment in this issue.

Thanks!
I wrote the code to use ginzame !
https://github.com/MokkeMeguru/meguru_tokenizer/blob/master/japanese/tokenize_sudachi.py


HDDS-9676. SORT_DATANODE audit log should include request details

What changes were proposed in this pull request?
SCM's audit log entry for sort datanodes request does not have information about the request (client, node list).  This change adds them.
https://issues.apache.org/jira/browse/HDDS-9676
How was this patch tested?
Checked audit log entry, example:
2023-11-13 08:41:13,856 | INFO  | SCMAudit | user=hadoop | ip=<IP_ADDRESS> | op=SORT_DATANODE {client=<IP_ADDRESS>, nodes=[6a9a42ad-9ecd-4e96-bf45-5255f6be66bf, a12806c3-6e7f-479a-be63-20cb3ecb0eb4, cfac92e5-cdce-471d-a995-e6f4dc22ea6f]} | ret=SUCCESS |

CI:
https://github.com/adoroszlai/ozone/actions/runs/6847145541

Thanks @sodonnel for the review.


Extra Bytes when connecting to loop server from client

Minecraft Version: 1.20.4
Server Version: 1.20.4
Waterfall (Bungee) Version: 1.20.4
Hello! I am getting an error wen switching over to the loop server from my client

Additionally I tried to connect to the test mc.loohpjames.com server with much the same error

I've had the same issue

Update


Add .editorconfig

Hey!
Awesome app, judging by the screenshots, I'm looking forward to the version for Android, looks cool! :champagne:

EditorConfig is a standardized opt-in way to help collaborators auto-set their editor on a per-project basis for various formatting options, e.g. spacing and tabs. Some editors (e.g. WebStorm) honor it out of the box; others (e.g. VSC) require installing a small extension. EditorConfig files also affect how code renders in certain engines, including GitHub's web interface.

Niceeee, thank you for this :) Please don't forget to add yourself as a contributor to the README!
Yep I can't wait to have that rolled out either #2, hoping within the next few weeks will have it launched!

Please don't forget to add yourself as a contributor to the README!
Oh, can you do it, because then you will need a new pull request? I do not want to do it because of this.


[Question]  company-tabnine-always-trigger

I'm curious what the rationale behind adding this behavior was.  It makes things like using pdb(lots of one-letter commands) very difficult, because I have to cancel the completion for everything.

I have the same question, is there any way to trigger tabnine only in prog-mode?

The company-tabnine-always-trigger option is to make TabNine trigger even when company doesn't (by default), such as when pressing space. TabNine is able to complete multiple words (even entire line), and meaning candidates can pop-up even when space is pressed.
To have mode-local behavior, such as changing this option in a certain mode, or disable completion entirely, just use a hook:
(add-hook 'prog-mode-hook (lambda () (setq-local company-tabnine-always-trigger nil)))


Error in resuduals when labels given as int instead of float64

When trying to train a simple neural network with labels fed as integers I encountered the following error
TypeError: Exception encountered when calling layer "tf.math.subtract" (type TFOpLambda). Input 'y' of 'Sub' Op has type float32 that does not match type int64 of argument 'x'.
Originating in the following method:
    def residuals(self, y_true, y_pred):         return y_true - y_pred
I tried casting in the method but It raised a further error. It started working once I simply converted the labels to floats before training.
Maybe we could add a check and a warning in order to avoid runtime exceptions.

Hi Andrea,
thanks for the tip, I'll take a look to it. I have to check what keras does in this situation, probably it just casts the input to float32/float64 (based on tf.keras.backend.floatx() setting) without giving any assert.


fix: handle non UTF-8 data when logging requests

When structlog is not installed, the body will not get parsed and shown as a byte sequence. This byte sequence is then serialized into a string with the assumption that it is valid UTF-8. This is not always the case, eg. when uploading a file.
Therefore, use backslashreplace to handle invalid UTF-8 sequences.

Pull Request Checklist

[X] New code has 100% test coverage
[ ] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[ ] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR
[X] Pre-Commit Checks were ran and passed
[ ] Tests were ran and passed

I don't have docker compose installed, so those tests failed. I've check that my changes do not cause more tests to fail then before.
Description

Uploading binary files no longer causes an exception when request logging is active withoout structlog installed

Close Issue(s)

Fixes #2529

@all-contributors please add @brakhane for code, bug.


support Google Trust certs

Hi.
Please add option for issuing free TLS certificates by Google Trust Services LLC.
For more information: Official Documentation of Google Certificate Manager

Looks like it should already work: https://cloud.google.com/certificate-manager/docs/public-ca-tutorial


Add syntax for global variables

I would like to write a guppy program such as:
@guppy.global(float)
rot = 1.0

@guppy
main() -> float:
  return rot

which compiles to a hugr containing a global Const node representing rot, which would be some CustomConst including a symbol name and a type. This Const would be further lowered to an extern symbol during codegen.
The syntax used above is purely for explanation and I have no attachment to it.

does this do the job? (it works now I believe)

rot = 1.0

@guppy
main() -> float:
  return py(rot)

does this do the job? (it works now I believe)

No it doesn't, although I accept this is a problem with my example. Perhaps It would be clearer to write rot = guppy.GlobalSymbol("rot"). The point is that I need this to compile to an external symbol.  Your example will paste "1.0" wherever py(rot) is written.

yes 👍
for compilation target, does this do the job: https://github.com/CQCL/hugr/issues/233

I think it might be easier to share intent if we replace "global" with "extern"/
"external", e.g., ExternSymbol.


Jumpscare on Death Script

Describe your problem here.
I was making a halloween mod, and I wanted to add a jumpscare when I died like in the Bunzo Bunny mod and the Vs. Blue V1 mod. I do not have any of these mods and I do not have space to download these mods.
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, I added multiple characters and a new song.

function onEndSong()

Look here https://github.com/ShadowMario/FNF-PsychEngine/issues/1795?


[CMake] Avoid add_custom_command output being used from multiple target

without a target. Because Xcode generator  doesn't like it. Use add_custom_command_target instead.

@swift-ci Please smoke test


Remove legitimate website

urlr.me is our solution for GDPR-compliant link shortening.
We have a very strict policy to detect and remove malicious links.
Tell me if you need more details.
Thanks in advance.
Best regards,

Good afternoon, we approve the de-listing request.


Directory Backend improvements

Implement changes stipulated in issue.

Some resources are defined in the config document (which drastically add up as you add more api roots, collections, server discovery, etc)

Although the objects are "cached" many other resources are not like the status and the aforementioned resources. The cache mechanism itself could be improved

The directory structure could be improved as handling them via bundles is impractical

Implement an eager saving strategy, optional saving status resources.

Removed bundle from test suite in favor of the new structure

closes #71

Codecov Report

Merging #76 into master will increase coverage by 0.04%.
The diff coverage is 84.95%.

@@            Coverage Diff             @@
##           master      #76      +/-   ##
==========================================
+ Coverage   88.39%   88.44%   +0.04%
==========================================
  Files          33       33
  Lines        2456     2492      +36
==========================================
+ Hits         2171     2204      +33
- Misses        285      288       +3

Impacted Files
Coverage Δ

medallion/test/config.py
100% <ø> (ø)
:arrow_up:

medallion/test/test_directory_backend.py
100% <100%> (ø)
:arrow_up:

medallion/backends/taxii/memory_backend.py
95.3% <100%> (+0.03%)
:arrow_up:

medallion/views/objects.py
97.5% <100%> (ø)
:arrow_up:

medallion/test/__init__.py
100% <100%> (ø)
:arrow_up:

medallion/backends/taxii/directory_backend.py
84.87% <83.63%> (+1.22%)
:arrow_up:

medallion/utils/common.py
88.33% <88.88%> (-0.96%)
:arrow_down:

Continue to review full report at Codecov.

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


Docker files and cleanup

Remove Spystore from deps
Do not commit vendor
Update makefile to use deps

Coverage remained the same at 3.157% when pulling a7c2e4bd1e76b3721ef028c5422e57b5d8bc6df0 on dockerize into 74102c8887380526ab8d80a1b3d7d8330bd445fa on develop.


fix(code): fix click clipboard button

What has been done

Increased the clickable area of the copy button

Issue:
459

Hi, thanks for the pull request!
Unfortunately, this issue has already been resolved in this pull request along with improvements to the focus behavior on this element. The issue is no longer relevant and I've closed it.
Anyway, thanks for participating and for your interest in our project.


Lato download returns 403

curl: (22) The requested URL returned error: 403 Forbidden
If you hit the URL via the browser it does work, but it does a bit of redirection:

From my machine, font-lato downloads normally. Can you still reproduce the issue? If so, do you have a custom .curlrc?

Oddly enough, it does work today. I know it had been broken for quite some time on multiple computers on multiple networks (I only tried again and reported yesterday). I do not have a custom .curlrc, but a good thought for sure. Since this cannot be reproduced, I will close. Thanks for taking a look!


INDIRECT is missing in GPUBufferUsage

INDIRECT is missing in GPUBufferUsage. Can we add it as it is part of the spec? See https://gpuweb.github.io/gpuweb/#dom-gpubufferusage-indirect
@kainino0x

oops, clearly I did a bad job of one of my types updates - missed at least 2 things :)

Done in 0.0.11

I thought you would programmatically generate those with some IDL to DTS library. Is this not the case?

I did autogenerate it once, but the script wasn't robust enough to use it every time. So I generated it once, fixed it up manually, then have been making the incremental changes by hand. (We don't make that many changes to the IDL so it's easy except that I miss things.)

IIRC this is the tool I used https://github.com/Microsoft/TSJS-lib-generator


Any intents to move to Datatables?

Hello. Is there any reason ng-admin is not using Datatables as table plugin for list views? Do you have any intents to move to datatables? The first thing I miss from Datatables is multicolumn sorting. There is much more: reordering, column freezing, inline editing etc.

Check out https://github.com/marmelab/ng-admin/issues/1056 this may give you an idea.
But you will need to rewire all the features you are talking about to bind them with REST api calls

There are about a gazillion grid plugins for angular. We don't plan to test them all. So no, thanks.


Support for lodash 4

contains has been replaced with includes in lodash ^4

Thanks for the PR! You need to update lodash dependency in package.json as well.

@mohsen1 Just didn't want to make that call for you.  Also happy to drop support :).

If we can get rid of Lodash dependency it would be amazing! Most of those functions are now in JavaScript!

@mohsen1 Think dropping lodash might be a bit much.  At first pass of removal, I have had to reimplement half of these methods.

ok that's fine. If tests pass I'll merge and publish this

@mohsen1 Actually might need help, the fail is in npm (if installed with yarn) all tests pass.  But I can't figure out what is going wrong when I install with npm.   It seems as such that mocha is not getting the correct version of lodash.

@mohsen1 any chance we can get this merged?


bug: cards not formatting correctly in Teams when using TeamsQueueHandler

Using logging dict configuration in django application
This configuration works:
'formatters': {
        'teamscard': {
            '()': Office365CardFormatter,
            'facts': ["name", "levelname", "lineno"],
        },
    },
'handlers': {
        'msteams': {
            'level': 'INFO',
            'class': 'teams_logger.TeamsHandler',
            'url': os.environ.get('TEAMS_LOGGING_URL', default=""),
            'formatter': 'teamscard',
        },
    },

the cards are displayed as normal in Teams:

However, I need a non-blocking implementation, so I changed to TeamsQueueHandler
'formatters': {
        'teamscard': {
            '()': Office365CardFormatter,
            'facts': ["name", "levelname", "lineno"],
        },
    },
'handlers': {
        'msteams': {
            'level': 'INFO',
            'class': 'teams_logger.TeamsQueueHandler',
            'url': os.environ.get('TEAMS_LOGGING_URL', default=""),
            'formatter': 'teamscard',
        },
    },

But this breaks the card formatting in Teams:

Is there a workaround that I have missed?

Excuse my late answer. I'll try to reproduce the issue and propose a fix.

The issue seems to be that the self.formatter which is set on the TeamsQueueHandler, is not transferred to the teams_handler that is given to the QueueListener.
I've tried addressing that with the following changes
class TeamsQueueHandler(QueueHandler):
    def __init__(self, url, level=NOTSET):
        self._log_queue = queue.Queue(-1)
        super().__init__(self._log_queue)

        self._teams_handler = TeamsHandler(url, level).     # changed to self._teams_handler
        teams_log_listener = QueueListener(self._log_queue, self._teams_handler). # changed
        teams_log_listener.start()

    def setFormatter(self, fmt):          # inserted extra method
        self._teams_handler.setFormatter(fmt)
        super().setFormatter(fmt)

But that didn't work out completely as expected. The cards are now shown with fields as expected, but the raw json content<EMAIL_ADDRESS>is inserted as subtitel in the card (instead of the log message). Couldn't really yet figure out why in the time I decided to spent on this.

I just published a release (0.4.1) wuth your suggested fixes


my first issues

Issue/Feature Description:
Why this issue to fixed / feature is needed(give scenarios or use cases):
How to reproduce, in case of a bug:
Other Notes /  Environment Information: (Please give the env information, log link or any useful information for this issue)

hi how are you

closing


Majority of directories are empty

Hi there.
I came here from a devnet sandbox lab. This git repo is referenced in the sandbox description for csr1000v programmability. Quite disappointing there is almost no usable content here. I was looking forward to try some code but majority of links are referring empty dirs and meaningless readme files. Can you guys populate some useful content?
Thanks!

Responding to this almost a year later, but I agree. This repo seems to be dead, but hopefully, they will accept pull requests because I'd gladly contribute some examples.


⚠ SceneTime has degraded performance

In ecb1beb, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1850 ms

Resolved: SceneTime performance has improved in ec423df after 6 minutes.


Fixes SQL wildcard escaping in LIKE queries

Potential fix for #10849.
Approach: The escaping of SQL wildcards (\_, \%) is handled as a special case. The escaping of \ is handled separately from the escaping of other meta characters.
Test plan: Existing unit tests pass. Added unit tests to validate the specific case that this fix solves.

@Aravind-Suresh Thanks for raising the PR. I will review this once the tests pass

Codecov Report

Merging #10897 (e47e637) into master (86b3b3e) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master   #10897   +/-   ##
=======================================
  Coverage    0.11%    0.11%
=======================================
  Files        2186     2186
  Lines      117493   117500    +7
  Branches    17762    17767    +5
=======================================
  Hits          137      137
- Misses     117336   117343    +7
  Partials       20       20

Flag
Coverage Δ

integration1temurin11
?

integration1temurin17
?

integration1temurin20
?

integration2temurin11
0.00% <0.00%> (ø)

integration2temurin17
?

integration2temurin20
?

unittests1temurin11
?

unittests1temurin17
?

unittests1temurin20
0.00% <0.00%> (ø)

unittests2temurin11
0.11% <0.00%> (ø)

unittests2temurin17
?

unittests2temurin20
0.11% <0.00%> (ø)

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

Impacted Files
Coverage Δ

...inot/common/utils/RegexpPatternConverterUtils.java
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[FreeBSD 14] Build breaks on arm64: ld: error: undefined symbol: brk

ld: error: undefined symbol: brk

referenced by mmap_hook.cc
              src/low_level_alloc_unittest-mmap_hook.o:(sbrk)
did you mean: sbrk
defined in: src/low_level_alloc_unittest-mmap_hook.o

brk isn't supposed to be used in general.
Version: 2.15
FreeBSD 14.0

Thanks for bug report. So looking closer, looks like our mmap hooks simply assumes that FreeBSD can do sbrk and looks like perhaps 14.0 doesn't anymore. I.e. without even looking at config.h where we have indication of sbrk availability. I welcome patch to fix this.
As for more general matter of not using sbrk. So, yes, in principle we should consider. But in practical terms, just doing our current version of mmap allocator will actually break large heap fragmentation unittest. Yes, this test's specific case is quite subtle, but it is one way to show that sbrk's built-in feature of allocating memory sequentially does give us substantial benefit. There is also potential for another benefit (and potential security downside) which is that brk area being immediately after bss makes certain TLB-miss effects cheaper. I.e. heap sitting closer (likely same pmd) to .bss/.data has possibly measurable performance benefit by having shorter page table walks.
So, yes, I will accept patches and benchmarks towards doing mmap-only allocation, but we cannot simply amputate sbrk just yet.

sbrk and brk have intentionally never been in a release of FreeBSD on arm64 since first released in 11.0 in 2016.


Feature: Show average cost of positions under Portfolio

It would be nice to see the avg. versus the current price to quickly evaluate if your position is positive or negative when considering a sell.

The Return column pretty much shows that. It's the difference between the average buy price and the current price, multiplied by the number of shares. If it's positive, that means your average buy price was lower than the current price. If its negative, then it's the opposite.
Are you looking for the difference per share?

I am looking for something like Avg./Share, next to Price/Share (to the left). I think having this value, in addition to Return would be beneficial. In some of my positions, I look to "average down" so having the average cost per share would be very helpful in this case.
Does that make sense?

I understand, but basically the same data is already shown as return. You'd average down if your return is negative and you buy shares, since you're average price per share is above the current price. It just doesnt show it like that since it's overall return (I found that more useful when developing it). I can look to add a tooltip or column though if you need to see the price per share, and not just overall return (which is (current price - avg. buy price) * number of shares owned)

I would like to see the price per share, but if it's not something that makes sense then don't worry about it. I can always consult with my iOS app.

With the latest code push I added a average buy price column