text:
[DoubleCross]面数指定なしのダイスをを10面に変更

問題点
「3D」のように面数を省略したとき、今までは6面ダイスが振られていたが、ダブルクロス2nd,3rdにおいては、使用するダイスは10面である。
変更内容
sides_implicit_dに10を指定することで、面数を省略したときに10面ダイスが振られるようにした。

影響が大きいので提案はとどまっていたのですが、最近ダブルクロスしたり、プレイヤーに聞いても10面ダイス標準で問題なさそうですので賛成します。
なにかのはずみでエディタが追加して、別PRに紛れる可能性があるので今のうちに末尾改行はあったほうが良いかと思います。

source: gharchive/pull-request

repo: bcdice/BCDice

license_type: permissive

license_source: github-api


text:
Application - Create a basic form

Actor

External User - Applicant

Screen

Create Application

Fields

Phase (default:  1)
Application Number* (format: CCBC-99999,  with random numbers)
Status* = Draft
Created date* = now
Question 1* (textbox)

Validations

Application number is unique.
*Mandatory

Actions

Save (blocked by #56)
Cancel

PS: We will improve this form in a near future.

Here is a link to our Figma wireframes https://www.figma.com/file/nhOquOVmWD1P3BxEY0KIh5/CCBC-Intake?node-id=0%3A1

@rgreensp , can you confirm the structure of the "Application Number"?

Form issue list:

"Other" option for org type, having the text input there may be difficult (don't know how)

Form issue list (for designer discussion):
Budget page:

drop down menus 'status of funding' and 'funding type' do they have more options available?

Trying to fix form issues - BLOCKED by #82

Hey team! Please add your planning poker estimate with ZenHub @BryanGK @marcellmueller

source: gharchive/issue

authors: BryanGK eazeredo wenzowski zoeyli-46

repo: bcgov/CONN-CCBC-portal


text:
Task: Update the ordering/grouping inconsistencies noticed between the wireframe and implementation

Describe the task
This ticket is for updating the ordering/grouping of fieldsin the CIF app to reflect the latest design, and goes hand in hand with #1029 (suggested to be completed first so that we have the accurate labelling in the app) which addresses field/button labelling inconsistencies between the wireframe and implementation.
Acceptance Criteria
(Fully refined by @nanyangpro, reach out if having questions.)
Budgets, Expenses & Payments

[x] Move the "Contract Start Date" and "Project Assets Life End Date" fields to the top, i.e. above "Maximum Funding Amount".
[ ] ~Move the "Total Project Value" and "Anticipated/Actual Funding Amount" fields to the bottom, i.e. below "Additional Funding Sources".~ captured in #1129

Emissions Intensity Report Form

[x] Group "GHG Emission Intensity Performance" and all the fields below with label "Upon Completion".

Additional context

Based on yesterday's (Sep 22) discussion with @nanyangpro

This ticket #1101 and #1029 (suggested done first) should go hand in hand. They are both fully refined addressing inconsistencies between design and implementation across the app instead of just for one form.

The second item will require a similar refactor to the milestone form, and should probably be split up in a separate card

Thank you @sam-warren! Verified in dev:

Contract start date and project assets life end date now displayed at the top
GHG fields now captured within a 'upon completion' frame

authors: LindsayMacfarlane Sepehr-Sobhani nanyangpro pbastia

repo: bcgov/cas-cif


text:
As a CIF user, I want to sort the projects by milestone due date, so that I can see which project needs attention next

Description:
Missing piece from #469, we need to be able to sort by next requirement due date

note: the search filed is not applicable here
Acceptance Criteria:
Given I am a CIF administrator
When I am on the projects lists page
Then I can sort the projects by next requirement due date
Development Checklist:

[x] The table header should use a SortableHeader in combination with a SortOnlyFilter
[x] a computed column project_next_milestone_due_date returning the next milestone due date for a project
[x] project_next_milestone_due_date is configured with sortable: true in postgraphile.tags.json5
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

Hey team! Please add your planning poker estimate with ZenHub @BCerki @dleard @gurjmatharu @matthieu-foucault @mikevespi @Sepehr-Sobhani

@LindsayMacfarlane we just need a priority tag on this one

Thanks @pbastia - I gave this one a high priority; however, if we are crunched for time to meet our release goals this can always wait until just after our first release.

Note: if we complete this ticket, we can wrap up the Milestone EPIC :)

Hi @sam-warren - just checking in on the status of this ticket. Do you need any support?

@LindsayMacfarlane It is ready for review :)

Thank you @sam-warren - just double checking based on the acceptance criteria - should I also be seeing a filter?

@LindsayMacfarlane filtering dates is much more complicated than a single field (date ranges? selecting inside or outside the range? ...) and provides little value in terms of usability, so our tables don't support it at this time. The original screenshot in the ticket is erroneous, and this card is only about the sorting

Thanks for that clarification @pbastia!

authors: LindsayMacfarlane pbastia sam-warren


text:
Modify the How to document and the instructions to create new project sets

Describe the Issue
The permanent TF token have been cancelled and instead ephemeral ones are used to create new project sets.
This ticket is to get acquaint with the new procedure and rewrite the instructions to create a new project set
Additional Context
It will require a meeting with the Tech team, probably with Max or Warren
Acceptance Criteria

A meeting with the tech team to learn the new procedure
Rewrite the How To document (equivalent to rewrite the test steps)
Upload the documents into the Teams folder.

Document finalized. It now reflects the new deployment procedure, with two separated PR. The location of the document is the same CFP Scrum Team > 003 Quality Assurance > How to

repo: bcgov/cloud-pathfinder


text:
Review expiring cloud certificates and determine next steps

Describe the issue
We acquired a set of certificates last year prior to having our current landing zones/tenancies, etc.  We received notices that these will be expiring in early April.  We have not used these certificates thus far, but we may still have a need these going forward.  We should review our anticipated work related to SSL Termination and make a decision whether to renew some/all of these.
Which Sprint Goal is this issue related to?

Note: 'Milestone' is a ZenHub term that we use synonymously with 'Sprint'.

The 'Milestone' description (created in ZenHub) should clearly list Sprint Goals. This section should indicate which 'goal' this issue is related to.
Additional context
Definition of done
Decision whether we need to renew certs.  If yes, ticket(s) related to renewals. If not, no-op.

Decision not to use (due to capacity).  Make ticket to create new ones later if needed.

authors: ActionAnalytics sheaphillips


text:
check for undefined TagSet

Description

handle TagSet when undefined in S3 GetObjectTaggingCommand() response.
steps to reproduce:
mount add an empty Dell s3 bucket to coms
upload a new file using S3 Browser/cyberduck
call coms sync for the bucket.
console shows error, new object not synced

other coms endpoints that use this command but because we add coms-id tag by default, issue did not present.

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have checked that unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

Superceded by #204

authors: TimCsaky jujaga

repo: bcgov/common-object-management-service


text:
Django 4.0 upgrade.

Django 4.0 upgrade.

Probably need to reinstall pip -r "requirements.txt" under api for this.

repo: bcgov/court-of-appeal


text:
Tekton Pipeline Tutorial

Create a tekton basic tutorial

understanding triggers
understanding templates
understanding tasks
understanding pipeline

@ASpiteri-BCGov not sure if you want to create a tutorial on pipelines, the scope doesn't have to be exactly followed, but this might a good way to crowd source our training tutorials.

repo: bcgov/des-training


text:
As a member of the public, I want to learn more about each phase of the engagement in the Engagement Phases widget (Desktop)

As a member of the public, I want to learn more about each phase of the engagement in the Engagement Phases widget (Desktop)
Acceptance Criteria:
Member of the public accesses an Engagement page with the engagement widget on it.
Matches wireframe:
https://xd.adobe.com/view/d0671e99-d506-4ed5-b51e-2bf6e3fcb523-8534/screen/b6e74f21-2177-475b-a224-42fbcbbeb0be
Title: The EA Process
Text:  Click on the sections below to expand them and learn more about each EA process phase. You can also learn more about each engagement period by clicking the engagement icon.
Include the following text in the arrow above the graphic:
Engagement and consensus-seeking with participating Indigenous nations occur at each stage of the process, supported by dispute resolution at certain stages if required.
Sections are clickable and each one opens a box with the description (static) of the phase.
Text as on PDF:
https://app.zenhub.com/files/480383041/ddd4fc0f-35c3-4abf-9e27-3110a3579db7/download
Matches wireframe:
https://xd.adobe.com/view/d0671e99-d506-4ed5-b51e-2bf6e3fcb523-8534/screen/778f3bf2-c219-4d57-bdab-0de013a839ec
Each Engagement icon is clickable, opens a box with the following text for each engagement:
TBD
Matches wireframes:
https://xd.adobe.com/view/d0671e99-d506-4ed5-b51e-2bf6e3fcb523-8534/screen/a2eb4142-b5a9-4add-b0d3-c65a5139f1dc

@marieanik to provide the mockups

@saravanpa-aot

Hey team! Please add your planning poker estimate with Zenhub @djnunez-aot @jadmsaadaot @saravanpa-aot @VineetBala-AOT

verified and closed, created a bug regarding. the "selected" phase

authors: marieanik tiagograf-AOT

repo: bcgov/met-public


text:
More changes

Group Select maximum text change
Address on NFR page display change
Added Mandatory provision logic & table column, user can no longer generate a document if all mandatory provisions have not been selected.
Added the option for groups to have no maximum and updated frontend for that change
Variable 'Value' column header changed to 'Enter Text'
Interested parties now populates from tenantAddr array, it seems that there will either be a legalname or a first/middle/last but not both so the way interested parties are displayed should probably change.

Your Pull Request code is being promoted!  Please follow the link below.
Main Merge Workflow

authors: barrfalk mgtennant

repo: bcgov/nr-ticdi


text:
Basic Message Storage plugin

Signed-off-by: Jason Sherman tools@usingtechnolo.gy

Can rebase in from develop to fix the resource strings I believe

authors: loneil usingtechnology

repo: bcgov/traction


text:
Fix unlocked slots in advanced inscriber

top and bottom slots now can be pulled when machine is being idle instead of being busy.

Fix #169

Thanks for this, from 3 years later.

authors: spikespaz zhykzhykzhyk

license: MIT


text:
🐛 Flyout menu - strange icon (feedback v4.0.0)

Describe the bug
On demo app:

There is a icon on the left and the indicator.
And Btw, when we open a submenu, if we click outside the menu, only the submenu is closed (on Windows, when we click outside the menu, all menu is closed). Maybe related to https://github.com/bdlukaa/fluent_ui/issues/332)

Weird. Is there any change of it being a rendering issue?

Tested on Firefox + Edge, same problem. (current demo app here https://bdlukaa.github.io/fluent_ui/)

Reproducible on VM-based environments as well!

FlyoutListTile builds the trailing widget twice. Removing line 212 solved it for me.
https://github.com/bdlukaa/fluent_ui/blob/de0e316c9e927b817e6f86b1d6e2bc95520dd398/lib/src/controls/surfaces/flyout/content.dart#L187-L215

Nice catch!

authors: WinXaito bdlukaa jesperborri


text:
Training Own Neural Network

Hello,
I am having trouble understanding the procedure to train my own detection model. I have a Jetson Nano 2GB and 4GB variant with me.
My objective is to detect if a person wears sunglasses or not. To accomplish this objective, my main queries are as follows.

I will have to train a detection model on my own dataset. It is mentioned in the Custom Containers document that I need to have one that is compatible with DeepStream. If I do manage to do this, what change should I make in which codes in the docker container so that it runs this different object detection neural network?
I am under the assumption that if I manage to train a custom object detection neural network following the instructions on the Deep Stream docs page, I will have a compatible neural network.  I should then put these weights in a shared drive and run the container, putting the trained weights in a particular folder (which I do not know the location of) and make changes in maskcam_run.py or maskcam_inference.py to point it to the updated weights. Are there flaws in my assumptions? Could you please correct me if I am wrong? I am new to docker as well so I might be missing something fundamental.

My work flow is the exact same as mask cam, with remote deployment and web server accessing and the rest. I just need to change the object detection mechanism. Even the statistics that it provides will be unchanged.
Thank you.

Hi @SmellingSalt,
As you mention, your use case seems pretty compatible with what we're doing!
I'd recommend you start training a YOLOv4 model, which should work great for your use case. This way you'll only need to convert your model to a TensorRT engine as described here:
https://github.com/Tianxiaomo/pytorch-YOLOv4#51-convert-from-onnx-of-static-batch-size
Once you have the TensorRT engine file, you need to make sure it gets included in the container image. That means changing this line specifically:
https://github.com/bdtinc/maskcam/blob/499205268d36a498e9d2d8e46ab44d90c3ab0b74/Dockerfile#L115
If the filename of your engine file is different from ours (most likely), change this line in the config file to point it correctly:
https://github.com/bdtinc/maskcam/blob/499205268d36a498e9d2d8e46ab44d90c3ab0b74/maskcam_config.txt#L105
And finally, since your object labels differ from ours, you'll need to adapt these names in the code (from mask/no_mask to glasses/no_glasses I guess 😄 ):
https://github.com/bdtinc/maskcam/blob/499205268d36a498e9d2d8e46ab44d90c3ab0b74/maskcam/maskcam_inference.py#L60
This documentation can also guide you in this process:
https://github.com/bdtinc/maskcam/blob/main/docs/Custom-Container-Development.md
In particular, some of the steps I just mentioned above, are also here:
https://github.com/bdtinc/maskcam/blob/main/docs/Custom-Container-Development.md#how-to-use-your-own-detection-model
Good luck hacking the code and let us know if you managed to adapt the system!

Thank you for your response!
I managed to run the docker container in interactive mode and mounted a local disk onto it as well.
By doing so, I was able to modify this line
https://github.com/bdtinc/maskcam/blob/499205268d36a498e9d2d8e46ab44d90c3ab0b74/maskcam_config.txt#L105
To point to the newly trained neural network and run things.
I will take your suggested approach from now on to make it more streamlined. Thank you!
I still have issues regarding training and interfacing with the docker image provided by you.
What I did
As my intentions were to first get the process to work, not caring about performance, I first wanted to understand the procedure to train and develop a .trt model.
To do this, I followed the procedures mentioned in this face mask detection repository by Nvidia and managed to get a .trt file at the end of it.
By modifying this line
https://github.com/bdtinc/maskcam/blob/499205268d36a498e9d2d8e46ab44d90c3ab0b74/maskcam_config.txt#L110
to point to the newly created resnet18 file and commenting out line 105, I assumed I could get things to work.
I unfortunately faced errors and could not get it to work on my custom resnet18 model. These errors I assume are owing to the fact that there are only 2 classes (mask/no mask) trained here and you use 3 classes (mask/no mask/ not visible), therefore the .trt model is an incompatible shape.
Help I need
As suggested by you, I will look into training a YOLOv4 model and use https://github.com/Tianxiaomo/pytorch-YOLOv4#51-convert-from-onnx-of-static-batch-size to convert it to a .trt file.
Here are some things I need help with;

The link suggested by you seems to convert weights in the format of .onnx to .trt. The file that you have shared here is in the format of .weights. The Nvidia documentation I mentioned earlier uses the format hdf5, which gets converted to .trt.
There seems to be a lot of formats, but in the end, they have to be converted to a .trt file after training them.

As I would need a YoloV4 model, I am unsure of which format to use to train, and where to obtain the neural network from, so could you explicitly state which format and from where I should obtain this?

Having read and understood your experience on training these neural networks, you have mentioned that you needed another class called not visible to help track people across the screen and not trigger false counts.
I am also in need of this feature and as you have rightly mentioned that there are no labelled datasets for this class, I am under the assumption that I have to use transfer learning and retrain your weights to learn the glasses/no glasses classes. I would like some clarification on whether I am right or wrong, and any further inputs you have, to know how to handle this situation.
Any repository/blogpost/resources that you have or suggest I follow to train a YOLOv4 model would be highly appreciated as well.

Thank you for your time!

Hi @SmellingSalt! I'm glad you're working on this.
I'll go over your questions:

The .weights file I provided in the other issue, is generated by training with the original darknet implementation of Yolov4 (see point 3). To convert this file, you also have instructions in the repo I linked, but in this other section. After you've ONNX, go to the ONNX->TensorRT part that follows.
Your understanding about the not visible class to improve tracking is correct. However, the latest version of our model isn't that good to detect that class precisely, because we merged a huge dataset that had much more examples of mask/no_mask. So, you've a couple options: not to use that class at first (I think the code should work anyway, otherwise you might add the label to YOLO even though you haven't actual samples on the dataset). Then you might add some examples of not_visible faces/heads to your dataset (I'm guessing that you might have some already without proper labeling, otherwise see answer to (3)). The other option is that you remove that class from the code entirely, if you don't think it's useful. One more thing to clarify is that we actually have 4 classes in the detector: mask/no_mask/not_visible/misplaced (ignore the misplaced entirely in your case, but that's why you'll see number of classes = 4 in some places of code or configuration files).
The AlexeyAB/darknet repository is a great starting point to learn about training and configuring YOLO.
Also, related to point (2), if you're short of examples of not_visible faces, you might want to add some images from a "head detection" dataset like this one

Hello,
Thank you for your inputs.
I have managed to train a YOLOV4 tiny neural network following the instructions provided in the links you shared.
I have the .weights and the .onnx files ready. I am now stuck at the penultimate step.
I followed the procedure outlined here and managed to generate a .engine file, but not the .trt file unfortunately. Earlier, when I had trained the resnet18 model following the steps here, the .trt file was automatically created.
On searching the internet for answers, I have come to the understanding that the trtexec command that is used here produces .engine files. I could find this file present in the same directory as where the .weights file was stored.
So in order to get the .trt model to replace here
https://github.com/bdtinc/maskcam/blob/499205268d36a498e9d2d8e46ab44d90c3ab0b74/maskcam_config.txt#L105
what was the procedure that you followed?
Or am I making a mistake somewhere else?
Also as a side note, I came across this answer on stack exchange, which claims the following

The downside of TRT is that the conversion to TRT needs to be done on the target device

And from the official documentation of NVIDIA's tensorrt, I came across this line

Note: Serialized engines are not portable across platforms or TensorRT versions. Engines are specific to the exact GPU model they were built on (in addition to the platforms and the TensorRT version)

So I would like to know if you did the conversion from .weights to .trt on the Jetson Nano, or on another device. I have so far been trying all of this on my laptop, and only ran your maskcam docker image on the Jetson Nano.

Hey there,
I believe that you can just use the .engine file, or even change the extension to .trt manually if you prefer that. If you produced that with the trtexec command, then you've a TensorRT file there, regardless of the extension.
About running the conversion command trtexec: yes, you need to run that last step (ONNX->TensorRT) on the device and the container itself.
TensorRT is quite picky so you need to match platforms and even versions. If the command is not found inside the container, you might install it using APT (I don't remember the exact name now but you can use apt update && apt search tensorrt).

Hello,
Thank you for your inputs. I have managed to successfully deploy my own neural network on the container, following them!
The only issue left now is with the class labels.
I get the following errors

WARNING: Num classes mismatch. Configured:2, detected by network: 4 printed repeatedly.

This warning doesn't make sense as I have trained the model with only two classes and set the same info in the .cfg file as well. I did start with your weights but I don't think that should affect it, however.

The camera feed outputs classes as not_visible and no_mask.

Changes I have made
File maskcam_inference.py
I have changed
LABEL_MASK = "mask"
LABEL_NO_MASK = "no_mask"  # YOLOv4: no_mask
LABEL_MISPLACED = "misplaced"
LABEL_NOT_VISIBLE = "not_visible"

To
LABEL_MASK = "glasses"
LABEL_NO_MASK = "no_glasses"  # YOLOv4: no_mask
LABEL_MISPLACED = "misplaced"
LABEL_NOT_VISIBLE = "not_visible"

File maskcam_config.txt
Change 1
https://github.com/bdtinc/maskcam/blob/499205268d36a498e9d2d8e46ab44d90c3ab0b74/maskcam_config.txt#L117
to
num-detected-classes=2

Change 2
python
model-engine-file=yolo/maskcam_y4t_1024_608_fp16.trt

to
python
model-engine-file=yolo/yolov4_1_3_416_416_static.trt

Change 3
labelfile-path=yolo/data/obj.names

To point to the new obj.names file which has only 2 names in it, glasses and no glasses
File 3 .cfg files
I have replaced the /yolo/facemask-yolov4-tiny.cfg file  with my own.
Could you let me know where else am I supposed to make the required changes?
Thank you!

Hi @SmellingSalt and @DonBraulio,
I am trying to do something similar. I am currently at the step where I successfully trained my custom yolov4-tiny model from darknet. I did convert my model to tensort based on the same repository proposed by the maskcam team.  I know that my tensort model is functional since I tested it with the demo_trt.py from the same repository. Now I am trying to use my yolov4-tiny.trt within the maskcam container but I get error message. From my understanding I need to do the conversion from onnx-tensort within the container since my tensort version on my jetson nano is not the same as the one in the container. My question for you is how did you proceed to this conversion inside the container.
Thanks for your help
Raphael

Hey @SmellingSalt, I'm really sorry I missed your message in the noise. I hope you could find the solution to your problem.
If not, I think that probably the thing you were missing was changing classes=4 to 2 in the yolo config file (here and on line 274), unfortunately it seems like the darknet implementation doesn't pick up the number of classes from the labels file (check the original docs for more info).
@Raphenri09 you should start your container in Development Mode and then run trtexec from the bash prompt inside the container.
I can't test right now if tensorrt is pre-installed in the container, but I've checked some notes and found that I was using something around this command to do the conversion:
/usr/src/tensorrt/bin/trtexec --onnx=../yolo/yolov4_1_3_608_608_static.onnx --explicitBatch --saveEngine=tensorrt_fp16.trt --fp16

Of course, you'll need to change the file names and check the path to that executable, but I hope it helps!

authors: DonBraulio Raphenri09 SmellingSalt

repo: bdtinc/maskcam


text:
NoMethodError for access_control when used in rails-api

rails-api doesn't have ActionController::Base which is what the controller methods are attached to.

Currently the work around is to add the acl9 helper to the app controller:
class ApplicationController < ActionController::API
  include Acl9::ControllerExtensions
end

Looking forward to an update.
Thanks!

Thanks for bumping this, and the workaround, I'll have something very shortly.

1.2.1 is now out on rubygems

Nice! Thank you!

You're welcome. Thanks again for the bump on this, I had the fix sitting locally and had just forgotten to push it up.

authors: brancusi smathy

license: mit

license_source: bigquery


text:
CSS "space_around_combinator" not working

Description
An issue with CSS selector spacing
https://github.com/Glavin001/atom-beautify/issues/2291
Input
The code looked like this before beautification:
.container>a {
  position: relative;
}

Expected Output
The code should have looked like this after beautification:
.container > a {
  position: relative;
}

Actual Output
The  code actually looked like this after beautification:
.container>a {
  position: relative;
}

This works on https://beautifier.io/ by putting this in the "additional settings":
{
   "space_around_combinator": true
}

Not sure what the problem is.

authors: bitwiseman prettydiff

repo: beautify-web/js-beautify


text:
Do not use hardcoded directory for tests

The hardcoded /tmp/js-beautify-mkdir directory path is used for tests,
and this directory it not removed after tests.
This can cause multiplie issues on a build server:

if multiple builds are running js-beautify tests concurrently, they may try
to manipulate the directory at the same time, and step on each other's toes
if multiple users are using the same build machine, since
/tmp/js-beautify-mkdir is not removed after tests, the permissions on
/tmp/js-beautify-mkdir will prevent another user to run tests

Great contribution.  Just a minor tweak, please, and I'll merge it.

@blino - Ping?

Hi,
Sorry, I did not find time to respond with a better fix.
Thanks for finalizing this, and also for the "touch -A" fix!

You had it mostly done.
No problem.  :smile:

authors: bitwiseman blino


text:
[C4GT] Develop Boilerplate UI + Backend Framework for BPPs

Project Details
Beckn protocol is a set of open specifications aimed to create a common language, that is machine-readable and enables interoperability for economic transactions between disparate platforms of any size and form - be it a cab reservation, or booking a stay, or confirming a doctor’s appointment, and many more. Thus it enables the creation of inclusive and equitable open networks offering a multitude of choices to the citizens, while at the same time negating the dependence on intermediaries to freely operate and generate economic transactions of value. It is akin to what SMTP is to E-mails or HTTP is to the Internet.
Since its inception in 2019 as a set of specifications, Beckn has been adopted across geographies in sectors such as mobility, retail, hyperlocal logistics, healthcare, skills, agriculture sectors, etc. Few notable examples of open networks built on the Beckn protocol are Open Network for Digital Commerce (ONDC), Namma Yatri at Bangalore, Kochi Open Mobility Network (KOMN), Unified Health Interface (UHI), etc.
The BPP Boilerplate SDK is a generic full-stack web + mobile framework that allows developers to quickly beckn-enabled seller/provider-facing applications (BPPs) via a boilerplate codebase. This consists of a base source-code when complied generates a basic BPP seller-side MIS with all APIs and screens for store/service management.  Developers can then modify these screens according various UI flows pertaining to different sector-specific experiences like mobility, health, retail, etc. This boilerplate code can be used to quickly create any kind of service management console like a simple retail store, a mobility service, a healthcare facility management system, a mentorship platform, and so on, via basic configurations and modifications of the source-code.
Features to be implemented

Admin UI Framework
Fulfillment Agent UI Framework
Backend API Framework and Network Interface

What exists

Beckn protocol sandbox at : https://github.com/beckn/beckn-sandbox
Beckn protocol specifications at  : https://github.com/beckn/protocol-specifications
Beckn protocol tech overview on Youtube : https://www.youtube.com/watch?v=7Otfcy37-NE&list=PLBC6c8MLy9uVUIb1BOgdOa8tP4rX6c4aK

What needs to be built

Open-source codebase with installation guide and developer docs
Live demo instance of Admin console
Downloadable apk of fulfillment agent app

Learning Path
Complexity
High
Skills Required

Open API 3.0
JSON Schema
NodeJS
JavaScript
React Native
React JS
MongoDB
MySQL

Name of Mentors:
Product Understanding

@ravi-prakash-v
@faizmagic

Protocol Specification Design

@ravi-prakash-v

Project Setup and Guidance

@faizmagic
@hemant-eminds
@nikhil2128
@ujjwal502

Product Setup

@nikhil2128
@ujjwal502

Product Architecture

@ravi-prakash-v
@nikhil2128

Frontend Development

@ujjwal502

Backend Development

@nikhil2128
@emindsajay
@zoyaashik

Deployment and Devops

@prasad-takale-eminds

Testing and QA

@SushanthKJ

Project size
8 Weeks
Project Setup Guide
To set up this project, please connect with the Project Setup and Guidance mentor for this project and follow their instructions
Product Set Up
To set up this project, please connect with the Product Setup and Guidance mentor for this project and follow their instructions
Acceptance Criteria

Demonstrate creation of a ride-hailing service through configuration of this platform and successfully process mobility ride requests from BAPs
Demonstrate creation of a transit-ticketing service through configuration of this platform and successfully process mobility transit ticketing requests from BAPs
Demonstrate creation of a tour booking service through configuration of this platform and successfully process tour booking requests from BAPs

Out of Scope

iOS app

Milestones

Understanding beckn protocol
Detailed product requirements document
Admin UI Framework source-code architecture
Admin UI Framework development
Fulfillment Agent UI Framework source-code architecture
Fulfillment Agent UI Framework development
Backend Framework source-code architecture
Backend Framework development

Hey!
I am Mohit from IET-DAVV Indore and currently working as a full stack developer fellow for motion design and play.
This project caught my attention due to the technologies involved in it and I believe it will be grateful for me to build this.
looking forward to contribute in it in coming days
Gracias!

👋 Hey @ravi-prakash-v, I'm really looking forward to submitting my proposal for this project! 🚀

@Mohit-Aasirwal @Sumitmaithani , It's great to see your interest in this project, you can make an active contribution via issue creation and by submitting your Pull Requests.
For support from fellow contributors, Join Beckn Open Collective server :https://bit.ly/bocWebInvite

authors: Mohit-Aasirwal Sumitmaithani dhirajshettyyy ravi-prakash-v

repo: beckn/BPP-Boilerplate-SDK


text:
[BBU] SF to ToIP Transition: GDPR Position Paper

Problem/Concern
Update Legal Architecture docs after Sovrin Foundation transitions GDPR paper to ToIP Foundation.

link to problem content

Proposed Solution
Collaborate with ToIP Foundation

Need to work with @tallree to understand where the GDPR paper will reside: ToIP or Sovrin Ecosystem Project.

repo: bedrock-consortium/bbu-gf


text:
[BBU-RFP] Question Title

RFP Topic Area
"Aid members in the development, installation, deployment and configuration, of transaction
endorser code."
Question
What do you mean by "Transaction Endorser code" here?  Since you are using Hyperledger Indy and Endorser code and logic is already built in to that code base, are you really just talking about configuration?
##RFP Topic Area

Build and Test Services
Develop and maintain build and test tools for use on all environments.

##Question
Does this mean that the applicant will be expected to produce their own builds of the Hyperledger Indy Node code, or is this just referring to building and testing the maintenance tools referred to elsewhere in the RFP?

Transaction Endorser's must adhere to the governance framework. The Indy codebase is baseline. Our onboard process with the Linux Foundation will incorporate write to the ledger such that endorser code can validate TAA signing. It also (unlike base indy) must check for entitlements owned by Endorser.

Applicant will build and maintain Bedrock Indy Code Base ...

Thanks!

We have more questions:
Questions for the Bedrock RFP.docx

I realized you are new to github so trying to help here ....Not sure what company you represent but it would be helpful to create a question for each in your word doc. Pls make sure that each is a specific question.  For example, the status of the BBU within LF is outside of the scope of this RFP. Respondents need to assume BBU is a legal entity that can pay for services. Please use the RFP Template for each.

thanks for the help - will do. Can I still submit questions today?

RFP Process has entered review stage.

authors: francesdr vinomaster


text:
Automatic pull request for permission-file permission-file-beerend-lauwers-test.md

Created via the Hask Anything web interface. If this contains copyrighted material, please ask the author if we are allowed to replicate it here with attribution.

Test complete.

repo: beerendlauwers/HaskAnything


text:
upper bound constraints

Hi. I wonder whether it is possible to add the upper bound constraints, i.e., gps<=fmax, which are opposite to the lower bound constraints, i.e., gps>=fmin. It seems to be possible to add the upper bound constraints to the "comput_safe_set" functioon when lipschitz constant L is infinite.

Hi. I wonder whether it is possible to add the upper bound constraints, i.e., gps<=fmax, which are opposite to the lower bound constraints, i.e., gps>=fmin. It seems to be possible to add the upper bound constraints to the "comput_safe_set" functioon when lipschitz constant L is infinite.

您好，您这个问题解决了吗？

Sorry for the late reply - sure, there's nothing that stops you from doing that. However, it's easy to already do this in the current format. Rather than a constraint f(x) <= fmax you can simply model -f(x) with a GP instead and have a constraint -f(x) >= -fmax.

repo: befelix/SafeOpt


text:
🛑 ddn is down

In 28e9326, ddn (http://ddn.vko-kmt.ru/users/sign_in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ddn is back up in a2209c5.

repo: beglov/upptime


text:
Get rid of count(1) by default

(This is related to #255)
In MANY cases the app is designed in the way where count is not needed at all. For example if you query items and show them to user in twitter/pinterest/facebook-like "infinite" list, when at the first step, only Top-N items are selected, then, for the second portion, again, Top-N items are selected but with some "shift" (using id or created column usually), and this process can be repeated many times.
This very common task. And usually you have many millions items in the table and query should be executed in milliseconds.
So in such cases count(1) is not needed at all. Moreover, estimated count is not needed either since the app doesn't show user any information about it (no items count, no page number). I implemented solutions with estimated count in a couple of large projects (dozends Ms of users) and unfortunately such approaches fail very fast – in cases when you have some filters where Postgres has no good statistics and makes error estimations (not to mention that it does require many additional milliseconds – see below). In many cases, it's better to show nothing to user than to show wrong information. So in my personal cases I decided to stop using estimated count for large datasets and design apps in a way where this info is not needed.
However, in some cases count(1) is useful of course and should be provided.
The main thing here is that for years Postgres has slow count(1). This is very serious problem and people who use Postgres know how to handle it and how to live with it.
What I want to say is that by default, count(1) is not needed. I propose to skip it by default and show only if user asks for it. This is separate issue than #255 since we would have 3 options:

no count
exact count
estimated count

.. and large projects need the first one to be used by default, otherwise performance issues will be real headache.
"Estimated count by default" is also no-good, since in loaded server it's better to avoid additional planner executions on every request. Here is a quick example for one real production server with 5k TPS, dozens of M of rows in the table:
XXXXXX=# explain select * from user where birthday <= '1980-01-01';
                                      QUERY PLAN
---------------------------------------------------------------------------------------
 Seq Scan on "user"  (cost=10000000000.00..10000273915.79 rows=1926654 width=405)
   Filter: (birthday <= '1980-01-01'::date)
(2 rows)

Time: 83.222 ms
XXXXXX=# explain select * from user where birthday <= '1980-01-01';
                                      QUERY PLAN
---------------------------------------------------------------------------------------
 Seq Scan on "user"  (cost=10000000000.00..10000273915.79 rows=1926654 width=405)
   Filter: (birthday <= '1980-01-01'::date)
(2 rows)

Time: 0.295 ms
XXXXXX=# explain select * from user where birthday > '2000-01-01';
                                     QUERY PLAN
-------------------------------------------------------------------------------------
 Seq Scan on "user"  (cost=10000000000.00..10000273915.79 rows=49839 width=405)
   Filter: (birthday > '2000-01-01'::date)
(2 rows)

Time: 24.530 ms
XXXXXX=# explain select * from user where birthday > '2000-01-01';
                                     QUERY PLAN
-------------------------------------------------------------------------------------
 Seq Scan on "user"  (cost=10000000000.00..10000273915.79 rows=49839 width=405)
   Filter: (birthday > '2000-01-01'::date)
(2 rows)

Time: 0.338 ms

– no one would be happy to have additional 20-80 ms (even though 2nd call is quicker, but it should be the same call and what if you have many possible filters?).
So I propose to disable count(1) by default. This will help to adopt this solution in mid-sized and big apps. The project itself is great and well designed and according my twitter, more and more people are interested in such solutions.

You make good points. Seems like you've had some real production experience with postgresql-powered apps. I'm fine with getting rid of count by default. When I first wrote it I was unaware of the performance problems and thought I was getting "two queries for the price of one!"
Also can I get your opinion on https://github.com/begriffs/postgrest/issues/254 ?

Thank you.
The "optimization #2" described in http://leopard.in.ua/2014/10/11/postgresql-paginattion/ is exactly what I talked about in the first paragraph.
This is widely used technique, with its drawbacks.
Cursor method I would rather consider for any heavy-loaded OLTP project. pgbouncer is a standard de facto right now, for connection pooling. I'm really not an expert in Postgres cursors topic, but AFAICS you're considering keeping connection between different requests – I'd expect problems with "statement" and  "transaction" pgbouncer's pooling modes (which are usually used under heavy load). So cursors are maybe not the best choice for OLTP apps that use pgbouncer. Though they might be considered as a good thing in non-OLTP fields when low numbers of users work with large data sets.
Meanwhile, I wonder why you at all thinking about implementing these tasks inside PostgREST. Is the pagination really a task that should be implemented by API engine? This can lead the project to narrowing use cases where it can be used – I'd stick to be as low-level as possible, leaving this task to the end user who can choose between true OFFSET and "order-and-shift" approaches for pagination. Both approaches could be easily achieved with eq and gte/lte abilities that are already provided.
Maybe it's better to be as low-level as possible and think about providing general ability to work with cursors for those who can afford them in their projects allowing implementing pagination or whatever on top of it?

Maybe I explained my thought not clear in the previous message.
What I propose regarding pagination problem is to improve PostgREST's capabilities  in more "low-level" fields: instead of solving:

instead of providing "exact & straightforward pagination with OFFSET feature" simply provide LIMIT/OFFSET feature itself (already present);
instead of providing "useful and cute shift-and-order pagination" (like in http://leopard.in.ua/2014/10/11/postgresql-paginattion/), provide capability to use ordering and < / > comparisons (both already present)
instead of providing "smart calculated pagination notation" (which is X-Y/N now) provide low-level numbers -- actually, in general case it's only one number, "how many items returned in the resultset". If requested, provide also overall count number (right now, after thinking some time on this issue, I already really doubt that it is a good idea at all to combine count(1) with main SELECT itself – doing this, API is doing "foreigner" work. Why? It's simple. One more reason against it came to my mind: in such a strategy you don't allow user to cache count(1) result or to keep it in app main memory. The next step in improving things will be adding cache to PostgtREST. Or explain user how to ask it only once... In other words, this supporting this feature lead the project to more and more of new tasks that move you away from clear and basic value proposition, which is, I believe, "to provide lightweight, scalable, fast and easy-to-use tool to build API (and only API) on top of Postgres".)
[maybe] instead of providing "how many rows at all" count, provide a simple additional ability to query it explicitly – smth like /api_method?somefilter=eq.XXX&anotherfilter=lte.YYY&count=[exact|estimated] (I'm not sure that it's worth to make count a "reserved" word – sometimes people create views with count(*) in definition, and some people are lazy and don't define aliases, so result sets have count column in such views :) )
again, instead of doing implicit estimated count, provide capability to do explicit API call for it (as in example above)
instead of providing pagination via cursors feature, so something to allow users use them via PostgREST, allowing them to decide what is the final purpose of doing it. (But I'm not sure how many users need it – I'd rather expect that pl-functions calls via PostgREST features around this field are more important. I'm by no doubts going to try plpgsql and maybe plv8 functions calls via PostgREST. I saw some warning about it but not sure what's wrong with it...)

I hope the general idea of being "as low-level as possible" is clear now. It is also good to do 1 thing better than anyone else, with excellent quality – than to do many things with so-so quality.

Edited. Sorry for mess in my English.

I generally agree with @NikolayS about keeping things low-level.  I'd like to see robust RPC and being able to fully exploit plv8 before we get into features that not everyone wants/needs. Once people start posting examples using plv8 and RPC to do advanced things with PostgREST I think that will get people thinking outside the box and give them the tools they need to work around nearly any limitation.
@begriffs Have you considered using a configuration file and/or request headers to enable/disable controversial features (high performance penalty and/or limited use case)? I personally would prefer anything with such a large performance impact to be an "opt-in" but I can see the value in "sane defaults".
If a client side dev knows how to send custom HTTP headers, I'd venture to say they know how implement pagination. As you said before, giving a way to retrieve count without any results is valuable independent of this discussion.
Additionally, when using RLS, we have to reconsider what we know about query performance (including count) in PostgreSQL and make sure we try and retry our previously held assumptions. I have found that enforcing ACL in white label or complex organizational scenarios can be the most expensive part of queries.
Big picture stuff
The beauty of PostgREST is showing what we can accomplish in the database without heavy middleware and/or app layers. We need to see good working examples of table partitions coupled with triggers, RLS, and materialized views (pop redis-fdw in there for the cool kids).
I think that it's hard to realize how all of these pieces can fit together without seeing it. To help beginners it might help to say "This works best with write once tables" or "This doesn't work well with tables that are updated often", etc... etc...
This is why I lean towards low-level and highly flexible. What if I want my counts to come from a materialized view? How can I do that without writing Haskell?

Any new on this? For myself, I just commented the count(1) parts of SQL and recompiled it, but for the project itself smth different is needed

So you can now suppress the count but by default it is calculated included. In v0.3 how about we switch the default to no count while allowing a client to send Prefer: count=exact? Later we can add count=approximate as well.

Reviewing this issue I realize that counts are still included by default 0.3. Oops, I made an oversight. :cry:
This change will semantically require a major version bump since it can break clients. I'll add it to the newly created v0.4 milestone.

There is a collision between Prefer: count=none and Prefer: return=representation – if you always want "count=none" by default and put it to your code library which talks to API, and at the same time  want  to tell API to return just-created-entities, sooner or later you will find yourself (or your client-side developer as in my case) having headache patching client code logic (react & react-native in my case).
I'm still 100% sure that  "count=none" should be default logic since in big project it's the only way to survive.
We ended up with this (excessive for some queries) solution – we add to all queries:
Prefer: count=none; return=representation

The bottom line is: current approach of counts enabled by default and collision with header naming for different instructions  makes PostgREST harder to understand and introduces possible point of errors.
P.S. any ideas why adding Prefer: count=none; return=representation to all queries might be a bad thing?

My own "oops" ;-) – I've just read that count=none by default is planned for v0.4.
👍

@NikolayS you can add those headers on the fly in nginx and remove them from client code. Might be even more secure since the clients won't be able by mistake to do counts

so this will be included to v0.4? when does it expected?

Yep it'll be in 0.4 along with some other things that are breaking changes.

authors: NikolayS begriffs jmealo ruslantalpa

repo: begriffs/postgrest


text:
No animation note is not working

Describe your bug here.
well the title explains itself, basically the custom note "no animation" is not working, i try to use a mod that already use it and also i manually add the note with the chart editor, but the character still does the animation, i only test it on android idk if happends on ios or pc
Crash Log or logcat logs (if existing)
No response
Are you modding a build from source or with Lua?
I am not modding
Have you open preload state?
Yes
What is your build target?
Android
Did you edit anything in this build? If so, mention or summarize your changes.
Is the default build, no changes

fixed


text:
Loosen pinning of runtime gems

Allows for a wider version of the runtime gems to be used while avoiding potential breaking changes in their versions.

You can use the fork in the meantime https://github.com/thewalkingtoast/solargraph-standardrb

Bump @bekicot

@bekicot this is e very low hanging 🍒, please pick it 😄

Thank you. And sorry for being late.

authors: bekicot codingluke thewalkingtoast

repo: bekicot/solargraph-standardrb


text:
Audio is not playing with WebRTC disabled

Describe the bug
If WebRTC is disabled for browser audio will fail to play
To Reproduce
Steps to reproduce the behavior:

Disable WebRTC in browser (in this case Firefox)
Join a channel

Expected behavior
Playing audio
What device are you on?
Desktop
Additional context
It probably can not be solved that easily without reworking whole audio stack but for people who like to keep WebRTC disabled this might be annoyance

is this a joke?

no I mean it just doesnt work with it disabled and I keep it disabled for reasons

you have no audio streams without WebRTC, what audio are you trying to play?

oh well I didnt check how it actually works

voice chat audio but if you say its how it plays audio it cant be helped

authors: nadirabbas okass

repo: benawad/dogehouse


text:
meme and tools emoji pack

Pack of 28x28 emojis
memes:

tools/frameworks/... used in dogehouse:

cool

authors: daloes ofsho


text:
(Re-)Fixed z̗͉͍͎̞̓ͭͭ̐̐a̲̻̺̹ͫͪͨ̑l̪̘̦͋̎̇ǵ̹͕̀o͎ͩ text

This PR:

Fixes the issues in #1982
Fixes #1970
[x] Does nothing else

@benawad  This is needed, otherwise the emotes will have no space (between it and the text) even when there is one

You're just hiding it with overflow-hidden wouldn't it be better to later prevent the User from using Zalgo in the first place?
as @Darker-Ink stated in #1970 : "It could also Crash people if they are on a Low end device and someone sends a Huge Piece Of text.". - Just hiding the overflowing Part wouldn't fix this then, right? Since the Browser renders the Text anyway.
I understand that this is no easy Task since these should survive the Check:
a ä ä A Ä Ä
e ë ë E Ë Ë
i ï ï I Ï Ï
o ö ö O Ö Ö
u ü ü U Ü Ü
y ÿ ÿ Y Ÿ Ÿ
æ Æ œ Œ
… ¼ ½ ¾ ‘ ’ “ ” ™
$ ¢ £ ¬ † ‡ • ‰ · ° ± ÷
Maybe someone has an Idea how to fix this, but this is a good solution for now though!

As far as I'm aware most rendering engines will not render whatever's hidden. Trying to simply cut it out will cause more issues as we have god knows how many languages supported (that may be affected by this).

authors: goldyydev l-mbert


text:
Enable retrying dynamic imports after failure.

Hi,
Previous PR kept failing and then I've noticed, that reify@0.17.2 was reverted, so I've changed test to represent reify@0.17.3 and bumped it in packages.json, hope that's ok with you.
Again, this is fix for https://github.com/meteor/meteor/issues/10182

Thanks for getting the ball rolling on this, @Gariest!

authors: Gariest benjamn

repo: benjamn/install


text:
🛑 Benmarte is down

In 29c61a0, Benmarte (https://benmarte.com) was down:

HTTP code: 526
Response time: 216 ms

Resolved: Benmarte is back up in 5085bdc after 40 minutes.


text:
Touch events are not working in on my Android phone

Hi
I just opened the main page in on phone and dragging is not working.
I tested with Firefox Mobile (Chrome and Opera had time out error!)

Hi, Yes you are correct about touch events. I currently have not implemented this as it creates issues when trying to scroll on mobile devices. only mouse events are currently implemented.

You can enable dragging when the user long touched. It seems to be the expected behavior.
I think that you can use Pressure.js library to simulate this.

Thankyou for your thoughts, I have enabled touch events on the touch branch of this project. Thanks for the link regarding pressure.js ill have a read when i get a moment.

FYI ive started some testing of another drag/resize lib:
Initial testing is here: https://github.com/bensladden/vue-interact & https://vue-interact-test.netlify.app/
See what you think.

Version .4 now used interactjs. moveHold and resizeHold props enable you to delay moving/resizing thus allowing scrolling behavour

authors: bensladden rostamiani

repo: bensladden/vue-responsive-dash


text:
Exposing signature validation errors?

Currently whatever error causes the SAML response signature validation to fail, the same error message is returned.
Would you be open to exposing these somehow? (Either in more detailed error messages, or via a property on the SAML object and method on the strategy to read it), or is hiding the specific error a deliberate decision to make attacks harder?

(specifically, would a pull request adding this be welcome?)

I may be able to help with this; I've just spent all day with the Node debugger attached to a process in my production environment hunting down an invalid signature. Looking through the code, in most cases it should be as simple as just throwing an error instead of just returning false. In others - those which use xml-crypto to validate signatures - it may be as easy as check the return code then throwing sig. validationErrors (an array of error messages collected in xml-crypto when validating signatures).

@ccampanale Just yesterday I realized a new version of passport-saml that dealt with this. Instead of returning "Invalid Signature" in 6 different places, each place now gets a unique error message. Does that meet your needs, o are their places where you want to pass along more detail as returned by the XML parser?

@markstos I didn't even realize that! Let me bump our package refs and take a look. I'll let you know. Thanks!

👍 Sorry I never got around to making a PR 🙈

Bumped the version and tested. Still seeing our same issues but I'm pretty sure the issues are with our IDP. The new error messages are nice as they let you know where exactly in saml.js the issue is occurring but there are some errors from xml-crypto that could be relayed as well as I mentioned above. (Not necessarily parser level errors, though that may be helpful in some cases?) It's not a huge deal but I could see how it may save folks from needing to do a deep dive with the debugger as I have the past couple of days.

@ccampanale If you'd like to make a PR to pass along the detailed failures from xml-crypto, I'm up for merging that as well. XML parsing has historically had some security flaws, so if XML is parsing sometimes fails in strange ways, it could be useful to log details for forensics as well as to debug IdP connections.

Yeah, since I'm still fighting the good fight with my organization's IDP and can't get our production deployment to work I may very well do that. As you said, if nothing else it may save others a good deal of time troubleshooting strange failures and/or from a forensics collection perspective.

I just about pulled my hair out with a recent integration, only to eventually realize that the profile field mapping between them and us wasn't as expected. It's increasingly tempting to consider using Okta or OneLogin for their "Service Provider" offering.

authors: autopulated ccampanale markstos

repo: bergie/passport-saml


text:
passReqToCallback: true not working on MultiSamlStrategy

In the conf below, I am using the   ,passReqToCallback: true .. then adding req to the callback function.  (this is how this option works on passport-facebook)
I am getting:
TypeError: done is not a function
If I remove req from the callback it works again but then I don't have the req object that I need to use with the profile
const conf = {
  path: '/login/callback',
  entryPoint: 'https://something',
  issuer: 'https://something',
  cert: fs.readFileSync('key.pem', 'utf-8'),
  decryptionPvk: fs.readFileSync('saml.pem', 'utf-8')
  ,logoutUrl: 'https://something'
  ,passReqToCallback: true
};

passport.use(new MultiSamlStrategy({
    getSamlOptions: function(request, done) {
      return done(null, conf);
    }
  },
  function(req, profile, done) {  //taking out req here will make this work but won't pass the req
    var user = profile;
    return done(null, user);
  })
);

Just checked and this does work if I use SamlStrategy instead of MultiSamlStrategy

@gavinbelson can you try:
passport.use(new MultiSamlStrategy({
    passReqToCallback: true,
    getSamlOptions: function(request, done) {
      return done(null, conf);
    }
  },
  function(req, profile, done) {  //taking out req here will make this work but won't pass the req
    var user = profile;
    return done(null, user);
  })
);

Lifesaver. Thanks man, this works.
I believe in the docs it says to do:
return done(null, provider.configuration);
Maybe, this should be added to the docs somewhere?

If the docs need improvement, a PR is welcome. Note there will be a bug-fix for Multi-SAML in the next release.

authors: gavinbelson markstos stavros-wb


text:
🛑 DAP Website is down

In 00a2041, DAP Website (http://web.ula.ve/dap/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DAP Website is back up in 22bc337 after 2 minutes.

repo: berlinserver/estatus


text:
🛑 SIDAP PROFESORES is down

In f900a74, SIDAP PROFESORES (http://uladap.adm.ula.ve/sidap/pdi) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SIDAP PROFESORES is back up in e68a65c after 7 minutes.


text:
🛑 vote.berty.community is down

In 15aba06, vote.berty.community (https://vote.berty.community) was down:

HTTP code: 0
Response time: 0 ms

Resolved: vote.berty.community is back up in eebab99.

repo: berty/uptime


text:
Add Rizomo script to home page

Resolve #194

@celiacheff On va retreindre à la page d'accueil

Screenshot en local

J'ai rajouté la variable sur la RA, elle était déjà sur la principal mais j'avais oublié que c'était pas propagé. C'est testable sur la RA du coup, et c'est bien que sur la page d'accueil

Ah j'ai compris, c'est nickel !

On peut merger et mettre en dev et en prod

authors: celiacheff jdauphant

repo: betagouv/audioconf


text:
une } se ballade sur la page detaillee des aliments

fait

repo: betagouv/ecolab-agribalyse


text:
Update sbt to 1.5.7

Updates org.scala-sbt:sbt from 1.2.8 to 1.5.7.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Scalafix Migrations

org.scala-sbt:sbt:1.5.0 (created no change)

https://gist.githubusercontent.com/eed3si9n/57e83f5330592d968ce49f0d5030d4d5/raw/7f576f16a90e432baa49911c9a66204c354947bb/Sbt0_13BuildSyntax.scala
Documentation: https://eed3si9n.com/syntactic-scalafix-rule-for-unified-slash-syntax

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, early-semver-minor, semver-spec-minor, scalafix-migrations, commit-count:1

Superseded by #90.

repo: betagouv/plante-et-moi-backend


text:
🛑 API Répertoire National des Métiers is down

In 0cea05d, API Répertoire National des Métiers (https://api-rnm.artisanat.fr/v2/entreprises/345184428) was down:

HTTP code: 404
Response time: 4270 ms

Resolved: API Répertoire National des Métiers is back up in a3cffad.


text:
Ajout d'explications sur le simulateur salarié

Ajout du texte pour améliorer le référencement naturel du simulateur salarié.
Todo:

[x] Liens internes vers la documentation (ne semble pas géré actuellement par sitePaths)

[x] Les liens sont maintenant fonctionnels, mais vu qu'ils sont "codés en dur" (via l'attribut href), la page est entièrement rechargée et l'UX n'est pas fluide. Il faudrait utiliser des <Link> de react-router à la place, mais cela nécessite probablement de changer la librairie qui parse le markdown de marked à react-markdown.

[x] Ne pas afficher les explications dans les embedded/intégrations sur sites tiers
[x] Ajout d'une illustration visuelle pour aérer le pavé de texte (peut-être une visualisation de brut = net + cotis salariales)

J'étais parti pour simplement rajouter un peu de texte, mais j'ai finalement fait quelques modifications dans la gestion du markdown (les liens étaient mal traités), ce qui explique le nombre de fichiers modifiés 😄.
Comme discuté ensemble, le but de la modif est d'avoir une description qui peut-être référencée pour le SEO, vous pouvez lire le texte ici : https://deploy-preview-600--syso.netlify.com/sécurité-sociale/salarié
J'envisage d'ajouter des descriptions textuelles sur d'autres pages, en particulier dans la documentation, en fonction de ce qui peut être pertinent pour le référencement naturel.

repo: betagouv/syso


text:
FIne-Tuning request for gpt-4o-2024-08-06, gpt-4o-mini-2024-07-18 and gpt-4-0613

Hi,
..\openai-master\OpenAI.Playground\TestHelpers\FineTuningJobTestHelper.cs
var createFineTuningJobResponse = await sdk.FineTuningJob.CreateFineTuningJob(new()
{
TrainingFile = uploadFilesResponse.Id,
Model = Models.Gpt_4o_mini        // from Gpt_3_5_Turbo to Gpt_4o_mini
});
I am trying to add fine-tuning for model Gpt_4o_mini, but got following error message. Do you have any plans to add fine-tuning function for gpt-4o-2024-08-06, gpt-4o-mini-2024-07-18, gpt-4-0613 and further o1 model?
Run Case Study Is The Model Making Untrue Statements:
ft:gpt-3.5-turbo-0125:nc::AbLl9Rrx
ft:gpt-3.5-turbo-0125:nc::AbI8tzQh
Uploading file FineTuningJobSample2.jsonl
FineTuningJobSample2.jsonl uploaded
Wait 5 seconds for the file to be ready
System.Net.Http.HttpRequestException: Response status code does not indicate success: 404 (Not Found).
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at System.Net.Http.HttpClient.GetStreamAsyncCore(HttpRequestMessage request, CancellationToken cancellationToken)
at OpenAI.Managers.OpenAIService.ListFineTuningJobEvents(FineTuningJobListEventsRequest fineTuningJobRequestModel, Nullable`1 stream, CancellationToken cancellationToken) in C:\Users\ChNa653\Documents\Projects\AI\openai-master\OpenAI.SDK\Managers\OpenAIFineTuningJob.cs:line 33
at OpenAI.Playground.TestHelpers.FineTuningJobTestHelper.RunCaseStudyIsTheModelMakingUntrueStatements(IOpenAIService sdk) in C:\Users\ChNa653\Documents\Projects\AI\openai-master\OpenAI.Playground\TestHelpers\FineTuningJobTestHelper.cs:line 48

sorry my bad, I should look into https://platform.openai.com/docs/guides/fine-tuning for more detail, however, since I change the mode to Model = Models.Gpt_4o_mini_2024_07_18, the code completed fine-tune function.
Thanks!

functions existed!

repo: betalgo/openai


text:
Removed ESIK_Result parameter from the delegate on SIK_JoinLobby_AsyncFunction

Removed casting from an EChatRoomEnterResponse to an ESIK_Result and broadcasting that value, which would have unintended consequences if someone tried to use that value. In fact, the LobbyEnter_t callback doesn't even have an EResult property, so I removed it from the delegate altogether.
A good replacement would be to broadcast the Param.m_ulSteamIDLobby of the lobby, which would provide an easy way to see if the callback had a bad response (SteamId would be 0 in this case).

Side note: I also removed the broadcasting of the ESIK_ChatRoomEnterResponse::None value and replaced it with ESIK_ChatRoomEnterResponse::ChatRoomEnterResponseError is this is the proper response the Steam API would return.
I understand if these changes aren't merged, as you may want to go a different direction with it. This was just something I caught while trying to utilize these functions and changed on my personal project.

repo: betidestudio/SteamIntegrationKit


text:
Series color issue

This issue depend on #262
When i fill my series collection by first call of my method

when I call my method second time , it calls seriescollection.clear() and fill it with a new series, but with a new colors =)

Its not good =)

This is actually the safest way for the library, every time a series is added it increments a counter, that is why you get a new color, this is safe so color never repeat, any ideas to change this is appreciated.
You can always force the colors fo your series as:
<lvc:LineSeires Stroke="Red" />

Thank you!
<lvc:LineSeires Stroke="Red" />
is all right.
But what do you think about to reset counter after calling seriescollection.clear() ?

I like it, will commit that to close this issue

authors: NickSavin beto-rodriguez

repo: beto-rodriguez/Live-Charts


text:
Modularize?

λ aims to be modular and browser-friendly. How about releasing every function as a separate script? This goes right in hand with “Methods are implemented individually and not as part of a whole.”
Here’s why: when you just want one or two λ functions, you still have to pull the whole source of contra into your bundle:
var concurrent = require("contra").concurrent;

3 kB minified code isn’t much – but it matters when you write a browser-facing app or library. It would be much better if you could just get the 300 bytes you really need:
var concurrent = require("contra/concurrent");

Here’s how: tjmehta/101 is a great example of such an approach.
You can also keep full backwards compatibility with the current syntax – var concurrent = require("contra").concurrent – by supplying an index.js like this one. This index.js could then also be compiled into a drop-in bundle for browsers. Just as it is now.

I did this for contra.emitter, which is typically all I need client-side. I don't have the time to do it, but it's definitely a welcome pull request

:) funny, I've actually filed this issue because I needed to import contra/emitter. Anyway, I'll do my best to submit a PR next week – though I'm also quite tied up at the moment.

I went ahead and did this myself for 1.9.0

Thank you. Sorry for not letting you know – I realized that I just needed the pubsub part, and that I needed more power. So I went ahead and wrote another library: stereo. It’s like λ/emitter, but split down further into many tiny modules.

No worries, I kinda needed it anyways :)

authors: bevacqua tomekwi

repo: bevacqua/contra


text:
fall back to native html5 if present

has this been a consideration?
@bevacqua please tag as a question

Drag and drop is usually tied into functionality that comes well after javascript is enabled, and plain HTML5 attribute-oriented implementations are only useful for the duration of the visit, making it pretty much moot in all but the simplest of cases (sorting things + not caring that their positions will be load on navigation)

authors: bevacqua swilliamset

repo: bevacqua/dragula


text:
Very high CPU usage on MacOS

Summary
On MacOS, even simple Bevy apps cause very high CPU load; for example, even a blank app that just loads DefaultPlugins to render a blank window sits at ~50% CPU usage on an Apple Silicon M1. Add a couple of rendered meshes and postprocessing and it'll quickly go up to about ~90% CPU.
On Windows and Linux, the same app will comfortable sit below 1% (even with some light rendering.)
Additional notes:

A MRP has been provided here.
It uses the opt-level = 3 etc. trick from the docs.
Compiling a --release build doesn't make a difference.
In addition, when hiding the app, CPU load doubles, but I understand there have already been issues filed about this particular problem.

Bevy version
0.11.3 (but I also tried 66f72dd, the newest commit on main at the time.)
Relevant system information

Rust 1.73.0
MacOS Sonoma 14.0

AdapterInfo { name: "Apple M1", vendor: 0, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Metal }
SystemInfo { os: "MacOS 14.0 ", kernel: "23.0.0", cpu: "Apple M1", core_count: "8", memory: "16.0 GiB" }

What you did

Build a "blank" Bevy app (code available here)
Compile and run it

What went wrong
Expected behavior: the app should cause CPU load in the single-digit percentage range, like it does on Windows (<1% CPU, on a Ryzen 7.)
Actual behavior: the app caused ~50% CPU load.

This is a long-standing bug, but it's nice to see it seemingly isolated to Mac. Could we see a tracing log? https://github.com/bevyengine/bevy/blob/main/docs/profiling.md
I'd also like to try stripping out even more things from the DefaultPlugins, and see if we can reduce this to one or two offending plugins. Unfortunately I don't have access to a Mac to test this myself, sorry.

I've created a tracing log using cargo run --release --features bevy/trace_chrome, letting run the app run for a handful of seconds, but it's already 442 MB, so I can't upload it here. :(
Is there any way I can send it to you, via Perfetto or otherwise?

Assuming that this represents a (randomly picked) single frame, maybe this is of use to you:

Maybe a GDrive link? Feel free to delete it after a couple days.
@superdump it looks like we're getting hit by excessively long prepare systems again 🤔

@alice-i-cecile - here's a Google Drive link for the trace, I hope it works for you:
https://drive.google.com/file/d/1DxPcWasjVDRJDlL1_PSQh-5qhpxEeA3p/view?usp=sharing

Trace downloaded and open locally, thank you very much!
Pulling this up in Perfetto, I'm still just seeing extremely long Prepare systems. I wonder if the way that wgpu polls is different on Mac? Perhaps it's spinning a thread to try and vsync automatically?

Pulling this up in Perfetto, I'm still just seeing extremely long Prepare systems. I wonder if the way that wgpu polls is different on Mac? Perhaps it's spinning a thread to try and vsync automatically?

Not sure how helpful this is, but I did try a couple of the more simple wgpu examples (from their latest main) and didn't observe any noticeable performance issues that looked like the one I was seeing with Bevy.
But please keep in mind that I'm new to this entire ecosystem (including Rust itself), so YMMV...

That's very helpful feedback.
This might be related to https://github.com/bevyengine/bevy/issues/9964.

Reduce frame rate to what?

I reduced the amount of code necessary to reproduce out on https://github.com/hmans/bevy-mrp-macos-performance/pull/1

Seems related to https://github.com/bevyengine/bevy/issues/5713

I noticed that my MacBook was running hot, and I found this issue. Upon running the example provided with DefaultPlugins, I noticed an unusually high CPU usage of 170%. Through a process of elimination, I determined that the culprit behind the issue is the RenderPlugin. The example runs smoothly with normal CPU usage when this particular plugin is excluded. While I intend to delve further into this matter, my limited experience with Bevy, having used it for only a day, may limit the extent of my assistance.

So I dug into this about 5 months ago, and found the same problem somewhere in the render pipeline. The discussion & profiling results are in the discord thread below.
It looked like it may have been a contention issue in wgpu.  That was about where I stopped because needed to make a wgpu-only poc to see if it was a wgpu-on-mac issue. Also this research was done on an Intel Mac.
https://discord.com/channels/691052431525675048/743663924229963868/1119076766405886004

I've just checked the current latest and this still seems to be an issue (2 full cores used on a M2 Pro with even the trivial examples.) Is there any outlook on this eventually improving?

We are interested in this improving! But this needs further investigation to pinpoint: it's still not at all clear where in the stack this is occurring. Does this occur with wgpu's examples?

related issue in my opinion

We are interested in this improving! But this needs further investigation to pinpoint: it's still not at all clear where in the stack this is occurring. Does this occur with wgpu's examples?

I just tried exactly this today (current HEAD there) and it seems fine. I'm happy to provide further testing or any other input that might help. Sadly I am not familiar with either codebase so I can't really provide any input there.

Great :) I would double-check at https://github.com/gfx-rs/wgpu/releases/tag/v0.19.4 which is the version Bevy is currently on, but I would suspect that there seems to be something wrong with Bevy's implementation then.
It looks like the various Prepare steps are at fault. I'll ask the rendering experts if they might have insight there. I suspect we're spin locking while waiting to coordinate between the various steps somewhere, which is manifesting as high CPU usage without actually doing useful work.
Are you able to achieve reasonable results (more than 50k entities) on the Bevymark example?

@hmans could you try forcing a scale_factor of 1.0 for the window and see if it makes a difference. For some reason macos reports a really high scale factor by default.

I tested with 0.11.3 and 0.14.0-rc.2 and observe the same. Using scale_factor of 1.0 makes no difference.
I looked at a GPU frame trace in Xcode and it's only running the no_camera_clear_pass and using microseconds of time. Oddly it said that pass was using 10800 vertices. No idea why.
I looked at a CPU profile using Instruments and that shows no significant CPU usage. Running for 20s put CPU cycles spent for frame updates (at 120Hz) at about the same as plugin initialisation.
2024-06-08 - bevy macos default plugins cpu.trace.zip

bevy-mrp-macos-performance.gputrace.zip
Here's the GPU trace with scale factor 1.0.

And just to note that I think tracy traces showing waiting on prepare set systems makes sense as they are blocked by waiting on vsync for a new swapchain texture.

I've tried 0.14 and the issue is still persisting.
Since wgpu itself does not seem to have this issue, from the perspective of a naive outsider who's not familiar with either code bases, my best guess would be that wgpu uses vsync out of the box (idling until it's time to render the next frame) and Bevy doesn't (at least on macOS); however, even the "fps_overlay" example that renders literally nothing uses ~100% CPU while displaying an FPS count of 100 (on my 100Hz screen) when focused, and ~60 FPS when unfocused.
A couple of folks on Reddit pointed me towards the (new?) WinitSettings::desktop_app(), but that isn't the solution to this issue because all it does is prevent the rendering of new frames if there is no user input. Once it does render frames, things are as described above.

Great :) I would double-check at https://github.com/gfx-rs/wgpu/releases/tag/v0.19.4 which is the version Bevy is currently on, but I would suspect that there seems to be something wrong with Bevy's implementation then.

I know I've taken my good time with doing this (apologies), but I now got around to checking that specific version, and its cube example uses a relaxed ~19% CPU time for rendering at 120 FPS (I'm on a M2 Pro now.)
Bevy 0.14 appears to use wgpu 0.20, which exhibits the same performance.
19% still feel a little too high for what the example is doing, but it's nowhere near the 50%-200% that I'm seeing with simple Bevy examples.
As mentioned on Reddit earlier today, I'm (stupidly and naively, and very likely unsuccessfully) trying to track this issue down myself now. Just wanted to post these numbers here for reference.

I can reproduce this by run Sprite Sheet example on m3max, it took 66-75% CPU and 34% CPU for opt-level = 1

Not looking good for just 1 sprite animation.

Can you try with opt-level=3 or just --release? opt-level=1 is barely any optimization and isn't a good indicator of real performance.

Can you try with opt-level=3 or just --release? opt-level=1 is barely any optimization and isn't a good indicator of real performance.

opt-level=1 👉 34% CPU
opt-level=3 👉 36% CPU
i didn't bother --release because i on dev and my m3 fans are spinning 🔥
[profile.dev]
opt-level = 3

[profile.release]
lto = true
opt-level = 3
codegen-units = 1
incremental = false
debug = false

And the result with [profile.release]  is
--release 👉 34% CPU
just --release 👉 36% CPU
Actually it look same all over setting. Something really weird here.

What are the chances this issue is related to how bevy is calling winit?
On the second to last known regression mentioned here: https://github.com/bevyengine/bevy/issues/11052
Bevy's entire update loop is currently running in the about_to_wait() wininit callback instead of WindowEvent::RedrawRequested. And there seems to be a whole bunch of workarounds + bevy ecs events passed around. (about_to_wait() is not supposed to be used for this, WindowEvent::RedrawRequested is supposed to be used instead according to the wininit docs).
See ApplicationHandler in bevy_winit::state.rs

If anyone can provide a recent MPC example of this problem I would gladly help pinpoint the exact issue.

If this still helps - I'm here with a M1 chip (Macbook Pro 2020 M1 16GB RAM).

git clone git@github.com:bevyengine/bevy.git
cargo run --features="bevy_dev_tools" --example fps_overlay runs at 60FPS & ~80% CPU (interestingly, when the window is not focused, it jumps to 85-90% CPU fairly consistently)
cargo run --release --features="bevy_dev_tools" --example fps_overlay runs at 60FPS & ~45% CPU

One interesting thing I noticed is that the CPU jumps considerably when you start moving the mouse over the window while it's not focused. Here's a short example:
https://github.com/user-attachments/assets/e4813bda-1038-459a-b81a-4888ff3158ab
(not sure if it's relevant, just thought it might be)
lmk if I can help reproducing anything, or trying out a fix 🙏🏻

I ran into similar issue on iOS (not Mac though). A simple example like https://bevyengine.org/examples/3d-rendering/3d-scene/ running on iOS (with bevy 0.14.2) has 100%+ CPU usage. I have not tried the --release flag yet.

authors: IceSentry Vrixyz Zajozor adals alice-i-cecile destravous dmlary hmans katopz matevz-ap superdump wentao

repo: bevyengine/bevy