can't convert bnf html

I use https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.13.1/highlight.min.js like

But it converts html
name ::= identifier

to
name ::= identifier

Convert
name ::= identifier

to
name ::= identifier

Anything wrong ? Thans first!

@isagalaev excuse ?

Hey! We don't do user support on Github, I encourage you to ask this sort of questions on Stack Overflow or similar forums.
However your question seems to be addressed in README: see "The CDN-hosted package doesn't have all the languages" in https://github.com/highlightjs/highlight.js/blob/master/README.md#getting-the-library on how to add the definition for BNF.

@isagalaev  Thanks very much!


Remarkable SSH setup?

How do I figure out the code for my remarkable SSH set up?

@karlek36, to get the device specific SSH password, on your device, go to Menu -> Settings -> Help -> Copyrights and licenses. Under the section "GPLv3 Compliance" you will see text like:
... you can connect using the SSH protocol using the username 'root' and the password 'xxx'.


Rigol MSO5074 crashes when we try to do stuff with glscopeclient

I need to include packet captures, but both the scope and glscopehal become unresponsive.

Possibly related to #146.
To avoid overlap, this ticket specifically for the scope firmware hanging, not glscopeclient.

Degi was able to reproduce the crash with this short code snippet: http://paste.debian.net/1165913/
(Posted on IRC here: https://freenode.irclog.whitequark.org/scopehal/2020-10-04#28061962 )

I cannot reproduce that issue with my Rigol MSO5000 (HW 01.01.00) and latest firmware <IP_ADDRESS>
Anyway so far on windows glscopeclient is unusable with something less than 1 frame per second...

Believed fixed with latest Rigol firmware.


Support inlined frames in the stack walker

Breakpad introduced support for inlined functions and frames in revision f0803507. Once we've got full support for stack unwinding using traditional Breakpad CFI we should support this too.

I'm demoting this to "cool dream" because it increasingly sounds like this whole thing is a mess upstream, so it's not obvious what implementing this even means.

This was fixed in #599 and #635. Somebody with the appropriate privileges can close this issue.


[BUG]: OpenAiWhisper always leads a transcribing failure

How are you running AnythingLLM?
Local development
What happened?
Once a Transcription API is set to OpenAiWhisper, transcription result is failure whenever I upload a .mp3 file. I find that the code in line 36 of OpenAiWhisper.js in collector directory is return a result like: content: response. I have referred to the docs in openai.com, the example shows that the text content should extract by using response.text. So I change the code to content: response.text, and my question is solved.
Are there known steps to reproduce?
Just change the transcription API to open whisper and upload a .mp3 file in your workshop.

I can confirm that PR #2618 actually introduces the bug that the associated PR is alleviating. We specifically return text and not JSON - so the response body is the text
https://github.com/Mintplex-Labs/anything-llm/blob/e41a9beaaeb30d1b0f4feacdb5ccd7647b71eb7c/collector/utils/WhisperProviders/OpenAiWhisper.js#L25
The only ways this behavior could be occurring is that you are on a modified version of AnythingLLM or are using a proxy or host override that instead maps to an OpenAI compatible service that is actually not fully 1:1 and always returns type json

@fiyen We just merged in a slight modification of this PR which should support your use case as well as not break compatibility with the current implementation of OpenAI in AnythingLLM #2621


Missing text-area(s) for import/export

If I remember correctly there where text-areas on the import/export tab earlier this year. I used them to great extend and miss them now.
Unfortunatly my skills in debugging and coding JavaScript are basicly non-existent.
Maybe you can have a look into it.

Nevermind was a problem with my browser.


Convert numpy float to Python float in feat score.

Address issue raised by @harupy in https://github.com/dmlc/xgboost/pull/7041#discussion_r654226008

Looks good to me.


Using XPlugin

I think we could introduce a plugin system for cell magics. It would be pretty helpful to the end-users.
Magics in xeus-cpp are registered into a magics_manager class, that inherits from a preamble which is used for detecting special inputs in the cell before deciding to parse the code.
Currently, the scarce available magics are part of the xeus-cpp codebase, and adding a new one means rebuilding and releasing xeus-cpp. A plugin system would avoid that. We could leverage the plugin system here (https://github.com/QuantStack/xplugin) . Xplugin would add the possibility to discover magics at runtime

We would eventually want a generic mechanism to register / fetch magics in xeus. So we could start with a proto in xeus-cpp before going for the generic solution and eventually have xplugin as a dependency in xeus.

A list of magics have been noted down in this issue.


ignoreForTagNames should include all form controls that accept keyboard input

In particular, textarea is not an input but acts like one, and select tags use keyboard input to jump to an option.

Thanks for raising an issue @DanielHeath !
You should be able to pass in the ignoreTagNames prop to ignore the suggested elements.
<ShortcutProvider ignoreTagNames={['input', 'textarea', 'select']}>
</ShortcutProvider>

That said I'm open to considering changing the default as right now it is only input.

I thought this over and agree that including the default form element types to the ignore list is beneficial. Appreciate your suggestion here.
This will be released in the next minor version.


task/rpm-ostree: Use --entrypoint bash

Required for https://github.com/CentOS/centos-bootc/pull/277
I am planning to potentially change to use bootc-image-builder for this, but it has a non-bash entrypoint.

Look for any open pull requests in the repository with the title "e2e-tests update" and
see if there are recent e2e-tests updates that will be applicable to your change.

/ok-to-test

/retest

/lgtm
/approved

@cgwalters , you say that you are planning to change the builder image but that has a different entry point. At that time, would you plan to submit a PR to the build definitions to modify the default builder image reference (reducing the need for it to be passed as a parameter) and also modifying the entrypoint? Or would you be more interested at that time to make the entrypoint configurable as well?

We could try to just change the default builder image here, yes.  I'm ok with that, but it seems like a larger change.
I don't think it really makes sense to make the entrypoint configurable because this pipeline relies on it being bash.

We can get this merged and address the change in the path with the default builder pipeline if needed in the future.


how to deal with import timestamp?

In my .proto file I have line:
import "google/protobuf/timestamp.proto";
and then I use:
message Command {
google.protobuf.Timestamp issuedDT = 1;
}
The generated C code looks good:
#include <pb.h>
#include "google/protobuf/timestamp.pb.h"
but then Compiler rightfully fails to find "google/protobuf/timestamp.pb.h" include file, because it does not exist.
Please, help as I am not sure how to handle this scenario.
Thank you

A short solution to my problem is like that.
Locate "google/protobuf/*.proto" that includes timestamp.proto file.  Compiling an entire "google/protobuf" fails with error
PATH=/home/sergei/bin:/home/sergei/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/sergei/gw/public/bin:/usr/local/maven/apache-maven-3.3.9/bin:/snap/bin:/home/sergei/500C-ISOM-Trunk/itron/gowspace/bin GOPATH=/home/sergei/500C-ISOM-Trunk/itron/gowspace /home/sergei/500C-ISOM-Trunk/tools/nanopb-0.3.8-linux-x86/generator-bin/protoc -I. --nanopb_out=google/protobuf google/protobuf/*.proto Traceback (most recent call last):   File "<string>", line 6, in <module>   File "__main__.py", line 128, in <module>   File "__main__protoc-gen-nanopb__.py", line 1664, in <module>   File "__main__protoc-gen-nanopb__.py", line 1644, in main_plugin   File "__main__protoc-gen-nanopb__.py", line 1519, in parse_file   File "__main__protoc-gen-nanopb__.py", line 1058, in __init__   File "__main__protoc-gen-nanopb__.py", line 1084, in parse   File "__main__protoc-gen-nanopb__.py", line 870, in __init__   File "__main__protoc-gen-nanopb__.py", line 757, in add_field Exception: Callback fields inside of oneof are not supported (field string_value) --nanopb_out: protoc-gen-nanopb: Plugin failed with status code 1.
So, I removed all files and kept timestamp.proto.  Rerunning command resulted in generated timestamp.pb.h and timestamp.pb.c files.  I included files in mbed project and it worked.

Yeah, compiling the whole google/protobuf would probably need a few options in .options.


Integrate CMCC use case

Integrate CMCC use case into prototype.
Code repository can be found here.
Data is accessible via google drive here.
There are multiple tasks to be done:

check that code is working as provided in the repo
split use case in preprocessing, training, validation/post-processing part
integrate by porting to PyTorch or providing TF support

Adapt to the new "pipeline" API


MustProcess: panic if processing fails, return the value

I originally made this PR to https://github.com/kelseyhightower/envconfig/pull/213 but this looks to be the supported alternative
This adds a generic MustProcess method, that panics if processing fails, and returns the spec value.
Example usage:
package main

import (
  "log"

  "github.com/sethvargo/go-envconfig"
)

var env = envconfig.MustProcess(context.Background(), &struct{
  Foo string `env:"FOO"`
}{})

func main() {
  log.Println("your FOO is " + env.Foo)
}

This lets the env struct be moved to an init-time var, out of func main, and retains all the env parsing behavior we've all come to know and love.
The structure of that var statement is kind of gross (inline-defining a struct and its empty value, and passing it to the method), if I'm missing some way to make it better, let me know.
Type parameters were required, since MustProcess(ctx, interface{}) interface{} loses information about the input type. You could cast back to the type you want, but generics are better IMO, since it lets you do it all in one statement.

I think this is achievable many idiomatic ways today, so I'm not sold on adding another API function. You could use an init function or a func enclosure that returns the var. I also think this is generally a bad practice because (a) you should have a concrete config type and (b) it makes testing a nightmare.
What problem are you trying to solve by not having the parsing in main?

I think this is achievable many idiomatic ways today, so I'm not sold on adding another API function. You could use an init function or a func enclosure that returns the var. I also think this is generally a bad practice because (a) you should have a concrete config type and (b) it makes testing a nightmare.
What problem are you trying to solve by not having the parsing in main?

These are all perfectly reasonable questions. If this isn't accepted, I totally understand. 😄
This came about from looking at how we've used envconfig (Kelsey's version), which generally follows this form:
package main

type env struct {
  Port        int    `envconfig:"port", required:"true"`
  BackendAddr string `envconfig:"backend", required:"true"`
  ... etc.
}

func main() {
  var env env
  if err := envconfig.Process("", &env); err != nil {
    log.Fatalf("bad env: %v", err)
  }
  ... use env.BackendAddr, etc.
}

This is ...fine. Some examples define type env struct inside func main(), a couple do it in func init to get it out of func main(), there's maybe half a dozen similar ways to do it. I do realize I'm proposing another one. 😆
In any case, our usage tends to be only inside package main, where we generally don't have a need to test the type. It's generally a shortcut for os.Getenv and verbose manual error-prone validation. The env values usually go straight in to a client setup and the client gets passed to a type that does the real work, and gets tested that way. The type is usually concretely defined today, but is unexported from package main so it doesn't really amount to much.
My line of thinking was roughly:

we always log.Fatal when Process returns its err; why not just have MustProcess (Kelsey's has this, but it doesn't return the value) -- this saves 2 lines of boilerplate.
when we have MustProcess, it could return the value -- this saves another line of boilerplate.
when we have a one-liner, it could go into the package-level var definition, with some anonymous struct contortions -- this lets us move it out of func main().

That line of thinking might be flawed, or overly clever, but that's how I got to this approach.
If this isn't considered an idiomatic way to use the library, I'll accept that. Thanks for this library, and for your thoughtful response 😄

@imjasonh I cleaned this up and updated docs in #115

@imjasonh I cleaned this up and updated docs in #115

Thanks! 😍


Clicking outside a menu blocks click from bubbling up

Current Behavior
There a fundamental issue with the menu dismissal. When presented with multiple buttons or select fields that show a menu, it take 2 clicks to dismiss the existing menu and show the next one.

Steps to Reproduce
In the demo below, try opening the first menu by clicking on the first button, then the second menu by clicking on the second button. Notice that an extra click is needed to dismiss the first menu then another one to show the second menu.
https://codesandbox.io/s/9lp94v86zo
Expected Behavior
Good UX guidelines recommend to reduce the number of clicks needed to perform an action. As opposed to modals and dialogs, menus are not expected to hijack the click away events.
The issue is that the background click to dismiss a menu, has a e.preventDefault() which prevents it from bubbling up to the other element.
In other frameworks, you can click on an other element, and it will have double effect: close up the first menu, and show the new one in one click action. For reference:
Bootstrap
http://getbootstrap.com/2.3.2/components.html#buttonDropdowns

Semantic-UI

Sencha ExtJS
http://examples.sencha.com/extjs/6.5.3/examples/kitchensink/?modern#buttons-split

UIKit
https://getuikit.com/v2/docs/button.html
Your Environment

Tech
Version

Material-UI
v1.0.0-beta.44

React
16

browser
Chrome 65

etc

@simoami The current Menu behavior was designed on purpose. It's following the menu behavior on Mobile. I do think there is room for the two behavior. It's a tradeoff. On mobile, the cost of wrongly interacting with an element is much higher. It might trigger a screen transition, it can slow users down.
Another important point to notice is the scroll blocking.
We have a related issue: #9893. I see two possible paths going forward. Either we add some options to the Popover or we build a new component on top of the Modal. It's prioritied for the post v1 roadmap.

Thanks @oliviertassinari
oh yes, I just noticed the scroll block too. While this solves for mobile, it is not a desired behavior for menus on desktop. Btw, I took a look at #9893 and I feel that the dropdown issue is only one instance of a side effect of the current menu behavior and that a fix shouldn't be limited to dropdown components. Another common scenario is a list with secondary actions with menus attached to them.
In terms of what you're suggesting, I'm open to either option, as long as the default behavior is not altered. I'm thinking that a configurable option is the easiest one. Angular's material project has a hasBackdrop option, but they don't have it implemented correctly. We could implement it properly to alter the event and scroll lock behavior at the same time.
hasBackdrop: true|false (defaults to true) When disabled, click away events are accessible to parent nodes and page scrolling is allowed.

Fyi, Google's own cloud platform (which is material design) has the menus behave the right way:

I see what you mean 👍 Like I said we can keep the default behavior intact and offer more customization. I think different use cases call for different behavior. I personally think one less click is better is it doesn't have a side effect.

@simoami What do you think of moving the discussion to #9893?
@fangeugene Interesting concern.

Related to #17353.

@oliviertassinari Sorry, I missed your last comment.
I'm ok moving the convo to the other issue. I just want to point out that this is not specific to the dropdown component. Take for example a table view with each row having the options icon. And with the clickaway layer, it also takes two clicks to open the menu for a different row. The common issue here and with the dropdown component is the menu clickaway layer that hijacks clicks.

I would question how we use the Popover for Menu or Select in the first place currently. These are pretty disruptive since they mess with page layout (see scroll bars) and the clickaway listener prevents any other clicks. As outlined in this issue you usually don't want them to have the same status as a something like a dialog (don't hide rest of the UI and don't intercept clicks).
Using the Popper and then closing the listboxes when it looses focus would be more like the platform handles these things. We only need to consider the edge case when we click the trigger again when the listbox is displayed. Native FocusEvent has relatedTarget but that is incorrectly polyfilled in react.

@eps1lon I share your feeling, the current menu and select behavior is too disruptive for desktop (I think that it's much better suited for mobile). There is a related comment you might appreciate in https://github.com/mui-org/material-ui/issues/17636#issuecomment-536693407.

Understanding, this works by design for mobile platforms, but for desktops (browsers) there is still not friendly behaviour.
The case:
App renders tree of folders. User calls a context menu for one folder, then for another folder, etc.. Currently user always needs to mandatory close previous popover by left clicking outside of it to open another.
I checked menus in Windows. When I call context menus for different folders, I do not need to close menu before opening a new one.
There are two issues I see here:

There is not event bubbling on desktops. I suppose there should be a flag (property) for this. Even for desktops. I ask to return to this question discussion.
Popover can be closed by left click outside only. Right click opens default browser menu - this turns the case twice harder for user. Now he have to close two menus before opening a new one!

Maybe the item (1) is for discuss, but I guess item (2) should be fixed. At least by disabling browser context menu on right click. This behaviour can be changed adding onContextMenu property only, not by CSS. But the best if right click will close the menu as well left click does.

Hey man, i've had the same issue. So i searched on the world wide web and found something which is similar to your problem. It solves the problem in a different way than the 'vanilla' way of MUI.
The website I found promoted an 'npm' package which provides a Custom React Hook that keeps track of the local state for a single popup, and functions to connect trigger, toggle, and popover/menu/popper components to the state.
So I tested it. And it worked fine for me. In my case i wanted just a hover menu, but here you can find some other usefull templates for dropdowns. Also as in your case a normal dropdown menu.
In my case i created a react component:
import * as React from 'react';
import HoverMenu from 'material-ui-popup-state/HoverMenu';
import {MenuItem, Button, Typography, Divider} from '@mui/material';
import ArrowDropDownRoundedIcon from '@mui/icons-material/ArrowDropDownRounded';
import { usePopupState, bindHover, bindMenu, } from 'material-ui-popup-state/hooks';
import Link from 'next/link';

//options on items collection:
//'br' => sets divider
//'TEXT' => button with link

const DropDown = ({title, items = []}) => {
  const popupState = usePopupState({
    variant: 'popover',
    popupId: 'menu',
  })

   return (
    <React.Fragment>
      <Button variant="ghost" {...bindHover(popupState)} endIcon={ <ArrowDropDownRoundedIcon />}>{title}</Button>
      <HoverMenu disableScrollLock={true} {...bindMenu(popupState)} anchorOrigin={{ vertical: 'bottom', horizontal: 'left' }} transformOrigin={{ vertical: 'top', horizontal: 'left' }}>
        {items.map(item => {
            if(item == 'br'){
                return <Divider />
            }
            else {
                return <MenuItem onClick={popupState.close}><Link href={item}><Typography variant='button'>Team</Typography></Link></MenuItem>
            }
        })}
      </HoverMenu>
    </React.Fragment>
  )
}

export default DropDown;

I hope this helps you and others!

Any update on this?

Hi All,
@simoami @oliviertassinari @fangeugene @eps1lon @iamharshad
The problem was that in the project, when we opened a menu, we had to click once to close it before being able to open another menu. This double-click requirement was inconvenient.
To fix this issue, I made changes to the code as below:

I added a property called disablePortal to the menu.
I applied a specific style to the menu using sx property with zIndex: 'unset'.

`<Menu
PaperProps={{
style: {
maxHeight: mdMatches ? '500px' : '300px',
},
}}
anchorOrigin={{
vertical: 'bottom',
horizontal: 'left',
}}
transformOrigin={{
vertical: 'top',
horizontal: 'left',
}}
sx={{
zIndex:'unset',
bgcolor: { xs: 'rgba(0,0,0,0.2)', md: 'unset' },
backdropFilter: { xs: 'blur(2px)', md: 'unset' },
ul: { py: '0px' },
'.MuiPaper-root': {
borderRadius: '10px',
boxShadow: '2px 2px 18px rgb(0 0 0 / 20%)',
border: ' 1px solid #ddd',
width: { xs: '100%', md: 'fit-content' },
},
}}
disablePortal

// List
`
These changes did the trick! Now, when you click to close an opened menu, you can immediately open another menu without having to click twice.
If anyone else is facing a similar problem, you can try implementing this solution. Let me know if it works for you too!

Just in case if someone else faces the same issue, I was able to solve with the following:

Added a scroll handler:

    React.useEffect(() => {
        window.addEventListener('scroll', handleProfileMenuScroll);
        return () => window.removeEventListener('scroll', handleProfileMenuScroll);
    }, [])

Then on handleProfileMenuScroll():

    const handleProfileMenuScroll = () => {
        setOpenMenu(false);
    }

Added the option disableScrollLock to the <Menu> definition

When the user scroll down, it closes the menu (useful if you're building dynamic Menus on different cards for example). If you only have one Menu (on the top for example), then you can skip the scroll handler and use the disableScrollLock option.
I hope it helps.

Hi @simoami ,
I encountered the same issue with menu dismissal while building a dropdown menu, where it required an extra click to dismiss one menu before opening another. This behavior disrupts the expected seamless interaction for users.
To address this, I recommend using the Material-UI Popup State library. It simplifies managing popups and menus, allowing clicks on other elements to simultaneously dismiss the current menu and open a new one, aligning with good UX practices.


pc run emits error if a project named ‘test’

Describe the bug
pc run emits error if a project named ‘test’.
I found that the name test can conflict with another python modules.
But is it fine that pynecone cannot run with the name test?
To Reproduce
$ mkdir test; cd test;
$ pc init
$ pc run

Expected behavior
running well
Screenshots

** Specifics (please complete the following information):**

Python Version: 3.10
Pynecone Version: 0.1.12
OS: Ubuntu 22.04.01
Browser (Optional):

Got it thanks, seem like you can't have a pynecone project called pynecone or test we should make this clear or throw a better message

Wait when I did this it seems to work fine, anyone else getting this issue?

Hi, @Alek99.
At first, I’m little confused that the error is not occurred when I run the command on the same computer which the only difference was that it was only on docker environment.
I ran it on the image python:3.10.6-buster.

However, it still emits error on the image ubuntu:jammy which is the same OS as my computer.
I know that buster uses debian.

Hmm the only thing I can think of is something in related to your $PYTHONPATH. The two reasons this may occur are:

You module test is not in you PYTHONPATH, but it since you're running out from the same directory that shouldn't be the issue
There exists some other module named test and the import is confusing it with your local folder.

In any case, maybe try renaming the project and see if you get the same issue on that Docker?

Just try to import test on my server which use Ubuntu 22.04, and it successed?
I think Ubuntu's build-in Python comes up with a package named test, when I try to print(test.__path__), it gave me /usr/lib/python3.10/test, and this folder is exist, with some Python file in it.
So we can explain this problem. Docker Image of Python is build on Debian, and you use Ubuntu, Debian does not has this package but Ubuntu does.
For solution, we can't delete this package due to risk of break the system, just don't use this name with Ubuntu, at least use a Docker Image for deployment.

Just try to import test on my server which use Ubuntu 22.04, and it successed?
I think Ubuntu's build-in Python comes up with a package named test, when I try to print(test.__path__), it gives me /usr/lib/python3.10/test, and this folder is exist, with some Python file in it.
So we can explain this problem. Docker Image of Python is build on Debian, and you use Ubuntu, Debian does not has this package but Ubuntu does.
For solution, we can't delete this package due to risk of break the system, just don't use this name with Ubuntu, at least use a Docker Image for deployment.

Oh nice I didn't know this change, thanks for finding this

... when I try to print(test.__path__), it gives me /usr/lib/python3.10/test, and this folder is exist, with some Python file in it.
So we can explain this problem. Docker Image of Python is build on Debian, and you use Ubuntu, Debian does not has this package but Ubuntu does.
For solution, we can't delete this package due to risk of break the system, just don't use this name with Ubuntu, at least use a Docker Image for deployment.

Right. And I checked that it occurs in Ubuntu focal and jammy version.
Then ,,, we should not use pynecone on ubuntu and close the issue?

Just name your project something else besides test (or any other builtin Python package) and it should work.

oh, right. I mean don't use the name test.


stable-2.2: add ceph_nfs_ceph_user to nfss.yml.sample

Add the ceph_nfs_ceph_user variable to nfss.yml.sample too (not just
all.yml.sample).
This was properly included in ada2f147f5c6537cf51171c995009b0b3288c027
in master, but was missing from
72e32ae0bf1f060aaabd88ddb9c8dd000c0c5d97 in stable-2.2.

@alimaredia This is the follow-up to #1912. Again, sorry about not including this the first time around.

@fghaas fyi: when you make changes to roles/ceph-{subcomponent}/defaults/main.yml, if you run generate_group_vars.sh it will automatically add all the changes into the corresponding files in the group_vars directory.

Yes I did that, but I forgot one git add. :/


Notepad editor

Love what you did with the editor but tbh there was no real reason to remove the notepad editor. Imo it was WAY easier to use than the internet one. I think you should give the ability for server moderators to choose which editor they want to use

Notepad editor?
Do you mean editing your database with text based editors, like yaml? That's always been a feature of LuckPerms. Maybe check the config under "storage-type".


Create NI-SWITCH message implementation

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Create an NI-SWITCH variant of the SLSC Switch message library.
Why should this Pull Request be merged?
We want to allow using NI-SWITCH hardware with the Routing and Faulting custom device.
What testing has been done?
Tested changes in conjunction with https://github.com/ni/niveristand-routing-and-faulting-custom-device/pull/220.

Do we need the SET caps file for NI-SWITCH tests?

No, good catch.

The tests hang on consumer initialization in setUp.vi on my machine in 2017. Is there a specific version of the base messaging library I need?

There shouldn't be. I'll reach out directly.

@buckd I've added the same workaround as is used in the custom device, which seems to prevent the hang. I've also removed the extraneous test asset.


how to using webpack minify multi html templates?

how to using webpack minify multi html templates?
https://github.com/jantimon/html-webpack-plugin
https://www.cnblogs.com/xgqfrms/p/9109493.html

webpack 3.x best practical
https://www.cnblogs.com/xgqfrms/p/9109493.html

https://github.com/xgqfrms/FEIQA/issues/22#issuecomment-414206129

https://abc.xgqfrms.xyz/webpack-all-in-one/


[Feature Request] Don't start Autolock timer until the door is closed.

Is your feature request related to a problem? Please describe.
My keymaster install will autolock with my door open despite having the entity for the door sensor in the page for code management
Describe the solution you'd like
Add the condition of the door being close to the autolock timer service starting.
Manual attempts to add this condition seems to break the autolock timer start service.

Well despite the Lovelace page showing the correct status of the door, I re-ran through the setup for the lock and repicked the contact sensor I am using and now autolock waits until after the door is closed to attempt to lock.


Bug: Velero restore fails to pull image from internal OpenShift registry.

Contact Details
<EMAIL_ADDRESS>Describe bug
When velero restores the backed up files to a new namespace due to which the imagestream throws an error as it tries to pull application images from external nexus registry instead of pulling them from the internal OpenShift registry.
 velero backup create <name of backup> --include-namespace <namespace>
 velero restore create <name of restore> --from-backup <name of backup>

The resources are successfully created. However when we try restoring we face ImagePullbackOff error.
In events, we noticed that it is trying to pull from nexus registry instead of internal OCP registry:
2m10s       Warning   Failed                   pod/locator-1-m8n5c                  Error: ImagePullBackOff
2m24s       Normal    Pulling                  pod/locator-1-m8n5c                  Pulling image "nexus.xxx:5000/locator@sha256:726f4551df12d6bc7b30155e09096bbea65de48c4ad9ccceb6d3e2ff9bcf9a27"
2m24s       Warning   Failed                   pod/locator-1-m8n5c                  Failed to pull image "nexus.xxx:5000/locator@sha256:726f4551df12d6bc7b30155e09096bbea65de48c4ad9ccceb6d3e2ff9bcf9a27": rpc error: code = Unknown desc = error pinging docker registry nexus.xxx:5000: Get "https://nexus.xxx:5000/v2/": http: server gave HTTP response to HTTPS client
2m24s       Warning   Failed                   pod/locator-1-m8n5c                  Error: ErrImagePull
2m36s       Normal    BackOff                  pod/locator-1-m8n5c                  Back-off pulling image "nexus.xxx:5000/locator@sha256:726f4551df12d6bc7b30155e09096bbea65de48c4ad9ccceb6d3e2ff9bcf9a27"

We noticed that there are two plugins in velero yaml.
defaultVeleroPlugins:
  - aws
  - openshift

Steps to reproduce:

Build the image and push it to nexus docker registry:
docker build -f ./Dockerfile -t nexusregistry:5000/sample-app .
docker push nexusregistry:5000/sample-app

Login to the OCP Cluster and the internal registry:
$ oc login --insecure-skip-tls-verify -u '${OCP_CREDS_USR}' -p '${OCP_CREDS_PSW}' ${ocpUrl}
$ sudo docker login -u system -p $(oc whoami -t) ${ocpRegistry}

There is a script which is executed at customer's end which has docker tag and push to the internal registry commands. Due to which pipeline job runs and resources(pods,deployment,is, etc) are created.

What happened?
We expect the images to be pulled from the internal OpenShift registry rather than the external registry.
OADP Version
0.4.x (Beta)
OpenShift Version
4.6
Velero pod logs
No response
Restic pod logs
No response
Operator pod logs
No response
New issue

[X] This issue is new

I'll attach the backup/restore logs along with oc get imagestream locator -oyaml shortly.

islocatore.txt --> Imagestream yaml of the image
backuplogs.txt --> Velero Backup logs
restorelogs.txt --> Velero Restore logs
errors.txt --> Velero backup error logs

@Bloom-P Here's what I am seeing... the Imagestream has this:
spec:
  lookupPolicy:
    local: false
  tags:
  - annotations: null
    from:
      kind: DockerImage
      name: nexus.abc.com:5000/locator:4.2.0-31-project
    generation: 22
    importPolicy:
      insecure: true
    name: 4.2.0-31-project
    referencePolicy:
      type: Source

If you have this in the Imagestream spec, then this is exactly how we will restore the imagestream onto the cluster. This DockerImage must be accessible from the cluster or this will fail. I'm failing to see how this is unexpected behavior.
If that host is unreachable, I don't think you want this imagestream definition. What am I missing?

It's not clear from the comments, but what resource are the ImagePullbackOff errors coming from? I'm assuming it's from a pod of some sort. Could you provide the pod (and associated Deployment/DC/etc.) yaml for this resource for the post-restore failure and also for the yaml before backup (if available)?

@dymurray They are storing their images in nexus and tagging them to the internal registry.
Adding a scrennshot of the stage in Jenkins.

@sseago I'll attach the requested outputs as I receive them.


Make it possible to use !Send even in Native LSP

fixes #187
use tokio::task::spawn_local and remove Send requirements.
Note:
The use of multi-threaded executor is still exists in the following places:

create_input
create_output
taplo-cli

Thank you!
I was not sure about removing the Send support from lsp-async-stub itself, but it certainly makes the implementation cleaner.


Add supported data types list to the dialect documentation

The list is already in the documentation.

The list is already in the documentation.


[BUG] EMFILE: too many open files error When Adding Multiple Images to a Worksheet

🐛 Bug Report

exceljs: 4.4.0, Node.js: 20.x
Steps To Reproduce

https://github.com/shuntagami/excel-util Here I reproduce with docker-compose, specifying ulimits
import ExcelJS from "exceljs";
import { readFileSync } from "fs";

async function main() {
  const workbook = new ExcelJS.Workbook();
  const targetSheet = workbook.addWorksheet("Target Sheet");

  for (let i = 0; i < 1000; i++) {
    const imagePath = `images/image-${i}.jpeg`
    console.log(imagePath);

    const imageId = workbook.addImage({
      filename: imagePath,
      // buffer: readFileSync(imagePath),
      extension: 'jpeg',
    });
    console.log(`image added to workbook, imageId: ${imageId}`);

    targetSheet.addImage(imageId, {
      tl: { col: 1, row: (i + 1)*3 },
      ext: { width: 100, height: 100 }
    });
    console.log('image added to worksheet');

  }
  const path = `./results/${Date.now()}.xlsx`;
  console.log(`writing data to ${path}`);

  await workbook.xlsx.writeFile(path)
  console.log(`File written to ${path}`);
}

main().catch((error) => console.error(error));

the problem is arround here below
const imageId = workbook.addImage({
      // filename: imagePath,
      buffer: readFileSync(imagePath),
      extension: 'jpeg',
    });

when I use filename: imagePath, it will raise the error, but if I use buffer: readFileSync(imagePath), not reproduce  so forget to close file anywhere ?
The error msg is below
images/image-998.jpeg
image added to workbook, imageId: 998
image added to worksheet
images/image-999.jpeg
image added to workbook, imageId: 999
image added to worksheet
writing data to ./results/1702012108045.xlsx
[Error: EMFILE: too many open files, open 'images/image-275.jpeg'] {
  errno: -24,
  code: 'EMFILE',
  syscall: 'open',
  path: 'images/image-275.jpeg'
}

The expected behaviour:
Work both on using filename and buffer
Possible solution (optional, but very helpful):
I want to fix this issue but still don't know where to fix it

Finally, I found the cause and solution https://github.com/exceljs/exceljs/pull/2624

What I need is https://github.com/exceljs/exceljs/pull/2632


Padding for behind a toolbar

This issue is relevant to #39
I want to set a padding to the ssiv, so that it reserves space for a toolbar, but it should fall behind the toolbar when zoomed in.
When using the following layout
<FrameLayout
    android:layout_width="match_parent"
    android:layout_height="match_parent">

    <com.davemorrissey.labs.subscaleview.SubsamplingScaleImageView
        android:id="@+id/image"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        android:paddingTop="56dp" />

    <TextView
        android:id="@+id/toolbar"
        android:layout_width="match_parent"
        android:layout_height="56dp" />

</FrameLayout>'

I get the following results:

As you can see the vertical image works fine but the horizontal image moves to the bottom, instead I want it centered vertically. The images do go behind the toolbar correctly when zoomed.
Is this intended behavior or is this a bug?
Thanks in advance.

That's the intended behaviour. If the padding is asymmetric, the view preserves the top:bottom and left:right padding ratios as you zoom in, so in this case, because you have no bottom padding, the image remains flush with the bottom until it becomes larger than the screen. I didn't really intend the view to be used with asymmetric padding, and this seemed to be the best option at the time.
Maybe you could detect whether the image has a greater width:height ratio than the space available in the view, and add bottom padding if so.

Thank you for your response, I'll try to see if I can do something with the padding.

I'll close this because it's intended behaviour but if you find a workaround it would be interesting to see how you did it.


Tari container - wallet password is not updated until the app restart

The container does not use the newly passed wallet password, until the application is restarted.

It affects all environment variables of all containers, ie. data_folder, monero urls, etc.


@1aurabrown => [Tabs] Add shows and magazine to available tabs.

Fixes #300.
On iPad, these views do not yet rotate, once loaded, due to #322.

awesome. failing tests are not indicative of an actual problem, right?

Nope, the only failing test is that one about related artworks that you told me about.


[pyspark] Convert tests to pytest style.

The tests derived from the python unittest module are not compatible with pytest. For instance, pytest.mark and pytest fixtures are not usable with existing pyspark tests. As a bouns, I think using pytest fixture instead of the setup function from unittest can accelerate the test performance by preventing repeated setups.
Aside from the test framework, we need to remove the use of hardcoded results.
@WeichenXu123 @wbo4958

I will convert a couple of them in https://github.com/dmlc/xgboost/pull/8272 .

@trivialfis Can you please file a separate PR for the revised tests?

will split up the PR.


Set SO_REUSEADDR in echo_op example

fix #1335

This is in https://github.com/boostorg/beast/pull/1334 now, waiting on CI

Hmm.....if we are going to make a bunch of changes to echo-op I think it would be best to put it in a single commit, and we can give it a couple of days to settle would that be OK?

Sure, I can close the echo-op related pull requests and submit a single one with all the changes.

I think that would be best


Add option for dump1090-mutability to bind to all interfaces

Currently, after installation of dump1090-mutability, it is set to bind to interface <IP_ADDRESS> (i.e. localhost) only. This is fine for all software that is installed with the script but may present issues when user adds more software that needs to connect to the Pi IP address rather than localhost. Example: VRS on separate Windows host that wants to connect to [Pi IP]:30005
This will not work without manually reconfiguring dump1090.
I can see 3 possible options here:

Just a warning/info for user to reconfigure dump1090 manually if required (however, this may be overlooked by some users)
Present a choice during installation to keep the default <IP_ADDRESS> or have a blank parameter (meaning it will bind to all interfaces)
Configure dump1090 to bind to all interfaces by default

I'd almost prefer if dpkg-reconfigure dump1090-mutability was run after installation so that all of the native options were presented to the user after all of the other scripting is set up.

That would work for me as well.

I have thought about this in the past especially being I like to connect to my receiver sometimes from work using VRS. I originally decided against opening to other interfaces due to the fact not everyone realizes the ramifications of doing so and I would hate to see someone's device or worse yet network taken down unknowingly because a vulnerability was found later on.
I could see giving an option to run dpkg-reconfigure but there again not everyone using the image or scripts is all that knowledgeable which leads to fouled up settings and "why does this not work now?" questions. Seems most people who are knowledgeable when it comes to dump1090-mutability realizes this option is available.
None of this means it is written in stone I would not make these changes just wanted to pose some different views which lead to their absence in the first place to get thoughts and feedback on the reasoning before considering them.

Yes, all valid reasons. Maybe display a prominent message, addressed to "Advanced Users", to run the dpkg-reconfigure manually if you need to access dump1090 from anything other than localhost?
My reason for bringing it up is that I helped someone via private forum messages to set up everything, incl. VRS and there he did not understand why it did not work out-of-the box. I told him to run the dpkg-reconfigure.

Joe, it actually stumped me for a while. I spent (embarrassed to admit) probably over two hours trying to figure out why the port forwarding on my router wasn't working for the remote Mlat group I participate in.
I definitely get the point about not wanting to endanger typical users though. Maybe adding an advanced menu is the way to go as it could be used as a jumping point for all kinds of feature creep in the future. dpkg-reconfigure dump1090-mutability would just be a start!

Added option to bind dump1090-mutability to all IP addresses. Changes were pushed to template branch and will be merged with master once the branch has been completed and tested.


Changed skill-related enums to strings for values that may change

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[X] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Can one of the admins verify this patch?

@jennifermarsman These enums are defined by us, right? It's not like LexicalAnalyzerName, where they can introduce their own values at run-time? I'm not sure these enums really need to be extensible. Unless we want to be able to add new values without shipping new SDKs, I don't know that there's a strong justification for this change.
@heaths I remember we talked about this, and non-extensible enums can be changed in a backward-compatible way in each target language, right?

Yes, so long as changes are merely additive. Names and values (often the same thing) that have already shipped can't change - even for extensible enums (compilation errors will occur).

@brjohnstmsft @heaths "these enums are defined by us" - it depends if you mean us as Microsoft or us as the Cognitive Search team.  These enums define values used in the skills, which are really defined by the Cognitive Services team, and they can/do/will change as they change their APIs.

@jennifermarsman I meant us as in not customers of the service. I think this change was unnecessary, but let's see what comes up in the API review board.


An argument named "source_policy_documents" is not expected here.

Description
Starting with v1.23 and #77, there is an issue with the secure transport policy as see below:
Error: Unsupported argument

  on .terraform/modules/dynamodb_backup.secondary_dynamodb_backup_bucket/main.tf line 247, in data "aws_iam_policy_document" "combined":
 247:   source_policy_documents = compact([

An argument named "source_policy_documents" is not expected here.

Versions

Terraform:
0.14.9
Provider(s):
3.36.0
Module:
1.23/1.24

Reproduction

Steps to reproduce the behavior:

Code Snippet to Reproduce

data "aws_iam_policy_document" "service_reports_artifact_bucket" {
  statement {
    sid    = "DenyNonSecureTransport"
    effect = "Deny"
    actions = [
      "s3:*"
    ]

    resources = [
      module.service_reports_artifact_bucket.this_s3_bucket_arn,
      "${module.service_reports_artifact_bucket.this_s3_bucket_arn}/*",
    ]

    principals {
      type        = "AWS"
      identifiers = ["*"]
    }

    condition {
      test     = "Bool"
      variable = "aws:SecureTransport"
      values = [
        "false"
      ]
    }
  }
}

module "service_reports_artifact_bucket" {
  source  = "terraform-aws-modules/s3-bucket/aws"
  version = "~> 1.22"

  bucket = "service-reports-artifacts-something-random"

  attach_policy = true
  policy        = data.aws_iam_policy_document.service_reports_artifact_bucket.json

  block_public_acls       = true
  block_public_policy     = true
  ignore_public_acls      = true
  restrict_public_buckets = true

  server_side_encryption_configuration = {
    rule = {
      apply_server_side_encryption_by_default = {
        sse_algorithm = "AES256"
      }
    }
  }

  lifecycle_rule = [
    {
      id      = "all"
      enabled = true

      expiration = {
        days = 30
      }

      noncurrent_version_expiration = {
        days = 5
      }
    }
  ]

  tags = module.tags.tags
}

Expected behavior

bucket should be provisioned without issue

Actual behavior

see above

I see that source_policy_documents was added in v3.28.0 of Terraform AWS provider, so we need to update versions.tf in the module (I will make a PR now), but if you have 3.36.0 already it should not be a problem.
Could you double-check that you are not using a version older than 3.28.0?

v1.25.0 has been just released. Please give it a try.

ah yes, this was my bad - one project is pinned to v3.20 and this was that one project. all good, thanks @antonbabenko !


-headless for unit tests?

Running unit tests spawns a lot of focus-stealing windows. Firefox has a -headless launch flag, but I can't seem to be able to force it correctly. I tried adding
firefoxArgs: ['-headless'] here but that does not have an effect it seems. Any ideas?

That's exactly what I do if I want to run the tests in headless mode (which is not often, because my window manager opens the windows in the background, and they don't steal the focus). It works for me on Linux and I just tried it on Windows 10 and it works there as well. I have no idea why it doesn't work for you.


[beta] project landing pages need CDN link and link to test suite pen

The following files need to be updated with the correct URL for the blank pen which houses the test suites (right now it links to the same pen on an un-official codepen account which I was using to test these) and the correct CDN link (it currently reflects my repo, but have a new CDN since the repo transferred ownership):
freeCodeCamp/seed/challenges/01-responsive-web-design/responsive-web-design-projects.json
freeCodeCamp/seed/challenges/03-front-end-libraries/front-end-libraries-projects.json
freeCodeCamp/seed/challenges/04-data-visualization/data-visualization-projects.json
I'm happy to take this one on since I know what needs to be changed where.
Also @QuincyLarson - 1 thing:

I know we were trying not to have a lot of copy for these, but I think for the calc project, the landing page is a good place to make a note about the 2 different types of calc logic, since this issue has been raised so many times. (including one just today :smile: ) It is a bit long to include in the user stories themselves.

Here is the note:

Note On Calculator Logic: It should be noted that there are two main schools of thought on calculator input logic: immediate execution and formula logic (our example utilizes formula logic and observes order of operation precedence, immediate execution does not). Either is acceptable, but please note that depending on which you choose, your calculator may yield different results than ours for certain equations (see below example). As long as your math can be verified by another production calculator, please do not consider this a bug.
EXAMPLE:

3 + 5 x 6 - 2 / 4 =
- Immediate Execution Logic: 11.5
- Formula/Expression Logic: 32.5

@no-stack-dub-sack Thanks for creating this issue, and for the additional details on the calculator app. I agree with your recommended changes, and that you're the ideal person to do this since you're familiar with these projects.


Fix statement response

fixes #916

/build

/build

/build

@cometta can you try ghcr.io/exacaster/lighter:919-spark3.5.1, looks like we had one dependency missing. I guess we need to do more testing before releasing, 0.1.0 seems to have quite a few problems :(.


chore: deactivate explicitly ngwaf

Is this to try to debug why it's not currently reporting? What's the purpose of setting the percentage to 100 while deactivating?


Use whole button (commit graph) as link

Update html template to use whole button as link, not only text inside button.

\cc @geek1011  @Fastidious

It would help is this was accompanied by a screenshot. You know, "an image is worth..."

@Fastidious Sure, updated with screenshots. Hope its clear now. Thx.

@Morlinest thanks.

LGTM

LGTM

Thank you very much


Version bump: http-parser-2.6.2

This is an adaption of the bump that was introduced in the nodejs tree. Hopefully we can improve this workflow moving forward since we're adding subtle discrepancies between the codebases.
Also, add a test for obstext characters.
Guessing this could be dropped in favour of #283 (and moving the test commit there). Your call.

ping @indutny, @jasnell! Again; happy to see #283 merge instead. Your call -- I mostly want a release and hopefully get commits in here moving forward.

Just a note; we can't use master to cut 2.6.2 any longer -- there's already been a commit landed that would introduce further discrepancies between the nodejs version of http-parser and this repo. An alternative would be branching off prior the last commit to master or just jump to 2.6.3 and import that to nodejs (making sure all changes follow). I can help out having a look at/review other open pr's if we're looking to get some changes in.

oh... this one works too. LGTM

Landed in dbcda19 and 5651aea


:sparkles: Support Mocking for Testing

Ensure neoclient-created clients can be easily mocked for integration tests. E.g. by implementing a MockNeoClient.
Note: Can supply httpx.Client an app! (WSGI/ASGI)
If this is the case, perhaps a real NeoClient instance should be used against a mock server?
Assuming a mock client was to be made, it would likely work a bit like this:
from neoclient import MockNeoClient

client = MockNeoClient()

@client.get("/greet")
def greet(name: str) -> dict:
    return {"message": name}

In this event, no composition or resolution ever happens. But how would you test middleware etc. :/
Maybe the user must specify their own fake client, which implements the Client interface ((Request, /) -> Response).

Provide test utilities from a separate neoclient-test library?


add Willow filter

Aw you beat me to making a PR for Willow! I think adding some halo effect would be good for this:
  &::after {
    background: radial-gradient(circle, transparent 55%, #000 200%);
    mix-blend-mode: multiply;
  }

Also change values from 0.02 to .02 since that's the convention.

:+1: what @jagtalon said

yeah, @jagtalon ,  i have adjust the effect according by your suggestion, but , i think the circle center position value :  left bottom is better than default center , like that:
  &::after {
    background: radial-gradient(left bottom, circle, transparent 55%, #000 200%);
     mix-blend-mode: multiply;
    }

do you think so ?   thanks a lot !

I think this is a good first take, but the color seems a bit dark. The willow filter has a radial gradient that is lighter near the top center -- see these:

it also has a very light pinkish overlay instead of being fully greyscale

ok, i will attemp to improve it

Hey Ivpeng! can you resubmit Sierra (there's a lot of breaking with the new structure and this PR includes two filters)
I went through and fixed the pink-grey issue using hue and overlay and not grayscaling for Willow, so I'm going to use the other solution I found :/


[BUG] Invoking workspace handler on Lazy.jl package never stops running

Please search existing issues to avoid duplicates.
Details

Atom version: master
Julia version: v1.2
OS:
Package versions:

Atom.jl: master
Lazy.jl: v0.14.0
julia-client: master
ink: master

notes
Once this happens, this will continue to happen even after restarting Julia process.

Dup of https://github.com/MikeInnes/Lazy.jl/issues/90

oops, sorry.


Fix inbox_get method of DefaultBackend

While working with the REST API, I ran into a problem with the inbox-detail view.
The inbox-list view serializes all messages in a user's inbox. The "id" values in the JSON response are primary keys of Message objects (when using the DefaultBackend). The /inbox/{id}/ endpoint provides a detail view of those messages. In the process, however, the "id" (of a message) is inadvertently used as the primary key of an Inbox object:
https://github.com/evonove/django-stored-messages/blob/master/stored_messages/backends/default/backend.py#L43
Why doesn't this show up in the current tests? Message and Inbox objects are often created in pairs. If the database starts numbering both tables at 1, corresponding objects will have the same primary key. Of course, you cannot rely on this.
I created a test that demonstrates the problem. By sending the same message to two users, the primary keys of the underlying message and inbox tables are no longer synchronous. In this situation, user2 can no longer obtain a detail view if user1 marks his message as read.
While writing my test, I noticed that api functions such as "add_message_for" are not using the STORAGE_BACKEND overridden by TestRESTApiWithRedis. I fixed this as well, by doing an inline import. NB: views.py is already doing it this way, so this fix is consistent with that.

Not sure how to read this output: https://travis-ci.org/evonove/django-stored-messages/jobs/157436805. Flake8 under Python 3.5.2 is complaining about files I didn't touch?

@byrman: since june this year (=after the last time the checks were run) flake8/pyflakes added an extra error for undefined variables from a "star" import. See http://flake8.pycqa.org/en/latest/release-notes/2.6.0.html
So if you change the "ignore" line in the top-level tox.ini to:
ignore = F403,F405

... then the tests should run OK again.

Travis is happy again. Thanks, @reinout. Perhaps it's better to address the star imports, but that's something for another pull request (imho).


修正错误链接

We appreciate your feedback. Our current focus is on translating Swift 6 content, while older versions will remain as is. Thank you for your understanding


GenerateTrials' object has no attribute 'RewardProb'

21 | GenerateTrials' object has no attribute 'RewardProb' | MyFunctions.py | _ShowInformation | line 916 | ephys1

Closing this issue since it hasn't happened in three weeks


[IconButton] IconButton sizes are no longer fixed and vary

As of v3.1.x, the IconButton size was removed and the padding was changed, due to this commit:
https://github.com/mui-org/material-ui/commit/fc42dde03f4b78379b2d8ce32aa923ac283b32f4#diff-fde406414bd717fcea45f653b5632078
The icon buttons now vary in size and when they are next to each other especially, it's very odd and jarring. Was there a reason the width / height of 48 was removed and the padding went from 0 to 12? We use the FontAwesome library for our icons but that should not (and doesn't appear to) have an impact.

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

The buttons should be sized consistently
Current Behavior

They vary in size
Steps to Reproduce

Link:

Context

Your Environment

Tech
Version

Material-UI
v3.1.x

React

Browser

TypeScript

etc.

Could you add a repro so that a possible fix can test against that?

Your issue has been closed because it does not conform to our issue requirements.
Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!


Fixes issues #21821 and #21819

Description:
This is a fix for issues #21821 and #21819
Related issue (if applicable): fixes #21821
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

Would it be possible to merge ASAP, please. Users are waiting for quick fix.

Well, I'm not sure if we release a 0.89.2 but it's tagged.

@pvizeli Thanks a lot!  Seems I haven't tested it well.

my sensor with sunset doesn't work anymore after this merge
- platform: tod
  name: Evening
  after: sunset
  after_offset: '-01:00:00'
  before: '21:00:00'

The entity isn't being created at all.

Hi Leonardo,
could you please provide any logs? Wha do you mean by entity isn't being
created?
Thanks,
Klaus
On Mon, Mar 11, 2019 at 10:40 PM Leonardo Merza<EMAIL_ADDRESS>wrote:

my sensor with sunset doesn't work anymore after this merge

platform: tod
name: Evening
after: sunset
after_offset: '-01:00:00'
before: '21:00:00'

The entity isn't being created at all.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/21911#issuecomment-471741138,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXYmtmRLLZjET-ke8PdVbfQofUBdjWRks5vVs1pgaJpZM4bnhay
.

sorry seemed to be a fluke. It works after another restart. Thanks for fixing the offset issue!


Deploy grafana-agent for rules via collections

The grafana agent on the MC used to send prometheus rules to mimir was deployed by hand. Let's deploy it via a collection and make sure we deploy it as a deployment instead of a daemonset to reduce usage

Adding mimir-grafana-agent to shared-config repo
Push mimir-grafana-agent to CAPA collection in grafana-agent repo

Let's deploy the app in the prometheus rules repo

Regarding a rules to check PrometheusRules are properly sent to mimir, we have those metrics available:
https://grafana.com/docs/agent/latest/flow/reference/components/mimir.rules.kubernetes/#debug-metrics
We can make a rules based on mimir_rules_events_failed_total > 0 for a period.
WDYT @giantswarm/team-atlas ?

Makes sense yes but do we have a grafana agent down alert as well? And I think if rules fail for 1h during business hours we can page. WDYT?
Aldo have you checked the mixins https://github.com/grafana/agent/tree/main/operations/agent-flow-mixin ?

Wait monday to release prometheus-rules...
I open a new ticket to handle alert and dashboard

Why do we need a separate issue though? This makes it really hard to track what happened, especially as it is not related to the epic. I would rather we rename the issue and add the alert in as a subtack of this issue

We currently don't have any rules on grafana-agent down.
We should have one for the agent responsible to scrape k8s events.
Maybe it should be addressed in an other ticket, right ?

I would think so yes but you can still add the alert today :)


Improvement: Add ability to ingest .epub format books

As a user, I would like to be able to select / upload an epub document/book, have the text content of the document extracted, and ingested into the database with keyword tagging.
I would further like ability to search across it and use it for some sort of Q/A RAG thing in the future. (Will split off into its own issue once epub ingestion is supported)
Calibre cli: (Calibre CLI -> convert X book format to raw text -> Ingest into DB)
https://manual.calibre-ebook.com/generated/en/ebook-convert.html
https://manual.calibre-ebook.com/conversion.html#conversion
Existing projects:
https://github.com/Medusa-ML/Book-Summarizer/tree/main
https://unix.stackexchange.com/questions/647686/convert-epub-to-txt-and-preserve-original-formatting

Will use pandoc, have the user supply the converted txt file:
pandoc -f epub -t plain -o filename.txt filename.epub

Closing this as I don't want to integrate pandoc right now. Don't feel its a big ask considering everything else necessary to get this working...


character order scrambled when entering a formula

(using Plotly's grid with this plugin, in Figlinq, you'll receive more info on Figlinq soon):
Typing blindly, there is a scrambling of characters going on.
To move the I-beam cursor, use the arrow keys on the keyboard as soon as you notice the cell contents is wrong.
https://user-images.githubusercontent.com/82650901/191288468-72f286f4-8d2b-46da-a34c-5064c480c7c1.mov

Hi,
Ok, i have reproduct the problem on my other version. I will patch that in next version

Hi,
New version is available on https://repo.gbonnaire.fr/product/jss-plugin-formula (2.2.12) with patch
Have good day


Are sidechains broken in PoW?

Might be a selling point for Cosmos:
https://bitcointalk.org/index.php?topic=1319681.msg17096880#msg17096880
Excuse me, I am not supposed to post here. Thought I'd share and then leave again.
P.S. if you can't solve the homework problem, you'll find the answer in section "7.2.6 Unbounded Transaction Formats Without Forks" of my whitepaper whenever it is published.

Your insights are much desired here, Shelby3.  Thanks for sharing.

Regarding the issue of miners "stealing" fees from others, causing a fight to the bottom, it seems that the source of the problem is the "high influence" of where-the-tx-goes determining who-gets-the-fee.  What if the fee is more disassociated, or spread out?  What if the fee gets spread out to the next 100 block miners, say, rather than limiting the recipients to just 1 or 2 blocks?  What if in addition, some nominal % (e.g. 5%) of the block's fees go to the current miner, so as to incentivize the proper collection of txs?

@jaekwon afaics, changing the number of blocks which share the fees, won't make it incentives compatible. The issue is that hashrate is concentrated in PoW because the system is a power vacuum driven by non-diminishing marginal-utility of controlling a greater portion of the systemic hashrate. So it doesn't matter how many blocks are involved since the probabilities of those who win blocks are the same over any number of blocks.
And another of the other salient points is the merged mining is an attack vector if not more than 50% of the miners from the main chain participate. And if they do, then the point of scaling was defeated.


Download all filings for specific/multiple companies.

Describe the bug
I am trying to download all available files for a specific company or companies using the following code.
import secedgar as sec
from secedgar import filings, FilingType

# 10Q filings for Apple and Facebook (tickers "aapl" and "fb")
my_filings = filings(cik_lookup=["aapl"],
                    filing_type=None,
                    user_agent="xxx (XXX")
my_filings.save("/mnt/f/SECCIKs")

Returns:
AttributeError: 'NoneType' object has no attribute 'value'
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Saving of all files for a specific company/multiple companies.

You need to specify which filing type you want to get (for example, filing_type=FilingType.FILING_10Q).


Image pull stuck when using a registry endpoint list

This could be a duplicate of #4078. I however still think that we are hitting a different issue.
Description
We are running containerd v1.3.3 as the container runtime for k8s. While introducing Kraken as a peer-to-peer image distribution layer, we started experiencing random appearances of Pods being stuck in PodInitializing or Init state. The k8s event for which this is happening is always Pulling image.... Our registry endpoint configuration looks like this:
[plugins.cri.registry.mirrors]
  [plugins.cri.registry.mirrors."registry.example.net"]
    endpoint = ["http://localhost:30081"]
                           ↳ Pointing to the local Kraken agent

The issue does not appear 100% of the time. In our test runs we had clusters with 3 master nodes, 3 etcd nodes and 5 minions. In these cases, at leat one Cilium Pod (spawned by a DeamonSet on all nodes) was stuck in PodInitializing or Init state (which had a ripple effect across the cluster as most other Pod cannot start without a fully set up overlay network on the node).
Steps to reproduce the issue:

Run a k8s cluster (v1.15 or v1.13) with containerd v1.3.3 as the container runtime
Setup the containerd registry endpoint list like seen above
Create a Pod which image is pointing to e.g. https://registry.example.net/mirror/busybox

Describe the results you received:
The Pod will get stuck in PodInitializing or Init state (if it has an init container) with the latest k8s event being Pulling image....
Describe the results you expected:
Containerd tries to pull the image from http://localhost:30081 and receives a connection refused (or maybe even timeout) as the Kraken agent is not yet started (because the overlay network is not set up yet). It then falls back to use the registry hostname as specified in the Pod definition (registry.example.net) and successfully pulls the image from there.
Output of containerd --version:
containerd github.com/containerd/containerd 1.3.3-0ubuntu1~18.04.2

Any other relevant information:

The issue did not appear in our previous version of containerd (v1.2.10-3).
The issue does not seem to appear when running crictl pull image-name.
The issue can be fixed by either:

Pulling the image manually on this node, killing the Pod and restarting it (basically skipping the automatic image pull action).
Not using a registry endpoint list (which is not really a long-term alternative).

The issue will even occur when the registry endpoint list holds the actual name of the registry as a second endpoint in case the fallback to the registry name fails:[plugins.cri.registry.mirrors]
  [plugins.cri.registry.mirrors."registry.example.net"]
    endpoint = ["http://localhost:30081", "https://registry.example.net"]

The issue will even occur when the registry endpoint list only holds the actual name of the registry as a single endpoint like this:[plugins.cri.registry.mirrors]
  [plugins.cri.registry.mirrors."registry.example.net"]
    endpoint = ["https://registry.example.net"]

I unfortunately no longer have the full containerd debug log from the day that showed the behaviour most clearly. The log however showed, amongst other things, these events (for pulling an image consisting of three layers):

One do request messages target at registry.example.net to fetch the image manifest.
One fetch response received confirming the download of the manifest
Three do request messages target at localhost to fetch the image layers.
No fetch response received message for ~20 minutes.
After ~20 minutes, the requests are issued again targeted at registry.example.net and succeed.

	Apr 02 14:59:45 minion3 containerd[1678]: time="2020-04-02T14:59:45.339215491Z" level=debug msg="do request" digest="sha256:7c" mediatype=application/vnd.docker.distribution.manifest.v2+json request.header.accept="application/vnd.docker.distribution.manifest.v2+json, */*" request.header.user-agent="containerd/1.3.3-0ubuntu1~18.04.2b" request.method=GET size=739 url="https://registry.example.net/v2/mirror/image/manifests/sha256:7c"

	Apr 02 14:59:45 minion3 containerd[1678]: time="2020-04-02T14:59:45.566764003Z" level=debug msg="fetch response received" digest="sha256:7c" mediatype=application/vnd.docker.distribution.manifest.v2+json response.header.content-length=739 response.header.content-type=application/vnd.docker.distribution.manifest.v2+json response.header.date="Thu, 02 Apr 2020 14:59:45 GMT" response.header.docker-content-digest="sha256:7c" response.header.docker-distribution-api-version=registry/2.0 response.header.etag="\"sha256:7c\"" response.header.server="beegoServer:1.12.1" response.header.set-cookie="sid=e2d06f703233a50af3a98e5c4b92c9f4; Path=/; HttpOnly" response.status="200 OK" size=739 url="https://registry.example.net/v2/mirror/image/manifests/sha256:7c"

	Apr 02 14:59:46 minion3 containerd[1678]: time="2020-04-02T14:59:46.764522990Z" level=debug msg="do request" digest="sha256:65" mediatype=application/vnd.docker.image.rootfs.diff.tar.gzip request.header.accept="application/vnd.docker.image.rootfs.diff.tar.gzip, */*" request.header.user-agent="containerd/1.3.3-0ubuntu1~18.04.2b" request.method=GET size=132022 url="http://localhost:30081/v2/mirror/image/blobs/sha256:65"

	Apr 02 14:59:46 minion3 containerd[1678]: time="2020-04-02T14:59:46.773267710Z" level=debug msg="do request" digest="sha256:70" mediatype=application/vnd.docker.image.rootfs.diff.tar.gzip request.header.accept="application/vnd.docker.image.rootfs.diff.tar.gzip, */*" request.header.user-agent="containerd/1.3.3-0ubuntu1~18.04.2b" request.method=GET size=16148261 url="http://localhost:30081/v2/mirror/image/blobs/sha256:70"

	Apr 02 14:59:46 minion3 containerd[1678]: time="2020-04-02T14:59:46.786073206Z" level=debug msg="do request" digest="sha256:cf" mediatype=application/vnd.docker.container.image.v1+json request.header.accept="application/vnd.docker.container.image.v1+json, */*" request.header.user-agent="containerd/1.3.3-0ubuntu1~18.04.2b" request.method=GET size=2168 url="http://localhost:30081/v2/mirror/image/blobs/sha256:cf"

Try with version 1.3.4
It seems this issue is fixed in https://github.com/containerd/containerd/pull/4007

Thanks @arpitjindal97 for the feedback. I didn't notice the newer version because there wasn't a build in our package repo.

I can confirm that v1.3.4 of containerd solves this issue. Thank you!


"Skipping locked wallet" instead of "was confirmed to peers" in log

Does the wallet need to be unlocked to forward blocks to peers?
Wallet unlocked:
[2018-01-19 14:12:08.345127]: Block 079D1E89273C9CB82F4F46F6E4C216FCCA05049F34E19D94687A33D81E8738F9 was confirmed to peers
[2018-01-19 14:12:08.356779]: Block 3960F22B4EA61D5543750DB5C0C1A1208F0DE51CD28D85512523E7638E1F0D64 was confirmed to peers
[2018-01-19 14:12:08.356977]: Block<PHONE_NUMBER>B5D53177DDBB56D27A15180F9378C2FD11736B2C4A0D2614281BE2 was confirmed to peers
[2018-01-19 14:12:08.357044]: Block 902188AF870573FC8F050A979FF750DE8D1E7841E49772EB85585B4A2EB61E94 was confirmed to peers

wallet locked:
[2018-01-19 14:12:31.527950]: Skipping locked wallet 5BF27F4444557A6639C6EE930944598029F26C1F2D62AA250B00EFDE4DC98604 with account xrb_31msnnyxn6hjfifo1aepbfkfd9wnse4765y8q4zxbxaxcdkr3kijarcqghho
[2018-01-19 14:12:31.632625]: Skipping locked wallet 5BF27F4444557A6639C6EE930944598029F26C1F2D62AA250B00EFDE4DC98604 with account xrb_31msnnyxn6hjfifo1aepbfkfd9wnse4765y8q4zxbxaxcdkr3kijarcqghho
[2018-01-19 14:12:31.666873]: Skipping locked wallet 5BF27F4444557A6639C6EE930944598029F26C1F2D62AA250B00EFDE4DC98604 with account xrb_31msnnyxn6hjfifo1aepbfkfd9wnse4765y8q4zxbxaxcdkr3kijarcqghho

Confirming requires signing which requires an unlocked wallet.


docs: Automated Changelog Update for v5.0.1-beta3.5

copilot:all
Automated changes by create-pull-request GitHub action

🤖 Generated by lychee action
Summary

Status
Count

🔍 Total
2191

✅ Successful
516

⏳ Timeouts
0

🔀 Redirected
0

👻 Excluded
1672

❓ Unknown
0

🚫 Errors
1

Errors per input
Errors in docs/blog/zh-Hans/2024/how-to-deploy-and-configure-meilisearch-using-docker/index.md

[403] https://zhuanlan.zhihu.com/p/703201822 | Failed: Network error: Forbidden

Full action output
Full Github Actions output


moon support

How about adding support for the moon?

Previously discussed in https://github.com/AitorDB/home-assistant-sun-card/issues/144

That's an interesting idea; let's investigate it. I can look into it next week. After a quick glance at the moon integration, it doesn't seem to provide rise/set times; only the moon phase. How could we support the moon's position? Any ideas?

Using the AstroWeather integration you will get these sensors:

You can use this:Broham/suncalcPy: A python implementation of the SunCalc javascript library.github.com Ormourner/suncalc: A tiny JavaScript library for calculating sun/moon positions and phases.github.comOn 18 Mar 2023, at 20:39, Tom-ahawk @.***> wrote:
Using the AstroWeather integration you will get these sensors:
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I would love to see the moon in the same card with a different color. looking forward to see your developments on this.

@ThomDietrich @avataar there are several options here and I think we can add optional support for the moon. I'd love to see this too. I think we can go ahead with the rename.

It's a good idea but let's not jump ahead with renaming things just yet. I'd first like to see the project stable and released before we decide on the bright future :)

All, please hold your horses :)
@avataar @selfish the only thing we need to discuss and decide ASAP is, whether we want to rename the project BEFORE publishing to HACS. Options:

"Sun Card" - the name many are used to from the parent project. I believe it wouldn't be totally illogical to add moon support, ISS support, Jupiter support, ... but it will surprise new users.
"Sun Moon Card" or similar - The name includes "Moon", but is limited to it. I honestly wonder if anyone is interested in other celestial objects?
"Astrology Card", "Sky Card" or similar - Anticipate sun, moon, X support. I am not in favor of ditching the known "Sun Card" name

I was thinking of other stuff that also could refer to more than just the sun:

dashboard-daybreak-card
dashboard-horizon-card
dashboard-atmosphere-card
dashboard-sky-card
dashboard-star-card

"Sun Card" - the name many are used to from the parent project. I believe it wouldn't be totally illogical to add moon support, ISS support, Jupiter support, ... but it will surprise new users.

Since this is what the card currently does, it's the most fitting and it's a drop in replacement for the original project, i.e. having "custom:sun-card" in your existing dashboard will continue to work.

"Sun Moon Card" or similar - The name includes "Moon", but is limited to it. I honestly wonder if anyone is interested in other celestial objects?

Since we still don't have moon support, the name doesn't fit. I don't believe other celestial objects are needed either.

"Astrology Card", "Sky Card", "Sun+X Card" or similar - Anticipate sun, and all further support. I am not in favor of ditching the known "Sun Card" name but happy to hear name suggestions.

"Sky Card" is a good fit if we really want to reserve the opportunity to add something other than the Sun in the future.
"Horizon Card" (based on @tjorim's suggestions) sounds good too.
Regarding the name of the repository, I think "lovelace-xxx-card" is better than "dashboard-xxx-card" as "lovelace" is a very specific term that refers to HA unambiguously while "dashboard" is very generic, but I have no strong opinion on that one.

I love the horizon-card option, leaves all options open for further developments.

The name lovelace-horizon-card is certainly quite neat.
Let's have the community decide:

React with 🎉 if you support the name lovelace-horizon-card -> "Horizon Card"
React with 🚀 if you prefer to stay with the established name lovelace-sun-card -> "Sun Card", while we would still add moon support, which would be slightly illogical but not a dealbreaker

"Sky card" would have my vote. 😜
Or "Astro card".

@edwardtfn you caught me off guard there. I feel ashamed that I've mixed terms known from clown culture and science 🙈
The majority has spoken :) We have a winner.

Nooo  -- I tuned in too late! Would have voted for lovelace-luminary-card or lovelace-luminaries-card.

@lcnittl care to elaborate? :-) https://dictionary.cambridge.org/de/worterbuch/englisch/luminary

@ThomDietrich absolutely!
It is a (slightly older, probably) term for (shining) celestial/heavenly bodies.
From https://en.wikipedia.org/wiki/Luminary

Luminary
A celestial body, as the sun or moon or an object that gives light; or, a person of eminence or brilliant achievement. From Old French luminarie or late Latin luminarium, from Latin lumen, lumin- "light".

From https://en.wiktionary.org/wiki/luminary#Noun

luminary (plural luminaries)
[...]
2) (archaic) A body that gives light; especially, one of the heavenly bodies.
[...]

So a nice collective term for both sun and moon (and others).

Love the idea of moon support.  I currently stack my horizon card with an entities card with a moon phase template entity that has a dynamic image icon for the moon phase.  It would be cool to see something like this integrated right into the horizon card.

Here is a preview of the upcoming Moon support (different locations and times):

What is the new Moon stuff:

Showing the Moon as it moves above and below the horizon visually matching what you'd see at your location/time
Support for showing the azimuth and elevation - I believe it's best if shown together with those of the Sun, with the appropriate astronomical symbols. If only the azimuth/elevation of one of the bodies is configured to be shown, no symbol will be displayed.
Support for showing moonrise, moonset and moon phase. The phase will be rotated to approximately match your latitude but that can be overridden via config option.

This is how it looks with different fields shown/hidden:

There are other non-moon related changes, see #40 for details.

A celestial body, as the sun or moon or an object that gives light;

It's a bit questionable call the Moon as an object that "gives light", no? 😜
If you say the Moon gives light you have to say that any visible object gives light.

Last teaser but I just had to share. It feels really good when the Moon is exactly where the Horizon card says it should be :) Local time 2:17.

Coming out soon!


Print help dialogue when no arguments are passed

A parameter to zinit() should be added. This behavior is not always suitable.

Not a desired feature


Get all pre-commit issues passing

Is your feature request related to a problem? Please describe.
Calina recently intro'd the optional use of the pre-commit tool into developers.md. It's cool!
If you use it when you're doing a commit, it will check the files that you've changed in your commit.
However you can also run it against the whole existing codebase via:
pre-commit run --all-files

I tried this! It changed about 6 files, and had a few failures. It would be good for pre-commit to be fully happy about the existing codebase, it will help us to move forward with less friction.
Describe the solution you'd like
Run pre-commit run --all-files. Commit the changes it's made (once unit tests pass). Then fix all the issues it reports (and ensure unit tests etc keep passing).

All the pre-commits have been run first on the entire codebase and both black and flake8 are required checks as GitHub actions. The reason for the pre-commit is so that you already have a local way of bumping into potential problems from the GitHub actions checks. This means that the failures you found are due to people not using pre-commit before (it was in the docs), merging branches without passing Github Actions, or simply conflicts/automatic merges by git.
I'll take a look later to see if everything is correctly mirrored from pre-commit checks to Github actions checks (I believe aquarius might not have the isort tool) and do a correction on all repos.


Scrolling seems inefficient in Safari

Try this https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame


dm-serializer redefines the global CSV constant on Ruby 1.8

dm-serializer/to_csv.rb redefines the global CSV constant to be an alias to FasterCSV when running under Ruby 1.8. While I understand the desire to keep the remainder of the code the same under 1.8 and 1.9, this causes two problems:

If the built-in CSV library has already been required when dm-serializer is loaded, you get a constant redefinition warning.
If the built-in CSV library is required after dm-serializer (e.g., by another library) you get a superclass mismatch for class Row error.

An alternative: define a method on DataMapper::Serializer that returns the appropriate module to use (CSV or FasterCSV) depending on the ruby version.

Does anyone still need this? Ruby 1.8 (and 1.9 for that matter) are unsupported any longer. I'm not sure we have the people to maintain support for these versions. If you are still using 1.8 please leave a comment and I'll reopen.


use cpp 17

Purpose
build with humble and rolling
Approach
use cpp 17
can be reverted after some fix lands in those repos

cpp 20 doesn't work with humble/rolling ??

cpp 20 doesn't work with humble/rolling ??

theres just currently some weird bug, and this is the easiest fix.  Theres already a proper fix proposed, merged even, but does seem yet released in the latest packages


Unity Catalog add modelVersions and registeredModels api endpoints

Add api endpoints for Model Versions
https://docs.databricks.com/api/workspace/modelversions

Add api endpoints for Registered Models
https://docs.databricks.com/api/workspace/registeredmodels

Update: I've made the relevant changes to add these endpoints and unit tests are passing. I will submit a pull request sometime soon

Included in #206


error on focus on vs-select

hello .

Mac Os Mojave
Node.js version 10.7.0
Vuesax version : 3.7.1
Browser version : Chrome 70.0.3538.77
Which package manager did you use for the install? NPM

I getting an error while clicking select, the error is
1 - Uncaught TypeError: _this2.$children[0].focusValue is not a function
In the sample code ( https://jsfiddle.net/vicvillalobos/gvczfyp0/ ) , this error exists.
please check console log after click on selectbox .

2 - after change tab , getting this error :

@brunokunace : This problem is similar to the other problem, but with the difference that the error is also in the other part.

@webafra @brunokunace i could not find the other one. The problem was solved? I'm having the same error.


MINT CR2-2022: OCSP Stapling

@kenji-acumen  Opening this GitHub issue to discuss if NDcPP v3.0 should add support for OCSP stapling.
MINT, please feel free to add your comments whether NDcPP v3.0 should support this or not.
Reasons for adding support for OCSP stapling:

For TLS client implementations that support OCSP stapling, the cost of an OCSP validation is reduced.
The collaborative Protection Profile for Application Software as well as NIAP PPs support OCSP stapling.

Reasons for not adding support for OCSP stapling:

OCSP stapling supports only one OCSP response at a time, which may not meet the FTP_ITC.1 requirement for TLS client connections where X.509 certificates are used to authenticate remote end points and revocation checking must support a certificate chain length of three.  RFC 6961 - Multiple Certificate Status Request Extension - added support for sending multiple OCSP responses but appears to have limited widespread support.

TLS 1.3 removed this limitation altogether.   See https://datatracker.ietf.org/doc/html/rfc8446#section-<IP_ADDRESS>).  With TLS 1.3, a server can send multiple OCSP responses, i.e., one for each certificate in the certificate chain, which deprecates the need to support RFC 6961.

This captures the concerns I mentioned on the call. I do not believe OCSP Multi-Stapling (RFC 6961) is widely supported, so since it is already been obsoleted by RFC8446, I would not expect it to achieve wide support. I don't believe it is worth the effort to add OCSP multi-stapling.
As far as whether to add OCSP stapling, it comes down to whether the NDiTC is OK with only having end-entity certificates being revocation checked (i.e., not checking ICAs). I don't have a strong position either way.
If we add OCSP stapling, we will need to consider and clarify testing with TLSv1.2 vs. TLSv1.3. This is a complication the NIAP PPs don't currently address.

This is resolved by pointing to X.509 Functional Package which has support for OCSP stapling and OCSP multi-stapling.


chore(deps): update terraform terraform-ibm-modules/icd-postgresql/ibm to v3.19.16

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/icd-postgresql/ibm (source)
module
patch
3.19.15 -> 3.19.16

Release Notes

terraform-ibm-modules/terraform-ibm-icd-postgresql (terraform-ibm-modules/icd-postgresql/ibm)
v3.19.16
Compare Source
Bug Fixes

deps: update terraform ibm to latest for deployable architectures (#545) (4bbc6be)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline


Interactive playground eats arrow keys

Wasn't able to reproduce but it went like this

had the welcome page showing
went into a TS file
trigger peek references, up/down arrows don't work to navigate in tree
enable trace log and see this KeybindingService#dispatch ↓ workbench.action.interactivePlayground.arrowDown

So, there must be something wrong with its context key definition but I can't say how it happened...
[2020-09-02 12:58:13.865] [renderer3] [trace] CommandService#executeCommand workbench.action.interactivePlayground.arrowUp
[2020-09-02 12:58:13.865] [renderer3] [trace] telemetry/workbenchActionExecuted {"id":"workbench.action.interactivePlayground.arrowUp","from":"keybinding"}
[2020-09-02 12:58:15.778] [renderer3] [trace] KeybindingService#dispatch ↓ workbench.action.interactivePlayground.arrowDown
[2020-09-02 12:58:15.778] [renderer3] [trace] CommandService#executeCommand workbench.action.interactivePlayground.arrowDown
[2020-09-02 12:58:15.778] [renderer3] [trace] telemetry/workbenchActionExecuted {"id":"workbench.action.interactivePlayground.arrowDown","from":"keybinding"}

I have a possibly related scenario:

Did not have the welcome page anywhere.
Opened a .ts file showing.
Triggered "Peek References".

Result:
✅ Up/down arrows work.
✅ Pressing enter to expand/collapse a file works.
❌ Pressing enter to navigate to a line does not work.


Proposed modal solution wont render modal in case of query parameters

Hello,
If you use the Modal solution proposed here: https://reacttraining.com/react-router/web/example/modal-gallery and pass query params to the modal route, then the modal will not render unless you refresh the page.
Repo with issue (2 pages where page 1 contains a link to a modal):
https://github.com/rgbskills/react-router-modal-query-param-issue

You need to put the query string in the search property of the location you're linking to:
      <Link
        to={{
          pathname: `/modal`,
          search: '?id=12'


Synthetic Flash

About the PR

Added a new flash with two charges instead of five. Replaced all of Sci's flashes with Synthetic Flashes.
Why / Balance

I've heard many complaints about Revs steamrolling because of high conversion rates because they literally only raid Sci and I read someone say something about Synthetic flashes with only two charges and thought this was a good idea to hopefully alleviate this. I didn't want to ruin Borgs by making flashes super expensive so I settled with this. Regular flashes can still be printed at secfabs so uh raid security I guess lmao.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

What do you think about providing a sprite for these "synthetic flashes"? Also, can you use these flashes to make borgs?

What do you think about providing a sprite for these "synthetic flashes"? Also, can you use these flashes to make borgs?

If I knew how to sprite I would and yes you can.

What do you think about providing a sprite for these "synthetic flashes"? Also, can you use these flashes to make borgs?

If I knew how to sprite I would and yes you can.

if you want i can sprite it for you

What do you think about providing a sprite for these "synthetic flashes"? Also, can you use these flashes to make borgs?

If I knew how to sprite I would and yes you can.

if you want i can sprite it for you

That would be greatly appreciated

whats the difference between a regular and synthetic flash? aside from the name and flash amount, what makes them synthetic?

made by sci gamers and not sec bozos :trollface:

do flashes grow on trees?

Anything is possible

This will make science even more of a target by headrevs while effecting the snowballing very slightly. Having 2 charges isn't an obstacle due to flashes themselves being very easy to make.

"Synthetic" is the wrong word. It implies that the normal flashes are somehow organic.

This will make science even more of a target by headrevs while effecting the snowballing very slightly. Having 2 charges isn't an obstacle due to flashes themselves being very easy to make.

We could always make it one charge

"Synthetic" is the wrong word. It implies that the normal flashes are somehow organic.

Yeah I just stole the word from an idea someone said on Discord. I'm open to name suggestions

i dont think that this should be be added, revs will just fill duffle bags with synthflashes and achieve the same thing, the only real change is more clutter from spent flashes and deconstructing the very station they are trying to rule to get more

Good PR, wouldn't say it solves the issue, though.
Wouldn't it make more sense to fix this issue by just making rev-flashes something that recharges/needs to be recharged/can be recharged so snowballing isn't as easy as it is now? This doesn't really fix the issue, its a band-aid on a giant gaping sword-wound. It helps, but not by a lot. I don't think this is really necessary, as whenever a new type of rev balancing is complete, this synthflash becomes useless.

Size increase too? You drive a hard bargain

NO PLEASE THATS NOT WHAT I MEAN

i think this kindof undermines the entire point of revs, its a conversion antag and is SUPPOSED to be a snowball, you get a few followers at the beginning and then you do something ballsy to get some more flashes to convert more people and overpower sec with numbers.
the answer isnt to nerf revs its to buff sec and give them better crow control gadgets like tear gas grenades or barrier grenades.
flashing people isnt without risk either because you could be outed as headrev and be hunted down, headrevs are still regular people and can be gunned down just as easily as anyone else

Wasn’t the consensus that “borg eyes” should be a different item entirely (that can’t flash)? Given it’s not hard for Sci to print massive amounts of these, I don’t see limiting the number to 2 actually solving anything.

I didn't even know about borg eyes but it'd probably help in phasing out flashes from sci, I'll look into it if nobody else is.

"Synthetic" is the wrong word. It implies that the normal flashes are somehow organic.

Yeah I just stole the word from an idea someone said on Discord. I'm open to name suggestions

Don't worry about it. The name comes from SS13, it's a synthetic flash designed to flash synthetic creatures, it can still stun an organic but it was made for borgs. That's why it's called synthetic flash. (At least I'm assuming, this is actually me entirely bullshitting and just guessing based on what I've seen in my brief time in SS13 sci)

As for the issue at hand. I think this is a step in the right direction. It may not fix the problem out right but it'll improve the flow a bit more until a proper fix is made. This is already a good change just in an over all way, not even just for revos.

i feel like having different names/designs is kinda unnecessary. Just add a variant that has reduced charges while keeping the same appearance. That's what 13 does, iirc.

i feel like having different names/designs is kinda unnecessary. Just add a variant that has reduced charges while keeping the same appearance. That's what 13 does, iirc.

It's changed. I'll miss my flashes that grow on trees.


Remove the code, "firstNonWhite"

My PR got locked.
I suggest the removal of
https://github.com/crystal-lang/crystal/blob/master/src/compiler/crystal/tools/playground/public/session.js#L518
      var firstNonWhite = 0;
      while (str[firstNonWhite] == ' ') {
        firstNonWhite++;
      }
      var rendered = "\u00a0".repeat(firstNonWhite) + str.substring(firstNonWhite);
      dom.append(document.createTextNode(rendered));

Or,  at least change the variable names. firstNonWhite can be conveyed as being very racist, and this kind of terminology should not exist in code. It has no place for it.
If you continue to delete my posts, I will continue to spam. Leave one open for discussion please.

@jhass Please help.

@bcardiff Please ban this user. Thank you.


Remove association-data index

We should evaluate usage of this index, and move to generating a file that can be read within data_pipeline and separately loaded into elasticsearch if necessary for rest_api

This is used by the API

Decision taken to close based on low priority and value at this point in platform refactor.


Fix Windows CI build

Use powershell for the build, instead of bash - I can't test this works without this being merged, but running the CI commands locally in powershell works fine, so they should run correctly in GitHub actions. There seem to be some path escaping issues or something in bash on Windows, so using powershell instead as that's a more standard option on Windows generally
Also remove the unnecessary warning - it isn't necessary, as picotool no longer throws an error with garbage coprocessor instructions
Fixes #1843

https://github.com/raspberrypi/pico-sdk/commits/develop/
Yay, green ticks :heavy_check_mark: :heavy_check_mark: :heavy_check_mark:


3.0.0-beta2 dashboard missing content type header --> html code as plain text in browser

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
switch from traefik V2.9 to V3.0.
deployed via helm version 20.8.0
repo: https://traefik.github.io/charts
after the update the dashboard does not work any more.
from what I can see the Content type header is missing on the http/https response to the browser.
accept-ranges: bytes
content-length: 3124
date: Sat, 28 Jan 2023 11:03:55 GMT
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-content-type-options: nosniff
x-xss-protection: 1; mode=block

What did you see instead?
plan html code

What version of Traefik are you using?
Version:      3.0.0-beta2
Codename:     beaufort
Go version:   go1.19.4
Built:        2022-12-07T16:32:34Z
OS/Arch:      linux/amd64
What is your environment & configuration?
---
apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: security
  namespace: traefik
spec:
  headers:
    customRequestHeaders:
      X-Forwarded-Proto: https
    sslRedirect: true
    browserXssFilter: true
    contentTypeNosniff: true
    #HSTS
    stsIncludeSubdomains: true
    stsPreload: true
    stsSeconds: 31536000
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  name: dashboard
  namespace: traefik
spec:
  tls:
    secretName: traefik-tls
  routes:
    - match: Host(`traefik.demo.test`) && (PathPrefix(`/api`) || PathPrefix(`/dashboard`))
      kind: Rule
      services:
        - name: api@internal
          kind: TraefikService
      middlewares:
        - name: security
          namespace: traefik

If applicable, please paste the log output in DEBUG level
No response

duplicate of #9647
Already fixed by #9622


Fixed clearing the back-buffer if canvas group doesn't have any items.

Fixes #54190.
The problem is caused because there is no clearing a backbuffer if we don't have any items in CanvasGroup (condition ci->canvas_group_owner != nullptr is always false).

Tested with existing project. Works as described.

Thanks!