Possible missing constant: Wx::FileSelectorPromptStr

Following the documentation (https://mcorino.github.io/wxRuby3/Wx/FilePickerCtrl.html) for the default message parameter, I tried creating the following:
    @filePicker = Wx::FilePickerCtrl.new(static_box_2.get_static_box, Wx::ID_ANY, (''),
      Wx::FileSelectorPromptStr, 'BMP files|*.bmp', Wx::DEFAULT_POSITION,
      Wx::DEFAULT_SIZE, Wx::FLP_USE_TEXTCTRL|Wx::FLP_OPEN|Wx::FLP_FILE_MUST_EXIST)

I then get:
global_const.rb:50:in `const_missing': uninitialized constant Wx::FileSelectorPromptStr (NameError)

I did try the uppercase snake-case version of the constant (Wx::FILE_SELECTOR_PROPT_STR), but that didn't work either.

The problem with constants like this one is that they are referenced in the documentation (as argument defaults) but not documented themselves. It is therefor not possible for the build scripts to generate wrapping code for them.
Manually wrapping would require trawling through the documentation looking for these and than checking the wxWidgets C++ code to find out what value the constant has.
That is not something I ever intend to do structurally.
The argument default as documented will still work (because that's coded in C++) but directly referencing them will cause errors like this.
Fixing them when found is not that difficult by just adding a constant definition in pure Ruby in an appropriate file in the Ruby code part of the wxRuby library.
I will pick this one up still and add a patch to the library but for future issues like this I will suggest users themselves submit PR's with the appropriate patch.

BTW, this report did point out to me that constant naming was not fully consistent in wxRuby (particularly concerning these "referenced but not officially documented" constants).
Thanks for that.
I fixed that now and added Wx::FILE_SELECTOR_PROMPT_STR to the library.
For future reference: any missing constants like this should be added to lib/wx/core/const.rb with an additional entry in lib/wx/doc/const.rb to enable documentation crossreferences (unlike in wxWidgets docs).


unable to create variables template

Describe the bug
when I tried to create a template it is never successful
To Reproduce
Steps to reproduce the behavior:
URL: http://<IP_ADDRESS>:8003/servers/templates/new/

Go to templates
Give name, category and Description
Add parameters
Click on create template
it does not show any error but the template its not saved

Expected behavior
We should have a new template saved
Screenshots

@abdelmaster @ulibn

@gerardvl could you share with us the way you start the docker image.
@fquinteroa is it possible that the behavior might be related with the way they start the docker image?

@abdelmaster
-I took the installer of here https://docs.docker.com/docker-for-windows/install/
-following the steps posted on bluexolo_useres channel by Fernando
-Running this command on CMD window---->docker run --privileged -ti -p 8000:8000 -e container=docker -v /sys/fs/cgroup:/sys/fs/cgroup -v /opt/bluexolo-data:/var/lib/pgsql \ bluexolo/bluexolo


MH-12703: Add userdirectory for Moodle

This PR adds a Moodle user and role provider analogous to the Sakai user and role provider. To efficiently query the necessary information, the moodle-tool_opencast plug-in has to be installed in Moodle. ~There is still a minor convenience feature that has to be implemented on Moodle site, which effects the documentation included in this PR. This work is therefore WIP, but I figured that at least the code can be reviewed. Function wise this integration should work.~

This is now ready for a review.

Any change we might find a reviewer until 22.3 😬? Otherwise I won't be able to work on this until the 5.x feature freeze (but no pressure, if it can't be done for 5.x there is 6.x 🙂).

At a glance, the code looks good to me. It would be ideal to find a reviewer who also uses moodle and can test it in production. But if no-one else volunteers, I'd be prepared to merge it in time for 5.x, as there's no reason it should wait until 6.x and it only really affects people who switch it on, so it's low-risk for everyone else.

I have adapted the PR according to your comments.

@wsmirnow is this good to go or do I need to work on it some more?

As there are minor requested changes (documentation of an exception) I suggest to merge this PR and create a patch afterwords. So the feature will be available in 5.x.


Nuke: OCIO env var workflow

Changelog Description
The OCIO environment variable needs to be consistently handled across all platforms. Nuke resolves the custom OCIO config path differently depending on the platform, so we included the ocio config path in the workfile with a partial replacement using an environment variable. Additionally, for Windows sessions, we replaced backward slashes with a TCL expression.
Testing notes:

activate Colorspace management and add config path with root token
open Nuke in the project and see the custom ocio config path was set to some strange values

In my case I was setting the path within {root[resources]}/...

If you want to make a new drive letter from some folder in case you want to test multi root - here it how to do it.
subs X: C:\path\to\folder
submit publish deadline farm job
make sure your last version .zip package is created and Deadline can see it.
all should be rendered as expected

Dependencies:
https://github.com/ynput/OpenPype/pull/5387
https://github.com/ynput/OpenPype/pull/5411

Apply settings do not work for some reason. Deadline crashes with error:
   at Deadline.Plugins.DeadlinePlugin.FailRender(String message) (Python.Runtime.PythonException)
  File "C:\ProgramData\Thinkbox\Deadline10\workers\qamtop\plugins\64cb841b5001a6ac7cdf94ef\Nuke.py", line 264, in RenderTasks
    self.WritePython(scriptContents)
  File "C:\ProgramData\Thinkbox\Deadline10\workers\qamtop\plugins\64cb841b5001a6ac7cdf94ef\Nuke.py", line 41, in WritePython
    self.WaitForProcess()
  File "C:\ProgramData\Thinkbox\Deadline10\workers\qamtop\plugins\64cb841b5001a6ac7cdf94ef\Nuke.py", line 48, in WaitForProcess
    self.FlushMonitoredManagedProcessStdout( self.ProcessName )
  File "C:\ProgramData\Thinkbox\Deadline10\workers\qamtop\plugins\64cb841b5001a6ac7cdf94ef\Nuke.py", line 623, in HandleError
    self.deadlinePlugin.FailRender( self.GetRegexMatch( 0 ) )
   at Python.Runtime.Dispatcher.Dispatch(ArrayList args)
   at __FranticX_GenericDelegate0Dispatcher.Invoke()
   at Deadline.Plugins.DeadlinePlugin.RenderTasks()
   at Deadline.Plugins.DeadlinePlugin.DoRenderTasks()
   at Deadline.Plugins.PluginWrapper.RenderTasks(Task task, String& outMessage, AbortLevel& abortLevel)
   at Deadline.Plugins.PluginWrapper.RenderTasks(Task task, String& outMessage, AbortLevel& abortLevel)

This PR https://github.com/ynput/OpenPype/pull/5411 would be good to include so the environment variable workflow is working as it should.


configuration for adding dynamic api-key(access token value).

I need to provide a access token on the swagger-ui page  so that all the request can be authenticated.
I have implemented the following.

@Bean
SecurityConfiguration security() {
return new SecurityConfiguration(null, null, null, "Spring Boot Swagger", "baedeb03-5142-466e-8d8f-c0987a8078f8", ApiKeyVehicle.HEADER, "X-AUTH-TOKEN",",");
}

Above: I have fixed the value of X-AUTH-TOKEN value, I want this to be added with swagger ui, whenever user testing the api.
Any suggestion would be of great help.

It should work, Is it not working? what version of springfox are you using?

This is working , you see I have hardcoded the value of "X-AUTH-TOKEN: baedeb03-5142-466e-8d8f-c0987a8078f", I want this value to be entered by tester like from swagger-ui,
btw I am using 2.7.0 for both.

We'll have that when we do the 3.x swagger-ui migration.

any expected date for availability of 3.x swagger-ui.

None yet. Looking for contributions.


Update symmetric key API documentation

This is a companion PR for #630, updating existing symmetric key API documentation, code examples, and tests to correctly use symmetric keys, not passphrases. Various bits of documentation are also updated and unified.
On the one hand, this is a lot of API documentation, much more extensive than any other wrapper has.  Plus, it's kinda dishonest to lower the quality bar.
Checklist

[X] Change is covered by automated tests
[X] The coding guidelines are followed
[X] Public API has proper documentation
[X] Example projects and code samples are up-to-date
[X] Changelog is updated (nothing notable)

@karenswry, I know that you're working on something in RustThemis docs too. I don't see any conflicts with your branch right now, but this is a heads up about some changed files that might cause conflicts later. Please consider syncing with master once this PR is merged.


[WIP] Add root DNS records for app services

Add .integration.govuk-internal.digital CNAMES to blue stack for
app records.

Can we go through this later? From my reading of it, if we deploy a project on a specific stack, it's going to update the top level domain (.integration.govuk.digital) to point to the thing that's just been deployed. Am I understanding this correctly, and if so, do we want it as part of the project or an independent thing?
I am also worried you asked me this question yesterday and I said the wrong thing from my limited understanding 😕


3616 - Change names to conform to the new naming conventions

3616 - Change names to conform to the new naming conventions
📲 What
Consistent naming within templates.
🤔 Why
This is to conform to naming standards of all the templates.
See this ADR: https://amidodevelopment.atlassian.net/wiki/spaces/TEC/pages/3398598736/ADR+.Net+-+Templates+naming+convention
🛠 How
Changes to templates files.
👀 Evidence
Screenshots / external resources / links / etc.
Link to documentation updated with changes impacted in the PR
🕵 How to test
Notes for QA
✅ Acceptance criteria Checklist
Code peer reviewed?
Documentation has been updated to reflect the changes?
Passing all automated tests, including a successful deployment?
Passing any exploratory testing?
Rebased/merged with latest changes from development and re-tested?
Meeting the Coding Standards?

/azp run


Investigate Dependabot high and critical severity alerts in mobile-ui-react

I was able to fix all the Dependabot alerts in this project.


Refactor error 1200

Addresses issue #1200
Custom error function changed in Errors factory.
No changes required for ERMrestjs.

Comments were added.


[WIP] Make idempotent zone updates

Refresh nsupdates facts for dns node to fix obsoleted secrets
used for nsupdates tasks issued against localhost (control node)
Purge zone journal files if zone db files has been changed by
the dns-server role applied.

Closes https://github.com/openshift/openshift-ansible-contrib/issues/494
Signed-off-by: Bogdan Dobrelya<EMAIL_ADDRESS>

@tomassedovic @oybed PTAL (I'm aware now of https://github.com/redhat-cop/infra-ansible/pull/24 but this still has to be fixed for the contrib repo anyway)

@bogdando it will be a nightmare to maintain the same roles in more than one place, so really don't want these changes to go in (especially since I gave a heads-up at time of initial merge that these roles will be moved out of contrib)

@oybed agree. We will rework the roles to be consumed as external modules from your repos perhaps

Also "purging journal files" is very risky in general as records may get lost. The better approach is to freeze the journal files before a change and "thaw" them afterwards. The change made in infra-ansible, however, is to avoid changes at all - i.e.: if a key already exists, don't touch it. (we may want to introduce a flag in the future to "refresh" keys when/if needed but that's a TBD)

Superseded by https://github.com/openshift/openshift-ansible-contrib/pull/529


Add iface based lookup.

Provide --iface eth0 as an alternate to using the Amazon Metadata Service to find the ip address.

@mfowlewebs  I like the overall idea of your PR. But JShint has some findings. Can you locally run
make test
and fix the errors that are found?

Thanks for the speedy reply; changed. Great app, many thanks.

And I threw in a blurb in the README too.

Thanks! Released as<EMAIL_ADDRESS>


[WIP] eclipse-platform, eclipse-sdk: 4.8 -> 4.9

Motivation for this change
To bump eclipse-platform and eclipse-sdk to the latest version. Also removes the oldest versions of these packages.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Fits CONTRIBUTING.md.

@grahamcofborg build list eclipses.eclipse-platform eclipses.eclipse-sdk eclipses.plugins.jdt

Success on aarch64-linux (full log)
Attempted: eclipses.plugins.jdt
The following builds were skipped because they don't evaluate on aarch64-linux: list, eclipses.eclipse-platform, eclipses.eclipse-sdk
Partial log (click to expand)
'org.junit.platform.suite.api_1.1.0.v20180327-1502.jar' -> '/nix/store/ixypi9cvm2n0xa043faklgmbsgbvapap-eclipse-plugin-jdt-4.9/eclipse/dropins/jdt-4.9/plugins/org.junit.platform.suite.api_1.1.0.v20180327-1502.jar'
'org.junit.vintage.engine_5.1.0.v20180327-1502.jar' -> '/nix/store/ixypi9cvm2n0xa043faklgmbsgbvapap-eclipse-plugin-jdt-4.9/eclipse/dropins/jdt-4.9/plugins/org.junit.vintage.engine_5.1.0.v20180327-1502.jar'
'org.junit_4.12.0.v201504281640.jar' -> '/nix/store/ixypi9cvm2n0xa043faklgmbsgbvapap-eclipse-plugin-jdt-4.9/eclipse/dropins/jdt-4.9/plugins/org.junit_4.12.0.v201504281640.jar'
'org.opentest4j_1.0.0.v20180327-1502.jar' -> '/nix/store/ixypi9cvm2n0xa043faklgmbsgbvapap-eclipse-plugin-jdt-4.9/eclipse/dropins/jdt-4.9/plugins/org.opentest4j_1.0.0.v20180327-1502.jar'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/ixypi9cvm2n0xa043faklgmbsgbvapap-eclipse-plugin-jdt-4.9
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/ixypi9cvm2n0xa043faklgmbsgbvapap-eclipse-plugin-jdt-4.9
checking for references to /build in /nix/store/ixypi9cvm2n0xa043faklgmbsgbvapap-eclipse-plugin-jdt-4.9...
/nix/store/ixypi9cvm2n0xa043faklgmbsgbvapap-eclipse-plugin-jdt-4.9

Success on x86_64-linux (full log)
Attempted: eclipses.eclipse-platform, eclipses.eclipse-sdk, eclipses.plugins.jdt
The following builds were skipped because they don't evaluate on x86_64-linux: list
Partial log (click to expand)
eclipse/plugins/org.eclipse.ui.intro.universal_3.3.300.v20180821-0700.jar
eclipse/plugins/org.hamcrest.core.source_1.3.0.v20180420-1519.jar
eclipse/plugins/org.eclipse.jdt.doc.isv_3.14.100.v20180905-0558.jar
eclipse/plugins/org.apache.commons.jxpath.source_1.3.0.v200911051830.jar
eclipse/plugins/org.eclipse.equinox.launcher_1.5.100.v20180827-1352.jar
eclipse/plugins/org.eclipse.equinox.p2.metadata.repository_1.3.100.v20180822-1302.jar
eclipse/eclipse.ini
eclipse/dropins/
eclipse/readme/
eclipse/readme/readme_eclipse.html


Automatically close stale PRs?

There is a GitHub Action that would allow us to close PRs that have been open too long:

https://github.com/actions/stale

I notice the MOOSE team using it. Their plan, which I propose to emulate, is to warn people their PR is getting stale after 100 days, and then 7 days later close the PR.

@opotowsky @albeanth Thoughts?

Makes sense to me.
I wonder if something similar could be done for issues. Maybe not close, but ping the originator and/or you, John. See if it's still relevant or not.

Makes sense to me.

Cool!

I wonder if something similar could be done for issues...

Yup, I could do that. Some tickets are backlogged not because they are stale and should be closed but because they just lost the "cost-benefit" analysis for a couple releases. So I don't think closing them is exactly right.  Food for thought though, yeah.

YES FOR ISSUES! I make them then forget about them
Fine for PRs too.

YES FOR ISSUES! I make them then forget about them

Just to be clear, not close, but ping. Yeah?

Yes, pings are useful. Closing probably a bit too heavy handed


Change setting.binary depending on a job tag

@ivansenic I am still not able to log in to the staging PC and test it, but it works fine on mine macos


Logistic Regression

Define You:

[x] DevIncept Participant
[x] Contributor

Is your feature request related to a problem? Please describe.

I want to contribute Logistic Regression Algorithm using this dataset by following the given project structure.

Describe the solution you'd like...

I'll proceed by following steps:
Step 1: Data preprocessing and exploration.
Step 2: Data visualization to draw useful insights.
Step 3: Data training & model creation.
Step 4: Performance evaluation to check efficiency of the algorithm by error & accuracy check.

@prathimacode-hub, please assign it to me.

Issue assigned. @ayushi424


Dscheck integration breaks utop

Current integration of dscheck breaks utop (link), and there does not seem to be a simple way to reconcile the two (per limitations). Is there a different way to achieve the same separation (i.e. no dscheck shadowing in production code) without losing utop?

A ppx that will select implementation of Atomic.* depending on environment flag
A different way to do the shadowing? (cc @lyrm)

Can we make dscheck a with-test dependency? One need not install dscheck when installing lockfree then.

We chatted during the multicore meeting:

Using with-test dependency sounds good to resolve the issue above. Nonetheless, it turns out the current integration also causes problems with OCaml 4 compatiblity (https://github.com/ocaml-multicore/lockfree/pull/37#issuecomment-1351369115), and there was some other idea proposed to try out there (https://github.com/ocaml-multicore/lockfree/pull/37#issuecomment-1351687468), so we might want to coordinate here to find one hack to kill both birds.

Another, possibly the simplest solution, would be to just use a dune rule to copy dscheck's atomic in testing.

Just to clarify, I have e.g.

lib/mod.ml : uses Atomic
test/dune : (copy ../lib/mod.ml mod.ml)
test/atomic.ml  : include Dscheck.TracedAtomic

So mod.ml is compiled with the regular Atomic module in lib, and with TracedAtomic in test.

Solved by #53.


do not use unkeyed fields in compose literals

splitting this off from https://github.com/containerd/containerd/pull/3116

LGTM

LGTM


org.apache.rocketmq:schema-registry-client non-existent

org.apache.rocketmq:schema-registry-client non-existent

ｍｅ　ｔｏｏ

org.apache.rocketmq:schema-registry-client non-existent

The official version will be released in the near future


Larger grid/font when printing

Proposing to add Print link (next to "Tools") that leads to 4 ways of printing/PDFing: 2-column (default), 3-column, 4-column, 1-column.
In the 3-column and 4-column modes, the grid would occupy 2 columns, making it bigger than the current size in printouts. There will probably also be an option to make the printed font-size bigger (I need to try things out a bit first though).
FWIW, I think the 2-column version is nice for printing puzzles with solutions and clue annotations (as they fill up a single page typically).
This was originally raised by @billykenny in a different discussion:

... if I right click and select Print to PDF (I'm using Windows 10 Pro and MS Edge, and not changing any settings) from the Exolve puzzle, the resulting printout occupies just about half the page, the font is quite small, as is the grid.
Acrosslite produces a larger, more user friendly output (in terms of writing in answers, although it doesn't look as elegant).

I admire your dedication and look forward to seeing the proposal implemented. Personally, I think the Financial Times PDF is the ideal, bearing in mind that many cryptic crossword lovers are older generation with poorer eyesight. The lights don't feel cramped when entering letters, and the font is big enough to read comfortably.
This is an example
Thank you for all your good work

I've implemented a better layout for incomplete grids now, with v1.21.
I decided not to create complicated printing options. Instead, I just changed the default behaviour (but have given the puzzle setter some options to override). Details copied below from CHANGELOG.md:
Version: Exolve v1.21 September 20 2021

Add a new, 3-column layout for printing (and creating PDFs). This is
now the default layout when printing while there are any unfilled
cells. This layout makes the grid larger (as it spans 2 of the 3 columns)
and is easier to write into. This is implemented using code to figure
out where to split the clues lists for balancing across three columns (as
CSS does not handle this kind of columnar layout where an element spans
multiple but not all columns).
The 2-column layout (with the grid placed in the first column) continues
to be the default for printing completed grids. This choice works well
especially when there are annotations/explanations revealed, as it is
more likely to get everything to fit within a single page.
Add exolve-options print-incomplete-2cols and print-completed-3cols
to override the above defaults if needed.
Unhighlight the current clue/cells before printing (and restore after
printing).
If there are span-specified ninas, make their colour appear in printing
too (this was a minor bug) by adding a CSS rule for .xlv-clue to render
the colour properly within that class when printing.

The new print layout looks funky on my puzzle (the one I shared with you) - 1) the grid overlaps the third column, 2) the numbering pushes down to the next page, and 3) there's an unusual extra space after one of the clues (36D).

That works fine on my puzzle and looks so much better - many thanks? Is it possible for me to change the fontsize for the clues in the print/PDF?

Just relaised you're already working on the fontsize - thanks!

I'll continue to tweak, keeping this open for now.
Will try to fix the bad rendering on Windows+Chrome and Firefox (seems bad across platforms). Will try to provide a larger font-size option; but unlike layout, which I think can be the setter's choice, I think a markedly larger font size has to be deliberately chosen by the solver. So I'll probably add a "Print" button next to "Tools" after all, which will lead to a panel where printing choices can be made. The defaults will continue to be what they are.
Printing is messy :-)

Yeah, some of the options look better if you change the scaling in the print dialog.

I've posted v1.22 that brings some more improvements to printing. I'm copying the CHANGELOG.md entry as well as the updated printing documentation from README.md below:
Version: Exolve v1.22 September 28 2021

Printing tweaks and bug-fixes. Do 2-columns manually like 3-columns.
Measure and fit more carefully. Avoid clipping at the bottom by
inserting special, measured DIVs at the bottom of the first page,
in each clues column.
Add a "Print" link. Give controls for page size, margin, font size.
Allow printing just the crossword (useful when the crossword is
buried in some section of the whole page).
Lots of nuances to this change, see the details in the updated
documentation.

--------------------- README.md: -----------------------------------------------------
Printing
You can print web pages containing Exolve crosswords using the browser's "Print"
command (Ctrl-P or Cmd-P) or by using the "Print" link shown under the grid
(this latter way of printing opens up a panel that provides some additional
settings: see below). The current state of the crossword gets printed. If you
want to print the blank grid after you've already filled some entries, or if
you want to print the "fully revealed" grid (if available), then you can
re-open the crossword in an incognito window, get it to the state you desire to
print, and then print.
The printed puzzle is laid out in a newspaper-like multi-column layout (similar
to what you get with the columnar-layout option). You can create PDF files for
your crosswords by "printing to file" in most browsers.
If not all the puzzle entries have been filled in, then the printing is done in
three columns, with the grid occupying two columns. This makes the grid a bit
larger and easier for writing into.
If all the puzzle entries have been filled in, then the printing is done in
two columns, with the grid occupying the first column (which makes it slightly
smaller than the three-column layout for incomplete puzzles). If the puzzle
provides annotations and/or explanations that get revealed, then this two-column
layout is especially useful to limit the printed size.
For most puzzles, this layout should fit within a single page, in Portrait mode,
for standard page sizes. You can reduce the printing scale manually (in the
browser's print settings) if it just goes over a single page by a few lines.
You can override the column choices for completed (default: 2 columns) and
incomplete (default: 3 columns) puzzles using the options
print-completed-3cols and print-incomplete-2cols respectively.
Before printing, any highlighting of the currently active clue is removed,
and it is restored after printing.
If it does not make sense for some chunks of text or some HTML elements to be
printed (for example, some instructions that only make sense in interactive
mode), you can enclose them in an HTML element (such as a DIV or a SPAN)
that has the class xlv-dont-print.
Additional settings for printing
Clicking on the "Print" link (that's shown under the grid) toggles a panel
with the title "Settings for printing/PDFs". This lets you specify:

Page size (such as 'Letter' or 'A4'). As of September 2021, you still need to
pick the same page size in the printer's settings that open up when you
print, if you use a paper size that's not the current choice in the printer's
settings.
Page margin in inches. Caveat: large margins may lead to some parts getting
clipped.
Font size (Normal, Large, Extra Large, Small).

Additionally, from this panel, you have two buttons for printing:

You can click on a button labelled "Print page". This will print the whole
page, just like what you'll get from the browser's "print" function.
You can click on a button labelled "Print crossword". This will print only
the crossword. This is useful if the crossword is embedded with some
background or other content around it.

Printing layout algorithm details
In preparation for printing, Exolve lays out the crossword part of the page
(which is usually the whole page) using a width of 992 pixels (488 + 16 in
2-columns format, and 320 + 16 + 320 + 16 + 320 in 3-column format) with 0
margin. It then balances the clues across the 3 or 2 columns, so that the
bottom edge is even.
This is followed by an attempt at pagination (only done if the top-left of the
Exolve crossword is very near the top-left of the page). The aspect ratio of
the page size specified (taking into account the margins) is used to find where
the page boundary is (in pixels). If the content already fits in one page, then
nothing further needs to be done. If the content seems to only slighlty spill
over to a second page, then a small left margin is added, sufficient to make the
aspect ratio fit. If there's a non-trivial spill onto a second page, then
Exolve inserts empty helper divs (with heights set as needed) to try to ensure
that no clue is cut midway at the bottom of the first page and that the the
remaining clues line up at the top on the second page. The hope is that browser
will simply scale the content correctly and will arrive at the same page
boundary.
After printing, Exolve reverts the page rendering to its original state.
Browser-specific printing peculiarities
Brwosers have their own printing layout algorithms that sometimes do not behave
as expected by Exolve's printing layout algorithm. Here are some known issues as
of September, 2021.

Printing settings in Firefox seem especially complex, and Exolve turns off
the pagination attempts described above if it detects the browser to be
Firefox. If the printed area seems too small with Firefox, try unchecking the
option: "Ignore Scaling and Shrink to Fit Page Width" and set the scale to
something like 70%.
In Chrome, if the margin is too high (say, more than 0.7 inches), then some
content may get clipped.

I'm closing this issue. Feel free to create new bugs for any specific printing issues you might observe. Thanks!


Fix DEDUP signature so that it reduces list nesting

When DEDUP is used with an aggregator or a macro (new in 2.7.0), it always generates a list of GTSs for each GTS. This is because this function is very similar to MAP so aggregators/macros can generate several GTSs. However, in the case the aggregator/macro returns a single GTS, MAP does not nest lists for simplicity.
This PR aims at replicating this behavior in DEDUP, avoiding list nesting when possible.
This does change the signature of DEDUP, however as this functionality is rather new and is already documented as avoiding nesting, this change may be considered as acceptable.
Signatures without this PR:
GTS AGGREGATOR/MACRO DEDUP LIST<GTS>
LIST<GTS> AGGREGATOR/MACRO DEDUP LIST<LIST<GTS>>
Signatures with this PR:
For an aggregator/macro generating a single GTS (most common case):
GTS AGGREGATOR/MACRO DEDUP GTS
LIST<GTS> AGGREGATOR/MACRO DEDUP LIST<GTS>
For an aggregator/macro generating multiple GTSs:
GTS AGGREGATOR/MACRO DEDUP LIST<GTS>
LIST<GTS> AGGREGATOR/MACRO DEDUP LIST<LIST<GTS>>

The documentation for DEDUP could go more into the details of what the aggregator/mapper can output and what effect it would have on the final result, especially on the number of GTS.

The documentation for DEDUP could go more into the details of what the aggregator/mapper can output and what effect it would have on the final result, especially on the number of GTS.

I agree, but I wouldn't change the doc without knowing first if the change introduced by this PR is deemed acceptable or not.

I agree, but I wouldn't change the doc without knowing first if the change introduced by this PR is deemed acceptable or not.

While removing the nesting when all inner lists have a single value is indeed a good idea, having DEDUP output a GTS instead of a LIST does not seem wise since it will force the calling code to perform a test to check if the result is a list or not prior to extracting the resulting GTS. So I would rather see the following new signatures

While removing the nesting when all inner lists have a single value is indeed a good idea, having DEDUP output a GTS instead of a LIST does not seem wise since it will force the calling code to perform a test to check if the result is a list or not prior to extracting the resulting GTS. So I would rather see the following new signatures

I understand you want to use the same rule as MAP but I think it could confuse users because GTS DEDUP will leave a single GTS but GTS AGGREGATOR/MACRO DEDUP will leave a LIST.
If your code has to test whether the result is a list or not would mean you don't know if the parameters are LIST<GTS> or simply GTS or if your mapper/macro generates a single GTS of several LIST<GTS>. I'm not sure the former often happens, correct me if I'm wrong, and for the latter you will also have to check if it's a LIST<GTS> or LIST<LIST<GTS>> or do a potentially useless FLATTEN.

I understand you want to use the same rule as MAP but I think it could confuse users because GTS DEDUP will leave a single GTS but GTS AGGREGATOR/MACRO DEDUP will leave a LIST.
If your code has to test whether the result is a list or not would mean you don't know if the parameters are LIST<GTS> or simply GTS or if your mapper/macro generates a single GTS of several LIST<GTS>. I'm not sure the former often happens, correct me if I'm wrong, and for the latter you will also have to check if it's a LIST<GTS> or LIST<LIST<GTS>> or do a potentially useless FLATTEN.

If you are the one providing the aggregator/macro then it is reasonable to assume you know what you are doing, but if you are writing a macro which accepts as a parameter an aggregator then you might not know.

If you are the one providing the aggregator/macro then it is reasonable to assume you know what you are doing, but if you are writing a macro which accepts as a parameter an aggregator then you might not know.

A useless FLATTEN on a LIST with no nesting works, but a FLATTEN on a GTS fails, hence my suggestion to always return a LIST

A useless FLATTEN on a LIST with no nesting works, but a FLATTEN on a GTS fails, hence my suggestion to always return a LIST

I feel like we complicating things for most of the cases for a rare case which can be solved by [ SWAP ] FLATTEN.
Also you may want a different logic if your mapper return several GTSs, which is a case you may not be able to detect with your suggestion.

I feel like we complicating things for most of the cases for a rare case which can be solved by [ SWAP ] FLATTEN.
Also you may want a different logic if your mapper return several GTSs, which is a case you may not be able to detect with your suggestion.


chore: mergeback release to development

Mergeback release versions to development

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

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

Totals

Change from base Build<PHONE_NUMBER>9:
0.0%

Covered Lines:
784

Relevant Lines:
961

💛  - Coveralls


Add ItemSlotArgumentParser

Resolve #55

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[FEATURE REQUEST/QUESTION] Customizable Sound Effects for PvP-enabled

[FEATURE REQUEST/QUESTION] Customizable Sound Effects for PvP-enabled
Discription: It seems that there is currently no title, subtitle, or sound effect associated with the PvP-enabled state. Can you confirm if this is indeed the case? If so, would it be possible to add a title, subtitle and matching sound effect to this event?
Like ‘Lava’ and ‘Deathmatch,’ it would be a valuable addition to have a title, subtitle and sound effect for when PvP is enabled. See also: #15

Currently, there is no visual effect when PVP is enabled, however, I will include this in the next release.

Thanks for implementing my suggestion. I look forward to seeing this feature soon in the next release.

Thank you for the suggestion! This feature will be included in the upcoming v2.0.4 release.
Commit: fee53d89919eb89205b3e21b1e6de2f4fd3143ad


java.lang.IllegalStateException: This YouTubePlayerView has already been initialized.

this happens when using YouTubePlayerView in a recyclerView . any support please ?

Hi, each view holder needs to have it's own YouTubePlayerView.


Update misc.lua

https://mods.factorio.com/mod/SeaBlock/discussion/60cdc56f894b788ddcd9d5c3

Tech tree cycle has already been fixed, thanks!


Make obsidian omnipotent in daily management - Full functionalities similar to ticktick and toggl track

Goal or desired outcome of this feature
implement all functionalities in
ticktick https://help.ticktick.com/articles/7054286604315131904
toggl track https://toggl.com/track/
Describe the feature
implement all functionalities in
ticktick https://help.ticktick.com/articles/7054286604315131904
toggl track https://toggl.com/track/
Enhance Obsidian to be an all-encompassing solution for daily management, incorporating a comprehensive set of features akin to both TickTick and Toggl Track. This includes integrating a daily timer, Pomodoro technique, Eisenhower Matrix (4-quadrant time management system), habit tracker, task archiving, and the ability to create events seamlessly under the daily folder (Daily notes folder/folder named with the current date/Events).
Screenshots, mockups, or videos

https://forum.obsidian.md/t/make-obsidian-omnipotent-for-daily-management/72112


add placeholder fields to appconfig

Add various placeholder fields to AppConfig
This way we can add plugins/app for list and details pages (same as aldryn-newsblog).

Coverage increased (+0.05%) to 96.006% when pulling 435b485c9da34dfc737444dc0751e94d2d4000d6 on razisayyed:develop into 86111befdef4fc87516d924629f46146dafde7b4 on nephila:develop.

Coverage increased (+0.05%) to 96.006% when pulling 435b485c9da34dfc737444dc0751e94d2d4000d6 on razisayyed:develop into 86111befdef4fc87516d924629f46146dafde7b4 on nephila:develop.

Coverage increased (+0.05%) to 96.006% when pulling 435b485c9da34dfc737444dc0751e94d2d4000d6 on razisayyed:develop into 86111befdef4fc87516d924629f46146dafde7b4 on nephila:develop.

I'm not keen to add this. I think static placeholders are much more flexible in this respect, as you can define the one you really want in the template instead of having the page cluttered with empty placeholders.
Would static placeholder solve your use case?

I do not know. But if I understand static placeholders the right way, I think they will be shared among different app instances using the same templates set, am I right?

Yes, but with templates set support of 0.9 you can have different sets of templates for different applications, or you can just use the namespace in the name of the static placeholders to have different static placeholders  in the same template set
On 18 September 2016 09:36:54 BST, Razi Alsayyed<EMAIL_ADDRESS>wrote:

I do not know. But if I understand static placeholders the right way, I
think they will be shared among different app instances using the same
templates set, am I right?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/nephila/djangocms-blog/pull/330#issuecomment-247834629

I like the Idea of using namespace in the name of static placeholders, I will give it a try.

namespace in the name of static placeholders works fine. I thinknit is better approach than adding placeholder fields to AppConfig. It give users more flexibility.

Thanks for reporting and liking the static placeholders solution! :+1:


Need help recovering bitcoins

I have not been able to access my bitcoins. It is not showing in my wallet.

@vapadilla You have not provided enough information, as @mr10008  said. I'll close this ticket. If for some reason you still do not see your funds, please open it again with more information.

@vapadilla
I can recover your wallet if you want need help send me email<EMAIL_ADDRESS>


Issue with state type but warning about store type in load-state

@ceoshikhar released in v0.12.1 just now


Inconsistent test results after update to lyon 0.15

Looks like we are getting some floating point inconsistencies on x86_64-unknown-linux-musl now. We already had issues on i586 before where we disabled the tests, but we should probably do a more robust hashing algorithm suited for images where tiny differences don't cause the hash to change.

The test is disabled for now until we have have a proper perceptual hashing algorithm. We should definitely look into img_hash though which implements a bunch of them.


Accept brotli encoding

Summary
Adds "br" to the Accept-encoding header. This will cause performance tests to use brotli compression if Kibana supports it.
Checklist
Delete any items that are not applicable to this PR.

[ ] Branch is successfully tested on Kibana CI
[ ] Unit tests are added

@dmlemeshko I've ran a build with this branch and brotli support on Kibana https://kibana-ci.elastic.co/job/elastic+kibana+load-testing/2159/parameters/
The numbers are different but still not 100% sure how to verify that brotli compression is actually used for all our API requests.

The numbers are different but still not 100% sure how to verify that brotli compression is actually used for all our API requests.

I will try to run locally with small load and enable verbose logging, it might help. I will add details as soon as I got it.

Gattling's request looks correct but I'm surprised that Kibana is responding without any Content-encoding header. main doesn't support brotli but it should gzip this response. I'll try to investigate this.

Oh the reason is that hapi doesn't compress responses less than 1024 bytes so it makes sense that this response wasn't compressed.

LGTM

Yes, but not on main yet as https://github.com/elastic/kibana/pull/142334 hasn't been merged yet.

Did another test with rockdaboot/use-brotli-compression branch and can see content-encoding: br header in response :tada:


HD44780 40x4 LCD displays?

Thank you for your pydPiper!
Are there any plans to support 40x4 LCD character displays?

It should be relatively straightforward to enhance the current HD44780 drive to support 40x4 but I do not have one to experiment with.


MINOR: Java 10 fixes so that the build passes

Upgrade EasyMock to 3.6 which adds support for Java 10
by upgrading to ASM 6.1.1.

Ensure that Jacoco is truly disabled for the core project.
This was the original intent, since it's in Scala, but it had not
been achieved. This is important because the Jacoco agent
fails when it tries to instrument the classes compiled by
scalac with Java 10.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@rajinisivaram trivial change that makes it possible to test against Java 10. Once we merge this, I will switch the PR jobs to use Java 10 instead of Java 9.


Build issue

Expected Behavior
Follow instructions to build the pocket web extension and load the resulting extension in Chrome Version 85.0.4183.102 (Official Build) (64-bit) in order to do development on Pocket.
Actual Behavior
Running npm run start fails to compile with an error:
Failed to compile.

./_chromium/background.js
Module not found: Can't resolve 'actions' in 'C:\Sites\extension-save-to-pocket\_chromium'
Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'C:\hiberfil.sys'

Steps to Reproduce the Problem

Clone master branch of this repo
Create keys.json in _chromium folder with the following:

{
  "Extension": "93318-XXXXXXXXXXXXXXXXX"
}

Run npm install
Run npm run start

Notes
Also tried loading the resulting build in build/_dev to chrome extension which is obviously not working due to some errors:
Uncaught Error: Cannot find module 'common/interface'
[WDS] Disconnected!

The build process has been updated. I recommend trying again following the new build instructions as of extension version 4.0.0


Double tap to zoom in iOS

It's possible to enable 'double tap to zoom' in fotorama on mobile safari?

Any changes on this? I would like to have this feature too. Great plugin btw.

Сlosing this, and leaving #313 open


Preserve style after double line break

Fixes: #5620
The issue: When you press Enter twice, the styling gets lost in the skipped paragraph, same when you type inside a table cells.
Why change this: consistent behaviour with other text editors.
This essentially undoes the changes done in here: https://github.com/facebook/lexical/pull/5292 while still fixing the issue that PR officially addressed.
Before:
https://github.com/facebook/lexical/assets/7893468/328f5197-fa2d-457a-a4dd-7b2a4802ceb1
After:
https://github.com/facebook/lexical/assets/7893468/ae34f9f5-8146-4f0b-8580-181fe2bff74b

^ We should really be writing some tests for all this discussion we're having above 😛

Hmm, which editors are you checking against for the table case? What I can see on GDocs and Word is that they retain the format regardless of whether you click again, but only for that specific position.
For the create paragraph, my hunch is that this logic is a one-off and they simply replicate the format when you insert a new paragraph.
Also, this PR seems to be preserving the style when clicking on a element position.
Screen.Recording.2024-03-12.at.9.42.24.AM.mov

Fair enough on tables, happy to keep it losing the current style between cells.
Losing the current format after a double line break, should be fixed though. If you have better suggestion on the approach, open to suggestions, since this is a super annoying problem when using the editor extensively.
I went with cleaning up the element node style nullifying because you can apply a style to a link node already and I couldn't find a use case when no style made sense, could be wrong. Happy to go for an alternative approach.

Hmm, which editors are you checking against for the table case? What I can see on GDocs and Word is that they retain the format regardless of whether you click again, but only for that specific position.
For the create paragraph, my hunch is that this logic is a one-off and they simply replicate the format when you insert a new paragraph.
Also, this PR seems to be preserving the style when clicking on a element position.
Screen.Recording.2024-03-12.at.9.42.24.AM.mov

Fair enough on tables, happy to keep it losing the current style between cells.
Losing the current format after a double line break, should be fixed though. If you have better suggestion on the approach, open to suggestions, since this is a super annoying problem when using the editor extensively. I went with cleaning up the element node style nullifying because you can apply a style to a link node already and I couldn't find a use case when no style made sense, could be wrong. Happy to go for an alternative approach.

Gave it a stab since I wasn't sure either, happy to follow up with a PR if you want - https://github.com/facebook/lexical/compare/main...eventsftw
https://github.com/facebook/lexical/assets/193447/b03a04fa-988c-41c7-bcc6-8dac2e5984d0
This should be very close to Word and GDoc. They seem to reset format but they leverage the empty "TextNode" to store this information when there's no text (this is a guess, I have no idea about their codebase).

Hmm, which editors are you checking against for the table case? What I can see on GDocs and Word is that they retain the format regardless of whether you click again, but only for that specific position.
For the create paragraph, my hunch is that this logic is a one-off and they simply replicate the format when you insert a new paragraph.
Also, this PR seems to be preserving the style when clicking on a element position.
Screen.Recording.2024-03-12.at.9.42.24.AM.mov

Fair enough on tables, happy to keep it losing the current style between cells.
Losing the current format after a double line break, should be fixed though. If you have better suggestion on the approach, open to suggestions, since this is a super annoying problem when using the editor extensively. I went with cleaning up the element node style nullifying because you can apply a style to a link node already and I couldn't find a use case when no style made sense, could be wrong. Happy to go for an alternative approach.

Gave it a stab since I wasn't sure either, happy to follow up with a polished PR if you want - main...eventsftw
Screen.Recording.2024-03-12.at.2.37.16.PM.mov
This should be very close to Word and GDoc. They seem to reset format but they leverage the empty "TextNode" to store this information when there's no text (this is a guess, I have no idea about their codebase).

Looking good, you can use $getPreviousSelection I think, the rest makes sense. Go for a proper PR :)


Release <IP_ADDRESS>

Changelog
- description: |
    Release <IP_ADDRESS>
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - improvement    # QoL changes e.g. refactoring
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
   - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context
Additional context for the PR goes here.
If the PR fixes a particular issue please provide a
link
to the issue.
Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] The change log section in the PR description has been filled in
[ ] New tests are added if needed and existing tests are updated.  These may include:

golden tests
property tests
round trip tests
integration tests
See Running tests for more details

[ ] The version bounds in .cabal files are updated
[ ] CI passes. See note on CI.  The following CI checks are required:

[ ] Code is linted with hlint.  See .github/workflows/check-hlint.yml to get the hlint version
[ ] Code is formatted with stylish-haskell.  See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
[ ] Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7

[ ] The changelog section in the PR is updated to describe the change
[ ] Self-reviewed the diff

@carbolymer question about the commands shifting to eras:
now that commands are again shifting into era based commands, whats the best way to call the commands we had up until conway in the past to be future proof? currently all my scripts are not using any era based parameter other than in the build-raw command. i have seen that when you use byron as the era, not all functions are available, which makes sense. so, the command are enabled we further go down all the eras right? so would it be safe to use "latest" as the default era? because that would support all available command with that cli version right?


Add search with autocomplete

Example data
[
  {
    "section": "Section name"
    "section_id": "section-name-1",
    "items": [
        {
            "page": "Page name 1",
            "page_id": "page-name-1",
            "text": "Lorem Ipsum is simply dummy text of the printing and typesetting industry"
        },
        {
            "page": "Page name 1",
            "page_id": "page-name-2",
            "text": "containing Lorem Ipsum passages, and more recently with desktop publishing software"
        }
    ]
  }
]

[x] Search input

[x] Search ≥ 2 symbols
[x] Search all keys

[ ] Search items

[x] Section link. Show section title if more than 1 page
[x] Page link
[x] Output content
[ ] Highlight
[ ] Link to anchor (need block id and #anchor from back-end)

[ ] Or without anchor: https://.../section-name-1/page-name-1#:~:text url (https://caniuse.com/url-scroll-to-text-fragment)

Design
https://www.figma.com/file/VpUQ8aZanmAIbwlSt5UTKH/🚲-Ekaterinburg.design?node-id=3405%3A3302

You can reverе these commit and continue working
https://github.com/ekaterinburgdev/guides/pull/119/files

We have disabled the searchbar. To continue its development, you can revert this changes:
https://github.com/ekaterinburgdev/guides/pull/119/files


import in python 2.7 fails with 127 error in Win 7

Windows 7, R works fine
python 2.7.10 | EPD 7.5-3 (64-bit), numpy, scipy, theano etc works fine
Steps:

cloned repository recursively
build and make in the main directory (no visible errors, libxgboost.dll and libxgboost.a libraries are in /lib folder)
switch to python-package folder, call python setup.py install, again no visible errors
start python, call
>>>import xgboost
get the following error message:

  File "<stdin>", line 1, in <module>
  File "xgboost\__init__.py", line 11, in <module>
    from .core import DMatrix, Booster
  File "xgboost\core.py", line 83, in <module>
    _LIB = _load_lib()
  File "xgboost\core.py", line 77, in _load_lib
    lib = ctypes.cdll.LoadLibrary(lib_path[0])
  File "P:\Python\Python27\lib\ctypes\__init__.py", line 443, in LoadLibrary
    return self._dlltype(name)
  File "P:\Python\Python27\lib\ctypes\__init__.py", line 365, in __init__
    self._handle = _dlopen(self._name, mode)
WindowsError: [Error 127] The specified procedure could not be found

I hacked core.py to check which library it actually tries to load :)
it actually looks for the right dll
/Sources/xgb/python-package/xgboost/../../lib/libxgboost.dll
which is exactly where it is located, freshly built few minutes ago

How do you build the xgboost？

you should follow this：
http://xgboost.readthedocs.io/en/latest/build.html#building-on-windows

then install the python package

I had the exact same error with you.
Try to uninstall other version of Python on your machine and reboot. I know this is not a nice solution, but it works for me.

I had the same error, but the fix leaves many questions unanswered. It turns out that, for whatever reason, having the mingw path at the beginning of the system path (rather than end for me) solved the issue.
>>> dir = r'C:\Program Files\mingw-w64\x86_64-6.2.0-posix-seh-rt_v5-rev1\mingw64\bin'
>>> import os
>>> os.environ['PATH'].count(dir)
1
>>> os.environ['PATH'].find(dir)
1491
>>> os.environ['PATH'] = dir + ';' + os.environ['PATH']
>>> import xgboost # I modified core.py to print the directory of the requested dll
C:\Users\Joey\Anaconda2\lib\site-packages\xgboost-0.6-py2.7.egg\xgboost\libxgboost.dll

This is the only way it works.
Please note that the directory of the requested dll is the same in both the failure and successful case, so it is not that. The only thing that changes is putting the mingw/bin directory in the beginning of the path variable.


Zig: Run Zig command fails to launch in Windows Powershell

On Windows, the Zig: Run Zig command attempts to invoke a command line in Powershell. This command fails for the following:
PS C:\[redacted]> "c:\[pathto]\zig.exe" run "c:\[pathto]\main.zig"
At line:1 char:113
+ ... age\ziglang.vscode-zig\zig\windows-x86_64-0.13.0\zig.exe" run "c:\Use ...
+                                                               ~~~
Unexpected token 'run' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnexpectedToken

A workaround I've found is to start the command line with an ampersand, &, known as the Powershell call operator.
PS C:\[redacted]> & "c:\[pathto]\zig.exe" run "c:\[pathto]\main.zig"
Hello, World!

Works for me though.  Here's what I see in the Terminal output when invoking Zig: Run Zig:
PS C:\Users\janne\dev\aoc2024\rest_of_days> C:\Users\janne\scoop\shims\zig.EXE build run

Your path to zig doesn't have quotes. I just tried running my command without quotes and it worked without ampersand. Not sure what the logic is for adding quotes though.


💭  How can I access iOS TrueDepth Camera?

Question
I've got an iphone 14 and I trying to use TrueDepth Camera to check how an object is.
Probably this is the wrong approach but this is what I did:

I called useCameraDevices() and got a list of devices.
Filtered out deviced which "isMultiCam" is false
The list devices ends up with a single element
I picked a format which "supportsDepthCapture" is true

This is what my camera element looks like:
<Camera
style={{ width: '100%', aspectRatio: 16 / 9 }}
device={trueDepthCamera}
format={trueDepthCameraFormat}
isActive={isCameraActive && isFocused}
enableDepthData={true}
ref={camera}
/>
However, I can't find any depth data. I've added a Frame Processor Plugin as well and still couldn't see any depth data.
Can you guys help me here ?
What I tried
No response
VisionCamera Version
"react-native-vision-camera": "^3.9.0",
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

See this feature request: https://github.com/mrousavy/react-native-vision-camera/issues/2628


chore: import repository https://github.com/jenkins-x-sampleproject/jenkinsquickstart.git

this commit will trigger a pipeline to generate the CI/CD configuration which will create a second commit on this Pull Request before it auto merges

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jx-info] Hi, we've detected that the pipelines in this repository are using a syntax that will soon be deprecated.
We'll continue to update you through PRs as we progress. Please check #8589 for further information.

@jxbotaccount: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

verify
9cb64c64cf7d3789c1ea862adab54ede28a1c30f
link
/test verify

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


templates.json: Remove deprecated dotnetUno and dotnetUnoFrameBuffer.  Also, little fix on createFromTemplate.ps1

Remove this deprecated templates from templates.json, so they don't showup as options on project creation.

LGTM!


Two tricks and a pitfall

With a little bit of delay, here's my code and tell from last week's message meeting.

I suggest that @LauWien reviews this PR instead of me

That's exactly what I wanted to do but for some reason GitHub didn't allow to select her as a reviewer. It probably has something to do with the access rights, I'll check


Wrap validation

ocr-fileformat also supports validation of many OCR formats, we should wrap that as well in addition to the core-provided XSD validation.
(ht @wrznr)

What should that processor do – merely output logging and an exit value, or create some sort of report in an output file group?


Instructions panel can't be scrolled to the bottom

Describe the bug
The instructions panel of an exercise can't be scrolled until the bottom. Some parts of the class diagram can't be seen.

Environment

 - OS: macOS Mojave 10.14.3
 - Browser: Chrome 73.0.3683.86
 - Version: Artemis 3.0.0

This is an issue with the way the editor is styled:
The build output component can overlay the instructions if the user has a small screen or resizes the components. I'll look into it.

https://github.com/ls1intum/ArTEMiS/pull/344

Resolved. @Khalphion Thanks for the report!


Update to api23

Hi @miguelpalacio,
These last days I discovered SL4A and since then I have been playing with it. You have made a great work updating the project to api 23! Congrats! :)
I am interested in contribute to the project and I have started making some minor changes in your branch 'UpdateToApi23'. Here are my proposal to merge with your repository if you want, of course.
The pull request includes the next changes:

Workaround to solve an issue related with bluetooth stack since android 4.2.

The public ip address is used in the ServerSocket constructor when the user chooses to start a public server. Doing this, the ip and port will be displayed properly in the ui.

Added new method to load a layout from a file.

Added new folder to hold scripts examples.

Cheers!
JJ

Hi @josejuansanchez,
Thank you for your interest in my work. I'm glad you liked it! I took me a little bit to review all your changes and they seem to be good (actually very good!), so I will merge them into my repository now. Thank you for sharing them :).
There's a caveat though: right now, the project is not ready for API 23. As you may already know, from Android Marshmallow, the way in which permissions are handled "radically" changed and now they are managed in runtime.
The related problem occurs when you are running SL4A on a device with Android 23, in which the application crashes (the simple workaround is to enable all the permissions manually from the App Info window on Android). I'm gonna write this on the README file so that people know.
PS: actually, at the moment I'm working more on the UiFacadeUpdates branch, targeting API 22, I don't know if I will manage to make the corrections regarding the permissions for Android Marshmallow.
Thank you again for your work, cheers!
Miguel Palacio

@miguelpalacio I would like to know more about the new permissions model in Android Marshmallow, so I could work on the UpdateToApi23branch and try to solve the current issue related with the permissions. I am going to experiment a little bit with it...

@josejuansanchez that's great! Please let me know if you can make some progress regarding this, or if you need any help (maybe I can help). For the next weeks I'll be kinda busy but I definitely will take a look at your fork ;-)


[fixed] set default role for accessibility

Fixes #653 .
Changes proposed:

Set default value for role

As @afercia suggested, we should set a default value for the dialog. And omit it entirely when passing null.
Upgrade Path (for changed or removed APIs):
No API changed
Acceptance Checklist:

[x] The commit message follows the guidelines in CONTRIBUTING.md.
[x] Documentation (README.md) and examples have been updated as needed.
[x] If this is a code change, a spec testing the functionality has been added.
[x] If the commit message has [changed] or [removed], there is an upgrade path above.

Coverage remained the same at 87.703% when pulling add7180f89e4cc5398b505d67e3e58c999cab4b1 on wszgxa:set-default-role into 1e349c07c855a3b6de1455908ad143bca9e4167a on reactjs:master.

@wszgxa I think it's just missing some tests to omit the role property. Can you include a test for it, please?

@diasbruno Done

Good job, @wszgxa. Thank you.


Allow using multiple threads to (de)compress hts files

Updates the --threads (-t) logic to allow using multiple threads to (de)compress HTS files. This can improve thread scaling.
The threads are split into two pools: lift (--lift_threads) and hts (--hts_threads). Users can specify them explicitly, or leverage the auto thread inference algorithm: with t threads assigned to leviosam2, max(0, t/4) threads are assigned to HTS and the rest are assigned to the lift core.

This would be great! One suggestion, I would set the default number of (de)compression threads to be the max of 1 and 25% of the total requested threads.
This isn't a perfect heuristic, but after playing with samtools on a lot of different systems and use cases, I find myself almost always doing this.

@mrvollger many thanks for the suggestion! I updated the PR to apply the logic.

Link to the issue: https://github.com/milkschen/leviosam2/issues/72


Settle on a coordinated color scheme and design language for icons

We want to synchronize colors between:

Goals
Actions
Crafting status
Signal kind
Abilities

There's matching variants in each (e.g. Ability::Lure and Goal::Lure), so these need to correspond correctly while being meaningfully distinct from their siblings.
Particularly important combinations (e.g. Push/Pull/Work) should be color-blind friendly too.
Spreadsheet seems like the only sensible way to plan this.

Each of these variants should get a a standardized modifier that surrounds the symbol (e.g. a circle or hex) so we can communicate symbol kind and reuse the inner icons.

Units, structures, and terraforming all need a modifier as well T_T


JTAppleCalendarViewDelegate methods are not called after calling ScrollToDate

When I called calendar view ScrollToDate, I thought all the related delegate method like didScrollToDateSegmentWith and scrollDidEndDecelerating will be called, but actually not.
Is this a issue?

This is a newly introduced bug in the last version. It has already been fixed on master branch.
To get the latest code put this in your pod file
pod 'JTAppleCalendar', :git => 'https://github.com/patchthecode/JTAppleCalendar.git'

and then do a pod install

new version released.
closing this issue


Imported component with bottomsheet has no closing animation slide

When creating a component with a bottomsheet in it and then importing that component into another component, the sliding animation that happens onClose is not happening, instead the bottomSheet just disappears instantly. the opening animation works correctly tho,  Any ideas on this ? Thanks

The issue was because the component Bundles with BottomSheet was wrapped inside a conditional rendering like this  {isBundlesOpen && (         <Bundles           onClose={CloseBundles}           isOpen={isBundlesOpen}           title="You're out of taps" // Pass the title as prop         />       )} removing the unecessary isBundlesOpen solved the issue.


[Feature][Data-Explorer]: Implement Data-Explorer UI

Connector Name
other (None Listed Above)
Suggested feature
Implement UIs for Data-Explorer following the UI designs here
Related issues
I am trying to do [...] but [...]

Decided to re-visit the design of the Choreo Data Explorer, therefore closing the issue


chore(requirements): updating django version and dependencies

Updating Django to newer version and pyOpenSSL in order to address security vulnerabilities. Also we need to address some code in order to upgrade djangorestframework package: https://github.com/teamhephy/controller/issues/80

CI passes and merging now


python3Packages.pikepdf: 4.4.0 -> 4.4.1

Motivation for this change
https://github.com/pikepdf/pikepdf/blob/v4.4.1/docs/release_notes.rst
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 157472 run on x86_64-linux 1

8 packages built:

img2pdf (python39Packages.img2pdf)
ocrmypdf (python39Packages.ocrmypdf)
paperless-ng
pdfarranger
python310Packages.img2pdf
python310Packages.ocrmypdf
python310Packages.pikepdf
python39Packages.pikepdf


Add xml v2 support

[x] Handle field selection
[x] Handle TargetApplication selection
[x] Handle plugin version filtering

This is based on top of #4 so we should merged it first.

However @magopian would you like to give me a review about this work: https://github.com/mozilla-services/kinto2xml/compare/add-xml-verifier...add-xml-v2-support?expand=1

r+ (not reviewed the xml thoroughly though)


Feature/#81 Add Google Auth Strategy 🚀

Conveniently found this guide, adapted it to our project, and it's working like a charm.
Didn't know if we have a dedicated account or not so I set up one in the mid-time.
Just pulling from google at the moment:

Name
Last name
Email
Photo
Secret key

@ArturoDucasse I've looked into the article you linked, and it's a good starting point but that is not going to work with our already established JWT system. I'm gonna try to give you some suggestions while I review the code.

Hey, thanks for the comments kero.
I appreciate the time you took to read it through, will make these changes. Yet I haven't done much, just followed the guide and connecting the dots (barely 😄) but I'm feeling more comfortable in Nest... at least I'm not that completely lost 😂.
I will get to these suggestions right away.

@all-contributors please add @ArturoDucasse  for code

@ArturoDucasse seems like I cannot request you for a review as it's your PR. I have pushed the changes we talked about and the ones I left in my review. You can look over the files to see if there is something else I've missed


Missing mandatory parameters in swagger

Hello waltid team!
I am looking to have a signed participant vc returned by the wallet.
I understand it's the /api/wallet/issuance/start route that can do this.
Only I don't know what parameter to give it to make it work... can you help me please?
@mikeplotean @severinstampler

Hi @oriana13
The api endpoint you're referring to, is used by the web wallet to trigger an issuance flow with an external issuer, following the OIDC for credential issuance protocol.
If you want to directly issue a signed credential, you could look into the issuer api of the walletkit.
You find a documentation of it here: https://docs.walt.id/v/web-wallet/getting-started/rest-apis/credential-issuance
Let me know if this helps, or if I misunderstood your use case.
Thanks. Best regards.


HTMLElement.focus missing options object

Missing/Incorrect APIs
The focus method of HTMLElement is missing the options object.

Relevant documentation
Typedef.
Focus docs.

Hi,
I am attempting to address this issue in PR #7711 as my first contribution. :smile:
Thanks,
Cindy

This should be addressed by #7711.


File switching method

Adds a method to facilitate navigating between codebooks for multiple files. Initialize like this:
var config = {files:[
	{path: "https://rhoinc.github.io/viz-library/0000-sample-data/safetyData/ADAE.csv", label: "ADAE", settings:{}},
	{path: "https://rhoinc.github.io/viz-library/0000-sample-data/safetyData/ADBDS.csv", label: "ADBDS", settings:{} },
	{path: "https://rhoinc.github.io/viz-library/0000-sample-data/safetyData/DM.csv", label: "DM", settings:{}},
	{path: "https://rhoinc.github.io/viz-library/0000-sample-data/safetyData/labs.csv", label: "labs", settings:{}},
	{path: "https://rhoinc.github.io/viz-library/0000-sample-data/safetyData/LB.csv", label: "LB", settings:{}},
	{path: "https://rhoinc.github.io/viz-library/0000-sample-data/safetyData/VS.csv", label: "VS", settings:{}}
]}

webcodebook.createExplorer("body",config).init()

Looks straightforward to me.  I do think it would be cool to open a local file from the webpage but that might involve scary things like ajax that I've never tried.

Yeah - allowing a user to load a file on their computer is definitely doable. We can add in a future release.


Remove duplicated text

The text:

All users with basic access can view, add, and configure Delivery Plans. Stakeholders, however, don't have access to Delivery Plans.

is repeated.

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


An internal server error of 500 occurred updating a subscription item

An internal server error of 500 occurred updating a subscription item.
API Reference: Update a subscription item
curl -X "PATCH" "https://api.lemonsqueezy.com/v1/subscription-items/211097" \
     -H 'Authorization: Bearer {api_key}' \
     -H 'Content-Type: application/vnd.api+json' \
     -H 'Accept: application/vnd.api+json' \
     -d $'{
  "data": {
    "type": "subscription-items",
    "id": "211097",
    "attributes": {
      "quantity": 10
    }
  }
}'

It keeps giving a 500 error :(

Thank you for reporting this. It will be fixed in the next couple of days.


Fixed a failure of a test1 case, update verification obs input, and use bending angle

Description

The default is set to 36 cores per node for the forecast step, which caused a failure for one 'test1' scenario pointing to Duda's folder missing the MPAS partition file for 288 cores. Set to 32 cores (thus use 256 cores) in the scenario yaml fixed the problem.

Update the hofx obs input location for cycling experiments using raw data with bias correction. Those hofx input obs are used for the forecast verification purpose and we'd better use GSI-ncdiag files and bias-corrected radiance data so that the consistent number of obs is used when comparing forecasts from multiple cycling experiments.

Use GNSSRO bending angle instead of refractivity

List of modified files
M       scenarios/3dvar_O30kmIE60km_ColdStart.yaml
M       test/testinput/3dvar_O30kmIE60km_ColdStart.yaml
M       scenarios/defaults/observations.yaml
M       initialize/data/Observations.py

@ibanos90 Bending angle results look good. So I changed the default to use bending angle now. Please review.

@ibanos90 Bending angle results look good. So I changed the default to use bending angle now. Please review.

Sorry that I missed this. These changes look good!

@liujake , I noticed that this PR is also merged to release/2.0.0 branch. I wonder if current release/2.0.0 branch of MPAS-Workflow is good for running some experiment. Or are there any further modification planned for release/2.0.0 ?

2.0.0 was cut off from the develop Yesterday. So they are the same now. Good to use 2.0.0 branch.

2.0.0 was cut off from the develop Yesterday. So they are the same now. Good to use 2.0.0 branch.

Thank you for confirming!


Role of Azure Load Balancer

Could you please elaborate what is the role and benefits of the Azure Load Balancer in that scenario? As far as I know, it is also possible to expose Ingress Controller directly to consumers. Why is it recommended to have LB in front of it?

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

ID: c5e2e444-d6b9-962e-56d4-8d1f3508ba9e
Version Independent ID: 061ea6aa-353b-a98d-cbf6-639209a5fd1b
Content: Microservices architecture on Azure Kubernetes Service (AKS)
Content Source: docs/reference-architectures/microservices/aks.md
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @MikeWasson
Microsoft Alias: pnp

@snake-net An ingress controller (like nginx-ingress) still runs on the cluster as a daemonset, so there is an instance running on each node. Now, as your cluster scales, you would have multiple nodes through which you can access the ingress endpoint running on your cluster.
And instead of loading all ingress traffic through one node, an Azure Load Balancer would help route traffic equally among the nodes.
Also, this way, your nodes (the VMs) don't have to be exposed directly to the internet as well.

That is clear now. Thank you!

@snake-net Glad that we could help!
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@PramodValavala-MSFT
FYI, I am a lerner-beginner.
I am a bit confused about LB. is this an old way of implementation. why are we not using API gateway that has both load balancer and WAF.  If we can use API gateway as an Ingress controller(Application Gateway Ingress Controller (AGIC)), we can expose API gateway right? (internally i can use API management PAAS service to map the different APIs from AKS). Please elaborate?

@mohanM5k Not really. It mostly comes down to choice.
With AGIC, like their docs mention, it eliminates the need for a load balancer since it handles both load balancing (between K8s nodes) and ingress for your services. So, as long as your all of your clusters are on Azure, AGIC is indeed a great way to go about it to simplify your infrastructure.
Without AGIC however, you would need separate services that perform both load balancing and ingress, where many use in-cluster solutions like nginx-ingress or even APIM directly running within K8s and a platform specific load balancing depending on where K8s is hosted. This is more platform agnostic since in-cluster solutions don't depend on where/how your K8s clusters are hosted.
I hope that helps clarify your query. Since this is an old post, it would be best to create a new post on Microsoft Q&A to engage the wider community, if you have any further queries.


Unable to route a request to a static file(images or htmt file)

Hi @typicode
First of all thanks for such an awesome mocking tool...!!
Please help me out in routing of a dynamic request to serve a static image file.
// route.json
{
"/storage/:id" : "/assets/images/test_1.png"
}
I can see test_1.png images with URL below in my browser after setting --static flag
http://localhost:5000/assets/images/test_1.png
but
http://locahost:5000/storage/123456789
is giving me 404 response.
Its urgent
Thanks in advance..!!

I am closing issue as i got solution for my query here


cycle, cycleWhile, cycleUntil don't make sense on Set, SortedSet, PSetX, POrderedSetX

Return type on these collections should be ListX or PStackX

Fixed on head.


Fixed typo in code example

Space was missing :)

@IrisClasson : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Heroku deployment

I tried deploying darkwire.io on Heroku but it seems the gulp setup is conflicting. I don't know if you haver tried it with Heroku but given that you can one instance of a node.js application for free it makes a great test system for the newest features if one doesn't just want to test locally.
If there is interest in making it runnable on Heroku I can provide some logs. I was hoping to be able to fix it myself and send you a PR. But it seems my node.js foo is just too pathetic for that.

I've used Heroku for other things. What error are you getting?
You might need to reference gulp locally. So in your Procfile try web: npm run bundle && node_modules/gulp/bin/gulp.js start

Actually, in production you probably shouldn't be using Nodemon to run the app. Try just web: npm run bundle && node index.js

I tried your suggestion. Install is successful but the app crashes: https://gist.github.com/dietmarw/1cfe1b871c9d0d60f69d

I'm guessing Gulp isn't installed globally on Heroku. So try node_modules/gulp/bin/gulp.js bundle && node index.js

One step further: https://gist.github.com/dietmarw/1cfe1b871c9d0d60f69d

What branch are you on? Do you have a .babelrc file in the root? Should look like this:
{
  "presets": ["es2015"]
}

I'm on feature/Filetransfer and yes that file is there.

Looks like it's having trouble finding that file. You can try something like this where you import the preset directly into Gulp.
Weird that it says 'relative to directory "/app"' - I guess /app is the root directory Heroku makes?

Yes "/app" is the directory heroku deploys from (so copies all the files to). I tried adding the solution you linked to into the gulpfile.babel.js but got exactly the same error message. So this did not help :frowning:

So our build process/dependencies are kind of a mess right now - so this will be sorted out - but I think the problem is that Heroku doesn't install devDependencies.
You can either move babel and other devDependencies in package.json into dependencies or run heroku config:set NPM_CONFIG_PRODUCTION=false

OK that brought it a good bit  further. So to summarise, with:

Procfile : web: npm run bundle && node_modules/gulp/bin/gulp.js start
heroku config:set NPM_CONFIG_PRODUCTION=false

Heroku manages to start the app now. It will timeout though because it can not bind the port 3000. Herokuapps normally take 5000. I think to have seen a commit one place where you can configure this in darkwire too now. Any pointers?

port=5000 npm start

npm run bundle && port=5000 node_modules/gulp/bin/gulp.js start
I wouldn't recommend using nodemon in production (which is what gulp start uses). I would use this: node_modules/gulp/bin/gulp.js bundle && port=5000 node index.js

I would also advise not using feature branches as they are just for development and changes rapidly. Stick with develop for an edge version and master for a stable release :+1:

Well sure. But the whole point here is being able to test things out and give early feedback. :-) It works fine on my local install and just thought it would be fun to have a through away heroku test instance.

Anyway it seems I found two pointers for a possible solution of the last remaining issue: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch. Either:

the localhost needs to be addressed as <IP_ADDRESS> (GH issue)

or/and

the port listening method needs to be slightly modified

Did you try this?
.listen(process.env.PORT || 5000)

I saw that but didn't know where to add that line.

Check out this branch.
Procfile
web: npm run bundle && port=$PORT node_modules/gulp/bin/gulp.js start

THAT WORKED! Thanks: http://moleaks.herokuapp.com/4yco8fOjg
Only difference, following @alanfriedman 's advice I used:
web: npm run bundle && port=$PORT node index.js

Awesome- from develop, you can use actually replace your Procfile with web: port=$PORT npm start and it should work. Also remember to https! Cheers.

OK will try that right away. Well though https gives additional "tunnel" the streams themselvs should still be encrypted even if via http, right?

Correct- however the app won't work in latest version of Chrome unless its through https. If you're just deploying for testing on another browser, you should be ok.

Thanks to the heroku test-setup I can now see that text-input is not working for Chrome browser (linux and windows). Works fine on Firefox. And local install works everywhere. Feel free to test it with the heroku address from above.

Ah you beat me to it again.  So: https://moleaks.herokuapp.com

Cool. I was just starting to look into Let's encrypt+Heroku

Btw, you might wanna register darkwire as herokuapp ;-) At first I've chosen that name but thought it might be confused with the real thing.

darkwire.herokuapp.com :+1:

SSL cert on Heroku is only needed if you want to use a custom domain.

You could use the herokuapp as part of CI deploy.


fix bad code migration

While working on PR #3382, I've noticed these strange characters in the topic and thought they looked wrong.
Here's the old version of the same topic:
https://msdn.microsoft.com/en-us/library/4571ccfe-8a60-4f06-9b37-7ac0b1c2d10f(vs.100)

@rpetrusha I've addressed your feedback. Please let me know if I got that right.

Yes, you did get it right, @mairaw. Thanks for making the additional improvements.


ReadME

README
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information
Acceptance Criteria
GIVEN the prework project repository,
WHEN I view the README for the repository,
THEN I can see a professional README that provides information on the project and how to use it

added project details to the README, using markdown language


Fixes

Fixed #78 #79 #80 #81

This has not been tested by me.

Thanks, merged via. https://github.com/shagu/pfQuest-turtle/commit/968fd1544f82a5181722114c6b7bb5aabfecedd3


AsyncSearcher Type

Hi,
I'm creating a typescript class and trying to type one of the properties as AsyncSearcher but it isn't an exported type. How should I correctly be typing a property that will hold the return of lilconfig('my_module')?
Example:
class MyClass {
  configSearcher: AsyncSearcher;

  constructor() {
    this.configSearcher = lilconfig('my_module');
  }
}

Hi and thank you for the issue.
The type is not exported as there is no such type exported from cosmiconfig.
However, you can still extract the type via ReturnType<typeof lilconfig>
import {lilconfig, lilconfigSync} from 'lilconfig'

declare function takesSearcher(searcher: ReturnType<typeof lilconfig>): void

const asyncSearcher = lilconfig('foo');

takesSearcher(asyncSearcher) // no error

takesSearcher({}) // expected error

const syncSearcher = lilconfigSync('foo');

takesSearcher(syncSearcher) // expected error

ts playground

@antonk52 That makes sense, thank you!


DBZ-7425 Use adapter-specific offset loaders when copying offsets

https://issues.redhat.com/browse/DBZ-7425

/packit test --labels oracle

/packit test --labels oracle

/packit test --labels oracle

Test failure is unrelated, being fixed in PR #5202

Applied to main (=2.6) and branch 2.5.


Click Evnets in EChart stacked Bar Chart

HI
I am using Echart library for my chart generation in that i am using mouse click events.
I am facing issue in Stacked bar chart.
Issue:When i am clicking on stacked bar chart i am getting values like below.
productA
Dinesh
But i need this values with there respective column names like below.
Product Name:productA
Sales Rep:Dinesh
This is the link i am musing to generate stacked bar chart....
https://ecomfe.github.io/echarts-examples/public/editor.html?c=bar-y-category-stack
Please help me to get click events like above what code i need to use.
Thanks in Advance............

No one facing this issue......
or this is the bug in echart????

Hello @AngariDinesh
This link may help you  : http://echarts.baidu.com/echarts2/doc/example/event.html
Cheers

If the title of an issue isn't spelled correctly... is it really an issue?


Uninstall previous sync extensions

Visual Studio Code Version : 1.2.1
Code Sync Settings Version : 1.3.0
Operating System : Windows 7
Steps to reproduce:

Setup vscode and code-settings-sync in 2 different environments (A and B)
Install an extension in environment A and sync settings.
Download settings in environment B and the extension is installed.
Uninstall the extension in environment B and sync settings. (Check gist and the extension.json file doesn't have the extension).
Download settings in environment A.

Expected situation: The extension is removed.
Actual situation: The extension remains installed.

yes i have not written the code to remove the extension, started working on it :)

I have updated the extension. I am closing this issue. Feel free to re open if there is any error.

It's working perfect!
thank you very much!


Example at README.md throws an error: undefined: v2.NewClientHTTP

I am a newbie in cloudevents and when I run the example of README.md it throw the error. Here is the code that wrote
package main

import (
	"context"
	"log"

	cloudevents "github.com/cloudevents/sdk-go/v2"
)

func main() {
	c, err := cloudevents.NewClientHTTP()
	if err != nil {
		log.Fatalf("failed to create client, %v", err)
	}

	// Create an Event.
	event := cloudevents.NewEvent()
	event.SetSource("example/uri")
	event.SetType("example.type")
	event.SetData(cloudevents.ApplicationJSON, map[string]string{"hello": "world"})

	// Set a target.
	ctx := cloudevents.ContextWithTarget(context.Background(), "http://localhost:8080/")

	// Send that Event.
	if result := c.Send(ctx, event); cloudevents.IsUndelivered(result) {
		log.Fatalf("failed to send, %v", result)
	}
}

I think the answer here is you are attempting to use documentation at HEAD but golang pulls the last release, which is https://github.com/cloudevents/sdk-go/tree/release-2.3

Ok @n3wscott I will try and let you know about the results soon. )


[Backend] Delete admin

Create a route to delete an admin. This can be performed only if the request is made by a SuperAdmin.
Refer to existing route for help
API testing is required. Refer #81 for resources

can you please assign me this issue.

you are GSSoC participant right?

yess

@sukhpreet-singh1 Please update your status and open pr.

Hi. I would like to work on this issue. I am a GSSOC participant

Hi. I would like to work on this issue. I am a GSSOC participant

You have been assigned an issue. Complete that before taking up another

Ok noted. Thanks

Hi. I need a little help.For testing purposes, I might need to create a new admin. Please help as to how can I do that.

ok noted. Thank you

@kumarshobhit any update? please udpate else will have to reassign this to someone else

You may please reassign it. I won't be able to work on it.

I would like to work on it

Can you assign this issue to me? ................I found this project interesting to work on.

Hi, is this issue still open? If so i would like to work on it!

I would like to work on this issue under GSSOC`22.

Hi , I'm a GSSOC'22 participant. Can you please assign this issue to me and I'll be happy to work with it.

@SciSaif please go ahead with this issue. @PriyankjeetPradhan please look for other issues as we can assign on the basis of FCFS(First Come, First Serve)

@Kajol-Kumari, please assign this to me


set default TFT_ROTATE value

For setting the parameter of fbtft_device. Set the default value to 0.
Connects to #38

Would this be better as ${TFT_ROTATE:-0} ?
There's a very subtle difference http://wiki.bash-hackers.org/syntax/pe#use_a_default_value

@lurch I think in this case it does not matter in practice, because in the dashboard at least you cannot create an empty variable. But anyways.
For reference:

If you omit the : (colon) the default value is only used when the parameter was unset, not when it was empty.


160 remove scheme from securityDefinitions after converting to  swagger_2

What does this PR do
Remove securityDefinitions.scheme after conversion.

Does it look good for you?

Looks good! Thanks for the contribution.

Published as 2.7.6


PrismaClientKnownRequestError is no longer identifiable

Bug description
Checking the instance of a Prisma error no longer works.  It worked for quite some time, however, it stopped working after we did package update to v4.
error instanceof PrismaClientKnownRequestError  will always return false even when it's a known error e.g. unique constraint violation - P2002.
This change prevents us from catching known Prisma errors as we used to with error instanceof PrismaClientKnownRequestError. It broke all of our server-side validation checks since we no longer have a guaranteed way to detect Prisma errors.
How to reproduce
Try to perform Prisma.create on a unique constraint that already exists to trigger a prisma error code 2002.  I believe the problem persist on other error codes as well but I cannot confirm.
Expected behavior
Known Prima errors should be able to be caught with error instanceof PrismaClientKnownRequestError
Prisma information

model Link {
  companyId  String   @db.Uuid
  id         String   @id @default(dbgenerated("gen_random_uuid()")) @db.Uuid
  type       String

  @@unique([companyId, type])
  @@map("link")
}

await prisma.companyLink.create({data:{type:"TEST", companyId:"company-uuid"}}});

Environment & setup

OS: Windows WSL - Ubuntu
Database: PostgreSQL
Node.js version: 16.15.0

Prisma Version
prisma: 4.10.0
@prisma/client: 4.10.0

I had the same. I have fixed it in a next way:
import { Prisma } from '@prisma/client';

if (error instanceof Prisma.PrismaClientKnownRequestError) {
  // your code
}

Docs reference https://www.prisma.io/docs/concepts/components/prisma-client/handling-exceptions-and-errors

@lifedup could you please share the full code snippet, including the imports. I mostly want to know where did you import PrismaClientKnownRequestError. The way @kukuew describes is the way it supposed to work. @prisma/client does not export PrismaClientKnownRequestError without Prisma namespace, so I am not sure where are you getting it from.

This seems to have been broken in 4.10 by the deprecation of import { PrismaClientKnownRequestError } from '@prisma/client/runtime'.
Is it now a different object entirely depending where it's imported from?

Depending on the configuration, there was always (even pre 4.10) a possibility that import from runtime module will not match the one imported from client. @prisma/client/runtime is a private module and it is not supposed to be used in the app code. Future proof and supported way of handling errors is importing it from Prisma namespace from @prisma/client module as our docs suggest.

@prisma/client/runtime is a private module and it is not supposed to be used in the app code

There is a bit of a foot-gun here where VSCode (and I assume other editors) will auto-generate an import from @prisma/client/runtime if we type PrismaClientKnownRequestError (without the Prisma. namespace prefix) and hit enter to select from the autocompleted suggested imports.  This type-checks just fine so it's easy to miss this isn't the documented import of Prisma.PrismaClientKnownRequestError from the public namespace.
It would be nice if the exports from the internal/private @prisma/client/runtime module could be prevented from showing up in editor autocomplete. (I think this could be achieved by refactoring the "private" runtime module to export under it's own namespace, for example - there may be better ways to achieve this.)

@andyjy @lifedup Thank you for the pointers, VS Code autocomplete is definitely a problem we'd like to address here.

I had the same. I have fixed it in a next way:
import { Prisma } from '@prisma/client';

if (error instanceof Prisma.PrismaClientKnownRequestError) {
  // your code
}

Docs reference https://www.prisma.io/docs/concepts/components/prisma-client/handling-exceptions-and-errors

l3ezz it works perfectly

This is working for me on localhost but not when I use docker.

I fixed the problem in this way. Until now it works well.
// imported
import { PrismaClientKnownRequestError } from<EMAIL_ADDRESS>
// coding inside try-catch
 if (error) {
      if (error instanceof PrismaClientKnownRequestError) {
        if (error.code === "P2002") {
          return {
            message: "Email already Exist in the DB",
          };
        }
      }
    }


Common image FX buffered image ops

Might be nice to predefine common image filters in bufferedimage ops like the anti alising one.
Black and white
Sepia
And other common filters might be handy.

Lighten and Darken may be helpful as well.

Fixed, added in 4.0
Didn't add sepia for lack of optimal color modification code and target color palette.


[kinesis] Add alarm on Kinesis read/write throttling

Create alarm on throttling events (N) reported by Kinesis.

There is addPutRecordsThrottledAlarm for Kinesis.

Another set of tips from the docs:
Best Practices with CloudWatch Alarms
Add CloudWatch alarms for when the following metrics exceed the buffering limit (a maximum of 15 minutes):

DeliveryToS3.DataFreshness
DeliveryToSplunk.DataFreshness
DeliveryToAmazonOpenSearchService.DataFreshness

Also, create alarms based on the following metric math expressions.

IncomingBytes (Sum per 5 Minutes) / 300 approaches a percentage of BytesPerSecondLimit.
IncomingRecords (Sum per 5 Minutes) / 300 approaches a percentage of RecordsPerSecondLimit.
IncomingPutRequests (Sum per 5 Minutes) / 300 approaches a percentage of PutRequestsPerSecondLimit.

Another metric for which we recommend an alarm is ThrottledRecords.


cmd/objdump: x86 disassembler does not recognize PDEPQ

What version of Go are you using (go version)?
go version go1.10.2 darwin/amd64

Does this issue reproduce with the latest release?
Yes, confirmed on 1.9.2 and 1.10.2. Not tested on master.
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/michaelmcloughlin/Library/Caches/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/michaelmcloughlin/gocode"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.10.2/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.10.2/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/p5/84p384bs42v7pbgfx0db9gq80000gn/T/go-build505202882=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
Compiled package with assembly code using PDEPQ. Viewed resulting assembly with go tool objdump.
Gist https://gist.github.com/mmcloughlin/b5bf1bcc7f31222ff2bc510f2777cd79 is a minimal example.
What did you expect to see?
Expect go tool objdump to show the PDEPQ instruction.
What did you see instead?
Output from objdump.sh script is as follows. The objdump tool does not recognize PDEPQ, and instead parses it as a sequence of instructions. Note that Apple's LLVM objdump correctly identifies the instruction.
+ go version
go version go1.10.2 darwin/amd64
+ go test -c
+ go tool objdump -s bmi.PDep bmi.test
TEXT github.com/mmcloughlin/bmi.PDep(SB) /Users/michaelmcloughlin/gocode/src/github.com/mmcloughlin/bmi/pdep.s
  pdep.s:7		0x10e7860		4c8b442408		MOVQ 0x8(SP), R8
  pdep.s:8		0x10e7865		4c8b4c2410		MOVQ 0x10(SP), R9
  pdep.s:10		0x10e786a		c442b3f5		CMC
  pdep.s:10		0x10e786e		d04c8954		RORB $0x1, 0x54(CX)(CX*4)
  pdep.s:12		0x10e7872		2418			ANDL $0x18, AL
  pdep.s:13		0x10e7874		c3			RET
  :-1			0x10e7875		cc			INT $0x3
  :-1			0x10e7876		cc			INT $0x3
  :-1			0x10e7877		cc			INT $0x3
  :-1			0x10e7878		cc			INT $0x3
  :-1			0x10e7879		cc			INT $0x3
  :-1			0x10e787a		cc			INT $0x3
  :-1			0x10e787b		cc			INT $0x3
  :-1			0x10e787c		cc			INT $0x3
  :-1			0x10e787d		cc			INT $0x3
  :-1			0x10e787e		cc			INT $0x3
  :-1			0x10e787f		cc			INT $0x3
+ objdump -disassemble-all bmi.test
+ grep -A 4 bmi.PDep:
github.com/mmcloughlin/bmi.PDep:
 10e7860:	4c 8b 44 24 08 	movq	8(%rsp), %r8
 10e7865:	4c 8b 4c 24 10 	movq	16(%rsp), %r9
 10e786a:	c4 42 b3 f5 d0 	pdepq	%r8, %r9, %r10
 10e786f:	4c 89 54 24 18 	movq	%r10, 24(%rsp)

#23386 is potentially linked. @Quasilyte suggested in a comment that the disassembler needs to be updated according to the latest x86.csv. From my limited digging into this, it does seem it could just be a matter of some instruction tables getting out of sync.

@mmcloughlin, that's my understanding that it's better to re-generate disassembler than to manually fix all issues (there are potentially a lots of them). It's possible to patch it, but decoder does not understand, for example, all recently added AVX-512 instructions, so it's not a matter of dozens, but hundreds of instructions.
The main problem is that updated x86.csv generator is on halt until some format questions are resolved. The encoder tables (for assembler) are generated from XED tables directly right now. It is possible to generate decoder tables from that too, but this would require discussion as well.

Thank you for the detailed reply. I'd agree that an automated solution to this is preferable.
I'm interested in learning more and helping out, but it seems that contributing in this area is non-trivial?


Upgrade @typescript-eslint packages to v8.7.0

Override failing test not related to this change:
/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-console"


#4338 keybindings to insert new section after, when changed/added dirty

#4376 raise/lower section should mark notebook as dirty
#4338 cmd-alt 1-4 to insert-after

this looks good except i find the cmd-alt-1 impossible to reach with my fingers.
any other ideas?
i am inclined to use cmd-shift-1 and 2 despite the fact that 3 and 4 are taken.
the smaller sections can either be reached with following cmd-< or we can go with 7 and 8 or something.

This is a good idea, main sections will be available with shortcut, but smaller ones you have to lower the level automatically.