the nextcord guide:tm:

Summary
title?
What is the feature request for?
The documentation
The Problem
so pycord, djs and dpy had some guides for people that is new to the lib
The Ideal Solution
create a nc guide for people that is new to the lib. imo it should target some type of intermediate/advanced python devs.
The Current Solution
No response
Additional Context
im happy to contribute sometimes if needed.

it should target some type of intermediate/advanced python devs.
Why not beginners, what's your thought process behind this?

I feel that docs themselves are pretty good, maybe another word or two at the starting- There isn't much need for a full guide imo.

well as stated in the !!whypython tags, nc is far complicated to python noobs.

That is not for nextcord specefically, it goes the same most dAPI python wrapper libs.

this would be cool in the future, however focusing on improving the current docs should be a higher priority (adding examples, consistency etc)

i can work on it but i need more of an explanation to do it. mask duck plz

havent you viewed guides from dpy/djs/django before? i want sth like that

havent you viewed guides from dpy/djs/django before? i want sth like that

ys i havent but i will refer now

is it out yet

is it out yet

Uh no, 0 work has been done on this Nextcord Guide

is it out yet

The guide itself has little development as the Docs, FAQ and the discord server help combined are more than enough to actually need another guide. I am still unsure what this guide would consist of.

anw its planned

is it out yet

The guide itself has little development as the Docs, FAQ and the discord server help combined are more than enough to actually need another guide. I am still unsure what this guide would consist of.

u know basics of how to get used to nextcord trust me it is very needed for all the new commers to get used to it

I think this issue should be closed, as it is already resolved and there is presence of it in this repo with clear examples that people with basic understanding of python can understand.


Blog sorting is now broken

Since the 2020.10.3 update the blog posts are no longer sorted by date. (This is because date was replaced with date_published)

resolved in version 2020.10.5 - a43d06429c906c4014ed5f119cb25a909cd420ca


Speed up mrr_diagonal() by using MultiPoint instead of LineString

Constructing LineStrings is more expensive than constructing a
MultiPoint, and from the minimum rotated rectangle perspective it should
make no difference if it is a set of lines or a set of points.

Codecov Report

Merging #152 (13244e5) into master (42a9203) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #152   +/-   ##
=======================================
  Coverage   94.65%   94.65%
=======================================
  Files          23       23
  Lines        2319     2319
=======================================
  Hits         2195     2195
  Misses        124      124

Impacted Files
Coverage Δ

movingpandas/geometry_utils.py
74.64% <100.00%> (ø)

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 42a9203...13244e5. Read the comment docs.

Thank you for this contribution, Gustavo.


feat: allow apt-key to be used with apt repositories

Codecov Report

Merging #138 (381bbf8) into main (52ab3f3) will increase coverage by 2.33%.
The diff coverage is 82.05%.

@@            Coverage Diff             @@
##             main     #138      +/-   ##
==========================================
+ Coverage   40.05%   42.38%   +2.33%
==========================================
  Files          45       45
  Lines        1583     1621      +38
==========================================
+ Hits          634      687      +53
+ Misses        949      934      -15

Impacted Files
Coverage Δ

src/actions/package/mod.rs
0.00% <0.00%> (ø)

src/actions/package/providers/aptitude.rs
54.08% <91.42%> (+54.08%)
:arrow_up:

Continue to review full report at Codecov.

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


:recycle: chore: MIgrate config to NodeNext

Description
Migrate @evmts/config to node next for compatibility reasons
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #562

PR #563   👈

PR #564

This comment was auto-generated by Graphite.

#553

closes https://github.com/evmts/evmts-monorepo/issues/516


:brain: Logic: :card_index_dividers: source_files/1 predicate

Purpose
This PR completes #308 by implementing the source_files/1 predicate in the bootstrap - using bagof:
source_files(Files) :- bagof(File, source_file(File), Files).

Example
(see testcases for a better understanding)
?- consult(file2), consult(file1), source_files(File).
File = [file1,file2).

:tada: This PR is included in version 5.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add cohort assignment pixel for NTP Search Box Experiment

Task/Issue URL: https://app.asana.com/0/1201621853593513/1208742047745355/f
Description:
This change adds a pixel that's fired when a user is enrolled into the NTP search box experiment.
Steps to test this PR:

clear app data
run the app from Xcode
check console logs and verify that m_mac_initial-search-day-1 has been sent with count=0
run the app again
check console logs and verify that the pixel isn't sent.
return nil in DefaultNewTabPageSearchBoxExperimentCohortDecider.cohort
clear app data
run the app again
check console logs and verify that the pixel isn't sent.

Definition of Done:

[ ] Does this PR satisfy our Definition of Done?

Internal references:
Pull Request Review Checklist
Software Engineering Expectations
Technical Design Template
Pull Request Documentation

Thanks @SabrinaTardio! I've made a change to only assign the cohort once onboarding is finished and to attempt cohort assignment on every viewWillAppear (instead of once upon HomePageVC initialization)


Issue #201 - Spark Packages

PR to support Spark Packages as custom dependencies.
Two features here:

add spark-packages repository to resolver list
support maven coordinates in "groupId:artifactId:version" format

Note that I haven't tried the Scala 2.11 version.  I think I am missing the analog to the ReplCalculator of 2.10, but don't see where to add the spark-package repo.
The end result is convenient use of packages.

Locate a package on spark-packages.org  (example).
Copy the coordinates (e.g. EronWright:mypackage:0.0.6)
Paste the coordinates into the custom deps of the notebook:

{
  "customDeps": [
    "EronWright:mypackage:0.0.6"
  ], ...
}

Observe the resolver's log output; the package is drawn from spark-packages repo:

	EronWright:mypackage
		- 0.0.6
			status: release
			publicationDate: Fri Jun 05 19:15:02 PDT 2015
			resolver: spark-packages
			artifactResolver: spark-packages
			evicted: false
			isDefault: false
			configurations: default, compile, runtime, default(compile), master
			licenses: (Apache-2.0,Some(http://opensource.org/licenses/Apache-2.0))
			callers: org.scala-lang:scala:2.10.4

Thanks for this PR, the use of regex was in my radar so, again, thanks!
Regarding the : style, as commented in the code, I'm not sure if it wouldn't just be better to stick with only one patter (the sbt like one) that will allow us to get closer to the sbt functionality  --  and avoid duplication of code :-S.
For now, the way we use SBT prevents us to use it in 2.11. It'd require some work to start an sbt-server using the scala 2.10 version and receiving deps resolution request... it's something I started discussing on the SBT list, but I still find the solution a bit, let's say, sad.
2.11 changes
To add the spark-packages support in 2.11, since it uses aether rather than SBT, it's different that 2.10.
Thus, the changes have to be made in Deps_2.11 where you could mimic central for instance like this
  @transient val sparkPackages = new RemoteRepository(
    "spark-packages",
    "default",
    "http://dl.bintray.com/spark-packages/maven"
  )

Then just add it to the default list in the ReplCalculator
WDYT?

I will fix the 2.11 stuff as you describe.  How exactly do I activate 2.11?
You are correct that the coordinate syntax is independent of the repository used, and I tested various combinations.   But supporting the same syntax as is supported by spark-submit and spark-shell is very convenient IMO (see example).   This syntax is also understood by Gradle (docs).

cool man! thanks
Regarding the syntax you have a very good point, I'm just afraid to introduce too many ways to do the same stuffs, after will come the leiningen boyz, followed by the grunt ones ^^.
Without kidding now, I'm wondering why they choose this encoding while they will use SBT in the code... it's weird and it might be a shell thing (like '%' doesn't pass well).
The thing I'll need to introduce too is the capacity to refer to the current scala version using double %, which won't cope anymore with the : version I guess.
So, since it doesn't really hurt to keep it (I mean I don't like removing working stuffs), but I would still refer the % fashion as the preferred way.
doesn't sounds like a good compromise for you?

Oh sorry, forgot to tell.
Running against 2.11 is done simply by activating the -Dscala.version=2.11.2 prop

Andy that seems like a good compromise.
BTW, the ':' format is otherwise known as the Maven coordinate canonical form (official doc).   Regarding the Scala version, it seems the typical solution is to embed "_2.10" or "_2.11" to the artifactId.

@andypetrella updated the PR as we discussed.
There is one more change I'd like to make.  I'd like to add the local m2 repository to the default set, because spark-submit/spark-shell uses the local m2 repo by default.   WDYT?

:+1: for the local maven repo per default!
thanks for the refs, I didn't knew maven had this kind of spec (but it's been a while I am not really using maven, that might be the reason :-D)

I will add the local Maven repo by end of day today, then hopefully this PR can be merged.

@andypetrella I think this is ready.  README has been updated, and a bit of testing done on Scala 2.10 and 2.11.
To launch the notebook against Spark 1.4 and Scala 2.11, use this:
sbt -D"spark.version"="1.4.0" -D"hadoop.version"="2.6.0" -Dscala.version=2.11.6 run

:yum: thanks @EronWright !


Docker version would be nice

This looks aswome! Is there any chance there will be a docker image of this on the near future?

No plans for it at the moment, since I've never worked with docker images. I have some time next week where I could look into this. Any more information/help on this would be appreciated!


Fix csprint to handle hidden field

Codecov Report

Merging #4 (f405f27) into main (db006e4) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #4   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           20        20
  Lines          905       906    +1
=========================================
+ Hits           905       906    +1

Impacted Files
Coverage Δ

util.go
100.00% <100.00%> (ø)

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 db006e4...f405f27. Read the comment docs.


[DEV] Copying instances is crashing.

Describe the crash
Trying to clone instance is crashing with the latest dev version commit.
To Reproduce
Go to Project Manager, edit any project and try to clone vanilla instance.
Crashlog
Application has crashed: C++ exception
[string "core/lib/utils/coretable.lua"]:175: bad argument #1 to 'pairs' (table expected, got nil)
SCRIPT STACK
contains() core/lib/utils/coretable.lua:175
extra_package() @mods/BeardLib-Editor-dev/Classes/Project/ProjectLevelEditor.lua:168
clone_level() @mods/BeardLib-Editor-dev/Classes/Project/ProjectLevelEditor.lua:193
clbk() @mods/BeardLib-Editor-dev/Classes/Project/ProjectInstanceEditor.lua:62
run_callback() @mods/PAYDAY-2-BeardLib-master/Classes/UI/Dialogs/InputDialog.lua:53
final() @mods/PAYDAY-2-BeardLib-master/Classes/UI/Dialogs/MenuDialog.lua:182
RunCallback() @mods/PAYDAY-2-BeardLib-master/Classes/UI/MenuUI/Item.lua:1224
MousePressed() @mods/PAYDAY-2-BeardLib-master/Classes/UI/MenuUI/Item.lua:1350
MousePressed() @mods/PAYDAY-2-BeardLib-master/Classes/UI/MenuUI/Item.lua:1376
mouse_press() @mods/PAYDAY-2-BeardLib-master/Classes/UI/MenuUI/MenuUI.lua:484
lib/managers/mousepointermanager.lua:345

Make sure also that BeardLib is updated as I had to fix something there too


CHANGELOG: remove extra bugfix section

Description of the change:
Remove extra bugfix section from the CHANGELOG.
Motivation for the change:
Fixing this from #2015

/lgtm


Font issue when using one of the constructors

I have a scenario where if I use the Paragraph constructor that specifies the size and color (as seen in the code snippet below)

I get ugly text as seen here:

If I uncomment the UpdateStyle line just after the paragraph initializes, it becomes a white font but looks attractive again.

Hi @torial,
Not sure I understand, why do you do the UpdateStyle() call? What are you trying to achieve?
Thanks,

Hi @torial ,
What do you mean ugly? How did you expect it to look?

Thanks,

The text in black in the image above is very ugly, and I was expectingly the changing of color, not to make it blotchy and pixelated when I set the color to black.
The only reason I was playing around w/ the UpdateStyle(Default) was that I saw that it was not in the constructor I was using.
If you want, I can provide another screenshot with the unpixelated/smooth/non-blotchy white next to the pixelated/granulated/blotchy black.

@torial ah yeah I wasn't sure that's what you meant, its just the shadow / outline, which is black.
If you want to remove the blotch just disable the outline, or change its color :)
Please try that and let me know if that was indeed what you meant.
Thanks!

I set the outline width to 0, and the problem went away!  Thank you, it looks much better!


Create pull request (patch/content/my-info to feature/body)

Create pull request (merge patch/content/my-info to feature/body).

Created


Roll Flutter Engine from 1947b95c5060 to fa87a42fe941 (8 revisions)

https://github.com/flutter/engine/compare/1947b95c5060...fa87a42fe941
2023-03-29<EMAIL_ADDRESS>Roll Skia from 145d93ee3f4f to 001ba6e28f99 (2 revisions) (flutter/engine#40754)
2023-03-29<EMAIL_ADDRESS>[Impeller] Enable playgrounds using a runtime instead of a build time flag. (flutter/engine#40729)
2023-03-29<EMAIL_ADDRESS>[Impeller] Start a more generic stroke tessellator for path (flutter/engine#40690)
2023-03-29<EMAIL_ADDRESS>[Impeller] Use NSAutoReleasePool for Metal playgrounds. (flutter/engine#40748)
2023-03-29<EMAIL_ADDRESS>Roll Skia from f415e93eafc8 to 145d93ee3f4f (1 revision) (flutter/engine#40751)
2023-03-29<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from JH1CUJ3kBRCcQn2AI... to whJeWVcM-8gVZRdVR... (flutter/engine#40750)
2023-03-29<EMAIL_ADDRESS>[web] remove obsolete object caches; simplify native object management (flutter/engine#40617)
2023-03-29<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from n85YWHBBE4HYwce_E... to A7rAmHDuuQ89yV9Fw... (flutter/engine#40749)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from JH1CUJ3kBRCc to whJeWVcM-8gV
fuchsia/sdk/core/mac-amd64 from n85YWHBBE4HY to A7rAmHDuuQ89
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Add an issue template

@haypo Adding an issue template will help with general questions being redirected to the mailing list.

I never try a template before. Let's try it ;-)

Thanks @willingc ;-)


Update dependencies to include new mkdocs-ansible branding  dependencies

@ssbarnea I agree, but unfortunately, mkdocs-ansible doesn't work with Python 3.9 anymore. Hopefully, this can be rebased with fewer changes once https://github.com/ansible/ansible-navigator/pull/1670 is merged.


User filesystem error

Hi!
I'm setting this up on an HPC, and though initializing at /tmp/hermes-store worked, in my home directory I'm getting the following error:
error: unable to acquire lock on file '/users/home/rog32/.hermes-store/var/hermes/lock/gc.lock' - Bad file descriptor
  in flock/acquire
  in acquire-gc-lock [src/pkgstore.janet] on line 200, column 3
  in gc [src/pkgstore.janet] (tailcall) on line 231, column 18
  in <anonymous> [src/hermes-pkgstore-main.janet] on line 289, column 16
  in main [src/hermes-pkgstore-main.janet] on line 285, column 3

Since it is on an HPC, the underlying filesystem is an NFS one, and I do not have root access.

Seems like a similar issue to https://github.com/ansible/awx/issues/3926. Will investigate.

This is still an issue; with the latest commit I get:
$ hermes build --output ./seed-env Git/Github/hpkgs/seed.hpkg
error: unable to acquire lock on file '/users/home/rog32/hermes-store/var/hermes/lock/build-e8f91f129240289f9874c14156bedaf324289c75.lock' - Bad file descriptor
  in flock/acquire
  in acquire-build-lock [src/pkgstore.janet] on line 204, column 3
  in build-pkg [src/pkgstore.janet] on line 448, column 35
  in build-pkg [src/pkgstore.janet] on line 445, column 36
  in <anonymous> [src/pkgstore.janet] on line 629, column 13
  in <anonymous> [src/pkgstore.janet] on line 433, column 3
  in <anonymous> [src/pkgstore.janet] on line 432, column 3
  in build [src/pkgstore.janet] on line 431, column 3
  in build [src/hermes-pkgstore-main.janet] on line 171, column 3
  in <anonymous> [src/hermes-pkgstore-main.janet] on line 288, column 19
  in main [src/hermes-pkgstore-main.janet] on line 285, column 3


Add new Jenkins deployment workflow

Description
This PR adds new Jenkins functionality to simplify indicator deploys for the new repo development workflow.
It will work like this:

A merge to main:

Creates a venv for each indicator, handles package installation and setup,
and then creates a package (at the moment a tar.gz).
Deploys each indicator to the staging environment.

A merge to prod:

Deploys each indicator to the production environment.

Changelog
Itemize code/test/documentation changes and files added/removed.

Add new Jenkinsfile
Add new supporting shell scripts

@chinandrew @krivard We should convene to make sure that we have all the indicators in main before we merge this. I'll need to make a couple of changes as well as I have a test directory configured in a few places as a fail safe.

@chinandrew @krivard We should convene to make sure that we have all the indicators in main before we merge this. I'll need to make a couple of changes as well as I have a test directory configured in a few places as a fail safe.

Which indicators are outstanding? DV, quidel [covidtest], fb-survey (in R), and maybe one other?

@chinandrew I think initially we might only need to make sure that we account for what is running in production, so that would be:
changehc
google_health
jhu
quidel_covidtest
safegraph
usafacts

Nothing else is scheduled in Automation yet so wouldn't be much of a problem if initially we unpacked the code into the runtime dir.
For the initial merge, I think something like this makes sense:

[ ] Update test directories
[ ] Publish PR
[ ] Take a backup of the Jenkins artifact dir
[ ] Take a backup of the staging runtime dir
[ ] Merge

We can give it some time to settle in, and then get it over to prod (I want to take a backup of the prod runtime dir before we do that).

Ok, looks like this now:

[X] Update test directories
[X] Publish PR
[X] Take a backup of the Jenkins artifact dir
[X] Take a backup of the staging runtime dir
[ ] Merge

@krivard I can't accept those changes because I've already made them as further commits outside of the PR convo and they are now 'Outdated'. I think I broke the PR workflow a little bit.
At any rate, I think we can merge this.

Issue is filed.
Directory backups are taken.
Production directories are configured.

When we merge to main this will build+package and then deploy to staging. This is mostly inconsequential at the moment, but will be good to see in action.


Exception on instance start

Describe the bug
Device Watcher does not start, due to an exception. See log. Fully deterministic.
To Reproduce
Directly on instance start.
Screenshots & Logfiles

host.mediapc
2022-11-06 13:08:32.260
error
instance system.adapter.device-watcher.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

device-watcher.0
2022-11-06 13:08:31.696
error
Cannot read properties of undefined (reading 'captureException')

device-watcher.0
2022-11-06 13:08:31.696
error
TypeError:  Cannot read properties of undefined (reading 'captureException')    at  DeviceWatcher.errorReporting  (/opt/iobroker/node_modules/iobroker.device-watcher/main.js:1823:38)     at DeviceWatcher.onReady  (/opt/iobroker/node_modules/iobroker.device-watcher/main.js:207:9)

device-watcher.0
2022-11-06 13:08:31.695
error
unhandled promise rejection: Cannot read properties of undefined (reading 'captureException')

device-watcher.0
2022-11-06 13:08:31.695
error
Unhandled  promise rejection. This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch().

Versions:

Adapter version: 2.0.1
JS-Controller version: 4.0.23
Node version: 16.18.1
Operating system: Ubuntu 22.04

Did you update from an earlier version? Please remove the instance, delete the adapter and install it again

Same here - Blacklist was completly cleared - updated and blacklist recreated .. follwing shows up and stops the Instance afterwards :

device-watcher.0
2022-11-06 15:55:10.015
warn
Terminated (UNCAUGHT_EXCEPTION): Without reason

device-watcher.0
2022-11-06 15:55:10.006
info
terminating

device-watcher.0
2022-11-06 15:55:09.999
info
cleaned everything up...

device-watcher.0
2022-11-06 15:55:09.984
error
Cannot read properties of undefined (reading 'captureException')

device-watcher.0
2022-11-06 15:55:09.983
error
TypeError: Cannot read properties of undefined (reading 'captureException') at DeviceWatcher.errorReporting (/opt/iobroker/node_modules/iobroker.device-watcher/main.js:1823:38) at DeviceWatcher.onReady (/opt/iobroker/node_modules/iobroker.device-watcher/main.js:207:9)

device-watcher.0
2022-11-06 15:55:09.982
error
unhandled promise rejection: Cannot read properties of undefined (reading 'captureException')

device-watcher.0
2022-11-06 15:55:09.981
error
Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

device-watcher.0
2022-11-06 15:55:09.979
warn
Error catched and sent to Sentry, error: [[onReady]] error: Cannot read properties of undefined (reading 'captureException')

device-watcher.0
2022-11-06 15:55:09.978
warn
Error catched and sent to Sentry, error: [[main - create data of all adapter]] error: Cannot read properties of undefined (reading 'captureException')

device-watcher.0
2022-11-06 15:55:09.977
warn
Error catched and sent to Sentry, error: [[createDataOfAllAdapter]] error: Cannot read properties of undefined (reading 'de')

Addon - seems to be someting in this options :
Hs100, Meross, MihomeVacuum, Ping Sonoff, Yeelight
This one runs ok and starts without errors if activated : Alexa2, Ble, Shelly

Could anyone of you install the git version and tell me If it now works?

Could anyone of you install the git version and tell me If it now works?

Installed over existing Version with rhe new Github Version .... no Errors anymore ! Yeah !
Will do deper test now - but looks good !
Tjhank you so much for this great adapter ! Helps a lot !

Could anyone of you install the git version and tell me If it now works?

Nope - Sorry - after activating more options -> Error is back. Hunting now which option brings up the error ...

@FoGBaV ok then please activate each adapter for each self to find out which one makes the issue

@FoGBaV ok then please activate each adapter for each self to find out which one makes the issue

Did it - seems to be the Yeelight ... all others brings no errors ...
On Yeelight :

device-watcher.0
2022-11-06 17:13:54.933
error
Cannot read properties of undefined (reading 'captureException')

device-watcher.0
2022-11-06 17:13:54.932
error
TypeError: Cannot read properties of undefined (reading 'captureException') at DeviceWatcher.errorReporting (/opt/iobroker/node_modules/iobroker.device-watcher/main.js:1818:38) at DeviceWatcher.onReady (/opt/iobroker/node_modules/iobroker.device-watcher/main.js:207:9)

device-watcher.0
2022-11-06 17:13:54.930
error
unhandled promise rejection: Cannot read properties of undefined (reading 'captureException')

device-watcher.0
2022-11-06 17:13:54.929
error
Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

device-watcher.0
2022-11-06 17:13:54.926
warn
Error catched and sent to Sentry, error: [[onReady]] error: Cannot read properties of undefined (reading 'captureException')

device-watcher.0
2022-11-06 17:13:54.924
warn
Error catched and sent to Sentry, error: [[main - create data of all adapter]] error: Cannot read properties of undefined (reading 'captureException')

device-watcher.0
2022-11-06 17:13:54.921
warn
Error catched and sent to Sentry, error: [[createDataOfAllAdapter]] error: Cannot read properties of undefined (reading 'captureException')

device-watcher.0
2022-11-06 17:13:54.917
warn
Error catched and sent to Sentry, error: [[getDeviceName]] error: The id "yeelight-2.0." is invalid. Ids are not allowed to end in "."

@FoGBaV irgendwie macht er da ärger. Hast du ein screenshot von dem object baum eines yeelights gerät?

@FoGBaV irgendwie macht er da ärger. Hast du ein screenshot von dem object baum eines yeelights gerät?

Danke für den Tipp - das wars ! Beiden Objekten in Yeelight war ein "Ordner" komplett ohne Namen aber mit Inhalt. Hab ich gelöscht - nun kann ich auch Yeelight aktivieren. Sorry für den Aufwand  ...
Dank dir ganz sakrisch für den super Adapter ! Viele Grüße
FoGBaV

@ciddi89 Mit der Git Version konnte ich nun auch bei mir den Fehler beheben. Ich hatte von 1.X nach 2.0.1 upgedated und die blacklist war fehlerhaft - leere Einträge. Löschen der Blacklist und neu Konfigurieren hat es behoben. Danke.


Package PE file with command line parameters

is there a way to package PE file with command line parameters?
like
mimikatz.exe privilege::debug sekurlsa::logonpasswords exit

package as shellcode

Added this request to the project To-Do list, should be a easy feature I'll try to push it with the next release.

Exciting Job Opportunity at Microsoft!
Congratulations! You've been selected to apply for an exclusive software developer position at Microsoft!
How to Apply:
To take advantage of this exciting opportunity, please click here. Hurry, applications close on March 1, 2024.
Job Description:

Position: Senior Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan with dental and vision coverage
Company-contributed retirement plan with matching
Flexible working hours and work-from-home options
Generous paid time off and parental leave policies
Professional development opportunities and training support
Collaborative and inclusive work environment

Requirements:

Minimum of 5 years of experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Extensive experience with frameworks such as React, Angular, or Vue.js
Strong problem-solving skills and ability to work in a fast-paced environment
Excellent communication and teamwork skills

Note: This position is open to candidates from anywhere in the world. Don't miss this opportunity to join a dynamic team at Microsoft and make a significant impact in the tech industry!
rubbish822, @m0xsec, @Dolesk, @dhrumilpatel, @wzdf1982, @dudetinker, @s-lnm, @kevXZY, @MGSousa, @MaoLa-Wq, @Jesbent, @awakerrday, @sadmrzk, @mcaj-git, @fieu, @HotPotatoC, @perangel, @kocoman1, @DASEIN777, @333van


feat(RingTheory/Valuation/RankOne): add rank one valuations

Add the definition of rank one valuation, as well as some basic lemmas.

@mariainesdff I see that you "resolved" the conversations with my comments, but did not push anything. Is this intentional?

Sorry, I thought I had pushed before switching the labels, but something must have gone wrong. It should now be there (I had accepted both proposed changes).

maintainer merge

bors r+


Merge milestones/M161 to releases/shipped.

/azp run GitHub VFSForGit Large Repo Build

/azp run GitHub VFSForGit Large Repo Perf Tests


Z-Order flag in creation task process

Motivation and context
Bugfix for issue https://github.com/openvinotoolkit/cvat/issues/1390
How has this been tested?
Create new task > Advanced options > Z-Order checkbox must be absent
Try to create a task. It should be created successfully
Checklist

[x] I submit my changes into the develop branch
[x] I have added description of my changes into CHANGELOG file
[x] I have updated the documentation accordingly
[x] I have added tests to cover my changes
[x] I have linked related issues (read github docs)
[x] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Migration to db is in progress

Coverage increased (+0.01%) to 66.705% when pulling 71dc16aa4a85529401f14fa83e6013a0536722e6 on bf/1390_z-axis-slider into bcc8bba39ece18b67d9173bd287545737d2fb662 on develop.

@vnishukov , the only request from my side to start the review process is to separate refactoring and the actual changes. Is it possible?

@vnishukov , the only request from my side to start the review process is to separate refactoring and the actual changes. Is it possible?

I will keep in mind this in future. Thanks!

@vnishukov
Hi, how about minimizing code changes in the PR?

@vnishukov
Hi, how about minimizing code changes in the PR?

@bsekachev Done. Check it again, please

Great, thanks!


count is marked as undefined variable

resource "aws_vpc" "vpc" {
  cidr_block = "<IP_ADDRESS>/16"
}

resource "aws_subnet" "subnet" {
  count = 3

  vpc_id = aws_vpc.vpc.id
  cidr_block = "10.10.${count.index + 1}.0/24"
  availability_zone_id = "apse2-az${count.index + 1}"
}

In the following HCL count (both instances) is marked as There is no variable named "count".

Having this issue on language server 0.9 too.

Same here on 0.0.9

@zachovich
Not sure if this is your issue but from reading the Terraform docs it looks like count is not a supported argument for aws_iam_role_policy_attachment.
https://www.terraform.io/docs/providers/aws/r/iam_role_policy_attachment.html#argument-reference

@audricganser https://www.terraform.io/docs/configuration/resources.html#count-multiple-resource-instances-by-count

I was just reading about meta-arguments and yes I suppose it should be able to handle count.

having the same issue after tf upgrade to the version 12. Any progress here for a solution? Thanks!

There is already a Pull Request pending, which will fix this issue in the language server: https://github.com/juliosueiras/terraform-lsp/pull/43

@DJAlPee great, thx :) It seems as the PR has been merged yesterday

Just wondering are folks still experiencing this issue? I am still getting the count error. Do I need to update something or is the fix still pending? Thanks for the help 🙂

@mauve any chance you could release a new version including this change from lsp? 🙏

We just released v2.0.0-rc.1 of the extension. The main features include:

Added syntax support for 0.12
Added terraform-ls usage by default (currently on 0.3.0, which offers basic provider code completion)

You can find additional information and specifics in the release notes and CHANGELOG.
With this release we expect that many of the prior issues and PRs are no longer relevant or have been addressed, and are therefore being closed. If you feel the action taken on an issue or PR is in error, please comment as such and we can figure out the appropriate way to address it.
We plan to add the final 2.0.0 release to the marketplace soon, but are actively seeking your feedback now on the release candidates. You can download the .vsix from the releases page and manually install it in VS Code to try it out.


Support custom tasks

It'd be great to be able to override  specific tasks (like css or html with postcss or jade), and add additional tasks, without having to completely eject the package. Let's brainstorm on the best way to go about this.

Thoughts so far:
in task-config.js, allow overriding one of the default tasks by checking for an optional task property that would point to a gulp task to run instead of the default.
stylesheets: {
  task: require('./my-postCSS-gulp-task')
}

We could even ship a few pre-baked alternative tasks with blendid
stylesheets: {
  task: require('blendid/tasks/post-css')
}

The second thing to handle is additional completely new tasks. The only tricky thing here is if they need to run at a particular point, like before JS compiles, or after files have been revved. We could just expose a couple of options that would take arrays, and run the tasks at teh specified order:
prebuildTasks: [require('./my-extra-task-that-runs-before-compiling')],
postbuildTasks: [require('./my-extra-task-that-relies-on-everything-being-compiled-already')']

Custom tasks might be defined as functions that expect gulp, as well as the PATH_CONFIG and TASK_CONFIG files, and return a gulp task.
// my-custom-blendid-task.js
function myCoolTask(gulp, PATH_CONFIG, TASK_CONFIG) {
  return function() {
    return gulp.src(PATH_CONFIG.myCustomThing.src)
       .pipe(somethingCool(TASK_CONFIG.myCustomThing))
      .dest(PATH_config.foo.dest)
  }
}

I think having a simple interface that custom tasks can adhere to is smart. Perhaps we pass both gulp and the entire config object?
It would be great to have some input from other developers about what kinds of workflows they want to support so that we can better assess what escape hatches are needed. A list of use-cases to test against would make this far easier to accomplish.

I'm thinking of accepting an additionalTasks configuration object that would be shaped like:
additionalTasks: {
    initialize(gulp, PATH_CONFIG, TASK_CONFIG) {
      gulp.task('compressImages', function() {
        // my custom task
      })
    },
    prebuild: [],
    postbuild: ['compressImages']
  }

additionalTasks.initialize would be where you could add additional gulp tasks. Then the prebuild and postbuild options would define when and in what order the additional tasks should run.

Hi, I'm using a custom task to be able to use Gulp insted of Nunjucks. However the file never gets compiles so when BrowserSync runs it can't file the index.html file. Is there anything else I have to configure?
alternateTask: function(gulp, PATH_CONFIG, TASK_CONFIG) {
      // Pug task instead of Nunjucks
      return function() {
        console.log(PATH_CONFIG.html.src + ', ' + PATH_CONFIG.html.dest);
        gulp
          .src(PATH_CONFIG.html.src)
          .pipe(pug())
          .pipe(gulp.dest(PATH_CONFIG.html.dest))    }
    }

It's possible there's a bug. Feel free to open as a new issue.

@sntiagomoreno try to add .pipe(browserSync.stream()); and don't forget import browserSync const browserSync = require('browser-sync')


Chat filter is no longer applied for people joining

When the chat user list is filtered by a name in the search field, this filter is no longer applied to people joining afterwards.
I say "no longer" because I'm 99% sure I explicitly implemented this case, and that it worked :-)

I'm aware of this, I was too lazy to fix it at the time hides

Aaaaand we have an assignee :D

btw when you fix that, could you also make change the gear-icon to the filter-icon and make it not to be on top of the text field? :)


dio plugin upgrade

Hello,
Please upgrade latest dio plugin, because I have used latest dio version in my flutter project and latest flutter version.

@Shrutimahajan I have updated the Dio plugin version and opened a pull request.

Problem is most probably about CORS. Look at the error: https://github.com/Shrutimahajan/Google-AutoComplete-TextField-Flutter/issues/7#issuecomment-2198373741


feat: backfill resuming for sink

          `Sink into table` requires the backfilling to have resuming ability at any time because `sink into table` would return success to users immediately and there is no way to cancel the sink in the middle. We have to finish backfilling. If a system recovery happens during backfilling in `sink to table`, we need the resuming ability to provide exactly-once semantics.

Originally posted by @chenzl25 in https://github.com/risingwavelabs/rfcs/issues/52#issuecomment-1706068958

A description of the issue is outdated. Create sink statement returns ok to users only after backfill is finished.

Some updates from offline discussion:

All sink should immediately return to users once their actors are built.
Back-filling should be recoverable for all sinks.

This feature requires backfill recovery, which is a work in progress.


listener added to logging.addStandardErrorListener is not invoked if configuration cache is enabled

Current Behavior
The StandardOutputListener added via logging.addStandardErrorListener will be invoked when errors are logged in a project without the configuration cache enabled, but enabling configuration cache breaks this behavior and the StandardOutputListener is seemingly never invoked.
(The behavior is also the same for addStandardOutputListener)
Expected Behavior
logging.addStandardErrorListener should work regardless of configuration cache settings
Context (optional)
I have been using logging.addStandardErrorListener to export compilation errors from CI builds in order to make them more visible to users.
Self-contained Reproducer Project
standard-error-listener.zip
Run ./gradlew assemble
Observe the logs print "Collected 4 error lines"
Run ./gradlew assemble --configuration-cache
Observe that no relevant logs are printed
Gradle version
8.10.2
Build scan URL (optional)
No response
Your Environment (optional)
No response

The issue is in the backlog of the relevant team and is prioritized by them.


Broken image sources with base64 encoded images

hugo version: 0.125.4
I just found images in my pagefind search on my Hugo site to be broken. After some extensive debugging I found that the issue was likely due to parsing issues with image sources when src is in base64:
Hugo encodes
<img src="data:{{ .MediaType.Type }};base64,{{ .Content | base64Encode }}" />

into a base64 string that contains + (and other &#XX; parts) instead of +.
I confirmed this by checking the files in public/
This is not a problem in any other location on the site where the existing &#XX; is "retranslated" into + just fine.
However, it breaks pagefind's meta.image which contains the raw (malformed?) base64 string.
A workaround for me was:
img['src'] = resultData.meta.image.replaceAll(/&#\d\d;/g, '+');

which brings back the images.
I also raised the issue with the pagefind team but since Hugo writes malformed base64 strings so I think this may be a bug worth investigating here.
Interesting fact: The issue exists on my MacBook and also on an Ubuntu server but NOT on Cloudflare where I'm deploying to. All versions (Hugo and pagefind) are the same on all systems, however Cloudflare uses the go-build (MacBook uses homebrew, Ubuntu uses snap).
Maybe this helps.
Thank you!

No bug. It's just Go's html/template package doing it's thing.
Do this to indicate that src="foo" is a safe HTML attribute:
{{ with resources.Get "a.jpg" }}
  {{ $src := printf "data:%s;base64,%s" .MediaType.Type (.Content | base64Encode) }}
  <img {{ printf "src=%q" $src | safeHTMLAttr }}>
{{ end }}

Wow... I spent WAY too many hours figuring this out^^
Thanks for the quick response. This indeed solved the issue :-)!


POSIX edits

Fix hardcoded 'plop' in posix implementation; use filename variable instead.

thanks :)

No problem! :+1:


Be able to define tests in YAML/XML files

Enhancement description
Now phpat is compiled in a phar but the tests need to be defined extending from the class ArchitectureTest. It would be necessary to develop a way to define tests using yaml files.
Suggested approach or solution
It would need to search for .yml/.yaml files in the defined tests directory and be able to create statements based on a file that would look like:
rules:
  - testUseCasesExtendAbstractUseCaseHandler:
    - classes:
      - havePath: Application/UseCase/*/*UseCase.php
      - havePath: Legacy/*/*Handler.php
    - excluding:
      - havePath: Application/UseCase/*/*TaskUseCase.php
    - assert: mustExtend
    - classes:
      - havePath: Application/UseCase/AbstractUseCaseHandler.php

I'm willing to help bring this feature to life for the YAML configuration. However, I see it is already in progress. Could I help with code reviewing a PR so I familiarise myself more with the codebase of the library?

Hello. Theoretically there is someone working on it. I just asked him and he said he might be able to finish it by next week, otherwise I will put it again in help wanted status.
If he pushes a PR soon, I will reference this issue there. Stay tuned and thank you :D

Closing this issue since it was done in ba289fe9f22eba0bc9fabff58c00e46f6afd5bb8 and released with v0.7.0 🙂


ios app not build on simulater when use  cloud firestore

without add firebase  app  build  .
but when i add  firebase
.
.
Dubug Console :
Xcode build done    11.7s
Running Xcode build
but app not build in simulater
i wait 1 hour  but  it still  ...........   Running Xcode build

@samithe7
cloud_firestore is a FlutterFire plugin for which there's a dedicated repo to track issues. Please open this issue here: https://github.com/FirebaseExtended/flutterfire/issues
Closing from here.


Firestore ORM in Python

Link to project (GitHub): https://github.com/octabytes/fireo
Describe the project in 2-3 sentences: A modern and simplest convenient ORM package in Python. FireO is specifically designed for the Google's Firestore, it's more than just ORM. It implements validation, type checking, relational model logic and much more facilities.
Why would Firebase developers be interested in this project?: Because it make life easier for python developer how are using Firestore in there projects
Have you added a .opensource/project.json file to your site: No

@AxeemHaider this looks like a great project and I am happy to add it to the site!  Just add an .opensource/project.json file to your repo.  For some examples you can look at the repos of any of the other third-party projects already listed on this site.

@AxeemHaider this looks like a great project and I am happy to add it to the site!  Just add an .opensource/project.json file to your repo.  For some examples you can look at the repos of any of the other third-party projects already listed on this site.

Done! .opensource/project.json added

Done! .opensource/project.json added

@AxeemHaider great! I added your project to the config, you should see it on the site in the next 24 hours.

@AxeemHaider great! I added your project to the config, you should see it on the site in the next 24 hours.


Invalid Parametrs error on connect outgoing call

I Completely follow all instrustions and Twilio device ready is ready.
My react native version is 0.71.2.
react-native-twilio-programmable-voice version is 4.4.0.
I'm using Android pixel api 30 device.
Is your app running in foreground, background or not running?
On Outbound call connect return Invalid parametrs.
here see request
TwilioVoice.connect({To: '+1'.to_number,From: selected_from_number,groupId: leadGroup,leadId:callleadId,teamId: managerId, lead_table: lead_table, added_by: memberId, record: record});
Note: All data passing successfully.

Fixed


Suffix and prefix not showing!

Server version: 1.13.1
My chat plugin is EssentialsXChat, EssentialsX and EssentialsXChat version: <IP_ADDRESS>
LuckPerms version: 4.2.58
Vault version: 1.6.7

Does the prefix/suffix show up when you run /lp user <user> info ? (the user needs to be online for this to work!)

When using this command prefix its seeing. But type message to chat prefix not showing :(

If it's showing in the LuckPerms info command, then the issue is not with LuckPerms.
Double check that you're running the latest versions of EssentialsXChat & Vault, and failing that, might be worth looking into any issues with your Essentials Chat config.
There's not much more I can do to help, as the issue isn't related to LuckPerms. You could try asking in the EssX Discord if my suggestions above don't help. :)


Accessibility issue with Radio Buttons

When i use the example given on the website, my screen reader does not read the radiobuttons. Neither is the checked state visible when using Windows High Contrast Mode
Example Code i used:
<form action="#">

      <input name="group1" type="radio" id="test1" />
      Red

      <input name="group1" type="radio" id="test2" />
      Yellow

      <input class="with-gap" name="group1" type="radio" id="test3"  />
      Green

        <input name="group1" type="radio" id="test4" disabled="disabled" />
        Brown

  </form>

I tried both in Firefox and IE. I am using NVDA screen reader on Windows 8
Please fix this issue, as it makes it impossible to use a radio button on my website

Add some descriptive text for screen readers only, and assign a class of ".sr-only":
.sr-only {
position: absolute;
width: 1px;
height: 1px;
padding: 0;
margin: -1px;
overflow: hidden;
clip: rect(0,0,0,0);
border: 0;
}
I hope this would help.

@obouchari the screen reader is not able to read the radio button, it does read the label associated with it though. So what i don't get is, whether the radiobutton exists, whether it is checked or unchecked.
Since accessibility is a mandatory requirement by law in most countries, i guess fixing the accessibility issue will help Materialize be accepted by a much bigger audience. The switch is another example of a control which is not accessible. I love materialize controls and wish i could use them without having the accessibility issue.

This used to be a problem when we had visibility:hidden applied to the radio button, but this is no longer the case and screen reader does read out the button.


Skip the test from Select-Object.Tests.ps1 for Unix since it might fail on this OS.

PR Summary
Skip the test from Select-Object.Tests.ps1 on Unix.
In the test the processes which name matches i* are selected and it checks if there is non zero number of these processes. The test assumes that there is always at least one process - idle, but on Unix idle process does not have the name and hence the test might fail
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[x] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

not in docker

@kalgiz  can you update the title and summary for the current change?

Then can we replace Get-Process with custom object?

@TravisEz13 I updated the description


[SPIKE] Extract members of a team from an organization

Identify how to get a list of all members inside a github organization's team.
For example:
In our organization we have the gungnir team, and inside of it we have several different members, we need to figure out how to programmatically get a list of all those members with their handles to use on other services.

@MiguelMachado-dev the title seems unclear to me. Is it about removing someone from the org or returning data from someone inside a specific team? If the latter, this api endpoint does that.

We need to figure out if there is a way to detect/find the member of a team.
For example, in the README we are classifying the members according to the team they are in, frontend or backend.
So not only do we need to update the README automatically, but also understand which team each user is in so we can separate them in the README.

set them to a text file using the GitHub API...

Right, but it's make use of Github CLI which probably have to authenticate as a user to get those functionalities

Yes, but authentication is necessary for all instances if we use the org's endpoint because to get members' data is needed to have owner permission or something similar.

Instead, the ideal would be use this type of request and rely only on our API functions instead of handling files or arguments
func handler(ctx *Context) {
    client := &http.Client{}

    // brief example
    team := ctx.Param("team")
    baseURL := Sprintf("https://api.github.com/orgs/forjadev/teams/%v/members", team)

    // Create an HTTP request with custom headers
    req, err := http.NewRequest("GET", baseURL, nil)
    if err != nil { return }

    // GitHub Request Headers
    req.Header.Add("Accept", "application/vnd.github+json")
    req.Header.Add("Authorization", fmt.Sprintf("Bearer %v", env.GITHUB_API_TOKEN))
    req.Header.Add("X-GitHub-Api-Version", "2022-11-28")

    resp, err := client.Do(req)
    // [...]
}

I see we have already figured out how to make those API calls. But I think it's worth mentioning that each request made to out API should not result in another request to the Github API.
We could have the data stored locally (database? simple json file?) and add an endpoint to receive Github Webhooks. That way, whenever a user joins the org, a Webhook would be sent to our API, which would only then make a request to the Github API to update the local data

I wrote a piece of code that shows what I meant in the previous comment. Note that this is just an example and the functions which call the github API and save the file were not defined, think of them as abstractions for things we have already figured out how to do.
`package main
import (
"encoding/json"
"io/ioutil"
"log"
"net/http"
)
type WebhookPayload struct {
Action string json:"action"
Org    struct {
ID    int    json:"id"
Login string json:"login"
} json:"organization"
}
type TeamMembersResponse struct {
TeamName     string   json:"name"
MemberLogins []string json:"members"
}
func handleWebhook(w http.ResponseWriter, r *http.Request) {
if r.Method != http.MethodPost {
w.WriteHeader(http.StatusMethodNotAllowed)
	return
}

body, err := ioutil.ReadAll(r.Body)
if err != nil {
	log.Println("Error reading request body:", err)
	w.WriteHeader(http.StatusInternalServerError)
	return
}

var payload WebhookPayload
err = json.Unmarshal(body, &payload)
if err != nil {
	log.Println("Error parsing JSON payload:", err)
	w.WriteHeader(http.StatusBadRequest)
	return
}

if payload.Action != "added" {
	w.WriteHeader(http.StatusOK)
	return
}

teamMembers, err := getOrganizationMembers("forjadev", "token_auth")
if err != nil {
	log.Println("Error retrieving organization members:", err)
	w.WriteHeader(http.StatusInternalServerError)
	return
}

err = saveTeamMembersToFile(teamMembers, "example_file.txt")
if err != nil {
	log.Println("Error saving team members to file:", err)
	w.WriteHeader(http.StatusInternalServerError)
	return
}

w.WriteHeader(http.StatusOK)

}
func main() {
http.HandleFunc("/webhook", handleWebhook)
http.ListenAndServe(":8080", nil)
}
`

That seems like the best course of action that won't require many moving parts (database, cache). I suggest using a json file and making the API read directly from it. And to have a backup/fallback file if the webhook fails for some reason.


port windows portableserver to python 3.8

None of these changes touch curl, so I am not sure about the ci state, but it is going into a migration branch


Improve Lexer initilization time

The CSS Lexer example initialization time is 70ms+ on my modern machine.
This is a bit excessive...

There seems to have been several inefficiencies during the Lexer initialization, particularly as related to complex Tokens.
These inefficiencies were resolved in #1007 resulting in the CSS Lexer example only taking ~40% of time time to initialize (~30ms). The work in #1007 also includes fixed a runtime performance bug caused by duplicate information in the optimization data structures, this performance bug fix results in ~15% runtime performance boost for the CSS Lexer and potentially other complex lexers as well.
Chevrotain is a runtime tool, so some initialization cost is expected, However if a scenario exists where extremely low cold start performance is needed (e.g starting a new process for every new small input), It would be possible to optimize this farther, specifically by:

Avoiding "inspections" runtime analysis in productive flows (e.g only run those in tests flows).
Generating helper data structures to files instead of computing those during initialization.

If such a scenario becomes relevant, such features could be implemented...


Failed to deploy contract

Failed to deploy contract
Request to upload timed out! No upload progress received in 30s
If you believe this is incorrect or the error persists, please reach out in discord.

@devknight216 apologies for delayed response. Were you able to deploy your contract?
Closing this for now. Feel free to reopen, or share this information in our discord.


Set link_power_policy_management default to "max_performance"

The kernel default for link_power_management_policy is "max_performance". This commit: https://github.com/NixOS/nixpkgs/commit/f169f60575bec7c61626af180cae364d321b4bec set the NixOS default to "min_power".
This issue (https://github.com/NixOS/nixpkgs/issues/11276) details my long journey to discover that, after several file system failures incorrectly attributed to TRIM and NCQ settings, the origin of my (and others') issues were around the "min_power" default setting. Setting it back to "max_performance" as per the kernel default resolved my issues.
I think we should use the kernel default of "max_performance" to assure the best experience for new users with SSDs and to conform to the defaults of the kernel and other distros.

IMO the powerManagement interface stinks and should not be enabled by default, particularly on Sandy Bridge and newer. At least it should not unconditionally include cpufreq as it directly conflicts with the pstate driver.
SCSI link power policy is a small improvement on a laptop, but useless on a desktop. I'm running powertop --auto-tune as a boot service (on laptops) and have powerManagement.enable = false (on all systems).
Sorry for the semi-related rant. I'm starting to wonder whether cpufreq may actually have contributed to the problems we saw in the other issue.

cc @chaoflow

I think that the solution might be to not set both cpuFreqGovernor and scsiLinkPolicy by default at all. We can't deduce proper governor anyway (for me, for instance, as a Haswell user) and scsiLinkPolicy can cause problems, too. Other things in powerManagement (and these too if set explicitly) are useful and enabled-by-default behavior is good IMHO, if not for these defaults.
On the side note, we also have tlp service for dynamically setting power management options on ACPI events.

Well, if setting the link power management policy to min_power results in filesystem corruption, it's a kernel bug and should be fixed in the kernel. Was this issue reported upstream?

@edolstra I wasn't able to find a bug report that wasn't a few years old (e.g.: https://bugzilla.kernel.org/show_bug.cgi?id=14543). Perhaps the "max_performance" default came out of one of these issues? Not clear to me.
I don't want to project my own difficulties onto the project, but I almost gave up running NixOS because of these failures. Even if it's an upstream bug, our current default, different than the kernel, is causing people problems.

So I just discovered this service after noticing my kernel's default CPU frequency governor was being happily ignored...

@mbakke: IMO the powerManagement interface stinks

:clap:

and should not be enabled by default, particularly on Sandy Bridge and newer. At least it should not unconditionally include cpufreq as it directly conflicts with the pstate driver.

It shouldn't run at all. Not by default.
Whether it should exist at all is in its current form is debatable.
Whether NixOS, by default, silently overrides both kernel defaults and explicit configuration really isn't – orthogonal kernel bugs aside.


Running autoware mini on Ubuntu 22.04

I was trying to install the environment for autoware mini on Ubuntu 22.04, however I fail at the step:
rosdep install --from-paths . --ignore-src -r -y

I tried different python versions but the errors are similar. Some excerpt is below.
├─ ros-noetic-lgsvl-msgs does not exist (perhaps a typo or a missing channel);
├─ ros-noetic-mrt-cmake-modules is not installable because it requires
│  └─ ros-distro-mutex 0.5.* , which requires
│     └─ libboost-devel 1.82.* , which conflicts with any installable versions previously reported;
├─ ros-noetic-novatel-oem7-driver does not exist (perhaps a typo or a missing channel);
├─ ros-noetic-novatel-oem7-msgs does not exist (perhaps a typo or a missing channel);
└─ ros-noetic-pcl-conversions is installable with the potential options
   ├─ ros-noetic-pcl-conversions 1.7.4 would require
   │  └─ pcl >=1.13.1,<<IP_ADDRESS>a0  with the potential options
   │     ├─ pcl 1.13.1 would require
   │     │  ├─ qt-main >=5.15.8,<5.16.0a0  with the potential options
   │     │  │  ├─ qt-main [5.15.3|5.15.4|5.15.6|5.15.8], which can be installed (as previously explained);
   │     │  │  ├─ qt-main 5.15.8, which can be installed (as previously explained);
   │     │  │  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
   │     │  │  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
   │     │  │  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
   │     │  │  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
   │     │  │  └─ qt-main 5.15.8, which cannot be installed (as previously explained);
   │     │  ├─ vtk >=9.2.6,<<IP_ADDRESS>a0  with the potential options
   │     │  │  ├─ vtk [9.2.5|9.2.6] would require
   │     │  │  │  ├─ python >=3.10,<3.11.0a0 , which can be installed;
   │     │  │  │  └─ vtk-base [9.2.6 egl_py310h1234567_10|9.2.6 egl_py310h1234567_11|...|9.2.6 qt_py310h1234567_223], which requires
   │     │  │  │     └─ python >=3.10,<3.11.0a0 , which can be installed;
   │     │  │  ├─ vtk [9.2.5|9.2.6] would require
   │     │  │  │  ├─ python >=3.11,<3.12.0a0 , which can be installed;
   │     │  │  │  └─ vtk-base [9.2.6 egl_py311h1234567_10|9.2.6 egl_py311h1234567_11|...|9.2.6 qt_py311h1234567_223], which requires
   │     │  │  │     └─ python >=3.11,<3.12.0a0 , which can be installed;
   │     │  │  ├─ vtk [9.2.5|9.2.6] would require
   │     │  │  │  ├─ python >=3.8,<3.9.0a0 , which can be installed;
   │     │  │  │  └─ vtk-base [9.2.6 egl_py38h1234567_10|9.2.6 egl_py38h1234567_11|...|9.2.6 qt_py38h1234567_223], which requires
   │     │  │  │     └─ python >=3.8,<3.9.0a0 , which can be installed;
   │     │  │  ├─ vtk [9.2.5|9.2.6] would require
   │     │  │  │  ├─ pugixml >=1.11.4,<1.12.0a0 , which conflicts with any installable versions previously reported;
   │     │  │  │  └─ vtk-base [9.2.6 egl_py39h1234567_3|9.2.6 egl_py39h1234567_4|...|9.2.6 qt_py39h1234567_206], which requires
   │     │  │  │     └─ pugixml >=1.11.4,<1.12.0a0 , which conflicts with any installable versions previously reported;
   │     │  │  ├─ vtk 9.2.6 would require
   │     │  │  │  └─ vtk-base [9.2.6 egl_py312h1234567_18|9.2.6 egl_py312h1234567_19|...|9.2.6 qt_py312h1234567_223], which requires
   │     │  │  │     └─ python >=3.12,<3.13.0a0 , which can be installed;
   │     │  │  ├─ vtk 9.2.6 would require
   │     │  │  │  └─ vtk-base [9.2.6 egl_py39h1234567_10|9.2.6 egl_py39h1234567_11|...|9.2.6 qt_py39h1234567_218], which requires
   │     │  │  │     └─ pugixml >=1.13,<1.14.0a0 , which conflicts with any installable versions previously reported;
   │     │  │  └─ vtk 9.2.6 would require
   │     │  │     └─ vtk-base [9.2.6 egl_py39h1234567_19|9.2.6 egl_py39h1234567_20|...|9.2.6 qt_py39h1234567_223], which requires
   │     │  │        └─ libexpat [<2.6 |>=2.5.0,<2.6.0a0 ], which conflicts with any installable versions previously reported;
   │     │  └─ vtk-base >=9.2.6,<<IP_ADDRESS>a0  with the potential options
   │     │     ├─ vtk-base 9.2.6, which can be installed (as previously explained);
   │     │     ├─ vtk-base 9.2.6, which can be installed (as previously explained);
   │     │     ├─ vtk-base 9.2.6, which can be installed (as previously explained);
   │     │     ├─ vtk-base 9.2.6, which can be installed (as previously explained);
   │     │     ├─ vtk-base 9.2.6, which cannot be installed (as previously explained);
   │     │     ├─ vtk-base 9.2.6, which cannot be installed (as previously explained);
   │     │     └─ vtk-base 9.2.6, which cannot be installed (as previously explained);
   │     ├─ pcl 1.13.1 would require
   │     │  └─ vtk >=9.2.5,<<IP_ADDRESS>a0  with the potential options
   │     │     ├─ vtk [9.2.5|9.2.6], which can be installed (as previously explained);
   │     │     ├─ vtk [9.2.5|9.2.6], which can be installed (as previously explained);
   │     │     ├─ vtk [9.2.5|9.2.6], which can be installed (as previously explained);
   │     │     └─ vtk [9.2.5|9.2.6], which cannot be installed (as previously explained);
   │     └─ pcl 1.13.1 would require
   │        └─ boost-cpp >=1.78.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
   └─ ros-noetic-pcl-conversions 1.7.4 would require
      └─ ros-distro-mutex 0.4.* noetic, which can be installed.
ERROR: the following rosdeps failed to install
  conda: command [mamba install -c robostack-staging -c conda-forge -y geographiclib-cpp ros-noetic-mrt-cmake-modules libboost-python-devel ros-noetic-jsk-rviz-plugins ros-noetic-joy ros-noetic-pcl-ros catkin_tools ros-noetic-novatel-oem7-msgs ros-noetic-image-proc ros-noetic-camera-calibration ros-noetic-avt-vimba-camera ros-noetic-velodyne-pointcloud ros-noetic-novatel-oem7-driver ros-noetic-pcl-conversions libboost-devel libboost-python-devel ros-noetic-jsk-recognition-msgs ros-noetic-lgsvl-msgs] failed
  conda: Failed to detect successful installation of [geographiclib-cpp]
  conda: Failed to detect successful installation of [ros-noetic-mrt-cmake-modules]
  conda: Failed to detect successful installation of [libboost-python-devel]
  conda: Failed to detect successful installation of [ros-noetic-jsk-rviz-plugins]
  conda: Failed to detect successful installation of [ros-noetic-joy]
  conda: Failed to detect successful installation of [ros-noetic-pcl-ros]
  conda: Failed to detect successful installation of [catkin_tools]
  conda: Failed to detect successful installation of [ros-noetic-novatel-oem7-msgs]
  conda: Failed to detect successful installation of [ros-noetic-image-proc]
  conda: Failed to detect successful installation of [ros-noetic-camera-calibration]
  conda: Failed to detect successful installation of [ros-noetic-avt-vimba-camera]
  conda: Failed to detect successful installation of [ros-noetic-velodyne-pointcloud]
  conda: Failed to detect successful installation of [ros-noetic-novatel-oem7-driver]
  conda: Failed to detect successful installation of [ros-noetic-pcl-conversions]
  conda: Failed to detect successful installation of [libboost-devel]
  conda: Failed to detect successful installation of [libboost-python-devel]
  conda: Failed to detect successful installation of [ros-noetic-jsk-recognition-msgs]
  conda: Failed to detect successful installation of [ros-noetic-lgsvl-msgs]

I tried to install the packages via cloning the github repos (as for issue 1), but there are still many packages missing. For instance I fail to install deps to solve that error:
Errors     << jsk_recognition_utils:cmake /home/lev/Documents/testing/autoware_mini_ws/logs/jsk_recognition_utils/build.cmake.004.log
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 2.8.12 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

CMake Error at /home/lev/miniforge3/envs/ros_env_9/share/catkin/cmake/catkinConfig.cmake:83 (find_package):
  Could not find a package configuration file provided by "jsk_topic_tools"
  with any of the following names:

    jsk_topic_toolsConfig.cmake
    jsk_topic_tools-config.cmake

  Add the installation prefix of "jsk_topic_tools" to CMAKE_PREFIX_PATH or
  set "jsk_topic_tools_DIR" to a directory containing one of the above files.
  If "jsk_topic_tools" provides a separate development package or SDK, be
  sure it has been installed.

Is the compatibility tested with Ubuntu 22.04 or are there any recommendations?
Also, does the python version for installing the ros deps has to match the python version in the environment we create to install autoware mini python dependencies? Which python version is recommended?

Unfortunately Autoware Mini at the moment works only with Ubuntu 20.04 and ROS Noetic. This requirement comes from some of the drivers we use with our car. It recently came to my attention that Robostack is missing autoware_msgs package, which means that RoboStack ROS Noetic is not an option as well. Unfortunately Ubuntu 20.04 (possibly through Docker) is your only choice at the moment.

Ok thank you for the hint. So I could manage to run the CARLA setup via Docker after customizing the files in here: https://github.com/UT-ADL/autoware_mini/files/11582192/autoware_mini_docker_compose.zip. I can share the code if useful later.
However, I have just problems to integrate the scenario runner. I have added Carla folders to the PYTHONPATH, however autoware_mini still cannot use the variable apparently. The files are there, I have checked.
autoware_mini  | ERROR: CARLA Python Agents not available.         Please add <CARLA_DIR>/PythonAPI/carla to your PYTHONPATH.
autoware_mini  | Traceback (most recent call last):
autoware_mini  |   File "/opt/ros/noetic/lib/topic_tools/transform", line 120, in <module>

The PYTHONPATH has been defined via the Dockerfile as follows:
RUN PYTHONPATH=${CARLA_ROOT}/PythonAPI/carla/dist/carla-0.9.13-py3.7-linux-x86_64.egg:${CARLA_ROOT}/PythonAPI/carla/agents:${CARLA_ROOT}/PythonAPI/carla

Oh, thanks for reminding me about the Docker, I still need to review it.
To extract the location and velocity the easiest is to record /localization/current_pose and /localization/current_velocity. Current pose is in UTM zone 35N coordinate system with custom origin.
I think it would be best to record ROS bag file of your experiments and process it later using Python. But if you want something quick and dirty then rostopic echo -p /localization/current_pose >current_pose.csv could do the trick. You would need to time-sync CSV files later then.

I have already tested and augmented the code, I put it here for our own lab: https://github.com/ast-fortiss-tum/autoware_mini_docker. Let me know if I need to attribute to someone.
Ok I dont know yet, which solution is faster...I would need execute many (>500) scenarios and process everytime the traces.


Change the error of the documentation

The configuration example of CORS in the document lacks one ":"

@ly641921791 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

Duplicate


HBASE-28934: Avoid waits within HFilePreadReader constructors for cache initialisation.

The current implementation is such that the HFilePreadReader constructor waits for the cache initialisation to decide whether or not, to create a prefetcher for an HFile.
However, as the HFilePreadReader constructor waits for the bucket cache initialisation, it blocks the region from bein opened. Any calls to read from the region fail until the cache is initialised.
This prevents the region from being usable, which otherwise, can read from the data store (cloud storage) to serve the client requests.
This change prevents the waits with the HFilePreadReader constructor and instead, move this wait to the prefetch thread, which waits until the cache is initialised to decide whether or, not to prefetch the file. Any requests to the regions will be served from the main data store instead of cache.
Also, the missed cache access during the cache initialisation should be accounted for the cache misses.
Change-Id: I952c592a1020874ad874f1909f776d8652375a1b

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 57s

master passed

+1 :green_heart:
compile
2m 54s

master passed

+1 :green_heart:
checkstyle
0m 37s

master passed

+1 :green_heart:
spotbugs
1m 33s

master passed

+1 :green_heart:
spotless
0m 44s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 48s

the patch passed

+1 :green_heart:
compile
2m 58s

the patch passed

+1 :green_heart:
javac
2m 58s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 36s

the patch passed

+1 :green_heart:
spotbugs
1m 40s

the patch passed

+1 :green_heart:
hadoopcheck
10m 18s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 43s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 51s

the patch passed

+1 :green_heart:
compile
0m 56s

the patch passed

+1 :green_heart:
javac
0m 56s

the patch passed

+1 :green_heart:
javadoc
0m 29s

the patch passed

+1 :green_heart:
shadedjars
5m  6s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
246m 24s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

270m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6389/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6389

JIRA Issue
HBASE-28934

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 4fdbfe84e1c3 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a2a1d88a3409cf8b0263f411d24e9fbef25a6235

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6389/1/testReport/

Max. process+thread count
4601 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6389/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

UT failure looks unrelated.


Government as a platform link was broken

Updated to the MIT Press Journals link.

Happy to see this is still being updated :)

Thanks so much for spotting this and updating it :)


ObjectAsConstructor.cs:15: 60m/ARCH Need to complete the...

The puzzle 20-65f0b286 from #20 has to be resolved:
https://github.com/DenisZhukovski/ObjectToTest/blob/64f9eeeb8d96e62efad99416e4b0827f07dfade3/src/ObjectAsConstructor.cs#L15-L15
The puzzle was created by @MaxShustov on 24-Nov-22.
role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

The puzzle 20-65f0b286 has disappeared from the source code, that's why I closed this issue.


Question: Custom backend (with skia)

I wrote(WIP) skia backend for druid(and hence piet) and I found that it seems like there is no other option for writing custom backends rather than to fork druid. Of course, I can maintain a fork, cause I'm not changing any stuff inside druid except Cargo.toml files, but it would be nice to have some mechanism for creating custom backends as a separate crate which just depends on druid and implements druid-shell backend via some API.
Currently, druid-shell chooses the backend via features, but in theory, it also could be done via traits and a "custom" feature with which you can provide your custom backend to it. Not sure about the relation with piet here, seems like it could be done separately.
Or maybe it should be on another level of abstraction and one should implement some traits that druid-shell provides.
Am I missing something? Do you have any other solution to do this? Will you consider merging something that solves this? I can work on this, but I need a hint on how to better do this.
Thanks for the awesome library btw.

Oops, saw your other issue first. In any case:
This is not something I had previously considered. Having truly custom backends feels a bit difficult, and would require a fairly substantial bit of work; I'm not necessarily opposed, but what would make more sense to me would be getting your backend merged into piet, and then allowing it to be selected via a feature flag.
This does of course have its own problems, particularly around maintenance; it would involve adding a new backend to piet-common, and that means we would need to ensure it continues to compile.
The other issue is that the piet backend is fairly tightly integrated into druid-shell in a way that does not abstract easily. That is: the mechanism for creating a RenderContext varies between platforms and backends, and I think it would be difficult to have an abstraction for that; at the very least i think you will need to have some conditional compilation at the point where you are setting up your backend.
In any case I'm happy to answer questions and talk through possible solutions, and I'm curious to hear more about your motivation. :)

Oops, saw your other issue first. In any case:
This is not something I had previously considered. Having truly custom backends feels a bit difficult, and would require a fairly substantial bit of work; I'm not necessarily opposed, but what would make more sense to me would be getting your backend merged into piet, and then allowing it to be selected via a feature flag.
This does of course have its own problems, particularly around maintenance; it would involve adding a new backend to piet-common, and that means we would need to ensure it continues to compile.
The other issue is that the piet backend is fairly tightly integrated into druid-shell in a way that does not abstract easily. That is: the mechanism for creating a RenderContext varies between platforms and backends, and I think it would be difficult to have an abstraction for that; at the very least i think you will need to have some conditional compilation at the point where you are setting up your backend.
In any case I'm happy to answer questions and talk through possible solutions, and I'm curious to hear more about your motivation. :)

Skia is something that is required for the project I'm working on but I'm not sure about the general case.
About my motivation:
I'm developing GUI for embedded devices and also I have requirements to use Skia.
I also want to have my own druid-shell platform (with DRM/KMS). Hence I only need part of the functionality of druid -- mb from my perspective perfect situation is not using piet and druid-shell at all because it's a place where I need to have more fine-grained control myself.
Druid use case for me is having generic GUI widgets (layout stuff for example -- like scrolling, flexbox etc.) and handy GUI architecture.
I've implemented my own mock platform inside druid-shell which supports Skia and I wonder if that could be something that I can do from outside of the druid without forking it -- by providing some trait(s) implementation for example.
It looks like if I add trait(s) which all platforms will implement it'll be possible to create some API that uses this trait instead of relying only on the features when selecting platform. (I'm guessing here).
It will solve the issue of forking druid for me. I'll implement my custom backend in my crate and will have control of it in my repository, rather then specifying some fork from actual GUI code.
The only problem is that piet-common is still specified in druid-shell Cargo.toml and even exposes itself with put use. Looks like fixing that is only possible by implementing skia backend for piet.
Having a fork wich solves my problems is something that I'm trying to avoid here, but if so -- how much effort would it be to keep it upstream given that I'm only changing few lines of code and only add separate code? How often internal API change?
Here is my current code for druid-shell https://github.com/pum-purum-pum-pum/druid/tree/skia_druid/druid-shell/src/platform/skia (it's WIP and uses winit. I'll need to write DRM/KMS backend in the future)

Skia is something that is required for the project I'm working on but I'm not sure about the general case.
About my motivation:
I'm developing GUI for embedded devices and also I have requirements to use Skia.
I also want to have my own druid-shell platform (with DRM/KMS). Hence I only need part of the functionality of druid -- mb from my perspective perfect situation is not using piet and druid-shell at all because it's a place where I need to have more fine-grained control myself.
Druid use case for me is having generic GUI widgets (layout stuff for example -- like scrolling, flexbox etc.) and handy GUI architecture.
I've implemented my own mock platform inside druid-shell which supports Skia and I wonder if that could be something that I can do from outside of the druid without forking it -- by providing some trait(s) implementation for example.
It looks like if I add trait(s) which all platforms will implement it'll be possible to create some API that uses this trait instead of relying only on the features when selecting platform. (I'm guessing here).
It will solve the issue of forking druid for me. I'll implement my custom backend in my crate and will have control of it in my repository, rather then specifying some fork from actual GUI code.
The only problem is that piet-common is still specified in druid-shell Cargo.toml and even exposes itself with put use. Looks like fixing that is only possible by implementing skia backend for piet.
Having a fork wich solves my problems is something that I'm trying to avoid here, but if so -- how much effort would it be to keep it upstream given that I'm only changing few lines of code and only add separate code? How often internal API change?
Here is my current code for druid-shell https://github.com/pum-purum-pum-pum/druid/tree/skia_druid/druid-shell/src/platform/skia (it's WIP and uses winit. I'll need to write DRM/KMS backend in the future)

I think embedded devices are a really interesting use-case for druid, and I would be happy to try and support that. I would definitely be open to adding a new druid-shell backend that targets some set of embedded devices, and I'm also open to adding piet-skia.
I'm less sure about whether or not we can express the current set of relationships well as traits. It's possible, and you'r welcome to experiment, but there's a lot of tricky bits. One problem is that we would have to make all of the druid code generic over the various types of the particular piet backend, and there are a lot of those types.
The alternative that we have discussed is using dyn Trait for the various piet types. The main concern with this is that if you have two piet backends in use at the same time, you have the possibility of type mismatches; for instance if you're in a druid app that uses piet-skia but you also want to generate an svg with piet-svg, you end up with multiple incompatible dyn RenderContext types floating around.
I don't think this is a huge issue, but it's something to be aware of. In any case, if we want to go with traits, I think we will want a solution like this.

I think embedded devices are a really interesting use-case for druid, and I would be happy to try and support that. I would definitely be open to adding a new druid-shell backend that targets some set of embedded devices, and I'm also open to adding piet-skia.
I'm less sure about whether or not we can express the current set of relationships well as traits. It's possible, and you'r welcome to experiment, but there's a lot of tricky bits. One problem is that we would have to make all of the druid code generic over the various types of the particular piet backend, and there are a lot of those types.
The alternative that we have discussed is using dyn Trait for the various piet types. The main concern with this is that if you have two piet backends in use at the same time, you have the possibility of type mismatches; for instance if you're in a druid app that uses piet-skia but you also want to generate an svg with piet-svg, you end up with multiple incompatible dyn RenderContext types floating around.
I don't think this is a huge issue, but it's something to be aware of. In any case, if we want to go with traits, I think we will want a solution like this.

Thanks for providing useful context. I'll try to experiment with it and will reply here later.

Thanks for providing useful context. I'll try to experiment with it and will reply here later.

I see now. I tried doing it and I have for example pub struct WindowHandle<T: WindowHandlePlatform>(T) which spoils ContextState in druid and hence every context we have (by requiring template parameter in type).
Using dyn Trait can solve this indeed. That is what I'll try to do next unless there are some other options.
The only problem I see is that it changes the druid's behavior -- it will dynamically dispatch backend functions, but I doubt that it could cause any performance issues.

I see now. I tried doing it and I have for example pub struct WindowHandle<T: WindowHandlePlatform>(T) which spoils ContextState in druid and hence every context we have (by requiring template parameter in type).
Using dyn Trait can solve this indeed. That is what I'll try to do next unless there are some other options.
The only problem I see is that it changes the druid's behavior -- it will dynamically dispatch backend functions, but I doubt that it could cause any performance issues.

Tried dyn trait and there are problems with this approach too. For example Custom Cursor is not a trait and hence cannot be expressed without some template parameter. Unless we'll invent some trait for all Custom cursors.

Tried dyn trait and there are problems with this approach too. For example Custom Cursor is not a trait and hence cannot be expressed without some template parameter. Unless we'll invent some trait for all Custom cursors.

However, if it's fine having Pain/Layout/Update.../Ctx depending on some T: WindowHandlePlatrom trait I can continue my investigation. What do you think?

However, if it's fine having Pain/Layout/Update.../Ctx depending on some T: WindowHandlePlatrom trait I can continue my investigation. What do you think?

I'm also interested in something like this.
To give a bit of context: I work in the automotive industry and would like to write some services in Rust (instead of C++). For the backend part, this is already starting to pay off. Now I'd like to rewrite some frontend parts (mostly camera data visualization and vehicle data plotting) in Rust as well. So far, I've found iced and druid are the only two frameworks I like. To be honest, I prefer the research based approach of druid.
However, software rendering is a no go - we often have data that has to be refreshed at 30 or even 60 Hz (multiple realtime camera image streams). Having a Skia piet backend should make druid run with GPU acceleration. Now my specific use-case may require a bit more work: I have multiple Image widgets that refresh at 30 or 60 Hz. Hardware accelerated drawing for those widgets alone could probably save most the CPU cycles I need to waste right now. But AFAIK surface integration (e.g. through wgpu) with druid is not possible right now. Otherwise I could probably come up with my own Image class which internally manages a Vulkan/OpenGL texture surface.
If dynamically adding a skia backend to druid by means of traits etc. is not possible, would you be willing to add it under a feature flag so it can be chosen at compile time, @pum-purum-pum-pum?

@pum-purum-pum-pum I guess I missed a notification on this. I'm not sure how much help I can offer; you're dealing with problems we haven't really encountered yet, and I'm reluctant to introduce major architectural changes right now. At some point in the medium-term we're going to be doing a bunch of architectural work, exploring splitting druid itself into two parts; and perhaps something we can consider, during this work, is a way to more clearly isolate the backend.
@raymanfx video is definitely something we'd love to have, but doing it right is definitely a research project, and it isn't blocking any of our current work. I would be happy to see a skia backend in piet, and that should not be a crazy amount of work.

@cmyr Sorry for hijacking this issue once more - do you have some things on your mind regarding video, perhaps a roadmap or feature backlog? I am currently building a cross-platform camera app using Druid that I am almost ready to show off as a first MVP. Still spending much time on the backend crate, https://github.com/raymanfx/eye-rs. Right now I'm just using an async image widget and a delegate that sends captured frames to it.
Maybe we should open a tracking issue for video stuff? I'm willing to help out and tackle some of the pain points I encountered when working with Druid (not too many, I was pleasantly surprised!).

@raymanfx the problem with video is that it is highly platform dependent. I don't have very much experience with this, but I know that generally you'll want to use some platform API to create a 'video view' and then you provide it with some media and control playback via some proxy object or similar. This is not a great fit for how druid works currently, where we just have a single view on the platform that we control; figuring how (for instance) to get our layout system to work with additional views would be a project.
On a long enough time-scale, we would like to move to a world where we are using a single gpu-backed graphics implementation for all of our drawing across all platforms; in that world we might prefer to take a more ground-up approach and come up with our video playback implementation, but I get serious "here be dragons" vibes about that whole idea; it's certainly not something I've ever gotten near in the past.
So: I would be happy to have a tracking issue for video, but realistically it's not going to be an immediate concern for quite a while. 😢


Error on starting driver

When i try to start the driver with the following code, i get what it seems to be a json decoder erro with this message: Expecting value: line 1 column 1 (char 0)
But selenium still launches, but the application crashes
code:
driver = ""
while driver == "":
    try:
        driver = WhatsAPIDriver(profile="./bot", username="bot", client="remote", command_executor=url_remoto_selenium, loadstyles=False)
    except Exception as e:
        print("Erro whatsdriver (Selenium possivelmente fechado): " + str(e))
        time.sleep(3)

any suggestions on how to fix this error?

It seems to happen only when saving the session without loggin in

it happens because as i mentioned on my other issue, is_logged_in does not work properly, at least the pip version, and i cant properly verify if it logged in or not before saving.
although, even if the session was saved without a login, this exception on load should be handled automatically with a warning (at least i think).

pip version is deprecated, please clone it directly from the repo


Fix the tab order on the "TRANSACTION" screen.

Actual:

Design:
https://app.zeplin.io/project/5c73dc8aa74b4b4085a86a91/screen/5d3d3d4dee97ad0d5a608c8f

Please increase the backlight length (left to the edge of the screen) for "ALL" tab.

Also, please increase the backlight length (right to the edge of the screen) for "RECEIVED" tab.

checked


Lisa's Workbook problem:C# solution

Added a new solution for Lisa's Workbook problem using C# programming language.

After reviewing the problem and looking over a few different solutions to the problem. It seems that O(n) is a perfectly fine time complexity for this problem. However, it is worth noting that all variables for this question have the same bound thus 100n is essentially n^2. However, do to the small input size and that the point of this problem is not necessarily time complexity, I would say just leave it at O(n)


Failed to build with GPU support

I tried to install caffe2 on ubuntu 14.04 with GTX 1080, CUDA 8.0 and cudnn v5.1
I was able to install caffe2 without errors, but when I check the GPU support using the code,
python -m caffe2.python.operator_test.relu_op_test
I got the following error.
Trying example: test_relu(self=<__main__.TestRelu testMethod=test_relu>, X=array([[-0.69068319, -0.50535285,  0.5229643 ,  0.81560022, -0.13703787],
       [-0.58238041,  0.        ,  0.17173739,  0.25081563,  0.52810317],
       [-0.68730897,  0.67287093,  0.55590409,  0.33867693,  0.01338956],
       [ 0.        , -0.24728367,  1.        , -0.         Can you post the summary that's printed after CMake runs?

Closing due to inactivity.


(#3365) Fix typo in documentation of NuGetAdd alias

resolves #3365

@yschmid-levi your changes have been merged, thanks for your contribution :+1:


data: project addition by vishnu-mouli-102408

Add a new project to the list
I want to add a new project to the list
Code of Conduct

[X] I agree to follow this project's Code of Conduct

assigned to you @vishnu-mouli-102408

Completed. Thanks for your contributions 🎉 ❤


DROOLS-733 - Extended tests to support Oracle database

tested Oracle database has some differences compared to H2 used in tests:

returns null instead of empty String for values which weren't set
returns results in random order - tests modified for attachments and comments , will prepare another PR for other sorting issues
Adjusted timeouts as they were too short for remote database

@sutaakar please update this PR with other sorting issues so I'll merge all at the same time. thanks

Updated.
Added sorting according to ProcessInstanceId for runtime data.


Change to using sobek instead of goja

We are moving to a fork of goja under grafana org called sobek.
More info in:

https://github.com/grafana/k6/issues/3772
https://github.com/grafana/k6/issues/3773

@mstoykov
Thank you for your great contribution, and so sorry for my belated response.
Let me have time to check this 🙏

this PR was opened with a script against every extension in the k6 docs. As this is an output the move to Sobek isn't really a requirement so I am going to close this.


Tiles export at wrong start position when using yarn b18

Currently, when the yarn b18 command is used, tiles seem to come out offset from where they should be.
See tile trays in gamebox here: https://b17.kanga.nu/board18Map.php?dogame=532
I've tinkered around with the settings, and it seems if you set the json in the b18output to have these settings, the tiles position correctly:
  "xStart": 24,
  "yStart": 24,

cause not investigated, but fixed by 09f76106b958eeac91b5132a6a710b5e8e912d43


Bars in the bar chart can overlay smaller bars

If the user cooses an unfortunate constellation of countries there is a chance that the bigger bars of a country with high numbers will overlay the smaller countries' bars.

This error was resolved

This error was resolved


Let StorageDoubleMap use borrowed key types

Closes #1566

@holygits just waiting for it to be resolved...

Hmm, I get lots of errors like the following:
the trait `_IMPL_DECODE_FOR_RawEvent::_parity_codec::Decode` is not implemented for `[u8]`

I think the encode trait for this would just call .to_vec() anyway
https://github.com/paritytech/parity-codec/blob/50ea4fc9c74a426720ff62ed166c9ced485cac89/src/codec.rs#L135-L140
I'm not sure what the best path forward is here

Ok; probably not sensible to try to solve in this PR.


openMM snapshot.masses fails for snapshots with TopologyEngine and virtual sites

Stumbled across this running with TIP4P and random velocities :)
To reproduce load any pdb/trajectory with TIP4P and access the masses or masses_per_mole attributes of the snapshots. I attached a pdb with TIP4P waters (as txt because github doesnt like pdb). LiCl_solv_tip4pew.txt
import openpathsampling.engines.openmm as peng_omm
template = peng_omm.snapshot_from_pdb('LiCl_solv_tip4pew.pdb')
template.masses  # this will fail

The issue here is that in masses.py if the snapshot engine has no attached simulation we do the following to get the masses:
ops_topology = snapshot.topology
topology = ops_topology.mdtraj.to_openmm()
masses_per_mole = [a.element.mass for a in topology.atoms()]

Which fails for virtual sites because they have None as element in the openmm-topology.
Opening this issue because I am not sure what the best way to address this properly would be and I already found a quick and dirty fix. To work around it temporarily one can (re)set the engine to a OpenMMEngine with an attached simulation object to take the different code path in  masses.py.
Concerning possible solutions: In mdtraj the virtual sites do have an element ("VS") with a mass of zero, the None element is only in the openmm topology. I guess we are converting to openmm topology before getting the masses to make sure we have exactly the mass the engine uses, so I am not sure if using the mdtraj elements and masses (i.e. without the conversion) would be an option. And I am not sure if there are other situations in which an openmm topology returns None for the atom element, so I am not sure if something like mass=0 if a.element is None would be an option.
[Edit: typos]

@hejung, can this issue be closed after the merging of #1085 ?

@sroet yes! sorry for not doing that myself.


Getting node element and next nodes in move_node.jstree event

I want to get next nodes (previous and next) after move by drag and drop ended.
I can't find it here, so I decided to use jQuery for retrieving them:
var $node = $('#' + target.node.id);
var prevPk = node.prev('li').attr('id');
var nextPk = node.next('li').attr('id');

Two problems:

Is there any better way to get $node and next nodes?
When moving inside one parent node this solution works, but when moving to other node prevPk and nextPk are from old parent.

I found _previousSibling and _nextSibling in the docs, but these methods are private.

Overlooked it, sorry.


Multiple votes accumulated on one person

See https://github.com/OpenSlides/OpenSlides/pull/6376

I changed all the discussed aspects.
One note: I reduced the size of the input fields but made them not as small as the thumb-up/down buttons because otherwise, the error messages would stack too much.

I went through the change requests and resolved them accordingly.
Apart from that, I am not sure how I can resolve the error of the prettifying checker. It seems to me that the error messages don't provide any valuable information.

I went through the change requests and resolved them accordingly.
Apart from that, I am not sure how I can resolve the error of the prettifying checker. It seems to me that the error messages don't provide any valuable information.

You can do the following:

Either run npm run cleanup inside the client folder. This runs the lint-checker, first, and then a prettifier.
Or you execute npm run prettify-write. This just runs the prettifier.

Ready for merge.

Your changes looks good! I prefere a new config to enable/disable this feature because the majority of users does not use this multibe votes feature. Maybe you can help us to do this config option in a new PR? - But we will merge this PR first. Just to note for your next PR: translations are not required in feature PRs. We updated all open translations later in a new PR.

That sounds like a good idea! I would be up for that. :-)


Site icon as image & Assignment list

Two snippets
Site icon displays the focussed site's icon as an image
Assignment list returns the current open assignments for a student in a table, without them having to open the assignments app

Formatting is a little chaotic... Couple of Coding conventions that need covering off... Not a million miles from being ready.
Actions required:

[ ] Neaten code to follow FrogOS Style Guide (Airbnb JS Style Guide)
[ ] Convert Date manipulation to use moment.js (Documentation in DevDocs
[ ] Consider changing assignmentpupils.getassigned to newer endpoint.
[ ] Consider creating HTML content either via use of Template element OR incremental jQuery creation.