Basic Documentation

The Forge sounds pretty great but there does not seem to be much in the way of documentation.
I don't even see simple "How to compile" or build instructions. Which seems like a good place to start.
The description talks about it being like "Legos" where you can use the different parts of the system as needed. So does that mean it can be built in sections and integrated into other projects piece by piece? If so how? It would be nice if there was something, maybe on the wiki, that showed exactly how you can build just the renderer, for example, or the renderer and lua scripting, etc.. into a library/libraries to include in other projects.
I know I could probably dig through the PyBuild file and look at all the source and try to figure it out myself. But I think it'd be a pretty big step in getting people to try this project out if they could actually 'get started' without having to put in a lot of work.

2:09 PM
Hello @Pewsplosions
As it stands The-Forge doesn't have much documentation other than what's in the wiki already but nothing related to building or compiling as you say. We are more than happy answering any questions you might have on our public Discord channel.
We distribute solution and project files for all our platforms as we do not use any type of build system or project generation tool.  The 01_Transformations examples serves as the minimal hello world to get something basic on the screen and should be used to understand how The-Forge works.
We also strive to make our interfaces self explanatory and hopefully should guide a new developer to understand what's possible.
The-Forge is made of multiple parts but the main two libraries will be the OS and the renderer which are independant of the other, thus legos as any OS library can be swapped in and used by the application. If you have a chance to look at our unit-tests solution and projects, you will see the different libraries that are part of our lego set.
As it stands the OS Library will contain more than you might require and it would be up to you to determine what's needed and what's just extra.
As it stands PyBuild is only used for Continuous integration and is not meant to be used as the main build tool. It actually just triggers msbuild on the projects themselves. If you'd really like to build from the command line you should be able to take a look at our github CI logs and see how PyBuild gets used.

Thanks for all the information. I've been surfing around the code a bit. I like what I've seen. I plan to look further at it tonight so I'll take your suggestions as jumping off points. :)
I was mostly suggesting that some 'Getting Started' -esque documentation would probably be very helpful for people that stumble across the project. As-is, a new person will see the extremely long readme, the sparse wiki, and probably give up before checking further.
Based on what you said, you could have a Getting Started heading in the wiki with subheadings of Visual Studio, XCode, and Ubuntu. Then on each of these pages just have a quick step-by-step of how to import the project on these platforms, open 01_Transformations and build the example.
Then back on the main readme have a link up at the top to the Getting Started page.
Just a suggestion. Doesn't have to be prioritized or anything. As it is right now it can definitely be intimidating to anyone that comes across it, even experienced developers. But from what I've seen so far you've got something pretty nice going here so it'd be cool to get more and more people involved.

Hey @Pewsplosions, do you want to add to our Wiki what you would consider a good starting point? I can give you access to the Wiki and you can change it.

@wolfgangfengel I don't think I'd be a good person to do that. I've not spent a lot of time with the project and what I have, I still can't even figure out to set it up or run anything. I'm not familiar with codelite to import the project and I haven't tried any of the others. Mostly, the little bit I've done, was just looking through how some of the rendering system is set up and the project structure itself. I've been looking around at how projects handle swapping backend systems when needed and such... nothing crazy in mind, just personal interest.
This is why I made the issue. I'm unfamiliar with the project. It looks nice. But I have no clue what to do and haven't had the time to figure it out. Whereas if there was a getting started section in the wiki, I may not ultimately get much further than that, but I'd at least get an actual feel for how working with the project would go.
I would assume I am not alone in this. I'm not sure how much traffic this repo gets, but I'm sure there have been many like me that would potentially go further with it but aren't able to put the initial time in to decide that.
Of course if I ever do get further with it, I would definitely be willing to write out some steps for others to follow. I'm just not in position to do that right now.

@wolfgangfengel  I am willing to write a baby step for Windows and Linux. It was easy to figure out to run the 01_transformation on linux (fedora in my case) but I still struggle with windows but I could do it if you guys are still interested.

Can you send me a pm and I set you up with the access code.

Here's some more build instructions:
Install a VulkanSDK.
Make sure you have the Win10SDK installed, it shouldve come with msvs, but who knows what you clicked in that installer.
When opening the solution in vs2019+, right click it and choose retarget solution to newer SDK.
This won't work on a few 3rd party libs, so you need to right click those. Like the gainput, ozz.
For Basisu, you need to add
#include <stdio.h>
#include <ctype.h>
to basisu_enc.h so it finds tolower().


CI test community aqua

Signed-off-by: Martin Vala<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Does your operator have nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Submit operators to both upstream-community-operators and community-operators at once
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/hold

/unhold

/unhold

/hold
Found modifications in already published version(s) of the operator. Setting corresponding labels. Please confirm by posting /unhold command or removing do-not-merge/hold  label.

Found modifications in already published version(s) of the operator. Setting corresponding labels. Please confirm by posting /unhold command or removing do-not-merge/hold label.

/hold
Found modifications in already published version(s) of the operator. Setting corresponding labels.
Please confirm by posting /unhold command or removing do-not-merge/hold label.

/hold
Found modifications in already published version(s) of the operator.
Please confirm by posting /unhold command or removing do-not-merge/hold  label.

One or multiple versions were modified.


ignore color formatting with custom titleFormatter

fixes #215

Codecov Report

Merging #216 into master will increase coverage by 0.23%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #216      +/-   ##
==========================================
+ Coverage   67.91%   68.14%   +0.23%
==========================================
  Files           5        5
  Lines         134      135       +1
==========================================
+ Hits           91       92       +1
  Misses         43       43

Impacted Files
Coverage Δ

src/core.js
78.33% <66.66%> (+0.36%)
: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 993c896...a04a28a. Read the comment docs.

thx

I actually quite liked the new colors! I simply added %c a couple times in my custom titleFormatter string and it colored my output properly.
@evgenyrodionov is there any way to keep the colors AND use a custom formatter now? After this PR my colors are broken again (3.0.1). Otherwise I'll make a PR.


VG-5800 - Added Font License to index.html

Codecov Report

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

@@            Coverage Diff            @@
##             master     #139   +/-   ##
=========================================
  Coverage          ?   79.62%
=========================================
  Files             ?      117
  Lines             ?     7937
  Branches          ?     1213
=========================================
  Hits              ?     6320
  Misses            ?     1617
  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 a571ff7...4f17f1d. Read the comment docs.


Get brightness status from hue group node

In 4.x the hue group node only outputs a very limited status message.
In my light control, I want to control all the groups (rooms) via group nodes.
Prior to 4.x these group nodes would allow me to get outputs like brightness and color, so I could reflect that in my dashboard.
However, since now it doesn't output these values anymore, what would be the best way to build my light control?
I assume I could add a light node for each room to receive status messages for brightness, color and colortemp.
But is adding another node really the best option?

Small remark: the status output is only received if I trigger it manually or via a payload to request the status.
Is there no way anymore to automatically output the status if any value is changed?

2nd remark: with 4.x setting the brightness doesn't seem to turn on the lights anymore?

3rd remark:
I have an automation for my bathroom, that triggers if the door is closed/opened.
If opened -> light off.
If it is closed -> check room brightness (aqara sensor), if too dark -> check if light is off -> if off -> set brigthness and colorTemp.
Problem: I can't use any huemagic node for this automatic. Because the node I would use for checking if the light is off would always output a status whenever the light is changed (e.g. via hue app) and NOT only if I request the status.
@Foddy is there any way to stop automatic status output for one specific node?
The way it is implemented right now would cause the light to always be turned on, since when turning it off the node for checking would output "false", which triggers the brightness/colorTemp to be set.
I only want to have the status if I send the payload "status" to the node :(


Return ingress.class value for ingress.provider if not set

This should solve a regression that causes the GCE ingress controller implementation to not work with manifests that don't explicitly set kubernetes.io/ingress.provider: gce. Without this change, these manifests would attempt to use the nginx provider.
This also solves a problem where the default supported ingress classes were not set correctly if not specified.

This is a follow-up to the recently merged #202 - @simonswine could you take a look over.
/cc @jackhopner

Any reason to remove the option to set the default @munnerz ? We could have it check if the default was set otherwise return the ingress class?


Run CI with assertion enabled

Codecov Report

Merging #47 (39e8e4f) into master (331f9d3) will decrease coverage by 14.77%.
The diff coverage is 0.00%.

:exclamation: Current head 39e8e4f differs from pull request most recent head 3880b2c. Consider uploading reports for the commit 3880b2c to get more accurate results

@@             Coverage Diff             @@
##           master      #47       +/-   ##
===========================================
- Coverage   87.55%   72.77%   -14.78%
===========================================
  Files          14       14
  Lines        1430     1429        -1
===========================================
- Hits         1252     1040      -212
- Misses        178      389      +211

Flag
Coverage Δ

unittests
72.77% <0.00%> (-14.78%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/utils.jl
38.70% <0.00%> (-30.46%)
:arrow_down:

src/promise.jl
0.00% <0.00%> (-88.89%)
:arrow_down:

src/lcrq.jl
73.83% <0.00%> (-19.19%)
:arrow_down:

src/dict.jl
71.31% <0.00%> (-18.30%)
:arrow_down:

src/msqueue.jl
72.91% <0.00%> (-14.59%)
:arrow_down:

src/ssqueue.jl
86.52% <0.00%> (-9.93%)
:arrow_down:

src/stack.jl
89.28% <0.00%> (-7.15%)
:arrow_down:

src/dlcrq.jl
77.16% <0.00%> (-6.07%)
:arrow_down:

src/workstealing.jl
90.17% <0.00%> (-1.79%)
:arrow_down:

Continue to review full report at Codecov.

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


Syntax highlighting should handle function signatures

Perl 5.20 allows subroutine signatures, but the highlighting gets very unhappy with them.
See also #164 about conditional features.

Looks like this has been implemented:
https://github.com/vim-perl/vim-perl/blob/dev/syntax/perl.vim#L368


CMLK-79: Fix jms-amqp-10 kamelets

some other docs updated by the scripts.

How should the kamelets in the library/ folder be modified ? Manually or by some script ?


Database Seeding

Describe what you want
Would love to be able to seed database like migrations.

You can just create a typescript file:
await db.insert(markets).values({
organisationUuid: '324583a3-51b0-4ca9-976b-4394e82833ae',
city: 'Gent',
country: 'Belgium',
startDate: new Date('2021-05-01T10:00:00.000Z'),
endDate: new Date('2021-05-01T18:00:00.000Z'),
province: 'Oost-Vlaanderen',
size: 100,
streetname: 'Korenmarkt',
streetnumber: '1',
type: ['FLEE_MARKET', 'ANTIQUES_MARKET', 'CLOTHES_MARKET'],
zipcode: '9000',
});
console.log('Seed complete!');
And have a npm script to run it:
"drizzle:seed": "dotenv -e .env.dev tsx src/database/seed.ts"

You can just create a typescript file:
await db.insert(markets).values({ organisationUuid: '324583a3-51b0-4ca9-976b-4394e82833ae', city: 'Gent', country: 'Belgium', startDate: new Date('2021-05-01T10:00:00.000Z'), endDate: new Date('2021-05-01T18:00:00.000Z'), province: 'Oost-Vlaanderen', size: 100, streetname: 'Korenmarkt', streetnumber: '1', type: ['FLEE_MARKET', 'ANTIQUES_MARKET', 'CLOTHES_MARKET'], zipcode: '9000', });
console.log('Seed complete!');
To execute
And have a npm script to run it: "drizzle:seed": "dotenv -e .env.dev tsx src/database/seed.ts"

What technology are you using if I may ask? I tried a similar approach with NextJS (13.4 App router). Unfortunately I keep getting an error.  I'll try to get it to work in a standalone package.

You can just create a typescript file:
await db.insert(markets).values({ organisationUuid: '324583a3-51b0-4ca9-976b-4394e82833ae', city: 'Gent', country: 'Belgium', startDate: new Date('2021-05-01T10:00:00.000Z'), endDate: new Date('2021-05-01T18:00:00.000Z'), province: 'Oost-Vlaanderen', size: 100, streetname: 'Korenmarkt', streetnumber: '1', type: ['FLEE_MARKET', 'ANTIQUES_MARKET', 'CLOTHES_MARKET'], zipcode: '9000', });
console.log('Seed complete!');
To execute
And have a npm script to run it: "drizzle:seed": "dotenv -e .env.dev tsx src/database/seed.ts"

What technology are you using if I may ask? I tried a similar approach with NextJS (13.4 App router). Unfortunately I keep getting an error. I'll try to get it to work in a standalone package.

My idea of seeding the database, is a development or testing purpose action.
The .ts (or .js) file with the inserts is simply called and ran with tsx (you can just use "node ./seed.js" for regular JS).
So it has nothing to do with Next.js.
But fyi, I have a node express project. A drizzle client is created and exported as "db".
That is used to seed the database.

Would be better if you could execute some code together with the migrations transactions.
That way your seed can follow your migrations.
Since the migrations are defined In SQL, I guess you can define insertions over there.
But it would be more comfortable to have them in TS, if somehow we could get a callback before/after each migration running to associate the seed with that.

Is this actionable @AndriiSherman ?

We have a use case for seeding in production, and it would be great if we could create them using ts.
We store some settings in a table, and the app doesn't expose an API to manage them, so our idea is to seed the database initially and (maybe) do some transformation later, using the same (or similar) migration system to prevent a seeding from running twice on a DB.
It would be great if the migration system allowed us to manage the schema and mutate the data. We are fixing issues in the data with "migrations", and we want to move to drizzle for new microservices, but this is a blocker for us now. We may need to implement our system if this is not a priority.

We have drizzle-seed package available!
Release notes: https://github.com/drizzle-team/drizzle-orm/releases/tag/0.36.4
Docs: https://orm.drizzle.team/docs/seed-overview


User cannot be unset

Once the user has been set, it cannot be unset anymore (e.g. for the case the user logged out or withdrew GDPR consent).
Neither user={undefined} nor user={{id: null}} work because of this code:

@fabb Currently within the SDK we require some string ID value in order to be able for the decision and tracking apis to function. We don't currently support functional use or generating a fallback ID ourselves in these cases within the SDK and need that passed-in string value.
Longer term we would consider handling anonymous users more directly out of the box, but currently for this case we would recommend overwriting the user to a specific new ID value. This could be an anonymous ID you have access to client-side, or even a fixed string value if you are just looking to have basic On/Off toggling available for Features in this state.

I default to a string and then when I run experiments I filter out the user(s) with that string


Op Support: aten.all.default

Add converter.
Related to #99

See if it is trivial enough to also add support for aten.all.dim at the same time. If not, that can be a separate issue


MSID: 88279 Version: 1 DOI: 2<IP_ADDRESS>5722

"msas": "Neuroscience"
"msid": "88279"
"preprintDoi": "10.1101/2<IP_ADDRESS>5722"
"Reviewed Preprint posted": "2023-07-04"
"Sent for peer review": "2023-04-05"
"Posted to bioRxiv": "2023-04-18" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>5722v2")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=88279)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/88279/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews
Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>5722)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/88279/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/88279)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/88279

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/88279

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/88279/v1/88279-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/88279)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

We have version 1 instead of version 2 loaded.


Change ConnectionIdManager interface

Hello,
Is it possible to change the signature of getId in ConnectionIdManager
from
long getId(Connection connection);
to
String getId(Connection connection);
This will allow for better tracking in some environments while keeping the current behavior for others. Example for such better identification would be the combination of Oracle's SID and serial#

The change is released as part of 1.4.8


GEP 1686: Mesh conformance testing plan

What type of PR is this?
/kind gep
/kind test
/area conformance
What this PR does / why we need it:
Introduces a plan for how to test GAMMA spec implementations for the next release as introduced in #1686.
Rendered

Shane's requested changes reflect my perspective as well; will re-review once those are addressed

/lgtm


Support yadm

I would like to support yadm if it wouldn't be too difficult. yadm is a dotfile manager which is essentially just a wrapper around Git. It has an almost identical CLI, with commands like yadm add, yadm commit, etc. I use it to manage my dotfiles.
If I could somehow determine the caller in the Bash scripts (either git or yadm), I could write the scripts to use the specific caller dynamically. That is, instead of using git ls-files internally, I could use $CALLER ls-files internally. That said, I can't currently think of a way to determine the caller dynamically.

This might be along the right path, but PARENT_COMMAND equals git when called by yadm.

This might be a step in the right direction. However, if PARENT_COMMAND is placed inside a script and that script is invoked by yadm, PARENT_COMMAND is nonetheless equal to git.
https://newbedev.com/get-the-name-of-the-caller-script-in-bash-script

This actually helps, and prints yadm when triggered by yadm.
https://superuser.com/a/1497598/1174309

I pushed some progress on this work to the yadm branch. I'm not sure I'm happy with how much more complicated this makes the project, though. It might be better to suggest that users do something like this, despite its drawbacks:
$ yadm enter
$ git iadd

One drawback is that this string of commands will pass way to fzf because the --others option is passed to git ls-files internally and yadm does not care about most files.


Reference error with free_email_provider_set in TS

Hi there, thanks for the package!
I ran into an error while trying to use it in a Typescript monorepo. It seems that the implicit declaration of free_email_provider_set is causing issues. Not sure if it's TS/es-build related but explicitly declaring it fixes the issue and all tests pass.
ERROR	ReferenceError: free_email_provider_set is not defined
at ../../node_modules/company-email-validator/free_email_provider_domains.js

I just declared it like const free_email_provider_set = new Set(free_email_provider_domains.split("\n")) and that worked.
I can push a PR up with a fix if this seems like a legit issue.

ReferenceError: free_email_provider_set is not defined
I also ran into this error.

Hi @rudeluv, thank you for your report and help. Please, could you create a PR for this issue, as you suggested?

@bnurbekov sure thing, this PR should fix it ☝.


Kubernetes minimum requirements?

HI, I'm deploying FabConnect on a Kubernetes environment and I'm wondering what are the minimum requirements for running FabConnect. Basically, I'm looking for resources.requests.cpu and resources.requests.memory values, the documentation does not mention anything on that matter.
Thanks in advance.

@jimthematrix Do you have recommendations on system requirements for Fabconnect?


Any way to configure width of Timemory output?

e.g.,

the kernel name is getting ellipsed (totally a verb) before I can see the relevant name.  I imagine the "right" way to do this is to hook-up with KokkosP to rename the kernels, however it would be good to add (or document, if one exists already) a method to control the width of these tables.

OMNITRACE_MAX_WIDTH
Also, the kernel names are not truncated in the JSON outputs.

omnitrace-avail -db -r WIDTH

Sigh, my reading comprehension ... :rofl:


Sdc changes

This PR

uses data criteria models for source data criteria, and parses these directly from the hqmf xml
removes data criteria which was a duplicated of source data criteria
pulls most basic fields out of the hqmf xml rather than using the existing parser (which could eventually be removed)

Pull requests into cqm-parsers require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[x] Internal ticket for this PR: https://jira.mitre.org/browse/BONNIE-1836
[x] Internal ticket links to this PR
[x] Code diff has been done and been reviewed
[ ] Tests are included and test edge cases
[ ] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Codecov Report

Merging #29 into master will increase coverage by 0.15%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #29      +/-   ##
==========================================
+ Coverage   76.61%   76.77%   +0.15%
==========================================
  Files         109      110       +1
  Lines        5277     5308      +31
==========================================
+ Hits         4043     4075      +32
+ Misses       1234     1233       -1

Impacted Files
Coverage Δ

lib/measure-loader/value_set_helpers.rb
100% <ø> (+1.72%)
:arrow_up:

lib/measure-loader/source_data_criteria_loader.rb
100% <100%> (ø)

lib/measure-loader/hqmf_measure_loader.rb
95.12% <100%> (+0.25%)
:arrow_up:

lib/hqmf-parser.rb
100% <100%> (ø)
:arrow_up:

lib/measure-loader/cql_loader.rb
100% <100%> (ø)
: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 90dfc2d...bdba61a. Read the comment docs.


[$250] mWeb -Room - Inconsistency while pasting highlighted mention in room and expense description

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.72
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
1.Go to https://staging.new.expensify.com/
2. Tap FAB > Start a Chat > create a new room
3. Copy the following text in chat
@applausetester++0411km
<EMAIL_ADDRESS>(notice: first mention selected from list, second mention is highlighted)

Tap header

Paste text in room description

Note second mention is not highlighted

Navigate to LHN

Tap fab -- track expense

Enter amount and tap next

Paste the same above text in track expense description

Note now second mention is highlighted and displayed

Expected Result:
There should not be inconsistency while pasting highlighted mention in room and expense description
Actual Result:
Inconsistency while pasting highlighted mention in room and expense description
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/019b0b29-175f-4a31-bcb2-8f1a1fc95d48
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01c4a08b3d6f351b65
Upwork Job ID:<PHONE_NUMBER>227322368
Last Price Increase: 2024-05-14
Automatic offers:

shubham1206agra | Reviewer | 0
tienifr | Contributor | 0
bernhardoj | Contributor | 0

Issue OwnerCurrent Issue Owner: @shubham1206agra

@Christinadobrzyn  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

I don't think this is a bug,
From what I can test, the only time the
<EMAIL_ADDRESS>isn't highlighted is after it's copied and pasted but before it's 'saved' in the room/expense/description. Once saved it turns into a mention and is highlighted.
@bernhardoj let me know if you feel otherwise but I'm going to close this as an edge case, small incident.

From what I can test, the only time the
<EMAIL_ADDRESS>isn't highlighted is after it's copied and pasted but before it's 'saved' in the room/expense/description. Once saved it turns into a mention and is highlighted.

@Christinadobrzyn That's true. To simplify it, the room description page currently doesn't enable the live markdown preview, while the expense/task description enables it. So, if we want to enable the live markdown preview for room description too, then we can reopen this.
Btw, there is a previous discussion here to enable the live markdown preview on some inputs, but looks like the room description page is missing from the list.

@Christinadobrzyn bump

Ah sorry @bernhardoj this GH was closed so I didn't see this. Ah yes, we should work on this based on this convo - https://expensify.slack.com/archives/C01GTK53T8Q/p1711641837108169

I assume this can be external?

Hi @shubham1206agra can you check out these proposals when you have a moment?

I think we are handling the short mention live markdown preview here.

Ok yeah, considering that @tienifr already put some time into this, splitting the bounty and using @bernhardoj's proposal sounds good to me.

(Co-assigning @bernhardoj for the payment later.)

monitoring PR - https://github.com/Expensify/App/pull/42361

monitoring PR - https://github.com/Expensify/App/pull/42361

PR - is in staging.
Just a heads up - I'm going to be ooo until June 24th so going to assign a teammate to watch this while I'm away

@garrettmknight this might need to be paid before I'm back - can you watch it while I'm away? TY!

@bernhardoj @tienifr updated offers sent to you to split the bounty.

Accepted

All paid out - @shubham1206agra can you complete the checklist when you get a chance?

@shubham1206agra can you check again? I think I just paid you through Upwork. @bernhardoj and @tienifr did you receive payment?

@Christinadobrzyn yes, I get the payment

okay I think this can be closed - payment summary here - https://github.com/Expensify/App/issues/41919#issuecomment-2166044223


refr(enso-org/cloud-v2#1088): Make Project fields camelCase

Modifies fields of Project-like structs to be camelCase. This brings more of the backend API into line with the existing style guide.
Note that the changes in this commit are breaking if the IDE is run against a backend that hasn't been updated to account for the corresponding API changes.
Pull Request Description

Important Notes

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

qa 🟢


Agent and user communication

To improve user experience, the Real Estate website must provide users with a method to contact their agent, and receive a response within 24 hours.

This rule makes sure the user has a way to contact their agent within


OptionsMonitor OnChange is triggered even though the last ConfigurationProvider has not changed

We have the following scenario where configuration providers are set as follows:

appsettings.json,
appsettings.{env.EnvironmentName}.json
User Secrets File
Azure App Configuration
Azure Key Vault
Environment Variables
Command Line Arguments

Command Line Arguments (7) is the configuration provider which it's settings take priority over the other providers. See: https://github.com/aspnet/Extensions/issues/1711
Let's say that both in appsettings.json and Azure App Configuration we have the following setting (Name: Lee). If I were to change the value to: (Name: Peter) from within the appsettings.json file, the OnChange event of OptionsMonitor would still trigger (not expected) as the returned value is Lee due to the Order of precedence described above (1. AppSettings.json, 4. Azure App Configuration).
The question: Is this expected behavior? Should the OnChange event still trigger even though the TOptions returned contained the original setting due to order of precedence?

@Eilon any updates on this?

(BTW I don't work on this project anymore. I just label things for fun 😄)
So you're saying the OnChange is unexpected because the effective value didn't change?


parse bpf program type

add helper to parse bpf program type

@geyslan (To check the unit tests error regarding use of inexistent OS dynamic library, instead of using the static lib we build).

@geyslan (To check the unit tests error regarding use of inexistent OS dynamic library, instead of using the static lib we build).

https://github.com/aquasecurity/libbpfgo/pull/212 merged.


Polyglot codebase

goal
this branch is for lombok, swagger, kotlin, scala, android, maven code generators, gradle contributors, anyone who wants to push the envelope and pursue (reducto-absurdum)-1 towards scalable and efficient real time trading methods and concise code representations
methodology/seed build
initially this uses a script to merge xchange-core and the style-guide compliant modules and should retain the ability to absorb development branch modifications as a baseline (see bin/bootstrap to start your own!)  this gives a noticeable build time improvement and simplifies debugging and hot reloading visibility by the tools.
testing
we know that the XChange/develop branch tests are at a certain state, though the json test resources lack package isolation and there are collisions when merged.  for this reasons the test phase of maven should be de-emphasized until enough compartmentalization exists in the parent fork.  these are not hard to fix, but there's a large and growing number of cut and paste module artifacts with un-mergable structure at this time.
coding standards
https://12factor.net and microservices aren't identical, but they are close cousins, and make good guidelines to supercede any manually evangelized set of coding/style guidelines with real-world examples like netflix and heroku ecosystems.  minimizing "bikeshedding" on indentation, module structure, and library increases the available time for someone with a vision to illustrate by doing, and forking if there are irreconcilable differences.

just merging #2432 is enough.  Watch me take up the cause for styleguide compliance after that gets merged in.
fw, this is a build log  https://gist.github.com/jnorthrup/6390b4f5989c95bb54d54340addd5d58/c4cf1e6ae255bbad4720c3b949e0e81f5b1028a1#file-gistfile1-txt-L1405

If you knew how to create IntelliJ and Eclipse formatters, that were identical to each other, that'd be wonderful.

i can install maven formatters with eclipse configs.  maven install will reformat.


Add support for "/" as card expiry separator, not solely " / "

Other payment gateways, e.g Braintree, do not support MM / YYYY as expiry date, only MM/YYYY, without spaces around the slash.

Hi there @paulozoom. As noted in the readme and contributing guidelines, we're not currently accepting feature requests.
With respect to your particular question: I'm not sure what's missing? jquery.payment helps you format display values and spits out structured data. Whether the customer sees "MM / YYYY" vs "MM/YYYY" shouldn't affect how it gets sent to your payment provider:
$.payment.cardExpiryVal('03 / 2025'); //=> {month: 3, year: 2025}

The simplest implementation of the Braintree SDK reads the value of card fields on input and gets a payment nonce all by itself. There's a more low-level implementation which I'll switch to, though.
Question: would you accept a PR where an option for the MM/YY separator was a configurable option?

On 15 Jun 2016, at 19:16, Jenan Wise<EMAIL_ADDRESS>wrote:
Closed #232.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@paulozoom Probably not, sorry. I suspect it would add a bit of extra complexity on top of a mountain. Please see the readme for details! I think Braintree's integration is actually a better place to ask for looser inputs -- jquery.payment is opinionated about how things should be formatted, and we'd rather not add knobs to that.


Upload package

Upload to Test PyPI
Test the package
Upload to PYPI
Release to Github

Useful workflow tutorial is here
https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

Is done in 6dc58c7c8abe5837a52b562cd16e0979cecebf60


Use new style exceptions in both Python 2 and Python 3

Old style exceptions are syntax errors in Python 3 but new style exceptions work as expected in both Python 2 and Python 3.

Hi,
Thank you ;).


hotfix: axios interceptor fix

Downgrade until https://github.com/axios/axios/issues/4012 is solved.

Revert when fixed.


upstream manpage issues

This issue documents a known limitation: some Debian packages have issues with regards to the manpages they ship.
Manpages in invalid directory

report
binary package
issue

850600
mirmon
manpages in invalid dir (man/pm/man3)

850618
controlaula
manpages in invalid dir (man/py/man1)

850619
plainbox
manpages in invalid dir (man/py/man1)

850621
dhcp-probe
manpages in invalid dir (man/cf/man5)

850623
partclone
manpages in invalid dir (man/dd/man8)

850624
sarg
manpages in invalid dir (man/man1/man1)

850625
libifd-cyberjack6
manpages in invalid dir (man/)

Manpages in wrong directory

report
binary package
issue

TODO
clang-format-3.8
manpages in wrong dir (man/man8 instead of man/man1)

850628
libcdio-utils
manpages in wrong dir (man/jp instead of man/ja)

Manpages with invalid names

report
binary package
issue

850641
libqwt-doc
manpages with wrong suffix (.3 inside man1)

850642
libexosip2-dev
manpages with wrong suffix (.3 inside man1)

Dangling symlinks

report
binary package
issue

696277
pyro
manpages are dangling symlinks

696277
pyro-gui
manpages are dangling symlinks

TODO
obexftp
manpages are dangling symlinks

850636
maildrop
manpages are dangling symlinks

850637
ksh
manpages are dangling symlinks

567093
ocsinventory-agent
manpages are dangling symlinks

850638
ng-cjk
manpages are dangling symlinks

850638
ng-cjk-canna
manpages are dangling symlinks

850638
ng-latin
manpages are dangling symlinks

850639
rust-lldb
manpages are dangling symlinks

850640
socks4-clients
manpages are dangling symlinks

awesome list. i wonder if this stuff could be automated? after all, it's "just" sending an email to the bts... ;)

Good point!
What I had in mind was working on lintian checks which catch these cases, but I’m not entirely sure yet how feasible it is to catch the different classes of errors.
In case lintian checks don’t work out, we should indeed automate the bug reporting.
One other aspect which would be good is exposing these errors to end users in an “errata” or “known issues” file, so that we don’t need to check the logs on behalf of users who are wondering about manpages not being present.


Fix for issue #17

also adds support for a bottom border for the buttons for ios.

Thanks!  👍 Would be nice if you could squash 13 commits into 1, and could you also update the README with the new properties?


Download standings table as csv

See https://gorails.com/episodes/export-to-csv

See also http://stackoverflow.com/questions/17014912/how-to-download-a-csv-file-in-ruby-on-rails


allow setting custom properties for systemd services, for instance to…

Signed-off-by: Bas<EMAIL_ADDRESS>Description
[Describe what this change achieves]
This change allow users to add custom properties to a systemd service. For instance properties that allow setting open file descriptors with LimitNOFILE
Issues Resolved
[List any existing issues this PR resolves]
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ v ] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

Thanks for the commit @bassteen. In the future we have tooling that handles the version bump so that doesn't need to be done.

no worries, glad to contribute and see that it is merged.


Connection to c-lighting is impossible

Running two nodes lnd and c-lighting. Both latest git.
When trying to connect between connection is dropped.
1438139-2019-10-22 15:38:19.040 [INF] SRVR: New inbound connection from <IP_ADDRESS>:43714
1438223:2019-10-22 15:38:19.040 [INF] SRVR: Finalizing connection to 031e8f3e16f06f78249497161f23fa50b3218c7a15c895149459942836ffc53f6c@<IP_ADDRESS>:43714, inbound=true
1438385:2019-10-22 15:38:19.043 [INF] PEER: NodeKey(031e8f3e16f06f78249497161f23fa50b3218c7a15c895149459942836ffc53f6c) loading ChannelPoint(1e42b9a53dfae24ea4f59e32bf3f809aad809276e33b062207c04bd7a5a596ae:0)
1438586-2019-10-22 15:38:19.043 [WRN] PEER: ChannelPoint(1e42b9a53dfae24ea4f59e32bf3f809aad809276e33b062207c04bd7a5a596ae:0) has status ChanStatusDefault|ChanStatusCommitBroadcasted, won't start.
1438774-2019-10-22 15:38:19.043 [INF] PEER: Sending 1 channel sync messages to peer after loading active channels
1438880:2019-10-22 15:38:19.043 [INF] SRVR: Negotiated chan series queries with 031e8f3e16f06f78249497161f23fa50b3218c7a15c895149459942836ffc53f6c
1439019:2019-10-22 15:38:19.043 [INF] DISC: Creating new GossipSyncer for peer=031e8f3e16f06f78249497161f23fa50b3218c7a15c895149459942836ffc53f6c
1439157:2019-10-22 15:38:19.051 [INF] PEER: unable to read message from 031e8f3e16f06f78249497161f23fa50b3218c7a15c895149459942836ffc53f6c@<IP_ADDRESS>:43714: EOF
1439313:2019-10-22 15:38:19.051 [INF] PEER: Disconnecting 031e8f3e16f06f78249497161f23fa50b3218c7a15c895149459942836ffc53f6c@<IP_ADDRESS>:43714, reason: read handler closed
1439479:2019-10-22 15:38:19.151 [INF] DISC: Removing GossipSyncer for peer=031e8f3e16f06f78249497161f23fa50b3218c7a15c895149459942836ffc53f6c
1439613-2019-10-22 15:38:24.628 [INF] CRTR: Processed channels=0 updates=19 nodes=0 in last 1m0.000117258s

Also reported on c-lightning side
https://github.com/ElementsProject/lightning/issues/3200

@Rav3nPL

Running two nodes lnd and c-lighting. Both latest git.

Have you tried the latest versions instead of "latest git", which seems to me the master version of both impls?
I'm running c-lightning "version": "v0.7.3rc3", and two lnd nodes  "version": "0.8.0-beta commit=v0.8.0-beta", I have no issue getting them connected and opened channels to each other, my c-lightning node can connect and have channels opened to both lnd nodes.

Unable to reproduce.

Happened to me as well.
clightning 0.9.3, lnd 0.12.1-beta
clightning side:
{
"type": "BROKEN",
"time": "773.825736853",
"node_id": "XXXXXXXXXXXXX",
"source": "openingd-chan#5175",
"log": "Unexpected message WIRE_ANNOUNCEMENT_SIGNATURES"
},
{
"type": "INFO",
"time": "773.825847754",
"node_id": "XXXXXXXXXXXXX",
"source": "openingd-chan#5175",
"log": "Peer connection lost"
},
{
"type": "INFO",
"time": "773.825894751",
"node_id": "XXXXXXXXXXXXX",
"source": "chan#5175",
"log": "Owning subdaemon openingd died (62208)"
},
lnd side:
2021-05-13 23:28:16.362 [INF] SRVR: New inbound connection from XXXXXXXXXXXXXXX                                 [5/4534]
2021-05-13 23:28:16.362 [INF] SRVR: Finalizing connection to XXXXXX, inbound=true
2021-05-13 23:28:16.365 [INF] PEER: NodeKey(XXXXXX) loading Chan
nelPoint(XXXXXX:1)
2021-05-13 23:28:16.365 [INF] HSWC: ChannelLink(678713:644:1): starting
2021-05-13 23:28:16.365 [INF] HSWC: Trimming open circuits for chan_id=678713:644:1, start_htlc_id=0
2021-05-13 23:28:16.365 [INF] HSWC: Adding live link chan_id=4b087f7e2a6b0032d549855f11ecc51e54c55216c1be0f0d621b1f47ece05b2
6, short_chan_id=678713:644:1
2021-05-13 23:28:16.365 [INF] CNCT: Attempting to update ContractSignals for ChannelPoint(XXXXXX:1)
2021-05-13 23:28:16.365 [INF] HSWC: ChannelLink(678713:644:1): HTLC manager started, bandwidth=2641778000 mSAT
2021-05-13 23:28:16.365 [INF] HSWC: ChannelLink(678713:644:1): attempting to re-resynchronize
2021-05-13 23:28:16.365 [INF] PEER: Negotiated chan series queries with XXXXXX
2021-05-13 23:28:16.365 [INF] DISC: Creating new GossipSyncer for peer=XXXXXX

2021-05-13 23:28:16.381 [INF] PEER: unable to read message from XXXXXX: EOF

2021-05-13 23:28:16.381 [INF] PEER: disconnecting XXXXXX reason: read handler closed
2021-05-13 23:28:16.589 [INF] DISC: Removing GossipSyncer for peer=XXXXXX
2021-05-13 23:28:16.589 [INF] HSWC: Removing channel link with ChannelID(XXXXXX)
2021-05-13 23:28:16.589 [INF] HSWC: ChannelLink(678713:644:1): stopping
2021-05-13 23:28:16.589 [WRN] HSWC: ChannelLink(678713:644:1): error when syncing channel states: link shutting down
2021-05-13 23:28:16.589 [INF] HSWC: ChannelLink(678713:644:1): exited

This is still happening and I cannot use my channel between lnd and clightning. And it is not only with me, I have two nodes that my clightning node connects to and it is the same. One of them is my lnd node.
Currently 0.13.1-beta on lnd side and clightning 0.10.1 on clightning side.


Move message templates to files, update settings enable events

Related issue: #31

Issue #25 will update in this issue


Predict impact of drafted message

Back End
Add to the messages list as if it were the last real message, and then only have 19 "real" messages to display + the predictive one?
Front End
Button inside the extension popup somewhere. Disappears once clicked.
When clicked, slide all messages up by one message slot.
Add in new message blob, opacity 50%.
Reset when they close the popup

Leaving this for v2.


H3 CLI Region Subcommands

Still as a draft because I've only hand tested some simple cases, and I know there's an issue with reading large polygon definitions from a file, but I wanted to get what I have up sooner rather than later so you can start taking a look at it.

coverage: 98.782%. remained the same
when pulling 31be7efd65b64b4f59caec22d2fc28078b64e09d on h3-cli-region-subcommands
into e8b16611b582275bdb9815bc5a80e0559a811758 on master.

I just ran this failure locally (set up CMAKE with the same configuration) and I can't reproduce it. @isaacbrodsky any idea what's going on here?


Support KSP 1.9.23-1.0.19

I've updated to

"com.google.devtools.ksp:com.google.devtools.ksp.gradle.plugin:1.9.23-1.0.19"
"com.google.devtools.ksp:symbol-processing-api:1.9.23-1.0.19"

And started to get :
w: [ksp] Unable to process:org.koin.compiler.BuilderProcessor:  ...

and koin-modules are not generated.
Probably because of newer KSP API than koin-annotations support (please, correct me if I'm wrong).
This is a proposal to support newer KSP API.

Error I've got probably has different cause. I'm still investigating.
Closing task for now.


#d2l add chapter 11.3 11.7 11.8 11.9 12.7 and update paddle.py

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

@an1018 已经修改完毕。

@an1018 修改完毕Pr已经更新。


Fix (ASAN-detected) stack overflow bug on NEON WT_8x8

                NNP_SIMD_ALIGN float block[8][8];
                for (float *block_ptr = &block[0][0], *block_end = &block[8][8]; block_ptr != block_end; block_ptr += 4) {
                                vst1q_f32(block_ptr, vzero);
                        }
                }

is broken, as the block_end is specified as &block[8][8] not &block[8][0]. This results in writes to the "invalid" indices &block[8][0] and &block[8][4].
Broken since https://github.com/Maratyszcza/NNPACK/commit/48cd8e08c69b828785a89460b8c5cf90f72b44b7

Thanks for the fix!


feat: pass base URL and subscription key as input parameter in instance creation

Notes
compare to base branch (SDKCF-3920) for now to limit the changes, will compare and merge to main branch after merging SDKCF-3920 PR
Checklist

[x] I have read the contributing guidelines
[x] I have not committed any secrets (passwords, tokens, internal urls etc.) or sensitive information
[x] I wrote/updated tests for new/changed code
[x] I checked that all possible internal and platform/library exceptions are gracefully handled and will not crash the host app
[x] I checked for open & known issues (especially crashes) for any newly added platform APIs or libraries
[x] I tested non-trivial changes on a real device
[x] I ran ./gradlew check without errors

Codecov Report

Merging #10 (4c7a2fd) into feature/SDKCF-3920 (43f638c) will decrease coverage by 0.11%.
The diff coverage is 100.00%.

@@                  Coverage Diff                   @@
##           feature/SDKCF-3920      #10      +/-   ##
======================================================
- Coverage               92.46%   92.34%   -0.12%
======================================================
  Files                       6        6
  Lines                     199      196       -3
  Branches                   31       32       +1
======================================================
- Hits                      184      181       -3
  Misses                      4        4
  Partials                   11       11

Impacted Files
Coverage Δ

...tentech/signatureverifier/RealSignatureVerifier.kt
89.65% <ø> (ø)

...rakutentech/signatureverifier/SignatureVerifier.kt
100.00% <100.00%> (ø)

...hub/rakutentech/signatureverifier/api/ApiClient.kt
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 43f638c...4c7a2fd. Read the comment docs.


impossible constraints of pythonPackages.trezor_agent and electrum

Issue description
electrum and trezor_agent both require the two packages:

keepkey which requires hidapi == 0.7.99.post15
trezor which requires hidapi >= 0.7.99.post20

The constraints are impossible to satisfy simultaneously.
Can we disable this madness entirely? Possible workaround besides downgrading?

9/10 times these specific versions are not required and are simply due to the developers using something like pip freeze (damn the person writing implementing that!).
I suggest you patch keepkey to remove the pinning to the specific version.

Something like this? https://github.com/rnhmjoj/nixpkgs/commits/hidapi

Yes, though instead of creating a patch a sed expression would likely be more easier to maintain here.


release 2.4.2

Update vendor properly this time.

@SuperQ @krasi-georgiev @brian-brazil

Looks like this is a serious issue: https://github.com/prometheus/prometheus/issues/4635
I ran 2.3.2 then 2.4.0/1 and both hit this:
err="opening storage failed: open e:\prometheus-data\wal\00000002: The system cannot find the file specified."`
I'm deferring the release until this is fixed.

@gouthamve btw I have done a wiki page for a reminder to myself how to update a vendored package.
https://github.com/prometheus/prometheus/wiki/Updating-a-vendored-package

@krasi-georgiev @brian-brazil @juliusv @fabxc @simonpasquier @grobie
This pulls in the WAL migration and corruption bugfixes from prometheus/tsdb.

Fixes #4635

LGTM


Adds URLContent interface

Pull Request Test Coverage Report for Build 7

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 43.401%

Totals

Change from base Build 5:
0.0%

Covered Lines:
342

Relevant Lines:
788

💛  - Coveralls


icon with name list clashes with list element in message element

If you use an icon name list in the message element, the CSS for the actual list element clashes and causes margin issues.
Here is a screen shot:

Here is the react code:
<Message
          icon="list"
          header="You haven't shortlisted any applications yet."
          content="Applications you shortlist because you like them, will end up here."
        />

And here is the overriding CSS as observed in Chrome browser:
.ui.message .list:not(.ui) {
    text-align: left;
    padding: 0;
    opacity: .85;
    list-style-position: inside;
    margin: .5em 0 0;
}

Apologies, I would like to try and fix this myself and submit a PR but I am on deadline and will just change icon for now.

Dear @chrispaynter,
I'd recommend you fork this jsFiddle and present a test-case for further analysis of the issue.
Since this is a usage question, I urge you to ask it in our Gitter channel or Discord Server
Closing till there's a test case.


getLoggedInUser keep returning null

// my getLoggedInUser()  the same with the original file
// I am debugging at line 8,9

Yeah, i figured out that, instead of return( get account(){return ...}), i do this


Missing WASM setup docs

I was trying to setup egui for a WASM project, and it took about 15 minutes of searching to find that I had to manually add getrandom as a dependency for it to work on WASM:
[target.'cfg(target_arch = "wasm32")'.dependencies]
getrandom = { version = "0.2", features = ["js"] }

If possible there should be clearer documentation for setting up on WASM, specifically for this issue. I had to look at commit 5514a8afda53c282d2be670bef657d5c7812d467 to find the solution.
Thanks!

I wonder if this could be solved by not using the (default) runtime-rng feature of ahash. That is: if the egui crates would have ahash = { version = "0.8", default-features = false, features = ["std"] }

Looks this is fixed, thanks!


env: always expand PATH vars

Make sure we always expand path env vars, even if they're REG_SZ in the registry.
Detailed Description of the Pull Request / Additional comments
On some systems path vars are REG_SZ instead of REG_EXPAND_SZ. We need to make sure we always expand them. We looked at the system code, and it also makes to sure to always expand them.
Validation Steps Performed
Built locally and made sure the problem went away. Also stepped through in the debugger to make sure things were working correctly.
Closes #15442

Thanks @sotteson1 for fixing this! Great find!

One might wonder why on some systems path vars are REG_SZ (containing candidates for expansion!) instead of REG_EXPAND_SZ in the first place, and why the Windows code does perform expansion on said REG_SZs...

PATH is probably the variable changed by the most installers, and so it gets exposed to all sorts of bugs.


Waypoint causing gap between fetched element count

This plugin is working fine but on fetch it leaves a padding like gap between the last fetched items and the next set in a vertical list. This makes lists look really weird and spaced oddly as one element is spaced much more than the others at the waypoint

Hi @rosman83! By default, the waypoint is rendered as a <span> element. As long as you keep that element outside of the list, it shouldn't affect styling.


Fix typo in cloud event resources documentation

Changes
According to the code the cloudEvent resources type is cloudEvent and
not cloudevent. cloud event resource tests.
This patch fix the type used in the documentation.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[X] Commit messages follow commit message best practices

@googlebot I signed it!

/ok-to-test


Include dict comprehension

dict comprehension is faster than using dict constructor

Thank you @boneyag for the contribution.


Support for Laravel 5.8

Already made a PR on MoeCasts fork, but it might be quicker to just make a new PR here.
You can delete this PR if another fix is merged.
Next version should probably be 1.1, since we drop support for previous php version.

I can confirm this PR fixes the event fire error.

I got the same issue while trying to upgrade to Laravel 5.8 and the PR fix it. Will it be available soon?

Approved but not merged....?
Would be great to get this merged in & released.

Any movement on this @hootlex? Thanks!

Some news about the pull request?

@hootlex hoping for a merge for Laravel 5.8 support!

Is the repo still maintained? Did someone else take over?

@kainxspirits - might as well update this PR to add Laravel 6.0 support as well ;)

@hootlex Please fill in these edits to support new versions of laravel


L515 not working in ubuntu 20.04 realsense-viewer

Hi,
I had followed the all the necessary steps to install realsense viewer for ubuntu 20.04
installation guide
but when I run the command realsense-viewer
it's not getting

Hi @Daya-AWR1642  If you used the distribution_linux.md guide then it is likely that the current latest 2.55.1 version of the RealSense SDK has been installed from dkms packages.
Support for L515 has been removed in 2.55.1 onwards as it is a retired camera model, so it is necessary to install the previous 2.54.2 SDK version in order to use L515 with it.
You can either build 2.54.2 from source code or use the showpkg command to find the filenames of the packages for the 2.54.2 version, as described at https://github.com/IntelRealSense/librealsense/issues/12892#issuecomment-2097781830

Hi @Daya-AWR1642  Do you require further assistance with this case, please?  Thanks!

No thanks

Thanks very much for the update!


20200316

Sorry. Wrong operation

@Fokatu Just curious, you closed it because it didn't work (I'd be curious why), or you didn't have time to polish it?

@leofang,  it works for me. But I am not familiar with github, I don't know how to contribute. The above is a wrong operation.

Thanks @Fokatu! If you could paste your scripts here for how you confirmed it's working, I could find some time to take over. I think it's in good shape, just needs tests, docs, and perhaps small style fixes.

it is great if you could add it to the main repository.
here is a small example
`import cupy as cp
write_surf_str = r"""
extern "C"
{
// Surface memory
global void write_surf(cudaSurfaceObject_t surf,
int width, int height)
{
int w = blockIdx.x * blockDim.x + threadIdx.x;
int h = blockIdx.y * blockDim.y + threadIdx.y;
	if (w < width && h < height)
	{
		float value = h * width + w;
		surf2Dwrite(value, surf, w * 4, h);
	}
}

}
"""
def create_texture(width, height):
format_desc = cp.cuda.texture.ChannelFormatDescriptor(32, 0, 0, 0,
cp.cuda.runtime.cudaChannelFormatKindFloat)  # always float32 format
cudaArraySurfaceLoadStore = 2
d_array = cp.cuda.texture.CUDAarray(format_desc, width, height, flags=cudaArraySurfaceLoadStore)
data = cp.zeros((height,width), dtype=cp.float32)
d_array.copy_from(data)
res_desc = cp.cuda.texture.ResourceDescriptor(
    restype=cp.cuda.runtime.cudaResourceTypeArray,
    cuArr=d_array
)

surf_obj = cp.cuda.texture.SurfaceObject(res_desc)

return surf_obj, d_array

write_surf = cp.RawKernel(write_surf_str, "write_surf")
width = 4
height = 4
img_surf, img_array = create_texture(width, height)
img_data = cp.zeros((4,4), dtype=cp.float32)
img_array.copy_from(img_data)
img_array.copy_to(img_data)
print("\nbefore write:\n", img_data)
grid_dim = (1, 1)
block_dim = (4, 4)
write_surf(grid_dim, block_dim, (img_surf, 4, 4))
img_array.copy_to(img_data)
print("\nafter write:\n", img_data)
`
the output is as follows:
`before write:
[[0. 0. 0. 0.]
[0. 0. 0. 0.]
[0. 0. 0. 0.]
[0. 0. 0. 0.]]
after write:
[[ 0.  1.  2.  3.]
[ 4.  5.  6.  7.]
[ 8.  9. 10. 11.]
[12. 13. 14. 15.]]`

Thank you, @Fokatu! I can reproduce.
import cupy as cp

write_surf_str = r"""
extern "C"
{
__global__ void write_surf(cudaSurfaceObject_t surf, int width, int height)
{
int w = blockIdx.x * blockDim.x + threadIdx.x;
int h = blockIdx.y * blockDim.y + threadIdx.y;

    if (w < width && h < height)
    {
        float value = h * width + w;
        surf2Dwrite(value, surf, w * 4, h);
    }
}
}
"""

def create_texture(width, height):
    format_desc = cp.cuda.texture.ChannelFormatDescriptor(32, 0, 0, 0,
        cp.cuda.runtime.cudaChannelFormatKindFloat) # always float32 format
    cudaArraySurfaceLoadStore = 2
    d_array = cp.cuda.texture.CUDAarray(format_desc, width, height, flags=cudaArraySurfaceLoadStore)
    data = cp.zeros((height,width), dtype=cp.float32)
    d_array.copy_from(data)

    res_desc = cp.cuda.texture.ResourceDescriptor(
        restype=cp.cuda.runtime.cudaResourceTypeArray,
        cuArr=d_array
    )

    surf_obj = cp.cuda.texture.SurfaceObject(res_desc)

    return surf_obj, d_array

write_surf = cp.RawKernel(write_surf_str, "write_surf")

width = 4
height = 4
img_surf, img_array = create_texture(width, height)

img_data = cp.zeros((4,4), dtype=cp.float32)
img_array.copy_from(img_data)

img_array.copy_to(img_data)
print("\nbefore write:\n", img_data)

grid_dim = (1, 1)
block_dim = (4, 4)
write_surf(grid_dim, block_dim, (img_surf, 4, 4))
img_array.copy_to(img_data)
print("\nafter write:\n", img_data)


adds specific version for when tmux's version is 'master' (99.9)

In https://github.com/tmuxinator/tmuxinator/issues/524#issuecomment-312065082, commenter @techgaun makes a good point about tmux master not failing (IIRC there was an issue for this item specifically, but I can't seem to find it ATM).  This creates an admittedly-arbitrary numeric value (99.9) to enable downstream invocations of Tmuxinator::Config.version to return a sensible value
Context
Currently, if tmux is built from scratch from the master branch, tmux -V returns tmux master, which resolves numerically to 0.0.  This is both factually incorrect (as of this writing, tmux's master branch is based off of 2.5) and misleading (as it implies that master is an older version than, say 2.5).  I'm open to other suggestions on how to deal with this, but figured this is a relatively easy solution (again, I think I saw someone else suggest it; they deserve the credit).
The use of 99.9 is, as indicated, clearly arbitrary.  My thinking is that it's fair to assume that master should be considered as equal-to-or-greater-than the highest published version, and that, for tmuxinator's purposes, as detecting same is to handle "API" changes as tmux ages, this should be sufficient.  Again, open to other ideas here...

I don't actually expect tmux to publish a version higher than 99, but Float::INFINITY might be a slightly better arbitrary value.
Is it correct to treat master as a numeric version at all, though? Depending on how frequently the user pulls from upstream, master may be ahead of or behind any given release.

Good point re: Float::INFINITY.  Will hold off on implementing until we decide the larger issue: is this a good plan, or should we do something else (as @rglassett states, perhaps it's not a great idea)?

Depending on how frequently the user pulls from upstream, master may be ahead of or behind any given release.

I think this is an important point.
Also, as I mentioned in #524, trying to support bleeding-edge master is problematic. Since Tmuxinator's test suite won't have been run against the latest feature set, there's no way to guarantee compatibility.
What would you all think about adding a supported version range check (again, per #524) and allowing people to use unsupported versions, but printing a warning message which tells them here be dragons if they're outside of the range?

A version range check with warnings sounds reasonable to me, and it seems fine to treat master as an arbitrarily high version number in that context.

Closed in favor of https://github.com/tmuxinator/tmuxinator/pull/574


ZBDongle-P fails to start after upgrading from Conbee 2 Stick

Description of the issue
Hey,
i wanted to upgrade to a ZBDongle-P stick from Sonoff because it should work better, faster and with more reach than the Conbee II stick.

I stopped Z2M
Unplugged Conbee II stick
Plugged ZBDongle-P stick
deleted/changed serial configuration and added the new ID of the sonoff stick from hardware/allhardware
Started the addon

Addon fails to start.
serial config:
port: /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0
#port: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2667712-if00
#adapter: deconz
Of cause i also tried it with port: /dev/ttyUSB0 - no luck
I tried reinstalling the addon - no luck
I tried reinstalling mosquitto - no luck
Are there any special steps or is the current version of Z2M just broken as it should work out of the box?
I don't think there is anything wrong with the configuration as it was working before. I now switched back to the Conbee stick, but i prefer the SonOff if it's supported.
Addon version
1.30.1-1
Platform
Home Assistant 2023.2.3
Supervisor 2023.01.1
Operating System 9.5
Frontend 20230202.0 - latest
Logs of the issue (if applicable)
[18:00:51] INFO: Preparing to start...
[18:00:51] INFO: Socat not enabled
[18:00:52] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:error 2023-02-10 18:01:03: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-02-10 18:01:03: Failed to start zigbee
Zigbee2MQTT:error 2023-02-10 18:01:03: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-02-10 18:01:03: Exiting...
Zigbee2MQTT:error 2023-02-10 18:01:03: undefined

Can you provide the herdsman debug log of this?
See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable the herdsman debug logging. Note that this is only logged to STDOUT and not to log files.

Hello @Koenkk ,
i will provide the logs tomorrow. I tested the same dongle on my RPI 3 at home. It was working without any issues on first try.
We are using a Lenovo M710 in our company as HA server, maybe that's a critical point.
I will let you know.

Notice to myself: Read the correct instructions for migrating to a different adapter. https://www.zigbee2mqtt.io/guide/faq/#how-do-i-migrate-from-one-adapter-to-another
I wasn't aware that such an article exist.
After deleting all files in config/zigbee2mqtt/ and reconfiguration of the Z2M configuration i could start the addon and add all devices to Z2M.
Sorry


Update baseimage as for tagging strategy (v0.1)

ADO#15208
Describe your changes

Issue ticket number and link

Checklist - Manual tasks

[ ] Examples are executing successfully
[ ] Created/updated unit tests. Code Coverage percentage on new code shall be >= 80%.
[ ] Created/updated integration tests.
[ ] Devcontainer can be opened successfully
[ ] Devcontainer can be opened successfully behind a corporate proxy
[ ] Devcontainer can be re-built successfully
[x] Extended the documentation (e.g. README.md, CONTRIBUTING.md, Velocitas)

done with #100


Fix duplicate word occurrences

It looks like autodidax.ipynb needs the same change as the associated md and py files.

Oh, I missed that. Fixed. This time I did more thorough search using this magical regex \b(\w+)\b \b\1\b and fixed bunch of other places too :smile:

Thanks! It looks like there are some conflicts in this branch – can you fix those, and then also rebase your changes into a single commit? (see https://jax.readthedocs.io/en/latest/contributing.html#single-change-commits-and-pull-requests) Thanks!

Rebased and changes squashed to single commit.


Created common use passing data to and from elements

Hopefully the explanation is in the format you want.  Let me know if you want something changed.

@munsterlander Thanks for the PR! I will review this soon. It's also necessary to modify modules.js to add this file to the dictionary since we don't have a server :smile:
I'll do that, don't worry!

@frankdiox I did not know about that file, but I do now!  In the future, I can modify as well.

@munsterlander Here it is :)
I named it Passing data outside Onsen UI because at least for ons-navigator there is actually a way to pass data within the framework itself, with the data object. Also I did some minor changes to the code.
For the next time, you can just clone this repo and serve it. It's completely standalone so you can test the result in local.

Sweet!  I came close to throwing in passing data in the options block but I thought the reference docs did  a pretty good job explaining that and I was afraid to make it too big.  It could be added if you think it is necessary though or my method is a poor way of doing it.  I know in the forums we have talked about globals, outside passing, and other pros / cons of this way.


Determine semantics for function overloads

Function overloads would provide a simpler alternative to TTL that we could potentially support in NTI, and would allow correctly and precisely typing many functions that are currently underspecified.
I can think of several potential use cases, which we should consider while defining any semantics:
function then(this: Promise<T>, T => Promise<U>): Promise<U>
function then(this: Promise<T>, T => U): Promise<U>

This is currently implemented via TTL.
function map(IArrayLike<T>, T => U): Array<U>
function map(string, string => U): Array<U>

This could potentially be worked around with a string ~ IArrayLike extern, but that's kind of nasty.
function assertThrows(string, function())
function assertThrow(function())

It would be nice if assertThrows(function(){}, function(){}) failed to typecheck.
function get(Object<V>, string, R): (V|R)
function get(Object<V>, string): (V|undefined)

This might already work in NTI, but the problem with the current implementation is that the R template type is effectively free if the optional argument is missing, which means that the function is effectively allowed to return anything without complaint, when we would like to say R=undefined always if the optional argument is missing.
I propose the following semantic.  Given a set of overloads, figure out which function signatures are assignable to which other signatures, provided that ? is mapped to * in all parameter types and to ⟂ in all return types.  If a function type with signature f is assignable to a function type with signature g (e.g. f(string|number, *): number is assignable to function(string): ⟂) then g is said to be a refinement of f.  When selecting overloads, find all overloads that could possibly match the currently-inferred argument (and return?) types, using the same temporary */⟂ substitution scheme.  Compare the matching overloads pairwise and if any match is a refinement of another match, then discard the less-refined match.  Now take the union of each parameter across the remaining matches to use for the inferred type of the unknown parameters (and the intersection of the return types?).  This scheme has the advantage that it is independent of declaration order.  But I'm not at all convinced it's actually sane, or sound.  In particular, I'm very unsure about the return types' variance, and could potentially be convinced that they should have the same variance as the parameter types.  I haven't worked through these examples thoroughly yet, but that's probably the next step.

@blickly @dimvar


#143304217 Defense 2 Feedback Implementation

What does this PR do?
Implements part of defense 2 feedback
What are the relevant pivotal tracker stories?
#143304217

Codecov Report

Merging #29 into develop will increase coverage by 1.41%.
The diff coverage is 50%.

@@             Coverage Diff             @@
##           develop      #29      +/-   ##
===========================================
+ Coverage    89.52%   90.93%   +1.41%
===========================================
  Files           17       17
  Lines          334      331       -3
  Branches        67       65       -2
===========================================
+ Hits           299      301       +2
+ Misses          35       30       -5

Impacted Files
Coverage Δ

server/db/seeds/DocumentSeed.js
100% <ø> (ø)
:arrow_up:

server/models/User.js
100% <100%> (ø)
:arrow_up:

server/controllers/UserController.js
87.91% <33.33%> (+3.86%)
:arrow_up:

server/controllers/DocumentController.js
78.08% <0%> (+1.36%)
: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 0bade33...72d4431. Read the comment docs.


Is this plugin still maintained ?

Hi,
this plugin is very interesting  and useful.
Some pull requests  like streamlogs would be great to be approved but there is no more activity on this plugin for almost 1 year.
There's also no response on "recent" issue.
Shall we use this plugin ? is there another solution ?
thanks  for your time

@bwkimmel @bendory Can you comment on this? I mean, the answer is obvious: it’s abandoned. A bit surprising, since Google Cloud Build integration would be such a valuable and obvious feature for Google’s apparent interest in Jenkins on GCP.
Having to go one abstraction layer deeper and use the GCE plugin to provision VMs seems outdated in comparison (but that plugin seems active).

hi !
i saw recent activity on this plugin, @tequilarista @donmccasland  !
is there any chance that the pull request  : https://github.com/jenkinsci/google-cloudbuild-plugin/pull/10
"Streaming build log" will be merged ?
thanks for your help !

As they don't accept PRs and latest commits are just security version bumps I purpose a fork.


Add Spyke Lionel to 2023 dir

Create README.md

Tasks
Getting started with Outreachy

[x] Read the official Outreachy Applicant Guide. All of it.
[x] Read the official Outreachy Internship Guide.
[x] If you haven’t already, create a GitHub account.
[x] Introduce yourself on our Welcome to Wagtail! Introductions discussion thread.
[x] And-or introduce yourself on the Wagtail Slack in #new-contributors.
[x] Set up your own personal blog. Blogging is a fundamental part of Outreachy, and generally a good way to solidify learnings. You can use a personal website if you want to, or keep it simple and use a platform like Dev.to, Hashnode, or Medium.

Open Source Contributions

[x] Read through How to contribute to open source
[x] Read Open source etiquette
[x] Make your first pull request with us! Add your name to the list of participants in 2023/README.md.

Your contribution period with Wagtail

[x] Make a fork this repository, then add a new folder inside 2023/ with your name as the folder name. Inside that folder, add a README.md file, and copy-paste the introduction you posted earlier. Submit this to our project as a pull request.
[x] Read through GitHub’s Markdown formatting documentation
[x] Now make another pull request to your own README file, adding a Markdown table with links to:

[x] Your GitHub profile
[x] Your personal website / blog
[x] Your preferred social profiles if any

[x] Update your pull request to add a new ## Tasks section to your README file, and copy-paste our contributor guide’s checklists into it, marking each item as completed or not according to your progress.

To stand out as an applicant,

[ ] Help others with their pull requests – spotting steps they might have missed, or suggesting improvements to their pull requests.
[ ] Demonstrate good awareness of open source etiquette when creating your pull requests (for example, adding an appropriate title and description, even if very concise).

Interest in learning
With this checklist, we expect you to demonstrate an ability to do research and learn new things. All tasks here will require updating your participant file within your fork of the outreachy repository in the 2023/ folder, and making pull requests.

[x] Create a new ## Research section in your personal file, with a list of links to the resources you’ve found most useful so far in trying to understand Wagtail as a project and the specific project idea(s) you’re interested in. Make sure to use full Markdown link syntax ([link text](link url)), so we can understand your choice of resources.
[x] Write a short blog post describing things you’ve learned recently, and share it with us. The post must be in English, include at least one image, be less than 500 words, and score a Grade 7 or better on https://hemingwayapp.com/. You can describe any recent learnings – share a list of the last few articles you read and liked, or focus on one specific thing you’ve been learning. It can be a broad area or a very narrow subject. It doesn’t have to be about tech. The post has to be posted on a publicly-available platform (Dev.to, Hashnode, Medium, your own website), and you must also add it as a new section in your personal file in this repository (so we can provide feedback on the contents).

Wagtail.org website accessibility

[x] Write a short blog post which demonstrates your understanding of accessibility. In English, with at least one image, less than 500 words. Demonstrate your understanding based on past experiences. For example, any specific accessibility improvements you’ve done in the past, or specific issues you identified. The more specific the better. The post has to be posted on a publicly-available platform (Dev.to, Hashnode, Medium, your own website), and you must also add it as a new section in your personal file in this repository (so we can provide feedback on the contents).
[x] Write a short blog post which demonstrates your understanding of Django, in less than 500 words. This can be an intro to an existing project of yours, or perhaps explanation of a specific code snippet you’re particularly proud of, or explanation of a specific problem you worked on. The more specific to your own experience the better. The post has to be posted on a publicly-available platform (Dev.to, Hashnode, Medium, your own website), and you must also add it as a new section in your personal file in this repository (so we can provide feedback on the contents).
[ ] Go through Wagtail’s tutorial: Your first Wagtail site. If you get stuck, ask for help on Slack or GitHub Discussions.
[X] Set up wagtail.org in Gitpod, via the "Open in Gitpod" link in the README.
[ ] Find an accessibility issue on the live wagtail.org website, and report it on the project’s issue tracker, with appropriate details (title, description, screenshot if applicable, why you think this is an accessibility issue).
[ ] Fork the wagtail.org repository and set up your own copy for development, either in Gitpod or on your own computer.
[ ] Contribute a solution to the issue you selected, by reproducing it on your copy of the project, and submitting a pull request to the main project.
[x] TBC – Additional tasks specific to the Outreachy application process.


Fixed formatting in hyper-v-vmm-performance-results.md

Primary site and Server Workload tables has formatting issues that made the tables difficult to read.
I've updated the the table formatting to make it more readable.

@comnam90 : Thanks for your contribution! The author, @sujayt, has been notified to review your proposed change.

Close/reopen for fresh validation post-migration.

@sujayt Sujay please sign off. thx

@sujayt Please review and sign off. Thx


Update dependencies and Actions

Update dependencies.
Update Actions.

@asimonok Should we updated as well?
% npm outdated
Package                        Current         Wanted  Latest  Location                              Depended by
@tanstack/react-table            8.9.3          8.9.3  8.13.2  node_modules/@tanstack/react-table    volkovlabs-variable-panel
@tanstack/react-virtual  3.0.0-beta.60  3.0.0-beta.60   3.1.3  node_modules/@tanstack/react-virtual  volkovlabs-variable-panel

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.21%. Comparing base (16a9882) to head (3c24e11).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #120      +/-   ##
==========================================
+ Coverage   98.25%   99.21%   +0.96%
==========================================
  Files          51       51
  Lines         916     1017     +101
  Branches      194      243      +49
==========================================
+ Hits          900     1009     +109
- Misses          3        8       +5
+ Partials       13        0      -13

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


Use chef/chef image instead of downloading from packages.chef.io

Description
Since we use kitchen-dokken, we are downloading the chef Docker image. To avoid downloading the Chef binary from packages.chef.io as well, use the chef/chef:current image available on the Docker Hub instead.
Issues Resolved

Excess bandwidth spent downloading duplicate Chef packages

Check List

[ ] New functionality includes tests
[ ] All tests pass
[ ] RELEASE_NOTES.md, has been updated if required (not required for bugfixes, required for API changes)
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Signed-off-by: Tom Duffield<EMAIL_ADDRESS>

looks correct to me, merge when green...


Bebop ffmpeg vision demo  not working

I am trying to get pictures live from the bebop2 and followed the docs. It went well until the "Bebop ffmpeg vision demo" code. I get the following error:

(executing file "pyparrot2.py")
Setting up mDNS listener since this is not a Mambo
Making a browser for _arsdk-090c._udp.local.
Service Bebop2-038622._arsdk-090c._udp.local. added, service info: ServiceInfo(type='_arsdk-090c._udp.local.', name='Bebop2-038622._arsdk-090c.udp.local.', addresses=[b'\xc0\xa8*\x01'], port=44444, weight=0, priority=0, server='Bebop2-038622.local.', properties={b'{"device_id":"PI040384AG6I038622"}': False})
{"d2c_port": 43210, "controller_type": "computer", "controller_name": "pyparrot", "arstream2_client_stream_port": 55004, "arstream2_client_control_port": 55005}
{'status': 0, 'c2d_port': 54321, 'c2d_update_port': 51, 'c2d_user_port': 21, 'qos_mode': 0, 'arstream2_server_stream_port': 5004, 'arstream2_server_control_port': 5005}
c2d_port is 54321
starting listening at
Success in setting up the wifi network to the drone!
51
c:\programdata\anaconda3\lib\site-packages\pyparrot\images
c:\programdata\anaconda3\lib\site-packages\pyparrot\utils
removing all the old images
Opening ffmpeg
ffmpeg -protocol_whitelist "file,rtp,udp" -i c:\programdata\anaconda3\lib\site-packages\pyparrot\utils/bebop.sdp -r 30 image%03d.png
starting vision thread
Opening non-blocking readers
'ffmpeg' isn't recognized as an internal command
Traceback (most recent call last):
File "C:\Users\alpha\Desktop\Informatique\TIPE\pyparrot\pyparrot2.py", line 36, in
success = bebopVision.open_video()
File "c:\programdata\anaconda3\lib\site-packages\pyparrot\DroneVision.py", line 146, in open_video
line_str = line.decode("utf-8")
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x82 in position 27: invalid start byte
timeout - trying again
timeout - trying again
timeout - trying again

and it keeps looping on "timeout - trying again"
What did I do wrong ? Btw, is there any command that only takes and sends pictures without starting a video stream ?
Thanks,

No, there is not a photo command for the bebop.  Did you install ffmpeg?  That's the error I see.

I did it twice to be sure, once with pip and then with the official website. But nothing changes. Is this error related to the file's path (directory names) ?
https://stackoverflow.com/questions/22216076/unicodedecodeerror-utf8-codec-cant-decode-byte-0xa5-in-position-0-invalid-s
Shall I edit the pyparrot code this way ?

The error is here:
'ffmpeg' isn't recognized as an internal command

NOT the utf error.  ffmpeg never starts!  You need it to be in your python path somehow.

Thank you it finally worked ! The issue was with the ffmpeg release, that had to be zeranoe's.

well I've had another problem:
[h264 @ 00000283ab0dccc0] decode_slice_header error
[h264 @ 00000283ab0dccc0] non-existing PPS 0 referenced
is looping in the shell.

ffmpeg prints out a LOT of messages.  And sometimes it takes awhile to get a keyframe.  I'd say just be patient.  They are sent every 5-10 seconds and I've seen the stream take ~20 to start sometimes. Since you are on a bebop, the best thing is to move to 5Ghz if your laptop supports it.  It drops a LOT less frames than 2Ghz.


Feature Request: Treat Warnings as Errors in certain configurations

We are currently switching from StyleCop Classic to Analyzers.
With StyleCop classic, we configured our projects, so that StyleCop issues were displayed as warnings during debug, and as errors during release builds. That way, we could work a bit easiering while developing and still could enforce the rules in the release build.
We would like some similiar setting for StyleCop Analyzers. Is anything like that planned?

That would be outside the scope of the project, but you could achieve this in two ways:

Enable the "Treat warnings as errors" within the project settings for release builds.
Use specific (custom) rule sets, where the debug rule set would contain warnings and the release rule set would contain errors.


Rift: Minting 4 items - error

Minting 4 NFTs at once: https://kodadot.xyz/ahp/drops/rift
Got this error. Tried again 4 NFTs got this error again.

https://github.com/kodadot/nft-gallery/assets/104380776/f5eb6be4-7b17-4284-a8c3-c7f91f24abb2


Add command line arguments with runner

Hi,
I'm running on python3 Ubuntu 14.04. With the argparser module I execute my script by:
./script.py --input /path/to/input
How do I tell runner to use "--input /path/to/input"?
Cheers

Runner doesn't really support adding command line arguments, it's meant as an interactive way to run small scripts while you edit them for "testing".
One thing you can usually do in these situations is to fake the command line arguments in your scripting environment. Something like:
sys.argv = ['new', 'arguments', 'here']

Closing since a workaround is supplied.


History Settings - Log Character Leaves cannot be turned off

The Character Leaves are always logged and shown even if the setting is off.
Below are the HistorySetting, Gameplay Screenshot and Timeline.

Below is from History.gd.
# See if we're logging arrivals and exits
	logArrivals = get_parent().settings.get_value('history', 'log_arrivals', true)
	logExits = get_parent().settings.get_value('history', 'log_exits', true)
                                                      //This get_value.() will always fail and return the default "true" argument.
	if logExits or logArrivals:
		eventsToLog.push_back('dialogic_002')

I have no idea how to fix it. I assume the get_value failed to find the 'log_exits' in the settings, but I don't know how to read, or where to read the setting field names.
The arrival counterpart is working perfectly.

Fixed with #1937


[Feature request] homebrew package

Easier to install and mantain under macos
thanks

Don't forget the man page:
ln -s ~/fff/fff.1 /usr/local/share/man/man1
P.S. I am also in favour of porting it to the home brew package managers under macOs

Any update on this?

@dylanaraps see https://github.com/Homebrew/homebrew-core/pull/35994 for updates

I'm aware. I've posted twice in the homebrew repo asking for an update to the PR. I'm asking back in this repo to not clutter theirs. The PR has been inactive for over 14 days now. I'd open a new PR myself but homebrew's guidelines disallow this if there's already an open PR.

@dylanaraps don't clutter this one too then, maybe you should wait for their response

fff 2.1 has been merged into homebrew-core


Writing our first Vamp-IR examples

As far as I understand, the goal of Vamp-IR is to be able to use complicated circuits in a simple way. I would like to have a practical example with a "complicated" circuit. For example, we can consider a hash function circuit, very useful for ZK proofs applications. Depending on your curve system, you can use Poseidon over:

the scalar field of bls12_381 using ZK-Garage implementation,
the scalar field of vesta using Zcash implementation.

The circuit can be designed differently depending on the implementation. For example it could either compute the hash and output it as a variable, either (given input and output) check that output is the hash of input. Using Vamp-IR, the user doesn't care about this implementation detail and is able to create the circuit in a simple way like:
// this is vamp-ir code
output = Poseidon(input)

(somewhere, the user needs to decide on the backend: Zcash or ZK-Garage)
My questions:

Can we already do this kind of example with Vamp-IR?
What is needed to achieve this example?
Do we need Juvix at some point for this?

Hi, there is now a balke2s hash in the repo, that can be used as a Vamp-IR example


Preferences dialog not opening

After pressing the Tools->Preferences button this error appears:
Error
An error occurred. Please start Anki while holding down the shift key, which will temporarily disable the add-ons you have installed.
If the issue only occurs when add-ons are enabled, please use the Tools > Add-ons menu item to disable some add-ons and restart Anki, repeating until you discover the add-on that is causing the problem.
When you've discovered the add-on that is causing the problem, please report the issue on the add-on support site.
Debug info:
Anki 2.1.47 (dc156f34) Python 3.9.7 Qt 5.15.2 PyQt 5.15.4
Platform: Linux
Flags: frz=False ao=True sv=2
Add-ons, last update check: 2021-09-30 21:41:54
Add-ons possibly involved: anki-forvo-dl - Forvo Pronunciation Downloader fully automatic

Caught exception:
Traceback (most recent call last):
  File "/home/yannicko/.local/share/Anki2/addons21/858591644/__init__.py", line 226, in on_pref_btn_click
    config_manager = ConfigManager(config)
  File "/home/yannicko/.local/share/Anki2/addons21/858591644/src/ConfigManager.py", line 123, in __init__
    self.nt_selector.addItem(str(next(nt.name for nt in self.mw.col.models.all_names_and_ids() if nt.id == nt_id)), nt_id)
StopIteration

Thanks for the report! I'll have a look.


Include the generated API documentation directly on the API page

This should make the API documentation slightly quicker to access for users by removing an extra click. Moreover, it makes the API documentation blend in with the rest of the website/theme (one of the points in #6526).
Fixes #18249.

/botio-linux preview

You can view the new version here: http://<IP_ADDRESS>:8877/6bf7801764fe89b/api/