New version: Turing v0.23.4

Registering package: Turing
Repository: https://github.com/TuringLang/Turing.jl
Created by: @torfjelde
Version: v0.23.4
Commit: 99a1d23333d852fdb1485457444181a94c2a52a0
Reviewed by: @torfjelde
Reference: https://github.com/TuringLang/Turing.jl/commit/99a1d23333d852fdb1485457444181a94c2a52a0#commitcomment-96499605
Description: Bayesian inference with probabilistic programming.

nvm

yeah dont'


Dump stacktrace to file

When an error occurs, users don't always have --stacktrace enabled, which makes debugging some problems hard. They can rerun the build with the option enabled, but this takes time and effort (as opposed to running a clean build), and it doesn't work for transitive errors.
We could dump the stacktrace to a file, even when --stacktrace is not enabled, similar to hs_err_pidXXX.log files generated by the JVM. The file would be useful when reporting problems on the forums, too.

Note that if you have build scans enabled then you can look there to see the stacktrace. Even if you didn't publish the scan for the failing build you can publish the scan afterwards with buildScanPublishPrevious.

I think such a feature would really help with Gradle development. Especially when the exception is hard to reproduce.


androidenv/ndk-bundle: fix auto-patching and mandate its success.

Description of changes
I'm not sure what exactly happened here, AFAICT the NDK used to have lib64 directories but upstream has since switched to only lib?
(It's possible older NDK versions still use lib64 and both directories should be handled? I only tested with platformVersions = [ "30" ];, which used to work a few months ago).
Simply changing lib64 to lib isn't enough though, because lib64 used to signal host-only, but lib is used in many more places in the NDK, so the patching gets overzealous and tries to patch Android .sos.
With the changes here I can use cargo-apk again (specifically this workflow), but I honestly have no idea if what I did breaks parts of the NDK I would never think to check.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

FYI may want to rebase against https://github.com/NixOS/nixpkgs/pull/278658


Ability for custom hoist riggings

Folks will probably have a need for creating custom hoist riggings that don't need to be merged upstream. Could we have a dedicated directory that bowline can search for custom hoists? related: #43

I believe 38520f8 achieves what we want here. One can add riggings to any path on their system with riggings external to the bowline repo. The path could also be a set of riggings tacked by another git repo.
Not closing this issue yet as this still needs to be documented in the readme.

Quick how-to example that needs to be documented yet:
cp .bowline/config.example .bowline/config
mkdir -p ~/bowline/riggings/foo

cat << EOF > ~/bowline/riggings/foo/foo.hoist
#!/usr/bin/env bash
echo "# Installing foo bar"
EOF

hoist

the output of that would be this:
 » hoist
Usage: hoist [rigging]

Available Bowline riggings:
behat  codeception  devtools  drupal-core-dev  phpunit

Available local riggings (in /home/dave/bowline/riggings):
foo

Note: if there are name conflicts, the local riggings will be used.

 » hoist foo
# Installing foo bar


fix: add apiservicedefinitions for rollouts API [1.10]

What type of PR is this?

/kind bug

What does this PR do / why we need it:

Adds the missing apiservicedefinitions for Argo Rollouts in the CSV.

Have you updated the necessary documentation?
NA

/lgtm
/approve


File input - even default demo does not work on IE 11

http://materializecss.com/forms.html - File Button or the action does not work on IE

In which release was it fixed ? It is still not working on the demo page.

This solution is working in IE11, I didn't test it in older versions
body.ie .file-field input[type=file] {
    height: 100%;
    text-indent: -9999999em;
    transition: none;
}


Understanding OSWAP Top 10 Vulnerabilities

We ask that you please be patient as our team works through approving and publishing all articles/tutorials in a timely manner. Allow 1-3 days for a topic to be reviewed and/or approved - allow 3-7 days for an articles to be reviewed and/or published.
Be sure to visit our Resources Page for tools, resources, and example articles to go over.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
NOTE: We tend to stray away or tend not to publish reviews/comparisons of commercial product offerings.
We're looking for the first 2-3 paragraphs of the article that appropriately summarize what your article will be about.
Proposed title of article
UNDERSTANDING OWASP TOP 10 VULNERABILITIES
Introduction paragraph (2-3 paragraphs):
The OWASP which is the Open Web Application Security Project in full is a global non-profit project that tries to equip users across different spectrums, training them about risks and vulnerabilities related to web application security.
OWASP brings together a diverse and rich group of professionals, allowing each individual to volunteer and participate in the creation of a knowledge base.
OWASP releases, after every few years, a list of commonly exploited web application vulnerabilities that hackers exploit. The risks are ranked based on the level of risk. Additionally, recommendations are made to help mitigate the addressed risks.
Key takeaways:

To act as awareness for organizations and professionals to help them understand the level of their application security
To help organizations to measure their security posture against the top 10 vulnerabilities.
To equip professionals to better handle the risks and vulnerabilities identified and mitigate them.

References:
https://owasp.org/www-project-top-ten/
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

@lucymkiiru
Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

Hello,
Just a clarification, it should be OWASP instead of OSWAP

Thank you for submitting your topic. @lucymkiiru
After some careful consideration, it struck us that this topic may be a bit over-saturated throughout other blog sites and official documentation.
We believe this is the best way for students to build a great portfolio (for potential employers) is by building what does not exist and what can provide the most value.
Please feel free to suggest an alternate topic to explore. 🚀


Flag variant behaviour

I'm looking (again) at 13529.p1 family from SFARI in ATP7B.

Selecting/deselecting "Flag variant", "Remove flag" causes the data to be reloaded. Also, focus is lost from the selected variant, so while you still see the data pertaining to the variant, you can no longer see which variant is selected (either in the table or the proband card).

Should be put the flag as the last row in the table? It is a little confusing to flag a variant, everything is reloaded, and the table is resorted and the variant you flagged has now moved over to the left (as the flag is the highest variable in the ranking). This gives the impression that gene flagged the wrong variant.

The table isn't always refreshed, so you can remove a flag, but the flag remains. So you end up with a flagged variant that also has the option to be flagged (not unflagged). You can replicate as follows:

a) Open 13529.p1 family from SSC in ATP7B
b) Select variant 15. Flag it.
c) Select variant 15. Flag it. (Variant 15 is now new - see point 2).
d) Select variant 9 - should be flagged. Remove flag. Removed it is not.

PeDante strikes again! I feel like this relates me to Dante.

So, you like your moniker, huh?  I just thought added the e made you sound even more sophisticated.  Nice touch, huh?
I'm working on this bug right now.  I think I'm then one in the circle of hell, not you. ;-)

I don't think it's an unreasonable argument that the flags are important to sort on first. Disorienting is the right word! Looks to me like:

FIXED: After flagging a variant, focus on that variant is now retained.

The flag/unflag option works correctly.

The whole page still refreshes after flagging a variant. I don't know if this is possible, but if on flagging a variant, the variant cards did not reload, and as the table refreshed, moving the variant to its new position, we had a message pop up over the table stating that it was resorting, or something like that? I initially thought gene was flagging the wrong variant (I thought it just kept flagging the variant next to the red flagged variants) , so I think this will trip people up if they don't have something showing that the variant they just flagged moved. I don't know what would make sense, or is technically reasonable though!

You know what would be cool?  This matrix is actually a D3 chart, so I should be able to use transitions.  PeDANT strikes again!


Complicated OSM building doesn't draw at zoom 19

The SF Ferry Building tower will draw at zoom 18, but fails at zoom 19.
Is this related to building outlines not drawing in general? But why does part of the tower draw?
19/37.79545/-122.39364
z18:

z19:

The building texture is rendering, but not the outlines?

I think your last guess is right – all building outlines seem to disappear
at z20:
http://tangrams.github.io/bubble-wrap/#20/37.79406/-122.39696
On Tue, May 10, 2016 at 2:47 PM, Nathaniel V. KELSO <
<EMAIL_ADDRESS>wrote:

The building texture is rendering, but not the outlines?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tangrams/tangram/issues/307#issuecomment-218252878,
or mute the thread
https://github.com/notifications/unsubscribe/AAcEwq_MYrFQ70_kHGpL1kIEHD7Pw8ORks5qANLIgaJpZM4IbZPQ
.

I have to confirm but I think it is this issue: https://github.com/tangrams/tangram/issues/267
The lines are thin enough that they collapse at z20. This can be verified by increasing the outline width to see if they draw. We started seeing this frequently when we switched to z16 tile overzooming, since the data is being scaled up by many more factors now.

I've confirmed my hypothesis and was able to hack together a quick fix, but would like to spend some more time thinking about the best way to address. Will update #267 and here.

I agree this is a dup, closing this in favor of #267.


Arm64 changes for universal package version 236

Task name: UniversalPackage
Description: Changes related to arm64
Documentation changes required: (Y/N) N
Added unit tests: (Y/N) N
Attached related issue: (Y/N) Issue is in sprint board
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected

/azp run

/azp run

/azp run


Can't open a channel using Eclair Mobile (Static Remote Key issue?)

Hi LND team,
I am running LND v0.12.1-beta on my Umbrel node.  Now I am trying to open a channel from my Eclair Mobile wallet and the response is: "Failed to open channel: incompatible features"   according to other Eclair users this is due to the Static Remote Key feature required on LND 0.12.0 - anyway I can change this setting to progress with the channel opening using Eclair?
Thanks in advance

Static remote key makes channels safer as you don't need a random value from the other side to recover your funds if they force close. You'll have to ask the eclair devs if/when they'll be adding the feature. I think maybe the Phoenix wallet supports it, but Eclair mobile itself doesn't.

Thanks, the benefits of the setting make sense, however would it be possible to change this if the user wanted to?

Static remote key makes channels safer as you don't need a random value from the other side to recover your funds if they force close. You'll have to ask the eclair devs if/when they'll be adding the feature. I think maybe the Phoenix wallet supports it, but Eclair mobile itself doesn't.

Thanks, the benefits of the setting make sense, however would it be possible to change this if the user wanted to?


Plugin conflicts/debugging

Thanks for making this - from the screenshots, it looks super useful!
I'm wondering if there are any possible conflicts between this and other LSP plugins (e.g. lspsaga, lspkind, lsp-status, etc.). I have (I think) followed the setup instructions correctly, but the "documentation" I get (with nvim-compe) does not match the screenshots on this repo, so something is clearly wrong.
What I get looks something like:

So: do you know of any "gotchas" that might override or prevent lua-dev from providing its documentation as expected?

Are you on windows by any chance? Haven't tested it there...

Sure:

I'm on Linux
Neovim version: NVIM v0.5.0-dev+1339-g5d9c56012 (with LuaJIT)
I do use packer, yes.

Results of luadev.setup:
{
  cmd = { "lua-language-server" },
  on_new_config = <function 1>,
  settings = {
    Lua = {
      awakened = {
        cat = true,
        <metatable> = <1>{
          __tostring = <function 2>
        }
      },
      diagnostics = {
        globals = { "vim" },
        <metatable> = <table 1>
      },
      runtime = {
        path = { "./?.lua", "/usr/share/luajit-2.0.5/?.lua", "/usr/local/share/lua/5.1/?.lua", "/usr/local/share/lua/5.1/?/init.lua", "/usr/share/lua/5.1/?.l
ua", "/usr/share/lua/5.1/?/init.lua", "lua/?.lua", "lua/?/init.lua" },
        version = "LuaJIT",
        <metatable> = <table 1>
      },
      telemetry = {
        enable = false,
        <metatable> = <table 1>
      },
      workspace = {
        library = {},
        maxPreload = 2000,
        preloadFileSize = 150,
        <metatable> = <table 1>
      },
      <metatable> = <table 1>
    },
    <metatable> = <table 1>
  }
}

Later in my setup, I modify that table by adding an on_attach and a capabilities table.
My full setup is here:

LSP stuff: https://github.com/wbthomason/dotfiles/blob/linux/neovim/.config/nvim/lua/config/lsp.lua
compe: https://github.com/wbthomason/dotfiles/blob/linux/neovim/.config/nvim/lua/config/compe.lua

What does :lua print(vim.inspect(require("lua-dev.sumneko").library())) give?

That gets me:
E5108: Error executing lua ...e/pack/packer/start/lua-dev.nvim/lua/lua-dev/sumneko.lua:9: table index is nil

Looking into that error, it seems that in lua-dev.sumneko.types, the problem is:
f = "/home/wil/.local/share/nvim/site/pack/packer/start/lua-dev.nvim/lua/lua-dev/s
umneko.lua"
vim.loop.fs_realpath(f .. '/../../../types') = nil ENOTDIR: not a directory: /home/wil/.local/share/nvim/site/pack/packer/sta
rt/lua-dev.nvim/lua/lua-dev/sumneko.lua/../../../types ENOTDIR

Thank you for debugging this! I just pushed a change with your suggestion.
The code that was there before actually started with a filename to go up, which for some reason works on macos, but probably not on your distro.
So I did something like lua/foo.lua/../../..
Your approach is definitely better :)

Thanks! Everything seems to work for me now! Thanks again for the plugin; this will make my life substantially easier.


Mapping type covariant in key

Is a possible implementation of a Mapping-like type that is covariant in the key as discussed here being considered?
Specifically, a mapping type whose __getitem__ has a key typed object.
The linked thread was referring to this package, so I'd thought I'd ask here. Thanks!

Sorry, returning to this after some reading; I think I must have gotten my thoughts crossed between the very early discussions (https://github.com/python/typing/issues/445) about making Mapping itself covariant in its key (for which there's nothing to be done), and the later discussions about offering Mapping supertypes that do not define __getitem__ / get, etc. I originally linked to, which could be relevant for this repo.
Apologies for the imprecise initial post!


Yosys Error. Unable to access 'https://github.com/YosysHQ/abc/': Could not resolve host: github.com

Yosys Error. Unable to access 'https://github.com/YosysHQ/abc/': Could not resolve host: github.com
[100%] Building abc/abc-bb64142
Pulling ABC from https://github.com/YosysHQ/abc:

test -d abc
git clone https://github.com/YosysHQ/abc abc
Cloning into 'abc'...
fatal: unable to access 'https://github.com/YosysHQ/abc/': Could not resolve host: github.com
cd abc
/bin/sh: 7: cd: can't cd to abc
make[5]: *** [Makefile:800: abc/abc-bb64142] Error 2
make[4]: *** [CMakeFiles/yosys.dir/build.make:72: CMakeFiles/yosys] Error 2
make[3]: *** [CMakeFiles/Makefile2:953: CMakeFiles/yosys.dir/all] Error 2
make[2]: *** [Makefile:146: all] Error 2
make[1]: *** [Makefile:76: compile] Error 2
make: *** [Makefile:84: all] Error 2

@ArslanNustian116 Can you provide how to reproduce the error? It looks like an internet issue to me. All the compilation scripts have been intensively tested through our CI system


Review the output when DefaultApiConventions is applied

Tracking item to ensure the swagger output matches expectations. This includes figuring out what we need to do about metadata that's missing - for instance https://github.com/aspnet/Mvc/pull/7889#discussion_r193931460

Verified as part of preview3 verification.


Make parboiled2 an actual module

This solves the problem of being unable to publishLocal and then depend on that when testing http4s.
I was reluctant to do this, because it appears to be another dependency, which is used in negative marketing.  All code in this newly published module is internal and was already in core.  Haters gonna hate.  This just simplifies our build and makes a better story for local development.
Alternatively, I tried ivyXML in addition to pomPostProcess, but I couldn't get it to affect the delivered Ivy file.

I think this one has irritated @ChristopherDavenport a lot, so I'll wait for his feedback, too.


Allow --derivatives to be named

What would you like to see added in fMRIPrep?
In #3252, we started creating DatasetLinks for derivative datasets passed through the --derivatives parameter. However, because there's no easy way to infer what each derivative dataset actually is, we're labeling them as deriv-<index> in the DatasetLinks. I think the DatasetLinks and BIDS URIs throughout the derivatives would be more interpretable if users could label their input derivative datsets.
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
I was thinking something like:
fmriprep ... --derivatives smriprep=/path/to/smriprep

Yes. I believe I actually implemented this in the wrapper but not the actual cli. I agree this is where we should go.


Allow local .htaccess settings

The current webserver does not allow overrides, which currently prevents me from testing some redirects. It's not really a big issue for me at the moment, but I think the proper way to go would be to use the .htaccess generated by wordpress in /vagrant/wordpress instead of hard-coding the data in the apache config.

patches welcomed! :smiley:

I'll look into it when I find the time.

@voidus do you have a specific example? I can take a stab at this...


Increase psalm level to 2

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues
-

👍


Update composer.lock

twig/twig : 1.44.7

Questions
Answers

Description?
Upgrade twig/twig to 1.44.7

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?

Sponsor company

How to test?
Everything should work as expected this is just a dependency minor update. Can you please verify if HTML pages of the upgrade software are displayed correctly?

Thank you @ValentinGratz !


Provide some mechanism for refreshing changing projects

This issue is similar to issue 36.  The problem is that I'll be working on something in say the snap package that involves unreleased code from the rest of the snap framework.  In the snap project directory,  I will have done add-source for local copies of snap-core, snap-server, heist, etc.  Then I'll modify something in one of those projects and I want the changes to show up when I build the snap project.  I don't want to delete the whole sandbox, because then the build will take forever.  My usual practice is to dig inside the sandbox directory, specifically delete files having to do with the changed project, then issue add-source for that project again.
The reason I'm opening a new issue instead of just commenting on issue 36 is because being warned about it isn't really a big problem for me.  I usually know when something changed, and I want to refresh it.  Ideally the add-source action would just detect changes and do the right thing.  I realize that could be difficult.  A simpler solution that would be completely acceptable would be to add a "-f" flag to the add-source action that would force the reload of said project.
This is a big issue for me.  I run into this all the time with the Snap framework and other proprietary projects I'm involved with that use multiple projects not on hackage.  Improving the workflow here would be a big win.

why do you need to delete anything? doesn't add-source properly overwrite existing added packages?
I sent a pull request for #44 which adds an add-source-list command which may make your workflow a little better.
Have you tried the workaround mentioned in the SO answer?

No, it doesn't overwrite...at least not when I've ever tried it.

I just knocked up the following bash script which emulates the "add-source -f" behaviour mentioned in the OP: https://gist.github.com/1557244
The assumption is that you have some cabal-dev sandbox directory (SANDBOX_DIR in the script), and in there you have a directory sdist which contains sdist tarballs.
Note that this script assumes you're using GHC and build with the currently installed version on your PATH, also its behaviour is undefined if you have multiple versions of a package in sdist installed in your sandbox.
Feel free to fork and improve.


WSL Toolbox <IP_ADDRESS> not launching

If you experience issues with launching WSL Toolbox <IP_ADDRESS> i suggest you downgrade for now;
winget install FalconNL93.WslToolbox --version <IP_ADDRESS> or https://github.com/FalconNL93/WslToolbox/releases/download/<IP_ADDRESS>/wsltoolbox_<IP_ADDRESS>_x64_setup.exe
I will try to fix this issue asap.

Only occurs when there is no [wsl2] section in %USERPROFILE%\.wslconfig.
Workaround is to add [wsl2] section to %USERPROFILE%\.wslconfig (create file if it doesnt exist) or update to <IP_ADDRESS>:
https://github.com/FalconNL93/WslToolbox/releases/download/<IP_ADDRESS>/wsltoolbox_<IP_ADDRESS>_x64_setup.exe
Fixed in <IP_ADDRESS>.


Display endpoint list

Change overview
Display a list of endpoints on cluster-interaction screen. Now it is hard-coded to be 0 and 1. The endpoint list is implemented using recycler view. Also implemented customized onClickListener to go to cluster detail page after clicking on the endpoint list item.
Testing
manually tested.

@chrisdecenzo @Damian-Nordic @jelderton @jmartinez-silabs @saurabhst can you help review? Thanks!


Null check in IncrementalIndexAdapter.getDimValueLookup()

relates to #2287

:+1:
To next reviewer: much easier to see change if you do https://github.com/druid-io/druid/pull/2288/files?w=1

:+1:


Feat: Storage Support with SD Card #570

Hello, is this PR ready? We are trying to test this, it compiles, but the disk access fails.

Merged, Kevin's but lmk if there's something here that should be merged that is not on main, thanks

@josancamon19 sorry been down with covid for 2-3 weeks. I'll review Kevin's PR and adjust if required. Worried about buffer memory with speaker and other devices but will check


[Feature] Update boilerplate Angular app for Schematic

What projects is this feature for?
Schematic
Description
Since I generated the Angular app schematic-app, recent versions of Angular introduced QoL (quality of life) improvement, including the adoption of standalone components and better server-side rendering, which is required for optimal SEO and generation of rich cards on social media sites.
The goal of this ticket to to create a new project schematic-web-app. There are at least two motivations for doing this now:

Provide the FAIR Data team / @linglp with an up-to-date Angular app template as part of their review of Angular vs. React
The Web Engineering team / Lawrence (@sagely1) decided to move the Agora Angular app to Sage Monorepo. This ticket can serve as a reference for the creation of Angular apps in Sage Monorepo, starting with observations that Lawrence and I made when starting the migration of Agora to Sage Monorepo.

cc: @linglp @sagely1
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

This ticket is no longer needed because I'm in the process of removing the existing Schematic web app code (with the permission of Schematic owner). These two components (schematic-app and schematic-api-client-angular) can be easily recreated if needed.


Use dimension separator in arrays instead of FSStore

Move all usage of dimension_separator from Zarr stores to individual Zarr arrays, in order to avoid .zmetadata dimension separator bug

Closes #42

Codecov Report

Merging #52 (bde1944) into main (6f0372c) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #52   +/-   ##
=======================================
  Coverage   80.85%   80.85%
=======================================
  Files          43       43
  Lines        1583     1583
  Branches      203      203
=======================================
  Hits         1280     1280
  Misses        267      267
  Partials       36       36

Impacted Files
Coverage Δ

src/mdio/api/io_utils.py
61.53% <ø> (ø)

src/mdio/converters/segy.py
76.56% <ø> (ø)

src/mdio/segy/blocked_io.py
90.16% <ø> (ø)

tests/unit/conftest.py
100.00% <100.00%> (ø)

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

thanks @sanath-2024


Better document usage of actions-mn/*

Right now they are not well documented in actions-mn.
We have two actions:

actions-mn/setup@v2
actions-mn/cli/site-gen@main

We need better documentation:

need explanation if there are any options (e.g. with:)
how to set path of metanorma.yml for site generation (actions-mn/cli/site-gen@main)
where is the site generated, there must be some options for site-get

This originates from #494 and #505

@ronaldtse I have added page https://www.metanorma.org/install/cicd/
But I don't think it makes sense to duplicate inputs documentation because all descriptions already available in action description
Let me know if anything else should be added


Fixes for HTTP routing

Addressed the following HTTP routing capabilities:

multiple HTTP ports in a service
domain names can be "name" or "name.namespace"
port is a part of the host name

This change is

The current model contains just enough information to be able to configure proxies on Kubernetes. I'd argue the model should be extended if needed to support other platforms. We clearly require a naming scheme to address service instances. The name has to include:

host name (split into name and namespace, but I'm ok collapsing it back into DNS name)
port name (I'm ok following DNS SRV convention)
service tag/cluster, which remains unclear.

Reviewed 9 of 9 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

Comments from Reviewable

Mesos supports the concept of labels with names for services. Currebt mesos version has support for pods as well. So I don't think the current model is kubernetes specific unless the platform specific abstractions have leaked out. Mesos has dns srv as well.
We don't need a host name. Just the IP and ports.  It would be good to periodically check against one non kubernetes platform (mesos) to make sure that we are not over specializing for kubernetes.


it would be nice if the metaCreator was also the identity function if not specified

I'd also like metaCreator will be identity function if not specified, since sometimes I want to pass some data as meta, not payload.
Finally I found identity function which provided by lodash will only return first argument it receives, so I think keep metaCreator with no default function is better.
Here is my code.
// treat 2nd argument as `meta` field
export const success = createAction(REQUEST_COMPELTED, null, (...args) => args[1]);

// I used redux-saga and this line likes ajax successful callback.
// with the action I created with redux-actions above, `data`
// will be `payload`, `{ whatever }` will be `meta`.
yield put(resource.success(data, { whatever }));


Updates

Move faq to https://docs.avax.network/v1.0/en/faq
Move quickstart to https://docs.avax.network/v1.0/en/quickstart
Minor bug fixes / improvements


Fix image overflow when media screen is smaller than 980px

When the screen width is too small (e.g. view in mobile device), some large image may overflow.
To fix this, I make the img becomes max-width: 100%; when media screen is below 992px. 992px is Medium Devices Desktops in Bootstrap. Hopefully only 1 line of css for this break-point is not too rare.

p.s. Put the line in max-width: 480px is not enough. And, for medium devices, fixing a certain width for images may be too small. That's why I make it 100%.

Thanks @Edditoria!


Chat progress messages are reported multiple times to screenreader

Testing #210661

Send a request to @workspace
This participant shows 3 progress messages
The screen reader reads them but they get read multiple times in random order

I'm not scrolling or anything, this is just what happens as the response renders normally. I'm assuming this is due to progress messages being re-rendered, and the screenreader hooking into the rendering flow

@roblourens I cannot reproduce, I am only seeing the progress messages once and they occur when I expect them to. Can you provide a gif?

They appear once, it's just that the screenreader reads them multiple times

I don't see the screen reader reading them multiple times. Can you make a gif?

It reads them once as they come in, and a second time when it reads the content of the response when the response is done. Pushing a change to not consider the progress message part of the 'content', which I think is correct since the progress messages disappear from the view once more content has loaded.
This also fixes the fact that the progress messages appear when I Copy a chat response (never noticed that before)


681 show disabled arrows

Resolves #681

The new functionality is behind a config flag (e.g. showDisabledArrows ) set to false so existing users' experience won't be affected. I'm not sure how to put in a PR for the documentation.

Thanks @imjonrourke for the contribution.
I don't think an option is necessary however.
Just add the disabled class and hide the arrows via display:none by default.
If you wanna show the arrows for whatever reason, you can override this with custom CSS.

Updated implementation and tests per code review.

Great work, thanks all for contributing :+1:

Thanks for maintaining flatpickr! Do you publish on a schedule?

@Alfredo-Delgado whenever I get free time. the next release is highly anticipated, but with the plethora of recent changes additional testing is necessary to prevent bugs from creeping into users' production.
If I gave an ETA it would be within the next 3-5 days


Playbooks cannot be saved. The request content is not valid and could not be deserialized: 'Could not find member 'defaultValue' on object of type 'FlowTemplateParameter'.

Logic Apps cannot be created from the json files available in the Playbooks folder.
To Reproduce

Go to 'https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Playbooks/Block-AADUser.json' and copy the content.
Paste into a new logic app.
Click save.
See error:
Failed to save logic app 'APPNAMEHERE'. The request content is not valid and could not be deserialized: 'Could not find member 'defaultValue' on object of type 'FlowTemplateParameter'. Path 'properties.parameters.PlaybookName.defaultValue', line 1, position 968.'.

Expected behavior
Successful save.
Desktop (please complete the following information):

OS: Win10
Browser: Chrome
Version:  Up to date.

Thanks for raising @Pagni  - this Playbook was created by @dicolanl - perhaps he can shed some light on this issue.

Hi @petebryan,
Thanks for following up.
This is user error by me. I thought I could simply create a blank logic app from inside Sentinel and use the code.
Should have paid more attention to the Playbooks README.
Closing off.


Some of the test cases have conditional PICS checks for each of the steps , need YAML support for this

Look at this example in the TC-DM-1.1 test case :

We need a way to conditionally execute certain steps based on the value , need a way in YAML to implement this as well

https://github.com/project-chip/connectedhomeip/pull/11322

PR Merged

Initial PR is most likely not sufficient for the Test Harness.  Will work with @vivien-apple to design something that works for both CI and Test Harness.

Should have been fixed by #11729. Feel free to reopen if that still not enough.


What is the difference between Easyphoto and kohya?

Is it another tool for Lora training?
If you want to swap face, you only need one image to use sd-roop and sd-reactor.
If you use 5-10 images, you can use kohya to train Lora model, so what are the advantages of using easyphoto?

Welcome to try EasyPhoto and compare the result with  sd-roop/sd-reactor.
Otherways, you could also try to train a LoRA by kohya.
I believe you would find the answer at the end.

Thanks for this question：
Our project is dedicated to using stablediffusion technology to create more realistic and visually appealing image editing techniques. Initially, we focused on portrait editing, and Lora is a part of the technology we've been working on. We have put significant effort into refining this aspect of the technology, but it also encompasses a wide range of other AI algorithms and techniques that come together to produce the final result. We appreciate your ongoing interest.
CN：我们的项目致力于使用stablediffusion技术打造更逼真，美观的图像编辑技术，人像是我们最初选择的方向，Lora是我们涉及的一部分技术，我们着重打磨了这部分技术，但也还包括大量的其他AI算法和技术，共同呈现最后的效果，欢迎您的持续关注。


PokeApiNet.Models.Effects is missing property short_effect

In Common.cs, the class Effects is missing a field short_effect. The Effects class is used in item, move, and ability resources; all of these resources have this field in the effect_entries object. See sample item, sample move, and sample ability. Backing code for item, move, and ability.
This field is a string value that is a shorter version of the string in the effect property.

Thats why there is also a PokeApiNet.Models.VerboseEffect class

Fixed in #12


MONDO:0009641

Hi,
I see that:
MONDO:0009641 is obsolete (replaced by: MONDO:0100294) - skipping annotation for SPAC1556.02c / mitochondrial_complex_ii_deficiency
but I find no tracker issue and Monarch is not yet updated, so I can't check that the replacement makes sense, i.e  it isn't a duplicate etc.
Is it possible to create tickets for obsoletion replacements?

Hi @ValWood - this is the tracker issue:
https://github.com/monarch-initiative/mondo/issues/2758
This term was split into the more specific class, 'mitochondrial complex II deficiency, nuclear type 1', the comment says: Created new class that is child of OMIMPS.
We do link Gitub issues to obsoleted terms, you can see this and the comment in OLS:
https://www.ebi.ac.uk/ols/ontologies/mondo/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FMONDO_0009641
Where were you looking?
We may not have GitHub issues linked to older obsoleted terms, but this it is part of our workflow now.
I will close but please reopen if you have further questions.


Touch runtime detection fields if runtime selection succeedes

Fixes
https://issues.redhat.com/browse/RHTAPBUGS-479

Description
Formik bug workaround suddenly stopped working, updated to use https://github.com/jaredpalmer/formik/issues/2083#issuecomment-639962222

Type of change

[ ] Feature
[x] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Screen shots / Gifs for design review
https://github.com/openshift/hac-dev/assets/20013884/64fc7e7e-ca93-4e25-b8f6-bd631c149b15

How to test or reproduce?
(see ticket)

Browser conformance:

[ ] Chrome
[x] Firefox
[ ] Safari
[ ] Edge

/retest

/cc @karthikjeeyar

/lgtm

/cc @rohitkrai03

/retest


chore: upgrade to Angular 8

changes are included in https://github.com/NativeScript/nativescript-imagepicker/pull/272


(PUP-10471) Use symbols for implementation names

Use symbols for names of runtime implementations, so that callers don't need to
allocate a string (puppet doesn't enforce frozen string literals yet).

jenkins please test this with servertest

CLA signed by all contributors.

There are 2 Travis checks, and the one from 18+ hours ago is still showing as queued.. I'm going to close this and reopen a new PR.


[WIP] Allow for other Embedded ConfigurationScriptSources

Currently the bulk of the logic for syncing configuration_script_sources from git_repositories lives in EmbeddedAnsible.  This makes it impractical to share this with other Embedded managers.
This moves the code out of EmbeddedAnsible and up into EmbeddedAutomationManager

Hard to tell in the diff, but is this s a straight move to the base class without changes?

The majority of this has been implemented already, I'm going to close this and tackle the refactoring in a follow-up


Support for Ubuntu

Please explain how should I compile this app in ubuntu, with all the necessary dependencies. Or if you're planning to release a deb. We have a project called Pacstall. We can serve your deb via there. Or, we'll compile the app from source and serve it in our Pacstall.

related to #108 . I have some basic packaging lying around, once debian bookworm is released I might package it.

I have tried to make a snap for it. But, it fails with some gtk4 issues, can you help me, if I give you the logs?


Having Pcons enabled after the new update crashes the game

After the new update using the pcons feature to automatically get ready crashes the game. Even if this is disabled it still crashes if an explorable area is loaded.

The same thing is happening to a lot of toolbox features as say on discord so a fix should be released soon

Fixed in 4.4


[v2.8] KDM Update for K8s July 2024 patch release

KDM Updates
TO BE RELEASED: OOB after v2.8.5

New Kubernetes Version
Min Rancher Version
Min RKE Version

1.28.12-rancher1-1
2.8.3-patch0
1.5.0-rc0

1.27.16-rancher1-1
2.8.0-patch0
1.5.0-rc0

Rancher System Images & Add-ons
Note: Please update system images and add-ons in the template as needed.
TBD
Developer Changelog

Add templates for new K8s versions. If a template that hasn't been released yet already exists, update it in place.
Update the default K8s version, and add or update the version information (MinRancherVersion and MinRKEVersion) in k8s_version_info.go for new K8s versions if needed (Use table from above).
Confirm versions for system images, add-on templates are correct using versioning reference table from below (expand details to view the table). Update the table if new versions are introduced.
Confirm add-on template version constraints in template.go are correct using versioning reference table from below (expand details to view the table). Update the table if needed.

Versioning Reference

Expand for system images & add-on templates versioning table

Note: Truncated repository names with a * indicates there are multiple images with that prefix. All repository names that match a truncated prefix should be checked for the same version stated in the table.
For example: rancher/weave-* matches weaveworks/weave-kube and weaveworks/weave-npc, and they should both have the same version.
v1.28.10-rancher1-1

Repository
Tag

rancher/mirrored-coreos-etcd
v3.5.10

rancher/hyperkube
v1.28.10-rancher1

rancher/rke-tools
v0.1.96

rancher/mirrored-k8s-dns-*
1.22.28

rancher/mirrored-cluster-proportional-autoscaler
1.8.9

rancher/flannel-cni
v0.3.0-rancher9

rancher/mirrored-flannel-flannel
v0.24.2

rancher/mirrored-calico-*
v3.27.0

weaveworks/weave-*
2.8.1

noiro/* (All ACI images)
<IP_ADDRESS>.81c2369

rancher/mirrored-pause
3.7

rancher/nginx-ingress-controller
nginx-1.9.6-rancher1

rancher/mirrored-nginx-ingress-controller-defaultbackend
1.5-rancher1

rancher/mirrored-jettech-kube-webhook-certgen
v20231226-1a7112e06

rancher/mirrored-metrics-server
v0.7.0

rancher/mirrored-coredns-coredns
1.10.1

rancher/mirrored-cluster-proportional-autoscaler
1.8.9

rancher/mirrored-k8s-dns-node-cache
1.22.28

Add-on Name
Add-on Template Version Constraint

Calico
calicov3261Rancher2

Canal
canalv3261Rancher2

Flannel
flannelv0214

CoreDNS
coreDnsv183Rancher2

KubeDNS
kubeDnsv116

MetricsServer
metricsServerv061

Weave
weavev122

Aci
aciv6032

NginxIngress
nginxIngressv194Rancher1

Nodelocal
nodelocalv121

v1.27.14-rancher1-1

Repository
Tag

rancher/mirrored-coreos-etcd
v3.5.10

rancher/hyperkube
v1.27.14-rancher1

rancher/rke-tools
v0.1.96

rancher/mirrored-k8s-dns-*
1.22.28

rancher/mirrored-cluster-proportional-autoscaler
1.8.9

rancher/flannel-cni
v0.3.0-rancher8

rancher/mirrored-flannel-flannel
v0.21.4

rancher/mirrored-calico-*
v3.26.3

weaveworks/weave-*
2.8.1

noiro/* (All ACI images)
<IP_ADDRESS>.81c2369

rancher/mirrored-pause
3.7

rancher/nginx-ingress-controller
nginx-1.9.4-rancher1

rancher/mirrored-nginx-ingress-controller-defaultbackend
1.5-rancher1

rancher/mirrored-jettech-kube-webhook-certgen
v20231011-8b53cabe0

rancher/mirrored-metrics-server
v0.6.3

rancher/mirrored-coredns-coredns
1.10.1

rancher/mirrored-cluster-proportional-autoscaler
1.8.9

rancher/mirrored-k8s-dns-node-cache
1.22.28

Add-on Name
Add-on Template Version Constraint

Calico
calicov3261Rancher2

Canal
canalv3261Rancher2

Flannel
flannelv0214

CoreDNS
coreDnsv183Rancher2

KubeDNS
kubeDnsv116

MetricsServer
metricsServerv061

Weave
weavev122

Aci
aciv6032

NginxIngress
nginxIngressv194Rancher1

Nodelocal
nodelocalv121

QA validated that provisioning v1.28.12-rancher1-1 and v1.27.16-rancher1-1 was successful along with automated post cluster provisioning checks. Additionally, standalone RKE was successful with RKE v1.5.12-rc1 along with post cluster provisioning checks.


adding build and deploy for target-web, target-node and target-androi…

We should serve those target tools in this project for now until we decide how to better handle the sdkgen outputs

CI is failing


Getting error files not found

Hi,
I followed the instructions you've provided to setup premake scripts for qt.  I run the basic usage example you have provided to test.  However, i'm getting an error that it's unable to files and dlls. I've placed the files into a location where premake5 should be able to pick them up.  I'm using premake 5 with visual studio 2013.
This is the type of error i'm getting.
Error: C:/premake/premake.lua:3: module 'premake-qt/qt.lua' not found:
no field package.preload['premake-qt/qt.lua']
no file '.\premake-qt/qt\lua.lua'
no file 'C:\premake\lua\premake-qt/qt\lua.lua'
no file 'C:\premake\lua\premake-qt/qt\lua\init.lua'
no file 'C:\premake\premake-qt/qt\lua.lua'
no file 'C:\premake\premake-qt/qt\lua\init.lua'
no file '.\premake-qt/qt\lua.dll'
no file 'C:\premake\premake-qt/qt\lua.dll'
no file 'C:\premake\loadall.dll'
no file '.\premake-qt/qt.dll'
no file 'C:\premake\premake-qt/qt.dll'
no file 'C:\premake\loadall.dll'
Thanks,
ccptleu

Hi,
The guide might be a bit outdated, I will check this today, and I'll let you know how to fix this :) (I'm using an embedded version of my script, so I didn't notice that it didn't work anymore, sorry for the inconvenience !)

Hi again,
Well, it seems to work fine. I think that you cloned the premake repository in a wrong place. Here, I did the following :

Download the latest Premake5 binary (http://premake.github.io/download.html) and unzip it.
In the same folder where the Premake5 executable is located, I ran git clone https://github.com/dcourtois/premake-qt.git

And it works. Here is how the folders should look :
YourProject/
      |------ Premake5.exe
      |------ premake-qt/
                    |------ qt.lua
                    |------ ... (the rest of the files of the extension

Hi,
Thanks for your help and prompt response!
I checked out the premake-qt folder to be in the same location where premake5.exe is located.  But i'm still getting the same errors when i run premake5 --file=premake.lua vs2013 from the premake scripts folder on Windows.
I'm using the following folder structure which i think should be fine as long as i'm setting the project location directories correctly in the build scripts.   My other premake scripts (not using qt) also reside in the premake scripts folder structure as well.
My Project
   |--- premake scripts folder
            |---premake5.exe
            |---premake.lua
            |---premake-qt folder
                 |---qt.lua, qtmodules.lua, _preload.lua, _manifest.lua

Hi,
What is the current working directory when you execute premake5.exe (e.g. what folder are you in when running the premake command) ? And are you using a recent version of Premake5 ?
I can't reproduce the problem here. Would you mind creating a zip file of your project (you can remove all the source files, just leave the stuff related to premake without changing the hierarchy) and send it so that I can try to spot the problem ?

Hi again,
I'm using premake5 Alpha 7 version.  Here's an example of the project structure i'd like to use.  The folder contains a master solution with two project files in it (one not using Qt and another using Qt). When running the premake command i'm in the project's premake folder.  The example contains a batch file which you can run from the command prompt to reproduce this issue.
Project.zip

Hi,
Sorry for the delay, I just noticed that you replied and sent a sample ! I reproduced the problem, and it seems to come from the require command syntax.
I don't know why, but in my projects I usually use the syntax that is used in the Readme.md file (that's what I did when I first tried to reproduce your problem) and in your project, it doesn't work.
You can fix this by removing the .lua extension when doing the require :
require( "premake-qt/qt" )

and it should work (at least it did on your project, on my computer :p)

Thanks a lot for your help! Don't know why i didn't catch that earlier. :) I'll close off this issue now.


create favicon + opengraph + startupscreen

Usecase
Upload an image
Creates Open graph startup screen and favicon
Provide Figma file with all the goodies for manual creation
Favicon

[x] Resizes to to faveicon sizes
[x] Ico file how ?

Opengraph default image created

[ ] Fb +
[ ] twitter

Splash screen

[ ] Android
[ ] iOS screen hell
Investigate if the loads is affecting first draw

https://fantinel.dev/fixing-favicons/


fix(config): handle mixed relative and absolute paths

We need to call absolute() to convert a relative path to an absolute path before trying to compare parents, as parents is (per the docs), 'a purely lexical operation'.
Fixes https://github.com/tconbeer/sqlfmt/issues/426.

The failure on Windows was because resolve() can be confusing there (at least, it was to me). I think absolute() is fine for this case - see https://github.com/python/cpython/pull/26153 - so let's see if that makes CI happy.

I'm assuming the coverage failure is because this PR is from a fork?
Error: you must supply a CC_TEST_REPORTER_ID ENV variable or pass it via the -r flag

I'm assuming the coverage failure is because this PR is from a fork?
Error: you must supply a CC_TEST_REPORTER_ID ENV variable or pass it via the -r flag

yes, don't worry about  that one

@smcgivern Thanks so much for contributing!

This turned out to be the wrong solution; click resolves paths before passing them into cli.main, so the rest of the code doesn't need to handle relative paths for files. We just weren't handling the case where there are no common parents. This isn't possible on posix systems, but it is on Windows.

I am on macOS and sqlfmt foo $PWD/foo crashes without something like this, so I'm not sure paths are resolved going in. I mean, you can also try the test here without this change and see if it passes 😃
However, I see what you mean about click. You can set resolve_path (https://click.palletsprojects.com/en/8.1.x/api/#click.Path), but it defaults to off, and it doesn't look like it's set here? https://github.com/tconbeer/sqlfmt/blob/96ed1165b06dffb5673a97771d27ca09075e4158/src/sqlfmt/cli.py#L158


[SPARK-50230][SQL] Added logic to support reading unknown collation name as utf8_binary

What changes were proposed in this pull request?

I propose adding a new SQLConf entry which enables spark to read an invalid collation name as UTF8_BINARY.
Why are the changes needed?

These changes are needed in case when spark needs to read a delta table which has metadata with other convention for naming collations. Instead of failing, when this conf is enabled, spark would return the UTF8_BINARY collation.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

This patch was tested by adding tests in DataTypeSuite.
Was this patch authored or co-authored using generative AI tooling?

No.

@MaxGekk @stefankandic @stevomitric can you please take a look at this PR?

+1, LGTM. Merging to master.
Thank you, @vladanvasi-db and @stefankandic for review.


Docs build fails if tag directive is in the first line of file

Observed in #35

From https://github.com/melissawm/sphinx-tags/pull/35#issuecomment-1407465407:

I think the connected event doesn't need to change after all, it seems specific to parsing rST. If you put tags at the top of a MyST document, it works fine.


Investigate possible unsafety of OwningHandle

See https://github.com/Kimundi/owning-ref-rs/pull/15#issuecomment-262142161

My understanding is that the issue comes from the fake lifetime parameters of the handle. OwningHandle hides the handle value itself, but depending on the implementation of the handle, that is insufficient to prevent the fake lifetime from leaking into safe code. Unfortunately, there is no way to check this in generic code.
On the other hand, there is technically no unsoundness, because the only way to get a fake lifetime parameter in the first place is to perform a pointer deref in the callback passed to OwningHandle::new_with_fn, which requires unsafe code. On the other hand, that's pretty much the intended use case, so realistically, every caller will do so. I think the best option is to add more documentation explaining about how the API is dangerous and the caller is responsible for ensuring that fake lifetime parameters don't leak or aren't used unsafely.
The other place to watch out is ToHandle/ToHandleMut. Currently, the only implementation of ToHandle provided is for RefCell, and it does introduce a fake lifetime. However, my understanding is that the T: 'static bound on the impl prevents it from leaking. I could be missing something, but I don't see any unsafety offhand.
The other issue is that ToHandle is a safe, public trait. However, in order for users to implement it, they would have to perform a pointer deref, which requires unsafe code, so there is technically no unsoundness. Still, I think it might be a good idea to make ToHandle and ToHandleMut into unsafe traits so that people realize that they have to be extremely careful when implementing these traits.

As @Storyyeller points out, the unsafety here is a result of the false lifetime being exposed to the outside world. The H: Deref bound was intended to prevent this by forcing you to reborrow the false lifetime away, but we can defeat that by just adding an extra level of deref. The false lifetime being exposed is very dangerous because borrowck can and will unify it with things that it shouldn't be unified with. Conceptually it's an existential lifetime known only to the OnwningHandle, but unfortunately there is no way to express that in rust yet.
After making that comment, I took some time to ponder this and if it was even possible to make this kind of thing safe at all. Rental was the result of that experimentation, but as can be seen from the code, it involves an absurdly arcane macro and subtle HRTB trickery to achieve it.
To boil it down, the only way to make it safe it to only allow access to the borrowed value within a closure bounded by: for<'a, 'fake> Fn(&'a MyHandle<'fake>), where 'fake is the false lifetime in this case. For a closure to satisfy this trait, it must be callable for any such lifetime, and since the lifetime that will be used is unknown in the context where the closure is created, borrowck can't unify it with anything outside of the closure, except in cases where it would be known to be variance-compatible anyway. Thus it becomes effectively existential for our purposes, and the code inside the closure is safe. Unfortunately, we can't express such a bound generically, since rust lacks HKT/ATC for the time being. This is what the gross macro is for, to construct a new type for each owner/borrow pair with the appropriate trait bounds.
I plan to redesign it as new enabling features land, but for now I can't envision a better way to expose an API like this. If you concede to allowing possible unsafety, though, the situation becomes much more tractable. One way would be to clearly mandate that the false lifetime must NOT appear in the type signature of the Deref target of the borrowed value. I don't think this can be mechanically enforced though. I do it in rental with helper macro that detects the false lifetime token in a type signature and erases it, but I'm not sure if such a think could be expressed with a trait or other static means.

There are some curious cases you can run into because of those faked lifetimes. In particular it permits you to crate code that looks okay but only becomes visible unsafe when you do things somewhere completely different.
In my case I have something that gives access to some mmap'ed or borrowed data. The mmapp'ed version is 'static. As a result of that, if not shielded carefully in a wrapper type you can easily give out borrows with a 'static lifetime instead of the lifetime of self.
I'm not sure what lesson is there to learn but right now I don't have much other options other than using OwnedHandle very carefully and wrapping it in another type that makes sure the exposed API is safe.


Highlight selected and focused photos.

No one recognized that selected and focused photos are not highlighted in the past 5 years? Weird :-)

Just a side note, I sometimes leave the redundant name on types because it helps with clarity between one namespace and another.

There might be a bug in this list (search limited to 500 results, might need to be refined) https://bugzilla.gnome.org/buglist.cgi?cmdtype=runnamed&list_id=92359&namedcmd=f-spot


Proposal: commit composer.lock in components and change travis to build with both locked and updated deps.

I'm experiencing an issue with contributing to the develop branch of zend-mvc; the recent changes in zend-servicemanager are not compatible with the current state of the component yet, and this makes further development troublesome, because I can't even run the tests, even though its latest official build passed (more than 3 months ago).
I think a developer should never find himself being unable to run the build right after a clone & install due to dependency hell.
This wouldn't happen if we had the composer.lock file, but final users of the components could still find themselves with out-of-sync dependencies because lock file is ignored for dependencies, i.e. a user requiring latest zend-mvc would still get an incompatible version of zend-servicemanager at the moment.
To solve this, we could add a further step in the build process where we run composer install both with the lock file and without it, so we have a reference snapshot for devs to test against, and the real scenario of what users would actually get when requiring the component.
This would result in me pushing my own fork of any given component, watching travis pass with the lock file and not with the latest deps, knowing what's happening and still having something to work with! Right know I don't know what version of zend-servicemanager I should use to run zend-mvc tests, so I can't work with it!
Thoughts?

@stefanotorresi that just adds one more entry in the build matrix: I don't see what it solves. Instead, we may test against oldest/newest versions (within the supported constraints), which is indeed what other projects do (see https://github.com/symfony/symfony/blob/cc84be9d53aefcd4a9a68ff9363a192453b979f8/.travis.yml#L65 )

Another solution (depending on the maintainer's opinion) is to simply gradually drop older package versions support, and bump dependencies whenever possible

uhm, yea, that absolutely works, I didn't think about that... but I'd still like to have the lock file to be able to install and build stuff without any hassle.
Otherwise I'd have to investigate the failure, guess it's a dependency problem, and manually run the update with --prefer-lowest, and the guessing part is what really bugs me. :-P

hmm, that actually doesn't work: I just tried and, for dependencies required via branch aliases (as zend-mvc#develop does with zend-servicemanager, one would still get the latest commit, which may not be compatible. So I still think that committing the lock file is a no-brainer to ease development, along with building the library with both locked and unlocked deps (adding both lowest and latest would be a further step).

One reason I've traditionally not committed the composer.lock file in library code is because omitting it has revealed issues with dependencies.
As an example, if a dependency update falls within the version constraints specified, but breaks our unit tests, it allows us to adapt:

we can choose a more strict version constraint.
we can determine how to make our code work both before and after the breakage.

When the composer.lock is present on the build system, it's easy to miss these issues.
The counter-argument often raised then is: you can introduce additional builds into the build matrix, one running against the composer.lock, another that runs against the results of composer update. (I've seen this done with the --prefer-lowest flag as well.)
One argument against this is that Travis has a limit on how many builds it runs simultaneously; as a result, we end up with builds taking far longer because they cannot be run in a single pass; some builds in the matrix are blocked until other builds complete. This may not seem like a problem, but, honestly, I've become accustomed to the sub-minute builds we currently have, and the longer builds I've seen on some of the components testing against v2 + v3 of zend-servicemanager are irritatingly frustrating to wait for; one key benefit to moving development from a monolithic repo to individual component repos was faster builds!
This is all my long-winded way of saying that I disagree with your assertion that "committing the lock file is a no-brainer to ease development;" there are other considerations at play here as well.

One argument against this is that Travis has a limit on how many builds it runs simultaneously;

Shouldn't be that big issue anymore, given that we split the repositories, and builds take considerably less time to run

Here is an update on the discussion:
I've had a long chat with @weierophinney on IRC yesterday and, even if he has concerns about the possible downfalls of having the lock file un-ignored, he agreed to consider my proposal.
Given the expressed concerns, I think we can take this slowly: I plan to submit a PR to initially implement the change in zend-mvc, since it's where the issue originated from and it's also the component with most dependencies; then see how it goes for some weeks, and if we are satisfied, then replicate the change in all the components. Sounds good?

@stefanotorresi since you are going to push this, please send a patch with:

low version
high version
lock version

Then just ping us and we'll watch what travis does :-)


GUI crashes with Mac canvas?

Traceback:
Traceback (most recent call last):
  File "/Users/adam/anaconda/envs/astropy27/lib/python2.7/site-packages/matplotlib/backend_bases.py", line 1936, in motion_notify_event
    self.callbacks.process(s, event)
  File "/Users/adam/anaconda/envs/astropy27/lib/python2.7/site-packages/matplotlib/cbook.py", line 540, in process
    proxy(*args, **kwargs)
  File "/Users/adam/anaconda/envs/astropy27/lib/python2.7/site-packages/matplotlib/cbook.py", line 415, in __call__
    return mtd(*args, **kwargs)
  File "/Users/adam/anaconda/envs/astropy27/lib/python2.7/site-packages/pvextractor-0.0.dev233-py2.7.egg/pvextractor/gui.py", line 157, in on_motion
    canvas.restore_region(self.background)
AttributeError: 'FigureCanvasMac' object has no attribute 'restore_region'

Yes, this is expected at the moment but would be good to have a workaround (basically can't blit on OSX backend, so have to re-draw every time - gonna be slow!)

Closing this as.... I don't know if mac canvases exist any more, but I don't have one.


fix for latest nightly

Make miri green again on nightly.
Waits for https://github.com/japaric/xargo/pull/228 to land.
Also this does not yet fix all tests, function_pointers.rs and mir_coercions.rs fail with "tried to dereference a function pointer" since https://github.com/rust-lang/rust/pull/56461.  These tests compare function pointers, which is likely the problem here.

All right, xargo is working again (using a git version for now).
What is left is the problem with the function pointers.

Yea I tried locally, but didn't have a free tree. I'll try again with the current state

Looks like this makes the test suite green, great.
However, I still think the old code should either work or get a better error message. I will open an issue.


adding nbinteract support

This PR adds support for nbinteract which lets you display interactive widgets powered by Binder. It is originally developed by @SamLau95 who also helps out with jupyter-book!
@SamLau95 if you have a moment, could you see if there's anything wrong with this implementation? I tried to mimic what you're doing on DS100...I don't quite have it working the way we'd like to properly ask Binder for a kernel and/or display update messages, any help would be appreciated
closes #82

For some reason this still isn't yet working...the kernel seems to correctly connect upon landing on the page, but:

the eventlistener still doesn't seem connected to the interact button at the top
nbinteract expects code cells to be in a div with this structure: div.code_cell div.input_area. While jupyter-book is just using div.input_area (no wrapping code cell). As such nbinteract doesn't seem to be finding the code cell text (and I assume this will also break the output execution and such.

@choldgraf is this ready to use? I am happy to give it a test drive if you want. I have some interacts in my jupyter-book and I'd love to try this out.

No tests updated? :)

nope not yet, I'm supposed to chat with @SamLau95 sometime this week to explain how to best-use nbinteract, I couldn't quite figure it out :-)

Notes from a chat with @SamLau95
Here's what nbinteract does:
when you click a button that launches nbinteract, it will do the following:

Loop through cells (expected to be something like div.cell with inputs/output divs inside it.
For each cell, run the contents of the input in Binder
If there is an output div called div.output_widget_view, then look at what binder sent back, if there is a widget in that then replace the contents of output_widget_view with the widget data that Binder sent back.

Normally, nbinteract uses a custom liquid template in order to add the .cell divs etc to the output HTML when you run it on a notebook...this is so that it adds the buttons to each cell that outputs a widget. However, we can get around that by using only one button (at the top of the page), and then adding the output_widget_view div code manually according to some metadata that the user gives in the cell (instead of automatically detecting this if there's a widget in the cell output metadata)
We should do something like:

Add
{% block codecell %}
<div markdown="1" class="cell border-box-sizing code_cell rendered">
{{ super() }}
</div>
{%- endblock codecell %}

so that cell components are grouped together in a div

Let use specify cell metadata for interactive outputs, if found, then add the classes that nbinteract looks for in running the cell (which is "div.output_widget_view")

Wooo, got it working :-)  thanks @SamLau95 for the advice:
https://811-137292803-gh.circle-artifacts.com/0/html/features/interact.html
now how the heck do we add a test for this 0.o

@jasmainak can you try clicking it again after waiting a moment? It took a second for nbinteract to initialize for me (I just tried the latest build and it seemed to work)...alternatively can you check the JS console to see if there are any errors?

we could do it that way as well with some modifications to the templates...I was thinking that it'd be simpler to just have it at the top (since once it's been activated once, it'll auto-activate in subsequent runs, and since clicking any one button will activate all of the widgets). Do you feel strongly on that one?

umm ... not too strongly, but I think the other one is more intuitive. At the moment, I am struggling to explain to people how to use the jupyter-book. Nobody seems to notice the buttons ... maybe it will be easier when I demo in person.

ok, I think this is pretty much ready to go except for tests
@SamLau95 do you have any recommendations for how to test nbinteract support?

@choldgraf One simple method is to make sure that the nbinteract-specific button(s) are present after converting notebooks into HTML.

I meant more like testing on the Javascript side :-) How did you test that kinda stuff in nbinteract? e.g., that when I click the button, the binder kernel properly connects etc

I'm gonna merge this in because it updates some of the cell CSS structure and could be useful in other PRs as well - we can iterate on the UI for nbinteract later on to see how it feels


Feature request: split index files, so they don't grow too big

Currently, as the final product of the rebuild-index/prune commands, a single big index is written out. And it can grow really large. On one of my repos, it has grown to 455MB. Such big files are not a problem for local disk repos, FS can handle them just fine. But, when using any kind of remote repo with HTTP transport, it's becoming a problem, as can be seen in #1386, #1411 and possibly more reported issues.
My suggestion would be to split index files, not unlike data blobs, so that there are more smaller size indexes which together form a full index. And my suggestion would also be that single index file is never bigger than about 64MB, but probably we could go for even smaller limit, somewhere in the 16 - 32MB.
And to not open a new issue, I'd also like to discuss the possibility of bringing index to the local side, would that make any sense? If I understand correctly, index files are basically kind of cache files, they are there just to speedup some lookups, right? They don't hold any new information, just information that's already in the repo, but packed in a way that makes it useful to do faster information retrieval about objects in the repo. So, unless I'm overlooking something, they could exist only on the local side, and the repo itself would be still complete?
I understand that increasing usage on the client side would be alarming for some, but even if this is implemented as an option would work. Then 455MB would not need to be uploaded over and over to the remote side, just to be pulled back to be used for the next restic operation. And then we could even consider using some other kind of on-disk fast lookup database (Bolt or similar), which I feel would bring restic memory usage down and make it more usable on smaller systems like Raspberry, various NAS devices etc...?
OK, that was a brain dump, it feels rather logical, but I'm probably missing something...

Definitely a good idea. The index file format can be split easily without breaking backwards compatibility, and I think we should try that.
The index files consist of all the headers of the pack files (basically "which blob is stored where"). This prevents having to list the pack files and read all headers of all pack files at the start. We could indeed move the index files completely to the local side, but that would break backwards compatibility with older versions of restic. Besides, that would still require listing all pack files at each start to find out about removed and new pack files. Depending on the backend, that's a much more expensive operation (in terms of latency and time) than downloading index files.
I think the index file handling in restic has huge potential for optimizations. Let's try implementing an upper bound for the index file size first (since that's backwards compatible) and see where this gets us.

A question on the thought of not storing the index on the server anymore; Won't this cause practical issues, at least huge performance problems, for the users that for whatever reason don't want to store the cache locally (i.e. that run without the cache)?
As the cache can grow insanely right now, and even if it doesn't, will take up GBs on disk, it's not always wanted to keep a cache local. Would be a bad thing if you'd be left without a cache at all. Then again perhaps that's not what we're talking about here.

rawtaz@ i think that question is answered by fd0 in the above 2nd paragraph :) and yes.
On #979 I posted the idea of using a bloomfilter, so that backup only, small machines can use only the bloom filter to determine if the hash is there. We would need some way of appending/joining to the index though, for the restic commands which need access to the actual data. But a bloomfilter can be a few orders of magnitude smaller than the complete index.


Add clickable image

I want to add images which should be clickable and redirect to given link.

Hi, sounds like a good idea.
Maybe this can be implemented as a "object attribute".
Also this seems to be related to #71

@techprimate-phil Thanks for your support. I'm trying to solve this from your suggestion of issue #71 but not getting the solution. Also I don't see any "object attribute" in the code.

You are correct, the "object attributes" do not exist.
That's just a more generic approach similar to HTML attributes (there might be other future attributes, such as in-document links).
My idea is the following:

Create any kind of PDFObject (e.g. PDFImageObject based on a PDFImage)
Calculate the frame of it
Render it
If a link attribute is given, add a clickable area using the link using the frame of the object

I actually just created an implementation on feature/170-clickable-objects, going to merge it on develop right now

Thank you very much @philprime . Temporarily I had implemented clickable image by overlapping a clear coloured link on Image. But that was working just for iOS. If I share that PDF in android device, it was not working. Today I implemented enhanced version of TPPDF and it works like charm now. Thank you so much :)


hasAcceptedDisclaimer RPC fast path

Narrowed getWalletSettingsLocal to hasAcceptedDisclaimerLocal which has one job, to return whether the user has accepted the disclaimer, caching when possible, but with no loss of serializability.
Calling hasAcceptedDisclaimerLocal when the user has accepted the disclaimer will result in 1 server RPC ever per install. Calling hasAcceptedDisclaimerLocal when the user has not accepted the disclaimer will still result in a server RPC each time, since you'd want to pick up an acceptance from another device.
The RPC can still error out on network conditions. But in the case where the user has viewed the wallet tab on the device before that will not happen.

Where does  s.disclaimerAccepted get set?

hm broke gui during rebase


Add documentation to exceptions

Current coverage is 100% (diff: 100%)

Merging #369 into 1.0.0 will not change coverage

@@           1.0.0   #369   diff @@
===================================
  Files         23     23
  Lines       1536   1537     +1
  Methods        0      0
  Messages       0      0
  Branches     183    183
===================================
+ Hits        1536   1537     +1
  Misses         0      0
  Partials       0      0

Powered by Codecov. Last update 3bdd354...f824e21

@kavdev should be g2g now 👍


tach check with circular dependencies should emit more details

With the configuration forbid_circular_dependencies = true, running tach check on a codebase that has circular imports may emit something like the following:
$ tach check
❌ Circular dependency detected for module 'foo.models'
❌ Circular dependency detected for module 'foo.utils'
❌ Circular dependency detected for module 'foo.tasks'

But doesn't provide much more beyond that.
It would be better to add a --verbose or --debug flag to this check to emit more details as to what cycle was found, how many steps, and generally provide more context to the reader on how to resolve.

This is due to performance concerns IIRC. The check stops at the first cycle, and I'm not sure if the current algorithm will have path information.
This can definitely be improved though, especially for smaller projects. Will look back into this.


Make withOpenDb internal.

@kabentley has changed its signature in #4057. Rather than backport that change to 3.3, just mark it internal until 3.4 is released.

Force-merge because appui-react tests hung on both macOS and linux.
@NancyMcCallB is someone looking into this problem?


Migrate segmented control

PR Type
Enhancement, Bug fix

Description

Migrated segmented control stories to a new format and removed multi-select and persistent control stories.
Added a new configuration file for the segmented control component with descriptions, status, and usage guidelines.
Simplified the SegmentedControlProps interface by removing multi-select related properties and updating onChange and selectedIndex properties.
Refactored the SegmentedControl component to remove multi-select logic, update styling, and use the useTheme hook.
Updated the SegmentedControl usage in the SplitPage component to the new props format.
Added a useTheme hook for accessing the theme context.

Changes walkthrough 📝
Relevant filesEnhancement

SegmentedControl.stories.tsxMigrate and update segmented control stories

apps/demo/stories/SegmentedControl.stories.tsx
Migrated segmented control stories to new format.  Removed multi-select and persistent control stories.  Updated SegmentedControl props to use selectedIndex.

+13/-47

SegmentedControl.config.tsxAdd configuration for segmented control component

apps/demo/story-config/SegmentedControl.config.tsx
Added new configuration file for segmented control.  Included descriptions, status, and usage guidelines.  Linked to Figma design and related components.

+40/-0

Common.tsSimplify SegmentedControlProps interface

packages/ui/src/Common.ts
Simplified SegmentedControlProps interface.  Removed multi-select related properties.  Updated onChange and selectedIndex properties.

+5/-21

SegmentedControl.tsxRefactor SegmentedControl component and update styling

packages/ui/src/SegmentedControl.tsx
Refactored SegmentedControl component.  Removed multi-select logic and related warnings.  Updated styling to use useTheme hook.

+44/-97

Theme.tsxAdd useTheme hook for theme context access

packages/ui/src/Theme.tsx

Added useTheme hook to access theme context.

+2/-0

Bug fix

SplitPage.tsxUpdate SegmentedControl usage in SplitPage component

packages/ui/src/SplitPage.tsx
Updated SegmentedControl usage to new props format.  Changed selectedItemIndexes to selectedIndex.

+1/-3

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

One more thought - Jo calls out that this is also known as a "Toggle Group". Not sure if we're willing to rename components as part of this work, but if so, I think ToggleGroup is a great, descriptive and to me slightly more intuitive name for this component.

I think Toggle usually denotes a boolean choice, where we support many choices with SegmentedControl.

I'm gonna talk to Jo about making those dots a different component completely. Also removed that render fn thing you noted, thank you!


Error: account has not yet been opened

In the previous version, when I deposited some nano in a new account and then did atto -a 2 b, this would create a receive block for me to get those funds.
Now, when I do that, it spits out "Error: account has not yet been opened"

I have now released v1.4.0 which hopefully reverts all previous regressions.


Helm cannot install Ambassador 0.35.3

Describe the bug
Ambassador version 0.35.3 is registered on helm but it is not installable. The reason why it fails is that the tarball at the following url is not available: https://www.getambassador.io/ambassador-0.35.3.tgz
To Reproduce
Steps to reproduce the behavior:

helm install datawire/ambassador

Expected behavior
Ambassador version 0.35.3 should be installable with helm.
Versions (please complete the following information):

Ambassador: 0.35.3
Kubernetes environment: AWS
Version: 1.9.1

Hey @noverby, this was already fixed in #639, try running helm repo update again?

@containscafeine thanks it worked.


Fix config file loading

Currently -config-file is broken due to missing config file parser option.
$ ./fastly-exporter -config-file test.cfg
level=error err="-token or FASTLY_API_TOKEN is required"

This PR fixes it:
 $ ./fastly-exporter -config-file test.cfg
level=info prometheus_addr=<IP_ADDRESS>:3759 path=/metrics namespace=fastly subsystem=rt
level=info filter=metrics type="name blocklist" expr=attack
level=info filter=metrics type="name blocklist" expr=imgopto
level=info filter=metrics type="name blocklist" expr=ipv6
level=info filter=metrics type="name blocklist" expr=otfp
level=info filter=metrics type="name blocklist" expr=pci
level=info filter=metrics type="name blocklist" expr=video
level=info filter=metrics type="name blocklist" expr=waf
level=info filter=services type="explicit service IDs" count=1
level=info component=rt.fastly.com service_id=xxxxxxxxxxxxx subscriber=create

Would be nice if you tag the PR with hacktoberfest-accepted 🙏

Wow!! I can't believe this bug existed for so long!!

How do I tag a PR?

Is just adding a label on the right :)

@skgsergio Doesn't that make the label kind of perpetually there for this repo?

Hmmm I think so. No worries of it is an issue.

Yeah I'd rather not :) But thank you for the contribution!!!


Hub Properties Observable & Writer

See spec which of them are observable and have writers
Lesson Learnt from #51

AdvertisementName (set, request, monitor, reset)
Button, RSSI, BatteryVoltage (request, monitor)
HwNetworkId (set, reset)
HwNetworkFamily (set)

Single observable for all properties. INotifyPropertyChanged for properties (also implement for devices)
Request, Monitor on/off via method Hub.SetupNotificationAsync and existing Hub.RequestHubPropertySingleUpdate.


Windows Install Issue

Hey Jed,
Running into an issue on install on Windows.  I'm just replacing my .nuke folder with yours, but it seems that something in the python is adding extra spaces.  I'm looking through the python code, but having trouble finding exactly where the spaces are coming from.
Could you take a look?
Thanks for sharing and your wonderful video on creation a Pano!
-Andy

Hey Andy!
Thanks for opening this issue... I'm aware of it, I just haven't gotten around to fixing it yet. Maybe this will motivate me!
It's coming from tools/python/nuketools/custom_toolsets.py ... something in that code is not properly escaping backslash characters in windows paths. It's based on Vitaly Musatov's Shared Toolsets: https://github.com/greenvfx/toolsets ... I am planning on rewriting this and massively simplifying it.
As a workaround for now, you could delete that python file, and rename the toolsets directory to ToolSets - this will just use the default Nuke toolsets system instead.
Hope that helps, and I'll post here again when I get around to properly solving this.

Thanks for the tip Jed, most appreciated:)
Cheers,
-a

I finally got around to moving toolsets to ToolSets and removing the custom_toolsets module.
I will write a better replacement that is more customizable one of these days, but now at least life is not broken by default on windows... Will close this issue.
Thanks again for reporting this @andyfedak


UI fails to load on safari due to regex error

The error is
SyntaxError: Invalid regular expression: invalid group specifier name

It seems that safari does not support lookbehinds like (?<= ) or (?<! ) since the support for lookbehinds is recently finalised for javascript under ECMA-262(ECMAScript 11) specification. See this.

https://caniuse.com/js-regexp-lookbehind
But on the other hand support for lookaheads like (?= ) or (?! ) was there already. So safari also supports lookaheads.
To resolve the issue just find an alternative to lookbehinds that your regex is using. Don't worry about lookaheads.

Updated regex from https://regex101.com/r/nEUpiR/1 to https://regex101.com/r/ArSQor/1
Done


Add Prometheus Remote Write Exporter to Collector Lambda Layer Components

Added the Prometheus Remote Write (PRW) exporter into the Collector Lambda Layer.
Tested by running make publish-layer in the /collector folder, which successfully publishes the layer to Lambda.

Hi @codeboten can you please review and merge this PR? Many thanks!


Fix BVT failures due to placements being removed in the policy collection

The placement related manifests in policy-collection were removed since those are environment specific. This has led to the BVT/SVT tests to fail that relied on those. This task is create the now missing placements and bindings in those tests. Ref: https://issues.redhat.com/browse/ACM-13584
Signed-off-by: yiraeChristineKim<EMAIL_ADDRESS>

This doesn't feel comfortable to me. We shouldn't be deleting a default installed namespace. It'll create havoc if our tests are run alongside other tests in places like the canaries.
Instead, I'd prefer that the policy-test namespace is used as normal and is bound to the global ManagedClusterSet.

Oh, I see now that it's not deleted. Still, I think it could be cleaner to have our own namespace that we can delete/manage. 😅

This doesn't feel comfortable to me. We shouldn't be deleting a default installed namespace. It'll create havoc if our tests are run alongside other tests in places like the canaries.
Instead, I'd prefer that the policy-test namespace is used as normal and is bound to the global ManagedClusterSet.

Oh, I see now that it's not deleted. Still, I think it could be cleaner to have our own namespace that we can delete/manage. 😅

You mean... should I add managedClusterBinding for our test?

You mean... should I add managedClusterBinding for our test?

Yes, that's what I'm thinking. I think it might be cleaner overall, and it'd behave the same way as open-cluster-management-global-set does.

/test test-e2e-grc-framework

/test test-e2e-grc-framework

/test test-e2e-grc-framework

/test test-e2e-grc-framework

/retest

/test test-e2e-grc-framework

/test test-e2e-grc-framework

/test test-e2e-grc-framework

Looks like the compliance history and Gatekeeper tests both install the Gatekeeper operator. My suspicion is that previously they were in different namespaces and didn't collide (or at least as frequently). Now that the namespaces are the same, they're running into conflicts:

intersecting operatorgroups provide the same apis, there are CRDs present for the operator, no existing operator Deployments

Looks like the compliance history and Gatekeeper tests both install the Gatekeeper operator. My suspicion is that previously they were in different namespaces and didn't collide (or at least as frequently). Now that the namespaces are the same, they're running into conflicts:

intersecting operatorgroups provide the same apis, there are CRDs present for the operator, no existing operator Deployments

Interesting observation @dhaiducek! I'm going to go ahead and merge this and I'll work on a fix. I think you're right that the uninstall is not working as expected.
I'll let @yiraeChristineKim focus on the discovered policies table.

/override ci/prow/test-e2e-grc-framework
Will be fixed in another PR


README updates

This issue is here so I remember all the inaccuracies in my readme documentation

[ ] Fix Installation instruction
[ ] Fix Hyperlinks (christiangroeber->pixlmint)


Remove product setting creation from BOPIS app in order to avoid duplicate setting creation

Current behavior
Currently, the app checks for settings, and if a setting is not found, it creates one with a default value of false. Occasionally, this results in duplicate settings being created. Although the root cause has not yet been identified, it is likely that the duplicate settings are being generated by the BOPIS app. To resolve this, prevent the BOPIS app from creating the following settings: ENABLE_TRACKING, PRINT_PACKING_SLIPS, PRINT_PICKLISTS, and SHOW_SHIPPING_ORDERS.
Expected behavior
Follwing settings are no longer created from BOPIS app - ENABLE_TRACKING, PRINT_PACKING_SLIPS, PRINT_PICKLISTS, SHOW_SHIPPING_ORDERS'
Steps to reproduce the issue

Can you handle fixing this bug by yourself?

[ ] YES
[ ] NO

Environment details

Browser:
OS:
Code Version:

Additional information

Verified the changes and are working fine in release v2.26.6. Hence, closing this issue.


docs: mesh with FIPS 140-2 on CentOS/RHEL 7

Signed-off-by: Nikolay Nikolaev<EMAIL_ADDRESS>

Thanks @lena-larionova!


Suppress spurious warnings from the CCS compiler

Supress spurious warnings from the CCS compiler
Description
Fixes warnings when building with CCS:
error #1916-D: definition at end of file not followed by a semicolon or a declarator
Test Steps
Compile a project with this fix, and the warning should go away
Related Issue
N/A
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@jscott-hotstart Thanks a lot for adding support for this board and compiler!
It seems like CCS gets confused by the creative use of #include in this project, but at least the warnings can be suppressed 🤷

@jonathangjertsen, thanks a lot for taking the time to create a PR.
We'll look into it and proceed with merging if all goes well.
Thanks,
Aniruddha


Add minimum version of PHP in composer file

Purpose
Currently anyone can install the package throught composer
Approach
Set a minimal version into composer.json

Sorry I was at vacation last three weeks.

Don't be sorry, it's open source 😄


FIX scroll jittering

The old code would trigger the reaction again and again.
I didn't find out exactly why, but it was partly because the
data of reaction was an object that was being recreated
each time something changed in the UI Store. This was fixed
by having the data be a simple string. It could also have been
fixed by passing options to the reaction of {equals: comparer.shallow}
PT-185826033

This same change is available as a second PR based on the 4.4.x branch: https://github.com/concord-consortium/collaborative-learning/pull/1869

The code still checks the docId, it just does it in the data part of the reaction. This way the reaction part of the reaction isn't run in components for other documents.
Yeah, I don't know why this started happening now. My best guess is like you said. Something is starting to change the UI store repeatedly. I'm not totally sure but I think any changes to the store would trigger a recalculation of the data part of the reaction. And that would then cause the reaction part of the reaction to run in the old code. We could track this down further with MobX debugging tools, but I didn't do it.
Since I'm in the middle of the layout refactoring I don't really want to put it down to dig in more. I made a new chore for that:
https://www.pivotaltracker.com/story/show/185827926
I probably won't get to this though, but maybe I can find the time.


add notebooks link to binning nb

Fixes #110

Codecov Report

Merging #111 (366e639) into main (e81040c) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main     #111   +/-   ##
=======================================
  Coverage   86.73%   86.73%
=======================================
  Files          14       14
  Lines         912      912
=======================================
  Hits          791      791
  Misses        121      121


Feature request: Non-fatal error for reading corrupted fasta records (skbio.io.read)

I encountered an error (below) reading in corrupted UNITE fasta files (fungal ITS sequence database).  Most of the sequences were fine but a few of them had characters outside of the DNA alphabet, when a record contained a bad character, the parser threw a fatal error.
It could be useful to have an error message giving the header of the corrupted entry and then continue reading the file (i.e. a non-fatal error).
The sequences I was using were from: https://unite.ut.ee/sh_files/UNITE_public_22.08.2016.fasta.zip
I gave them a list of which ones were corrupted and I think they fixed it in the newer release.
When I first encountered this error, it took me a bit to figure out which entries were corrupted.
path = "/Users/Mu/Downloads/UNITE_public_22.08.2016.fasta"
>>> for seq_record in skbio.io.read(path, constructor=skbio.DNA, format="fasta", lowercase=True):
...     pass
...
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/Mu/anaconda/lib/python3.5/site-packages/skbio/io/registry.py", line 506, in <genexpr>
    return (x for x in itertools.chain([next(gen)], gen))
  File "/Users/Mu/anaconda/lib/python3.5/site-packages/skbio/io/registry.py", line 531, in _read_gen
    yield from reader(file, **kwargs)
  File "/Users/Mu/anaconda/lib/python3.5/site-packages/skbio/io/registry.py", line 1008, in wrapped_reader
    yield from reader_function(fhs[-1], **kwargs)
  File "/Users/Mu/anaconda/lib/python3.5/site-packages/skbio/io/format/fasta.py", line 677, in _fasta_to_generator
    **kwargs)
  File "/Users/Mu/anaconda/lib/python3.5/site-packages/skbio/sequence/_grammared_sequence.py", line 336, in __init__
    self._validate()
  File "/Users/Mu/anaconda/lib/python3.5/site-packages/skbio/sequence/_grammared_sequence.py", line 360, in _validate
    list(self.alphabet)))
ValueError: Invalid character in sequence: b'U'.
Valid characters: ['R', 'H', 'V', 'B', 'N', 'W', 'S', 'C', 'M', '.', 'T', 'K', '-', 'D', 'G', 'Y', 'A']
Note: Use `lowercase` if your sequence contains lowercase characters not in the sequence's alphabet.

One of the entries was:

UDB002609|k__Fungi;p__Basidiomycota;c__Agaricomycetes;o__Thelephorales;f__Thelephoraceae;g__unidentified;s__Thelephoraceae_sp|SH189369.07FU
CCGAATTGTTGACACGAGTTGTTGCTGGCCTTCAAACGGGGGCACGTGCACGCTCTGTTTATACATCCACCCACCCCTGTGCACCTTTTGTAGCTCTGTGGTCTGGAGGCTCCGCTTCCCTTCCGCGGTTCTACGTCTTTACACACACACGTTAAAGAAGTCTGTGGAATGTACGCCGCGTTTACGCAATACAATACAACTTTCAGCAACGGATCTCTTGGCTCTCGCATCGATGAAGAACGCAGCGAAATGCGATAAGTAATGTGAATTGCAGAATTCAGTGAATCATCGAATCTTTGAACGCACCTTGCGCCCTTTGGCTATTCCGAAGGGCATGCCTGTTTGAGTATCATGAACACCTCAACCCTCACGGTTCCTCGTGATGGGCTTGGACTTGGGGGCTTTGTTGGCCTGTGGTCAGCTCTCCTCAAATAAATCAGCTCGCCAGTGTCTGGCGGCATCATGGGTGTGATAACCATCTACGCTTGTGATCGCCTGCGAGGTAAACCTCTGGTCTGCAGAGGTTCGCTGGAGCTTATAGATGTCTCTCCTCCGTGAAGACAGCTGTCTGAAGTTCGATCTCAAATCAGGTAGGACTACCCGCTGAACTTAAGCATATCAATAAGCGGAGGAAAAGAAACTAACAAGGATTCCCCTAGTAACTGCGAGTGAAGCGGGAAGAGCTCAAATTTAAAATCTGGCGTGCCTCCGGTCGTCCGAGTTGTAGTCTGGAGAAGCGTTTTCCGTGTTGGACCGTGTATAAGTCTCTTGGAACAGGGCGTCATAGAGGGTGAGAATCCCGTCTTTGACACGGACTGCCAATGCTTTGTGATGCGCTCTCAAAGAGTCGAGTTGTTTGGGAATGCAGCTCAAAATGGGTGGTAAATTCCATCTAAAGUDB

Note: this is migrated from https://github.com/biocore/scikit-bio/issues/1438

:+1: I think this could be handled like open's errors parameter. I think it should stay a fatal error by default, but if you have a handler you can opt out because you've given skbio something to do instead of except.

What if it still threw a fatal error but also gave the header in which the error occurred for debugging purposes?


drewr/postal

I've been experimenting with drewr/postal to be able to send e-mails from a native-image.
So far it fails for me with:
#error {
 :cause "smtps"
 :via
 [{:type javax.mail.NoSuchProviderException
   :message "smtps"
   :at [javax.mail.Session getService "Session.java" 811]}]

I've tried adding com.sun.mail.smtp.SMTPTransport to the reflection config, but this didn't help.

Useful comment from the graalvm slack:

looks like smtps requires com.sun.mail.smtp.SMTPSSLTransport  instead of SMTPTransport

Confirming that worked!

Fantastic, would you be able to add an example?

@BrunoBonacci I'm trying to add it to babashka: https://github.com/borkdude/babashka/
Once that's finished, I'll have a look if I can add a small example here.

Hi Michiel,
that's great!
funny enough I was just watching your :ClojureD talk on Babashka this morning!! ;-)
Really great work!

The only thing that I haven't mentioned in this issue is that you have to set the System property postal.version to something, else you'll get a NullPointerException in your GraalVM native-image binary.
I'm not going to spend any energy in it right now, because the above approach only works on java8 and not with java11 versions of GraalVM. Maybe I'll revisit in the future.


 This would match the behavior of killing a Dart process. Instead those sockets seem to remain open without any way of interacting with them.
For example:
import 'dart:async';
import 'dart:io';
import 'dart:isolate';

main() async {
  var rp = new ReceivePort();
  print("spawning isolate");
  var isolate = await Isolate.spawnUri(new Uri.dataFromString(r"""
    import "dart:async";
    import "dart:io";
    import "dart:isolate";

    main(_, SendPort port) async {
      var socket = await ServerSocket.bind("localhost", 0);
      print("bound server socket");
      socket.listen(null);
      port.send(socket.port);
    }
  """), [], rp.sendPort);

  var port = await rp.first;
  print("connecting client socket");
  var socket = await Socket.connect("localhost", port);
  socket.listen(null, onDone: () => print("socket closed"));

  print("killing isolate");
  isolate.kill();
}

I'd expect this to print "socket closed", but it never does.

@lrhn @floitschG could one of ya'll take a look at this?

Sounds similar to #27898

@sgjesse for possible insights.

The VM registers weak persistent handles on the Dart objects with native fields that wrap C++ wrappers around file descriptors for files and sockets (and a few other things). See, e.g.:
https://github.com/dart-lang/sdk/blob/master/runtime/bin/file.cc#L72
and after the change referenced above:
https://github.com/dart-lang/sdk/blob/master/runtime/bin/socket.cc#L984
When the Dart objects are GC'd the finalizers registered with the handles close the file descriptors, either directly in the case of files, or indirectly through the event handler in the case of sockets.
The specific case that @lrhn mentions, in which the event handler or IO service opens a file or socket but the requesting isolate is killed before the native wrapper object and the finalizer can be set up, is probably the only remaining situation where we may still leak a file or socket. Something relatively simple like setting up the native wrapper objects before sending the requests to the event handler and IO service would probably be sufficient, though.

@lrhn
Please re-evaluate this and do one of the following:

Add it to a milestone if it is still P1
Change priority label and add milestone if no longer P1
Close, if this issue is no longer needed

This is no longer seems to be a problem:
import 'dart:async';
import 'dart:io';
import 'dart:isolate';

child(SendPort port) async {
  var socket = await ServerSocket.bind("localhost", 0);
  print("bound server socket");
  socket.listen(null);
  port.send(socket.port);
}

main() async {
  var rp = new ReceivePort();
  print("spawning isolate");
  var isolate = await Isolate.spawn(child, rp.sendPort);

  var port = await rp.first;
  print("connecting client socket");
  var socket = await Socket.connect("localhost", port);
  socket.listen(null, onDone: () => print("socket closed"));

  print("killing isolate");
  isolate.kill();
}

─➤  xcodebuild/ReleaseX64/dart isolate-socket.dart                                                                                spawning isolate
bound server socket
connecting client socket
killing isolate
socket closed
^C


Is it possible to compile to WASM (WebAssembly)?

I think there's some WASM GBA emulators, if that's what you're searching for.

Closed due to lack of activity.