Access to UITextField's _placeholderLabel ivar is prohibited

iOS 13 Crashing due to uncaught exception 'NSGenericException', reason: 'Access to UITextField's _placeholderLabel ivar is prohibited. This is an application bug'
we are getting crashes because of how the framework uses KVC to access Apple's private APIs.

This is is resolved please make sure you are using latest version of pods.
Thanks
Sent from my iPhone

On 19-Nov-2019, at 3:13 PM, sidlowanshi<EMAIL_ADDRESS>wrote:
iOS 13 Crashing due to uncaught exception 'NSGenericException', reason: 'Access to UITextField's _placeholderLabel ivar is prohibited. This is an application bug'
we are getting crashes because of how the framework uses KVC to access Apple's private APIs.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Am also got that the same issue "iOS 13 Crashing due to uncaught exception 'NSGenericException', reason: 'Access to UITextField's _placeholderLabel Ivar is prohibited. This is an application bug'.
Once I update the latest version. It will be working fine. Thanks buddy.

Thanks
Sent from my iPhone

On 21-Nov-2019, at 4:16 PM, Srinivasan Sampath<EMAIL_ADDRESS>wrote:
Am also got that the same issue "iOS 13 Crashing due to uncaught exception 'NSGenericException', reason: 'Access to UITextField's _placeholderLabel Ivar is prohibited. This is an application bug'.
Once I update the latest version. It will be working fine. Thanks buddy.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

FIXED


.whl includes .gitignored content

I am not sure if this is expected but when I do flit build it creates the tar.gz and also -any.whl distributions.
The tar.gz respects my .gitignore but the .whl includes ignored content.
(I tried setting in my MANIFEST.in but looks like flit ignores this also)

Yes, that's expected - wheel builds do not involve the VCS at all. It should be smart enough to avoid including .pyc files, though.
What files are you seeing included which should not be?

And, as you found, it doesn't use MANIFEST.in. One of my main motivations for flit was to avoid the need for MANIFEST.in, because I have to look up the syntax every time I write one.

@takluyver That is strange because wheel and sdist are suposed to have the same contents no?
I have some generated files, media files, database files, passwords files, .env files etc
They are all on my .gitignore so releasing sdist exclude all those files.
Usually I put exclude patterns in MANIFEST.in and I agree syntax is not the best, but works for wheels and sdists.
Why wheel does not exclude the .gitignored files?

Building a wheel deliberately doesn't use any information from the VCS. It simply zips up the whole package you've pointed it to, with whatever it contains. This is partly because that's simple to understand, and partly because it means that making a wheel doesn't depend on any kind of VCS tools.
Why are those other files getting saved inside the package directory? It's best to reserve that space for the code and any data files you expect to ship along with your code.

It's best to reserve that space for the code and any data files you expect to ship along with your code.

I know and I try to follow this when I can, but for some legacy projects here we have some assets generated at runtime that cannot be included (neither deleted because they are part of development environment)
In my understanding I think the best would be:

Project have a repository in github with many files
The sdist is generated with the same files
The wheel is generated with the same files

So repo, sdist, wheel has exact the same file tree and flit already achieve this by using the .gitignore which I think is very clever. (not for those who are not using vcs)
Is there a reason to build wheel in a file tree different of sdist?

I know you don't like to add more flags but one way is to keeo it optional.
flit [sdist wheel publish build] [--vcs]

while --vcs can be enabled by default or even having it as option in flit.ini [flit] section.

It looks like, once PEP 517 support is implemented, pip install . will work by trying to build an sdist, and if that succeeds, using it as the source for building a wheel.
So one option for the future is that flit build makes an sdist first, and then builds the wheel from that, while flit wheel remains as the quick-and-dirty option to build a wheel directly.

In flit 0.12, flit build builds an sdist first, then unpacks that and uses it to build the wheel. So the wheel should not include any files that aren't in the sdist.


Upstream ciphersuite and key exchange identifiers and configuration API for TLS 1.3

Context: While TLS versions prior to 1.3 package a choice of asymmetric key exchange mechanism and symmetric hash and encryption algorithms as "ciphersuites", TLS 1.3 treats those independently, reserving the name "ciphersuite" for the choice of symmetric algorithms.
Task: Find and implement a way to introduce TLS 1.3 identifiers and configuration API for key exchange mechanisms and ciphersuites alongside existing identifiers and interfaces for TLS 1.2.
Estimated time: 3 engineering days

@daverodgman I am labelling this as mbedtls-3 because doing this task might lead to suggestions for changes in the ciphersuite configuration API for Mbed TLS 3.0 to better align it with TLS 1.3.

Implemented by #4811


More details for our Cloud 2 locations

We have customers who want to know where our Cloud 2 on Azure instance is. Currently it states "West Europe".

But that's not helpful for determining compliance requirements. For instance, Germany is in western Europe, but has data privacy laws that go beyond EU regulations:
https://www.complianceweek.com/data-privacy/germanys-dual-approach-to-data-regulation-under-the-gdpr/28386.article
--
Other issues:
#2
Admittedly nitpicky, but we say "Frankfurt" and not "Frankfurt, Germany". I deal with enough customer emails to not be surprised if someone might scan this and think it's Frankfurt Kentucky/Alabama/Illinois/Indiana/Kansas/Maine/etc.

#3
We don't explicitly name which regions we're in. We state "US West", not "US West 2" for instance. At volume, I worry about someone saying that our doc only said "US West", and claim they purchased thinking we were in Northern California (AWS US West 1 region).
Yes, these would be silly objections, but it'd burn up cycles needlessly defending against. It the history of business disputes, there have been sillier claims made.
Relevant URLs
https://v2.docs.influxdata.com/v2.0/reference/urls/
Proposed solution
Be explicit about where we are running. In the Region column, state the exact region that each of the cloud providers use the following, respectively:
us-west-1
eu-central-1
us-central1
westeurope-1
Create a new column, Location, with the city (if well-known), state (if well-known) and country. So use the following, respectively:
Oregon, USA
Frankfurt, Germany
Iowa, USA
Amsterdam, Netherlands

Hi @alsargent , thanks for this issue.
We can definitely include the country for Frankfurt and add the city/country for the Azure data center.
But not sure what you're asking for re. # 3 above:

We don't explicitly name which regions we're in. We state "US West", not "US West 2" for instance. At volume, I worry about someone saying that our doc only said "US West", and claim they purchased thinking we were in Northern California (AWS US West 1 region).

The screenshot you took very clearly says Oregon? I'm not sure if you're referring to a different place in the docs or you somehow didn't see that. Can you clarify?


Update backwards-compat import for ovos-utils 0.1 compat

Replace import deprecated in ovos-utils 0.1
Bug noted in https://github.com/NeonGeckoCom/NeonCore/actions/runs/8840311299/job/24275381025
Related, #442 introduced a dependency on ovos-utils 0.1.0aX

a check for version can be added here if we need to downgrade the version bump
https://github.com/OpenVoiceOS/ovos-core/pull/442/files#diff-18a7548d5ad5b1290294a05f00f905a9f7980e4cf86f2b6a7d5007467490fd02R798


Update topic structs and functions

Scope of changes
Added the following client methods and corresponding tests:
ProjectTopicList
ProjectTopicCreate
TopicList
TopicCreate
Fixes SC-10354
Type of change

[x] new feature
[ ] bug fix
[ ] documentation
[x] testing
[ ] technical debt
[ ] other (describe)

Acceptance criteria
Describe how reviewers can test this change to be sure that it works correctly. Add a checklist if possible.
Author checklist

[x] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[x]  I have added new test fixtures as needed to support added tests
[ ]  Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

@bbengfort I'll resolve the merge conflicts after PR #57 is approved.

@bbengfort The repetition is helping me remember what I've learned, so it's fine.


cannot use temp group parents

Using LP version 5.1.64 on Paper 1.16.1 (ver 26 currently but don't think it's relevant)
When i try to execute command like
/lp user playername parent addtemp vip 31d
i get exception in console and nothing happens
[16:43:48 WARN]: java.lang.NoSuchMethodError: net.luckperms.api.node.Node.getExpiryDuration()Ljava/time/Duration;
[16:43:48 WARN]: at me.lucko.luckperms.common.commands.generic.parent.ParentAddTemp.execute(ParentAddTemp.java:98)
[16:43:48 WARN]: at me.lucko.luckperms.common.command.abstraction.GenericParentCommand.execute(GenericParentCommand.java:90)
[16:43:48 WARN]: at me.lucko.luckperms.common.command.abstraction.GenericParentCommand.execute(GenericParentCommand.java:49)
[16:43:48 WARN]: at me.lucko.luckperms.common.command.abstraction.ParentCommand.execute(ParentCommand.java:109)
[16:43:48 WARN]: at me.lucko.luckperms.common.command.abstraction.ParentCommand.execute(ParentCommand.java:45)
[16:43:48 WARN]: at me.lucko.luckperms.common.command.CommandManager.execute(CommandManager.java:204)
[16:43:48 WARN]: at me.lucko.luckperms.common.command.CommandManager.lambda$executeCommand$1(CommandManager.java:145)
[16:43:48 WARN]: at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1604)
[16:43:48 WARN]: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[16:43:48 WARN]: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[16:43:48 WARN]: at java.lang.Thread.run(Thread.java:748)

One of your other plugins is shading an older version of the LuckPerms API - try removing anything with a dependency on LuckPerms, that should resolve the issue. When (if) you find the plugin which is causing the issue, then report it to the author. :)


python3Packages.django_extensions tests fail

This breaks the build when the mailman module is enabled.
$ nix-build -A python3Packages.django_extensions
[...]
=========================== short test summary info ============================
FAILED tests/templatetags/test_syntax_color.py::SyntaxColorTagTests::test_should_colorize_table_with_default_lexer
= 1 failed, 467 passed, 4 skipped, 3 xfailed, 7 xpassed, 237 warnings in 20.79s =

Caused by changes in https://github.com/NixOS/nixpkgs/pull/117452

58009e85204 is the first bad commit


Added option for alternative background

I was annoyed by the standard Plex background images for media section. So I added an option to show nice blue cinema curtain instead. Can be activated in "options" and when activated replaces the standard background (e.g. this yellow cinema chairs in movie or the TV with Dog in TV Shows).
The new image "movie.jpg" is created by me and does not hold any copyright. So feel free to include it in your Master
Show Media Background on Hover (if activated) still works fine.
In addition I corrected another typing error in the german de.json file and corrected an error, that has not written back the selection of disabled subtitles to Plex
Best regards
Stefan
p.s. I changed the following files only:
index.html
script/index.js
script/media.js
script/player.js
language/de.json
language/en.json

happy to implement the language changes but I am not adding an option to change the background art ... there are other ways to do this and I would rather stick with what PLEX provide ... thanks for the updates ...

OK, no prob. I stick with my implementation on USB then.


M1 Mac Install Issues

Are there known issue to make M1 Mac installs not work? Can't get the build wheels for chiavdf to install.

Having issue with the install... Keeps giving me a ERROR: Failed building wheel for chiavdf each time. Seems to be related to fatal error: 'boost/asio.hpp' file not found. This is on an M1 Mac, so if i should just give up i will, or if not if someone can point me in the right direction that would be helpful.

Seems it was a weird python issue. Was able to wipe out any 3.8 instals and it is now working.


Disable skr test assertions

Description
Disable assertions that false fail tests. To enable again we need to be able to get the actual cluster config without using Gardener kubeconfig.
Changes proposed in this pull request:
Related issue(s)

See also #153

/kind enhancement

/test pre-kyma-environment-broker

/test pre-kyma-environment-broker


Handmade list_contains

Seems like vim.list_contains is "new" so let's do it ourselves.

Aw man, srry, I completely missed that you prepared a fix for this :(
Do you see any downsides with letting deduplicate deal with this later on?

True, if there is a dedup in the pipeline then it's not a problem.


How to add new products

hey how can i add new products and render them.
/create/product
not working..

it supposed to work. attach screenshot

you need to setup your database either locally or at mongodb.

It works. You have some errors at your end. Check console.


After deleting Network, can't use the same name (Version 1.1.8)

If I want to delete a Network and want to create a new one with the same name as the old, it doesn't work.
Before I can do that, I need to replace the Block, where I want to change it.

Fixed in dev


vscode-extensions.ms-python: 2018.12.1 -> 2019.4.11987

Motivation for this change
Package not up to date.
Things done
Used this extension for developing python projects. Debugged with it successfully, tested integration with linters such as flake / mypy. Everything still works fine (even better than previous version).

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Duplicate of #55149

Superseded by #55149 which has been merged.


Fix build issues on Unity 2021.2

I found the problem and solution for issue #36. In the WalletConnectSharp.unity package they are using the Native WebSockets plugin and this plugin creates the issue. Luckily somebody already created a PR with a fix: https://github.com/endel/NativeWebSocket/pull/54
So this PR will make the same changes and i can make a WebGL build again on Unity 2021.2.8f1.

Reviewed change, change is only to jslib in endle/NativeWebsocket. Accepting change.


Create an Entity Framework Core Package

I've got two different projects that integrate PeachtreeBus and Entity Framework Core. They both make use of class that extends Entity Framework Core's DbContext, and connects it to the PeachtreeBus ISharedDatabase. The implementation of both of those classes are for the most part identical. This strongly suggests that this code should be in a shared library, which has been made even more true since they both now have special Dispose Logic because of the way that the data connection is shared across scopes. The extended DbContext was already coupled to PeachtreeBus through ISharedDatabase, but now its not just a dependency, it has behaviors that 'knows' something about the internal functions of PeachtreeBus. See: https://github.com/simpleinjector/SimpleInjector/issues/992

So it turned out that refusing to dispose was the wrong approach. I just needed to tell Entity Framework Core that it doesn't own the connection when passing the connection in.
https://github.com/wleader/PeachtreeBus/blob/8dcde751b05e5a610c1f31b19ea7e4c87bda3a1e/PeachtreeBus.EntityFrameworkCore/SharedDatabaseDbContext.cs#L63
This resolved with https://github.com/wleader/PeachtreeBus/commit/8dcde751b05e5a610c1f31b19ea7e4c87bda3a1e


Use / in paths in the auto-generated files' header

Fixes spurious checked-out file after building on Unix machines.

Nope, that's backwards. The intent of this change is to use the same character regardless of platform. We used a regex replace because the result doesn't really matter, especially now that it's gitignored.


Type ahead: don't predict when the first character on the line is :

Some programs like git log/less use the normal buffer, we should prevent predictions for this case where the line is not wrapped, starts with :  and the cursor is on the second column (1 based).

Not sure what the expected output is here.
If I run git log, and then try typing or holding down a, nothing happens.
I have local echo set to 0

That's expected -- you should not get predictions in git log


vscode devcontainer: include more utilities and preserve fish history

See the individual commits for details.

This change it totally unrelated to any actual logic in osbuild and the test failure are just infra issues. Merging.


AllowInsecureAuthInProduction is recommended to be set to true

Under the section 'Configure the RESTful API technical profile' it states
AllowInsecureAuthInProduction. In a production environment, make sure to set this metadata to true
The recommended setting should be false.
This is the same as #78405 but on a different page.

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

ID: 781ff5da-dba7-1be3-b310-e74ddf3bbce0
Version Independent ID: d904416e-c5ba-89dd-c6d6-b8e6375b9c63
Content: REST API claims exchanges - Azure Active Directory B2C
Content Source: articles/active-directory-b2c/custom-policy-rest-api-claims-exchange.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@AquilaSands
Thanks for your feedback! We will investigate and update as appropriate.

@AquilaSands
Thank you for pointing this out! I've created a PR to update the documentation and it's currently waiting for the author to review and sign off.
I will now close out this issue. Please allow some time for the author to review and the changes to reflect.
Thank you for your time and patience!


Serve and Deploy of Functions failing after updating Admin from 10.3.0 to 11.2.0

[READ] Step 1: Are you in the right place?
I think so, yes.
[REQUIRED] Step 2: Describe your environment
See my previous report on Firebase Functions for details about my environment. Since then, I have updated my TS version to 4.6.4, which fixed the errors I initially had with Admin SDK. But now I have a fresh set of errors.

Operating System version: GH Actions image + macOS Monterey 12.5.1
Firebase Product: database, functions
Firebase SDK version: 11 (see more)
Node.js version: 16 (see more)
NPM version: 8 (see more)

The problem I'm reporting started happening after I updated Admin from 10.3.0 to 11.2.0.
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
It looks like initialization of Firebase Admin fails on launch. This happens both with serve and deploy --only functions. TSC and Lint pass fine without any issues.
Here's the console output with --debug:
[2022-10-27T11:19:49.312Z] Building nodejs source
[2022-10-27T11:19:49.312Z] Analyzing nodejs backend spec
[2022-10-27T11:19:49.319Z] Could not find functions.yaml. Must use http discovery
[2022-10-27T11:19:49.450Z] Serving at port 9007

[2022-10-27T11:19:49.568Z] Got response from /__/functions.yaml Failed to generate manifest from function source: TypeError: Cannot read properties of undefined (reading 'create')
[2022-10-27T11:19:49.570Z] Failed to parse functions.yamlincomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 1, column 60:
     ...  from function source: TypeError: Cannot read properties of unde ...
                                         ^ {"name":"YAMLException","reason":"incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line","mark":{"name":null,"buffer":"Failed to generate manifest from function source: TypeError: Cannot read properties of undefined (reading 'create')\n\u0000","position":59,"line":0,"column":59},"message":"incomplete explicit mapping pair; a key node is missed; or followed by a non-tabulated empty line at line 1, column 60:\n     ...  from function source: TypeError: Cannot read properties of unde ... \n                                         ^"}
[2022-10-27T11:19:49.583Z] shutdown requested via /__/quitquitquit

⬢  functions: Failed to load function definition from source: FirebaseError: Failed to load function definition from source: Failed to generate manifest from function source: TypeError: Cannot read properties of undefined (reading 'create') {"metadata":{"emulator":{"name":"functions"},"message":"Failed to load function definition from source: FirebaseError: Failed to load function definition from source: Failed to generate manifest from function source: TypeError: Cannot read properties of undefined (reading 'create')"}}

Relevant Code:
This is how I initialize the SDK now:
import * as functions from "firebase-functions";
import * as firebaseAdmin from "firebase-admin";

firebaseAdmin.initializeApp();

...

In another file I also have the following, but I don't think my run ever reaches that stage to require the file to run.
import * as firebaseAdmin from "firebase-admin";

private static database = firebaseAdmin.database();

...

What have I tried:

Googling, StackOverflowing, etc.
This advice, even though the official documentation does not reflect it. It doesn't fix the issue for me
Reverting back to v10, which works but is not a solution to this problem

Priority
From my POV it's high priority because the functions won't launch, but not urgent.
I can give more code/information if needed.
cc @cryptonikki @erakoviczoran

I think that api:database label is misleading, this is a failure on initialization. It impacts the DB, sure, but it seems unlikely to be related... anyway, let's see.

Looks like this is an issue that might be addressed by the functions team. Trasferring to firebase/firebase-functions


When the drawer is closed, the scroll position undesirably jumps to the top of the page and then back again

When the drawer is closed, the scroll position undesirably jumps to the top of the page and then back again
https://github.com/shadcn-ui/ui/assets/55032687/ec4af7be-5a19-4840-8879-e7e3cec87829

facing the same issue here

I guess it is supposed to take the window height rather than the full page?

https://github.com/shadcn-ui/ui/assets/145198186/f817cb37-f2b1-4f1b-bc50-d1cb0c2fdfba
same issue

I think I found a solution, the problem is scroll-behavior: smooth from html class css attribute I just removed scroll-behavior: smooth or scroll-smooth from the html.
Video.tanpa.judul.Dibuat.dengan.Clipchamp.mp4

@begalinsaf Yes, it seems to do the trick, I still want to preserve the smooth scroll behavior on my site so I added a simple hook to fix this issue:
// use-scroll-behavior.tsx
import { useEffect } from 'react'

function useScrollBehavior(isOpen: boolean) {
  useEffect(() => {
    if (isOpen) {
      document.documentElement.style.scrollBehavior = 'auto'
    } else {
      setTimeout(() => {
        document.documentElement.style.scrollBehavior = 'smooth'
      }, 1000)
    }
  }, [isOpen])
}

export default useScrollBehavior

To use it:
//...
const [open, setOpen] = useState(false)
useScrollBehavior(open)
return (
<Drawer open={open} onOpenChange={setOpen}>
  <DrawerTrigger asChild>
    <Button variant="outline">Button</Button>
  </DrawerTrigger>
  <DrawerContent>
    {/* ... */}
  </DrawerContent>
</Drawer>
)
}

I had the same issue and fixed it by setting document.documentElement.style.scrollBehavior to 'auto' when the drawer is open, and back to 'smooth' after a 400ms timeout when it closes. This short delay prevents unwanted scroll to the top on rapid interactions.

It looks like the issue was caused by vaul
Take a look here: vaul/issue

The same is happening on the

The same is happening on the "Sheet" component.

Try updating vaul dependency, the issue is already closed and it was the solution for me at the time

can anyone post code ?

The scroll-behavior: smooth property was the issue for me, i just got around it by using responsive breakpoints, so mobile wont have smooth behavior. Very annoying issue with radix ui..

Unfortunately in my case workaround for scroll-smooth did not work. This bug was hard to reproduce, I mean after adding a workaround for scroll smooth sometimes I had no issues, but after a few reloads, changing screen size the bug kept coming back. I have a sticky header that is dependent on scrolling, so drawer unreasonably messing with the scroll caused some pain here.
I ended up controlling drawer open/close state on my own without using DrawerTrigger, and it works well and I have no issues with the drawer, while having scroll-smooth always enabled on  tag.
const [isOpen, setIsOpen] = useState(false);

return (
    <Drawer open={isOpen} snapPoints={[1.05]}>
    {/* <DrawerTrigger asChild> */}
    {/* Controlling it with onClick handler because of the crazy scroll jump bug */}
	<Button variant="outlineTransparent" size="none" className="pl-1 pr-2 py-2.5" onClick={() => setIsOpen(true)}>
		Btn text
	</Button>
	{/* </DrawerTrigger> */}
	{/* Added custom prop onOverlayClick to close drawer on overlay click because of scroll jump bug */}
	<DrawerContent onOverlayClick={() => setIsOpen(false)} >

And passing onOverlayClick additional prop to close drawer when clicked on overlay
// extended with onOverlayClick because of the scroll jump bug
type DrawerContentProps = React.ComponentPropsWithoutRef<typeof DrawerPrimitive.Content> & {
  onOverlayClick?: () => void;
};
const DrawerContent = React.forwardRef<
  React.ElementRef<typeof DrawerPrimitive.Content>,
  DrawerContentProps
>(({ className, children, onOverlayClick, ...props }, ref) => (
  <DrawerPortal>
    <DrawerOverlay onClick={onOverlayClick} />

I solved it by making my navbar sticky, which is convenient in most cases, and worked for me just fine.
The problem with the vaul package is when we close the Drawer, it is an expected behavior according to the

Hey, this is expected behavior as we focus back on the trigger when the drawer closes for accessibility reasons.

Also for some reason preventScrollRestoration is not working, along with all other methods such as using useState to control the open state.
Note: I am using left direction for the drawer.
        <Drawer
            open={isOpen}
            onOpenChange={setIsOpen}
            direction='left'
        >
            <DrawerTrigger className='flex items-center justify-center gap-2 lg:hidden'>
                <Menu className='h-6 w-6' />
                Menu
            </DrawerTrigger>
            <DrawerContent
                className='left-0 right-auto top-0 mt-0 h-lvh w-3/4 rounded-none'
                onClick={(event: MouseEvent<HTMLDivElement>) => {
                    const target = event.target as HTMLElement
                    if (target.tagName === 'A') setIsOpen(false)
                }}
            >
           {/* Code... */}
        </Drawer>

Sheet and Dialog are add data-scroll-locked="1" to body and use the style below.
In my case, the problem comes from padding-top. So I made body padding-topstyle to important style and fixed it.

Thank you eukosh, your solution actually woked and is simple

Guys please help, it is still happening and I dont see anything related to the scroll-behavior: smooth
https://github.com/user-attachments/assets/2d0a4fc4-5932-45f8-aadf-74160344bff8


Make poster for Wikimania 2023

Description
As the submission (see #272) was accepted, we should make a poster. This can be based on the design in #252.

Poster: https://commons.wikimedia.org/wiki/File:Govdirectory-Wikimania2023-poster.pdf
Was printed and displayed in Singapore.


npm ERR! missing script: dev

This is now what in file "weacast/package.json". It seems there is no dev in scripts. The cmd gives me npm ERR! missing script: dev when I run npm run dev in weacast folder.
{
  "name": "weacast",
  "private": true,
  "scripts": {
    "install": "lerna bootstrap",
    "lint": "lerna run lint",
    "test": "nyc lerna run test"
  },
  "devDependencies": {
    "nyc": "^15.1.0",
    "lerna": "^4.0.0"
  }
}

debug.log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Users\\chenw\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'dev'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose stack Error: missing script: dev
4 verbose stack     at run (C:\Users\chenw\AppData\Roaming\npm\node_modules\npm\lib\run-script.js:155:19)
4 verbose stack     at C:\Users\chenw\AppData\Roaming\npm\node_modules\npm\lib\run-script.js:63:5
4 verbose stack     at C:\Users\chenw\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:116:5
4 verbose stack     at C:\Users\chenw\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:436:5
4 verbose stack     at checkBinReferences_ (C:\Users\chenw\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:391:45)
4 verbose stack     at final (C:\Users\chenw\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:434:3)
4 verbose stack     at then (C:\Users\chenw\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:161:5)
4 verbose stack     at C:\Users\chenw\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:382:12
4 verbose stack     at C:\Users\chenw\AppData\Roaming\npm\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:123:16
4 verbose stack     at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3)
5 verbose cwd D:\project\weacast\weacast
6 verbose Windows_NT 10.0.22000
7 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\chenw\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
8 verbose node v16.13.1
9 verbose npm  v6.14.16
10 error missing script: dev
11 verbose exit [ 1, true ]

Hi, I've just added a notice on the README. This repo is actually a new Weacast monorepo with all packages that will be published to the @weacast npm organization, which is a work in progress.
It was previously the repository of the weacast demo application you can now find here: https://github.com/weacast/weacast-app. Docs will be updated soon accordingly, sorry for the inconvenience.

Thanks for your contributing and the reply @claustres, good work!

I suggest not to use the master branch of the demo app now, which should not work anymore with previous weacast repos, you can use a tag if you'd really like to pull the demo app repo, otherwise rely on released docker images.

Oh no! I've been solved a thousand problems when set the development environment and finally been here.  Anyway thanks though!

@chenwei19940207 No worry, not much change in the documented environment setup, you should simply clone the demo app repo using the latest tag instead of this one and this sould work.


Creating an Azure Policy Failed

Hi,
I am trying to save the following policy definition in Azure Policies.
{
"type": "Microsoft.Authorization/policyDefinitions",
"name": "restrict-storageAccount-firewall-rules-policyDef",
"properties": {
"displayName": "Enforce Encryption Data at Rest in Storage Accounts",
"description": "This policy will enforce encryption for data at rest in storage accounts.",
"metadata": {
"category": "Storage"
},
"parameters": {
"keyVaultUri": {
"type": "String",
"metadata": {
"description": "Enter the URL of the key vault used containing the encryption key.",
"displayName": "Key Vault"
}
},
"keyName": {
"type": "String",
"metadata": {
"description": "Key used for encryption.",
"displayName": "Key Name"
}
},
"keyVersion": {
"type": "String",
"metadata": {
"description": "Version of the encryption key.",
"displayName": "Key Version"
}
},
"effect": {
"type": "String",
"metadata": {
"displayName": "Effect",
"description": "Enable or disable the execution of the policy"
},
"allowedValues": [
"DeployIfNotExists",
"AuditIfNotExists",
"Deny",
"Append",
"Disabled"
],
"defaultValue": "Disabled"
}
}
},
"mode": "All",
"policyRule": {
"if": {
"field": "type",
"equals": "Microsoft.Storage/storageAccounts"
},
"then": {
"effect": "[parameters('effect')]",
"details": {
"type": "Microsoft.Storage/storageAccounts/",
"name": "current",
"roleDefinitionIds": [
"/subscriptions//providers/Microsoft.Authorization/roleDefinitions/"
],
"existanceCondition": {
"allOf": [
{
"field": "Microsoft.Storage/storageAccounts/encryption.keySource",
"equals": "Microsoft.Keyvault"
}
]
},
"deployment": {
"properties": {
"mode": "incremental",
"template": {
"$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "<IP_ADDRESS>",
"parameters": {
"storageAccountName": {
"type": "string"
}
},
"resources": [
{
"apiVersion": "2019-04-01",
"location": "East US",
"type": "Microsoft.Storage/storageAccounts",
"name": "[parameters('storageAccountName')]",
"properties": {
"encryption": {
"keyvaultproperties": {
"keyvaulturi": "[parameters('keyVaultUri')]",
"keyname": "[parameters('keyName')]",
"keyversion": "[parameters('keyVersion')]"
},
"services": {
"file": {
"enabled": true
},
"blob": {
"enabled": true
}
},
"keySource": "Microsoft.Keyvault"
}
}
}
]
}
}
}
}
}
}
}
When I hit Save, I get the following error. I do not understand why the 'policyRule' gets null. Can some one help me figure out what I am doing wrong here?
readyState: 4
responseText: {"error":{"code":"InvalidRequestContent","message":"The request content was invalid and could not be deserialized: 'Required property 'policyRule' expects a value but got null. Path 'properties', line 1, position 770.'."}}
status: 400
statusText: error

@mudithac thanks for the comment. To get the best possible answer to your question,  Kindly post your question on the Azure technical Forum. Our community engineers who moderate the forums will be in the best position to help you with this or redirect as appropriate. This channel is reserved for issues and feedback on Documentation only. thanks for understanding.
We will now close this issue but we look forward to engaging you further.
Cheers.


selfdrive: Add Highlander 2018 LE

Add new fingerprint for Highlander

Thanks. could you please share a cabana route where you were running stock system so we can verify the fingerprint? You can DM it to me on Discord.

Add new fingerprint for Highlander

Just cloned a fresh repo and tried again this fingerprint it works. I would merge it for now and make some Highlander users happy. Thanks!

Thanks @dougsland for the submission.  Please DM @rbiasini a cabana share link for a route where you were running stock ADAS (Giraffe DIP 1001) so Comma can verify the fingerprint?

Thanks @dougsland for the submission. Please DM @rbiasini (on Discord) a cabana share link for a route where you were running stock ADAS (Giraffe DIP 1001) so Comma can verify the fingerprint. Also, let us know if your car has any modifications like an aftermarket security system, remote start, or infotainment.

Hey @ErichMoraga. Sent him, I can send again or to you. Fell free to reach me at discord too.

This is merged internally with a longer fingerprint. If you waited long enough with, you could actually find 98 messages.


Publish Release 0.9.0

Github and Project Planning

[x] Review pull requests and merge as appropriate.
[x] Review the issues assigned to the release's milestone.

User Agent

[x] Use find-and-replace to update the version number in the userAgent prefixes.
[x] Temporarily make userAgent a required parameter to RestRequest.

Tests and Verification

[x] Run all tests to verify correctness. Fix any errors.
[x] Verify that all necessary changes to .travis.yml have been made.
[x] If changes were made to Speech to Text then test continuous streaming support on a physical device.

Documentation

[x] Update the generateDocumentation.sh script for any new targets/services.
[x] Generate documentation for the gh-pages branch using generateDocumentation.sh.
[x] Fix any undocumented code. Then re-generate the gh-pages documentation.
[x] Update the change log.
[x] Update the readme.

Publish Release

[x] Use Github to create a tag/release.
[x] Ensure that Carthage successfully builds each service's framework.
[x] Celebrate the team's hard work! :)

We need to document that users who want to use the Language Translation service instead of Language Translator will need to change the service URL to specify the Language Translation service.

@glennrfisher Language Translation and Language Translator are two different services. They have the same API and one is deprecated but they should both live in the SDK. At least for 1 year until Language Translation is fully removed.


Add link to very simple introductory project

I was just getting started with Nan and found the examples were too complex to understand what is necessary for working with Nan versus incidental complexity due to line-endings or monte carlo estimations. It took me hours to get to a point where I felt like I could just get started. Hopefully my work can be the next person's starting point.
Thanks for building and maintaining such a powerful tool.

Thanks, more examples are always welcome. I'll merge this for now and release NAN 1.9 quite soon. However, big changes are coming in time for io.js 3.0 and I'll probably remove links to outdated examples for NAN 2.0, if I remember to do so. They can of course be added back at some point if the code gets updated.


Bump pywayland and pywlroots version.

Please add your info to the top of the ebuild.

Added my info.


gltfio: fix crash when material is  unspecified

I moved the inputMat = inputMat ? inputMat : &kDefaultMat.  Wups.

Wrong fix, closing.


confirmationNumber in SuccessWizardlet

https://nanopay.atlassian.net/browse/NP-8828

Why is this in foam?

Why is this in foam?

Agree, this should be another view in NP that extends SuccessWizardlet


VS Code does not treat typescript dot files like normal typescript files

VSCode Version: 1.22.2
OS Version: Arch Linux

Steps to Reproduce

Create tsconfig.json

{
  "compilerOptions": {
     "target": "es2017",
     "module": "commonjs",
     "lib": ["es2017"]
  }
}

Create 2 files: .dotfile.ts (begin with a dot) and normalfile.ts

Object.entries({})

Expected behavior
There should be no problem
Actual behavior
In .dotfile.ts, linter marks entries word with message [ts] Property 'entries' does not exist on type 'ObjectConstructor'.
Things are okay in normalfile.ts
Screenshot

Yes this is by-design. In most cases you do not want dot files included in a project.
To explicitly include dot files, try setting:
{
    "compilerOptions": {
        "target": "es2017",
        "module": "commonjs",
        "lib": [
            "es2017"
        ]
    },
    "exclude": [
        "node_modules"

    ],
    "include": [
        "**/*.ts",
        "**/.*.ts"
    ]
}

@mjbvz Still, there's inconsistency: tsc cli treats them differently (allowing them). I wouldn't complain if its behavior was consistent. My point is VS Code should only tell user what tsc cli would tell.

This issue was moved to Microsoft/TypeScript#23750


lib: os: cbprintf: Fixes for sparc and size calculation of void * argument

Similarly to runtime packaging, sparc architecture needed special treatment for unaligned storing of 64/128 bit arguments.
Additionally, there was an error in calculation of void * size in static packaging and description of Z_CBPRINTF_ARG_SIZE which relaying on older concept for cbprintf packaging.

@npitre in cbprintf you have used defines like __xtensa__, __i386__ to distinguish between platforms. I am not sure if they are C or GCC specific. Zephyr in general is using zephyr specific defines from Kconfig (e.g. CONFIG_XTENSA). Are you ok if i change them to those zephyr specific equivalents?

I don't think that is a good idea. I used compiler specific defines
because this va_list game is somewhat compiler specific too. This
appears to be the case at least for Xtensa with no official ABI
documentation I could find. In the end there is nothing actually Zephyr
specific here either.
I'd prefer to wait until some other compiler without the gcc/clang
defines shows up and potentially break the test due to unsuitable
default settings so that we can have a closer look right away.


Invalid patch?

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/github/workspace/autopr/gh_actions_entrypoint.py", line 18, in <module>
    main(
  File "/github/workspace/autopr/main.py", line 46, in main
    pr = generator.generate_pr(tree, issue_title, issue_body, issue_number)
  File "/github/workspace/autopr/services/generation_service.py", line 238, in generate_pr
    pr_model = self._generate_pr(codebase, issue_text)
  File "/github/workspace/autopr/services/generation_service.py", line 181, in _generate_pr
    raw_o, dict_o = pr_guard(
  File "/github/home/.cache/pypoetry/virtualenvs/autopr-cDQ_M3T8-py3.9/lib/python3.9/site-packages/guardrails/guardrails.py", line 101, in __call__
    return self.ask_with_validation(prompt, llm_ask, num_reasks)
  File "/github/home/.cache/pypoetry/virtualenvs/autopr-cDQ_M3T8-py3.9/lib/python3.9/site-packages/guardrails/guardrails.py", line 108, in ask_with_validation
    guard_history = self.validation_inner_loop(
  File "/github/home/.cache/pypoetry/virtualenvs/autopr-cDQ_M3T8-py3.9/lib/python3.9/site-packages/guardrails/guardrails.py", line 169, in validation_inner_loop
    validated_response, reasks = self.validate_output(
  File "/github/home/.cache/pypoetry/virtualenvs/autopr-cDQ_M3T8-py3.9/lib/python3.9/site-packages/guardrails/guardrails.py", line 239, in validate_output
    validated_response = schema[field].validate(
  File "/github/home/.cache/pypoetry/virtualenvs/autopr-cDQ_M3T8-py3.9/lib/python3.9/site-packages/guardrails/datatypes.py", line 299, in validate
    value = child_data_type.validate(
  File "/github/home/.cache/pypoetry/virtualenvs/autopr-cDQ_M3T8-py3.9/lib/python3.9/site-packages/guardrails/datatypes.py", line 259, in validate
    value = item_type.validate(i, item, value)
  File "/github/home/.cache/pypoetry/virtualenvs/autopr-cDQ_M3T8-py3.9/lib/python3.9/site-packages/guardrails/datatypes.py", line 299, in validate
    value = child_data_type.validate(
  File "/github/home/.cache/pypoetry/virtualenvs/autopr-cDQ_M3T8-py3.9/lib/python3.9/site-packages/guardrails/datatypes.py", line 126, in validate
    schema = validator.validate_with_correction(key, value, schema)
  File "/github/home/.cache/pypoetry/virtualenvs/autopr-cDQ_M3T8-py3.9/lib/python3.9/site-packages/guardrails/validators.py", line 196, in validate_with_correction
    return self.on_fail(e)
  File "/github/workspace/autopr/validators.py", line 239, in fix
    lines = remove_hallucinated_lines(lines, tree)
  File "/github/workspace/autopr/validators.py", line 108, in remove_hallucinated_lines
    check_file_line = current_file_content[check_line_number]
IndexError: list index out of range

Fixed by #11


Conflicts with existing docker/boot2docker installation

Since I already have boot2docker installed on OSX, and DOCKER_* paths in my ~/.zshrc file, this causes conflicts when I install drude.
Namely I get this error:
$ dsh up
Bringing machine 'boot2docker' up with 'virtualbox' provider...
==> boot2docker: Checking if box 'blinkreaction/boot2docker' is up to date...
==> boot2docker: VirtualBox VM is already running.
Starting containers...
SSL error: [Errno 1] _ssl.c:504: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number

Using docker ps directly I get
$ docker ps
FATA[0000] An error occurred trying to connect: Get https://localhost:2375/v1.18/containers/json: tls: oversized record received with length 20527

Issue was that I had these env flags already set:
$ printenv
...
DOCKER_CERT_PATH=/Users/fcarey/.boot2docker/certs/boot2docker-vm
DOCKER_TLS_VERIFY=1

I commented these out in my ~/.zshrc file and then it works
Potential solutions

Look for the existence of these ENV vars either before up runs or when it installs and throw a warning.

Addressed in<PHONE_NUMBER>6673c9f6fe44987dbc2d9f4d7ec07a


Review metrics recorded by middleware extensions

Ensure all metrics recorded by app metrics middleware extensions are correct and simplify where possible, also ensure metrics reporting are easily discoverable in influxdb for example.

Metrics recorded correctly, an improvement to the per request timer middleware would be to have a single timer  but tag the metric per endpoint so for example a table could automatically be show all the api's endpoints without having to manually create a new chart.
https://github.com/alhardy/AppMetrics/issues/71


multiclass?

Hi! Two questions:

Is this code adapt to multiclass instances or only for binary cases?
Is possible to have any txt example?
thanks!

The code will learn and extract embeddings which can be used for several applications, among them kNN classification, which can be multiclass.
There's no text examples checked-in at this time, but the the format is simple: anchor, positive, and negative images (paths and filenames) are supplied in text files, with aligned rows, i.e.:
anchor:
mypath/dog1.jpg
mypath/dog2.jpg
positive:
mypath/dog3.jpg
mypath/dog1.jpg
negative:
mypath/cat1.jpg
mypath/boat35.jpg
So in this example, the first triplet is (dog1, dog3, cat1) and the second triplet is (dog2, dog1, boat35).
Hope this helps.


Pkg currently not working with node-rsa 0.2.20

A couple of days ago node-rsa released version 0.2.20. This update appears to have been minor, but after updating the deps for crx my builds started failing. A quick look at the stack trace revealed this (taken directly from console):
Error: TypeError: undefined is not a function
  at jenkins-home/workspace/SignalsExtension-Master/node_modules/crx/src/crx.js:83:13
  at $$$internal$$tryCatch (jenkins-home/workspace/SignalsExtension-Master/node_modules/crx/node_modules/es6-promise/dist/es6-promise.js:304:16)
  at $$$internal$$invokeCallback (jenkins-home/workspace/SignalsExtension-Master/node_modules/crx/node_modules/es6-promise/dist/es6-promise.js:316:17)
  at jenkins-home/workspace/SignalsExtension-Master/node_modules/crx/node_modules/es6-promise/dist/es6-promise.js:874:13
  at $$asap$$flush (jenkins-home/workspace/SignalsExtension-Master/node_modules/crx/node_modules/es6-promise/dist/es6-promise.js:111:9)
  at process._tickCallback (node.js:419:13)

Manually hard-coding the node-rsa dependency in package.json seems to totally resolve the issue. I will try to post more detailed logging shortly, but this happened on a Jenkins box so I don't have the full logs.
As a side note: I am loading a key.pem file into crx via a string buffer, then packing an extension.

@erikmunson thanks for your report. You might double post it on the node-rsa issue tracker. If a method got deprecated/removed, its maintainer should have bumped the major version.

@oncletom Perfect, will do.

@oncletom Turns out this was a small bug in v0.2.20 that just got patched in v0.2.21. Tested on the build which had been failing and works great. Thanks for prompting to cross-post on node-rsa!
Details: https://github.com/rzcoder/node-rsa/issues/32

That's great :-) I love solving problems without writing a single line of code ;-)

Amen!


sbt-blockade does not work with sbt-coursier (for transitive dependency violations?)

It seems, at least from my experiments, that sbt-blockade does not play nice with sbt-coursier for transitive dependency violations. It seems to work fine for direct dependencies. Here is my reproduction:
build.sbt
scalaVersion := "2.12.1"

blockadeUris := Seq(new java.net.URI(s"file:///${baseDirectory.in(ThisBuild).value}/blockade.json"))

compile in Compile := { blockade.value; (compile in Compile).value }

libraryDependencies += "co.fs2" %% "fs2-io" % "0.9.6"

blockade.json
{
  "blacklist": [
    {
      "organization": "co.fs2",
      "name": "fs2-core",
      "range": "(,0.9.6]",
      "expiry": "2017-09-21 00:00:00"
    }
  ]
}

project/plugins.sbt
addSbtPlugin("io.verizon.build"  % "sbt-blockade" % "0.2.35")
// addSbtPlugin("io.get-coursier" % "sbt-coursier" % "1.0.0-RC3")

project/build.properties
sbt.version=0.13.15

Running blockade warns as expected. Un-commenting the sbt-coursier plugin and running again says it succeeds.
If the fs2-io dependency is changed to fs2-core then it seems to succeed with or without Coursier :man_shrugging:

@adelbertc i'm not sure what you're seeing here, but we use the two together without issue. If you collect more information then i'll happily reexamine this :-)

@timperrett The above is what I am seeing, those files are the reproduction. Without sbt-coursier blockade will warn, with it it passes.


OpenShift - error validating existing CRs against new CRD's schema

hello,
We had HPE CSI Driver 2.1.0 installed and we were showing an update for 2.2.0 in the Installed Operators page, after clicking update, I am seeing this error:
"error validating existing CRs against new CRD's schema for "hpecsidrivers.storage.hpe.com": error validating custom resource against new schema for HPECSIDriver hpe-csi-driver/csi-driver: [[].spec.csp: Required value, [].spec.controller: Required value, [].spec.node: Required value]"

Hi,
It looks like the older operator exists and there is an attempt to install a newer version. Can you tell us how did you upgrade the operator ?

The upgrade requires you to follow the instructions at the Scod Page :
https://scod.hpedev.io/partners/redhat_openshift/index.html#upgrading
After all "uninstall" steps in the instructions are completed and before installing the new operator, there is one additional step (not yet mentioned in scod) that you would need to do.
oc delete crd hpecsidrivers.storage.hpe.com
After this, you can proceed to install the latest v2.2.1 operator.

Can you tell us how did you upgrade the operator ?

Through the GUI in the Operators page, I simply clicked the upgrade button and got the errors above. The old operator is still there, I now have the old and the new one and both are errored out, but no impact to PVCs.
I can go ahead and uninstall the operator to solve this issue, but just to clarify, does that not impact my current running PODs with persistent storage accounts through this operator? Can I safely do that without ruining anything? The thought of "uninstall" is a little concerning.

Just wanted to verify if uninstalling the operator is going to have any impact on my currently running pods.

Just wanted to verify if uninstalling the operator is going to have any impact on my currently running pods.

No. PVs, PVCs and StorageClasses remain unaffected while uninstalling and deleting the HPECSIDriver resources and Operator. In-flight CSI operations and new requests will be retried once the new CSI driver is instantiated.

Thank you so much for the confirmation! One last question, how can I successfully get rid of HPECSIDriver? The contenxt menu in the GUI is grayed out

I could really use some help here! This "simple" upgrade process is slowly turning into a nightmare! I tried reaching out to Red Hat too and they said to reach out to you.
I am not sure how to get rid of HPECSIDriver before uninstalling the operator! Everything is grayed out. The only thing I can do is to uninstall the operator itself.

I finally got it! (What's a few heart attacks here and there?)
The HPECSIDriver CRD was not properly terminating so when I uninstalled the operator and installed again, the same HPECSIDriver was present. I manually removed the finalizers from HPECSIDriver and then it was deleted, uninstalled the operator, installed the operator again, created a new HPECSIDrive instance and everything worked! All while not impacting my current bound PVCs/PVs.
Thank you all for the help as I get more familiar with this upgrade process!

Thank you all for the help as I get more familiar with this upgrade process!

I apologize you had to go through this. We have not officially shipped yet and we have documentation that more clearly outlines the steps to "upgrade". It will be published next week and the page you're bookmarking is this one: https://scod.hpedev.io/partners/redhat_openshift/index.html

I am just glad it's working now!
Honestly, the upgrade documentation could use some clarification. Maybe a note indicating that it is OK to "remove the driver and uninstall the operator, it will not impact any running pods with persistent storage. Clarify what is OK to be deleted and what is not! I identify all the important resources and how to get to them.
When I had a chat with Red Hat, they wanted me to delete the whole project and re-create - I said nope! Not knowing whether it was OK or not, the whole thought of "delete/uninstall" and recreate is concerning in general.
That said, I do have a supported OpenShift cluster and I'm happy to contribute if needed.

I'm still a little puzzled about how the official upgrade procedure works.
Why aren't the CRDs simply versioned cleanly so that an in-place upgrade works?

Why aren't the CRDs simply versioned cleanly so that an in-place upgrade works?

Because it's not a real "Operator". It's a Helm chart. A Helm chart packaged in an Operator as per Red Hat's guidelines on how to provide certified CSI drivers to OpenShift. Helm charts does not manage CRDs as you may know.

Yes got it - thanks for clarification! Good to know!
We may switch to the helm installation directly than instead of the "operator catalog" installation.


LSP support

Zed has landed support for lsp-s in the preview, so could you add kotlin language server (https://github.com/fwcd/kotlin-language-server) support

I'm working on Docker Compose support rn but happy to fork Kotlin and pick this one up after ^^

Hey thanks for reaching out, I'm not looking to maintain the Kotlin extension for Zed anymore and I'd be happy to let someone else take over, I've let the extension be available as there currently seem to be no other alternative.
I'm not sure how this would work, but if you're interested in maintaining it instead maybe githubs ownership transfer feature might work, or maybe you can fork this repository and i pr a removal of this one from the extensions repo?

@evrsen You could transfer the repo to the @zed-extensions org and we can add anyone who wants to help maintain it.

Sound good to me @maxdeviant , i tried transferring but got this error

Ah, I see.
Could you try transferring it to me? And then I can transfer it into the organization.

Done 👍

Is anyone actively working on kotlin lsp support? If not I might

@cholwell You can probably help out at https://github.com/zed-extensions/zed-kotlin

@maxdeviant what is the difference between https://github.com/zed-industries/zed/tree/2ee257a5621d3c2714945e117d958383c14ae513/extensions and https://github.com/zed-extensions ?

@maxdeviant what is the difference between https://github.com/zed-industries/zed/tree/2ee257a5621d3c2714945e117d958383c14ae513/extensions and https://github.com/zed-extensions ?

The extensions/ directory in the Zed repo is for languages that were previously built in to Zed that we extracted into extensions. We kept them in the Zed repo to make it easier to iterate on them. At some point they will likely move out into their own repositories.
The @zed-extensions org is for extensions that that are maintained (at least in part) by the Zed team. We will accept interested parties to help maintain them, though.

So I made some progress:

If I download and build the lsp from source and hardcode the command in extension it will run... however it wont highlight the majority of compliation errors ?
Trying to get the extension to download from https://github.com/fwcd/kotlin-language-server/releases fails with 'failed to unzip name archive'

Will have another go at some point but if anyone wants to help, or has any insight on either point let me know.

So I made some progress:
* If I download and build the lsp from source and hardcode the command in extension it will run... however it wont highlight the majority of compliation errors ?

* Trying to get the extension to download from https://github.com/fwcd/kotlin-language-server/releases fails with 'failed to unzip _name_ archive'

Will have another go at some point but if anyone wants to help, or has any insight on either point let me know.

Could you show me the code you've written so far?

https://github.com/cholwell/zed-kotlin/blob/main/src/kotlin.rs @WeetHet

https://github.com/cholwell/zed-kotlin/blob/main/src/kotlin.rs @WeetHet

I not sure if I'm right, but in my extension, I download to the binary_path, not version_dir. Could you try that?

@WeetHet I believe the whole installation zip is required due to it containing jar dependencies,
also I tried it and it fails with no such file or directory so not sure

working https://github.com/zed-extensions/zed-kotlin/pull/8

@WeetHet please can you close issue now PR is merged

Language server support is available now in v0.0.3 of the Kotlin extension.

Hey @maxdeviant you said lsp support added, but its not working.

Hello @maxdeviant i fixed the issue with lsp not working in windows, and it working fine in windows

@spaceunifyfifty yeah ive done that its now fixed with #16


[Idea] 0042 MetaMask Snap for the XRP Ledger

View Proposal Here

Create a UI / library for event organizer to mint and distribute Proof of Attendance NFTs (with event metadata - <date, description, cover art...> embedded in memo field)


Propose to add Freeze Keyboard&Mouse feature

Description of the new feature / enhancement
Freeze the keyboard and the mouse so that no unintended operations will be mistakenly done.
Scenario when this would be used?
Sometimes, I want to put something on the keyboard or the cat just walk on it, or I put the wireless mouse into the bag without turning the mouse and the PC off.
Supporting information
No response

Could also useful when cleaning the PC/Keyboard

Freeze for 'x' period of time would be one way, but that might be not flexible enough. A better way might be to input a fixed sequence of code or press a certain combination of keys. A maximum time could also be set in case that the code or keys are forgoten.


Gap between panels leads to some panels' size overflow

Describe the bug
Having a layout with nested branches and gaps between panels (--dv-group-gap-size: 0.5rem;) leads to some panels' overflowing their expected boundaries (panels 4 and 5 in the screenshot)

To Reproduce
Steps to reproduce the behavior:

Go to https://stackblitz.com/edit/vitejs-vite-wsic2s?file=src%2FApp.tsx,src%2Findex.css
See that panels' 4 and 5 are bigger than expected and overflow over the gap between panels

Expected behavior
Nested panels respect gaps in their sizing calculation
Screenshots
^
Desktop (please complete the following information):

Browser Chrome
Version 124.0.6367.208

Additional context
-

Release in 1.14.1

@mathuo the fix breaks group's custom styling (like border radius) 😅 you can check this at the demo page with replit theme
after update

before (i just disabled gap's border style for one case, border radius is back)

@mathuo the fix breaks group's custom styling (like border radius) 😅
you can check this at the demo page with the replit theme (i also made the gap bigger to showcase the issue)
after update
before (with border gap back to .view, border radius and color are back)

damn, I guess this needs a bit more though. Let me have a think

1.15.0 now uses a prop gap defined in pixels . The CSS property --group-gap-size is no longer used.
Let me know if this does the trick.

@mathuo looks like passing gap={6} to the DockviewReact component doesn't work - https://stackblitz.com/edit/vitejs-vite-9f1xvv?file=src%2FApp.tsx,package.json

Looks like I missed testing this directly through React and only tested through the api object - should all be working as expected in 1.15.1.

@mathuo it works, thx a lot )


Initial release of cluster-standup-teardown module

What does this PR do?
Towards https://github.com/giantswarm/giantswarm/issues/30661
Added

ClusterBuilder for CAPA, CAPV, CAPVCD, CAPZ and EKS along with default values for each
standup and teardown modules for use in other projects
standup and teardown CLIs
Dockerfile containing the two CLIs

The majority of this code is copied over from cluster-test-suites and modified slightly to make it more useful across multiple applications.
Still outstanding but not to be included in this PR:

Merging of values files (currently any provided values files overrides the ones found in this repo)

Checklist

[x] CHANGELOG.md has been updated

I find it weird that the pkg/clusterbuilder/providers doesn't follow the provider names from https://github.com/giantswarm/clustertest/blob/main/pkg/application/cluster_app.go#L23.
leaving that aside, the PR looks good in general

I find it weird that the pkg/clusterbuilder/providers doesn't follow the provider names from<EMAIL_ADDRESS>
Naming is hard 😅  The term provider means different things in different context and it get super confusing 😞  I might see if I can clean that up somewhat. I don't think switching these to the same as the providers you linked to is best though as importing cloud-director as a module is a pain and needs renaming when importing. We've also have a bunch of confusion about if it's cloud-director or clouddirector etc.

Once change I have done based on that is to move the EKS builder under capa. It doesn't make sense to be split out in this module (but makes sense in cluster-test-suites as triggered by different PRs).


AttributeError: 'ShowZetaOnHalfPlane' object has no attribute 'y_min'

When I run
python extract_scene.py -p old_projects/zeta.py ShowZetaOnHalfPlane

I have the following error
Writing "\zeta( s )= \frac{1}{1^s} +  \frac{1}{2^s} +  \frac{1}{3^s} +  \frac{1}{4^s} +  \cdots" to /Users/laurent/Work/xxxx/manim/files/Tex/-5201468256000681301.tex
Writing "\zeta(" to /Users/laurent/Work/xxxx/manim/files/Tex/3529308138940232413.tex
Writing ")=" to /Users/laurent/Work/xxxx/manim/files/Tex/8430908102380925009.tex
Writing "\frac{1}{1^s} +" to /Users/laurent/Work/xxxx/manim/files/Tex/1583025563881409802.tex
Writing "\frac{1}{2^s} +" to /Users/laurent/Work/xxxx/manim/files/Tex/6484072650047720569.tex
Writing "\frac{1}{3^s} +" to /Users/laurent/Work/xxxx/manim/files/Tex/1463901432775095568.tex
Writing "\frac{1}{4^s} +" to /Users/laurent/Work/xxxxs/manim/files/Tex/5428990312259487727.tex
Writing "\cdots" to /Users/laurent/Work/xxxx/manim/files/Tex/5511331107690932742.tex

Traceback (most recent call last):
  File "extract_scene.py", line 206, in main
    handle_scene(SceneClass(**scene_kwargs), **config)
  File "/Users/laurent/Work/xxxx/manim/scene/scene.py", line 52, in __init__
    self.construct(*self.construct_args)
  File "/Users/laurent/Work/xxxx/manim/./old_projects/zeta.py", line 1760, in construct
    self.initial_transformation()
  File "/Users/laurent/Work/xxxx/manim/./old_projects/zeta.py", line 1788, in initial_transformation
    self.add_extra_plane_lines_for_zeta(animate = True)
  File "/Users/laurent/Work/xxxx/manim/./old_projects/zeta.py", line 84, in add_extra_plane_lines_for_zeta
    dense_grid = self.get_dense_grid(**kwargs)
  File "/Users/laurent/Work/xxxx/manim/./old_projects/zeta.py", line 98, in get_dense_grid
    max(self.y_min, self.extra_lines_y_min),
AttributeError: 'ShowZetaOnHalfPlane' object has no attribute 'y_min'

sh: play: command not found

Solved by adding in CONFIG :
"y_min" : 1,
"y_max" : int(SPACE_WIDTH+2),

Noticed also missing image Riemann :
photo = ImageMobject("Riemann", invert = False)

Closing, since this issue seems to be resolved.


Public cloud: Update readme with links to per project contribution guidelines

GitHub repo: https://github.com/canonical/ubuntu-cloud-docs
Update the repo's readme.rst file to include links to each sub-project's contribution guidelines. There are 7 sub-projects, each with its own 'Contribute to these docs' page. So put links to them, e.g. this is the link to the AWS project.

@k-dimple I would like to work on this issue.

Sure Keith, done! Thanks!


Version 1.0.0

🧋 Backstage AWS CloudFormation Plugin 🧋

Backstage plugin which pulls entities from AWS CloudFormation stacks metadata.
Setup

Setup AWS profile credentials on your machine

# ~/.aws/credentials
[myProfile]
aws_access_key_id=AKIAIOSFODNN7EXAMPLE
aws_secret_access_key=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

Learn more in AWS documentation here.

Add Backstage notation to your CloudFormation template's Metadata section

Make sure to put the notation to correct path: Metadata.Backstage.Entities.

Click to show content of the template example
AWSTemplateFormatVersion: 2010-09-09
Resources:
  MyLambdaFunction:
    Type: 'AWS::Lambda::Function'
    Properties:
      FunctionName: my-lambda
Metadata:
  Backstage:
    Entities:
      - apiVersion: backstage.io/v1alpha1
        kind: Component
        metadata:
          name: petstore
          namespace: external-systems
          description: Petstore
        spec:
          type: service
          lifecycle: experimental
          owner: 'group:pet-managers'
          providesApis:
            - petstore
            - internal/streetlights
            - hello-world
      - apiVersion: backstage.io/v1alpha1
        kind: API
        metadata:
          name: petstore
          description: The Petstore API
        spec:
          type: openapi
          lifecycle: production
          owner<EMAIL_ADDRESS>          definition:
            $text: 'https://petstore.swagger.io/v2/swagger.json'

If you have a standalone app (you didn't clone this repo), then do

# From your Backstage root directory
cd packages/backend
yarn add backstage-aws-cloudformation-plugin

Add the CloudFormationRegionProcessor and CloudFormationStackProcessor processors your catalog builder

// In packages/backend/src/plugins/catalog.ts
import {
	CloudFormationRegionProcessor,
	CloudFormationStackProcessor,
} from 'backstage-aws-cloudformation-plugin';

export default async function createPlugin(
	env: PluginEnvironment,
): Promise<Router> {
	const builder = await CatalogBuilder.create(env);

    // Here add the catalog processors
	builder.addProcessor(new CloudFormationStackProcessor(env.config));
	builder.addProcessor(new CloudFormationRegionProcessor(env.config));

	const {
		entitiesCatalog,
		locationsCatalog,
		locationService,
		processingEngine,
		locationAnalyzer,
	} = await builder.build();

Optionaly add default profile configuration

# In app-config.yaml
integrations:
  aws:
    profile: purple-technology

Add Locations

# In app-config.yaml
catalog:
  locations:
    # Pull single stack from the profile "myProfile"
    - type: aws:cloudformation:stack
      target: myProfile@arn:aws:cloudformation:ap-southeast-1:123456789000:stack/some-stack/123-345-12-1235-123123
    # Pull single stack from the default profile
    - type: aws:cloudformation:stack
      target: arn:aws:cloudformation:eu-central-1:123456789000:stack/other-stack/532-123-59-593-19481
    # Pull whole region from the "myProfile" profile
    - type: aws:cloudformation:region
      target: myProfile@ap-southeast-1
    # Pull whole region from the default profile
    - type: aws:cloudformation:region
      target: eu-central-1

Location types
aws:cloudformation:stack
Accepts as a target ARN of the CloudFormation stack and optionally also name of the profile separated by @.
[profileName@]stack_arn

aws:cloudformation:region
Accepts as a target ID of the AWS region and optionally also name of the profile separated by @.
[profileName@]region-name-1

Features

Pull arbitrary number of Backstage entities from CloudFormation stack's Metadata
Scan whole CloudFormation region
Use multiple AWS profiles/accounts

Limitations

The plugin has built-in mechanism for dealing with throttling, but in case of indexing a whole region be careful with the number of stacks in the region

Codecov Report

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

@@            Coverage Diff             @@
##             master        #1   +/-   ##
==========================================
  Coverage          ?   100.00%
==========================================
  Files             ?         7
  Lines             ?        96
  Branches          ?        22
==========================================
  Hits              ?        96
  Misses            ?         0
  Partials          ?         0

Continue to review full report at Codecov.

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

Docs: https://backstage.io/docs/features/software-catalog/external-integrations


Make cancel job integration tests more reliable

Motivation for this is that these integration tests regularly fail - wasting a lot of our time + preventing images getting pushed
Adding a sleep to allow time for the submitted job to get through pulsar into redis before we cancel

If the job isn't in redis when the cancel is called, the job doesn't get cancelled. This leads to it running and the test failing

Adding filtering - as if the job gets Leased before the cancel - it breaks the expected events

Now we just ensure we get the expected cancel events in the expected order - but ignore intermediate events

This is a workaround

Long term we need to make it so the cancel happens async - so the cancel gets put onto pulsar after the job submission

This will mean it should always work

Codecov Report
Base: 46.52% // Head: 46.52% // No change to project coverage :thumbsup:

Coverage data is based on head (2b45014) compared to base (bdfa894).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2164   +/-   ##
=======================================
  Coverage   46.52%   46.52%
=======================================
  Files         223      223
  Lines       33054    33054
=======================================
  Hits        15378    15378
  Misses      16442    16442
  Partials     1234     1234

Flag
Coverage Δ

armada-server
46.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Create more robust unit tests for structured requests

In GitLab by @jakebeal on Aug 26, 2019, 10:17
Right now, the unit test for structure requests tests shallowly; it needs to inspect deeply.

In GitLab by @nwalczak on Sep 5, 2019, 11:58
One thing this should include is running the cp-requests repos validation script against the generated structured request.

In GitLab by @nwalczak on Sep 12, 2019, 09:03
created branch 93-create-more-robust-unit-tests-for-structured-requests

In GitLab by @nwalczak on Sep 12, 2019, 09:03
mentioned in merge request !56

In GitLab by @nwalczak on Sep 16, 2019, 09:33
closed via merge request !56

In GitLab by @nwalczak on Sep 16, 2019, 09:33
closed via commit 2e52bf23f5adb9d6ac8311b673abf8393f253e18

In GitLab by @nwalczak on Sep 16, 2019, 11:47
mentioned in commit 2e52bf23f5adb9d6ac8311b673abf8393f253e18


Problem installing .net core on ubuntu 16.04

Hi I tried to install .NET CORE 2.2 runtime on an Ubuntu 16.04 x32 (i686)machine but I am not able.I already have apache2 installed and I need to run .NET CORE Web Applications on it for publishing. Could you please suggest me what to do?

Please give us some details. How are you trying to install .NET Core 2.2, and what isn't working when you try it?

The getting started ASP.NET Core tutorial may give you some ideas.

Closing out, please re-open with some more detail if you still need help.


Add @simplewebauthn/typescript-types to dependencies of @simplewebauthn/server

Describe the issue
Because of type package is not listed in regular dependencies of server package, I have some problems with type inference in VSCode, as the compiler tries to get types from @simplewebauthn/typescript-types, which is not installed, as it listed only in devDependencies, and not in dependencies.
Reproduction Steps

Install @simplewebauthn/server via npm
Call generateAuthenticationOptions, assign result to variable
Try to access any field of result, and get advantage of type hinting in VSCode. There will be no hint, also there will be no type checking for the argument of generateAuthenticationOptions

Expected behavior
Type hints are displayed in the IDE
Code Samples + WebAuthn Options and Responses
https://github.com/dkonasov/simplewebauthn-types-demo/blob/main/index.ts#L5
Dependencies

OS: macOS 12.0.1
Node/NPM 18.12.0/8.19.2
Typescript 4.9.5

SimpleWebAuthn Libraries

$ npm list --depth=0 | grep @simplewebauthn
<EMAIL_ADDRESS># ...

@dkonasov Thank you for reporting this, I'm realizing now that I should have had typescript-types included in "dependencies" this whole time. I'll go ahead and update that so everyone always gets the types too.

@dkonasov I just published<EMAIL_ADDRESS>(and<EMAIL_ADDRESS>that should resolve this issue 🚀


Fix some race conditions

Run every package on travis
No more race condition in shard.GetStats
No more race condition in shard.del
New TestParallel test to have Set, Get, Del operations running in parallel.

Coverage decreased (-10.4%) to 87.642% when pulling a194b31ca557895215b625cc0d271e7f02a57ee1 on cristaloleg:fix-race-cond into 03db05b7c6e2ffe08b3f4818c8e8e73476580772 on allegro:master.

I've a proposal to disable coverage for server package :D


No SOURCES given to target: Games

I installed all dependencies and ran cmake .. inside the build directory after creating it.
This was  the output:
-- Caffe2: CUDA detected: 10.2
-- Caffe2: CUDA nvcc is: /usr/local/cuda-10.2/bin/nvcc
-- Caffe2: CUDA toolkit directory: /usr/local/cuda-10.2
-- Caffe2: Header version is: 10.2
-- Found cuDNN: v8.1.0  (include: /usr/include, library: /usr/lib/x86_64-linux-gnu/libcudnn.so)
-- /usr/local/cuda-10.2/lib64/libnvrtc.so shorthash is 08c4863f
CMake Warning at /opt/conda/lib/python3.8/site-packages/torch/share/cmake/Caffe2/public/utils.cmake:365 (message):
In the future we will require one to explicitly pass TORCH_CUDA_ARCH_LIST
to cmake instead of implicitly setting it as an env variable.  This will
become a FATAL_ERROR in future version of pytorch.
Call Stack (most recent call first):
/opt/conda/lib/python3.8/site-packages/torch/share/cmake/Caffe2/public/cuda.cmake:483 (torch_cuda_get_nvcc_gencode_flag)
/opt/conda/lib/python3.8/site-packages/torch/share/cmake/Caffe2/Caffe2Config.cmake:88 (include)
/opt/conda/lib/python3.8/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:68 (find_package)
CMakeLists.txt:15 (find_package)
-- Added CUDA NVCC flags for: -gencode;arch=compute_52,code=sm_52;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86;-gencode;arch=compute_86,code=compute_86
CMake Deprecation Warning at Unit_Tests/lib/CMakeLists.txt:4 (cmake_minimum_required):
Compatibility with CMake < 2.8.12 will be removed from a future version of
CMake.
Update the VERSION argument  value or use a ... suffix to tell
CMake that the project does not need compatibility with older versions.
CMake Deprecation Warning at Unit_Tests/lib/googlemock/CMakeLists.txt:45 (cmake_minimum_required):
Compatibility with CMake < 2.8.12 will be removed from a future version of
CMake.
Update the VERSION argument  value or use a ... suffix to tell
CMake that the project does not need compatibility with older versions.
CMake Deprecation Warning at Unit_Tests/lib/googletest/CMakeLists.txt:56 (cmake_minimum_required):
Compatibility with CMake < 2.8.12 will be removed from a future version of
CMake.
Update the VERSION argument  value or use a ... suffix to tell
CMake that the project does not need compatibility with older versions.
-- Configuring done
CMake Error at Games/CMakeLists.txt:92 (add_library):
Cannot find source file:
/notebooks/AlphaZero/Games/include/TicTacToe/Gamelogic.h

Tried extensions .c .C .c++ .cc .cpp .cxx .cu .m .M .mm .h .hh .h++ .hm
.hpp .hxx .in .txx .f .F .for .f77 .f90 .f95 .f03 .ispc
CMake Error at Games/CMakeLists.txt:92 (add_library):
No SOURCES given to target: Games
CMake Generate step failed.  Build files cannot be regenerated correctly.

It's been a while since i've builded it for Linux. So right now only Windows is supported.
But i'll update it on the weekend so that Linux is again supported.


Docs: Add example exclude entry matching all tags

There was no example of the match pattern used other than "patterns (in the grep sense)", which tripped me up as I was using unescaped + in my patterns which didn't match anything. An example here should help avoid others' confusion :smile:

Thanks @dgoodlad !
Small question though - the script basically passes the output of docker images (after some transforms) to the standard input of grep -f <file containing excludes> . So instead of matching redis:[^ ]\+ (to match any tag of the redis image I presume) couldn't you also just have the pattern be redis: ?

@mattnworb I tried that, but discovered after winding through the code that the patterns here get transformed by https://github.com/spotify/docker-gc/blob/0c808722e4b47b3d915a4d8a0ae5a7358420ffbf/docker-gc#L113, adding a space to the beginning and end, like so:
redis: -> redis:
redis:[^ ]\+ -> redis:[^ ]\+
The former will not match redis:latest, while the latter will.
The extra spaces were what made figuring out exactly how to use the "grep style" pattern matching work :smile:

Gotcha, thanks for clarifying.


does udocker work without access to the internet?

I apologize for the question since I am a new user and not very computer literate. Does udocker require access to the internet to function? I can use udocker locally on my linux partition of my laptop and my directory (head node) of my institution's computer cluster. The reason I ask if udocker runs without internet access is that I can't get "udocker run" or even "udocker help" to run on the compute nodes/target/execute machines of our HPC. I know the compute nodes of our HPC do not have access to the internet. Having access or not to the internet is the only difference I am aware of between my directory on the head node and the compute nodes. Our system administrator is MIA and no one has been onsite since mid-March. I know the eventual plan is to give the compute nodes access to the internet (and reinitialize Docker- which had been turned off to perform an update several months ago). When I run udocker on a target/execute machine I get the following error:
Traceback (most recent call last):
File "./udocker", line 8547, in
sys.exit(Main().start())
File "./udocker", line 8486, in init
self.udocker = Udocker(self.localrepo)
File "./udocker", line 7095, in init
self.dockerioapi = DockerIoAPI(localrepo)
File "./udocker", line 5857, in init
self.curl = GetURL()
File "./udocker", line 5529, in init
self._select_implementation()
File "./udocker", line 5537, in _select_implementation
elif GetURLexeCurl().is_available():
File "./udocker", line 5726, in is_available
return bool(FileUtil("curl").find_exec())
File "./udocker", line 1336, in find_exec
cmd = self._find_exec(["type", "-p", self.basename])
File "./udocker", line 1322, in _find_exec
exec_pathname = Uprocess().get_output(cmd_to_use)
File "./udocker", line 410, in get_output
close_fds=True)
File "./udocker", line 400, in check_output
return subprocess.check_output(*popenargs, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 567, in check_output
process = Popen(stdout=PIPE, *popenargs, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 711, in init
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 13] Permission denied
Any help would be greatly appreciated.
Thanks
Matt

Hi,
It seems that the compute nodes do not have the pycurl module for python 2, then udocker tries to locate the curl executable using type but also fails. Check that the command type is in your path in the compute nodes and that it works. udocker uses which or type to locate other Linux commands. If this is fixed and the home is shared across the cluster it should work.

Thank you so much. Like I said I have pretty much no experience with python. I will fiddle around with your suggestions. I was also thinking about trying to run udocker in a virtualenv to see if that helps by giving me some more control over the python2 environment udocker run in (not sure if that is an actual viable solution).


In Storybook dragging gets stuck when long-pressing on Android

This doesn't work in Chrome on Android:
https://5fc05e08a4a65d0021ae0bf2-unebtvimdp.chromatic.com/?path=/story/presets-sortable-vertical--press-delay
https://user-images.githubusercontent.com/3730074/148017262-96c212fe-5780-4fc3-8f2c-40ce8447966a.mp4

Can you replicate the issue on this URL?

The same problem:
https://user-images.githubusercontent.com/3730074/148562333-1472e9a6-176a-48c1-847f-375faec857e1.mp4

I did not reproduce this with Press Delay, but the same problem occurs with the following two.

https://5fc05e08a4a65d0021ae0bf2-xdfdwqtypr.chromatic.com/iframe.html?id=presets-sortable-virtualized--basic-setup&args=&viewMode=story
https://5fc05e08a4a65d0021ae0bf2-xdfdwqtypr.chromatic.com/iframe.html?id=presets-sortable-integration-with-other-libraries--framer-motion&args=&viewMode=story

Environment

OS

Android 12 (Galaxy S21 & Galaxy Z Fold 3)

Browser

Chrome
Opera

The problem occurs on chrome for android because of the redesigned long-press context menu since chrome 78.
An easy fix is to use user-select: none; a.k.a userSelect: 'none', in your container style.

Thank you @Knaackee , had the same problem for a while.
Unfortunately, the container for me is not enough since I have elements that are close to others and being precise would require another context or props drilling to set another upper state to apply the class (since the text should be selectable while not dragging).
I have solved with pure JS/CSS:
body.is-dragging {
  * {
    user-select: none;
  }
}

// Apply to any DnD context
<DnDContext
  onDragStart={() => document.body.classList.add('is-dragging')}
  onDragEnd={() => document.body.classList.remove('is-dragging')}
>

Wondering if it can be something we can control via DnD context prop in the library?


Fix outdated comments in MemoryPool

All query pools no longer have the same parent (in fact, they have
no parent).
Each MemoryPool also no longer uses "raw pointers" to record its
children.
MemoryUsageTracker has already been merged into MemoryPool.

@xiaoxmeng  Could you please help to review, thanks.

Friendly ping, please take a look. @xiaoxmeng

@xiaoxmeng Friendly ping, please take a look.


lil_matrix 2d logical indexing not working as expected

Using sparse lil_matrix, I'm trying to pull out a block within a larger matrix, but my logical indexing returns a 1D array (shape 1x2) instead of the expected 2D array (shape 2x2):
Reproducing code example:

# test_code
lilm = sparse.lil_matrix(np.array([[1, 1, 0], [1, 1, 0], [0, 0, 1]]))
inds = np.squeeze(lilm[0, :].toarray() != 0)
out = lilm[inds, inds].toarray()
print(out.shape)

>>> (1, 2)

Scipy/Numpy/Python version information:
1.3.0 1.16.4 sys.version_info(major=3, minor=6, micro=2, releaselevel='final', serial=0)

This is old and I hope you've figured it out @alexchartier, but this isn't a bug. Sparse is correctly replicating numpy indexing here.  For example:
In [1]: import numpy as np

In [2]: from scipy import sparse

In [3]: a = np.arange(9).reshape(3,3)

In [4]: index = np.array([True, False, True])

In [5]: m = sparse.lil_matrix(a)

In [6]: a[index, index]
Out[6]: array([0, 8])

In [7]: m[index, index].toarray()
Out[7]: array([[0, 8]], dtype=int64)

You can use np.ix_ to get the result you're looking for:
In [8]: a[np.ix_(index, index)]
Out[8]:
array([[0, 2],
       [6, 8]])

In [9]: m[np.ix_(index, index)].toarray()
Out[9]:
array([[0, 2],
       [6, 8]], dtype=int64)

And the results without np.ix_ can be under stood by inserting nonzero() on both of the boolean indexing arrays:
In [11]: a[index.nonzero(), index.nonzero()]
Out[11]: array([[0, 8]])


Undefined index: #theme-name

Fresh install. Get this error message when trying to access the following paths.
PATH = /admin/themes
at HandleExceptions->handleError('8', 'Undefined index: #theme-name', '/Users/david/Sites/IdeaSpace/app/Http/Controllers/Admin/ThemesController.php', '96', array('user' => object(User), 'directories' => array('themes/hello-world', 'themes/photo-sphere-diver', 'themes/photosphere-viewer', 'themes/timeline'), 'e' => object(ModelNotFoundException), 'directory' => 'themes/timeline', 'theme' => object(Theme), 'themes' => object(Collection), 'themes_mod' => array(array('id' => '1', 'theme-name' => 'Hello World', 'theme-description' => 'An example theme using a textinput control.', 'theme-version' => '1.0', 'theme-author-name' => 'IdeaSpace', 'theme-author-email' =><EMAIL_ADDRESS>'theme-homepage' => 'https://www.ideaspacevr.org/themes', 'theme-keywords' => 'example, hello world', 'theme-compatibility' => array('Oculus Rift DK2', ' Oculus Rift CV1', ' HTC Vive', ' Google Cardboard v2', ' Google Daydream'), 'status' => 'active', 'status_class' => 'active', 'status_aria_pressed' => 'true', 'status_text' => 'Uninstall', 'screenshot' => 'http://l.ideaspace/themes/hello-world/screenshot.png')), 'config' => array('title' => 'Web VR Photosphere Viewer', 'description' => '360-degree photo sphere viewer with navigation menu.', 'configuration' => array('panels' => array('my-panel-0' => array('label' => 'Your Images', 'priority' => '5')), 'controls' => array('images_upload' => array('type' => 'images', 'required' => true, 'label' => 'Upload Equirectangular Images', 'description' => 'Images are automatically resized to the nearest power of two for width and height.', 'panel' => 'my-panel-0')))), 'theme_mod' => array('id' => '2'))) in ThemesController.php line 96```

PATH = `/admin/space/add/select-theme`

in SpaceAddController.php line 48
at HandleExceptions->handleError('8', 'Undefined index: #theme-name', '/Users/david/Sites/IdeaSpace/app/Http/Controllers/Admin/SpaceAddController.php', '48', array('themes' => object(Collection), 'themes_mod' => array(array('id' => '1', 'theme-name' => 'Hello World', 'theme-description' => 'An example theme using a textinput control.', 'theme-compatibility' => array('Oculus Rift DK2', ' Oculus Rift CV1', ' HTC Vive', ' Google Cardboard v2', ' Google Daydream'), 'screenshot' => 'http://l.ideaspace/themes/hello-world/screenshot.png')), 'theme' => object(Theme), 'config' => array('title' => 'Web VR Photosphere Viewer', 'description' => '360-degree photo sphere viewer with navigation menu.', 'configuration' => array('panels' => array('my-panel-0' => array('label' => 'Your Images', 'priority' => '5')), 'controls' => array('images_upload' => array('type' => 'images', 'required' => true, 'label' => 'Upload Equirectangular Images', 'description' => 'Images are automatically resized to the nearest power of two for width and height.', 'panel' => 'my-panel-0')))), 'theme_mod' => array('id' => '2'))) in SpaceAddController.php line 48

Did you install the most recent release from https://github.com/IdeaSpaceVR/IdeaSpace/releases ?
You seem to have installed the master branch of IdeaSpace, which is the development branch.

Good catch. Yeah I just did a checkout and was hoping to run the latest version.


[Question] unreproducible double-dot syntax example on README

Hello, I am new to swift-case-paths and reading README.md.
regarding section Case paths vs. key paths, I would like you to conform my usage is correct or not, because I can't use double-dot syntax to dive into deeper enum case.

Case paths, like key paths, compose. Where key paths use dot-syntax to dive deeper into a structure, case paths use a double-dot syntax:
\HighScore.user.name
// WritableKeyPath<HighScore, String>

/Result<Authentication, Error>..Authentication.authenticated
// CasePath<Result<Authentication, Error>, String>

here is my code trying above syntax.
import CasePaths
import Foundation

enum Selection: String {
    case alice
    case bob
}

/**
 To dive into a structure, keyPath uses dot (`.`) syntax, but case-paths uses double-dot (`..`) syntax.
 */
func example02() {
    /Result<Selection, Error>..Selection.alice

}

instead, I could use below way but I would like to check if README is old or not.
import CasePaths
import Foundation

enum Selection: String {
    case alice
    case bob
}

/**
 To dive into a structure, keyPath uses dot (`.`) syntax, but case-paths uses double-dot (`..`) syntax.
 */
func example02() {
    /Result<Selection, Error>.success(.alice)
}

@fummicc1 Sorry for the confusion, the .. operator requires parenthesizing of the path, or spaces around it for the compiler to parse things correctly.
/Result<Selection, Error>.success .. Selection.alice

I've updated the README, but also we plan to address some shortcomings of the current operator in the near future. Stay tuned!


Fix race condition between command.Wait() and fetchOutput

I've observed the exitcode sometimes coming back as 0 if it should have been non-zero.
It turns out that both command.Wait() and fetchOutput(* command) were racing to receive command.done. The break statements were only breaking out of the select, not the for loop, so the exit code kept being updated forever.
Apparently at least one implementation of WSMAN returns ExitCode 0 on subsequent Receive messages, even though it was non-zero on the first Receive response with CommandState/@State=done.
I changed fetchOutput/Wait to the canonical 'done channel' pattern to terminate on the first encounter of a CommandState/@State=done fragment.
Not sure why fetchOutput was trying to receive command.done, since it's only sent by the very same function?

We used to signal the command.done channel from command Close, but it somehow disappeared. So either it wasn't necessary, as the slurp will terminate if we close to the server, or it's a bug and we can't close a running command.

In the current code, fetchOutput never terminates, I believe. The break's only break out of the select clause, not the for loop. Even in this case, a command could get stuck, if the server never returns 'done' (ie. it's waiting for input in pending state).

That's right, the code was broken. I'm just trying to figure out if we need to restore the original behavior (ie allowing to exit fetchOutput) if we Close, or if the server will return done anyway...

IMHO, closing/cancelling a command should be a separate channel, like this. If that's what you want, I can add that to this PR. Seems like a good idea to me to not trust the server to do the right thing? Or we could give it a timeout (i.e. close the channel in a go routine which first waits for a certain time)?

@paulmey this looks good to me. Can you add the cancel feature to this PR (in a separate commit maybe)?
I'm not sure about the timeout though, I fear it would add complexity all over this part of the code (and add more complexity for the clients of this code).

Done. TALP...

@paulmey, do you think you could add a test for the second patch?

Yep I'll work on that. I'm a bit busy with some other things, so it might take a couple of days... not sure. :-)

Added tests to master, verified they detect the bugs, rebased fixes on top to verify that the bugs are now fixed.

Thanks @paulmey , this looks good! Merging...


Dbz-2152: EventRouter with bytes based keys

https://issues.redhat.com/browse/DBZ-2152
Enhances the EventRouter to pass along keys that are not Strings

I force pushed an update to rename the commit message to conform to the ticket prefix in the message.

Hi @dcumberland, could you open the pull request against master rather than the 1.1 branch?

@Naros , yes.  I'll open a new PR shortly.

PR https://github.com/debezium/debezium/pull/1570 rebased onto master.