text:
Docker events fails on windows

Currently this does not work with docker on windows.

Error: Error executing sub-child: docker events --format {{json .}} --filter image=selenium/standalone-chrome-debug

The following change to dockerEvents.js fixes it.
const DEFAULT_OPTIONS = {
  format: '"{{json .}}"'
};

@Sureiya strangely enough it fails on macOS :/ So you have tested with above change and it worked? The reason I ask is that above error can also appear when older version of Docker is installed (the one that doesn't support events).

Yes I have, I'm running the latest version of docker-desktop in windows.
I'm guessing we may need some more platform independent method to run the
command, or It may be that an upstream bug needs to be filed with docker on
windows? I'm leaning more towards the former.
On Tue., Jul. 30, 2019, 9:31 p.m. Simon Tsvilik, notifications@github.com
wrote:

@Sureiya https://github.com/Sureiya strangely enough it fails on macOS
:/ So you have tested with above change and it worked? The reason I ask is
that above error can also appear when older version of Docker is installed
(the one that doesn't support events).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stsvilik/wdio-docker-service/issues/56?email_source=notifications&email_token=AAB26AZQZNNGKDOKHO5AZPDQCDTQJA5CNFSM4IH62PSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3FY5ZA#issuecomment-516656868,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB26AZ42UIA2SXKTTPDAUTQCDTQJANCNFSM4IH62PSA
.

@Sureiya sorry for long delay - I'm in the middle of a house move, is there a way you could put together a PR for this fix?

Is there any workaround for this?

@Sureiya just to be sure, do you have Win 10 Pro? I need to know how to test this on a Windows VM

@serbanghita I am using Windows 10 Pro build 1903

I'm seeing the same issue running on Ubuntu 16.04.4.  I had another installation that was working fine before on the same server but appears to not be working anymore.
Docker version 18.06.0-ce, build 0ffa825

I'm embarrassed to say that I made a little mistake and didn't have privileges to run docker.  I must have been testing with running the docker image standalone before.  Still having some issues but I did resolve that one at least.

@webOS101 you almost made me think that Docker has fixed that inconsistency - guess not :)

@Sureiya and @webOS101  could you check the RC version on Windows to see if it fixes the problem?

i see this on mac (10.13.6) running docker 2.1.0.4 (39773).  engine 19.03.4.

That's with version 2.1.5.rc.0?

From: calltojohn notifications@github.com
Sent: Wednesday, December 4, 2019 8:34:30 AM
To: stsvilik/wdio-docker-service wdio-docker-service@noreply.github.com
Cc: Simon Tsvilik st777@msn.com; Comment comment@noreply.github.com
Subject: Re: [stsvilik/wdio-docker-service] Docker events fails on windows (#56)
i see this on mac (10.13.6) running docker 2.1.0.4 (39773). engine 19.03.4.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/stsvilik/wdio-docker-service/issues/56?email_source=notifications&email_token=AABC3UEZ77IT74C4LGJOQZLQW6WWNA5CNFSM4IH62PSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF5BCXI#issuecomment-561647965, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABC3UEFOQ6FT64RZWPDFYLQW6WWNANCNFSM4IH62PSA.

yeah.  2.1.5-rc.0

Would it be too much to ask for any of you to test my PR locally https://github.com/stsvilik/wdio-docker-service/pull/64. I added a code to handle docker events command based on OS, but looks like it doesn't work. I'm not really setup now to test on Windows :(

@calltojohn  and @webOS101  I have tested latest RC 2.1.5-rc.1 on my Windows machine and it works fine - do you mind giving it another shot?

I don't use Windows and my problem was unrelated, it was a configuration error on my part.

closing this issue for now

Hello! I just tested the latest RC 2.1.5-rc.1 on Windows, and I got the error :(

Thanks @stsvilik. I know we are talking about Windows here. On my personal MAC everything works fine but I am getting same error:
2020-02-04T14:38:11.092Z ERROR wdio-docker-service: Error: Error executing sub-child: docker events --format {{json\ .}} --filter image=<image> with latest release while running the same tests as part of CI/CD pipeline. We are using https://drone.io/ and deployed using drone-terraform.  Can you please suggest?

Upsetting part is that everything works on my Windows 10 at home :(. Would you be able to echo value of process.plarform in Node running on your CI?

From: prathameshnyt notifications@github.com
Sent: Tuesday, February 4, 2020 9:47:39 AM
To: stsvilik/wdio-docker-service wdio-docker-service@noreply.github.com
Cc: Simon Tsvilik st777@msn.com; Mention mention@noreply.github.com
Subject: Re: [stsvilik/wdio-docker-service] Docker events fails on windows (#56)
Thanks @stsvilikhttps://github.com/stsvilik. I know we are talking about Windows here. On my personal MAC everything works fine but I am getting same error:
2020-02-04T14:38:11.092Z ERROR wdio-docker-service: Error: Error executing sub-child: docker events --format {{json\ .}} --filter image= with latest release while running the same tests as part of CI/CD pipeline. We are using https://drone.io/ and deployed using drone-terraform. Can you please suggest?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/stsvilik/wdio-docker-service/issues/56?email_source=notifications&email_token=AABC3UE2GOVPF5NDZRDSF73RBF5YXA5CNFSM4IH62PSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKX4F7I#issuecomment-581944061, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABC3UETUEMUWCBHLG7HBYDRBF5YXANCNFSM4IH62PSA.

Hi @stsvilik , in case of my local MAC it's darwin and in case of CI it's linux . Please let me know in case you need any other information. Thanks for looking.

@prathameshnyt thank you for that! As I don't have all possible environments to test on this sort of information is really important. I believe that core of this issue is in that difference between how Docker on different OS's works. I did not know that linux was also a subject to this issue as the CI this package tests run on is also a Linux OS. I will look into running more tests under various systems.

Thank you so much @stsvilik for looking into it.
Thanks,
Prathamesh

@prathameshnyt apparently my refactoring of options serialization code few PR's ago also eliminated the need to format that docker events JSON option differently for different OS's (who knew).  With that said please give a shot to my latest version 2.3.0. Hope this settles this issue once and for all (fingers crossed).

https://github.com/stsvilik/wdio-docker-service/issues/63, Still its not working for me.

Thanks @stsvilik. Getting same error with 2.3.0 version.
Thanks,
Prathamesh

I guess it's something else. Anyway for you to get a printout of the log file generated by service?

From: prathameshnyt notifications@github.com
Sent: Wednesday, February 5, 2020 9:15:07 AM
To: stsvilik/wdio-docker-service wdio-docker-service@noreply.github.com
Cc: Simon Tsvilik st777@msn.com; Mention mention@noreply.github.com
Subject: Re: [stsvilik/wdio-docker-service] Docker events fails on windows (#56)
Thanks @stsvilikhttps://github.com/stsvilik. Getting same error with 2.3.0 version.
Thanks,
Prathamesh
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/stsvilik/wdio-docker-service/issues/56?email_source=notifications&email_token=AABC3UFCTBRDE5OBI7F4JUTRBLCWXA5CNFSM4IH62PSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK3SE3A#issuecomment-582427244, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABC3UGGF35CWZOYYP77OWDRBLCWXANCNFSM4IH62PSA.

I will check. Thanks.

I see the same error https://github.com/stsvilik/wdio-docker-service/issues/63#issuecomment-581997657 Thanks, Prathamesh

May, it's not waiting for Docker to come up and not retrying as well though we have
healthCheck: {
            url: 'http://localhost:4444',
            maxRetries: 3,
            inspectInterval: 2000,
            startDelay: 5000
        },

I killed docker application and started again on my local machine MAC, but before it starts completely, If I run the test, I am seeing above error.
Thanks,
Prathamesh

This is likely the issue, since starting docker doesn't guarantee the start of the app.

From: prathameshnyt notifications@github.com
Sent: Wednesday, February 5, 2020 2:55:19 PM
To: stsvilik/wdio-docker-service wdio-docker-service@noreply.github.com
Cc: Simon Tsvilik st777@msn.com; Mention mention@noreply.github.com
Subject: Re: [stsvilik/wdio-docker-service] Docker events fails on windows (#56)
May, it's not waiting for Docker to come up and not retrying as well though we have
healthCheck: {
url: 'http://localhost:4444',
maxRetries: 3,
inspectInterval: 2000,
startDelay: 5000
},
I killed docker application and started again on my local machine MAC, but before it starts completely, If I run the test, I am seeing above error.
Thanks,
Prathamesh
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/stsvilik/wdio-docker-service/issues/56?email_source=notifications&email_token=AABC3UELD2VAB6ENNZLZ37LRBMKSPA5CNFSM4IH62PSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK4YHMA#issuecomment-582583216, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABC3UAXLMTJGTPDJD65OGTRBMKSPANCNFSM4IH62PSA.

@stsvilik , can you please check if startDelay setting works for you? Thanks.

@prathameshnyt Yes it does. Here is how I set that
healthCheck: {
       url: 'http://localhost:4444',
       startDelay: 15000
},

@prathameshnyt One thing to note that service will try to use native docker healthcheck event to start testing earlier. What this means is if Dockerfile has HEALTHCHECK set and it signals in success, tests will not wait for artificial delay. Same also applies if Docker healthcheck is set via command line.

Ok, thanks. Not sure, why it's not waiting in my case. I have tried now with image: 'selenium/standalone-chrome-debug' I don't see HEALTHCHECK.
Thanks,
Prathamesh

I see health-check [adding-a-healthcheck-to-the-grid](https://github.com/SeleniumHQ/docker-selenium/blob/5b7626c705bda91d90af4a7f74bb57b1e4056612/README.md#adding-a-healthcheck-to-the-grid added to Base image) added to Base image Dockerfile

authors: Sureiya VisuSubbaiyan abhijit945 calltojohn nvega-ms prathameshnyt serbanghita stsvilik webOS101

repo: stsvilik/wdio-docker-service


text:
Everything section

Baigta sekcija. Turi responsive design.

@media (min-width: 768px) {    .container>.row {       width: 720px;    }
Tiesiogiai pakoreguota visi containeriuose esantys row. Not good

source: gharchive/pull-request

authors: eyyMinda simonasablinaite

repo: student-to-dev/Omex-landing-page

license: MIT

license_type: permissive

license_source: github-api


text:
Add eslint-plugin-import

Add eslint-plugin-import to help clean up imports
https://github.com/import-js/eslint-plugin-import
Config for Sen but can be adapted to be generic
"import/order": [
      "error",
      {
        "groups": ["external", "index"],
        "pathGroups": [
          {
            "pattern": "src/components/**/*",
            "group": "internal"
          },
          {
            "pattern": "src/core/**/*",
            "group": "external",
            "position": "after"
          }
        ],
        "newlines-between": "always"
      }
    ]

I've actually started to dislike this 🙃

source: gharchive/issue


text:
🛑 Beefs and Beers is down

In 91d338f, Beefs and Beers (https://beefsandbeers.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Beefs and Beers is back up in 85dd3a1 after 6 minutes.

repo: studiovlijmscherp/uptime


text:
Function results in attrs should not be overridden by component instance attributes

This issue emerged from the spectrum.chat discussion.
I believe the current attrs behaviour regarding props precedence is wrong.
Vanilla react component declarations have final say on how they interpret props coming from component instances.
I can merge a component instance attributes giving them a higher precedence:
const PliableDiv = props => {
  const style = {
    ...props.style,
    backgroundColor: "green"
  };

  return
{props.children}
;
};

<PliableDiv style={{color: "red", backgroundColor: "blue"}}>Hello</PliableDiv>

I can merge a component instance attributes giving them a lower precedence:
const OpinionatedDiv = props => {
  const style = {
    backgroundColor: "green",
    ...props.style
  };

  return
{props.children}
;
};

<OpinionatedDiv style={{color: "red", backgroundColor: "blue"}}>Hello</OpinionatedDiv>

Or I can completely ignore what a component instance is trying to impose:
const CarelessDiv = props => {
  const style = {};
  return
{props.children}
;
};
< CarelessDiv style={{color: "red", backgroundColor: "blue"}}>Hello</CarelessDiv>

Contrary to a standard component's behaviour, function results in styled component attrs' are always overridden by component instance attributes:
// I want to get rid of the inline style, but I can't!
const CarelessStyledDiv = styled.div.attrs({
  style: props => ({})
})``;

<CarelessStyledDiv style={ color: "red" } />

Initially, I stumbled upon this issue when dealing with children in attrs, but it applies to any props; I use inline style here because it's easier to see - check out the codesandbox demo.
It can be worked around by assigning a different props name, like this: const Div = styled.div.attrs({style: props => props.instanceStyle}). But I'd prefer to align the behaviour with ordinary react components.

Vanilla react component declarations have final say on how they interpret props coming from component instances.

This isn't an equivalent comparison. attrs is essentially a second layer of props that are akin to defaultProps, with the added bonus of being able to inspect other sibling props at runtime and adjust itself as desired. As such, explicitly passed props will always take priority over attrs because they are not a fallback.

authors: mvasin probablyup

repo: styled-components/styled-components

license: mit

license_source: bigquery


text:
Disappearing property of styled button

Environment
Codesandbox.
Reproduction

const StyledButton = styled.button``;

const id = 42;

function StripedButton({ stripeid }) {
  return (
    <StyledButton
      onClick={event => {
        event.persist();
        console.log(event.target);
      }}
      id={stripeid}
      stripeid={stripeid}
    >
      Select
    </StyledButton>
  );
}

Steps to reproduce

Press Styled Select button
Press Normal Button for comparison

Expected Behavior
The styled button will log <button id="42" stripeid="42" class="sc-gisBJw kDlVKO">Select</button>
Actual Behavior
The styled button logging <button id="42" stripeid="42">Select</button>

@denvash Hey there, I think you're saying stripeid isn't showing up in the sandbox right? When you use a styled DOM primitive like styled.button we try and filter out things we know aren't real DOM attributes to avoid React's warnings on the subject. For arbitrary data you're not using for styling it's recommended to use data attributes instead.

authors: denvash probablyup


text:
Bug dist/styled-components.browser.esm.js:2153 console.log (spam in console)

Environment
System:

OS: macOS 10.15.2
CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Memory: 50.38 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh

Binaries:

Node: 12.13.0 - /usr/local/bin/node
npm: 6.12.0 - /usr/local/bin/npm

npmPackages:

react: ^16.8.6 => 16.12.0
react-dom: ^16.8.6 => 16.12.0
styled-components: ^4.4.1 => 4.4.1
typescript: ^3.5.3 => 3.7.3

Reproduction
I can't reproduce it on codesandbox - I was unable to configure the assembly with styled-components as ES Module (styled-components.browser.esm.js), thats building there as CommonJS (styled-components.browser.cjs.js)
Steps to reproduce

install styled-components@4.4.1
configure your webpack4.4+ project to build with tree-shaking (es-modules)
write some code with usages of styled components
start up your code, and see in developer tools console in your browser
you must see, same as:

as many times as called 'styled' constructor

it happens in dist/styled-components.browser.esm.js file at line 2153

i could't find this source in repo to make PR with fix, i think this is artifact of build process to publish package to npm
Expected Behavior
in console printed only warring and error messages from styled-component library
Actual Behavior
in console printed excess output thats print function-object at code with styled-components usages execution

after remove node_modules and reinstall package - problem resolved, at 2153 line of  dist/styled-components.browser.esm.js no console.log instruction anymore


text:
Architecture: reactive message bus in environment

Capturing from discussion in #784.
Motivation

There are certain actions in the app that have global consequences, and all components must be reactively notified when these things happen.

Example: deleting a memo must remove that memo from all detail stacks. Lists must refresh themselves.

To do this, we need a shared resource that publishes messages when these things happen... a message bus, essentially.

Input gets sent in
Output is published as a one-to-many event publisher

We are currently using the app component's store to manage these cases.

The store has essentially the same shape as a message bus, it just has state as well.
We send request actions to the sub-component's store, and these get relayed to the app's store via some onReceive() wiring. Every component can subscribe to the app component's store to react to these actions.

However it is a bit unfortunate that we have to pass around a second store for this kind of shared global messaging.

It is un-ergonomic, and requires wiring in the view code
You can only do this wiring between two top-level @ObservableObjects

Environment is supposed to offer shared services. It might be nice if there were such a thing as reactive services that could publish notifications when certain things happen.

Services are shared via the component's environment anyway
Services are meant to represent IO or a shared resource

We could have a shared message bus on the environment.

This would be a lot like a store, but without the state.
Services would be connected to the bus. Their job would be to react to messages, perform side-effects, and publish back to the bus.
All components could share this bus, and both publish messages and subscribe to messages.
Components would be responsible for accumulating their own state based on these messages.

Tradeoffs

We only really have this problem because we have separate self-contained components, which means we need to communicate between them.

If everything were done purely as a single hierarchical state tree, like Elm App Architecture, we would end up communicating everything up to the root of the tree, and then back down.
However, for perf reasons, we must split the app into separate self-contained components that own their own state.

Code sketch
//
//  MessageBus.swift
//  SubconsciousExperiments
//
//  Created by Gordon Brander on 7/7/23.
//

import Foundation
import Combine

public final class MessageBus<Message> {
    /// Stores cancellables by ID
    private var cancellables: [UUID: AnyCancellable] = [:]
    /// Private for all actions sent to the store.
    private(set) var messages = PassthroughSubject<Message, Never>()

    public func send(_ message: Message) {
        messages.send(message)
    }

    /// Subscribe to a publisher of actions, piping them through to
    /// the messages.
    ///
    /// Holds on to the cancellable until publisher completes.
    /// When publisher completes, removes cancellable.
    public func subscribe(to publisher: AnyPublisher<Message, Never>) {
        // Create a UUID for the cancellable.
        // Store cancellable in dictionary by UUID.
        // Remove cancellable from dictionary upon effect completion.
        // This retains the effect pipeline for as long as it takes to complete
        // the effect, and then removes it, so we don't have a cancellables
        // memory leak.
        let id = UUID()

        // Receive Fx on main thread. This does two important things:
        //
        // First, SwiftUI requires that any state mutations that would change
        // views happen on the main thread. Receiving on main ensures that
        // all fx-driven state transitions happen on main, even if the
        // publisher is off-main-thread.
        //
        // Second, if we didn't schedule receive on main, it would be possible
        // for publishers to complete immediately, causing receiveCompletion
        // to attempt to remove the publisher from `cancellables` before
        // it is added. By scheduling to receive publisher on main,
        // we force publisher to complete on next tick, ensuring that it
        // is always first added, then removed from `cancellables`.
        let cancellable = publisher
            .receive(
                on: DispatchQueue.main,
                options: .init(qos: .default)
            )
            .sink(
                receiveCompletion: { [weak self] _ in
                    self?.cancellables.removeValue(forKey: id)
                },
                receiveValue: { [weak self] message in
                    self?.send(message)
                }
            )
        self.cancellables[id] = cancellable
    }

    public func connect(
        _ update: @escaping (Message) -> AnyPublisher<Message, Never>
    ) {
        subscribe(
            to: messages.flatMap(update).eraseToAnyPublisher()
        )
    }
}

enum Message {
    case foo
    case bar
}

struct FooService {
    func update(_ message: Message) -> AnyPublisher<Message, Never> {
        switch message {
        case .foo:
            return foo()
        default:
            return Empty().eraseToAnyPublisher()
        }
    }

    func foo() -> AnyPublisher<Message, Never> {
        Just(.bar).eraseToAnyPublisher()
    }
}

struct Environment {
    let bus = MessageBus<Message>()
    let foo = FooService()

    init() {
        bus.connect(foo.update)
    }
}

Some relatively off-the-cuff thoughts on this topic:

The ephemeral nature of message bus events may introduce the potential for race conditions where a statefull component is initialized too late to register as an observer of a particular event but too soon such that it is initialized with state that is about to be updated (but is effectively stale)
In some apps I have worked on, issues with keeping large stand-alone components in sync have been dealt with by ensuring that those components' inputs are all that is needed to observe critical global state changes. A simplified/contrived example is a stand-alone component who takes as its only input a monotonically increasing value that represents "the global app state changing in critical way."
For sufficiently complex components, I like to think about their relationship to the app as similar to the relationship of iframes to a parent browser frame (from a state compartmentalization perspective, that is). With this framing (heh), the parent frame has its own store, its own actions, its own state shape. Each complex component is its own state machine and is emitting generic events pertinent to its domain as state changes; the app, meanwhile, converts those into relevant actions, and passes critical global state back down to the components via their properties/inputs/etc.
In general, if UI is not a pure function of a single notion of global state, beware of the potential for race conditions leading to inconsistent representations of state.

The ephemeral nature of message bus events may introduce the potential for race conditions where a statefull component is initialized too late to register as an observer of a particular event but too soon such that it is initialized with state that is about to be updated (but is effectively stale)

Great point.

In some apps I have worked on, issues with keeping large stand-alone components in sync have been dealt with by ensuring that those components' inputs are all that is needed to observe critical global state changes. A simplified/contrived example is a stand-alone component who takes as its only input a monotonically increasing value that represents "the global app state changing in critical way."

This is sort of our base case. Major components of the app are managed by a single store. That root store cascades state changes down the view tree. Unfortunately, in SwiftUI this approach runs up against perf limits, and you end up wanting to divide the app into several such "main" components. So we have:

App

Notebook

Editor*n
UserProfile*n

Each of these bullet points manages its own self-contained store, but is also nested underneath another component. In future, each major app tab in addition to notebook will have its own self-contained store as well.

For sufficiently complex components, I like to think about their relationship to the app as similar to the relationship of iframes to a parent browser frame (from a state compartmentalization perspective, that is). With this framing (heh), the parent frame has its own store, its own actions, its own state shape. Each complex component is its own state machine and is emitting generic events pertinent to its domain as state changes; the app, meanwhile, converts those into relevant actions, and passes critical global state back down to the components via their properties/inputs/etc.

That scans. A question I'm juggling is, what's wiring these components together? It could be the App component. Or it could be the Environment (which is a shared IO/services resource between all components).
For now, I'm leaning toward just using the App component.

In general, if UI is not a "pure function of a single notion of global state" (allowances made for however you like to define this), beware of the potential for race conditions leading to inconsistent representations of state.

Truth.

I think this has further convinced me of the merits of a hierarchical tree of views. If so,

We should not be passing app down more than one level
Editor and UserProfile should be communicating up to Notebook (or whatever other enclosing tab) exclusively
Notebook (or whatever other enclosing tab) should communicate up to App

I think this will be resolved by SwiftUI's new Observation macro, which allows for nested state objects which only re-render children if the corresponding child state has changed.
Tracking Store based on this new primitive here: https://github.com/subconsciousnetwork/ObservableStore/issues/37

authors: cdata gordonbrander

repo: subconsciousnetwork/subconscious


text:
[Bug]: Password icon is missing in the login form

Describe the bug
The password icon is missing on the login page.
To Reproduce
Visit: https://biobranch.vercel.app/login
Bug Screenshot

How to resolve this bug
Simply add a password icon in the login form
Please checkmark the following checklist

[x] I make sure that a similar issue is not opened

Hey @Abhi0049k  Can you assign this to me?

I would like to fix this issue. please assign it to me

i would like to fix this issue, can you please assign this to me u der gssoc ext level.

Guys, I am not the maintainer; only a maintainer can assign an issue to someone.

Hey @subhadipbhowmik , i have fixed the issue and have raised the PR. plz check and merge accordingly

@subhadipbhowmik thank you for assigning it to me

@subhadipbhowmik , i had raised a PR 2 days back, plz check it

Hi @subhadipbhowmik,
I’ve added the password visibility toggle feature for both the Login and Register pages using an eye icon, allowing users to show or hide their password input. Let me know if any changes are needed.

Hi @subhadipbhowmik
Things I have worked on:

Added missing icons for both login and register page
Added toggle feature for both login and register page

Best regards
Mangalam

repo: subhadipbhowmik/bio-branch


text:
🛑 Cubari (imgBB) is down

In 5a585c8, Cubari (imgBB) (https://cubari.moe/read/imgbb/SQMcSX/?cache_buster=$GITHUB_RUN_NUMBER) was down:

HTTP code: 500
Response time: 93 ms

Resolved: Cubari (imgBB) is back up in 319d4ad after 5 minutes.

repo: subject-f/cubari-status-page


text:
🛑 Cubari (imgbox) is down

In 9541a62, Cubari (imgbox) (https://cubari.moe/read/imgbox/cUGEkRbdZZ/?cache_buster=$GITHUB_RUN_NUMBER) was down:

HTTP code: 500
Response time: 8451 ms

Resolved: Cubari (imgbox) is back up in a324c4e after 5 minutes.


text:
Change namespace to SubjectivePHP

Fixes #20

Coverage remained the same at 100.0% when pulling 7c2611db6071a56238474f0820d6e94cb699fe09 on chadicus:dev/issue-20 into 8f81f76455172de63715ae937db5a4b2d32618af on subjective-php:master.

authors: chadicus coveralls

repo: subjective-php/util-exceptions


text:
Update impersonation_employee_payroll_fraud.yml

Adding ACH

/update-test-rules

repo: sublime-security/sublime-rules


text:
Add MAG developers to CodeOwners

Signed-off-by: Andrew Stoycos astoycos@redhat.com

This is taken care of by https://github.com/submariner-io/submariner/pull/1743

Ack thanks!

authors: astoycos skitt

repo: submariner-io/submariner


text:
Fix exposed requires being persisted across bundles

As mentioned in the comments on issue #908 https://github.com/substack/node-browserify/issues/908#issuecomment-55956552, exposed files were being persisted across calls to browserify. I tracked this down to a leak where modules were being appended to the (module) global builtins object. Fixed with a test, though I'm not sure if you want a test for such a fine grained bug, so feel free to remove it, but it does demonstrate the failure & subsequent pass with this fix.

LGTM :+1:
@substack ?

I think the root cause of this might be a bug in module-deps, which I've been trying to get to the bottom of. I asked about it in substack/module-deps/pull/65, but it was merged without comment (so far). Long story short, with the way I'm proposing resolving pathnames of exposed modules, it gets them treated as built-in (e.g. transforms aren't run). More info in substack/node-browserify/pull/1077. So I think something needs to change in module-deps re: that anyway, and it might solve the problem you're talking about as well.

I'll have a patch fix for this soon once I finish the v9 branch.

Published in 9.0.1. Thanks for the patch!

authors: jmm latentflip substack terinjokes

repo: substack/node-browserify


text:
Streamline configurator API's.

Move ProseEditor-specific API into separate ProseEditorConfigurator. Do not import firstPackage on construction. This is too early as inherited configurators may to things on construction before the first package is imported.

Please review. I removed firstPackage argument from the constructor, so this change will break the examples. If you are good with this I will update the examples and then merge.

Coverage remained the same at 76.254% when pulling 5a34621265d33bd1681f8eb01c09ff214698e661 on multiple-configurators into 41b87c7c485ed3db42777a958fd3eebb856854ff on develop.

👍

Could you please explain new concept?
On Fri, Jul 8, 2016 at 4:20 PM Oliver Buchtala notifications@github.com
wrote:

👍
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/substance/substance/pull/743#issuecomment-231357300,
or mute the thread
https://github.com/notifications/unsubscribe/AALG-qgPB2tMKYDVG9hTQSazayqdW_yJks5qTk6agaJpZM4JIA4a
.

@Integral There is no new concept. It's just a realization that we should use multiple configurators to configure Reader/Writer separately. I need to get the examples updated and the PR's merged. I will be in the chat once done, so we can discuss the Notes app short.

authors: Integral coveralls michael oliver----

repo: substance/substance


text:
CSS: spacing between abstract and body

Maybe a little bit more spacing here...

Particularly it appears to be different to other spacings

Not finished yet! Just a 🐄 boy mode
On Fri, 14 Sep 2018, 23:33 Oliver Buchtala, notifications@github.com
wrote:

Maybe a little bit more spacing here...
[image: image]
https://user-images.githubusercontent.com/284099/45576207-86adf800-b876-11e8-82d8-59476e1c5bea.png
Particularly it appears to be different to other spacings
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/substance/texture/issues/848, or mute the thread
https://github.com/notifications/unsubscribe-auth/AALG-thQLQrqJHLHERHAg8Vqnunghy7kks5ubCCWgaJpZM4Wp-yY
.

Ok :)

This is fixed now.

authors: Integral oliver----

repo: substance/texture


text:
Code snip in substrate kitties tutorial doesn't compile

Content request
construct_runtime!(
    // --snip
    {
        // --snip
        SubstrateKitties: pallet_kitties,
    }
);

On the substrate kitties tutorial doesn't compile with a bunch of errors. Please make the relevant changes for us beginners, Thanks! So far using
SubstrateKitties: pallet_kitties::{Pallet, Storage, Call, Event<T>},

works but the dispatchable calls don't show up on the extrinsics page.
Are you willing to help with this request?
Yes!

Correct me if I'm wrong but it seems like you're using a node template that's tagged to a monthly that's monthly-2021-10 or less. Please let me know :)

Hey sorry for the late reply. Indeed it is monthly-2021-10.

repo: substrate-developer-hub/substrate-docs


text:
Port KS8995MA switch into ZYNQ

We need to connect KS8995MA switch with ZYNQ through EMIO with GMIO into MII interfaces and needed to find compatible driver for it.

https://forums.xilinx.com/t5/Zynq-All-Programmable-SoC/RGMII-to-GMII-or-GMII-to-MII-IP-core/td-p/644257
https://www.xilinx.com/support/answers/47792.html

Micrel KS8995 SPI controlled Ethernet Switch families
http://lxr.free-electrons.com/source/Documentation/devicetree/bindings/net/micrel-ks8995.txt

Faced with clock pins assignments

Faced with gmii clock pins assignments

On constrains was added:
set_property CLOCK_DEDICATED_ROUTE FALSE [get_nets GMII_ETHERNET_1_rx_clk_IBUF]
set_property CLOCK_DEDICATED_ROUTE FALSE [get_nets GMII_ETHERNET_1_tx_clk_IBUF]

xdc file
set_property PACKAGE_PIN T12 [get_ports mdio_ethernet_1_mdio_io]
set_property PACKAGE_PIN U12 [get_ports MDIO_ETHERNET_1_mdc]
set_property PACKAGE_PIN U13 [get_ports {GMII_ETHERNET_1_tx_en[0]}]
set_property PACKAGE_PIN V13 [get_ports {GMII_ETHERNET_1_tx_er[0]}]
set_property PACKAGE_PIN V12 [get_ports GMII_ETHERNET_1_col]
set_property PACKAGE_PIN W13 [get_ports GMII_ETHERNET_1_crs]
set_property PACKAGE_PIN Y14 [get_ports GMII_ETHERNET_1_tx_clk]
set_property PACKAGE_PIN W14 [get_ports {GMII_ETHERNET_1_txd[3]}]
set_property PACKAGE_PIN T15 [get_ports {GMII_ETHERNET_1_txd[2]}]
set_property PACKAGE_PIN W10 [get_ports {GMII_ETHERNET_1_txd[1]}]
set_property PACKAGE_PIN U10 [get_ports {GMII_ETHERNET_1_txd[0]}]
set_property PACKAGE_PIN T9 [get_ports GMII_ETHERNET_1_rx_er]
set_property PACKAGE_PIN V10 [get_ports GMII_ETHERNET_1_rx_clk]
set_property PACKAGE_PIN V11 [get_ports GMII_ETHERNET_1_rx_dv]
set_property PACKAGE_PIN Y11 [get_ports {GMII_ETHERNET_1_rxd[3]}]
set_property PACKAGE_PIN W11 [get_ports {GMII_ETHERNET_1_rxd[2]}]
set_property PACKAGE_PIN Y13 [get_ports {GMII_ETHERNET_1_rxd[1]}]
set_property PACKAGE_PIN Y12 [get_ports {GMII_ETHERNET_1_rxd[0]}]
set_property CLOCK_DEDICATED_ROUTE FALSE [get_nets GMII_ETHERNET_1_rx_clk_IBUF]
set_property CLOCK_DEDICATED_ROUTE FALSE [get_nets GMII_ETHERNET_1_tx_clk_IBUF]
set_property PACKAGE_PIN T10 [get_ports spi_1_io0_io]
set_property PACKAGE_PIN U15 [get_ports spi_1_io1_io]
set_property PACKAGE_PIN U14 [get_ports spi_1_sck_io]
set_property PACKAGE_PIN T11 [get_ports spi_1_ss_io]

http://wiki.dave.eu/index.php/AN-BELK-006:_Enabling_dual_Gigabit_Ethernet_support_on_BoraEVB/BoraXEVB

Faced with error:
[    0.813171] libphy: MACB_mii_bus: probed
[    0.815715] mdio_bus e000c000.etherne: /amba/ethernet@e000c000/mdio has invalid PHY address
[    0.822774] mdio_bus e000c000.etherne: scan phy mdio at address 0
[    0.827880] mdio_bus e000c000.etherne: scan phy mdio at address 1
SPI driver instantiated and devicetree changed
spi@e0007000 {
compatible = "xlnx,zynq-spi-r1p6";
reg = <0xe0007000 0x1000>;
status = "okay";
interrupt-parent = <0x3>;
interrupts = <0x0 0x31 0x4>;
clocks = <0x1 0x1a 0x1 0x23>;
clock-names = "ref_clk", "pclk";
#address-cells = <0x1>;
#size-cells = <0x0>;
                    ethernet-switch@0 {
                            compatible = "micrel,ks8995";
                            spi-max-frequency = <1000000>;
                            reg = <0>;
                    };
            ethernet@e000c000 {
                    compatible = "cdns,zynq-gem", "cdns,gem";
                    reg = <0xe000c000 0x1000>;
                    status = "okay";
                    interrupts = <0x0 0x2d 0x4>;
                    clocks = <0x1 0x1f 0x1 0x1f 0x1 0xe>;
                    clock-names = "pclk", "hclk", "tx_clk";
                    #address-cells = <0x1>;
                    #size-cells = <0x0>;
                    #local-mac-address = [00 0a 35 00 00 00];
                    phy-handle = <0x6>;
                    phy-mode = "mii-id";
                    ethernet-phy@1 {
                            compatible = "micrel,ks8995";
                            device_type = "ethernet-phy";
                            reg = <0x3>;
                            linux,phandle = <0x6>;
                            phandle = <0x6>;
                    };
            };

Boot output
[    0.726337] cdns-spi e0007000.spi: registered master spi32766 (dynamic)
[    0.726503] spi spi32766.0: setup mode 0, 8 bits/w, 1000000 Hz max --> 0
[    0.726798] cdns-spi e0007000.spi: registered child spi32766.0
[    0.728826] spi-ks8995 spi32766.0: setup mode 0, 8 bits/w, 1000000 Hz max --> 0
[    0.728862] spi-ks8995 spi32766.0: cdns_spi_setup_transfer, mode 0, 8 bits/w, 651041 clock speed
[    0.728936] spi-ks8995 spi32766.0: cdns_spi_setup_transfer, mode 0, 8 bits/w, 651041 clock speed
[    0.728991] spi-ks8995 spi32766.0: chip family id mismatch: expected 0x95 but 0x00 read

Boot output
root@linaro-developer:~# dmesg | grep spi
[    0.694118] cdns-spi e0007000.spi: registered master spi32766 (dynamic)
[    0.694265] spi spi32766.0: setup mode 0, 8 bits/w, 10000000 Hz max --> 0
[    0.694560] cdns-spi e0007000.spi: registered child spi32766.0
[    0.696459] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/amba/spi@e0007000/ethernet-switch)
[    0.696496] spi-ks8995 spi32766.0: setup mode 0, 8 bits/w, 10000000 Hz max --> 0
[    0.696532] spi-ks8995 spi32766.0: cdns_spi_setup_transfer, mode 0, 8 bits/w, 5208333 clock speed
[    0.696569] spi-ks8995 spi32766.0: cdns_spi_setup_transfer, mode 0, 8 bits/w, 5208333 clock speed
[    0.696625] spi-ks8995 spi32766.0: cdns_spi_setup_transfer, mode 0, 8 bits/w, 5208333 clock speed
[    0.696661] spi-ks8995 spi32766.0: cdns_spi_setup_transfer, mode 0, 8 bits/w, 5208333 clock speed
[    0.696698] spi-ks8995 spi32766.0: cdns_spi_setup_transfer, mode 0, 8 bits/w, 5208333 clock speed
[    0.696717] spi-ks8995 spi32766.0: cdns_spi_setup_transfer, mode 0, 8 bits/w, 5208333 clock speed
[    0.696772] spi-ks8995 spi32766.0: cdns_spi_setup_transfer, mode 0, 8 bits/w, 5208333 clock speed
[    0.696809] spi-ks8995 spi32766.0: cdns_spi_setup_transfer, mode 0, 8 bits/w, 5208333 clock speed
[    0.696846] spi-ks8995 spi32766.0: KS8995MA device found, Chip ID:0, Revision:4
devicetree
spi@e0007000 {
compatible = "xlnx,zynq-spi-r1p6";
reg = <0xe0007000 0x1000>;
status = "okay";
interrupt-parent = <0x3>;
interrupts = <0x0 0x31 0x4>;
clocks = <0x1 0x1a 0x1 0x23>;
clock-names = "ref_clk", "pclk";
#address-cells = <0x1>;
#size-cells = <0x0>;
                    ethernet-switch@0 {
                            compatible = "micrel,ks8995";
                            spi-max-frequency = <0x989680>;
                            reg = <0x0>;
                            reset-gpios = <&gpio 0x1 0x1>;
                    };
            };

Config
+CONFIG_SPI_DEBUG=y
+CONFIG_SPI_MASTER=y
+CONFIG_MICREL_KS8995MA=y
+CONFIG_MICREL_PHY=y
+CONFIG_NET_VENDOR_MICREL=y

Switch registers are accessed via dd
dd if=/sys/bus/spi/devices/spi32766.0/registers count=1 bs=1 skip=0 | od -x
dd if=/sys/bus/spi/devices/spi32766.0/registers count=1 bs=1 skip=1 | od -x
dd if=/sys/bus/spi/devices/spi32766.0/registers count=1 bs=1 skip=31 | od -x

1 Port Link is up
root@linaro-developer:~# sudo lshw -class network
*-network:0
description: Ethernet interface
physical id: 1
logical name: eth0
serial: 04:4f:8b:00:00:00
size: 100Mbit/s
capacity: 1Gbit/s
capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=macb duplex=full ip=192.168.0.100 link=yes multicast=yes port=MII speed=100Mbit/s
*-network:1
description: Ethernet interface
physical id: 2
logical name: eth1
serial: e2:a7:df:21:79:1b
size: 100Mbit/s
capacity: 100Mbit/s
capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=macb duplex=full link=yes multicast=yes port=MII speed=100Mbit/s

In new LR 2.0 the Ethernet switch will be replaced

repo: subutai-io/liquid-router


text:
Implement linkedin login authentication

Current State
linkedin login buttons isn't functional
Desired State
Implement Backend with for the Login with linkedin button
" Derived from #140 "
Do not generate your own API keys (Ask for the keys, when you start working on the issue)

I would like to work on this issue.

working on this ?
Yes


text:
Settings panel design #43

What is the change?

Changed font style, and size for settings panel.

Which issue does this resolve?
Fixes: #43
Submissions guide:

[x] Have you followed the Contribution guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[ ] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.

@sudo-rgorai, pull request #62 can be a temporary solution for issue #43 since there are some bugs in the design, if you want I can redo the dropdown menu with an improved design. But it might require more than a week.

@sudo-rgorai, pull request #62 can be a temporary solution for issue #43 since there are some bugs in the design, if you want I can redo the dropdown menu with an improved design. But it might require more than a week.

Sure! The dropdown looks relatively better. However the behaviour seems quite buggy. For example the position of hover effect seems a bit off (not sure if this problem already existed in master), Font styles menu has been dislocated, etc.
You're free to take more time. Keep pushing commits to your branch and comment here when you think you're done. If you want the current changes to be merged, make sure you've fixed the bugs.
Thanks :relaxed:

Sure! The dropdown looks relatively better. However the behaviour seems quite buggy. For example the position of hover effect seems a bit off (not sure if this problem already existed in master), Font styles menu has been dislocated, etc.
You're free to take more time. Keep pushing commits to your branch and comment here when you think you're done. If you want the current changes to be merged, make sure you've fixed the bugs.
Thanks :relaxed:

@sudo-rgorai, the current design might have bugs, but it's comparatively better than the previous panel, so you can merge this one, and I'll start working on the new design.

@sudo-rgorai, the current design might have bugs, but it's comparatively better than the previous panel, so you can merge this one, and I'll start working on the new design.

repo: sudo-rgorai/DarkSite


text:
[request error] [unhandled] [500] Status code: 500 when tried to chat with a created KB.

Hit a new issue now:
Chat with knowledge base with id:  19
Knowledge base kb10 with embedding "nomic-embed-text:latest"
Creating embeddings for Ollama served model: nomic-embed-text:latest
Creating Chroma vector store
Initializing ParentDocumentRetriever with RedisDocstore
Redis client options:  { host: 'redis', port: 6379, username: undefined, password: undefined }
Chat with Ollama, Host: http://host.docker.internal:11434
User query:  connected vpc
Reformulated query:  connected vpc
Relevant documents:  [
Document {
pageContent: 'THE VPC CROSS-LINK AND CONNECTED VPC\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'Every production SDDC must be cross-linked to a VPC within the customer-owned AWS account, referred to as the connected VPC. This\n' +
'cross-linking is accomplished using the Cross-Account Elastic network interface\n' +
'[https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html] (ENI) feature of AWS and creates a connection between every\n' +
'host within the management cluster of the SDDC to a subnet within the cross-linked VPC. This cross-link provides the SDDC with a\n' +
'high-bandwidth and low-latency network forwarding path to services maintained within the customer-owned AWS account.\n' +
'\n' +
'[data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==]',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'These VMkernel adapters are visible from the networking section of the conﬁguration tab of the ESXi host. You can also get a sense\n' +
'of the setup by viewing the TCP/IP conﬁguration for the host.\n' +
'\n' +
'The last portion of the underlay network are the virtual switches. Again, these are visible from the networking section of the\n' +
'conﬁguration tab of the ESXi host. Here, you will see a mix of switches; some that are part of the underlay network and others\n' +
'which represent NSX network segments. The switches which are part of the underlay network are there to provide connectivity to the\n' +
'various management appliances of the SDDC. Of particular note is the management switch, which exists in order to provide the\n' +
'appliances with access to the management network. You can get a sense of some of the other important virtual switches in a host by\n' +
'examining their names as well as the management appliances which are attached to them.\n' +
'\n' +
'\n' +
'THE VPC CROSS-LINK AND CONNECTED VPC',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'The vCenter, NSX Managers and NSX edge appliances are typically deployed in the same AZ. In the event of an AZ failure, if\n' +
'vCenter, NSX Managers, and NSX edge appliances are in the impacted AZ, vSphere HA will restart these appliances and customers’\n' +
'workloads in the surviving AZ. These management appliances and NSX edge appliances will continue to operate there, even after the\n' +
'affected AZ is restored, until a failure or other scenario necessitates their recovery in another AZ. \n' +
'\n' +
'\n' +
'STRETCHED CLUSTER CONNECTED VPC\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'Stretched clusters require an Amazon VPC with two subnets, one subnet per availability zone. The subnets determine ESXi hosts\n' +
'placement between the two AZs. In the event that the active edge appliance migrates between hosts or AZs, the route tables of the\n' +
'connected VPC will be updated to route traﬃc through the appropriate cross-link ENI.\n' +
'\n' +
'[data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==]\n' +
'\n' +
'\n' +
'CROSS-AZ DATA FLOWS',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'The MTU size for Internet Uplink is 1500 bytes, which is not configurable.\n' +
'\n' +
'\n' +
'SERVICES UPLINK\n' +
'\n' +
'The services uplink connects the SDDC edge appliances to the connected VPC in the customer-owned AWS account. A static route on\n' +
'the SDDC edge appliances is configured for the primary CIDR of the VPC which points to the VPC router as a next hop during the\n' +
'SDDC provisioning. It enables compute workloads to leverage this uplink to consume AWS services and resources in the connected\n' +
'VPC. For services not running in the connected VPC, it is still possible to using the uplink to get connected through VPC\n' +
'endpoints [https://docs.aws.amazon.com/whitepapers/latest/aws-privatelink/what-are-vpc-endpoints.html].',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'VMware Cloud on AWS supports three types of compute network segments: routed, extended and disconnected.\n' +
'\n' +
'The difference of three network types is primarily in their connectivity capability:\n' +
'\n' +
' * Routed – routed (default type) network segments have connectivity to other segments within an SDDC and to external networks.\n' +
' * Extended – extended network segments are used with the NSX L2VPN to create a common broadcast domain between a VMware Cloud on\n' +
'   AWS SDDC and on-premises networks.\n' +
' * Disconnected – disconnected network segments have no uplinks and create an isolated segment. Disconnected networks are\n' +
'   primarily created by HCX, that can be changed to routed networks.\n' +
'\n' +
'For more information, please refer to Understanding Segments in VMC on AWS\n' +
'[https://vmc.techzone.vmware.com/understanding-segments-vmc-aws].\n' +
'\n' +
'\n' +
'CONNECTED VPC CONNECTIVITY',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'For more information, please refer to Understanding Segments in VMC on AWS\n' +
'[https://vmc.techzone.vmware.com/understanding-segments-vmc-aws].\n' +
'\n' +
'\n' +
'CONNECTED VPC CONNECTIVITY\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'Since we must always pass through the Edge SR whenever traﬃc leaves the SDDC, all traﬃc to and from the connected VPC must pass\n' +
'through the active edge appliance of the SDDC. Since this edge appliance is a VM, it resides on a speciﬁc ESXi host. As such, it\n' +
'will always use the Cross-Account ENI for that host. It should be noted that the hosts of the SDDC will be deployed within the\n' +
'same AZ as the cross-link subnet (the subnet which contains the Cross- Account ENIs). This mechanism controls the AZ placement of\n' +
'the SDDC (customer chooses the subnet and thus controls the AZ placement), but also serves to eliminate cross-AZ bandwidth charges\n' +
'between the edge and any native AWS resources within that same AZ.',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'ROUTE PRIORITY\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'When the NSX learns the same route from different sources, the NSX T0 router will choose the route based on its source in the\n' +
'following order:\n' +
'\n' +
' * Connected VPC\n' +
' * Route-based VPN (“Use VPN as backup to Direct Connect” is OFF)\n' +
' * Policy-based VPN *\n' +
' * VMware Transit Connect\n' +
' * Direct Connect Private VIF\n' +
' * Route-based VPN (“Use VPN as Backup to Direct Connect” is ON) \n' +
' * AWS Internet Gateway \n' +
'\n' +
'IPsec VPN will never be used for traffic from ESXi hosts if SDDC is a member of an SDDC Group or has a DX Private VIF attached.\n' +
'\n' +
' Use VPN as Backup to Direct Connect option is not applied to routes learned through VMware Transit Connect.\n' +
'\n' +
' Default Route only.\n' +
'\n' +
'\n' +
'NETWORK SERVICES\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'VPC PEERING FOR EXTERNAL STORAGE CONNECTION',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: ' Customers VPC connections are achieved through resource sharing from the VMware AWS account to the customer-owned AWS account.\n' +
'   Once the VTGW resource sharing request is accepted in the customers AWS      Resource Access Manager, customer VPCs can be\n' +
'   attached to VTGW through a VPC attachment from the AWS console. The attachment request must be accepted in VMware Cloud on AWS\n' +
'   before the attachment is completed.\n' +
' * In terms of interconnectivity for customers AWS Transit Connect Gateways, these TGWs would be interconnected to VTGW through\n' +
'   TGW peering. In a multi-region SDDC group, the choice of region for AWS TGW connection to is configurable.\n' +
" * Similarly, VTGW can be associated with customers DXGW through a TGW association. In the association configuration, 'allow\n" +
"   prefixes' will be defined to specify which routes will be advertised to on-premises networks over the DXGW, with an AWS limit\n" +
'   of up to 20 prefixes.',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: 'A screenshot of a computer Description automatically generated\n' +
'[data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==]\n' +
'\n' +
'For more information about the AWS Managed Prefix List Mode, please refer to Understanding Managed Prefix List Mode for Connected\n' +
'VPC in VMC on AWS [https://vmc.techzone.vmware.com/understanding-managed-prefix-list-mode-connected-vpc-vmc-aws].\n' +
'\n' +
'\n' +
'EDGE UPLINKS\n' +
'\n' +
'There are currently three uplinks from the tier-0 routers of the SDDC. These are described below.\n' +
'\n' +
'\n' +
'INTERNET UPLINK\n' +
'\n' +
'The internet uplink is connected to AWS IGW within the underlay VPC. Since the default from other sources such as Direct Connect,\n' +
'IPSec VPN or VMware Transit Connect (VTC) has a higher priority, the IGW path would be only used when no other default routes are\n' +
'learned.',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
},
Document {
pageContent: '[data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==]\n' +
'\n' +
'An internet gateway [https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Internet_Gateway.html] (IGW) and virtual private gateway\n' +
'[https://aws.amazon.com/directconnect/faqs/] (VGW) will also be created for this VPC. These gateways enable internet and Direct\n' +
"Connect connectivity to the VPC.  It's important to note that customers cannot directly see or manage these AWS components. Any\n" +
'interaction with or configuration of these components must be done through VMware-provided options such as the NSX UI, API, and\n' +
'Cloud Console.\n' +
'\n' +
'\n' +
'THE SDDC UNDERLAY\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'\n' +
'ESXI NETWORKING',
metadata: {
source: 'https://vmc.techzone.vmware.com/resource/vmware-cloud-aws-network-architecture',
title: 'VMware Cloud on AWS: Network Architecture | VMware',
description: 'Overview The networking architecture of a VMware Cloud on AWS Software-Defined Data Center (SDDC) is arguably one of the most',
language: 'en',
loc: [Object]
}
}
]
Cohere Rerank Options:  {
apiKey: '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',
baseUrl: 'http://peanutshell:8000/v1',
model: 'ms-marco-MiniLM-L-6-v2',
topN: 4
}
[nuxt] [request error] [unhandled] [500] Status code: 500
Body: "Internal Server Error"
at CohereClient. (./.output/server/node_modules/cohere-ai/Client.js:481:27)
at Generator.next ()
at fulfilled (./.output/server/node_modules/cohere-ai/Client.js:31:58)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5
Please help.

Looks it's some issue in the peanut-shell API.
Could you please try a couple of things at your end, following https://github.com/sugarforever/peanut-shell?

If the models endpoint works - curl --location 'http://localhost:8000/v1/models'
If the rerank endpoint works:

curl --location 'http://localhost:8000/v1/rerank/' \
--header 'Content-Type: application/json' \
--data '{
    "model": "ms-marco-MiniLM-L-6-v2",
    "query": "What is the capital of the United States?",
    "top_n": 3,
    "documents": [
        "Carson City is the capital city of the American state of Nevada.",
        "The Commonwealth of the Northern Mariana Islands is a group of islands in the Pacific Ocean. Its capital is Saipan.",
        "Washington, D.C. (also known as simply Washington or D.C., and officially as the District of Columbia) is the capital of the United States. It is a federal district.",
        "Capital punishment (the death penalty) has existed in the United States since beforethe United States was a country. As of 2017, capital punishment is legal in 30 of the 50 states."
    ]
}'

Please change the host localhost to your docker set up.
Let me know if you see any issue.

repo: sugarforever/chat-ollama


text:
[Request] add clothing (white shirt) and hairstyle (long hair, bob cut)

Thank you for the useful node.
[Request] Is it possible to add clothes (white shirt) and hairstyle (long hair, bob cut) to the tag filter?
Thank you in advance.

Thank you for your request! Understood, I will add the clothes (white shirt) and hairstyle (long hair, bob cut) to the tag filter.
Thank you in advance for your patience.

Upon checking, it seems that these tags are already added. The difference is in cases like "long hair" where there is a space. In the JSON data, we use underscores instead of spaces (e.g., long_hair).
Currently, there is code that does not differentiate between spaces and underscores, but some code does, leading to inconsistency.
I plan to fix this soon so that it works with both spaces and underscores.
In the meantime, could you try using underscores instead of spaces and see if that works for you?

Thank you for your response.
I tried it with underscores and it worked!
Thanks!

authors: Zakutu sugarkwork


text:
Add Clear button

Clear button will clear the canvas.
Is it a good feature to add?

Sure.

@walterbender please check #15.

PR #19 And PR #26 closes this issue

authors: DipanshKhandelwal ravjot07 walterbender

repo: sugarlabs/connect-the-dots-activity


text:
[DRAFT] [SPIKE] Use hotwire for work form validation

Note that installation requires the asset pipeline, which requires the sprockets railtie. Why not just install via yarn and rely on webpacker? We could, but then we would not get any of the hotwire helpers that come from installing via the hotwire-rails gem, e.g., broadcasts_to, turbo_frame_tag, turbo_stream_action_tag.
Note as well that we should ultimately be able to replace remote forms entirely with the hotwire approach, hence the new TODO and commented-out configuration option in config/application.rb.
Connects to #786
Why was this change made?
To experiment with using hotwire to improve H2 form validation, in terms of user experience and developer understanding.
How was this change tested?
CI
Which documentation and/or configurations were updated?
None

Closing. See rationale: https://github.com/sul-dlss/happy-heron/issues/786#issuecomment-759052241

Closing. See rationale: https://github.com/sul-dlss/happy-heron/issues/786#issuecomment-759052241

repo: sul-dlss/happy-heron


text:
Fixed account-contact position

tasks:

[ ] gather feedback for my changes

informations:

q
a

Fixed tickets
none

BC breaks
none

Documentation PR
none

Currently it is also not working for existing person. Please translation contact/person.

@chirimoya fixed

ack

authors: chirimoya wachterjohannes

repo: sulu-io/sulu


text:
有办法关闭这个提示吗

每次打开都会出现这个request action 选择哪个选项都不行,
重启nvim，或者重新打开一个lua文件都会出现这个，有办法关闭这个提示吗

好的感谢，我试试

另外也有可能是一个bug导致的，你可以试试更新到这个提交看看还有没有问题：
b2857d1ba8b5a64ffa4879d9aa95fb7a26ef2101

这么设置了貌似不行，还是我设置方法不对吗，我试试更新下你的最新提交版本看看~~

另外也有可能是一个bug导致的，你可以试试更新到这个提交看看还有没有问题： b2857d1

应该是这个bug造成的，然后还发现一个事情，就是必须在我的项目工程根目录创建这个.luarc.json文件，哪怕这个文件是空的也没有问题，如果不创建就会报禁止创建的提示，不理解为什么不做成我用nvim第一次在我项目的根目录打开，就直接把这个目录当成语言服务器将来要scanf的目录,
【ps】

在这里设置不起作用

工作目录的路径是你的客户端发给服务器的，如果有问题请联系你的客户端。参考：https://github.com/sumneko/lua-language-server/wiki/Why-scanning-home-folder

repo: sumneko/lua-language-server


text:
Literal alias will throw false alarm

How are you using the lua-language-server?
Visual Studio Code Extension (sumneko.lua)
Which OS are you using?
MacOS
What is the issue affecting?
Annotations, Type Checking
Expected Behaviour
Follow the wiki tutorial:
local A = "Hello"
local B = "World"

---@alias myLiteralAliases `A` | `B`

---@param x myLiteralAliases
function foo(x) end

it should not show any warning when using it:
foo(A)

Actual Behaviour
It show warning:
Cannot assign `string` to parameter ``A`|`B``.
- `string` cannot match ``A`|`B``Lua Diagnostics.(param-type-mismatch)

Reproduction steps
Enter the code in VSCode
local A = "Hello"
local B = "World"

---@alias myLiteralAliases `A` | `B`

---@param x myLiteralAliases
function foo(x) end

foo(A)

then you will see it
Additional Notes
Some info:
$ code --version
1.73.0
8fa188b2b301d36553cbc9ce1b0a146ccb93351f
x64
$ ls ~/.vscode/extensions/ | grep sumneko
sumneko.lua-3.6.2-darwin-x64

Log File
No response

holy efficency


text:
请问下有QQ或者微信群么，以方便及时问答

针对Orange使用的提问，对于简单几句话描述不清的问题，请使用以下格式，不符合格式或描述含糊不清的issue将不予回复。根据问题模板填写好后，提问之前请去除模板的无用内容。
使用的Orange版本
如v0.7.0
需求或场景
描述你想实现的功能
使用的插件
针对这个需求你使用了哪个或哪几个插件
具体的配置
在插件里做了什么配置，可以截图，一定要描述清楚你的配置
期望的结果
按你选用的插件和所做的配置，你期望的结果是什么？比如访问了哪个URL，参数都是什么，期望的输出是什么
错误的结果
描述实际的结果，比如错误的输出或截图

有的  加我微信 1017109588 拉你进群

authors: jakytianjingqing wujunze

repo: sumory/orange


text:
Also include regular commits (not via PRs) in the changelog to avoid gaps

Found out how to get the commits, but not yet how to avoid that they completely steal the show :)
Need to find a way to abbreviate them in the output. In its current form this change makes the assetgraph changelog go from 147252 bytes to 1199038 bytes, making github refuse to render is as markdown :laughing:

How about this? I changed it so it lists up to 5 regular commits per release, and if there are more, it puts a "+n more" entry linking to the full compare url.

Makes the assetgraph changelog look like this: https://github.com/assetgraph/assetgraph/blob/master/CHANGELOG.md

That sounds really good, let me have a look.

I like the result, I'll review code later today.

We should make sure that this runs on node 6.9.1, otherwise we need to bump the engine.

It does work with node 6.9.1 :hugs:

One thing that rubs me the wrong way, is that the commits is not ordered by time together with the PR's, I see a changelog as a timeline. But I can see that it might be a bit odd to end with a PR and then have +2 more that is actually after that PR. I don't really know what the best solution is. It would be interesting to just try to add a h4 heading pull request section and commit section where we have a mix.
Example: (don't know if I like it 😄)
v5.8.0 (2019-03-03)

#987 autoprefixer: Add errorIfNotFound option (Andreas Lind)
#985 Switch to the split out font-tracer module (Andreas Lind)
#983 Make the loading the default stylesheets rollup-friendly, avoid fs.readFile (Andreas Lind)
#984 getTextByFontProperties: Don't require the AssetGraph instance (Andreas Lind)

v5.7.0 (2019-02-23)

Pass the mount root as part of the canonicalRoot instead (Andreas Lind)
Complain if both canonicalRoot and mountRoot are given, and canonicalRoot has a different path (Andreas Lind)
mountRoot POC (Andreas Lind)
Quick and dirty implementation of a mount root (Andreas Lind)

v5.6.4 (2019-02-21)
Pull requests

#981 Upgrade mocha to version 6.0.0 (depfu[bot])
#976 Allow custom sw-precache configuration (Márton Salomváry)
#977 Upgrade cssnano to version 4.1.10 (depfu[bot])

Commits to master

Fix Asset#replaceWith when the replacement asset is inline and contains a root-relative url (Andreas Lind)
Switch back to the official escodegen now that estools/escodegen#389 was merged and released in 1.11.1 (Andreas Lind)
addPrecache...: Throw if staticFileGlobs is passed (Andreas Lind)
Switch to sw-precache's promise interface, fixes error reporting (Andreas Lind)
Interpret config paths as relative to process.cwd() (Andreas Lind)
+2 more

Hmm, I see the point, it would be really nice to actually have it chronological.
I like your suggestion, although I think it gets a bit verbose. But maybe that's actually fine.

I like your suggestion, although I think it gets a bit verbose. But maybe that's actually fine.

Let's try that, the great thing is that it is just a projection, so we can always improve it.

Let's try that

Implemented in ac983e7
Updated https://github.com/assetgraph/assetgraph/blob/master/CHANGELOG.md

Released as offline-github-changelog@1.5.0

authors: papandreou sunesimonsen

repo: sunesimonsen/offline-github-changelog


text:
"Compare words" dropdown

Clicking the 'Compare X' button on term detail pages should drop the 2-word comparison form down from the main search bar.

fixed in d9fb178

repo: sunlightlabs/Capitol-Words


text:
[BUG] Error: Failed to parse Bard response

Error: Failed to parse Bard response

i think is something of BARD, because https://bard.google.com/?hl=en, not working to

repo: sunner/ChatALL


text:
cli arguments --history_prompt type error

i don't understand why this cli command won't work, typing.Union[typing.Dict, str, NoneType] to my understanding, is should accept a string or a Dict?
Mac OSX M1
$ python -m bark --text "大家好，这里是测试" --history_prompt "/projects/test/bark/bark/assets/prompts/zh_speaker_1.npz"

the error
__main__.py: error: argument --history_prompt: invalid typing.Union[typing.Dict, str, NoneType] value: '/projects/test/bark/bark/assets/prompts/zh_speaker_1.npz'

same, any fix

Thanks for reporting. I will open a PR to fix this.

I can't remember what led me to this solution but I ended up doing this to work around that error and it works like a charm. I make hour long audios, then I run that through rhubarb to make a lip animation, and then I overlay that on a still image of an anime chic with no mouth :)
`from bark import generate_audio, preload_models
from scipy.io.wavfile import write as write_wav
import numpy as np
import nltk
import os
nltk.download('punkt')
preload_models()
long_string = """
UNLIMITED TEXT HERE. I REMOVE QUOTE AND COLONS FIRST
AUDIO GETS SAVED AS INDIVIDUAL AUDIO FILES IN A FOLDER
AT THE END OF THE COMPLETION ALL SEGMENTS GET STRUNG INTO ONE AUDIO FILE IN MAIN DIR
IF ANY SEGMENTS WENT BAD YOU STILL HAVE THE SEGMENTS TO WORK WITH IN THE SUB DIR
"""
sentences = nltk.sent_tokenize(long_string)
Set up sample rate
SAMPLE_RATE = 22050
HISTORY_PROMPT = "en_speaker_6"
chunks = ['']
token_counter = 0
for sentence in sentences:
current_tokens = len(nltk.Text(sentence))
if token_counter + current_tokens <= 250:
token_counter = token_counter + current_tokens
chunks[-1] = chunks[-1] + " " + sentence
else:
chunks.append(sentence)
token_counter = current_tokens
Generate audio for each prompt
audio_arrays = []
output_directory = "audio_files"
if not os.path.exists(output_directory):
os.makedirs(output_directory)
for i, prompt in enumerate(chunks):
audio_array = generate_audio(prompt, history_prompt=HISTORY_PROMPT)
filename = os.path.join(output_directory, f"chunk_{i}.wav")
write_wav(filename, SAMPLE_RATE, audio_array)
audio_arrays.append(audio_array)
Combine the audio files
combined_audio = np.concatenate(audio_arrays)
Write the combined audio to a file
write_wav("combined_audio.wav", SAMPLE_RATE, combined_audio)
`

@eisneim The issue should have been fixed in the updated main branch. Thanks for reporting. Let us know if you run into other issues.

pretty sure this fix broke memory consumption on smaller than 12gb gfx cards. old version runs 0n 2070 and n1650ti, new version requires small models.. and sounds terrible.. garbled

pretty sure this fix broke memory consumption on smaller than 12gb gfx cards. old version runs 0n 2070 and n1650ti, new version requires small models.. and sounds terrible.. garbled

Hi @cybershrapnel, I only updated the cli.py. If you are not interacting with the command line this shouldn't impact you. Something else might be going on.

authors: cybershrapnel eisneim tongbaojia

repo: suno-ai/bark


text:
Add benchmarks to be included with each release

It would be good to be aware of the speeds of different common types of operations. If we want to optimize for performance, the first step is to at least know what the performance is.
The benchee benchmarking library looks like it might be all we need. We could probably just write a benchmarking script and run it on the release, and include the output in the changelog / release notes.

This is not a priority right now, so I'm closing it for possible revisiting later.

repo: sunsetworks/depo


text:
Model 701 updates

Model 701 needs the following updates based on review and working group discussion:

Update ACType to collapse THREE_PHASE_DELTA and THREE_PHASE_WYE to THREE_PHASE.
Update St with WARNING and ERROR where:
WARNING – There is an active alarm, device is able to generate with possible constraints
ERROR – This is an active alarm; device is not able to generate due to one or more of the alarm issues
Update phase A, B, C references to L1, L2, L3.
Correct Total Apparent Power description.
Add a ConnSt field that indicates whether the device is connected to the grid. The valid values are:
0 – Not connected
1 – Connected
Add ThrottlePct and ThrottleSrc with source enums.
Add an alarm bit (MANUFACTURER_ALRM) to indicate that there are additional vendor specific alarms active that are not represented in the alarm field.
Add manufacturer alarm string field – 64 bytes (32 registers) at the end of the model. The contents of the field is null terminated vendor specific string (encoding? UTF-8, Latin, other?). The MANUFACTUER_ALRM bit should be set if there is active content in manufacturer alarm string.

Resolved in #73

repo: sunspec/models


text:
Updating a user's password kills their session

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
Historically, when the PUT /admin/users/:id route was used to change a user's password (maybe other fields too — I've only tested changing passwords) their current session would not be affected. In the latest version (somewhere after v2.149) their session is immediately killed and they must re-authenticate.
This may have been an intentional change, but it appears to have caused problems for a number of people. I've included a workaround for others hitting this issue.
To Reproduce
I am only able to see this behaviour using the Supabase hosted platform (it's affecting our staging and production apps, but is not present in our development environments). If I connect my local app to the CLI Supabase instance (CLI v1.165 which ships with GoTrue v2.149) then I cannot see this behaviour, if I connect it to a hosted Supabase instance I can see this behaviour.
Here's a simplified version to reproduce with a hosted instance:

Create a user with just an email (POST /admin/users).
Generate a OTP link for that user (POST /admin/generate_link).
Verify user with OTP (POST /verify).
Update that user's password (PUT /admin/users/:id).

After step 3 the user has a session, but after step 4 the user no longer has a session.
Expected behaviour
In earlier versions (such as v2.149) the user's session would not be affected by their password being updated.
Screenshots
N/A
System information
This is on the Supabase hosted platform — I'm not sure of the GoTrue version. Is there somewhere I can see the version numbers in the dashboard? 🤷
Additional context
Issues/discussions that are possibly related:

https://github.com/orgs/supabase/discussions/23715
https://discord.com/channels/839993398554656828/1235896967754682478/1235896967754682478

Terms people hitting this issue might be searching for:

updateUserById
Session from session_id claim in JWT does not exist

Workaround
In my case, to retain the historical behaviour, we can re-authenticate the users immediately after the password is updated by signing them in again with supabase.auth.signInWithPassword() (POST /token?grant_type=password).

This is 100% expected and correct behavior. If a user's password changes, they must be logged out of all places. The user's password didn't change for no reason. For example, suppose the user learns that someone has access to their password and they take action to change it.
The only way to "kick out" the would-be attacker is to revoke all sessions for the user.

@hf Thanks! Good to know this was an intentional change to the platform.
I've said this before about other issues I've run into — it's really frustrating that changes get applied to the production environment before the CLI is updated (or even has a way to use the latest version). It means in situations like this it's impossible to reproduce the behaviour locally until the CLI happens to get updated to the latest version. I'll open issue over on the CLI repo about it.

Also note this is a breaking change since the original behavior has been changed because before you wouldn't be logged out previously and now you are being logged out.

It's not a breaking change if the previous behavior was buggy and especially in this case as it pertains to security.

I don't remember being logged out of other services when I do a password change.

It's done like this pretty much everywhere. It's industry best practice also.

then hits submit and is now signed out

Is this really true? The code is to log all other sessions: https://github.com/supabase/auth/blob/master/internal/api/user.go#L185

It's not a breaking change if the previous behavior was buggy and especially in this case as it pertains to security.

If previously it behaved one way and then that behavior has changed even if for security reasons it's a breaking change.

It's done like this pretty much everywhere. It's industry best practice also.

This is talking about forgot password, not update password. These are two different things although Supabase treats both as the same thing.

Is this really true? The code is to log all other sessions: https://github.com/supabase/auth/blob/master/internal/api/user.go#L185

I haven't tested this, but going off what's described by OP and the reply you gave I would assume this is true. I will try and get a test project setup to see if this behavior is as I've described.

If previously a public API behaved one way and then that behavior has changed even if for security reasons it's a breaking change.

It's not a breaking change if a bug/security issue was fixed. This behavior should have been expected. If there's a problem with a flow not working as intended -- not super clear if that's the case as the code will not log out the user causing the password change, then there's not much further to discuss.

It was killing the "current" session for me… but maybe that's because the password update was being done via the admin API using the service role? I'm assuming the user's session would be considered a different session than the admin role?

@haydn
Try using the "regular" api to update a password.
And "admin" api to do the rest.
Session should be intact then.

authors: hala94 haydn hf silentworks

repo: supabase/auth


text:
bug: accessing pages with an invalid #access_token hash param logs error but won't throw

Bug report
Describe the bug
As per title, accessing a page with an invalid #access_token will result in GoTrueClient failing to initialize the user sessions, but the error is only logged internally and there is no way for the client to handle this error. For an example, in my application, I would like to redirect the user to a error page and log it to Sentry, given that I know that the user with #access_token param expects to have a session associated to it.
Here it is where the error gets caught and where the "log-and-go" happens.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Minimal reproducible example lives here

run supabase stack locally supabase start
serve the POC file and open it in the browser
visit the link including #access_token=test in the url, e.g. http://localhost:3000/#access_token=test
check the browser logs for the error Error getting session from URL. Error: No expires_in detected. but won't bubble it.

Expected behavior
I would like to be able to handle that error by taking action upon it, so I would expect it to get bubbled up.

@naripok with supbase v2 release candidate (rc branch) you can catch that error and handle it. I amended your POC.
Does that fix your issue?
 <html>
  <head>
    <meta charset="utf-8">
    <title>Supabase token bug POC</title>
    <script src="https://cdn.jsdelivr.net/npm/@supabase/supabase-js@rc"></script>
    <script>
      (async () => {
        const { createClient } = supabase
        const client = createClient(
          'http://localhost:54321',
          'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24ifQ.625_WdcF3KHqz5amU0x2X5WWHP-OEs_4qj0ssLNHzTs'
        );

        const { error } = await client.auth.initialize();

        if (error) {
          console.error('Got error', error);
        } else {
          const { data: { user }, error } = await client.auth.getUser();
          console.log(user, error);
        }
      })();
    </script>
</html>

Hey @pixtron!
Thanks for the replies and sorry for the delay.
Yea, it looks like it would solve the issue. The work around looks good too.
I'll try and test it when I get the chance and let you know of any problems.
Again, thank you very much! =D

@naripok the workaround, will only work in v1, it won't work anymore in v2.

@pixtron It will work, the method is still there. https://supabase.github.io/gotrue-js/v2/classes/GoTrueClient.html#initialize

authors: hf naripok pixtron

repo: supabase/gotrue-js


text:
fix: types in package.json

make it work on deno

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: kiwicopple soedirgo

repo: supabase/storage-js


text:
Vercel NextJS with-supabase example does not work with latest node20 runtime

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
Node fetch failure when trying to use auth api.
TypeError: fetch failed
    at node:internal/deps/undici/undici:12502:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ah (/var/task/apps/www/.next/server/chunks/125.js:1:75941)
    at async au (/var/task/apps/www/.next/server/chunks/125.js:1:75685)
    at async aP.signInAnonymously (/var/task/apps/www/.next/server/chunks/125.js:1:86849)
    at async P (/var/task/apps/www/.next/server/app/quiz/hair-type/page.js:1:5165)
    at async /var/task/node_modules/.pnpm/next@14.2.3_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:418
    at async rP (/var/task/node_modules/.pnpm/next@14.2.3_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:7978)
    at async r5 (/var/task/node_modules/.pnpm/next@14.2.3_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:18:1139)
    at async es (/var/task/node_modules/.pnpm/next@14.2.3_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:16:26320) {
  [cause]: Error: connect ECONNREFUSED 127.0.0.1:54321
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1606:16)
      at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
    errno: -111,
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '127.0.0.1',
    port: 54321
  }
}

To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Following the guide to use the next boilerplate and create a project with supabase auth. only change I made was to use supabase.auth.signInAnonymously within a server action.
I deployed to vercel (where default runtime is the latest, node20) and encountered the error. Tore my hair out for a while wondering if I was missing env (particularly because I saw the 127.0.0.1 portion but I think a bit of a red herring in the end) and eventually tried to downgrade the runtime to node18 and redeploy. It worked.
https://vercel.com/templates/next.js/supabase
Expected behavior
No error when using node 20.
System information

OS: [e.g. macOS, Windows]
Browser (if applies) [chrome
Version of supabase-js: "@supabase/ssr": "^0.4.0", "@supabase/supabase-js": "^2.45.0",
Version of Node.js: 20

Additional context
The vercel template page says to report any issues here.

Hey @encima, unfortunately this can't be confirmed because the issue is encountered when deployed to Vercel which is running on AWS Lambda which only supports node.20x/18x/16x runtimes and not yet 22.

Hi @chrisui
No worries, you can use a custom fetch implementation in that case. Let me know if it doesn't work and we can reopen :)

authors: chrisui encima

repo: supabase/supabase-js


text:
fix: bump functions-js to 2.4.4

What kind of change does this PR introduce?
Updates functions-js to 2.4.4

Pull Request Test Coverage Report for Build 12408373659
Details

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

Totals

Change from base Build 12389444550:
0.0%

Covered Lines:
99

Relevant Lines:
128

💛  - Coveralls

authors: coveralls laktek


text:
BigQuery wrapper: all columns must be defined

The BQ wrapper works great out-of-the-box on supabase cloud. A game changer really for us as we only started evaluating SB yesterday.
One word of caution though - or a feature request ?: when creating the PG foreign table as per the instructions, the list of columns must match exactly the source table. Ideally one would want to define any subset instead i.e. if you only need the read a few fields. If no plan to change, please update the documentation ( + also update https://supabase.com/docs/guides/database/extensions/wrappers and  https://supabase.github.io/wrappers/ as BigQuery is available)
Workaround (especially if lots of columns): create & use a BQ view as source.

By extension, this leads to an enhancement request namely allowing a query in the server table option as seen in others fdws like https://github.com/laurenz/oracle_fdw/commit/b96f9d9ed13a8a1bec681b07096dd9f5b7918bd6

repo: supabase/wrappers


text:
chore: simplified awk usage for version extraction

Proposed changes
Simplified version extract from Gradle files from 3 calls to 1.
Readiness checklist
In order to have this pull request merged, complete the following tasks.
Pull request author tasks

[ ] I checked that all workflows return a success.
[x] I included all the needed documentation for this change.
[x] I provided the necessary tests.
[x] I squashed all the commits into a single commit.
[x] I followed the Conventional Commit v1.0.0 spec.
[ ] I wrote the necessary upgrade instructions in the upgrade guide.
[ ] If this pull request is about and existing issue,
I added the Fix #ISSUE_NUMBER or Close #ISSUE_NUMBER text to the description of the pull request.

Super-linter maintainer tasks

[x] Label as breaking if this change breaks compatibility with the previous released version.
[x] Label as either: automation, bug, documentation, enhancement, infrastructure.
[x] Add the pull request to a milestone, eventually creating one, that matches with the version that release-please proposes.

Thanks for this PR!

authors: fearphage ferrarimarco

repo: super-linter/super-linter


text:
Add rate limit to social-media/posts-lookup profile

Description

This PR

adds rate limit support to social-media/posts-lookup profile
bumps minor version of the profile to 1.2.0
adds social-media/posts-lookup profile examples
adds support for  social-media/posts-lookup v1.2.0 to Twitter and Mock map

Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I haven't repeated the code. (DRY)
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@jnv thanks for review, I fixed your comments

repo: superfaceai/station


text:
feat: use bound profile provider to call perform.

Description
This PR changes approach to calling SDK. BoundProfileProvider instance is created and used to call perform.
Creation of instance can be divided into two steps:

resolution of "SF files" we load super.json and local profileAST, mapAST and providerJson (resolveSuperfaceFiles function)
creation of BoundProfileProvider instance from "SF files"  (createBoundProfileProvider function)

these steps (functions) are used in prepareSuperface (naming sucks). This function prepares everything we need to call perform. It is easy to mock with mockBoundProfileProvider eg. in temporary test file superface-test-new.test
This approach can be extended to some (startRecording and endRecording) functions that are now private in SuperfaceTest. That would allow us easier testing (easy mocking + easy unit testing of recording fns)
This approach is, I think:

easy to test
easy to read
unable to use remote files (for now)
possibly problematic due to OneSdk exports (we need function for preparing BoundProfileProvider exported)

There is a lot of TODOs and thing that can be improved (errors). My main goal was to simplify whole solution and enable reasonable testing.
Motivation and Context
Using Client that actually calls bind is imo not good approach - it is hard to test and to read. It is also more complicated that it has to be (I believe).
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have updated the documentation accordingly. If you are changing code related to user secrets you need to really make sure that security documentation is correct.
[ ] I have read the CONTRIBUTION_GUIDE document.
[ ] I haven't repeated the code. (DRY)
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@Jakub-Vacek @freaz I finished most of what we talked about, so please review 🙏🏻
I only have to fix not passing tests and maybe figure out how to mock recording better, now that it's abstracted to functions.

It looks ok (I checked files that were changed after my last review). Please resolve conflicts before final review.

authors: Jakub-Vacek martinalbert

repo: superfaceai/testing


text:
Upgrade etcd version

Upgrade etcd from version 2 to version 3 to align with
CoreOS version.

Coverage increased (+0.02%) to 55.327% when pulling 10dd934b443ae80b19bcac8a2467f9187a535679 on stgleb:fix_master_yaml into db1e21f4e6891a29a1fa56d4506f4afa5371c440 on supergiant:master.

LGTM

LGTM

authors: coveralls gopherstein saheienko stgleb

repo: supergiant/supergiant


text:
[SuperEditor] [Android] Magnifier position is broken when Editor in a CustomScrollView

Package Version
main branch with commit hash https://github.com/superlistapp/super_editor/commit/2cb93e23ba2442e911c1bfcaf107c247adc6d131
To Reproduce

Go to Sliver Editor demo
Scroll down a bit
Place the selection in the content
Start dragging the drag handle upwards

Actual behavior
Initially the magnifier is not visible and as the drag handle is moved towards the top of the editor, then we see the magnifier coming from the bottom and getting closer to the selection.
Expected behavior
The magnifier is visible above the selection.
Platform
Android.
Flutter version
Flutter master commit e278279a48f0479386c249cf18f26b29c6f9018f.
Screenshots
https://github.com/superlistapp/super_editor/assets/31278849/bba51f3a-6ca4-4f2a-b29c-91c31e6f00e1

Hey super editor team, Is it possible to kill 2 birds with one stone, fixing the ios magnifier position? :)
https://github.com/superlistapp/super_editor/issues/1496

@BazinC this work is already done. Can you please file a new ticket? Btw, we'll need more than just a screenshot. Please show where the magnifier should appear vs where it actually appears. You might want to place an iOS screeshot next to a SuperEditor screenshot for comparison.

authors: BazinC matthew-carroll miguelcmedeiros


text:
Make tests compile + pass

Just tidied up a few syntax errors so tests would pass again! :octocat:
Looks like the current MakeFile returns 0 if tests don't compile, which gives travis a false-positive.

@supermarin looks like the build stalled. Can you try re-running it?

@dasmer thanks for the contribution! yes - let me try to run it again

authors: dasmer supermarin

repo: supermarin/ObjectiveSugar


text:
Rename /test to /t to work with most p6 testing tools

The p6 tools should probably be changed to take /test, but
until then...
http://testers.perl6.org/dist/SCGI

The reason the tests are in /test and not /t is that they are not automated tests. They don't work with any testing tools. The /test directory should probably be renamed /samples instead.

Don't know how I overlooked that. Thanks for clarifying!

authors: supernovus ugexe

repo: supernovus/SCGI


text:
🛑 Node - tr-2d50afca.yalaso.top is down

In a41de1f, Node - tr-2d50afca.yalaso.top (http://tr-2d50afca.yalaso.top/api/v1/ping) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Node - tr-2d50afca.yalaso.top is back up in 083f1df after 8 days, 11 hours, 55 minutes.

repo: superrr-vpn/status


text:
🛑 Snack Sized Fiction is down

In 14f8851, Snack Sized Fiction (https://snacksizefiction.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Snack Sized Fiction is back up in 254f232 after 17 minutes.

repo: superwebpros/uptime


text:
同步代码

同步代码

同步


text:
Potential performance problem

For some reason when I do an HTTP query to get all data from a table that contains 3 records the average response is 50ms.
But when I do the query directly using the HTTP client (Insomnia) the query takes under 1ms. Even in python library query using WS takes under 1ms.
For both HTTP and WS client the query duration is same.
      Sending HTTP request GET http://127.0.0.1:8000/key/migrations
info: System.Net.Http.HttpClient.[SurrealDB] http://127.0.0.1:8000/.ClientHandler[101]
      Received HTTP response headers after 44.1242ms - 200
info: System.Net.Http.HttpClient.[SurrealDB] http://127.0.0.1:8000/.LogicalHandler[101]
      End processing HTTP request after 44.2145ms - 200

os: macOS 14.5
chipset: Apple M3 Pro 18gb
docker: 4.30.0
surreal: 1.5.2
dotnet: 8.0.302
surreal.net: 0.5.0

Hello Thomas,
50ms is not an eternity but it still feels very suspicious indeed.

Let me just start that benchmarks are run daily and the last one (you can see here) that run gives me the following:

Method
Runtime
Mean
Error
StdDev
Gen0
Allocated

Http
NativeAOT 8.0
18.522 ms
0.2651 ms
0.2479 ms
-
259.16 KB

HttpWithClientFactory
NativeAOT 8.0
18.527 ms
0.2570 ms
0.2279 ms
-
262.46 KB

WsText
NativeAOT 8.0
10.812 ms
0.1067 ms
0.0998 ms
15.6250
2015.37 KB

Http
.NET 8.0
18.865 ms
0.3771 ms
0.4191 ms
-
289.67 KB

HttpWithClientFactory
.NET 8.0
18.873 ms
0.2826 ms
0.2643 ms
-
295.26 KB

WsText
.NET 8.0
9.100 ms
0.0882 ms
0.0782 ms
-
2011.19 KB

Let's concentrate on the .NET 8.0 runtime for now. The WsText protocol is the fastest one and it gets 1_000 records in less than 10ms. Details of the machine where the test ran:
BenchmarkDotNet v0.13.10, Ubuntu 22.04.4 LTS (Jammy Jellyfish)
AMD EPYC 7763, 1 CPU, 4 logical and 2 physical cores
.NET SDK 8.0.302
  [Host]     : .NET 8.0.6 (8.0.624.26715), X64 RyuJIT AVX2
  Job-BVNALS : .NET 8.0.6, X64 NativeAOT AVX2
  Job-GMCZFX : .NET 8.0.6 (8.0.624.26715), X64 RyuJIT AVX2

I assume your machine is even more performant than this one.

I can see that you are running an ASP.NET Core app. So, is 50ms the time the library spent to retrieve and deserialize the response, or is it the total time of the HTTP server request? Note that an ASP.NET server can add overhead (middleware, logging, etc..).

If this is indeed the total time of the server request, you can use a Stopwatch around the Select method to measure the (almost exact) time the .NET SDK take to get and the result.

Of course 50ms is not forever. It just struck me that the same query SELECT * FROM migrations in surrealist.app takes +- 0.5ms and in dotnet8 100x more.
The 50ms is measured with Stopwatch and in python time.time directly on the Query method. Added log from console approximately the same with Stopwatch measurement.

This is weird. Do you have a reproduction program to share?

using System.Diagnostics;
using System.Text.Json;

using SurrealDb.Net;

var builder = WebApplication.CreateBuilder(args);

var url = Var("SURREAL_URL") ?? "127.0.0.1:8000";
var protocol = Var("SURREAL_PROTOCOL") ?? "ws";
var suffix = protocol.StartsWith("ws") ? "/rpc" : "";
var endpoint = $"{protocol}://{url}{suffix}";

builder.Services.AddSurreal(
    SurrealDbOptions
            .Create()
            .WithEndpoint(endpoint)
            .WithNamespace(Var("SURREAL_NAMESPACE") ?? "default_ns")
            .WithDatabase(Var("SURREAL_DATABASE") ?? "default_db")
            .WithUsername(Var("SURREAL_USERNAME") ?? "root")
            .WithPassword(Var("SURREAL_PASSWORD") ?? "root")
            .Build(),
    lifetime: ServiceLifetime.Scoped,
    configureJsonSerializerOptions: options => {
        options.PropertyNamingPolicy = JsonNamingPolicy.SnakeCaseLower;
    }
);

var app = builder.Build();

app.MapGet("/", () => "Hello World!");

app.MapGet("/AllMigrations", async (ISurrealDbClient client, CancellationToken ct) => {
    var stopwatch = new Stopwatch();
    stopwatch.Start();
    var response = await client.Query($"SELECT * FROM migrations", ct);
    stopwatch.Stop();

    Console.WriteLine($"Ellapsed on AllMigrations query: {stopwatch.ElapsedMilliseconds}ms");
});

app.MapGet("/GetCompletedMigrations", async (ISurrealDbClient client, CancellationToken ct) => {
    var stopwatch = new Stopwatch();
    stopwatch.Start();
    var response = await client.Query($"SELECT VALUE name FROM migrations WHERE completed = true", ct);
    stopwatch.Stop();

    Console.WriteLine($"Ellapsed on GetCompletedMigrations query: {stopwatch.ElapsedMilliseconds}ms");

    stopwatch = new Stopwatch();
    stopwatch.Start();
    var names = response.GetValues<string>(0);
    stopwatch.Stop();

    Console.WriteLine($"Ellapsed on GetValues<string> for GetCompletedMigrations: {stopwatch.ElapsedMilliseconds}ms");

    return names;
});

app.Run();

static string? Var(string varName) {
    return Environment.GetEnvironmentVariable(varName);
}

Ah, thank you for taking the time to make a reproduction example.
I can see 2 major performance limitations. This first one made me jump from 30ms to 3ms. The second one down to 1ms. I'll explain.

The main pain point I if should say so is that you set lifetime: ServiceLifetime.Scoped, which mean that every time you trigger an endpoint, it will create a new instance of the client. When you create, it is not connected to the database, so you lost a lot of time not only to create a new client but also to create a new Socket connection (whether HTTP or WS). I can see that you do not depend on authentication feature (i.e. per user query), so setting ServiceLifetime.Singleton would be better for your use case.

I am currently working on a way to consume a pool of clients, so that you do not have to recreate a client and better yet not to reconnect on each instance injection. So, I'd recommend to use Singleton (if you can) for the best performance until this feature is available.

You are setting configureJsonSerializerOptions to set the JsonNamingPolicy. As of now, this factory will create a new Serializer each time you make a request. I already implemented a cache on this pattern. It will come soon.

Hope that would be helpful to you. Feel free to ask any question.

That makes sense. I thought client pooling was implemented, so I automatically chose scoped lifetime, but singleton is the way to go for me too.
Unfortunately, I removed all the converters I have implemented for Strong Typed IDs from this demo. So I'll wait.
I'm closing this issue now that penalties are already addressed. Thanks for the explanation and I look forward to the update!
P.S. Wouldn't it be useful to note that for now there is no client pooling and JsonSerializer is not cached?

authors: Odonno Thomasparsley