Engagement Experience Dashboards - APEX Program, Releases, TypeSpec milestone/tasks interval tracking

Creation of PowerBI Dashboards for APEX Program and Release Plans.
Release Plan and APEX Prototype is in progress - https://msit.powerbi.com/groups/3e17dcb0-4257-4a30-b843-77f47f1d4121/reports/75926d99-0ce6-430e-87f5-684fbc90958b/5c677b3eacf6dca228fa?ctid=72f988bf-86f1-41af-91ab-2d7cd011db47&experience=power-bi
Initial thoughts captured in this word doc - https://msit.powerbi.com/groups/3e17dcb0-4257-4a30-b843-77f47f1d4121/reports/75926d99-0ce6-430e-87f5-684fbc90958b/5c677b3eacf6dca228fa?ctid=72f988bf-86f1-41af-91ab-2d7cd011db47&experience=power-bi
Deliverables:

[ ] APEX Program Dashboard Prototype (June/July)
[ ] Enhance TypeSpec milestone/task time tracking dashboard with visuals (June/July) https://github.com/Azure/azure-sdk-tools/issues/7769
[ ] APEX Program Alerts and Notifications (July/August)

### General TODOs
- [ ] Send email with link to prototype PowerBI Report to Josephine.  Requested that she experiment with using the Release page and that I would schedule time with her next week to discuss what would be useful for management plane page/customized visualizations.
- [ ] Schedule meeting with Josephine 1H June to discuss management plane release plan page (insights/metrics).
- [ ] Schedule meeting with Mario 1H June to look over visuals and data in the TypeSpec (time spent on tasks in release planner) PowerBI report.

### DPG (Data Plane Codegen) page
- [ ] Create customized release plan page for DPG.
- [ ] Only show data plane release plans.
- [ ] Gaps that need to be addressed for DPG stakeholder insights/metrics - https://github.com/Azure/azure-sdk-tools/issues/8194

###  All Release page
- [x] Release Plan Dashboard Stakeholder Feedback with Renhe and Laurent scheduled for 05/15/2024.
- [ ] Gaps in data need to be resolved - https://github.com/Azure/azure-sdk-tools/issues/8225.
- [ ] % of Self-Service release plans (Release page):  Show % release plans created by service partners vs created by SDK team (release plan submitted by field will not contain<EMAIL_ADDRESS>or<EMAIL_ADDRESS> @AngelosP

### APEX page
- [ ] Add the following filter options to the APEX page - RP Name, Product Type, PrivPrev State, PubPrev State, GA State
- [ ] Add visuals to APEX page that show Product types, PrivPrev State, PubPrev State, GA State.  @AngelosP
- [ ] Confirm that APEX page does not include product epics (epic type=product) that State = New, Duplicate, Closing Down, Retired and Tags do not contain "Release Planner App Test" or "non-APEX tracking".  @AngelosP

### Onboarding page
- [ ] New page named Onboarding.
- [ ] **Product Onboarding visual (bar graph)** Bar graph that shows total number of products onboarded each month.  Triage work items grouped by the Product Onboard Date date field. Triage work items for products will have data in the Product Service Tree ID field.  If data value is blank or N/A, the triage work item should be counted as service onboarding. @AngelosP
- [ ]  **Product Onboarding visual (from bar graph data)**. Visual that shows product types. @AngelosP
- [ ] **Product Onboarding table (show below bar graph**).  Fields to display: Link to triage work item, link to related epic (product type), State field (name Onboard State in table), Product Name, Product Service Tree ID, Product Type, Info Meeting State, Info Meeting Date @AngelosP
- [ ] Product Onboarding filter options for bar graph, table, ...).  Filter by State, DataScope, MgmtScope, Info Meeting State, Product Service Tree ID, Associated Service ServiceTree ID @AngelosP
- [ ] **Service Onboarding visual (bar graph):**  Bar graph that shows number of services onboarded (no product).  There will be no data or N/A in the Product Service Tree ID ADO data field of triage work item.  @AngelosP
- [ ] **Service Onboarding visual for product type**. Visual that shows product types for services onboarded (no data or N/A in the Product Service Tree ID triage work item field)  @AngelosP
- [ ] **Service Onboarding table.**  Fields to display: Link to triage work item, link to related epic (product type), State field (name Onboard State in table), Product Name, Product Service Tree  ID, Product Type, Info Meeting State, Info Meeting Date @AngelosP
- [ ] Service Onboarding filters: Link to triage work item, link to related epic (product type), State field (name Onboard State in table), Product Name, Product Service Tree ID, Product Type, Info Meeting State, Info Meeting Date @AngelosP
- [ ]  **% of Self-Service products onboarded** (Onboarding page) Visual that indicates the % and number that are self-service.  Logic to determine self-service onboarding - IF Triage work item (Onboarding Questionnaire Submitted by ADO field <> "Yogananda Krishnaswamy" OR "LaDonna Quinn") AND (Info Meeting State= Not Required" OR "Cancelled" OR field is blank), THEN the product was onboarded via self-service.  @AngelosP
- [ ] **% of Self-Service services onboarded** (Onboarding page). Visual that indicates the % and number that are self-service.  Logic to determine self-service onboarding - IF Triage work item (Onboarding Questionnaire Submitted by ADO field <> "Yogananda Krishnaswamy" OR "LaDonna Quinn") AND (Info Meeting State= Not Required" OR "Cancelled" OR field is blank), THEN the product was onboarded via self-service.  @AngelosP
- [ ] Clean up the Product Onboard Data data in Azure Devops.  Triage work items migrated or created in 2023 do not have any data in the Product Onboard data field. Will need to export to excel and update manually.  The Product Onboard Date will be the "Created date" in the archived onboard work item.  @ladonnaq

No further progress can be made until engineering completes the back-end work to add or expose new data fields for the dashboard.  Once this work is done, then we will resume activities on progressing the dashboard.


nixos-enter --help  needs elevated privileges

Describe the bug
nixos-enter does not show a --help output gracefully and instead crashes, when run without elevated privileges.
Steps To Reproduce
Steps to reproduce the behavior:
Run nixos-enter --help
❯ nixos-enter --help
Assertion `!(st.st_mode & S_ISUID) || (st.st_uid == geteuid())` in NixOS's wrapper.c failed.
/run/current-system/sw/bin/nixos-enter: line 16:     2 Aborted                 (core dumped) mount --make-rprivate /

Expected behavior
A clear and concise description of what you expected to happen.
nixos-enter --help
Should not require elevated privileges to run.

I couldn't find a maintainers attribute, so I will @ some people that committed to the shell script recently.
@lopsided98
@Enzime
@l0b0
@Artturin
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.63, NixOS, 22.11 (Raccoon)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.10.3`
 - channels(root): `"nixos-21.11pre304626.8ecc61c91a5, home-manager, home-manager-09-20.09, stable-21.03pre265961.891f607d530, unstable-21.03pre265961.891f607d530"`
 - channels(user): `"home-manager-20.03.tar.gz, nixos-20.09, nixos-20.09-20.09, unstable"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

This is still an issue.
Running nixos-enter without sudo in general produces this error. Very user-unfriendly.


[BUG] can't make crystalizer

[Please fill out the form below and delete the sections in square brackets after reading them]
Version of Advanced Rocketry

AdvancedRocketry-1.12.2-1.7.0-235-universal

Have you verified this is an issue in the latest unstable build

[x] N

Version of LibVulpes

LibVulpes-1.12.2-0.4.2-75-universal

Version of Minecraft

1.12.2

[x] N/A

Crash report or log or visualVM (if applicable)
http://pastebin.com is a good place to put them
crash reports that are put in the issue itself are
hard to read
Description of the problem

I try to make a crystallizer and there's just an x up and to the left and i don't know what to do

Use a holoprojector. that item allows you to project any multiblock structures with ease.

yet it doesn't really show the problem

Version out of date.

ok then. i'll try updating

i updated to AdvancedRocketry-1.12.2-1.7.0-240-universal and it did the same thing

a) that's still not the latest
b) you might want to take a look at your middle mouse wheel's scroll feature

i'm trying to update and i downloaded two libvulpes versions. they didn't work. I then tried to find out what the right version was by removing libvulpes all together and letting the crash tell me. i apparently need "%LIBVULPESVSERSION% or above (missing)"

you need a) the latest LV (possibly an alpha) and b) the latest AR (a beta I think), all the latest 1.12 versions

thank you! i figured it out. The reason i didn't think to scroll is cause i use a trackpad.


More details on File Blobs

More details on File Blobs

This issue was imported from Google Moderator
Moderator votes: +6
Issue added by Tim Fox on 2011-08-22
To vote this issue up or down, simply include +1 or -1 in your comment.

Probably refers to https://caniuse.com/#feat=mdn-api_file or https://caniuse.com/#feat=mdn-api_blob


Replace os.Setenv with t.Setenv in tests

Summary
It is recommended to use t.Setenv instead of os.Setenv in tests, so I replaced them.
How was it tested?
test and linter

/test

@savil How can I re-run failed tests?

@hezhizhen sorry about that. Could you rebase and try again? We had some sporadic failures on Friday, but those seem to have gone away today (from observing other PRs). Thanks!

Nevermind - it passed now 🙄 . Not great, but will look into it if this issue keeps reoccuring.
Thanks for the PR!


Convert Rx connection points created in molecules mode into chem attachment points in macromolecules mode

Background
Currently there is no way to define attachment points for molecules, so it is not possible to connect them in macromolecules mode with monomer.
Solution
Ketcher should handle R-Group labels and convert it to attachment points.
Molecules mode:

Macromolecules mode:

In Ketcher model and ket format attachment point contains information about leaving group atom and attachment atom.
Atom with R-Group label should be used as leaving group atom. Hydrogen (H) atom should be used here because r group label does not contain information about atom label.
Atom connected to R-Group label by bond should be used as attachment atom.

If there are more that one attachment atom for same R-Group label then attachment point should NOT be created.

Tests added to the automation table.

Verified.

Indigo Toolkit Version 1.20.0-dev.1.32-gf28bad61-wasm32-wasm-clang-12.0.0
Ketcher Version 2.21.0-rc.2 Build at 2024-05-13; 05:32:02
Chrome Version 124.0.6367.201 (Official Build) (64-bit)
Windows 10


Cache control when serving static files

We don't send cache headers when serving files and we don't respect conditional requests either.
See http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html

Looks like sending of the ETag response header and honoring of the If-None-Match request header was added in commit 3bcab36, shortly after this was filed. Is that enough to close this, or should we add support for the Last-Modified response header and If-Modified-Since request header?


Direct zip upload with worker to process uploaded files

Direct upload for zip files. Uses JS ActiveStorage library to send files directly to S3.

Few issues spotted:

when I upload eg. 100 files, checking files counter still show as 1 - Expected to show correct count 100 files
when I upload 100 files, page becomes very slow like frozen. - Need show some spinner or disable the continue button

Few issues spotted:

when I upload eg. 100 files, checking files counter still show as 1 - Expected to show correct count 100 files
when I upload 100 files, page becomes very slow like frozen. - Need show some spinner or disable the continue button


filter out non redhat artifacts comming from Brew

I've asked @ruhan1 to review this. If he's ok with it, please merge it.

It seems once this is enabled, we can only have one filter. Not sure it is enough. Do we need multiple patterns for the version filter?

@ruhan1 this is for the story https://projects.engineering.redhat.com/browse/NOS-1062 , to resolve the filter of non-readhat artifacts, so I wonder if multiple patterns allowed here, what's the relationship of the patterns? 'or' or 'and' ? Regular expression may describe these kinds of relationship. While multipe supports sounds good to further extension, depends on what the users will set. @jdcasey could you give a decision here?

@yma88, @ruhan1 I'm not sure if we need to have multiple version patterns in the config file. The point about how to combine them (and vs. or semantics) is a really good one...if we implement it one way, we can depend on someone at some point wanting it to be the other way.
Doing combinations in regex is usually not pretty...regex can be really hard to understand sometimes...but at least it is possible to do either and or or a regex. It's consistency, even if it's consistently ugly to mess with.
IMO this should work as it is, and if we need to refactor later to accommodate multiple patterns I think we can do it easily here.

Yeah, one single regex can do a lot. I have no problem with it. Please go
ahead merge it.
On Thu, Nov 9, 2017 at 12:42 PM, John Casey<EMAIL_ADDRESS>wrote:

@yma88 https://github.com/yma88, @ruhan1 https://github.com/ruhan1
I'm not sure if we need to have multiple version patterns in the config
file. The point about how to combine them (and vs. or semantics) is a
really good one...if we implement it one way, we can depend on someone at
some point wanting it to be the other way.
Doing combinations in regex is usually not pretty...regex can be really
hard to understand sometimes...but at least it is possible to do either
and or or a regex. It's consistency, even if it's consistently ugly to
mess with.
IMO this should work as it is, and if we need to refactor later to
accommodate multiple patterns I think we can do it easily here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Commonjava/indy/pull/826#issuecomment-343045806, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGL--siedUhn52b6ALquNdPEw4Mwtlf9ks5s0oKugaJpZM4QUj4E
.


Can't "Log in" ParsecSoda

When i opened ParsecSoda,exe and tap to "Log in" i saw rolling ring and words "Log in" again.
How it must work? And what i need to do log in parsecsoda?
Thanks

same.

if yall didnt know this whole project is dead due to parsec cutting 3rd party API requests


Ibex example Arty A7-100T

Simple example of how Ibex can be used to run software on a FPGA target.

Thanks a lot @imphil for the comments! I will incorporate those soon.

* Can we go for a unified address space for data and instruction, starting from 0? (So essentially remove the ROM/RAM masking.)

Changed to 0

* Can we go from a 2p memory to a 1p memory? The core won't issue a data and instruction operation at the same time anyways, so we can go simpler here (in line with having that a minimal example).  (Please ping me on Zulip if that paragraph doesn't make sense to you.)

Using 1p memory now

* Optional: 57 MHz looks rather strange. So I'd go back to 50 MHz if we cannot go higher to a number that looks "normal".

I only put in 57 MHz to show the highest one possible for now, but I agree, 50 MHz is nicer, so used this now again.

The core won't issue a data and instruction operation at the same time anyways, so we can go simpler here (in line with having that a minimal example).

@imphil This seems to be a convenient but surprising limitation. Why go for two buses at all at the top level of the Ibex if the two buses are never used simultaneously ?

I will make the changes to the documentation after the tracer PR is merged as this simplifies the rebase.

Looks like this is ready to be merged now?
One more thing: This currently doesn't support byte reads/writes. That's fine for now, but we should at least add a TODO in the code and file an issue for it.

I will add a TODO regarding the byte access.
My last push was already rebased on https://github.com/lowRISC/ibex/pull/77 so the commits are appearing here as well now, so we should wait until tracer is merged so I can rebase on the master branch for better attribution.

This should be ready after a rebase on top of master now that the tracer has gone in.

Thanks Tobias!


Bump to bare-metal 0.1.1

Needed to compile on current nightly

Thanks, @jonas-schievink.
@homunkulus r+

:pushpin: Commit c3d8ee7 has been approved by japaric

:hourglass: Testing commit c3d8ee7 with merge c3d8ee7...

:sunny: Test successful - status-travis
Approved by: japaric
Pushing c3d8ee714adaada8b79aa59db32b5f29a2ff35e5 to master...


Reorder Flaw update saving operations

OSIDB-3099 OSIDB-3049
Checklist:

[x] Linting passed
[x] Type checks passed
[x] Tests suite passed
[x] Commits consolidated
[x] Changelog updated
[ ] Manually test on stage
[x] Jira ticket updated

Summary:
Reorders save operations for updating flaws, flaw & affect component validation, refreshing for trackers.
Changes:

Change saving order

 - Affects, Delete Affects, Flaw CVSS, Flaw
 + Flaw, Flaw CVSS, Delete Affects, Affects

Added validations for presence of Flaw components in its affected offerings
Refresh trackers after filing trackers

Considerations:
Merge into stage for testing.
Closes OSIDB-3049.
Closes OSIDB-3099.

Does this one depend on https://github.com/RedHatProductSecurity/osim/pull/340?


bug:  "starter" lazyvim config throwing inlay_hint.lua errors

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.10.0-dev-2509+g633bf61d3
Operating system/version
Debian 6.6.15-2rodete2 (2024-03-19) x86_64 GNU/Linux
Describe the bug
After cloning lazyvim starter into .config/nvim, upon launching usual chugging of tree-sitter compiles eventually yields lazy starter page (but with the error shown in picture).  This is across multiple clean installs.

Steps To Reproduce

Issued following shell commands:

$git clone https://github.com/LazyVim/starter ~/.config/nvim
$ rm -rf ~/.config/nvim/.git
$ nvim
(note:  no further user input needed past here except occasional spacebar or ENTER in response to tree-sitter init prompts)

Sit through usual updating and churning of default components and settings.

Eventually processing ends at LazyVim "starter screen", only with error message overlay as per picture.

Expected Behavior
Resolve to LazyVim default "starter screen" WITHOUT error overlay.
Repro
-- bootstrap lazy.nvim, LazyVim and your plugins
require("config.lazy")

-- NOTE: Yes, completely default, no changes.

BTW, though I saw various mentions of historical inlay_hints.lua issues, I did not see anything where inlay errors were being displayed from a completely virgin installation at first launch.

You have an old nightly build 0.10-dev. Switch to 0.10 stable or a recent 0.11-dev nightly.


Issues with hubot-vault after upgrading

I've upgraded from 0.6.56 to 0.12.1, but I can't make it work.
This is the error message I get, so it seems that hubot-vault isn't loaded correctly:
2015-12-30T13:36:48.411640+00:00 app[web.1]:   at TextListener.callback (/app/node_modules/hubot-deploy/src/scripts/deploy.coffee:95:24)```

I ran into this before and tried dropping hubot-vault into my external-scripts.json but I'm not seeing that in my current, functional, hubot using this. I'll see what I can track down today.

@torbjornvatn I'm in the process of updating my slack bot now, but this should work for you.

I upgraded to 0.12.5 and the deploy command works as it should.
However it seems that deploys and where can I deploy has stopped working. I see that deploy.coffee was altered to use robot.emit in 0.10.0. Am I supposed to add some custom robot.on code like the one in the hipchat example, or is something missing?

I need to finish a slack example. Hopefully soon. :snowboarder:

So I got this mostly working in my personal slack tonight and noticed that I moved the default response for  "hubot deploys hubot" got moved to an event emission a few releases back.
If you take a look at this example you should be able to wire it up pretty easily. The "where can I deploy" behavior is here.
Now that I have everything mostly working I can hopefully figure out how to take advantage of some of the rich text formatting stuff available in slack.


Date based urgency calculations don't consider whether a task is done

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
Given the following tasks:
- [x] task 1 📅 2022-12-30 ✅ 2022-12-30
- [ ] task 2

I would expect task 2 to appear above task 1.
Current behaviour
Task 1 appears above task 2 in a task query using the default sort. The urgency calculation shows that task 1 is considered overdue, even though it's done.

task 1 📅 2022-12-30 ✅ 2022-12-30 13.95 (test)
task 2 1.95 (test)

Steps to reproduce
Create a file test.md with tasks:
- [x] task 1 📅 2022-12-30 ✅ 2022-12-30
- [ ] task 2

and task query:
tasks
path includes test.md

Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[ ] Linux
[X] macOS
[ ] Windows

Obsidian Version
1.1.9 (installer version 0.15.9)
Tasks Plugin Version
1.22.0
Checks

[ ] I have tried it with all other plugins disabled and the error still occurs

Possible solution
It depends if you want the urgency of a done task to be the same as before it was done or not.
If a consistent urgency score pre/post done isn't important, you could just set the urgency of done tasks to -1. Done tasks would be ordered in an undefined way below any tasks that aren't done.
If that consistency is desirable, the urgency calculation code could be updated to pass task.doneDate to moment for date calculations, like this:
const daysOverdue = Math.round(window.moment(task.doneDate).diff(task.dueDate) / Urgency.milliSecondsPerDay);

This would freeze the date based components of the urgency score on the day the task is done and prevent it from floating to the top of a list over time. With a null doneDate the behavior would be unchanged.

I guess nobody has reported this so far because usually done tasks are filtered out from views sorted by urgency since the whole concept of "urgency" makes no sense for done tasks.
But yes, maybe the urgency score should be modified for done tasks. I like the idea of using the done date instead of the current date for the calculations.
Note that there are also plans to make the whole urgency score function customizable, then you could change this as you like. But still, the default function should be somewhat reasonable and useful already.

Thanks @cito.
@tsaylor-spothero There has been a lot of discussion about changing the urgency score in the past, and it is such a subjective thing that I would not want to spend any time changing it, and would not support changing the algorithm.
One thing that arose out of the previous discussions was this, which I recommend you read and up-vote it is of interest:
https://github.com/obsidian-tasks-group/obsidian-tasks/discussions/1162
If you don't give a sort instruction, the order of sorting is:
        const defaultComparators: Comparator[] = [
            new UrgencyField().comparator(),
            new StatusField().comparator(),
            new DueDateField().comparator(),
            new PriorityField().comparator(),
            new PathField().comparator(),
        ];

So you have the option of using a different order, by providing your own sort instructions.
So you could do something like this, to sort by status first, and only afterwards, sort by urgency:
sort by status
sort by urgency

or the opposite - depending on which way you want them to appear.
sort by status reverse
sort by urgency

Looking at that default sort order above, I think it was intentional for status to not be included in the urgency field, and I think that no action is required on this issue.

Maybe we should then add in the documentation that a filter for urgency should be combined with a filter or sort for status?

Maybe we should then add in the documentation that sorting urgency should be combined with a filter or sort for status?

That’s an excellent idea. It’s not something I will got to for quite some time, as mired much more deeply  in the custom status work than I expected.

I've put the documentation label on this as a reminder not to close this.
And I've added the help wanted label - picking up from this comment: https://github.com/obsidian-tasks-group/obsidian-tasks/issues/1480#issuecomment-1374480628

I've just discovered that the docs are wrong for the default sort order:
https://obsidian-tasks-group.github.io/obsidian-tasks/queries/sorting/
They only talk about a single default sort order, not the several listed in a comment above:

I'm starting to form the view that I should change the default sort order to reverse these two:
From this:
        const defaultComparators: Comparator[] = [
            new UrgencyField().comparator(),
            new StatusField().comparator(),

to this:
        const defaultComparators: Comparator[] = [
            new StatusField().comparator(),
            new UrgencyField().comparator(),

I think I can claim this is a bug-fix rather than a breaking change.
Any thoughts?

In Tasks 6.

I'm starting to form the view that I should change the default sort order to reverse these two:
From this:
        const defaultComparators: Comparator[] = [
            new UrgencyField().comparator(),
            new StatusField().comparator(),

to this:
        const defaultComparators: Comparator[] = [
            new StatusField().comparator(),
            new UrgencyField().comparator(),

I think I can claim this is a bug-fix rather than a breaking change.
Any thoughts?

The above change was made in Tasks 6.0.0. The code now looks like this:
https://github.com/obsidian-tasks-group/obsidian-tasks/blob/b954d241221463a5f2a361891e27ee148ab2869e/src/Query/Sort/Sort.ts#L25-L33
I also finally added a documentation section explaining the Default sort order.
I did label it a breaking release.
Closing this as done.


the catalog can change when using Presto connection

Now, we can setup several presto connections for every presto catalog, I need to achieve that :
I only setup one presto connection with/without default catalog and can change every catalog in region Toggle Schema, like yanagishima

I think this sort of aligns with similar requests for other databases as well, like SQL Server or MySQL where multiple "databases" can be on a single server and queried against.
I'm not opposed to this, but it could potentially involve a lot of work. I don't know that I have the time but if someone wants to open a PR for it I'd gladly accept.
@dengc367 something I'm curious about: how would you anticipate saved queries working? Would you expect the query to also save the database/catalog name that is selected?

I think that it need not to save the database/catalog name in the saved queries.

when I have the time, I develop this feature. At first I think whether there will be another good solution.


4.11 Req: migrate to klogv2

You should not need k8s.io/klog v1, none of k8s should be using it at this point in time.
klog/v2 even though a bit limited should be preferred for logging over any other solution.

/assign @sfxworks

@sfxworks The dep change includes a change in the flags because of the difference between setting the level with logrus and klog. log-level will need to be replaced with -v=X X being 1-9.


[All Hosts] (runtimes) add overview of runtimes

Docs Build status updates of commit 7e2fc33:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/testing/runtimes.md
:warning:Warning
View
Details

docs/toc.yml
:white_check_mark:Succeeded
View

docs/testing/runtimes.md

Line 110, Column 606: [Warning: file-not-found - See documentation] Invalid file link: '../develop/configure-your-add-in-to-use-a-shared-runtime'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit e2eb733:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit d630270:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 9790c9c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 6e879a6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 582a71e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f0acb70:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 3e0fdc1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 129aae7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5eb610f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ededdab:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 43af531:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit d08f602:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/testing/runtimes.md
:warning:Warning
View
Details

docs/toc.yml
:white_check_mark:Succeeded
View

docs/testing/runtimes.md

Line 94, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 468e4d2:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/testing/runtimes.md
:warning:Warning
View
Details

docs/toc.yml
:white_check_mark:Succeeded
View

docs/testing/runtimes.md

Line 94, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit fdafd10:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/testing/runtimes.md
:warning:Warning
View
Details

docs/toc.yml
:white_check_mark:Succeeded
View

docs/testing/runtimes.md

Line 94, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 7dce0a2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ec5dcac:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/testing/runtimes.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Advanced search?

@caseyedavis12 : Do we need an advanced search on OV like on AAPB? If you want the same functionality, it is relatively low cost to copy and paste, though we could try to make a gem out of it. But if we don't need it, great.

@mccalluc: We don't need an advanced search for Open Vault.

yay.


Add 404 error return

title, this was me attempting to code and make a PR for a C# project
idk if this works because I have no way to test it

lol

This is not needed at all, as anything can be sent from client --> server and vice versa. It is not for modifying to your needs. You use it elsewhere, including handling.

okay, there's really no need to get savage

That wasn't my intent. My intent was to be direct and to logically respond. Sorry if I came off that way.

yeah, it's fine

If ya need any assistance, or just want to hang out, hmu at Kanna#0002

alright 👍🏻


Fix equal operation for typed enums

Summary
Fix #49278
Screen proof:

How I Fix it
op_binary can't compare two builtin_type. ENUM_VALUE returns Variant::NIL and ENUM returns Variant::DICTIONARY. Problem was in default value for builtin_type, because for ENUM_VALUE we doesn't set builtin_type and using default Variant::NIL

For the reference, the email used to author your commit (see header of https://github.com/godotengine/godot/commit/6449c5f2464076ab51d4955bf5b8e627beefb8ce.patch) is not linked to your GitHub account, which is why the commit doesn't appear authored by your @SpectralDragon account. It's not a problem for Git or GitHub, but if you want to have your GitHub account credited for the contribution, you can add this email as secondary email in your settings.

I’ll update it a couple of hours

@akien-mga I added my email as secondary to Github. Thanks for suggestion!

@vnen can you look at this PR?

Thanks!


What's the syntax for adding multiple named arguments to the "Arguments" box?

I came here looking for this, but couldn't see. Better yet, it should be available in the info button at the UI.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 77731c06-e4fd-8125-0daf-870c9ccedd3f
Version Independent ID: 0d5c338d-80f9-c64e-b675-bf7b4eb8e32b
Content: Use a PowerShell script to customize your build pipeline - Azure Pipelines & TFS
Content Source: docs/pipelines/scripts/powershell.md
Product: devops
GitHub Login: @andyjlewis
Microsoft Alias: alewis

Closed this since I've found it already. But note that it may not be obvious to people not used to Microsoft tools that the arguments should be passed just like you pass to a Powershell script.


chore: add migration notes to recent address changes and npk_m comment fixes

Title

Docs Preview
Hey there! 👋 You can check your preview at https://6724aae808b6750e8b228c06--aztec-docs-dev.netlify.app


Documentation for vector of union

Hello,
I am trying to use a vector of union in my flatbuffers' schema, but unfortunately, there is no documentation how this could be achieved.
// schema.fbs
union Layer { Domain, User }

table Structure {
  layers:[Layer];
}
table Domain {
  loc:int32;
}
table User {
  example:int32;
}

Currently I am using the following code to write into the buffer, which seems to be fine (Am I already wrong here?).
// write
flatcc_builder_init(B);

structure_Domain_ref_t domain_1 = structure_Domain_create(B, 2);
structure_Layer_union_ref_t domain_union_1 = structure_Layer_as_Domain(domain_1);

structure_Domain_ref_t domain_2 = structure_Domain_create(B, 3);
structure_Layer_union_ref_t domain_union_2 = structure_Layer_as_Domain(domain_2);

structure_Layer_vec_start(B);
structure_Layer_vec_push(B, domain_union_1);
structure_Layer_vec_push(B, domain_union_2);
structure_Layer_union_vec_ref_t layers = structure_Layer_vec_end(B);

structure_Structure_start_as_root(B);
structure_Structure_layers_add(B, layers);
structure_Structure_end_as_root(B);

uint8_t *buf = flatcc_builder_finalize_buffer(B, size);

I cannot figure out, how I am able to read the vector of union from the buffer again:
// read
structure_Structure_table_t structure = structure_Structure_as_root(buf);
// is this the correct type?
structure_Layer_vec_t layers = structure_Structure_layers(structure);
size_t layers_len = structure_Layer_vec_len(layers);

for(int i = 0; i < layers_len; i++) {

  // is this the correct type?
  const structure_Layer_union_type_t ith_layer = structure_Layer_vec_at(layers, i);
  // is always false?
  if(ith_layer == structure_Layer_Domain) {
      // not sure how to parse or access the layer/ lines of code field?
   } else {
        printf("else");
    }
}
// -> leads to segmentation error

Does anyone have a similar problem or any ideas how to solve this?
EDIT:
I am sorry, this is my fault. I found the test that covers union vectors as described in the README and was able to solve my problem:
void read(uint8_t *buf, size_t size) {
    structure_Structure_table_t structure = structure_Structure_as_root(buf);
    structure_Layer_union_vec_t layers = structure_Structure_layers_union(structure);
    size_t layers_len = structure_Layer_union_vec_len(layers);

    for(int i = 0; i < layers_len; i++) {
        structure_Layer_union_t ith_layer = structure_Layer_union_vec_at(layers, i);

        if(ith_layer.type == structure_Layer_Domain) {
            structure_Domain_table_t domain_layer = ith_layer.value;
            int32_t loc = structure_Domain_loc(domain_layer);
            printf("Domain with loc:  %d", loc);
        } else {
            printf("else");
        }
    }
}

For reference, her is the link to the builder documntation:
https://github.com/dvidelabs/flatcc/blob/master/doc/builder.md#union-vectors


issue with onClick option

When I declare an onCLick option  like this :
options = {
'onClick': 'graphClickEvent',
}
The generated JSON is  : "onClick" : "graphClickEvent"
Expected is "onClick" : graphClickEvent
This code in init.py:get_configuration() solves this issue :
def get_configuration(self, *args, **kwargs):
config = self.chartjs_configuration(*args, **kwargs)
jsonrender=json.dumps(config, cls=self.json_encoder_class)
pat=re.search('"onClick" *: *"\w+"',jsonrender)
tab=re.split('"onClick" *: *"\w+"',jsonrender)
f=re.search('"onClick" *: *(?P"\w+")',pat.group())
    if f.group('fonction') is not None:
        return '%s %s %s'%(tab[0],re.sub(f.group('fonction'),f.group('fonction').replace('"',''),pat.group(0)),tab[1])
    else:
        return jsonrender

Hi, thank you for this contribution. Would you be willing to create a PR solving this issue. Potentially we should also update the examples on the website reflecting the usage of onClick configuration option.

OK I'm going to create a PR asap.
J.y

Le 15 oct. 2017 à 17:07, Matthisk Heimensen<EMAIL_ADDRESS>a écrit :
Hi, thank you for this contribution. Would you be willing to create a PR solving this issue. Potentially we should also update the examples on the website reflecting the usage of onClick configuration option.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Has this PR been created an merged? I am still seeing the same behavior that options={'onClick':'graphClickEvent}` gets translated to a quoted version of graphClickEvent in the javascript, and clicking on the item returns an error in the console: Uncaught TypeError: n.onClick.call is not a function.


Request: Don't start dragging unless cursor been dragged x pixels.

I ran into an issue where I have items that expand when clicked. When making them sortable they no longer respond to a click, instead they become dragged immediately. I can get around this by setting the "pressDelay" but then you have to wait for the delay before it's draggable which I noticed that people tend not to do.
I'd like a way to not start the sorting unless you have actually dragged the cursor for say 5px.

Yes, I guess it will be much more evident to users than "pressDelay" option
Really looking forward to this feature too

I encountered a similar issue with sortable FlexTable rows. My table contained <input> tags which stopped working when I made the whole row draggable. (Clicks on the <input> would just start a drag.) I ended up using the drag-handle approach, which works pretty well. But if there was some sort of threshold it might be nicer still.
This might still lead to edge-cases when it comes to things like text-selection so maybe some way to cancel/block a drag (eg #36) might also be nice.

Just published 0.0.8 with this feature. Just pass in a distance prop to your SortableContainer.
Alternatively, you may also use shouldCancelStart, which was just released today as well. This function gets invoked before sorting begins and can be used to programatically cancel sorting before it begins.
Here's the default implementation:
function shouldCancelStart(e) {
    // Cancel sorting if the event target is an `input`, `textarea`, `select` or `option`
    if (['input', 'textarea', 'select', 'option'].indexOf(e.target.tagName.toLowerCase()) !== -1) {
        return true; // Return true to cancel sorting
    }
}

aww yeah!

Sweet, thanks @clauderic!


operator: Filter vault-operator cache to reduce memory usage

Q
A

Bug fix?
yes

New feature?
no

API breaks?
no

Deprecations?
no

Related tickets
fixes #1288

License
Apache 2.0

What's in this PR?
Upgrade controller-runtime to latest release (v0.11.2) and filter cache to only target those resources created by the controller/labeled with common keys. app.kubernetes.io/name in (vault, vault-configurator)
Why?
In clusters with large number of configmaps, vault-operator memory usage is very high (~2Gi for 60k configmaps). While no cluster should have that many, I think we don't need to cache all of those.
Additional context
In previous conditions, using v1.15.2, this is the memory usage ~1m after launch:
# k top pods -n keos-core vault-operator-86b8bf4596-gqpgr
NAME                              CPU(cores)   MEMORY(bytes)
vault-operator-86b8bf4596-gqpgr   85m          2091Mi

This is the memory usage with the changes included in this PR in the same conditions:
# k top pods -n keos-core vault-operator-65d6c98759-wvbwp
NAME                              CPU(cores)   MEMORY(bytes)
vault-operator-65d6c98759-wvbwp   2m           33Mi

Checklist

[x] Code meets the Developer Guide
[x] User guide and development docs updated (if needed)
[x] Related Helm chart(s) updated (if needed)

To Do

[ ] Check if all the kinds filtered actually have the right label
[ ] Haven't thoroughly tested all features of vault CR

 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.

Don't worry we have a flaky test framework around the webhook, this works fine locally! (resources on GitHub is a bit little for the whole setup with Kubernetes).

I was checking the logs of the acceptance test and it looks like the vault-configurer pod can't start now for some reason, that is probably because of the changes (not the flaky part of the test).

I think I can take a look at it. Any errors in the log?

Yes, it seems that there is no vault-config file available for the configurer (all in the build logs):
+ kubectl logs deployment/vault-configurer
Found 2 pods, using pod/vault-configurer-6f7fbd89b8-qk2fz
{"level":"info","msg":"vault metrics exporter enabled: :9091/metrics","time":"2022-05-13T18:51:27Z"}
{"level":"fatal","msg":"error reading vault config template: open vault-config.yml: no such file or directory","time":"2022-05-13T18:51:27Z"}

hi @majimenez-stratio @bonifaido and thans for fix.
Is there any timeline hen we can expect this changes to be released ?
Thanks a lot!

@majimenez-stratio once you are there please rebase on the main branch.

Sorry, didn't have the time to look at it. Hope I find some time during the week to fix the issues with vault-configurer. Sorry!

Sorry @bonifaido, I rebased the PR but I can't find the error you mentioned. What I'm getting is this error instead:
+ kubectl logs -n vswh deployment/vault-secrets-webhook
Error from server (NotFound): namespaces "vswh" not found
Error: Process completed with exit code 1.

Any advice on how can I fix this one?
Moreover, I think vault-configurer is working as expected without any further change, according to the latest build logs:
2022-06-03T05:12:23.5994754Z + kubectl logs deployment/vault-configurer
2022-06-03T05:12:23.6783533Z {"level":"info","msg":"vault metrics exporter enabled: :9091/metrics","time":"2022-06-03T05:11:20Z"}
2022-06-03T05:12:23.6784616Z {"level":"info","msg":"applying config file : /config/vault-configurer/vault-config.yml","time":"2022-06-03T05:11:20Z"}
2022-06-03T05:12:23.6786025Z {"level":"info","msg":"checking if vault is sealed...","time":"2022-06-03T05:11:20Z"}
2022-06-03T05:12:23.6787135Z {"level":"info","msg":"watching directory for changes: /config/vault-configurer/","time":"2022-06-03T05:11:20Z"}
2022-06-03T05:12:23.6788223Z {"level":"error","msg":"error checking if vault is sealed: error checking status: Get \"https://vault.default:8200/v1/sys/seal-status\": dial tcp <IP_ADDRESS>:8200: connect: connection refused, waiting 5s before trying again...","time":"2022-06-03T05:11:24Z"}
2022-06-03T05:12:23.6788988Z {"level":"info","msg":"checking if vault is sealed...","time":"2022-06-03T05:11:29Z"}
2022-06-03T05:12:23.6789960Z {"level":"error","msg":"error checking if vault is sealed: error checking status: Get \"https://vault.default:8200/v1/sys/seal-status\": dial tcp <IP_ADDRESS>:8200: connect: connection refused, waiting 5s before trying again...","time":"2022-06-03T05:11:33Z"}
2022-06-03T05:12:23.6790710Z {"level":"info","msg":"checking if vault is sealed...","time":"2022-06-03T05:11:38Z"}
2022-06-03T05:12:23.6791233Z {"level":"info","msg":"vault is unsealed, configuring...","time":"2022-06-03T05:11:38Z"}
2022-06-03T05:12:23.6791798Z {"level":"info","msg":"adding auth method kubernetes (kubernetes)","time":"2022-06-03T05:11:38Z"}
2022-06-03T05:12:23.6792383Z {"level":"info","msg":"removing group-aliases ... map[string]string","time":"2022-06-03T05:11:38Z"}
2022-06-03T05:12:23.6792927Z {"level":"info","msg":"adding policy allow_secrets","time":"2022-06-03T05:11:38Z"}
2022-06-03T05:12:23.6793447Z {"level":"info","msg":"adding secret engine secret (kv)","time":"2022-06-03T05:11:38Z"}
2022-06-03T05:12:23.6793975Z {"level":"info","msg":"successfully configured vault","time":"2022-06-03T05:11:38Z"}

@majimenez-stratio the project has been migrated to https://github.com/bank-vaults/vault-operator.
In addition, we have also updated the controller-runtime to the latest version, so this might not be relevant anymore.
If you can test it out with the latest vault-operator version, we can decide if this needs to be reopened.


Add vendored feature to zstd-sys for providing pre-built zstd libs

I would like to be able to provide my own libzstd.a when building zstd-safe. This change introduces the vendored feature in combination with the following environments to support this:

ZSTD_SYS_VENDORED: An extra flag to enable the vendored search even if the feature is not enabled
ZSTD_SYS_VENDORED_LIBS: A space delimited string of paths to compiled zstd libraries
ZSTD_SYS_VENDORED_INCLUDE: The path to the zstd include directory where headers like zstd.h can be found.

The naming of the feature was inspired by https://docs.rs/openssl/latest/openssl/#vendored

Hi, and thanks for the report!
Is there any way this could be done with the current pkg_config feature?


Cslang

Description
Integrate cslang into source academy frontend as another language tab that allows for programming in C.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

PR is currently a work in progress (in midst of enhancing compilation error reporting on frontend). Will request your review @RichDom2185 after its completed and will fix the formatting issues before that.

PR is currently a work in progress

Ok sure, I'll mark it as draft first in that case so that it won't be touched by others. Thanks!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

6 of 51 (11.76%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.08%) to 35.16%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/commons/utils/AceHelper.ts
0
1
0.0%

src/commons/editor/Editor.tsx
2
5
40.0%

src/commons/utils/CToWasmHelper.ts
2
22
9.09%

src/commons/sagas/WorkspaceSaga/helpers/evalCode.ts
1
22
4.55%

Totals

Change from base Build<PHONE_NUMBER>:
-0.08%

Covered Lines:
5103

Relevant Lines:
13548

💛  - Coveralls


Modes of Paymaster seems unclear

How could we improve the Biconomy documentation site?
I think we should have 2 different sections along with "Integration" in Paymaster. The sections should be "Sponsored" and "ERC20", and in each one of them integration of modes should be explained respectively. In the current scenario, we have spoken about feeQuotes and response at the beginning of "Methods" section and have defined modes below it, which is quite confusing and unclear.

so these pages are for paymaster package integration, are you looking for a paymaster only flow methods integration example?
smart account already have these calls integrated in the sendTransaction.

The core problems are below

Users are unable to understand if in order to use the SDK, do they need to check the paymaster and bundler sections also.
Restructure the docs to showcase Account abstraction SDK in such a way that its intuitive that one doesn't need bundler or paymaster package/ methods to use the SDK
Tutorials are not visible - for example the gasless and ERC20 tutorials are not visible directly.
Mention in the quickstart and overview
Method param definition like maxApproval
Add references to the tech documentation (tsDocs) and improve tsDocs for param definitions, given there are a lot of params in each method

Apart from these we can mention in the Overview page, how to use docs.


bug: CoreImage documentation

Description
CoreImage documentation has indentation problems, need to be fixed

Closing as done.

CoreImage needs to be restructured as per #211


Fix WorldMapOverlay to draw pixel perfect on the WorldMap

Fixes a poorly implemented getPixelsPerTile to make the WorldMap tile sizing more predictable. (In practice it is not a noticeable change unless you are drawing overlays)

This is ready to be reviewed / merged

Merged as part of #2451


Expander: Move to public

Description

Only needed to move to public, API spec seemed to be identical to the current implementation. There still seems to be an ongoing discussion how background/foreground should propagate and what lightweight styling resources should be added. Those already listed in the spec are present.
Motivation and Context

Closes #4147
How Has This Been Tested?

Tested manually
Screenshots (if appropriate):

/azp run


Create WDS select component

Hey team! Please add your planning poker estimate with Zenhub @dhruvikn @jsartisan @KelvinOm

@KelvinOm - before adding my estimate for the planning poker, can you please add the designs and/or any relevant docs for this component? I would like to gather some context before estimating.

Please add your planning poker estimate with Zenhub @jsartisan

@dhruvikn

Reuse the wds components Menu and TextInput as the basis of the Select.
As part of the task, it is necessary to analyse the property pane in prod and add the necessary functionality (create tickets for this).

Have added my estimate.


Window size forwarding not working on Darwin

Need _DARWIN_C_SOURCE to get the SIGWINCH definition.

On Darwin, open(slave_name, O_RDWR | O_NOCTTY) is needed before doing TIOCSWINSZ in the parent process. I don't know why.


min_child_samples plays bad with weights

Description
I'm revisiting a previous report of mine: https://github.com/microsoft/LightGBM/issues/3634
I've been having lots of trouble trying to fit models with heterogeneous sample weights, for example:

Stratified sampling on the response (Horvitz-Thompson), when there are too many zero responses I sample them down with some probability of inclusion pi and then compensate using weight 1 / pi.

In logistic regression, sometimes I group a run of zeros or a run of ones having the same X so the size of the group is given by the weight of the observation.

The heuristic implemented for min_child_samples works poorly in cases like these, for example requiring min_child_samples = 200 yields many nodes with less than 10 observations. In many cases, this is unacceptable, selected models are extremely noisy and the selection itself is dominated by the variance of the cv error estimate.
Some alternatives are using ridge regularization in order to change the prior (like if there were a number of extra zero observations inside the leaf) or using min_child_weight to bound the hessian. The first alternative introduces shrinkage that's not always the best option while the second one is difficult to fine tune since although the hessian is related to the sum of weights, the exact relationship depends on the type of regression, the current estimate and the value of the independent variable.
I believe a simple and reliable control over the number of samples in a leaf is an important hyperparameter, but the current heuristic isn't reliable.

@memeplex Thanks. I do think it is necessary to provide an exact control over min_child_samples. Will include this as a feature request.

Closed in favor of being in https://github.com/microsoft/LightGBM/issues/2302. We decided to keep all feature requests in one place.
Welcome to contribute this feature! Please re-open this issue (or post a comment if you are not a topic starter) if you are actively working on implementing this feature.

I've been trying to fix this issue. I tried a number of approaches:

Make hist_t a struct with grad, hess and cnt fields. But the current representation as a series of doubles alternating grad and hess is leaking everywhere, it's very very difficult to get this right, not because of any conceptual complexity but simply due to the many accesses to the internal representation of a histogram, lots of << 1 and * 2 and pointer arithmetic here and there. A lot of this code I'm not even able to test (e.g. CUDA).
When building a histogram don't add buckets with cnt < min_child_samples at the beginning or end of the hist array, but accumulate until cumcnt >= min_child_samples, so splits at the leftmost and rightmost buckets of the hist are not considered unless enough samples have been accumulated. But since buckets are filled in a random order I still need to keep all counts somewhere while creating the histogram and then accumulate and remove leftmost and rightmost buckets at the end of histogram creation. After this, I can get rid of the temporary counts array.
This is the quick&dirty approach: use the lower bits of the mantissa of the hessian to keep a value count. Since the hessian is represented as a double, there are 52 bits of mantissa. For normal floating points numbers, which are always of the 1.dddd... form, using about 12-13 least significant bits won't affect precision in any appreciable way (more than 10 decimal digits of separation from the most significant digit). This also works with subnormal numbers, indeed. Moreover, hessians are only added so there will be no cumulative relative error. This is the easiest solution I can figure out, most things will keep working with a tiny error while no extra memory is used and counts are represented exactly up to some number of bits.

Thanks for working on this!
Re-opening the discussion since you're working on it, and tagging @guolinke and @shiyu1994 to help respond to you when they have time. Please be patient, as the project's small maintainer team is very focused right now on issues critical to the next release (#5153).


Policy for supporting and testing against various OpenStack version?

Hi folks,
I see in the README this project CI's against Liberty, Mitaka, and Newton.  According to https://releases.openstack.org, Liberty and Mitaka are past EOL and Legacy Support (Phase III), and Ocata and Pike have been released this year.

How are the versions of OpenStack that get tested decided today?
Do the versions of OpenStack supported by this CPI correspond 1-to-1 with the versions that are CI'd against, or is there any notion of declaring support for other versions and just not testing against all supported versions (because there may be other factors making it difficult to test against so many versions)?
Going forward, would there be any thought towards having a CI policy expressed in terms of the upstream https://releases.openstack.org policy, e.g. CI'ing the most recent EOL version plus all but the most recent active (non-EOL) versions?
Likewise, what about a support policy also expressed in terms of upstream supported versions.

I'm sure in reality there are complexities related to how you're getting your OpenStack test environments (e.g. from some vendor), but I wonder if there could be a more generally predictable or vendor-agnostic policy that's not too far outside what's possible to actually test against.

Hi @Amit-PivotalLabs,
thanks for bringing this up! Let's talk first about the theory behind what we're doing and then we get to the practicalities.
theory

How are the versions of OpenStack that get tested decided today?

That's currently decided very locally in our team. We don't have an official process for this.

Do the versions of OpenStack supported by this CPI correspond 1-to-1 with the versions that are CI'd against, or is there any notion of declaring support for other versions and just not testing against all supported versions (because there may be other factors making it difficult to test against so many versions)?

We only list 'supported versions' when we actively CI against them.

Going forward, would there be any thought towards having a CI policy expressed in terms of the upstream https://releases.openstack.org policy, e.g. CI'ing the most recent EOL version plus all but the most recent active (non-EOL) versions?

That was our goal when we started: Supporting whatever OpenStack lists as 'officially supported' releases (i.e. the last 3 ones) plus potentially the newest EOL version.

Likewise, what about a support policy also expressed in terms of upstream supported versions.

I'm not sure how you distinguish between 'support policy' and 'CI policy' from the previous question. Could you elaborate a bit more on the difference?
practice

we're unable to setup and maintain stable OpenStack environments from open-source upstream ourselves, therefore we rely on a vendor to do this for us
OpenStack is released twice a year, most OpenStack vendors, however, only release a product once per year. We do have an agreement, though, to also get the 'intermediary' releases of OpenStack being setup for us
the vendors' releases lag behind the official release dates by ~3-4 months. This means: while OpenStack pike was released in October 2017, we don't expect a product based on Pike before January 2018

Currently, the situation is especially bad, given that we don't even have an Ocata based test setup running. I understand that for everyone setting up a DevStack to test BOSH against the most recent OpenStack versions it seems weird, that we only test against versions which are EOL for quite some time.

I wonder if there could be a more generally predictable or vendor-agnostic policy that's not too far outside what's possible to actually test against

We're open for suggestions to improve the situation. Recently, I had a look at vendors providing a publicly available OpenStack, but didn't find a good solution. Do you have anything specific in mind?

Thanks @voelzmo !

I'm not sure how you distinguish between 'support policy' and 'CI policy' from the previous question. Could you elaborate a bit more on the difference?

For example, imagine that due to practical considerations you are only able to CI against M and N, but you nonetheless want to signal to users that you're sufficiently confident they can use the CPI against L and O as well.  In that case, you could say you CI against M and N, and support L-O.
A general policy might look like: "we CI against all but the latest active release plus the latest EOL release (so today that would equal M-O) and we support additionally the latest active release plus the next-to-latest EOL release (so today that would equal L-P)."
Not saying that's a good or bad policy, just an example of what a CI policy and support policy could look like.
Here "support" of course just means what it typically means for OSS projects, "we think you'll be successful using it and can help answer questions if you have any," not "you can call us in the middle of the night."  I think vendors would like to say, "we will commercially support whatever the OSS CPI project claims to support."  This gives vendors a more predictable message, so that customers don't have to ask the question every time: "now Queens is out, does  support BOSH on Queens"?
There are lots of moving pieces:

OpenStack support policy for releases
OpenStack vendor support policy for their distributions
what CPI team CIs/supports
BOSH vendor support policies

I'm trying to think about which of these policies can be turned into predictable functions of the upstream policy.  In an ideal world, your vendor sticks to your aforementioned agreement with them, allowing the CPI team to CI against a predictable set of OpenStack releases.  Ideally the CPI team also has a support policy that is a predictable function of that (maybe CI'd versions == supported versions, maybe supported versions include 1 extra ahead and/or behind the set of CI'd versions, etc.).  Then BOSH vendors can have some some support policy that is a function of the CPI policy.  And ultimately BOSH customers can more easily reason about their future plans around OpenStack.

we're unable to setup and maintain stable OpenStack environments from open-source upstream ourselves, therefore we rely on a vendor to do this for us

I can empathize with that pain!

We're open for suggestions to improve the situation. Recently, I had a look at vendors providing a publicly available OpenStack, but didn't find a good solution. Do you have anything specific in mind?

With respect to OpenStack vendors, no, I think this is an industry-wide challenge.  It's definitely understandable.  Just wanted to have a conversation and understand your team's thinking on this general question of how can customers of BOSH-on-OpenStack reason about their future OpenStack plans as the upstream OpenStack project continues to ship and EOL releases?

Hey @Amit-PivotalLabs
Sorry for not following up on this more timely.
I do agree with many of the things you said. We should really get back on track with the original plan to CI and officially support all OpenStack releases that are non-EOL'ed. We should also communicate that this is our policy and act predictively on it. Ideally, we'd also do additional tests with the currently developed version once it comes closer to being released, so we could ensure it works from day 1 of a new release.
In the past, I've wondered, if the people asking about "does the CPI work on OpenStack X?" shortly after it being released are actually using a hand-rolled open-source version of OpenStack, or if this is more of an academic exercise. In my experience, vendors take their time releasing new versions and skip one release per year. Additionally, many people seem to struggle with updating their OpenStack installations, so I don't see many companies updating their stack twice a year.

Sorry for not following up on this more timely.

No sweat :)

We should really get back on track with the original plan to CI and officially support all OpenStack releases that are non-EOL'ed. We should also communicate that this is our policy and act predictively on it. Ideally, we'd also do additional tests with the currently developed version once it comes closer to being released, so we could ensure it works from day 1 of a new release.

That would be hot!

In the past, I've wondered, if the people asking about "does the CPI work on OpenStack X?" shortly after it being released are actually using a hand-rolled open-source version of OpenStack, or if this is more of an academic exercise.

Maybe "academic" isn't the right characterization, but it's more about planning.  Some organizations may start planning an upgrade to a new Openstack version many months in advance of doing it, and they need to see if all their ducks will be in a row when that time comes, so they will want to know whether BOSH will be ready at that point in time.

In my experience, vendors take their time releasing new versions and skip one release per year.

I tend to see Cloud Foundry adopted by very large enterprises, and these large enterprises often have special support from their Openstack vendors.  Very often this takes the form of the vendor supporting a version of Openstack that has gone EOL from the OSS perspective.  I can imagine this also taking the form of a vendor providing support for a very new version of Openstack to a large enterprise account that they wouldn't make generally available right away.

Also, a data point with regards to vendor support timelines vis a vis OSS timelines, it looks like RedHat makes their versions GA about 3 months after OpenStack org's official release date, and ends maintenance support about 3 months after OpenStack's EOL date.  Compare OpenStack Releases with the Life Cycle Dates section of Red Hat OpenStack Platform Life Cycle

This would be very helpful, thanks for reaching out @dims. Let's continue to discuss some details in the cf slack #openstack channel!

Fixed with https://github.com/cloudfoundry/bosh-openstack-cpi-release/commit/d292dddaaeef55701abf04177edab7b807e53721
Official support policy is now at https://github.com/cloudfoundry/bosh-openstack-cpi-release#supported-openstack-versions
Let me know if this policy doesn't work for you, or if we should word it differently to help you in discussions with your customers.
Thanks @Amit-PivotalLabs for bringing this up and all the OpenLab people for helping us setting this up!

Thanks!


Product-Level analytics

Includes reporting for all events that Amelia/Kevin/I identified as wanting in the first pass for product-level analytics. The GoogleAnalyticsUtils and GoogleAnalyticsFields classes provide good context and explanations for what was added, and I outlined/explained the hierarchy of event reporting in more detail here: https://docs.google.com/a/dimagi.com/spreadsheets/d/1-vdt6oiaHwNcbN7Dz6qc6o69RA3J5C-eLP85hf0z2po/edit?usp=sharing
Ready for review but don't merge yet; missing some small final add-ons like legal stuff
@dimagi/product

Nice!
Finished a pass and left some questions and actionable items.

Heads up that a change removing the "Call Log" settings entry has been merged into master.

@amstone326 What's the minimum API verison of the google analytics API's, btw? A few places in the code make it look like it's > than our min, but the code doesn't seem to reflect that on the whole

@ctsims Addressed and implemented changes for all comments except the 1 that I didn't really understand. Left a question about my solution to the version compatibility issue.

@amstone326 Ok, this looks pretty legit now. I think we should likely kill the user ID caching, and there's the 2.2 test pending, but am happy with the code overall.

@ctsims I added the opt out language for legal, and added the functionality you wanted for tracking CC Version with app installs. This should be good to pull now that we know we're not doing anything for 2.2 compat!

Awesome!! Can we re-run on 2.3.7 and make sure we're good on that as well?
I think should be fine, but want to make sure the new odd inclusions are
working.
-Clayton
On Thu, Jan 21, 2016 at 1:30 PM, Aliza Stone<EMAIL_ADDRESS>wrote:

@ctsims https://github.com/ctsims I added the opt out language for
legal, and added the functionality you wanted for tracking CC Version with
app installs. This should be good to pull now that we know we're not doing
anything for 2.2 compat!
—
Reply to this email directly or view it on GitHub
https://github.com/dimagi/commcare-odk/pull/816#issuecomment-173665699.

@ctsims What are "odd inclusions"?

The way we're injecting the new libraries, mostly (with the overwrite
stuff), but we may not need to do that anymore with the 2.2 exclusion?
On Thu, Jan 21, 2016 at 3:21 PM, Aliza Stone<EMAIL_ADDRESS>wrote:

@ctsims https://github.com/ctsims What are "odd inclusions"?
—
Reply to this email directly or view it on GitHub
https://github.com/dimagi/commcare-odk/pull/816#issuecomment-173696909.

Oh actually.. I should probably be actually changing our app's min SDK in
this PR, and then remove the override stuff I was doing, right?
On Thu, Jan 21, 2016 at 3:38 PM, ctsims<EMAIL_ADDRESS>wrote:

The way we're injecting the new libraries, mostly (with the overwrite
stuff), but we may not need to do that anymore with the 2.2 exclusion?
On Thu, Jan 21, 2016 at 3:21 PM, Aliza Stone<EMAIL_ADDRESS>wrote:

@ctsims https://github.com/ctsims What are "odd inclusions"?
—
Reply to this email directly or view it on GitHub
<https://github.com/dimagi/commcare-odk/pull/816#issuecomment-173696909
.

—
Reply to this email directly or view it on GitHub
https://github.com/dimagi/commcare-odk/pull/816#issuecomment-173700975.


Guide refresh

Hello everyone!
I started writing this guide a few years ago because I noticed there was a lack of quality information out there about how to create Steam bots. Sure, everyone and their dog can find guides online about creating Slack bots and Discord bots in Node.js, but there wasn't any in-depth guide on how to navigate the oddities of Steam bot programming.
Over the past few years, interest and traffic to this guide has varied quite drastically, but over the past few months there seems to be a spike in demand. I've noticed this not only in this repository's insights, but also in the number of people who have contacted me about questions or job offers.
Given that Steam bots seem to once again be on the rise coming into this new decade, I've decided that it would be a good idea to do a complete refresh of this guide, from the ground up.
This guide is meant to help you, so I'd really appreciate some suggestions into what kind of things you'd like to see in this new guide. I feel like the best way of learning is by getting your hands dirty and building something, so suggestions about what to build are welcome (nothing against Steam's TOS, like gambling websites, please!)
Finally, I am incredibly grateful for everyone who has contributed to this guide over the past few years -- it would not be the same without you!
If this guide has helped you at all, please consider sponsoring me on GitHub! Writing this guide takes a lot of time and effort, so sponsoring me will help ensure that I have as much time as possible to get this new guide written. I totally understand if you don't have the funds to donate, so luckily there are other ways to help the project, like creating an issue or submitting a PR!
Best,
Andrew

Things I'd like to hear from you

Database to use? MongoDB? MySQL?
Project to do? Trading website (like BitSkins)? Selling website (like csgo.cash)?

Hello. Yes this is a great idea. I'd really like to see MySQL instead of MongoDB.

@jeanmichelmorin Thanks for the suggestion!

Also, do you think you could do videos? I think videos are way easier to follow because you can explain everything step by step as you do the code.

Interesting idea, I hadn't considered that. I might write the written guide first, and look into publishing videos after since I expect they would take a significant amount of time.

Would it be possible to go through the creation of a steam leveling website?
Also as mentioned previously, videos would help immensely!
Cheers♥

Would it be possible to go through the creation of a steam leveling website?
Also as mentioned previously, videos would help immensely!
Cheers♥

Hello, I'm really looking forward to the update, I would like to see MySQL and Selling site (like csgo.cash), can i help with it?

can i help with it*
this


kie-test-util: ComparePair updates

Depends on:
Depended on by:

https://github.com/droolsjbpm/jbpm-console-ng/pull/237

+1


Moore's Voting Algorithm in C++ to find the majority element in an array

Please include this as HACKTOBERFEST 2022 issue. I really need that t-shirt. I will be very grateful to you. Pls tag this as Hacktoberfest so it can be counted.
I have even commented every step as well in order to make it more understandable and readable.
#include<bits/stdc++.h>
using namespace std;

int moore_voting(int [], int);

int main()
{
    int n, ar[50];
    cout << "Enter the size of the array: ";
    cin >> n;
    for(int i = 0; i<n; i++)
    {
        cout << "ar[" << i << "] = ";
        cin >> ar[i];
    }
    cout << "The majority element in the array is: ";
    cout << moore_voting(ar, n);
}

int moore_voting(int arr[], int size)
{
    //Phase 1: - Finds a suitable candidate for the majority element
    int res = 0, count = 1;     //
    for(int i = 1; i<size; i++)    //Traversing the array
    {
        if(arr[res] == arr[i])   //Checking if first element is same as ith element
            count++;     //If yes then incrementing the count by 1
        else
            count--;     //Decrementing the count if ith element is not equal to first element
        if(count==0)     //If at any point the count becomes 0 while decrementing
        {
            res = i;     //Updating the ith element as result since it's not a suitable
            count = 1;   //candidate for majority. Also resetting the count of majority element
        }
    }

    //Phase 2: - Checks if the candidate selected is actually in majority or not
    count = 0;
    for(int i = 0; i<size; i++)
    {
        if(arr[res] == arr[i])

            count++;              //Line 36-44: - Checks if the candidate
    }                             //element is a majority element or not
    if(count <= size/2)
        res = -1;
    return res;
}

Hey @maheshjainckd can you explain me how to create a pull request? i cloned the repo and forked it. how to proceed from here?

Hey @maheshjainckd  my contribution status says excluded PR on hacktoberfest website. How to correct it?

Hey @maheshjainckd my contribution status says excluded PR on hacktoberfest website. How to correct it?

Sorry to inform, but this repo is excluded from hacktoberfest2022. You can contribute to any of other open source projects for Hacktoberfest.


component charts do not support variable reference

settings like this won't work in kubebb
# Default values for u4a-system.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.

# You must check and update the value of each variable below
deploymentConfig:
  # bffServer info
  bffHost: &bffHost
    portal.<IP_ADDRESS>.nip.io

https://github.com/kubebb/components/blob/main/charts/u4a-component/values.yaml#L8C13-L8C20

closed as this is not a bug.


Add support for Simple Requests to keep number of request classes low

I started using this library in an ASP.NET Core web api and I started to find that I was creating a lot of request classes with only a single property (for operations such as GetById or DeleteById) since I can't send a request of a primitive type (int, string, bool, etc). I came up with a solution that I think others may benefit from.
It involves creating a generic request class:
public class SimpleRequest<TRequest, TResponse> : IRequest<TResponse> {

    public TRequest Request { get; }

    public SimpleRequest(TRequest request) => Request = request;
}

And also an abstract request handler (based on RequestHandler):
public abstract class SimpleRequestHandler<TRequest, TResponse> : RequestHandler<SimpleRequest<TRequest, TResponse>, TResponse> {

    protected abstract TResponse Handle(TRequest request);

    protected override TResponse Handle(SimpleRequest<TRequest, TResponse> request)
        => Handle(request.Request);
}

Usage
So if I have a controller with a GetById method, I could use the simple request like this:
public class FooController : ControllerBase {

    public Task<Foo> GetById(int id)
        => _mediator.Send(new SimpleRequest<int, Foo>(id));
}

And my handler would look like this:
public class FooHandler : SimpleRequestHandler<int, Foo> {
    protected override Foo Handle(int request) {
        // code to get Foo and return it
    }
}

I'd be happy to work on adding this if you think it would be helpful to other users of the library. I also thought of adding a SimpleAsyncRequestHandler<TRequest, TResponse> in much the same way.

That's an interesting idea! I'm a little worried about adding too many helpers I don't use though - we don't have primitive requests like this, so I wouldn't know if the feature needed any changes or not.


getchar() can not detect cmd-v on MacOS

Describe the bug
getchar() can not detect cmd-v on MacOS
To Reproduce

vim
:echom getchar() == "\<D-v>"

Expected behavior
outputs 1

Only on console or also on GUI?

Only on console or also on GUI?

Both.

FYI: Terminal.app by Apple doesn't send cmd key combinations to any app you run inside.

@Yggdroot Can you put an example of what do you want to achieve?

Also FYI: GUI menu key bindings are processed on macOS level so you have to unbind a key combination from menu and then you can use it.

@Yggdroot Can you put an example of what do you want to achieve?

I wrote a fuzzy finder plugin for vim, and encounter this issue: https://github.com/Yggdroot/LeaderF/issues/428

In MacVim you can unmap Cmd-V from menu and then you can use it in GUI. iTerm2 and other terminals could send this code if you configure them this way.

This should probably be resolved in https://github.com/macvim-dev/macvim/issues/1066 since it's a specific MacVim issue. I don't think <D-v> is a thing in vanilla Vim.

closing then.


Make issue reports great again!

This adds an issue template for our GitHub issues:

Nice, maybe we can add a section for additionnal informations that might be important to know ?
Docker's issue as example has the following section:
**Additional information you deem important (e.g. issue happens only occasionally):**

Nice.
Perhaps encourage to set some labels?

Labels can only be assigned with enhanced permissions.


feat: allow to pass extra opts to vim.keymap.set()

Allow additional opts to be passed to vim.keymap.set().
Context
I want to pass { nowait = true }.
Description
Allow additional opts to be passed to vim.keymap.set().
Test Plan
Define an nmap that begins with <Esc> as follows, and pass { nowait = true } to see if the delay exists.
nnoremap <Esc><Esc> <Cmd>nohl<CR>

How about this?

Thanks for the PR!


Support indented here-docs (fix incorrect string highlighting)

I'm talking about this: http://perldoc.perl.org/perlop.html#Indented-Here-docs
Steps to Reproduce:

write perl code like that:

if ($cond) {
    my $string = <<~EOF;
        indented
        text
        will be
        indented
        just by 4 spaces
        and totally not 8
    EOF
    my $res = $self->method;
}
...

code after closing EOF will be colored as if it's still inside the string.

Currently it works only if opening here-doc marker does not have a tilde; AND closing marker is not indented (at all).
Reproduces without extensions: Yes

@mjbvz This is perl, not PHP :D

This issue was moved to textmate/perl.tmbundle#26


Not working

I think kahoot has changed their protocol again. The bots do not join the given game pin.

Yes, whenever I try to run it, it gives me the "websocket: bad handshake" error.

Same here.

Kahoot added a simple maths challenge for the computer to calculate.

Dealt with in f77408b894361af231ab0cd01ebbf8928aee5351.


PHP files dont work

I was wondering how I might be able to load PHP files because when I click them it just downloads, it doesn't open.

PHP files are not support.

@jas-chen, maybe you should learn from the package https://github.com/leijou/php-server.

@gusbemacbe, maybe you should learn go or Rails.


fix up panel display for shelving locations. Fixes FOLIO-1208

Fixes FOLIO-1208

yarn run v1.5.1
$ eslint *.js settings
/home/jenkins/workspace/folio-org/ui-organization/PR-54/project/settings/LocationLocations/LocationForm.js
9:8  warning  'TextArea' is defined but never used  no-unused-vars
/home/jenkins/workspace/folio-org/ui-organization/PR-54/project/settings/ShelvingLocationsSettings.js
24:7  error  Expected indentation of 8 space characters but found 6  react/jsx-indent
32:9  error  Expected indentation of 6 space characters but found 8  react/jsx-indent
✖ 3 problems (2 errors, 1 warning)
2 errors, 0 warnings potentially fixable with the --fix option.
info If you think this is a bug, please open a bug report with the information provided in "/home/jenkins/workspace/folio-org/ui-organization/PR-54/project/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.


Bgfx initialization allocates more memory

The initial operation of bgfx allocates about 51M of memory. Can we reduce this memory consumption? The current value of sizeof(Context) is 53862336.
		s_ctx = BX_ALIGNED_NEW(g_allocator, Context, 64);

I want to set the macro definition value in config.h to be smaller, but I don't know how big the impact will be caused. Can you give some suggestions?

You can reduce number of draw calls, size of transient buffers, etc.
You can do it via build script here:
https://github.com/bkaradzic/bgfx/blob/de35a369bac35b80a8a335ebb2d976ec787f2c72/scripts/genie.lua#L434
bgfxProject("", "StaticLib", { "BGFX_CONFIG_MAX_DRAW_CALLS=1024" })

According to our use of bgfx, we modify the code as follows, the memory is reduced from 51M to about 10M。Because we can't fully understand the usage scenarios of each parameter, if you feel any potential risks to this modification, please let us know, thank you.
change BGFX_CONFIG_MAX_DRAW_CALLS from (64<<10)-1 to (64<<2)-1

change BGFX_CONFIG_MAX_BLIT_ITEMS from 1<<10 to 1<<8

change BGFX_CONFIG_MAX_RECT_CACHE from 4<<10 to 4<<7

change BGFX_CONFIG_SORT_KEY_NUM_BITS_DEPTH from 32 to 16

change BGFX_CONFIG_SORT_KEY_NUM_BITS_SEQ from 20 to 10

change BGFX_CONFIG_MAX_VIEW_NAME from 256 to 64

change BGFX_CONFIG_MAX_VERTEX_DECLS from 64 to 32

change BGFX_CONFIG_MAX_INDEX_BUFFERS from 4<<10 to 4<<7 = 512

change BGFX_CONFIG_MAX_DYNAMIC_INDEX_BUFFERS from 4<<10 to 4<<5 = 128

change BGFX_CONFIG_MAX_DYNAMIC_VERTEX_BUFFERS from 4<<10 to 4<<5 = 128

change BGFX_CONFIG_DYNAMIC_INDEX_BUFFER_SIZE from 1<<20 to 1<<7 = 128

change BGFX_CONFIG_DYNAMIC_VERTEX_BUFFER_SIZE from 3<<20 to 3<<6 = 192

change BGFX_CONFIG_MAX_TEXTURES from 4<<10 to 4<<7 = 512

change BGFX_CONFIG_MAX_FRAME_BUFFERS from 128 to 64

change BGFX_CONFIG_MAX_OCCLUSION_QUERIES from 256 to 32

change BGFX_CONFIG_MAX_COMMAND_BUFFER_SIZE from 64<<10 to 64<<7

change BGFX_CONFIG_TRANSIENT_VERTEX_BUFFER_SIZE from 6<<20 to 6<<10

change BGFX_CONFIG_TRANSIENT_INDEX_BUFFER_SIZE from 2<<20 to 2<<10

change BGFX_CONFIG_TRANSIENT_INDEX_BUFFER_SIZE from 8 to 4

My suggestion is to not change shift values. This <<10 means 1KiB. Change number in front of it, or just write number.

Some of values you're changing are not affecting memory usage... For example BGFX_CONFIG_SORT_KEY_*

@bkaradzic  thanks for your help。 I will check it again.


Use local nuget over PATH based nuget

It seems like if someone has a nuget.exe from the v2 erra, that when installing cake the destination folder is incorrect, it includes the Version in the folder name.
We don't see this on CI because the CI server doesn't come with nuget.exe by default, and locally I'm sure I don't have any V2 nuget.exe in my path.
fixes #484
cc @troydai @danroth27

Looks good. Sorry for missing it in the script when I pulled it in. The UNIX script works this way already and it makes sense.


devcontainer: adapt to composer

Make the devcontainer more complete for osbuild-composer by
installing more dependencies and plugins.
This enables golang and github integration by default.
Also add a basic (off by default) pre-commit hook to enforce some sanity checks on our code before it is committed.

I dropped the pre-commit hooks as that was giving me more problems than it was solving.


Dark mode for desktop

See #60.

Only seem to face the issue with the flatpak.
With built from sources on my Linux Mint 22 Cinnamon Framework 13:

What about dark tiles?

Related to Benjamin_Loison/app.organicmaps.desktop/issues/2.


fix(Travis): after_success has to be used with explicit failure mechanism

Codecov Report

Merging #6 (d83fe59) into main (b6cd3ab) will decrease coverage by 0.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
- Coverage   90.85%   90.69%   -0.17%
==========================================
  Files           5        5
  Lines        3596     3534      -62
==========================================
- Hits         3267     3205      -62
  Misses        329      329

Impacted Files
Coverage Δ

ibm_scc/configuration_governance_v1.py
89.35% <0.00%> (-0.19%)
:arrow_down:

ibm_scc/findings_v1.py
90.95% <0.00%> (-0.15%)
:arrow_down:

ibm_scc/notifications_v1.py
92.98% <0.00%> (-0.14%)
: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 b6cd3ab...d83fe59. Read the comment docs.


Adding powercasting for a module built on dnd5e

I have a module that is built on dnd5e system and it has the ability to cast "tech" powers. Similar to way Starfinder works. The problem is that "spells" don't show up in the cast spell tab because they are not "prepared"  they are set at powercasting.
Is there a way to tweak this behavior to support showing "powers" that are not prepared and don't take a spell slot?

Hello! It seems you haven't read the Before Posting an issue as indicated at the top of the Repository Readme The Issue has been closed.
If you are reporting a bug, feel free to follow the steps here (https://theripper93.com/info/issues) and reopen the issue with all the relevant information.


Replace Account interface default arguments

Describe your changes

This PR replaces default arguments in Account interface with polymorphic methods. Default arguments don't translate nicely to java.
Linked issues

Closes
Breaking changes

[x] This issue contains breaking changes

Changes in Account interface

Codecov Report
Base: 70.31% // Head: 70.22% // Decreases project coverage by -0.09% :warning:

Coverage data is based on head (0c55301) compared to base (7570023).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@                    Coverage Diff                    @@
##           feat/account-typedata     #238      +/-   ##
=========================================================
- Coverage                  70.31%   70.22%   -0.09%
=========================================================
  Files                         60       60
  Lines                       1792     1790       -2
  Branches                     136      136
=========================================================
- Hits                        1260     1257       -3
- Misses                       490      493       +3
+ Partials                      42       40       -2

Impacted Files
Coverage Δ

...n/kotlin/com/swmansion/starknet/account/Account.kt
88.88% <100.00%> (-11.12%)
:arrow_down:

...in/kotlin/com/swmansion/starknet/data/TypedData.kt
93.33% <0.00%> (-0.09%)
:arrow_down:

...tlin/com/swmansion/starknet/crypto/NativeLoader.kt
29.03% <0.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


refactor(getCookie): get the value directly

What does this change?
Refactor the map check in getCookie to always get, instead of checking has before.
Why?
Currently, we don’t have 100% coverage because of a TS limitation.
There’s safety built-in the get method, so let’s use it directly.
We could alternatively use a //@ts-expect-error or an as string type assertion.

Coverage increased (+0.2%) to 100.0% when pulling c69327bedbeb702f005297129c75c1514daa9a90 on mxdvl/coverage-100-percent into feb83462c364dc60d8bfe2b5f81d5e20fcebd089 on main.

Duplicate of #335