Error after reload vimrc

I copy this line from doc to my vimrc:
let g:Lf_StlSeparator = { 'left': "\ue0b1", 'right': "\ue0b2"}

The font field is missing, which should be
let g:Lf_StlSeparator = { 'left': "\ue0b1", 'right': "\ue0b2", 'font': ''}

LeaderF works well until :source ~/.vim/vimrc. When I invoke a LeaderF command, :messages gives following output:
Messages maintainer: Bram Moolenaar<EMAIL_ADDRESS>"~/.vim/vimrc" 945L, 29485C
Error detected while processing function leaderf#Mru#startExpl[2]..leaderf#LfPy:
line    1:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/benyip/.vim/bundle/LeaderF/autoload/leaderf/python/leaderf/manager.py", line 731, in startExplorer
    self._getInstance().enterBuffer(win_pos)
  File "/home/benyip/.vim/bundle/LeaderF/autoload/leaderf/python/leaderf/manager.py", line 225, in _getInstance
    self._afterExit)
  File "/home/benyip/.vim/bundle/LeaderF/autoload/leaderf/python/leaderf/instance.py", line 40, in __init__
    self._highlightStl()
  File "/home/benyip/.vim/bundle/LeaderF/autoload/leaderf/python/leaderf/instance.py", line 64, in _highlightStl
    lfCmd("call leaderf#colorscheme#highlight('{}')".format(self._category))
vim.error: Vim(if):E716: Key not present in Dictionary: font
Error detected while processing function leaderf#Mru#startExpl:
line    2:
E171: Missing :endif
1 more line

E474: Invalid argument

This seems like a regression, it didn't happen before. Should we update the doc?

Thanks for reporting, this issue seems the same as issue #129, I 'll try to fix it.

Fixed.


deploy failed

Hello, I got this when deploying your example, have any clue?
Serverless Error ----------------------------------------
An error occurred: HelloLambdaFunction - Properties validation failed for resource HelloLambdaFunction with message:
#/Environment/Variables: extraneous key [_] is not permitted.

Sorry about that. f67dfbfddc9915218566bdf6b1ff485b12c4048c should resolve this, and is in main.


Scenes Not Loading

What happened?

Scenes do not load while using desktop, tried at all resolutions and jumped to multiple locations with the same result.
//update//
Looks like decreasing the resolution, draw distance, and scene load distance has resolved. Internet connection must be too slow to load scenes correctly.
Steps to reproduce
Just jumping into the game as guest.
Operating System
Windows 10  (10.0.19043) 64bit
Wallet
None, played as guest
CPU
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
GPU
Intel(R) UHD Graphics 620 8135MB
RAM
16270MB
Kernel Version
1.0.0-1990570041.commit-c77c4c3
Unity Version
desktop-main.commit-cedda56
Realm
unicorn
NameTag
dude#a178

Likely a performance issue.

Is this still happening to you? the realm you are connected to can also affect the download speed of the assets

We've seen this happening with a DNS error that we don't know how to reproduce


Issue #296: Upgrades webpack to v2

Updated to webpack 3 in my previous commit, since that's the latest stable.

Another PR is in that solves this.


Cursor improvement

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I will add the js and CSS logic so that when the cursor moves into the navbar the color drop that moves with the cursor will vanish and it wil become only a cursor
Use Case
This will help us to clearly visualize which button we are clicking
Benefits
No response
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Hey @HimanshuNarware please assign me this issue


chore(client): remove unused match

This match isn't actually unused, it's matching an an uninhabitable type, making the entire branch unreachable. It helps with optimization.

Great, got it. Thanks

Great, got it. Thanks


fix logging bug: log statements outside pgcli.main not logged to file

file handler was attached to the pgcli.main logger instead of pgcli

Damn, that was quick. :)
I'll try it out. Thanks!

hah, i actually figured it out yesterday and then forgot about it until i
saw the issue
On Sat, Jan 10, 2015 at 7:45 PM, Amjith Ramanujam<EMAIL_ADDRESS>wrote:

Damn, that was quick. :)
I'll try it out. Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/amjith/pgcli/pull/103#issuecomment-69478698.

Thank you! Just tested it and works great.
Cheers! :bulb:


Document reason why the package is added as a dependency and not a devDependency

I'm surprised the "@simondotm/nx-firebase" package is installed as a dependency and not a devDependency.
Is there a reason for this? It could be useful to add the reason to the documentation?

Hi @LanderBeeuwsaert , thanks for the feedback.
You are correct, the documentation should recommend the plugin is installed as a devDependency. Good spot!


v2.2.2-RC3 Error Following User

Brief Description: Using v2.2.2-RC3 desktop bundle to control a remote server (v0.12.1-RC3). Trying to get that remote server to follow the local bundle server store. Causes the following error.
Operating System (OS and version): Windows 10 Home
OpenBazaar version (shown on About OpenBazaar page in menu):
Hardware: Intel i7, 16GB RAM
Reproducible (Always / Almost Always / Sometimes / Rarely / Couldn't Reproduce):
Steps to reproduce:

Open 2.2.2-RC3 bundle. Copy the URI of the local bundle-server store.
Use bundle client to log into a remote server running v0.12.1-RC3.
Paste URI of local bundle-server store to open that stores page.
Try to follow the store.

C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\jquery\dist\jque…:9600

GET http://<IP_ADDRESS>:4002/ob/listings/Qmd3aTpRpEuVFahXaeKga6GTF18Wg7sDtLiitGZvhkP953 404 (Not Found)

  | send | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\jquery\dist\jque…:9600
-- | -- | -- | --
  | ajax | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\jquery\dist\jque…:9206
  | Backbone.ajax | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\backbone\backbon…:1460
  | Backbone.sync | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\backbone\backbon…:1443
  | sync | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\backbone\backbon…:798
  | fetch | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\backbone\backbon…:1055
  | createStoreTabView | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\prod\views\userPage\UserPage.…:304
  | selectTab | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\prod\views\userPage\UserPage.…:361
  | setState | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\prod\views\userPage\UserPage.…:319
  | (anonymous) | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\prod\views\userPage\UserPage.…:423
  | sendBackTmpl | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\prod\utils\loadTemplate.js:54
  | loadTemplate | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\prod\utils\loadTemplate.js:73
  | render | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\prod\views\userPage\UserPage.…:386
  | (anonymous) | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\prod\router.js:568
  | fire | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\jquery\dist\jque…:3268
  | fireWith | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\jquery\dist\jque…:3398
  | (anonymous) | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\prod\lib\whenAll.jquery.js:28
  | fire | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\jquery\dist\jque…:3268
  | fireWith | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\jquery\dist\jque…:3398
  | done | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\jquery\dist\jque…:9305
  | (anonymous) | @ | C:\Users\Chris\AppData\Local\OpenBazaar2\app-2.2.2\resources\app.asar\node_modules\jquery\dist\jque…:9548

I notice the listings call on that node 404s, but I'm able to follow it normally.
This works: http://localhost:4002/ob/profile/Qmd3aTpRpEuVFahXaeKga6GTF18Wg7sDtLiitGZvhkP953
This 404s: http://localhost:4002/ob/listings/Qmd3aTpRpEuVFahXaeKga6GTF18Wg7sDtLiitGZvhkP953
{
    "success": false,
    "reason": "no link named 'listings.json' under zdj7Wk8u1MHpBZnEUusN9EFnioybrkYEfr7qBMcpKwq9ED8ZT"
}

It looks to me like there's something wrong with that node. How did you create it?

@cpacia @placer14 @tyler-smith can any of you think of something that would cause listings.json to be missing?

@christroutner Do you have any output from the server (or in the ob.log) from when you upgraded this installation? Looking for the Migrating to version 10 line in the logs for any errors following?

I will try to duplicate this issue in the latest release. This same server was causing odd BCH wallet behavior, and I believe the reason was due to out-of-memory issues.
I'll close this issue for now and reopen if I manage to reproduce the error after I've bumped the swap memory on the server.


FLib Throws NoClassDefFound error for IConditionSerializer

Minecraft Version: 1.21
Forge Version: 51.0.23
Mod Version: 1.20.1-0.0.14.jar
Single Player or Server: Server
Describe problem (what you were doing; what happened; what should have happened):
Installed Forge Server, Flib, and Creeperheal.
When trying to start the server, server fails to start due to missing class IConditionSerializer.
Removing FLlib and Creeperheal resolves issue and server starts normally.
 Thats what I get for putting in bug reports at 1am. Sorry about that.
Hope you update soon though I'd love to run creeperheal


Cleanup

[x] renamed heatmap generator
[x] aggregation time is a param
[x] add heatmap generator to launch
[x] add sim option in factory.launch
[ ] repo structure should be as per THMHO

@ipa-rar please test the launch with both options
with gazebo:
roslaunch factory_sim factory.launch sim:=true

with real laser scanners:
roslaunch factory_sim factory.launch sim:=false

tested for both sim and real scans


%E2%80%8B — spurious percent encoding in additional resources

Describe the issue
https://datatracker.ietf.org/doc/draft-ietf-emailcore-rfc5321bis/
has this as additional resource:
%E2%80%8Bhttps%3A//mailarchive.ietf.org/arch/browse/emailcore/
(see also other emailcore documents),
This looks like it has been mangled by some .NET software (or something else that inserts a zero-width space and then percent-encodes).
I don't know whether the additional resource was originally supplied this way, but even if, data tracker should not accept a resource that starts with a % character.  Possibly, the resource was mangled by some data tracker bug.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

In this case, it's not an entered DocExtResource, but a synthetic one computed at runtime (if a link to the list archive isn't already present). It computes a value based on a template using the group's configured list_archive value.
In this case the emailcore group has a list_archive value of '\u200bhttps://mailarchive.ietf.org/arch/browse/emailcore/'. Likely a paste error - nothing would have added a zero-width space in the code.
So there's an improvement to be made in validating those away, and a bug to fix in how it gets mangled on the way to being displayed.
But in the meantime, I've corrected the value in the database for the emailcore group.
p.s.
We've gone back and forth in the code/UI design on whether it makes the most sense to display this as an external resource or take the space to give it its own row. Past arguments for having it appear as an external resource have included making it obvious that a document can have external resources without having a majority of documents displaying a blank entry taking up space.


Death to Mr Incredible when "any" appears in TS

It would be epic if Mr Incredible's face teared down when an any is typed in a .ts or .d.ts file.

hello  @ezeamin , good idea, very similar to the one I told you this morning.


Possible bug in PhoneGap Android, but not iOS reported by user

This is related to the following:
http://blog.couchbase.com/using-couchbase-in-your-ionic-framework-application-part-1#comment-2557540255

Android 4.1.2. I'm deploying on device using ionic build android -> ionic run android.
However, if it helps, I ran it in ios emulator and it works.

A few others are reporting the same.

Hi @nraboy,
Could you please provide details of this issue?
Thanks!

The details were in the comments:

@pasin do you mind taking a look at this?

Just reviewed the blog comments.  Nothing new has been reported.  Posted a follow up response in the comments of the blog article.
Best,

The status code = 0 is weird. From the Router.java, I guessed that openDB() method returned status code = 0 however I couldn't see how that can happen.
https://github.com/couchbase/couchbase-lite-java-core/blob/release/1.2.0/src/main/java/com/couchbase/lite/router/Router.java#L389-L398

@nraboy it would be really helpful, if the user can provide the exception from the log cat. I guessed there should be one.


Don't use generic names that might clash

It looks like that mondrianModel method does not exist anymore. For that reason I close the pull request.

Indeed, this is now replaced with element graph model, where graph provides a separate "namespace" for extensions.


Implement chain-specific keyrings (closes #231, #111)

Moves from a single global keyring to chain-specific keyrings, where keys/signers can be potentially shared across chains if desired.
This enables true multitenancy for supporting multiple chains with a single KMS instance, and reloves lingering questions around the access control model, namely that each connection has an associated chain ID, and signing operations are isolated to that chain's keyring.

awesome. save a lot of money for us.


Display how long ago the release was made

We'll want to display how long ago the release was made on the project/release detail page. Probably we'll want to implement this in javascript?

@dstufft I also want to make sure that we are consistent in the way that we display dates across all pages.  So, something like "April 10th, 2015"??  I prefer to avoid "4/10/15" as a format, as (unless we enable internationalisation) this means 4th October here...
It would also be cool if we could do something similar to https://docs.djangoproject.com/en/dev/ref/contrib/humanize/#naturaltime

Right now all dates are displayed using a filter that does localization (though it only supports en-us right now I think). Anything that isn't "static" should be done via javascript (e.g. April 10th, 2015 is static, it's always going to be april 10th, 2015 but '6 months ago' is dynamic, in 6 more months it's going to be '12 months ago').
Whatever we do though, it should handle localization and translation.


Upgrade to Openlayers7

Breaking change
Upgrades ol package to version v7.x and sets proper peer dependency.
Also upgrades geostyler-openlayers-parser package to v4.0.0 to fix dependency resolving conflict.
The PR includes some post upgrade code adaptations as well as test and linting fixtures.
Please review @terrestris/devs

In order to release a semantically correct version by semantic-release-bot you have to rename (at least) a single commit starting with breaking AFAIK

A line in the description text starting with BREAKING CHANGE: is sufficient.
That is the standard behaviour: https://semantic-release.gitbook.io/semantic-release/

🔝 thx


sound works, but volume control does not (pavucontrol) xubuntu samsung chromebook 4

The sound works but the gui volume control does not

This is being tracked in #113


Error: Expr.chartAt is not a function

I updated wdio-cucumber-framework  to 2.0.0 when I execute my test I get the following message. I have current cucumber.js installed (4.1.0).
ERROR: expr.charAt is not a function
chrome
Type    at tokenize /node_modules/cucumber-tag-expressions/lib/tag_expression_parser.js:87:20)

What is your cucumber opts? Especially tags.
Please share with us.
On Sat, 31 Mar 2018, 14:14 James Halls<EMAIL_ADDRESS>wrote:

I updated wdio-cucumber-framework to 2.0.0 when I execute my test I get
the following message. I have current cucumber.js installed (4.1.0).
ERROR: expr.charAt is not a function
chrome
Type    at tokenize /node_modules/cucumber-tag-expressions/lib/tag_expression_parser.js:87:20)
[image: screen shot 2018-03-31 at 12 10 12]
https://user-images.githubusercontent.com/35871107/38162651-f09afbdc-34dc-11e8-8ab3-1d3daed87515.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/webdriverio/wdio-cucumber-framework/issues/107, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGNmZBkIvVee1SRmP5cAMw0DAC_4RKbFks5tj2UTgaJpZM4TCbYO
.

Thanks for your help @BorisOsipov
Happy Easter!
`cucumberOpts: {
require: [
'./features/step_definitions/HomePageStepDefs.js',
'./features/step_definitions/LoginPageStepDefs.js.js'
    ],
    backtrace: false,
    compiler: ['js:babel-core/register'],
    dryRun: false,
    failFast: false,
    format: ['pretty'],
    colors: true,
    snippets: true,
    source: true,
    strict: false,
    tags: ['@chasers', '@complete'],
    timeout: 280000,
    ignoreUndefinedDefinitions: true,
},`

tags should be a tag expression
try to change ['@chasers', '@complete'] to '@chasers and @complete'
Happy Easter!

Yep, this has updated with the cucumber update. We probably need to update the readme. Will create a separate issue for this.

Was an issue created to track this? I couldn't find it but maybe I missed it.

Can you let me know the status on this issue?

@devth @harishkalaiselvan there is no issue.
see my comment on https://github.com/webdriverio/wdio-cucumber-framework/issues/107#issuecomment-377694195


GH-114 increase coverage in gateway package

What
Coverage change for the gateway package to 90.1%
Extended unit test coverage and created test files for booth controllers.
No work on the integration right now.
Verification
Verification is straightforward - tests are passing on the PR and coe looks neat and covers all the cases it should - PR is verified.

/hold
This PR now will wait for #162 and #175 and they will change a lot about the Gateway package and tests would need to be done over again

/label tide/merge-method-squash
/unhold

At a skim, this looks OK to me - but it would be good to get another once-over from someone who's familiar with our tests generally as well @mikenairn @david-martin @philbrookes

/lgtm

/approved

/approve

resolved the merge conflict and moved things around a bit. The goal is to have the test package hold interface implementations and functions that could be reused in other packages. The package-specific helpers now reside at the bottom of the appropriate unit test. Added build flags.
The conversation remains about what exactly should be covered by unit and integration but this should be as close as we could get right now

/lgtm
/approve


How To Generate Myself NPZ File

Like This bark/assets/prompts/v2/zh_speaker_8.npz

take a look in this repo:
https://github.com/gitmylo/bark-voice-cloning-HuBERT-quantizer
but I've been testing for a while and it does not work correctly in suno-ai bark

You have to make sure you use a quantizer that matches the language of the voice you are trying to clone.


Update dependencies

Coverage remained the same at 48.532% when pulling 93b6891a5568b4573b8c618564f7cc46acdd837a on sepe81:update-dependencies into 070f16c1564fe79fcd3312741c2af2320ca9b3bd on apache:master.

LGTM 👍


Switch device structure to optional

What type of PR is this?
Add one of the following kinds:

enhancement/feature

What this PR does / why we need it:
Shift device structure cardinality to optional has the device identifier could be obtained from the 3-legs process.
Which issue(s) this PR fixes:

Fixes #173
Special notes for reviewers:
Changelog input
 release-note
- Device structure is now optional has the device identifier could be obtained from the 3-legs process.

Additional documentation
This section can be blank.
docs

@sachinvodafone @akoshunyadi @fernandopradocabrillo Gentle reminder for this one as is it a simple one.
As we're close to the finish line and there is few other topic to adress for these API like error code.
Thanks


UI Interaction appears broken in Unity 2017

NOTE: Any issue that does not follow the below template will be immediately closed and not re-opened until the template structure is adhered to.

Precheck
Done.
Environment

Source of VRTK (Unity Asset Store or Github)
Unity asset store
Version of VRTK (Unity Asset Store/Github release number) (Github master commit hash)
3.1.0
Version of Unity3D (e.g. Unity 5.4.4f1)
Unity 2017.10b1
Hardware used (e.g. Vive/Oculus)
Vive
SDK used (e.g. OpenVR/SteamVR/Oculus Utilities)
OpenVr

Steps to reproduce

New Unity project
Import latest steamVr (version 1.2.1)
Import VRTK (version 3.1.0)
Open scene 034_controls_interactingWithUnityUI
Run controller cursor over UI elements, pulling trigger frantically
matches anything

Expected behavior
Should change ray color. Trigger pulls when over a control should activate control.
Current behavior
Color only changes when the ray hits the floor. The controls in canvases do not get highlighted/ are not interactable.
Briefly describe what is actually happening
Breakpoint debugging reveals that the raycast in CheckRaycasts of VRTK_VRInputModules never

closed - didn't realize this is already fixed in the github version


Comparing django with fastapi ?

Hi,
I have worked in Django and I really loved it but then i got to know it doesn't support asynchronosim natively and i was introduced to FastAPI. Can FastAPI do everything Django does ? like creating web applications (not just API) and what are the technical differences between the two ? I maybe giving a presentation where I wanna include a section of why choose FastAPI over Django or similar old frameworks.

https://fastapi.tiangolo.com/alternatives/
https://ahmed-nafies.medium.com/why-did-we-choose-fast-api-over-flask-and-django-for-our-restful-micro-services-77589534c036
https://medium.com/datadriveninvestor/is-fastapi-going-to-replace-django-87441de76383
https://dev.to/fuadrafid/fastapi-the-good-the-bad-and-the-ugly-20ob
https://www.quora.com/How-does-FastAPI-compare-to-Django-for-backend-web-development-with-Python

Google is a thing.

FastAPI is intended for APIs first. For the website portion of a web service, you would be better off with Django and Flask. That isn't to say you can't have Django or Flask make calls to the APIs you build with FastAPI, even run them in the same WSGI/ASGI web server.
However the benefit of using FastAPI for the data access/api calls behind a website is that it can be absurdly simple to write, and fast for end users.
If your question is answered, can you please close the issue?

The answer depends on what are you trying to achieve.
With FastAPI, yes you can do everything that you can do in Django, since FastAPI is a micro-framework, the solution could be different because Django is a high-level web framework and offers so many things out of the box.
But that does not mean you can not do them with FastAPI, in the end, all of these frameworks stand on layer 7 right? So why not?
Yes, you can create web applications, and as your project grows you probably could concern about reliability and scalability, in that point you can considering moving from MVC to Microservices, and FastAPI does it so well.

Since this is a micro-framework, you can create applications with minimal effort.
OpenAPI and Swagger integration is absolute.
FastAPI is faster, a lot.

Here are the benchmarks from TechEmpower

Test Type
Django
FastAPI
Summary

JSON Serialization
72.039
170,128
In this test, each response is a JSON serialization of a freshly-instantiated object that maps the key message to the value Hello, World!

Single Query
19,264
66,185
In this test, each request is processed by fetching a single row from a simple database table. That row is then serialized as a JSON response.

Multiple Queries
1,491
13,022
In this test, each request is processed by fetching multiple rows from a simple database table and serializing these rows as a JSON response

Fortunes
14,699
51,981
In this test, the framework's ORM is used to fetch all rows from a database table containing an unknown number of Unix fortune cookie messages (the table has 12 rows, but the code cannot have foreknowledge of the table's size).

Data Updates
568
5,909
This test exercises database writes. Each request is processed by fetching multiple rows from a simple database table, converting the rows to in-memory objects, modifying one attribute of each object in memory, updating each associated row in the database individually, and then serializing the list of objects as a JSON response.

Plaintext
78.132
159,381
In this test, the framework responds with the simplest of responses: a "Hello, World" message rendered as plain text

Thanks for the help here everyone! :clap: :bow:
Thanks for reporting back and closing the issue :+1:
You can probably do everything you do with Django in FastAPI with some details:

You would use an ORM instead of Django's, you can choose it. For example SQLAlchemy.
You would probably use Jinja2 as the template engine instead of Django's.
There is no equivalent of Django-admin, as that depends on the ORM. But you could use Flask-admin with the same SQLAlchemy models and mount it as a WSGI app. I think this is the weakest point in FastAPI. Also, improving it is one of my future planned projects.

For the rest, and especially for the API stuff, FastAPI should be enough. I'm not sure if there's anything else Django can do that FastAPI can't do in some way.

Also, you can use Django alongside FastAPI. Even Django's ORM inside of FastAPI. It's a weird experiment, but some people have done that.


Clear grep options

Clear the environment variable GREP_OPTIONS to avoid incorrect results with grep and to potentially increase performance.

Thank you, I didn't know about GREP_OPTIONS. But a quick googling showed me that the option was deprecated two years ago and the use of it is now heavily discouraged, so I'll just assume that it is no longer used and ignore that it can interfere with our script, because I don't want to sprinkle GREP_OPTIONS='' all over the place. I've already gotten tired of repeating command grep or \grep and GREP_OPTIONS='' command grep just feels too much :)


Feature/orm convert method

@JuergenGleiss Please make a new PR without old commits that have been merged into drogon.  Thanks

sorry, I'll forgot git push


Get user snapshots dataframe

Upgrade indico-client 4.9.0 > 5.0.1

Created Usermetrics class

Function to write user metrics to disk

Importing UserMetrics

Test - Added tests for user metrics

Example - Added an example of storing user metrics df and writing to …

Hey- checkout the version of "black" that is in main, build is failing because of:
Run black indico_toolkit Traceback (most recent call last):   File "/opt/hostedtoolcache/Python/3.7.[12](https://github.com/IndicoDataSolutions/Indico-Solutions-Toolkit/runs/6017779550?check_suite_focus=true#step:5:12)/x64/bin/black", line 8, in <module>     sys.exit(patched_main())   File "/opt/hostedtoolcache/Python/3.7.12/x64/lib/python3.7/site-packages/black/__init__.py", line 6985, in patched_main     patch_click()   File "/opt/hostedtoolcache/Python/3.7.12/x64/lib/python3.7/site-packages/black/__init__.py", line 6974, in patch_click     from click import _unicodefun  # type: ignore ImportError: cannot import name '_unicodefun' from 'click' (/opt/hostedtoolcache/Python/3.7.12/x64/lib/python3.7/site-packages/click/__init__.py)

@andrew8bit  if you resolve something, you should make a note of the change you made and click "resolve"

@andrew8bit should we keep this? I'd test and see if it still works, otherwise can close


The function OverrideFont can't find some fonts installed in OS

I have installed some fonts and want to use it,but when I tried to use it,it tolds me:
The specified override font is not available.
and give me a long list,which have some fonts installed on my computer——but not all.
I have thought it only supported for the fonts which has installed at the system install.but I find a font named TeamViewer15,it's not a pre - installed font——Actually it was installed by Teamviewer.So I think whether this function need fonts have some special fix?Or it's a bug...?
"This font can be use,and I don't know why"

"This is the list,and I don't know why many fonts can't display"

To be honest I don't know the answer to this. The API used to obtain these fonts is called Font.GetOSInstalledFontNames(), which is a part of Unity.
I have no idea which fonts qualifies to be returned from this API. The unity documentation states that the supported font formats are .otf and .ttf (old docs). But this is during design time in the editor.
If your font is in this format and it still doesn't show up, then I have no idea.

I use a monitor software and find  why. The  Font.GetOSInstalledFontNames()  tried to read the fonts that included in C:\Windows\Fonts . But in WIN10(Or my computer?),The font that you tried to install will put in this folder:
C:\Users\Administrator\AppData\Local\Microsoft\Windows\Fonts
And that's why the game cannot find the fonts. Seems it is hard to change that... there don't have any way to change the method and allowed it to read another location...

Can't say I know much about how fonts are installed. Perhaps you can simply drag your font file into the C:\Windows\Fonts folder? That's how I've installed fonts in the past.

I tried,but it also put it in C:\Users\Administrator\AppData\Local\Microsoft\Windows\Fonts.but I find how to fix(?) it.
1.Use WinHex to open UnityPlayer.dll (Which can change Hexadecimal) and search "466f6e7473"(Mean Fonts),then change the Fonts to others like Donts, and put fonts in this folder.
2.Use WinRAR or other tools and set the unzip location to C:\Windows\Fonts,It will successfully put the fonts in this folder.
(I think it must need Administrator to do that)
The fonts name seems must only English letters/numbers.
Thank you for answer me, or I'll never know how to fix it.

Fix Way:when you install font,choose install for all user.

I assume this issue has been solved. Feel free to re-open if not.


Adjusted the serializer's fields variable names  to sync with the FE ( Comment section)

Multiple files affected. Majority are frontend files


fix: remove prod call for state pull

Description

fix: remove prod call for state pull

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[ ] Roll Forward
[x] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.69.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


hw/bus/drivers/spi_da1469x: Allow for 16-bit spi dma transfers

The previous da1469x spi driver only allowed for 8-bit DMA transfers as the current spi config code does not support 16-bit transfers. However, there may be a need for this so added code to check to see if the word size is 16-bits and, if so, do 16-bit transfers. Note that no other configurations are expected currently and it is assumed if the spi word size is not 8-bit it is 16-bit.
Note that I think the hal spi and the da1469x code should be updated with the ability to do 16-bit spi but that change is a bit more intensive so just wanted to do this for now.

something is odd here. Closing PR.


frontend: injections created with the new editor don't work in legacy-content

See https://de.serlo-staging.dev/mathe, the first exercise was created with the new editor. You can't select any of the answers, though.
Btw: might also be a problem in the legacy-editor-renderer, not sure.

Probably related to nextjs is not hydrating injections


CAPA / CAPI support and documentation questions

Hello! 👋
Getting right to it there is this doc: https://github.com/aws/karpenter/blob/main/designs/aws-launch-templates-options.md#capi-integration
This says that CAPI integration is discussed in a different doc. Can someone please point me to that doc? :) That would be awesome.
I'm trying to get integration with CAPA started with Karpenter and I was wondering what elements/objects/components CAPA could/should/shouldn't manage with Karpenter. Any help is much appreciated. Cheers!

we are working towards a cluster api enhancment (CAEP) from the capi karpenter feature group, perhaps we should update the doc to point users to the feature group's work?

i'm happy to allow this to close or keep it open for tracking, whatever folks prefer.
for anyone who is curious about the karpenter provider cluster-api, please come visit the cluster api karpenter feature group.

I am super interested to know where this goes, as it would be a blocker for folks who have already adopted Karpenter on AWS and now also on Azure to switch to CAPA/CAPI for cluster management.

for now, the best way to follow the progress is to attend our feature group meetings, or review the agenda. i try to keep notes there, and we do record the meeting.


Verify status.loadBalancer when deploying a service of type LoadBalancer

What are you trying to accomplish with this PR?
Fixes part of https://github.com/Shopify/kubernetes-deploy/issues/543.
Make sure that we only declare a service of type LoadBalancer as deployed after its IP address is published (which is an asynchronous process in the case of most cloud providers).
According to the documentation:

The actual creation of the load balancer happens asynchronously, and information about the provisioned balancer is published in the Service’s .status.loadBalancer field

After being fully provisioned, this will show as something like this:
status:
  loadBalancer:
    ingress:
      - ip: <IP_ADDRESS>

How is this accomplished?
I added an extra condition that will only run if the type of the Service is LoadBalancer; if that's the case, it will check for the presence of status.loadBalancer.ingress.ip to determine if the Service has been fully provisioned.
What could go wrong?
It seems that testing this particular condition is not possible with minikube, as (specifically in that environment) the IP address is never published to the resource data and you need a special command to retrieve it.
Live test
$ kubernetes-deploy dirceu-test tierstaging-us-east1-2 --template-dir ~/Desktop
[INFO][2019-09-09 08:28:54 -0400]
[INFO][2019-09-09 08:28:54 -0400]	------------------------------------Phase 1: Initializing deploy------------------------------------
[INFO][2019-09-09 08:28:55 -0400]	Context tierstaging-us-east1-2 found
[INFO][2019-09-09 08:28:55 -0400]	Namespace dirceu-test found
[INFO][2019-09-09 08:28:55 -0400]	All required parameters and files are present
[INFO][2019-09-09 08:28:55 -0400]	Discovering resources:
[INFO][2019-09-09 08:28:56 -0400]	  - Service/test-lb
[INFO][2019-09-09 08:28:56 -0400]
[INFO][2019-09-09 08:28:56 -0400]	----------------------------Phase 2: Checking initial resource statuses-----------------------------
[INFO][2019-09-09 08:28:56 -0400]	Service/test-lb                                   Not found
[INFO][2019-09-09 08:28:56 -0400]
[INFO][2019-09-09 08:28:56 -0400]	----------------------------------Phase 3: Deploying all resources----------------------------------
[INFO][2019-09-09 08:28:56 -0400]	Deploying Service/test-lb (timeout: 420s)
[INFO][2019-09-09 08:29:30 -0400]	Still waiting for: Service/test-lb
[INFO][2019-09-09 08:30:00 -0400]	Still waiting for: Service/test-lb
[INFO][2019-09-09 08:30:30 -0400]	Still waiting for: Service/test-lb
[INFO][2019-09-09 08:30:54 -0400]	Successfully deployed in 118.0s: Service/test-lb
[INFO][2019-09-09 08:30:54 -0400]
[INFO][2019-09-09 08:30:54 -0400]	------------------------------------------Result: SUCCESS-------------------------------------------
[INFO][2019-09-09 08:30:54 -0400]	Pruned 1 resource and successfully deployed 1 resource
[INFO][2019-09-09 08:30:54 -0400]
[INFO][2019-09-09 08:30:54 -0400]	Successful resources
[INFO][2019-09-09 08:30:54 -0400]	Service/test-lb                                   Doesn't require any endpoints

$ kubectl --context tierstaging-us-east1-2 -n dirceu-test get service test-lb -o yaml
apiVersion: v1
kind: Service
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"Service","metadata":{"annotations":{},"labels":{"app":"test-lb","name":"test-lb"},"name":"test-lb","namespace":"dirceu-test"},"spec":{"ports":[{"name":"http","port":80,"targetPort":"http"}],"type":"LoadBalancer"}}
  creationTimestamp: "2019-09-09T12:28:57Z"
  labels:
    app: test-lb
    name: test-lb
  name: test-lb
  namespace: dirceu-test
  resourceVersion: "39073112"
  selfLink: /api/v1/namespaces/dirceu-test/services/test-lb
  uid: 64fe58ff-d2fd-11e9-8940-58010a8e017b
spec:
  clusterIP: <REDACTED>
  externalTrafficPolicy: Cluster
  ports:
  - name: http
    nodePort: 32731
    port: 80
    protocol: TCP
    targetPort: http
  sessionAffinity: None
  type: LoadBalancer
status:
  loadBalancer:
    ingress:
    - ip: <REDACTED>

You can merge this PR as is, but ❤ if you'd add an update to CHANGELOG.md with this enhancement. (We're trying to do this in each PR instead since doing them in the PR that bumps the gem version is a bit painful).


Implement GitHub comment commands to start Azure Pipelines CI builds

request build: windows triggers ITK.Windows build, etc.

Note: we can currently use
/azp run ITK.Linux

or
/AzurePipelines run ITK.Linux

to restart the Linux build, for example. Per:
https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops#trigger-builds-using-github-pull-request-comments

Still depending on GitHub Actions coming out of beta


de-DE: Replace ASCII apostrophes

This replaces ASCII apostrophes in the German translation with U+2019.
See also: https://github.com/OpenRCT2/Localisation/issues/2121

Object translations are now also maintained in the Localisation repository. For German, you need to modify this file: https://github.com/OpenRCT2/Localisation/blob/master/objects/de-DE.json

Object translations are now also maintained in the Localisation repository. For German, you need to modify this file: https://github.com/OpenRCT2/Localisation/blob/master/objects/de-DE.json


HTML

Sure, here is a simple HTML code that displays "HTML":
<!DOCTYPE html>

    <title>HTML</title>

HTML

This doesn't look like an issue.

Issue a change view comment here


It should be possible to commit even if there are error in eslint

Description
It should be possible to run linting commands without it aborting commiting (through configuration).   It puts projects in danger of losing changes because current work cannot be pushed to a private branch.  This way if someone drops their computer in a toilet, they do not lose their work.
Steps to reproduce
Add eslint --fix to your lint setup in package.json.  Commit, and notice that it fails
  "lint-staged": {
    "*.{js,jsx,ts,tsx}": [
      "prettier --write",
      "eslint --fix"
    ],
    "*.{html,css,less,scss}": [
      "prettier --write"
    ]
  },

You would expect to have configuration to make it not block the commit if a command fails or at least accept (eslint --fix) || true.  For whateve reason, this project is systematically blocking all approaches.
Debug Logs

expand to view
COPY THE DEBUG LOGS HERE

✔ Preparing...
⚠ Running tasks...
  ❯ Running tasks for *.{js,jsx,ts,tsx}
    ✖ prettier --write [FAILED]
    ◼ eslint --fix
  ❯ Running tasks for *.{html,css,less,scss}
    ✖ prettier --write [FAILED]
↓ Skipped because of errors from tasks. [SKIPPED]
✔ Reverting to original state because of errors...
✔ Cleaning up...

Environment
Linux.
"lint-staged": 11.2.3

I tried using the .lintstagedrc and it doesn't work either. The --shell option makes no difference.  I don't see any choice but to move to shell script to do what this command is doing.

@slalomzacharyd
Hi, perhaps i'm mistaken but judging by your logs you've presented the failure occurs in prettier not in eslint, my guess is that there was some exception thrown by prettier, or the wrapper trying to run prettier which in turn failed your process.

This kind of flag is outside the scope of lint-staged, because the entire point is to prevent committing in case of errors. You can try configuring ESLint/prettier to not error, or alternative commit with the --no-verify flag to skip git hooks (not recommended).
Feel free to re-open this issue if I understood something wrong.


Fix sticky header in diff view

Ressurection of #23549.
Fix regression https://github.com/go-gitea/gitea/pull/23513#issuecomment-1474356817 from #23271.
The previous sticky CSS did assume the content is always 2 rows, but since that PR, it's single-row above 993px width.
Adjust the sticky offset to match and add a small tweak that hides content behind the border-radius.
Single row:

Double row:

Left a bit of a mess with the PRs, but this is the one that is the bugfix and it would be nice to have it for 1.19.0 release ideally.

Moving to 1.19.0 milestone as this fixes a pretty important bug imho.

Yes, while it should be fixed before 1.19.0, it is probably still a good idea to let it target 1.20, so that it is correctly classified.

:trumpet: :robot:


Add a CHANGELOG file

Don't have a way to keep track of what's changing between versions right now. Need to fix that.

Done in a56ab82


Auto Focus

How can we add auto focus to surfaceview while Recording stream

#62 doesn't make any difference in camera preview.


Test code

@savvinsergey,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


[discussion] First steps on gesture integration using Hammer

Ongoing work to be discussed, don't merge! :)
Related to issue #107. Before I keep working on it, I would like to know your thoughts.
Here's a first attempt to integrate Hammer with Framer, so we can recognize pinches, rotations, panning, etc. From the few tests I've done it seems to work well together with the existing events. I have tried to make both gesture and browser events transparent for the final user, even if behind the scenes they are two completely different things.
I see this as an exercise to explore how gesture events could be handled in Framer. I went with Hammer because they already deal with a lot of corner cases and gives a good idea on how to solve the gesture recognition in an elegant way. But maybe in the future this dependency could be removed by implementing the functionality in Framer?
This is an overview on how Hammer implements classes / concepts:

Input: everything that can be consider a source of a gestural event. Subclasses: MouseInput, TouchInput, PointerEventInput, etc. This is also the class calculating velocities, directions and every extra info of the events.
Recognizer: The gestures themselves. Subclasses: PanRecognizer, PinchRecognizer, etc. The base class contains a state machine to follow the gesture evolution.
Manager: Assign handlers (or listeners) to recognizers based on a specific device input. It has similar responsibilities as Framer's EventManagerElement.

So what I've done for now is adding a GestureManager class that wraps Hammer functionality, and creates recognizers as they are requested depending on the gestures the layer is listening to.
Still to do:

Add the remaining events to the list (rotate, pan, etc)
Implement removeEventListener: this one is a bit tricky: after removing a listener, we should remove the given gesture recognizer if there are no more events remaining of that type attached to the layer.
Make complex examples: using ScrollComponent, PageComponent, sublayers, etc
Write tests (are there any existing tests that target events, listeners and handlers?)

Side note: if this PR finally see the light, it would be very nice to integrate this Touch Emulator into Framer Studio, so users could emulate multi touch gestures using their keyboard. That would bring Framer a step closer to the iPhone Simulator!! :)
Finally, a small example that you can copy & paste:
layerA = new Layer
	width: Screen.width
	height: Screen.height
	image: "http://lorempixel.com/900/900/"
# With draggable true some events are more difficult to trigger, but they work
layerA.draggable = false
initialScale = 0
layerA.on Events.PinchStart, (ev) ->
	# TODO layerA.origin =
	initialScale = layerA.scale
layerA.on Events.PinchEnd, (ev) ->
	if layerA.scale < 1
		layerA.animate
			properties:
				scale: 1
			curve: "spring(300, 40, 0)"
layerA.on Events.Pinch, (ev) ->
	layerA.scale = ev.scale*initialScale
	textLayer.html = "Zoom: " + layerA.scale.toFixed(1)
layerA.on Events.Press, (ev) ->
	textLayer.html = "Long press!"
	layerA.scale = ev.scale
layerA.on Events.SwipeRight, (ev) ->
	textLayer.html = "Swipe right!"
layerA.on Events.SwipeLeft, (ev) ->
	textLayer.html = "Swipe left!"
layerA.on Events.TouchStart, (ev) ->
	textLayer.html = "Touch start!"

textLayer = new Layer
	width: Screen.width
	height: 100
	html: "Zoom: 1.0"
textLayer.style =
	"font-size" : "50px"
	"line-height" : "100px"
	"font-weight" : "600"
	"text-align" : "center"

Ho Shit @jchavarri I totally missed this. This is awesome!

Thanks! :) Do you think this is the right approach to add other gestures to Framer? If yes, I would keep adding the remaining stuff on the todo list in order to finish this PR.

Yeah this looks really good. I'd love to finish this up and add it.

:+1:  I'll keep working on this branch and ping you in this thread once it's "ready for review".

Awesome!

@koenbok So I think this is ready for review! I didn't add any testing to it as I don't have any clue on how to test this kind of gestural interaction 😅. I saw that the HammerJS guys have created a "Simulator". Maybe we could add something like this to test it?
In order to test all the available gestures and events, I have created a Framer project. You can test it here, the code for this demo is on Github.
So the next things I'm interested in adding are:

Tests (somehow)
Using something similar to Touch Emulator to have double touch in the browser

Let me know your thoughts!  I think the implications for this pr are mostly renames.

👏🏻
On Sun, Nov 29, 2015 at 9:09 PM Koen Bok<EMAIL_ADDRESS>wrote:

Hey @jchavarri https://github.com/jchavarri I'm going to land a big one
first: https://github.com/koenbok/Framer/tree/context-freeze-restore
This will refactor a bunch of event and context stuff. I think the
implications for this pr are mostly renames.
—
Reply to this email directly or view it on GitHub
https://github.com/koenbok/Framer/pull/244#issuecomment-160516826.

Ok, cool! I'll keep an eye on the context-free-restore branch so I can merge with it once it's ready.

Jeu @jchavarri I'm ready with https://github.com/koenbok/Framer/tree/context-freeze-restore. Wanna give it a try?

Sure @koenbok, I will be more than happy to wrap this up! I think I can have something by tomorrow.
Side note: regarding the tests, I saw the HammerJS team uses both manual and unit tests:

Manual tests are basically webpages with a lot of features that allow them to quickly check if things are working as they're supposed to. I guess this is something similar to what I did in the framer-gestures.framer project.
Unit tests are done using a Simulator that can trigger complex gestures like pinch, etc.

Do you think adding any of these kinds of tests to this PR is worth it?

@jchavarri You're and utter legend. I can't wait for this to drop.

@jornvandijk Sorry, but I have to disagree :) you and @koenbok are the original rockstars that started all this top-notch-designed hyper-elegantly-coded prototyping madness! 😊 I am also eager to see what you and the awesome Framer community do with these new events...
So, everything has been merged and integrated with branch context-freeze-restore and the brand new DOMElementManager. I have tested as far as I could and everything seems to work. I wanted to share some points to know your thoughts:

I have created a new file LayerEventsTest.coffee where I copied all the previous events tests + some new gestures events tests. The reason is that the file LayerTest.coffee had around 1k lines and it seemed hard to read to me. I hope that's ok!
There's now these new "gesture events" object that are returned with every callback attached to a gesture event. I think these differences between "regular events" and "gesture events" callback objects should be reflected on the Framer docs, right? –the HammerJS docs can help to know which information is being passed to the gesture events callback objects–.
If you think it can help testing this feature, there's also the companion .framer project to test manually all the gesture events and different cases

I still have pending the addition of the HammerJS Simulator class -or something similar- in order to add more tests for the gesture events.
Let me know your thoughts!

Thanks for the kind words! Yeah, this is gonna be a substantial update to our docs. Will take some time to write it all out in an easy/understandable way.

Merged with master. Updated to add gesture event helpers (see PR #272 )

Hmpf, I can't update the branch :-/

It would also be great to have some Framer Studio projects with examples of common stuff.

@koenbok Access granted! :)
Related to the examples, can they be the same examples included in the framer-gestures.framer repo I set up? Or maybe they should be splitted into a separate .framer project each? If they need to be splitted into separate projects, it won't take long as each example is already in a separate file/module.
This is a capture of the main screen that points to the examples I created in that repo:

Woop yeah that's prefect.

Beng!

🚀

This is awesome, and I was really hoping this would happen someday!
I'm just starting to look at the examples … I like that these new events have all of HammerJS's ev object available during the event. I'm wondering, for consistency reasons, should this object be available for all other/regular events, like drag or click, as well?
Reason is, some of the things inside ev are really interesting, such as ev.direction or ev.angle or ev.distance — those can be extremly useful for drag events

That's a very good point. These are my thoughts on both observations:
1. Consistency
I think these are all the event types that can be passed to a listener on Framer atm:

TouchEvent: passed to listeners of regular DOM events on a mobile device
MouseEvent: passed to listeners of regular DOM events on a "non-touch" device. Even if you use on Events.TouchEnd or similar, a MouseEvent will be returned
Event aka "HammerEvent": passed to listeners of gesture events.

Hammer already takes care of these differences between TouchEvent, MouseEvent and PointerEvent by abstracting them into an Input class. Quoting from the site:

Input Events
Hammer maps all types of input (mousedown, mousemove, touchmove, pointercancel) to these contants.
| Name	           |     Value
INPUT_START	    1
INPUT_MOVE	    2
INPUT_END             4
INPUT_CANCEL	    8

Apparently there's a hammer.input secret event that is triggered for each of these constants, so maybe we can use all this to unify the events passed to the listeners.
NOTE: I'm afraid there will always be events like MouseWheel that won't be part of the unified event party, as they are very platform specific.
2. LayerDraggable
This one is simpler to tackle :) I think that just by replacing Events.TouchMove for Events.PanMove on the LayerDraggable class a HammerEvent object would be passed to the listeners.


Document building/distributing for openSUSE

Is your feature request related to a problem? Please describe
It looks like there's a community effort around openSUSE!
https://build.opensuse.org/package/users/security:logging/opensearch
Describe the solution you'd like
Add a section to https://github.com/opensearch-project/opensearch-build#making-a-release
Add to documentation and https://opensearch.org/artifacts/
Additional context
Coming from https://github.com/opensearch-project/opensearch-build/issues/27#issuecomment-1077989625

We have documentation on RPM: https://opensearch.org/docs/latest/install-and-configure/install-opensearch/rpm/. Closing this issue.


path_find has confusing error dstAmountMalformed (Version: 1.9.4)

Issue Description
The path_find command returns the error dstAmtMalformed when I add a send_max value to a request that otherwise works fine.
Steps to Reproduce
The following path_find returns a set of paths as expected:
{
    "id": "path_find_without_send_max",
    "command": "path_find",
    "subcommand": "create",
    "source_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59",
    "destination_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59",
    "destination_amount": {
        "value": "0.001",
        "currency": "USD",
        "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
    }
}

(WebSocket Tool Link))
But adding the a send_max field to it, which should be valid, causes the command to fail.
Request:
{
    "id": "path_find_with_send_max",
    "command": "path_find",
    "subcommand": "create",
    "source_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59",
    "destination_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59",
    "destination_amount": {
        "value": "0.001",
        "currency": "USD",
        "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
    },
    "send_max": "500000"
}

(WebSocket Tool Link)
Expected Result
The result should include only paths that spend up to the specified amount of whatever source currency was specified (in this case, XRP—which the successful path find result without send_max confirmed was a valid source currency!).
If there is an error, the error message should at least point at the correct field. It should not tell me that the destination_amount field is invalid if it's valid when I omit send_max.
Actual Result
The result is the following error:
{
  "error": "dstAmtMalformed",
  "error_code": 51,
  "error_message": "Destination amount/currency/issuer is malformed.",
  "id": "path_find_with_send_max",
  "request": {
    "command": "path_find",
    "destination_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59",
    "destination_amount": {
      "currency": "USD",
      "issuer": "rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B",
      "value": "0.001"
    },
    "id": "path_find_with_send_max",
    "send_max": "500000",
    "source_account": "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59",
    "subcommand": "create"
  },
  "status": "error",
  "type": "response"
}

Environment
Confirmed using the WebSocket tool connected to s1 and xrplcluster.

I believe the relevant check is at: https://github.com/XRPLF/rippled/blob/develop/src/ripple/app/paths/PathRequest.cpp#L177-L182
It is documented at https://xrpl.org/path_find.html#request-format in the descriptions for the destination_amount and send_max fields, though it isn't entirely clear that mixing them in this way is not allowed.

Hello - I'm a beginner that would like to work on this issue. Could you assign it to me please? @ximinez @intelliot

@scjundev please go ahead and work on this issue - and open a PR when ready.
There's no need to have the issue assigned to you, but I've gone ahead and done so anyway :)


Support disk.model hw requirement for mrack

Pull Request Checklist

[ ] implement the feature
[ ] write the documentation
[ ] extend the test coverage
[ ] update the specification
[ ] adjust plugin docstring
[ ] modify the json schema
[ ] mention the version
[ ] include a release note

@skycastlelily I'm not sure whether you are aware, but the specification for disk[].model does not exist yet. If you already work on that, feel free to ignore this note ;)

Yeah,I know, I was thinking to submit three merge requests in several minutes last night,but after I submitted this merge request, and  going  to paste this link and the artemis link to the disk.fmf, I found you already comment on the artemis one.It's pretty late,I was  a little sleepy,and failed to find a solution off  top of my mind which  fit both beaker users' need and openstack users' need, and my changing  "note:" to "note for size"   made tmt lint complaints,so I decided to go to sleep. Beaker disk don't have  model-name param, it's model typically is vendor-name + model-name, I do some magic,and I think it will make both beaker's users and openstack's users happy:)

Hi @dav-pascual ,would you please spare some time to review this tiny merge request?Thanks.

Looks good as far as my knowledge of tmt goes.
It also looks like there are two duplicate commits that can be squashed

Looks good, thanks! Could you please update the specification and mention this in the release notes as well?

Updated accordingly:)

Looks good as far as my knowledge of tmt goes.

Thanks for your review:)

It also looks like there are two duplicate commits that can be squashed

Yeah,now there are three,and they will become one when this MR merged to main.

updated:)
On Thu, Feb 29, 2024 at 10:33 PM Miloš Prchlík @.***>
wrote:

@.**** commented on this pull request.
In docs/releases.rst
https://github.com/teemtee/tmt/pull/2705#discussion_r1507685084:

@@ -8,7 +8,8 @@ tmt-1.32

The hardware specification for :ref:`/spec/hardware/disk` has been
-extended with the new ``model-name`` key.
+extended with the new ``model-name`` key. Users can provision beaker
+servers with a given model disk model using mrack plugin.

A couple of stylistic notes:

  - "Beaker" instead of "beaker",
  - "guests" instead of "servers",
  - "beaker" plugin instead of "mrack" plugin,
  - and we can reference to the plugin as well:

... using :ref:`/spec/plans/provision/beaker` plugin.

—
Reply to this email directly, view it on GitHub
<https://github.com/teemtee/tmt/pull/2705#pullrequestreview-1909049141>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKFR23BS2KX2NJTWP2E7LL3YV4543AVCNFSM6AAAAABDVHO7FCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSMBZGA2DSMJUGE>
.
You are receiving this because you were mentioned.Message ID:
<EMAIL_ADDRESS>

/packit test

Thanks: )
On Tue, Mar 5, 2024 at 4:11 AM Petr Šplíchal @.***>
wrote:

@.**** approved this pull request.
Thanks for the adjustments, now looks good, I just fixed a small typo in
a1f73a5
https://github.com/teemtee/tmt/commit/a1f73a5eca11a76dd783d3690760b73ea07bfb9c
.
—
Reply to this email directly, view it on GitHub
https://github.com/teemtee/tmt/pull/2705#pullrequestreview-1915251291,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKFR23EVCCZQ3GKX2H6YNJLYWTIO7AVCNFSM6AAAAABDVHO7FCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSMJVGI2TCMRZGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

/packit test


move some modules to the pkg dir

move some modules to the pkg dir

I think you can PR those modules one by one?


Add Apache 2.0 license preamble

This change adds the apache license preamble to source files fully and
partially owned.

Not needed - done elsewhere


Building for production

Are there any special build steps needed to use this lib in a production environment? Deploying a serverless Next.js app to Now yields this warning in prod, but only on the page that I include react-three-fiber

https://next-portfolio-lq04tz2oe.now.sh/particles

That would be quite odd. The lib doesn't contain React. See<EMAIL_ADDRESS>It just fetches react, react-dom, react-reconciler and scheduler, without any slashes or other aliases.

I've been scratching my head over this for a few days but I'll dig a little deeper, maybe it is related to Three or something else. Using a fairly vanilla webpack/next.js config

Would also be weirds if it's three, i see no reason for it to cause it. Maybe you can track the warning itself and debug it, see where it comes from and why it is thrown.

After a lot of digging, it turns out another lib was causing the issue, not using react/react-dom as peer deps


Improve CI

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@1fb718b). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             main      #1   +/-   ##
======================================
  Coverage        ?   0.00%
======================================
  Files           ?      10
  Lines           ?     163
  Branches        ?       0
======================================
  Hits            ?       0
  Misses          ?     163
  Partials        ?       0

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 1fb718b...19c5631. Read the comment docs.


Black screen with external display

When way-cooler is started with external display attached to notebook, screen flickers once and stays black.
Opening/closing notebook lid before start changes nothing, everything works fine without external display.
 INFO [way_cooler] src/main.rs:158 Logger initialized, setting wlc handlers.
 INFO [way_cooler] src/main.rs:163 DBUS_SESSION_BUS_ADDRESS: unix:path=/run/user/1000/bus
 INFO [way_cooler] src/main.rs:163 HOME: /home/wcm
 INFO [way_cooler] src/main.rs:163 INVOCATION_ID: faade6f0ee844a46b2a06e04b7dea6f7
 INFO [way_cooler] src/main.rs:163 JOURNAL_STREAM: 9:20153
 INFO [way_cooler] src/main.rs:163 LANG: ru_RU.UTF-8
 INFO [way_cooler] src/main.rs:163 LOGNAME: wcm
 INFO [way_cooler] src/main.rs:163 MAIL: /var/spool/mail/wcm
 INFO [way_cooler] src/main.rs:163 PATH: /usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
 INFO [way_cooler] src/main.rs:163 PWD: /home/wcm
 INFO [way_cooler] src/main.rs:163 SHELL: /usr/bin/fish
 INFO [way_cooler] src/main.rs:163 SHLVL: 1
 INFO [way_cooler] src/main.rs:163 TERM: linux
 INFO [way_cooler] src/main.rs:163 USER: wcm
 INFO [way_cooler] src/main.rs:163 XDG_RUNTIME_DIR: /run/user/1000
 INFO [way_cooler] src/main.rs:163 XDG_SEAT: seat0
 INFO [way_cooler] src/main.rs:163 XDG_SESSION_ID: c3
 INFO [way_cooler] src/main.rs:163 XDG_VTNR: 2
 INFO [way_cooler] src/main.rs:163 XKB_DEFAULT_LAYOUT: us,ru
 INFO [way_cooler] src/main.rs:163 XKB_DEFAULT_OPTIONS: grp:caps_toggle
 INFO [wayland] src/wayland/mod.rs:6 Initializing wayland protocols
 INFO [wayland::gamma_control] src/wayland/gamma_control.rs:235 Initializing gamma control manager
 TRACE [callbacks] src/callbacks.rs:183 Registered wlc callbacks
 INFO [lua::thread] src/lua/thread.rs:121 Initializing lua...
 INFO [lua::thread] src/lua/thread.rs:125 Loading Lua libraries...
 INFO [lua::thread] src/lua/thread.rs:127 Loading way-cooler libraries...
 TRACE [lua::rust_interop] src/lua/rust_interop.rs:23 Registering Rust libraries...
 TRACE [lua::rust_interop] src/lua/rust_interop.rs:36 Executing Lua init...
 TRACE [lua::rust_interop] src/lua/rust_interop.rs:43 Lua register_libraries complete
 TRACE [lua::init_path] src/lua/init_path.rs:60 Looking for init file at ~/.config/way-cooler/init.lua
 INFO [lua::init_path] src/lua/init_path.rs:62 Reading init file from ~/.config/way-cooler/init.lua
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("r")) for Event: KeyEvent::Lua, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("Return")) for Event: KeyEvent::Lua, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("l")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("h")) for Event: KeyEvent::Lua, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("Left")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("Right")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("Up")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("Down")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("Left")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("Right")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("Up")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("Down")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("h")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("v")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("e")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("s")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("w")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("f")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("c")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("space")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("space")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("r")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("q")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("1")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("1")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("2")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("2")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("3")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("3")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("4")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("4")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("5")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("5")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("6")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("6")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("7")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("7")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("8")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("8")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_MOD4, Some("9")) for Event: KeyEvent::Command, passthrough: false
 TRACE [keys] src/keys/mod.rs:88 Registering Keypress(MOD_SHIFT | MOD_MOD4, Some("9")) for Event: KeyEvent::Command, passthrough: false
 INFO [lua::thread] src/lua/thread.rs:135 Read init.lua successfully
 INFO [lua::thread] src/lua/thread.rs:158 Entering main loop...
 WARN [layout::actions::layout] src/layout/actions/layout.rs:481 LayoutTree {
    tree: InnerTree {
        graph: StableGraph {
            Ty: "Directed",
            edges: ,
            node weights: {
                0: Root(
                    Uuid("da87c17e-665f-4889-8558-5b007ecdcdc6")
                )
            },
            edge weights: {},
            free_node: NodeIndex(4294967295),
            free_edge: EdgeIndex(4294967295),
            node_count: 1,
            edge_count: 0
        },
        id_map: {},
        view_map: {},
        root: NodeIndex(0),
        active_path: "0"
    },
    active_container: None
} did not have a parent of type Root, doing nothing!
 TRACE [lua::thread] src/lua/thread.rs:195 Lua: awaiting request
 TRACE [lua::thread] src/lua/thread.rs:206 Handling a request
 TRACE [lua::thread] src/lua/thread.rs:354 Updating programs:lock_screen = String(
    "wc-lock"
)
 TRACE [lua::thread] src/lua/thread.rs:354 Updating programs:x11_bar = String(
    "lemonbar"
)
 TRACE [lua::thread] src/lua/thread.rs:354 Updating mouse:lock_to_corner_on_resize = Boolean(
    false
)
 TRACE [lua::thread] src/lua/thread.rs:195 Lua: awaiting request
 INFO [way_cooler] src/main.rs:214 Running wlc...
 INFO [way_cooler] src/main.rs:61 wlc: libinput: resume
 INFO [way_cooler] src/main.rs:61 wlc: Activating tty
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (0) 1600x900@60000 *
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (0) 1600x900@40000
 WARN [way_cooler] src/main.rs:62 wlc: Connector 1 is not connected or has no modes
 WARN [way_cooler] src/main.rs:62 wlc: Connector 2 is not connected or has no modes
 WARN [way_cooler] src/main.rs:62 wlc: Connector 3 is not connected or has no modes
 WARN [way_cooler] src/main.rs:62 wlc: Connector 4 is not connected or has no modes
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 1920x1080@60000 *
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 1680x1050@60000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 1600x900@60000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 1280x1024@75000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 1280x1024@60000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 1280x800@60000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 1152x864@75000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 1280x720@60000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 1024x768@75000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 1024x768@60000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 832x624@75000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 800x600@75000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 800x600@60000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 640x480@75000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 640x480@60000
 INFO [way_cooler] src/main.rs:61 wlc: MODE: (5) 720x400@70000
 WARN [way_cooler] src/main.rs:62 wlc: Connector 6 is not connected or has no modes
 WARN [way_cooler] src/main.rs:62 wlc: Connector 7 is not connected or has no modes
 INFO [way_cooler] src/main.rs:61 wlc: LVDS-1 Chose mode (0) 1600x900
 TRACE [callbacks] src/callbacks.rs:37 output_resolution: WlcOutput { handle: 1, name: "LVDS-1", views: [] } from  Size { w: 0, h: 0 } to Size { w: 1600, h: 900 }
 WARN [layout::actions::layout] src/layout/actions/layout.rs:481 LayoutTree {
    tree: InnerTree {
        graph: StableGraph {
            Ty: "Directed",
            edges: ,
            node weights: {
                0: Root(
                    Uuid("da87c17e-665f-4889-8558-5b007ecdcdc6")
                )
            },
            edge weights: {},
            free_node: NodeIndex(4294967295),
            free_edge: EdgeIndex(4294967295),
            node_count: 1,
            edge_count: 0
        },
        id_map: {},
        view_map: {},
        root: NodeIndex(0),
        active_path: "0"
    },
    active_container: None
} did not have a parent of type Output, doing nothing!
 TRACE [callbacks] src/callbacks.rs:18 output_created: WlcOutput { handle: 1, name: "LVDS-1", views: [] }: LVDS-1
 TRACE [layout::core::tree] src/layout/core/tree.rs:453 Adding new output with WlcOutput { handle: 1, name: "LVDS-1", views: [] }
 TRACE [layout::core::graph_tree] src/layout/core/graph_tree.rs:508 Normalized edge weights for: NodeIndex(0)
 INFO [layout::core::graph_tree] src/layout/core/graph_tree.rs:240 Added new child NodeIndex(1) for Output { handle: WlcOutput { handle: 1, name: "LVDS-1", views: [] }, background: None, bar: None, id: Uuid("2297ef4c-59f6-4af5-98f1-5a980510a1b1") }
 TRACE [layout::actions::workspace] src/layout/actions/workspace.rs:44 Adding workspace Workspace { name: "1", geometry: Geometry { origin: Point { x: 0, y: 0 }, size: Size { w: 1600, h: 900 } }, fullscreen_c: [], id: Uuid("34518565-3487-42e1-9053-827d5f52ee58") }
 TRACE [layout::core::graph_tree] src/layout/core/graph_tree.rs:508 Normalized edge weights for: NodeIndex(1)
 INFO [layout::core::graph_tree] src/layout/core/graph_tree.rs:240 Added new child NodeIndex(2) for Workspace { name: "1", geometry: Geometry { origin: Point { x: 0, y: 0 }, size: Size { w: 1600, h: 900 } }, fullscreen_c: [], id: Uuid("34518565-3487-42e1-9053-827d5f52ee58") }
 TRACE [layout::core::graph_tree] src/layout/core/graph_tree.rs:508 Normalized edge weights for: NodeIndex(2)
 INFO [layout::core::graph_tree] src/layout/core/graph_tree.rs:240 Added new child NodeIndex(3) for Container { layout: Horizontal, floating: false, fullscreen: false, output_handle: WlcOutput { handle: 1, name: "LVDS-1", views: [] }, apparent_geometry: Geometry { origin: Point { x: 0, y: 0 }, size: Size { w: 1600, h: 900 } }, geometry: Geometry { origin: Point { x: 0, y: 0 }, size: Size { w: 1600, h: 900 } }, id: Uuid("b478fdcd-d06f-41d3-8422-2f4d5a3ebb6f"), borders: None }
 DEBUG [layout::commands] src/layout/commands.rs:374 Layout.SwitchWorkspace("1")
 TRACE [layout::actions::workspace] src/layout/actions/workspace.rs:79 Switching to workspace 1
 INFO [way_cooler] src/main.rs:61 wlc: EGL context is double buffered
 INFO [way_cooler] src/main.rs:61 wlc: EGL version: 1.4 (DRI2)
 INFO [way_cooler] src/main.rs:61 wlc: EGL vendor: Mesa Project
 INFO [way_cooler] src/main.rs:61 wlc: EGL client APIs: OpenGL OpenGL_ES
 INFO [way_cooler] src/main.rs:61 wlc: EGL context (RGB888)
 INFO [way_cooler] src/main.rs:61 wlc: EGL_ANDROID_native_fence_sync EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import EGL_KHR_config_attribs EGL_KHR_create_context EGL_KHR_fence_sync EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_no_config_context EGL_KHR_reusable_sync EGL_KHR_surfaceless_context EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image EGL_MESA_image_dma_buf_export EGL_WL_bind_wayland_display
 INFO [way_cooler] src/main.rs:61 wlc: GL version: OpenGL ES 3.0 Mesa 17.1.6
 INFO [way_cooler] src/main.rs:61 wlc: GL vendor: Intel Open Source Technology Center
 INFO [way_cooler] src/main.rs:61 wlc: GL_EXT_blend_minmax GL_EXT_multi_draw_arrays GL_EXT_texture_filter_anisotropic GL_EXT_texture_compression_dxt1 GL_EXT_texture_format_BGRA8888 GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth24 GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_mapbuffer GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_stencil8 GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float GL_EXT_texture_sRGB_decode GL_OES_EGL_image GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_type_2_10_10_10_REV GL_OES_get_program_binary GL_APPLE_texture_max_level GL_EXT_discard_framebuffer GL_EXT_read_format_bgra GL_EXT_frag_depth GL_NV_fbo_color_attachments GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_array_object GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_EXT_robustness GL_EXT_texture_rg GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer GL_NV_read_depth GL_NV_read_depth_stencil GL_NV_read_stencil GL_EXT_draw_buffers GL_EXT_map_buffer_range GL_KHR_debug GL_KHR_robustness GL_OES_depth_texture_cube_map GL_OES_surfaceless_context GL_EXT_color_buffer_float GL_EXT_separate_shader_objects GL_EXT_shader_integer_mix GL_INTEL_performance_query GL_EXT_compressed_ETC1_RGB8_sub_texture GL_EXT_draw_buffers_indexed GL_EXT_draw_elements_base_vertex GL_EXT_polygon_offset_clamp GL_EXT_texture_border_clamp GL_KHR_blend_equation_advanced GL_KHR_context_flush_control GL_OES_draw_buffers_indexed GL_OES_draw_elements_base_vertex GL_OES_sample_shading GL_OES_sample_variables GL_OES_shader_multisample_interpolation GL_OES_texture_border_clamp GL_EXT_blend_func_extended GL_EXT_clip_cull_distance GL_MESA_shader_integer_functions
 INFO [way_cooler] src/main.rs:61 wlc: GLES2 renderer initialized
 INFO [way_cooler] src/main.rs:61 wlc: Set new bsurface to output (1)
 TRACE [callbacks] src/callbacks.rs:30 output_focus: WlcOutput { handle: 1, name: "LVDS-1", views: [] } focus=true
 INFO [way_cooler] src/main.rs:61 wlc: Added output (1)
 INFO [way_cooler] src/main.rs:61 wlc: HDMI-A-3 Chose mode (0) 1920x1080
 TRACE [callbacks] src/callbacks.rs:37 output_resolution: WlcOutput { handle: 2, name: "HDMI-A-3", views: [] } from  Size { w: 0, h: 0 } to Size { w: 1920, h: 1080 }
 TRACE [callbacks] src/callbacks.rs:18 output_created: WlcOutput { handle: 2, name: "HDMI-A-3", views: [] }: HDMI-A-3
 TRACE [layout::core::tree] src/layout/core/tree.rs:453 Adding new output with WlcOutput { handle: 2, name: "HDMI-A-3", views: [] }
 TRACE [layout::core::graph_tree] src/layout/core/graph_tree.rs:508 Normalized edge weights for: NodeIndex(0)
 INFO [layout::core::graph_tree] src/layout/core/graph_tree.rs:240 Added new child NodeIndex(4) for Output { handle: WlcOutput { handle: 2, name: "HDMI-A-3", views: [] }, background: None, bar: None, id: Uuid("8ebd9b12-b815-427d-b2be-17922a934eac") }
 TRACE [layout::actions::workspace] src/layout/actions/workspace.rs:44 Adding workspace Workspace { name: "2", geometry: Geometry { origin: Point { x: 0, y: 0 }, size: Size { w: 1920, h: 1080 } }, fullscreen_c: [], id: Uuid("732e0016-3f6d-4968-bfc0-344bbb589c6c") }
 TRACE [layout::core::graph_tree] src/layout/core/graph_tree.rs:508 Normalized edge weights for: NodeIndex(4)
 INFO [layout::core::graph_tree] src/layout/core/graph_tree.rs:240 Added new child NodeIndex(5) for Workspace { name: "2", geometry: Geometry { origin: Point { x: 0, y: 0 }, size: Size { w: 1920, h: 1080 } }, fullscreen_c: [], id: Uuid("732e0016-3f6d-4968-bfc0-344bbb589c6c") }
 TRACE [layout::core::graph_tree] src/layout/core/graph_tree.rs:508 Normalized edge weights for: NodeIndex(5)
 INFO [layout::core::graph_tree] src/layout/core/graph_tree.rs:240 Added new child NodeIndex(6) for Container { layout: Horizontal, floating: false, fullscreen: false, output_handle: WlcOutput { handle: 2, name: "HDMI-A-3", views: [] }, apparent_geometry: Geometry { origin: Point { x: 0, y: 0 }, size: Size { w: 1920, h: 1080 } }, geometry: Geometry { origin: Point { x: 0, y: 0 }, size: Size { w: 1920, h: 1080 } }, id: Uuid("2c6931ea-de4f-4e48-b0bb-a175d18d69a9"), borders: None }
 DEBUG [layout::commands] src/layout/commands.rs:374 Layout.SwitchWorkspace("1")
 TRACE [layout::actions::workspace] src/layout/actions/workspace.rs:79 Switching to workspace 1
 TRACE [layout::actions::workspace] src/layout/actions/workspace.rs:188 Focusing on next container
 TRACE [layout::actions::focus] src/layout/actions/focus.rs:260 Active container set to container NodeIndex(3)
 INFO [layout::core::tree] src/layout/core/tree.rs:231 Active container was 3, is now 3
 INFO [way_cooler] src/main.rs:61 wlc: EGL context is double buffered
 INFO [way_cooler] src/main.rs:61 wlc: EGL version: 1.4 (DRI2)
 INFO [way_cooler] src/main.rs:61 wlc: EGL vendor: Mesa Project
 INFO [way_cooler] src/main.rs:61 wlc: EGL client APIs: OpenGL OpenGL_ES
 INFO [way_cooler] src/main.rs:61 wlc: EGL context (RGB888)
 INFO [way_cooler] src/main.rs:61 wlc: EGL_ANDROID_native_fence_sync EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import EGL_KHR_config_attribs EGL_KHR_create_context EGL_KHR_fence_sync EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_no_config_context EGL_KHR_reusable_sync EGL_KHR_surfaceless_context EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image EGL_MESA_image_dma_buf_export EGL_WL_bind_wayland_display
 INFO [way_cooler] src/main.rs:61 wlc: GL version: OpenGL ES 3.0 Mesa 17.1.6
 INFO [way_cooler] src/main.rs:61 wlc: GL vendor: Intel Open Source Technology Center
 INFO [way_cooler] src/main.rs:61 wlc: GL_EXT_blend_minmax GL_EXT_multi_draw_arrays GL_EXT_texture_filter_anisotropic GL_EXT_texture_compression_dxt1 GL_EXT_texture_format_BGRA8888 GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth24 GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_mapbuffer GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_stencil8 GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float GL_EXT_texture_sRGB_decode GL_OES_EGL_image GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_type_2_10_10_10_REV GL_OES_get_program_binary GL_APPLE_texture_max_level GL_EXT_discard_framebuffer GL_EXT_read_format_bgra GL_EXT_frag_depth GL_NV_fbo_color_attachments GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_array_object GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_EXT_robustness GL_EXT_texture_rg GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer GL_NV_read_depth GL_NV_read_depth_stencil GL_NV_read_stencil GL_EXT_draw_buffers GL_EXT_map_buffer_range GL_KHR_debug GL_KHR_robustness GL_OES_depth_texture_cube_map GL_OES_surfaceless_context GL_EXT_color_buffer_float GL_EXT_separate_shader_objects GL_EXT_shader_integer_mix GL_INTEL_performance_query GL_EXT_compressed_ETC1_RGB8_sub_texture GL_EXT_draw_buffers_indexed GL_EXT_draw_elements_base_vertex GL_EXT_polygon_offset_clamp GL_EXT_texture_border_clamp GL_KHR_blend_equation_advanced GL_KHR_context_flush_control GL_OES_draw_buffers_indexed GL_OES_draw_elements_base_vertex GL_OES_sample_shading GL_OES_sample_variables GL_OES_shader_multisample_interpolation GL_OES_texture_border_clamp GL_EXT_blend_func_extended GL_EXT_clip_cull_distance GL_MESA_shader_integer_functions
 INFO [way_cooler] src/main.rs:61 wlc: GLES2 renderer initialized
 INFO [way_cooler] src/main.rs:61 wlc: Set new bsurface to output (2)
 INFO [way_cooler] src/main.rs:61 wlc: Added output (2)
 INFO [way_cooler] src/main.rs:61 wlc: become active
 INFO [way_cooler] src/main.rs:61 wlc: Xwayland started (DISPLAY :0)
 INFO [way_cooler] src/main.rs:61 wlc: xfixes (5.0)
 INFO [callbacks] src/callbacks.rs:130 Preparing compositor!
 INFO [lua::thread] src/lua/thread.rs:181 Running lua on_init()
 TRACE [lua::thread] src/lua/thread.rs:206 Handling a request
 TRACE [lua::thread] src/lua/thread.rs:251 Received request to execute way_cooler.on_init()
 TRACE [lua::thread] src/lua/thread.rs:259 Code executed okay.
 TRACE [lua::thread] src/lua/thread.rs:195 Lua: awaiting request
 INFO [way_cooler] src/main.rs:61 wlc: libinput: suspend
 INFO [way_cooler] src/main.rs:61 wlc: Released drm surface (0x7f19ccb24160)
 INFO [way_cooler] src/main.rs:61 wlc: Removed bsurface from output (1)
 INFO [way_cooler] src/main.rs:61 wlc: Released drm surface (0x7f19ccb24558)
 INFO [way_cooler] src/main.rs:61 wlc: Removed bsurface from output (2)
 INFO [way_cooler] src/main.rs:61 wlc: Activate vt: 3
 INFO [way_cooler] src/main.rs:61 wlc: SIGUSR1
 INFO [way_cooler] src/main.rs:61 wlc: libinput: suspend
 INFO [way_cooler] src/main.rs:61 wlc: Releasing tty
 INFO [way_cooler] src/main.rs:61 wlc: deactive

WARN [layout::actions::layout] src/layout/actions/layout.rs:481 LayoutTree {
    tree: InnerTree {
        graph: StableGraph {
            Ty: "Directed",
            edges: ,
            node weights: {
                0: Root(
                    Uuid("da87c17e-665f-4889-8558-5b007ecdcdc6")
                )
            },
            edge weights: {},
            free_node: NodeIndex(4294967295),
            free_edge: EdgeIndex(4294967295),
            node_count: 1,
            edge_count: 0
        },
        id_map: {},
        view_map: {},
        root: NodeIndex(0),
        active_path: "0"
    },
    active_container: None
} did not have a parent of type Output, doing nothing! ```

Hm, that makes me think there's a bug somewhere in the tiling code. That might just be an erroneous warning though...

Is it the external display that's staying black, or the notebook? I.E is the other monitor not working, or does the presence of the other cause neither of them to work?

If the former, then have you tried switching to the output by going to the second workspace ("<meta or alt or whatever key you use> + 2")? Currently Way Cooler only displays its background on the first output that is active, I haven't gotten around to fixing the background so it displays on both. So it's possible it is working fine, it just isn't immediately apparent.

Switching to another workspace helped, workspaces 1-5 was on notebook's display which i thought was disabled, 6-9 changed to external.
So the problem is: way-cooler starts on display which is supposed to be disabled.

Are you expecting the note book's display to be disabled? Currently Way Cooler doesn't have a way of managing outputs, that feature will come with wlroots.


Allow osbuild to run on rawhide (f33)

Add an additional symlink for Fedora Rawhide, which is currently set
as release 33.
Signed-off-by: Major Hayden<EMAIL_ADDRESS>

@ondrejbudai Oh, good catch!