Cannot render states with typing.ForwardRef

Describe the bug
I tried to render a tree, but kept getting missing attribute errors whenever I had a ForwardRef in my state.
To Reproduce
Steps to reproduce the behavior:

Code/Link to Repo:

class ASTNodeState(rx.Base):
    key: str = "unknown"
    type: str = "unknown"
    text: str = "loading"
    children: List["ASTNodeState"] = []

class ASTNodeView(rx.ComponentState):

    @classmethod
    def get_component(cls, children: List[ASTNodeState], key: str, type: str, text: str) -> rx.Component:

        return rx.chakra.span(rx.text(key), rx.chakra.text(type), rx.chakra.text(text),
                              rx.foreach(children, render_child))

ast_node_view = ASTNodeView.create

def render_child(item: ASTNodeState):
    # hack to make recursion possible, this leads to an infinite loop in some deep copy function
    # item.__var_type = ASTNodeState
    # hack that I tried to use to derive type of the member (by also hacking in the Var.__getattr__ function)
    # item.___actual_class = ASTNodeState
    # final hack I tried, that also didn't work
    # other_item: ASTNodeState = item
    return ast_node_view(key=item.key, type=item.type, text=item.text, children=item.children)

Expected behavior
I expected a beautiful tree structure to render...
Specifics (please complete the following information):

Python Version: 3.11 and 3.9 I tried
Reflex Version: reflex==0.5.2
OS: Ubuntu
Browser (Optional): Chrome, but the problem seems to occur in the python code.

Additional context
When I hack the __var_type to the correct class I get infinite loops. I tried to create a member with the actual class and use that to detect type, but that for some weird reason raised an exception when run (but not when evaluated in my debugger).
The end of a frustrating day...
Weird stuff...

Note that this means no cyclic references between states and thus no recursion. So you wouldn't be able to make redit, because redit contains a tree structure, which is recursive.

Using rx.cond also doesn't fix this...

@guidocalvano I was looking a bit into this yesterday. There's a couple fixes we need to make to the framework to fully support this, but the code below avoids the infinite recursion:
import reflex as rx
from typing import List

class ASTNodeState(rx.Base):
    key: str = "unknown"
    type: str = "unknown"
    text: str = "loading"
    children: List["ASTNodeState"] = []

class ASTNodeView(rx.ComponentState):

    @classmethod
    def get_component(
        cls, children: List[ASTNodeState], key: str, type: str, text: str
    ) -> rx.Component:
        # need to convert it to a var and specify the type.
        children = rx.Var.create(children).to(list[ASTNodeState])

        return rx.chakra.span(
            rx.text(key),
            rx.chakra.text(type),
            rx.chakra.text(text),
            rx.foreach(children, render_child),
        )

ast_node_view = ASTNodeView.create

# rx.memo pulls the function into it's own definition, avoiding the infinite recursion
@rx.memo
def ast_node(children: List[ASTNodeState], key: str, type: str, text: str):
    return ast_node_view(key=key, type=type, text=text, children=children)

def render_child(item: ASTNodeState):
    return ast_node(
        key=item.key, type=item.type, text=item.text, children=item.children
    )

comp = ASTNodeState(key="1", type="type1", text="text1", children=[
        ASTNodeState(key="1.1", type="type1", text="text1", children=[
    ]),
])

def index() -> rx.Component:
    return rx.fragment(
        ast_node_view([
            ASTNodeState(key="1", type="type1", text="text1", children=[
                ASTNodeState(key="1.1", type="type1", text="text1", children=[
            ]),
            ]),
        ], key="root", type="root", text="root"),
    )

app = rx.App()
app.add_page(index)

The recursion is caused because by default Reflex evaluates all the components into one giant component for the page. Using @rx.memo pulls out the component into its own function instead of evaluating it. There's one bug we need to fix #3438 to fix the serialization and then this should work.
The @rx.memo isn't documented much because it was kind of a hack we needed. We're planning on cleaning it up and documenting it in the future.

Hello, I was applying for your open source developer position and was interested in applying. Could I be assigned this issue in order to start?

@shauryaryan just assigned you to it - this one may be a bit hard, let us know if you need any help going through it


Bot crash

2022-04-07 05:46:18.196960912 +00:00 Fetching data from https://warthunder.com/en/news 2022-04-07 05:46:18.573269299 +00:00 Fetching data from https://warthunder.com/en/news/7640-event-the-battle-for-arachis-en 2022-04-07 05:46:18.810562546 Content was recently fetched and is not new 2022-04-07 05:46:18.810603955 +00:00 Fetching data from https://warthunder.com/en/game/changelog/ 2022-04-07 05:46:19.001074839 +00:00 Fetching data from https://warthunder.com/en/game/changelog/current/1360 thread 'main' panicked at 'called Option::unwrap()on aNonevalue', src/scrapers/scrape_meta.rs:117:82 note: run withRUST_BACKTRACE=1 environment variable to display a backtrace

Investigating now


Any idea for how to create calendar event for ng-bootstrap modal popup

Sir, Any idea for how to make your calendar event for  ng-bootstrap modal popup ??

Im attached my  sample calendar view, I want to know how to add this event for modal popup?
(I mean When I click the some event i want to show some modal popup, example click on the 16 of  December   ,  its has 2 event name , i want to show click 1st event Susena  want to display modal popup, click 2nd event  name Lahiru   want to display modal popup,   ) any idea ?
This is my code
index.component.ts
export class IndexComponent {

calendarOptions: Object = {
    height: 'auto',

    defaultDate: '2017-12',
    editable: true,
    eventLimit: true, // allow "more" link when too many events
    navLinks: true,
    resourceAreaWidth: '15%',
    views: {
      timelineThreeDays: {
        type: 'timeline',
        duration: {
          days: 365
        }
      }
    },
    resourceLabelText: 'Rooms',
    resources: [{
      id: 'a',
      Rooms: ' Single Rooms (8)',
      title: 'Room # 1'
    }, {
      id: 'b',
      Rooms: ' Single Rooms (8)',
      title: 'Room # 2',
      eventColor: 'green'
    }, {
      id: 'c',
      Rooms: ' Single Rooms (8)',
      title: 'Room # 3',
      eventColor: 'orange'
    }, {
      id: 'd',
      Rooms: ' Single Rooms (8)',
      title: 'Room # 4',
      children: []
    }, {
      id: 'e',
      Rooms: ' Single Rooms (8)',
      title: 'Room # 5'
    }, {
      id: 'f',
      Rooms: ' Single Rooms (8)',
      title: 'Room # 6',
      eventColor: 'red'
    }, {
      id: 'g',
      Rooms: ' Single Rooms (8)',
      title: 'Room # 7',
      eventColor: 'orange'
    }, {
      id: 'h',
      Rooms: ' Single Rooms (8)',
      title: 'Room # 8',
      eventColor: 'green'
    }, {
      id: 'i',
      Rooms: ' Double Rooms (2)',
      title: 'Room # 9',
      eventColor: 'red'
    }, ],
    events: [

      {
        id: '1',
        resourceId: 'a',
        start: '2017-12-01',
        end: '2017-12-07',
        title: 'Mahesh'
      }, {
        id: '2',
        resourceId: 'b',
        start: '2017-12-12',
        end: '2017-12-15',
        title: 'Anushka'
      }, {
        id: '3',
        resourceId: 'c',
        start: '2017-12-11',
        end: '2017-12-15',
        title: 'Ramesh'
      }, {
        id: '4',
        resourceId: 'd',
        start: '2017-12-11',
        end: '2017-12-19',
        title: 'Susena'
      }, {
        id: '5',
        resourceId: 'e',
        start: '2017-12-15',
        end: '2017-12-28',
        title: 'Lahiru'
      }, {
        id: '6',
        resourceId: 'f',
        start: '2017-12-01',
        end: '2017-12-10',
        title: 'Chamath'
      }, {
        id: '7',
        resourceId: 'g',
        start: '2017-12-10',
        end: '2017-12-11',
        title: 'Channa'
      }, {
        id: '8',
        resourceId: 'h',
        start: '2017-12-09',
        end: '2017-12-14',
        title: 'Ganesh'
      }, {
        id: '9',
        resourceId: 'i',
        start: '2017-12-05',
        end: '2017-12-09',
        title: 'Priya'
      }
    ],
  }

maybe (eventClick)="eventClick($event.detail)"?


Document Whatever,  WhateverCode and HyperWhatever methods

The problem
These classes define some methods, and they are not documented.
Suggestions
After clarification of what they actually are, add some documentation either in the form of methods or simply adding to the intro. Also check out #2017  before this.

Updated links to match core.c

WhateverCode
Whatever


Remove 'image' from 'CrowPi Goes Java'-Project

todo

remove everything dealing with image creation from CrowPi Goes Java
update tutorial

done

CrowPi Goes Java

[x] successful build
[ ] new release

tutorial

[x] developer has used the updated tutorial to start with a new CrowPi-project
[ ] new release

@ppmathis Do we really want to have a new release?

While I am not sure if there is any need for a new release, it could be created via GitHub UI:

Click on Releases on the right hand side of the repo view
Click on Draft a new release in the top right
Specify a new tag name like 1.1.0 according to semantic versioniong
Add some title/text and click Publish release

Unlike the OS images it is not such a big deal with the example/docs repos, but releases would allow to clearly mark some version as "good-to-go", so once everything has been updated it might make sense to create one.


Pricing Calculator V2

Summary
On August 11th, we launched V1 of the pricing calculator page that supports the cost estimates for Codespaces, Actions, Packages, GHAS.
We are planning to add the following new features to the pricing calculator and continue improving the experience to calculate the cost for GitHub products.
Q2 Milestones

[x] FAQ
[x] Free Trial CTA
[x] Hints

Intended Outcome
Enable GitHub Sales and Customers to calculate cost and budgets for Consumables.
How will it work?
Free Trial CTA

FAQs

Hints

https://github.com/pricing/calculator


Spike Address Lookup

What is the context of this PR?
The initial approach to integrating the address lookup.
Options considered:
1. New answer type:
Looked at using a new answer type; but it was not suitable and did not fit the model we currently have. The only way new answer type might be feasible is by having a new property on the answer object like we have "options" with Checkbox/Radio. However, this didn't solve the issue of still being able to store each address field answer individually and required a lot more changes. A new answer type would be appropriate, if we wanted to store all lines of the address as one answer.
2. New question type (spike)
This was the best option to make address lookup work which met the requirements while making minimal changes.
As implemented, the new question type allows us to have the 4 separate address answer fields which means we can store the answers separately while reusing existing functionality to concatenate these together for the user on the summary using question summary. This approach should also help us with handling the UPRN hidden field.
Caveats:
Due to the way the address component is built, there are a few rules we need to adhere to:

The answer IDs must be consistent and must have the same parent id. To do this, I used the format:

{question_id}-{field_id} for example address-line1, address-line2, address-town etc.

Only address line 1 can be mandatory, the front-end component doesn't support address other mandatory fields, so questionnaire validator will need to ensure that address line 1 is and is the only mandatory answer.
Have not added support for answer guidance to each answer field. Not required for the current Address lookup.

Known issues:

If the API is down, returning to the address lookup question from the summary displays the lookup when it shouldn't. This will be fixed soon in the DS.
Error panel shown on the manual fields will persist and be displayed on the lookup pag which results in a double error panel. This will also be fixed soon in the DS.

How to review

To test this, you will need to get your IP whitelisted for AI whitelodge by requesting it via #typeaheadintegration Slack channel.
Make sure you load the latest templates.

Ensure the address lookup works as expected.
Ensure answers are in the payload as expected.
Do you agree with the approach?
Was anything missed?

Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

Going to spike an answer type approach with a new custom answer store object.

There are some downsides to the new question type:

We are adding logic to the jinja filters that we've said we need to move away from
There are a number of schema properties that need to be defined in a specific way for this to work, and align to the fixed values in the jinja filter. This would also mean extra validator logic to ensure the schema for addresses is valid, which again we've said we'd like to avoid.

I think we should spike the answer type approach, then we can compare the two and choose the best option.
In order for us to be able to store each address field independently, we could store the answer as an object in the answer store, something like:
{
  "line1": "dsvdsv",
  "line2": "dvdsv",
  "town": "dsvdsv",
  ...
}

https://github.com/ONSdigital/eq-questionnaire-runner/pull/241 chosen as the preferred way to implementing addresses in runner.

https://github.com/ONSdigital/eq-questionnaire-runner/pull/241 chosen as the preferred way to implementing addresses in runner.


[WIP] [DO NOT MERGE] Propagate constraints

test run of basically rewritten constraint propagation

@swift-ci Please test

Are you going to add some new tests too?

@slavapestov Before this gets merged, yes. I need to go through bug reports and see what is working at this point and start adding reasonable representatives as scale-test style tests.
I already know there are a couple crashers and regressed diagnostics so it might be a couple days before this is enabled.

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - c2efc60c0f7f6881f1d638c09aa2491f95ac2cb6
Test requested by - @rudkx

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - c2efc60c0f7f6881f1d638c09aa2491f95ac2cb6
Test requested by - @rudkx


automatically group question-like ressources

keys like

"Are you sure?"
"Do you rellay want to delete the file '{fileName}'?)
"Enable the feature {featureName} for user {userName}

could produce extensionMethods used like:

localize.Questions().Are_you_sure()
localize.Questions().Do_you_really_want_to_delete_the_file__fileName(objectfileName)
localize.Questions().Enable_the_feature__featureName__for_user__userName(object featureName, object userName)

parsing should respect known locale-specifics like spanish:

Delete file '{fileName}' ? ¿Eliminar archivo '{Nombre}'?

possible convention could be to group all keys starting (or ending) with ? int such an extension

Maybe there should be a manually usable convention under the hood, where this could plug into.

#14 should be tackled with, first

now with the arrival of #64, this should be easily achieved

feature is too opiniated about the structure of resx-file keys.
Staring with v0.8, people can utilize groupings no matter what. No need to be opiniated, here...


[Feature Request]Any plans to upgrade the following code to MiniCssExtractPlugin

As per title, are there plans to upgrade the following code to use MiniCssExtractPlugin since the Webpack team is ending support for ExtractTextWebpackPlugin.
https://github.com/vuejs-templates/webpack/blob/4ffcccb2e3b5c8f18ac5c28023ed983bb183ef96/template/build/utils.js#L48-L51
The reason for this issue is because I am unable to use the MiniCssExtractPlugin.loader for extracting the css.

We might switch this template to webpack 4 in some time. When we do that, we will use rust plugin as well


Fill kwargs

Solves the problem #6 with new Summary instances created with labels not using invariants, max_age_seconds and age_buckets

Thank you for pull request!


Fix documentation typo

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

ok. I assume you are ok to keep the typo in your doc. cleaning up.


Update documentation code samples to reflect updates in HelloWorld sample generator

Category

[ ] Question
[ ] Typo
[X] Bug
[ ] Additional article idea

Expected or Desired Behavior
Tutorial code examples should work with the current Yeoman HelloWorld sample generator.
Observed Behavior
Starting on this page of the tutorial, and continuing through the remainder of it - the code examples produce errors in the current version of HelloWorld.
Here is another user's StackExchange posting indicating the same issue 9 months ago.
Steps to Reproduce

Create a new HelloWorld web part by running the Yeoman SharePoint Generator.
Navigate here, and attempt to copy/paste the code samples as instructed in the documentation tutorials.
Continue here, and attempt to copy/paste the code examples as instructed in the documentation tutorials.

Just ran through the entire tutorial with zero issues so I think this is an old issue that was already resolved...


Uncaught TypeError: Cannot read property 'file' of undefined

[Enter steps to reproduce below:]
Just tried to open the python debugger from the packages menu
Atom Version: 1.9.2
System: Mac OS X 10.11.6
Thrown From: python-debugger package, v0.1.0
Stack Trace
Uncaught TypeError: Cannot read property 'file' of undefined
At /Users/zakkhoyt/.atom/packages/python-debugger/lib/python-debugger-view.coffee:19

TypeError: Cannot read property 'file' of undefined
    at PythonDebuggerView.module.exports.PythonDebuggerView.getCurrentFilePath (/Users/zakkhoyt/.atom/packages/python-debugger/lib/python-debugger-view.coffee:19:26)
    at PythonDebuggerView.module.exports.PythonDebuggerView.initialize (/Users/zakkhoyt/.atom/packages/python-debugger/lib/python-debugger-view.coffee:156:26)
    at PythonDebuggerView.View [as constructor] (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-space-pen-views/node_modules/space-pen/lib/space-pen.js:184:25)
    at new PythonDebuggerView (/Users/zakkhoyt/.atom/packages/python-debugger/lib/python-debugger-view.coffee:12:3)
    at Object.module.exports.PythonDebugger.createDebuggerView (/Users/zakkhoyt/.atom/packages/python-debugger/lib/python-debugger.coffee:18:33)
    at atom-workspace.subscriptions.add.atom.commands.add.python-debugger:toggle (/Users/zakkhoyt/.atom/packages/python-debugger/lib/python-debugger.coffee:28:37)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:160:19)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (/Applications/Atom.app/Contents/Resources/app.asar/src/atom-environment.js:1104:28)
    at EventEmitter.outerCallback (/Applications/Atom.app/Contents/Resources/app.asar/src/application-delegate.js:327:25)
    at emitTwo (events.js:100:13)
    at EventEmitter.emit (events.js:185:7)

Commands
     -0:00.2.0 python-debugger:toggle (table.package-keymap-table.table.native-key-bindings.text)

Config
{
  "core": {
    "projectHome": "~/Code/repositories"
  }
}

Installed Packages
# User
language-python, v0.45.0 (active)
python-debugger, v0.1.0 (inactive)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.51.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.43.0 (inactive)
base16-tomorrow-dark-theme, v1.1.0 (inactive)
base16-tomorrow-light-theme, v1.1.1 (inactive)
one-dark-ui, v1.3.2 (active)
one-light-ui, v1.3.2 (inactive)
one-dark-syntax, v1.2.0 (active)
one-light-syntax, v1.2.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.5.2 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.1 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.0 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.0 (active)
bookmarks, v0.41.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.38.1 (active)
fuzzy-finder, v1.3.0 (active)
git-diff, v1.1.0 (active)
find-and-replace, v0.198.0 (inactive)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.1 (active)
image-view, v0.58.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v0.53.1 (active)
notifications, v0.64.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.238.0 (active)
snippets, v1.0.2 (active)
spell-check, v0.67.1 (active)
status-bar, v1.4.0 (active)
styleguide, v0.46.0 (active)
symbols-view, v0.113.0 (inactive)
tabs, v0.98.0 (active)
timecop, v0.33.1 (active)
tree-view, v0.208.0 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.34.0 (active)
whitespace, v0.32.2 (active)
wrap-guide, v0.38.1 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.0 (active)
language-csharp, v0.12.1 (active)
language-css, v0.36.2 (active)
language-gfm, v0.86.0 (active)
language-git, v0.13.0 (active)
language-go, v0.42.0 (active)
language-html, v0.44.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.22.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.0 (active)
language-less, v0.29.3 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.0 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.68.5 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.52.0 (active)
language-shellscript, v0.22.3 (active)
language-source, v0.9.0 (active)
language-sql, v0.21.1 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.8 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

I'm currently traveling and I'll look into this when I return. In the meantime, if you find how to fix the issue, I'll definitely welcome a pull request.

Sorry for the long wait. I'm not able to reproduce this. Are you still having the same issue? (I'm on Atom 1.10.2.) Thanks.

No worries, I understand. It can be hard to tend to all projects all the
time.
Sorry, but I don't have any feedback for you at this time. I was using your
tool for a quick project and have since moved on. I'll let you know if I
come back to it and am having issue.
Thanks,
-Zakk
On Tue, Sep 20, 2016 at 3:08 PM, Dominique<EMAIL_ADDRESS>wrote:

Sorry for the long wait. I'm not able to reproduce this. Are you still
having the same issue? (I'm on Atom 1.10.2.) Thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dpo/atom-python-debugger/issues/9#issuecomment-248450006,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACIEoLYCVyVgRJ-RlF_y8BtXn9XvsfbBks5qsFl6gaJpZM4JcTh3
.

Ok thanks. I'll go ahead and close this but feel free to open a new issue if problems persist.

I still have this issue. @dpo
Steps to reproduce

Select Packages > Python-debugger > Toggle on Search page

Atom Version: 1.10.2
Electron Version: 0.37.8
System: "Fedora release
Thrown From: python-debugger package, v0.1.0
Stack Trace
Uncaught TypeError: Cannot read property 'file' of undefined
At /home/fdobrovo/.atom/packages/python-debugger/lib/python-debugger-view.coffee:19

TypeError: Cannot read property 'file' of undefined
    at PythonDebuggerView.module.exports.PythonDebuggerView.getCurrentFilePath (/home/fdobrovo/.atom/packages/python-debugger/lib/python-debugger-view.coffee:19:26)
    at PythonDebuggerView.module.exports.PythonDebuggerView.initialize (/home/fdobrovo/.atom/packages/python-debugger/lib/python-debugger-view.coffee:156:26)
    at PythonDebuggerView.View [as constructor] (/home/fdobrovo/.atom/packages/python-debugger/node_modules/space-pen/lib/space-pen.js:184:25)
    at new PythonDebuggerView (/home/fdobrovo/.atom/packages/python-debugger/lib/python-debugger-view.coffee:12:3)
    at Object.module.exports.PythonDebugger.createDebuggerView (/home/fdobrovo/.atom/packages/python-debugger/lib/python-debugger.coffee:18:33)
    at atom-workspace.subscriptions.add.atom.commands.add.python-debugger:toggle (/home/fdobrovo/.atom/packages/python-debugger/lib/python-debugger.coffee:28:37)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app.asar/src/command-registry.js:260:29)
    at CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app.asar/src/command-registry.js:3:61)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (/usr/share/atom/resources/app.asar/src/command-registry.js:160:19)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (/usr/share/atom/resources/app.asar/src/atom-environment.js:1109:28)
    at EventEmitter.outerCallback (/usr/share/atom/resources/app.asar/src/application-delegate.js:329:25)
    at emitTwo (events.js:100:13)
    at EventEmitter.emit (events.js:185:7)

Commands
     -0:26.3.0 settings-view:open (atom-text-editor.editor.is-focused)
     -0:18.6.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -0:00.2.0 python-debugger:toggle (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)

Config
{
  "core": {
    "themes": [
      "one-light-ui",
      "one-light-syntax"
    ]
  }
}

Installed Packages
# User
autocomplete-python, v1.8.12 (active)
linter, v1.11.18 (active)
linter-flake8, v2.1.1 (active)
linter-pydocstyle, v0.4.3 (active)
minimap, v4.25.6 (active)
minimap-bookmarks, v0.4.2 (active)
minimap-cursorline, v0.2.0 (active)
minimap-find-and-replace, v4.5.1 (active)
minimap-highlight-selected, v4.4.0 (active)
minimap-linter, v1.6.0 (active)
python-debugger, v0.1.0 (inactive)
python-indent, v1.0.0 (active)
python-isort, v0.0.7 (active)
python-tools, v0.6.8 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.1.0 (inactive)
base16-tomorrow-light-theme, v1.1.1 (inactive)
one-dark-ui, v1.5.0 (inactive)
one-light-ui, v1.5.0 (active)
one-dark-syntax, v1.3.0 (inactive)
one-light-syntax, v1.3.0 (active)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.5.3 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.41.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.39.0 (active)
find-and-replace, v0.201.0 (active)
fuzzy-finder, v1.3.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.1 (active)
image-view, v0.58.2 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v0.53.1 (active)
notifications, v0.65.0 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2 (active)
snippets, v1.0.2 (active)
spell-check, v0.67.1 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.0 (inactive)
tabs, v0.100.2 (active)
timecop, v0.33.2 (active)
tree-view, v0.208.2 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.34.0 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.1 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

Sorry for the long delay. Should be fixed in #38.

I'm having this issue now.  Is there a work-around?

[Enter steps to reproduce:]

Packages->Python-Debugger->Toggle
Uncaught TypeError pops up

Atom: 1.26.0 x64
Electron: 1.7.11
OS: Microsoft Windows 7 Professional
Thrown From: python-debugger package 0.2.0
Stack Trace
Uncaught TypeError: Cannot read property 'file' of undefined
At C:\Users\Stephen.Fitzgerald\.atom\packages\python-debugger\lib\python-debugger-view.coffee:19

TypeError: Cannot read property 'file' of undefined
    at PythonDebuggerView.module.exports.PythonDebuggerView.getCurrentFilePath (/packages/python-debugger/lib/python-debugger-view.coffee:19:26)
    at PythonDebuggerView.module.exports.PythonDebuggerView.initialize (/packages/python-debugger/lib/python-debugger-view.coffee:156:26)
    at /packages/autocomplete-python/node_modules/space-pen/lib/space-pen.js:184:25)
    at /packages/python-debugger/lib/python-debugger-view.coffee:11:7)
    at Object.createDebuggerView (/packages/python-debugger/lib/python-debugger.coffee:19:29)
    at /packages/python-debugger/lib/python-debugger.coffee:29:37)
    at CommandRegistry.handleCommandEvent (~/AppData/Local/atom/app-1.26.0/resources/app/src/command-registry.js:384:49)
    at CommandRegistry.dispatch (~/AppData/Local/atom/app-1.26.0/resources/app/src/command-registry.js:273:23)
    at AtomEnvironment.dispatchApplicationMenuCommand (~/AppData/Local/atom/app-1.26.0/resources/app/src/atom-environment.js:1347:25)
    at EventEmitter.outerCallback (~/AppData/Local/atom/app-1.26.0/resources/app/src/application-delegate.js:339:53)
    at emitThree (events.js:116:13)
    at EventEmitter.emit (events.js:197:7)

Commands
     -3:51.2.0 debugger:show (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -3:45 debugger:show-launch-dialog (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -3:40 core:cancel (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -3:21.8.0 python-debugger:toggle (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)

Non-Core Packages
atom-ide-ui 0.11.0
atom-python-run 0.9.6
autocomplete-python 1.10.5
ide-python 0.9.2
python-debugger 0.2.0
python-indent 1.1.5
python-tools 0.6.9


Add FastConnectable = true option?

It always takes at least 5 seconds for my linux laptop to connect to the pi with the standard bluetooth config.
If I add FastConnectable = true to the pi it always connects <1s. Perhaps worth adding to your script?

I could not really find what FastConnectable exactly does, other than enabling faster connections and leading to higher power consumption (on which device? On the client also?)
In some cases it seems to lead to poor sound quality: https://erikdubois.be/installing-bose-quietcomfort-35-linux-mint-18/ (In this report it is used on the A2DP source however, in our case it's the A2DP sink).

I too don't understand what it does but probably sends out advertisements/beacons more quickly than normal or something?On 21 Sep 2020 16:59, Nico Kaiser<EMAIL_ADDRESS>wrote:
I could not really find what FastConnectable exactly does, other than enabling faster connections and leading to higher power consumption (on which device? On the client also?)
In some cases it seems to lead to poor sound quality: https://erikdubois.be/installing-bose-quietcomfort-35-linux-mint-18/ (In this report it is used on the A2DP source however, in our case it's the A2DP sink).
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

I added a section about this in the Wiki: https://github.com/nicokaiser/rpi-audio-receiver/wiki/Bluetooth-troubleshooting


Exception (handled) in TextMate TokenizerThread on repeated LoadDiffContent()

For large Diff contents, calling LoadDiffContent() repeatedly in quick succession (for example, quickly toggling "Ignore Whitespace Change" a few times) can cause a NullReferenceException inside UpdateTokensInRange() in TextMateSharp.Model.TMModel.TokenizerThread (probably because TextEditor content is reloaded while TokenizerThread is still doing work).
However, this exception is handled by try-catch around RevalidateTokens() and causes a Debug.WriteLine() before moving on. That's probably OK in Release builds, but will cause a halt when debugging (it's possible to continue debugging, though).
If this is deemed to be OK, then this issue can be closed. Just wanted to flag this behavior, for future reference.

I think this ISSUE should be reported in the [AvaloniaText] (https://github.com/AvaloniaUI/AvaloniaEdit/issues) project.


Drop the redundant r from the definition of Parser

Currently it's impossible to use Parser in a monad-transformer stack. In cases like the following:
type MyParser s b m a = StateT s (Pipes.Parse.Parser b m) a

the compiler complains with:
Type synonym ‘Pipes.Parse.Parser’ should have 3 arguments, but has been given 2

So I suggest to remove the redundant r from the definition of Parser:
- type Parser a m r = forall x . StateT (Producer a m x) m r
+ type Parser a m = forall x . StateT (Producer a m x) m

Of course, it's possible to work around the issue by expanding the type synonym in place, but it's still an issue.

This doesn't work (the library won't compile if you delete the r on both sides), because now you're universally quantifying a higher-kinded type, which is almost always not going to behave well.
The reason this causes problems is that if you write:
Parser a m r

... the compiler will expand  it to:
(forall x . StateT (Producer a m x) m) r

... which is not the same thing as:
forall x . StateT (Producer a m x) m r

Sorry. My bad.

No problem at all! :)


CHANGELOG.MD: Move update responsibility to repo maintainers?

I'm sure this has been discussed elsewhere previously, but I wanted to see what people think about changing the repo responsibilities so that the repo maintainers have to update the CHANGELOG.MD, not the people submitting Pull Requests. We often get in a situation where a handful of PR's have been approved via code review, but only one can be merged at a time since the changes from one merge cause the other PR's to require a rebase. I propose changing the requirements so that the person submitting the PR must put a detailed change entry in the PR itself, but all changes to the CHANGELOG would be done by maintainers, in separate Pull Requests. Thoughts?

Tagging @PlagueHO as the co-maintainer of this module. And also @johlju since he maintains a number of modules himself.

I missed this one and actually commented on this elsewhere.
If you add the each change just under the # Unreleased header then this issue dosesn't occur as often because git can usually fast-foward changes like that.
This actually makes more sense from a chronological perspective (but not at first) - because you'd expect older changes to be closer to the bottom of the file while the most recent changes to be at the top.

Ok. Maybe we should update the Pull Request template then to say that the changelog entry must go directly underneath the Unreleased section?

We'd probably also need to update the contribution document as well. Might be worth raising this issue over in DSCResources repo instead?

Sounds good. Also, just for my understanding, are you saying putting entries directly under "Unreleased" would eliminate the need for a rebase, or would eliminate merge conflicts when doing a rebase? My intention here is to eliminate the need for a rebase, not just to make rebasing easier.

It should eliminate the need for the rebase I think because Git will be able to automatically update without a merge conflict. I could be wrong though.

Right, but it still causes the Pull Request to have to go through Continuous Integration again, which adds another hour before it can be merged. And that's if there aren't other Pull Requests in a similar state, in which case you'll wait a minimum of an hour for each PR. I would like to eliminate this 'Pull Request Queuing' where we keep having to do new commits, and as a result, new tests, just to keep the change log up to date.
Also, don't you have to manually hit the Update button to begin the auto merge?

You do have to hit the update button. But I think the reality is that we're always going to need a process to do that. Fundamentally the CI must run against the "merged" branch prior to performing the merge. Otherwise we'd likely end up with broken builds in Dev more often.
Perhaps there is an option in AppVeyor to terminate CI runs when a newer commit is present? This is an option in Azure DevOps. This would eliminate some queues.
Although, in reality we're not going to have quite the volume of PR's going through this repo once we've finished cleaning it up. Or at least I'd assume we won't.

Yeah again, the problem I have isn't really with needing to hit an update button. It's just that we're forcing additional hours upon PR's that are otherwise ready to merge, just because of changed code in a file those PR's weren't even necessarily trying to fix in the first place. I think it would be better if the Pull Requester only ever had to do rebases on files they were specifically updating, and the maintainers could keep the change log up to date separately.
Not sure if it's possible, but with the changes @johlju made recently, we also might be able to configure Appveyor.yml to only execute the Meta tests (and skip the Unit and Integration tests) when a PR that only modified the .MD files was made. That would make it a lot quicker for a maintainer to keep the changelog up to date.
I agree that PR's may not always be queuing like this, but I think any streamlining we can do of the process is a win. Especially when in repos that take 40+ minutes to runs all tests.
Another benefit of having maintainers keep the change log up to date would be that it would be easier to keep a consistent format throughout the file.

Perhaps there is an option in AppVeyor to terminate CI runs when a newer commit is present? This is an option in Azure DevOps. This would eliminate some queues.

That was just addressed in #569 so I think we're good there.

I think I'd rather avoid having to keep the CHANGELOG up-to-date myself for every change as we'd still need to track change in DEV somehow - someplace. I'd love consistency with the CHANGELOG.MD but from what I've seen there isn't any consistency across repos anyway - even with the instructions we provide.
I'd also worry that if a maintainer wasn't around to update the CHANGELOG.MD prior to monthly release then the module would get omitted or worse, released without an updated CHANGELOG.MD.
The thing I try to consider when thinking about changes like this is that it affects 10s of repos and incurs a lot of change across the board - which is most likely not going to get picked up everywhere.

Not sure if it's possible, but what about if we could configure Appveyor.yml to perform this sort of logic:
-If the immediately prior commit for this PR has run and passed all required tests
-And if the current commit is only modifying a .MD file
-Then only run Meta tests
Would you be open to that? That would speed up the process as well.

I rather not update the change log monthly, that would just be to much work. If we do something like this, we should update release notes and use the GitHub releases instead somehow (automatic). Not possible I think.
I don't see this as a big problem. 🙂 I usually wait until next day and merge next PR if i could resolve the conflicts for the contributor (and let the tests run).

And if the current commit is only modifying a .MD file

You can add a 'skip CI' in a commit message and the entire CI is skipped. There is some control around skipping CI on certain files, but I think then they are always skipped.
The logic you suggest above must be coded I think.

Sounds like I'm the only one that thinks this is a good idea, so I'll go ahead and close out for now.


Keywords file and override

Pull out all the keywords into a separate file. There's probably a better word for this, but examples include:

by
next post
previous page

Putting this into a file enables us to then provide overrides in the options. This could be useful if someone wants to have their blog be in a different language, and don't want a bunch of English words appearing everywhere!

I've also included some arrow symbols (→) in the text as well, since I think it looks good. Other people might have different opinions, and this functionality could also be used to remove the arrows.

@deer Im going to look into a solution for this today


Pretty Differ JS

Pretty Differ with scala-js support.

Closing in favor of https://github.com/scalatest/scalatest/pull/1027


Report the number of tests in result

julia> include("runtests.jl")
Test Summary:
outer    |  Pass: 8/8 (100.0 %)
  inner1 |  Pass: 4/4 (100.0 %)
    d    |  Pass: 1/1 (100.0 %)
  inner1 |  Pass: 4/4 (100.0 %)

Current coverage is 58.53%

Merging #1 into master will not affect coverage as of 50737ac

@@            master      #1   diff @@
======================================
  Files            3       3
  Stmts          123     123
  Branches         0       0
  Methods          0       0
======================================
  Hit             72      72
  Partial          0       0
  Missed          51      51

Review entire Coverage Diff as of 50737ac

Powered by Codecov. Updated on successful CI builds.

You could even get rid of Pass: , or make it a heading?

I should expand: what I was thinking was simply display the proportion of passing tests (even when there are test fails, as the proportion of failing is just redundant information). I also agree with Jake that you don't need percentages. So I was thinking something like:
Test set | Passing
==================
outer    | 8/8
  inner1 | 4/4
    d    | 1/1
  inner1 | 4/4

You also want some way for the reader to quickly identify which sets have failed. I guess some sort of colour?

or even a bar graph using block elements?

that seems even more useless than printing the % :-)

Yeah, I'm not convinced it would be a good idea, but visually it should be quicker to scan through than looking at percentages.

Headings get tricky if you have, e.g. 0 passing tests, you have to walk the whole tree to get totals first, and so on. I'll think on it

I meant have the heading be always Passing. So if all tests failed you would have
Test set | Passing
==================
outer    |  0 / 8
  inner1 |  0 / 4
    d    |  0 / 1
  inner1 |  0 / 4

Oh I see what you're saying. Interesting. I'll explore.
I'm not going to merge this, but I'll incorporate the original suggetsion, just without the %


CSS modules migration: < SectionName />, < RelatedComponent />, < RelatedComponents />

Monday ticket
CSS modules migration guideline

@SergeyRoyt Please assign this to me

Assigned to you! 😉

Resolved, thanks to @Kritik-J !


Adjust header in output file

From some research, it looked to me that the pertinent part of the name in the header was the "Seita.9G099800" part, so I wanted to split that from the rest. First, see if the header is longer than one element and then isolate the "Seita.9G099800" portion:
if len(header.split()) > 1:
                first_elem = header.split()[0]
                name = '.'.join(first_elem.split('.')[:2])

If the header is just one word, simply assign the header to the name and put that in the output_file:
else:
   name = header

output_file = args.pdb / f"{name}.pdb"

Please let me know if this is satisfactory, or if you had something else in mind.

I agree that having space seperated text might not be optimal. However, I don't think having . as a separator is conventional either. Better to just do header.split()[0] generically imo.

@dawsonhunt Thanks for your contribution! Do you want to update the PR or shall we abandon?

I'll close it for now but happy to re-open and revise in the future!


Throwing eye of ender is not prevented

Seems like https://github.com/CivClassic/SimpleAdminHacks/commit/bb72921ee995456ca087d50db2addbd302bcbf63 didn't work, further investigation reveals that throwing an eye of ender does not call a ProjectileLaunchEvent at all. Need to cancel via PlayerInteractEvent instead

Adressed by https://github.com/CivClassic/SimpleAdminHacks/pull/15


Rename 'proto' to 'nanopb_proto'

This fixes #845 and allows proto-plus-python  to be installed on the system without causing any conflict with nanopb.

I'm not sure I like this.
I think it would be better to have one common structure of Python packaging of nanopb, namely, the way pip install nanopb does it currently: installs as a package called nanopb.

you mean changing nanopb_proto to nanopb?

No. Instead of renaming any of the source directories, build up the directory structure in CMake installation.

ah ok, got it! I'll look into it

I think to start with, it would be useful if you can add a GitHub workflow to run some tests on the CMake and Conan installation methods. When they are totally untested, they'll just keep breaking with future releases.


Add files and edits

Adding Laps.py and Laps executable file along with updating ReadMe. Currently, running the .py file with something like 'python3 path/laps.py' might not work due to the directory pointing to the exec file. It may create the 'Laps-history.txt' file in usr/local/bin.

Merging


Tern on MacOS docker_run.sh command generates empty output.txt

Describe the bug
Tern on MacOS builds but docker_run.sh command generates empty output.txt
To Reproduce
Steps to reproduce the behavior:

git clone https://github.com/vmware/tern.git
docker build -t ternd .
./docker_run.sh workdir ternd "-l report -i debian:buster" > output.txt

Results in an empty output.txt file.
Error in terminal
020-01-28 19:25:51,509 - ERROR - rootfs - Command failed. getfattr: ./usr/bin/tee: Operation not sup
11:34

then a whole bunch of these getfattr operation not permitted

getfattr: ./lib/x86_64-linux-gnu/libc-2.28.so: Operation not supported
getfattr: ./run/utmp: Operation not supported
020-01-28 19:25:51,513 - WARNING - report - Error in loading image: Command '['/usr/lib/python3.7/site-packages/tern/tools/fs_hash.sh', '/hostmount/temp/3e5eb770a25e8700e63a79e57e4cb51837589f72410afe73254eccdf19094040/contents']' returned non-zero exit status 1.
2020-01-28 19:25:51,515 - WARNING - run - Cannot retrieve full image metadata
2020-01-28 19:25:51,516 - DEBUG - run - Teardown...
2020-01-28 19:25:51,539 - DEBUG - rootfs - Running command: rm -rf /hostmount/temp/mergedir
2020-01-28 19:25:51,544 - DEBUG - rootfs - Running command: rm -rf /hostmount/temp/workdir
2020-01-28 19:26:01,253 - DEBUG - __main__ - Report completed.
2020-01-28 19:26:01,254 - DEBUG - __main__ - Finished

Expected behavior
Expected an output.txt file with a BoM of the Debian container.
 (Jan 22, 2020)
tern_log.txt

Operating System: MacOS Mojave 10.14.6

Container OS phone: 3.0 (per Dockerfile)

Python version (3.6 or higher)

Please attach files if they exist

tern.log
report.*

Closing this as a note about working on MacOS was merged at commit 0c1a7b03a8f1d94044e1b7d744765b9c4d92ba82


can not insert the content with image upload into Database, data is gone

I working with CodeIgniter. when I submit Image is gone but Video embed is still stored in database except image and the images and thumbnail data is stored in Directory but no data in MySQL Database.

How do you get a content from the editor? You should use editor.serialize() function.

@mrtawans have you solved this?
I'm having a similar issue, still browsing through closed issues to see if I can find a similar problem..
I can upload images but they are only stored as HTML content if I try to input something in MediumEditor after uploads.
Not sure if image insert is not triggering something right at MediumEditor.. must be some configuration error, I don't know :-/

@wkurosawa You can #254 for an example of the code which got it going for me.


Fix logs

ALL log messages regarding messages from p2p (not local things) should include the sender's node_id.

Fix bytes representations to something readable:
Failed sending HARE_PROTOCOL msg [123 129 185 230 148 211 148 26 48 31 95 93] to

In the log
could not get result for layer in range
there is
"error":"no result for the requested layer"
The word error should not appear

Block id is now a short string/id of 5 characters -- causes too collisions (in the logs) -- should be longer (12 char. ?)

"got new ATX" should include all possible information: similar to the info in "ATX published!" + other ATX fields (in particular `epoch_id').

fix JSON in starting build atx in epoch %v and re-entering atx creation in epoch %v

late hare messages (late preround / "contextually invalid message") should include the node_id that sent the message. "contextually invalid" is not a good name - should be "late" / "not in time" (if too early)

we have
sending message failed %!(EXTRA *service.DataMsgWrapper=&{true 6 1 [113 169 217 46 19 216 93 89 35 103 13 132 9 97 7 74 149 179 217 161 81 4 131 209 229 113 105 88 151 40 90 48]}, string= error: , *errors.errorString=connection was closed)
as well as
peer responded with nil to poet request DFjCnmocNHoa3Kyd16LWQpFTTcRZThP1CS6vuB8WvFEj%!(EXTRA []uint8=[113 169 217 46 19 216 93 89 35 103 13 132 9 97 7 74 149 179 217 161 81 4 131 209 229 113 105 88 151 40 90 48])
should fix the presentation to something comprehensible (in all relevant places)
(see also:
handle atx request {atx_ids %!s(zapcore.FieldType=15) %!s(int64=0) [ca1cfd21703c8ed26655722c3da2f37a009ec7aeabe2131140498422af57514a b1a56aa5afc2d523f7d1c907c88bd579ecaa29d5dbfaf947cbc9d06d84c19a67 d5b4af7d28cf9df9d8ef568e843a7544cd5a78d5a1760ee91971441d851a61c9 789885c3ac2307cad568ca9fa70de707dcb434b8353fe923f396cd1180ba8647 6c34150b8a2bd843246185c3b8f84a2f15424493ce4608c0ed25426db941026a  ] <nil>})

Reward calculated appears twice in each layer

Fix atx size %!s(int=18956)%!(EXTRA log.Field={atx_id 15 0 f6f9c <nil>}). It is better if this is part of the "ATX published!" log

Add epoch_id to "I've created a block"

unfamiliar atx was requested (id: %s), fix %s

Add duration to "finished PoST execution"

Any log about the initial post creation / proof root etc.?

the function CalcActiveSetSize should print the calculated active set size. Can write it under done calculating active set size

Fix the %s and <nil> here handle atx request {atx_ids %!s(zapcore.FieldType=15) %!s(int64=0) [361ee3710cf0c78cf84b23367dfb986d3ef9bc2b0076b2ac7fe54e86fafb890a] <nil>}

block created and block received should have associated ATX in short string.

already synced for layer appears every 10 seconds. Consider the benefit of printing it.

In the message Failed sending newBlock msg [22 91 102 90 183 144 70 218 165 121 166 12] to 6S3sSsvzYv4kb2oQLsbCHae2xS5GtLKU6JvTCMMfG6uP, reason=connection was closed the peer name is not the correct peer we failed sending the message to.

add epoch_id to the release tick log.

Blocks coming by fetching (as opposed to gossip) should have all the logs as in got new block. Currently some logs are under the start handle block log (in the handleBlock() function).

For dashboard purposes:

got new atx should have longer ids than 5 characters (atx_id, _sender_id etc.) to prevent collisions and displaying inaccurate information.

@lrettig if you're working on logs then you should be aware of this change I made a couple of months ago: https://github.com/spacemeshos/go-spacemesh/pull/1808
It makes many of our custom types implement the LoggableField interface which allows us to just include a variable in the log message and it will be formatted in a way that makes sense. I haven't converted any of the existing logs to use this mechanism, but we should do it gradually, as we update these logging statements. Let me know if you need help with this.

@noamnelke thanks for the heads up! That's exactly what I've been doing in #1952 - see for instance https://github.com/spacemeshos/go-spacemesh/pull/1952/files#diff-fbc8f466cd0cde2afe76fa37ca7ee514R174


What is the syntax to add multiple lint-cmd for different languages?

Issue
--lint-cmd doc:

Specify lint commands to run for different languages, eg: "python: flake8 --select=..." (can be used multiple times)

How can I specify lint-cmd for multiple languages? Which separator should be used?
Thank you for this awesome tool!
Version and model info
aider v0.50.1

Thanks for trying aider and filing this issue. This doc may be helpful:
https://aider.chat/docs/config/options.html#--lint-cmd
You can specify multiple --lint-cmd "python:pylinter" --lint-cmd "c:myfavclinter" etc.

I'm going to close this issue for now, but feel free to add a comment here and I will re-open or file a new issue any time.


Adding a splash screen

Currently, we don't have a splash screen for our project it would be convenient to have so.

I am willing to work on this issue. Please assigned it to me.

Assigned for 3 days to @karanpatel2329

Uploading splash-screen.mp4
Here clip of Splash Screen.
I am unable to join slack. can you help me.


Enhance scalar validation to handle non-strings when paired with a regex predicate

Regarding: version 4
Issue: When using a regular expression predicate, if the scalar is not a string, the validation halts with an exception.
 Adjust the validation form from
(re-matches predicate scalar)
to
(and (string? scalar) (re-matches predicate scalar))

Fixed: version 5
(valid-scalars? [:foo] [#"a.c"]) ;; => false


K8SPS-171 - Uncomment expose options for haproxy, router and orchestrator

Closing since decided for the moment to not touch it.


Add typos to pre-commit config

Description
Related issue: #1005
Motivation and Context
How has this been tested?
Types of Changes

[x] Build related changes

Checklist

[x] I have read the contributor guide.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

I added the following directories and patterns to the exclude list, meaning typos will not check those.

rdmo/locale/.*
rdmo/.*_de.html$
rdmo/.*_es.html$
rdmo/.*_fr.html$
rdmo/.*_it.html$
testing/.*.json # contains german
testing/.*.xml # contains german

typos wants to change toggleDescandants to toggleDescendants in a few js files. Is that alright?

typos wants to change toggleDescandants to toggleDescendants in a few js files. Is that alright?

I still need a decision here. Should I rename these? CI/typos fails at the moment.

Sorry, yes, its fine.

Alright, will rename those.


get_eventbrite_events is coded with environment variable

add a variable to config.ini.example that gives number of days to use for past events.

Thanks. I believe you can push fixes into this PR. I don't recall the process but I'm pretty sure it's simple and will save from creating new PRs.

Yeah, I think it will include new commits in the same branch used for the pull request.
https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork
Using the development brand will work, but I don't believe it's the best practice.  Rather, you want to do git branch some-branchname and that way you can create a PR off that specific branch and it will be assoicated with the PR until it's deleted / closed.

You might adopt the flow used for the Chapter project, since it seems to be well vetted.
It has commands to also help stay in-sync with the "upstream" since other people could be making PRs that make overlapping changes with your branches and code.

https://github.com/freeCodeCamp/chapter/blob/master/CONTRIBUTING.md#2-contribute-to-this-open-source-codebase

Okay, I think I understand. It's essentially keeping a PR for one issue, and making commits to the one PR until it is merged or closed?

With Git, you typically work with branches when your doing anything. You can commit into the master branch, but that's usually frowned upon if you're more than 1 person and have a need for testing.
The dev, develop, development branch is just a convention. In fact, this main git repository doesn't have a development branch at the moment, just a master branch.
I've historically worked with both a master and develop(ment) branch, like with the HackGreenville repo because it's part of git-flow's pattern.  It's less necessary with GitHub's pattern.
You don't need it, but most projects will select a named, persistent branch where code or PRs are are merged into, like develop(ment). This allows you to be doing testing, QA, and such without impacting the dev teams ability to commit. You could call this branch anything. developers-playground would work just the same as dev or develop or development  since branch names have no meaning in git. master is also a convention to my knowledge. You could delete your master branch and call-it awesome and work off it as your persistent main branch just the same.
Developers are expected to sync up their branches with the "upstream" copies on a regular basis before creating new branches, and even while branches are open.
If you have a bug, then you create a branch for the bug. Usually you're branching off either master or develop.
If you have a feature, then you create a branch for it in the same way.  This allows you to keep things separate so if you're working on a feature and the project manager needs you to jump on a bug fix, then you simply create a new branch for the bug, fix it, PR or commit it, and then it's merged into the persistent branches (ex. develop and/or master).  All the while, your feature branch was not impacted and you can just switch back to it, sync up with any upstream changes, and pick up where you left off.
The more people you have working on a project the more you have to keep your branches in sync with the "upstream" branches into which everyone is pushing and pulling code.  Developers will usually adopt a "commit early and often" workflow because if people are writing code in isolation for a long time (hours, days, or weeks depending on the project) then the likelihood of merge conflicts increases.
Merge conflicts are when the same lines of code of code are changed by multiple people.  They are often a pain to resolve, so they are to be avoided whenever possible.  The more often you commit, merge, and pull the more in-sync the codebase becomes and the less frequently you'll have complex merge conflicts to resolve.
There are suggested patterns like a develop / qa / master pattern where the developers all branch off the develop(ment) branch. When code is ready to be tested you can do a release that merges code from develop to qa and then that qa branch can be pulled to a qa site/app where people can test it. All the while the developers can continue to commit code to develop without messing up the QA team and the master branch (usually the production code) also isn't impacted.
When code is tested then it can be merged into the master branch and there are different strategies to deploying the latest code to production. I'm on small projects and usually we just pull the master branch to the production server and it's live.  Others will create specific release tags and checkout the tagged release to production. Plus, there are way more advanced things to consider on deploying the larger and more complex the product or tech stack.
For your purposes as a developer, you should get in the habit of always creating a branch and not commit directly to persistent branches [usually called master and/or develop].  It will certain work the same to commit direct to master or develop as it would to create a branch and merge the branch into master or develop.
In the context of Github, when you create a branch it allows you to easy create a PR that specific to that branch. That way when you commit anything new to your branch it will update the PR when you push it to Github.
The branches would allow you to work on a number of things at once without them getting mixed up.
When you have branches open, then it's good/necessary to regularly be synchronizing with the upstream code base if/as there are relevant changes being made which might cause a merge conflict or cause your local environment to break due to changes others made to the code.
In our case, there's not a lot of development going on, but it's good to get in the habit of acting like you're on a big team. It will avoid a lot of problems, plus you'll be prepared for when you are on a big team.
Again, there are a lot of conventions on how to wrangle git code and branches.  Github pull requests are unique to GitHub. I've actually used the "git-flow" conventions for years and command line tool, because we didn't use Github.  It's has similar results, but without the PR requirement and GitHub tooling.
So, before your next PR, do something like in Step 2 of the Chapter workflow., which works off the master branch and doesn't have a "develop" branch pattern.

Okay, that is an awesome explanation of that, and super helpful!
I've been working on a development branch but never understood the whole picture of why and how to manage the branches. Although I don't fully understand having a remote/upstream to the main (ie: codeforgreenville) repository, but I likely just need to read it a second or third time.
Thanks so much, Jim, this really is invaluable!

This CFG repo would be the "upstream".    So, origin master means your Github copy.
You add an "upstream", again the this name is convention and you could called it "ducky" and then you sync up between your fork's copies and the upstream (repo).
Step 2.2 of the Chapter contributing docs talk about adding an upstream to your local dev environment
If you're working for a company, the upstream would be the company's core repository and ever developer would have a fork.
If you're not using Github, then it's possible just to give people write permissions to an origin repo and people push and pull branches into that single origin, with no upstreams or forks.  Though, the GitHub methodology of forks, PRs, and upstreams is who GH does things and is really a benfit for open-source projects because anybody can contribute a suggestion (via a PR) without needing read or write permissions to the origin / base repo.  They simply fork it (essentially cloning, but a cloning to a personal copy of the original repo).

Ooh I see. So the company's or, I'll say Codeforgreenville's remote is just used to sync up your own branch with the original?
Also, this pull request should be good for Problem 3 in Issue #31
Let me know if I'm mistaken though!

This repo, https://github.com/codeforgreenville/upstate_tech_cal_service/, is just the one we're using as the main one.  It's master branch is where the production code lives for the website.
One of the benefits of a fork is it's pretty easy to switch your local git configuration to any remote repository as an origin.
 At that point, they would set your fork/copy as their "upstream" and it would take the role of this repo as the agreed upon central codebase for production, testing, and such.
We could also go to the live website and change the code to point at your fork's remote URL, pull the code, and it would immediately be using your copy.
So, a lot of things in Git and the workflow are implied based on what people agree upon.
In this case, we agree to create pull requests against https://github.com/codeforgreenville/upstate_tech_cal_service/ based on forked copies. That prevents having to give dozens of people write access to the "production" codebase and it allows for visual peer review of the code by someone, or everyone, and then the people with the permission to write to this repo can "merge" a branch of code into the repo by merging a pull request.
It's possible to do all of this without GitHub.  I could go to the command line and set your remote repo's URL  as an "upstream" an call it ramona
git remote add ramona https://github.com/ramonaspence/upstate_tech_cal_service/
git checkout master
git merge ramona xyz

Cool stuff!

I've squashed and merged this PR.
Squashing takes the 3 commits you had and smashes them into 1 commit into the master branch.
I had one small suggestion, but I'll post that on #31


autodiff statefulness

Bug Report
This is in reference to the wiki entry https://github.com/stan-dev/stan/wiki/Automatic-Differentiation-API. I know it says the instructions don't apply to the develop branch so I found ways to make it work anyways, then I came across this when trying to simply use stan as an autodiff library in C++. The changes I needed to make were
using stan::math::var;
using stan::math::recover_memory;
var x = 1;
recover_memory();

instead of
stan::math::var x = 1;
stan::math::recover_memory()

Version
822ab42d0
Description
The gradient is incorrect if independent variables of type stan::math::var are reused. The output changes from one wrong value to another wrong value if recover_memory is called in between calls. Things work fine if no var is reused or if only the dependent var is reused.
Steps
A minimal working example that can be compiled according to the instructions at https://github.com/stan-dev/stan/wiki/Automatic-Differentiation-API#basic-usage
#include <stan/math/prim/arr/meta.hpp>
#include <stan/math/prim/mat/meta.hpp>
#include <stan/math/prim/scal/meta.hpp>
#include <stan/math/rev/scal/meta.hpp>
#include <stan/math/prim.hpp>
#include <stan/math/rev.hpp>

#include <iostream>

using std::cout;
using std::endl;
using stan::math::var;
using stan::math::recover_memory;

template <typename T1, typename T2, typename T3, typename T4>
void print(const T1& x, const T2& mu, const T3& sigma, T4& z, const std::vector<double>& gradients, const std::string& msg="")
{
    std::cout << msg << std::endl
              << "z:       " << z.val() << std::endl
              << "x:" << x << endl
              << "mu:" << mu << endl
              << "sigma:" << sigma << endl
              << "dz / dx: " << gradients[0] << std::endl
              << "dz / dmu: " << gradients[1] << std::endl
              << "dz / dsigma: " << gradients[2] << std::endl;
}

template <typename T1, typename T2, typename T3, typename T4>
void gradient_reuse(const T1& x, const T2& mu, const T3& sigma, T4& z, bool recover=false)
{
    std::vector<var> independent_vars{x, mu, sigma};
    std::vector<double> gradients;
    z.grad(independent_vars, gradients);

    // if memory not recovered, 2nd gradient is wrong
    // if memory recovered too early, a 2nd call to the gradient sometimes leads to a segfault
    if (recover)
        recover_memory();

    print(x, mu, sigma, z, gradients, std::string("reuse with") + (recover ? "" : "out") + " recover");
}

void gradient_new(bool recover=true)
{
    var x = 1.0, mu = 0.0, sigma = 1.0;
    var z = normal_log(x, mu, sigma);

    std::vector<var> independent_vars{x, mu, sigma};
    std::vector<double> gradients;
    z.grad(independent_vars, gradients);

    // if memory not recovered, 2nd gradient is wrong
    // if memory recovered too early, a 2nd call to the gradient yields a segfault
    if (recover)
        recover_memory();

    print(x, mu, sigma, z, gradients, std::string("new with") + (recover ? "" : "out") + " recover");
}

void test_suite(bool recover)
{
    var x = 1.0, mu = 0.0, sigma = 1.0;

    // everything should work as expected
    gradient_new(recover);
    gradient_new(recover);

    // first call should give same result as above
    var z1 = normal_log(x, mu, sigma);
    gradient_reuse(x, mu, sigma, z1, recover);

    // x, mu, sigma are reused => gradient is off
    var z2 = normal_log(x, mu, sigma);
    gradient_reuse(x, mu, sigma, z2, recover);

    // reuse z2 but not x, mu, sigma => gradient OK
    var x2 = 1.0, mu2 = 0.0, sigma2 = 1.0;
    z2 = normal_log(x2, mu2, sigma2);
    gradient_reuse(x2, mu2, sigma2, z2, recover);
}

int main()
{
    // if gradient is incorrect, the values differ depending on
    // whether memory recovered between calls
    test_suite(false);
    test_suite(true);
    return 0;
}

Output
new without recover
z:       -1.41894
x:1
mu:0
sigma:1
dz / dx: -1
dz / dmu: 1
dz / dsigma: 0
new without recover
z:       -1.41894
x:1
mu:0
sigma:1
dz / dx: -1
dz / dmu: 1
dz / dsigma: 0
reuse without recover
z:       -1.41894
x:1
mu:0
sigma:1
dz / dx: -1
dz / dmu: 1
dz / dsigma: 0
reuse without recover
z:       -1.41894
x:1
mu:0
sigma:1
dz / dx: -3
dz / dmu: 3
dz / dsigma: 0
reuse without recover
z:       -1.41894
x:1
mu:0
sigma:1
dz / dx: -1
dz / dmu: 1
dz / dsigma: 0
new with recover
z:       -1.41894
x:1
mu:0
sigma:1
dz / dx: -1
dz / dmu: 1
dz / dsigma: 0
new with recover
z:       -1.41894
x:1
mu:0
sigma:1
dz / dx: -1
dz / dmu: 1
dz / dsigma: 0
reuse with recover
z:       -1.41894
x:1
mu:0
sigma:1
dz / dx: -1
dz / dmu: 1
dz / dsigma: 0
reuse with recover
z:       -1.41894
x:1
mu:0
sigma:1
dz / dx: -2
dz / dmu: 2
dz / dsigma: 0
reuse with recover
z:       -1.41894
x:1
mu:0
sigma:1
dz / dx: -1
dz / dmu: 1
dz / dsigma: 0

Expected Output
The expected output for a single run is
z:       -1.41894
x:1
mu:0
sigma:1
dz / dx: -1
dz / dmu: 1
dz / dsigma: 0

The two cases that don't match the expected result are the 2nd runs that the reuse the variables
    var z1 = normal_log(x, mu, sigma);
    gradient_reuse(x, mu, sigma, z1, recover);

    // x, mu, sigma are reused => gradient is off
    var z2 = normal_log(x, mu, sigma);
    gradient_reuse(x, mu, sigma, z2, recover);

Note that without recover_memory(), dz / dx: -3, while with recover_memory(), we have dz / dx: -2
Additional Information
In my original test that had all this in one big function, I observed segfaults if recover_memory() was called twice. The problem went away in this minimal working example but I guess this is just by chance.

@fredRos, thanks for the detailed info. Just wanted to let you know that I saw it, I've assigned myself, and will look at it. (won't have time until next week -- we're trying to get a release out and work on some of the interfaces for the rest of the week)

Thanks for the careful report --- we really appreciate code examples.  I'm going to close this issue, because while it's not an ideal design we have, it's also not a bug according to our intended usage.
If you have a reproducible example where recover_memory() segfaults, please open another issue with that example.  It shouldn't segfault no matter how you call it.
As for the autodiff lib, the var instances aren't intended to be reused.  They're just lightweight pointers to vari instances. The intent is that recover_memory() is called after the derivatives are extracted after each use.  Any other use is going to mess up any existing variables you had because derivatives will get propagated twice.  Although not ideal, it's a consequence of the design, not a bug.
What we're really hoping is that everyone uses our encapsulating functionals, which don't have any of these issues with using the raw autodiff.
We have a paper that we're about to release on how the autodiff works end to end and we'll be revising the Wiki to match. The best way to see how it's intended to be used is in the deifnition of functionals like gradient() and hessian().  If you want the paper, just send me an e-mail at<EMAIL_ADDRESS>and I can send you a draft.
I don't understand why the using statements would give you different answers, so presumably that was just for convenience.

Thanks for the quick reply. I will send Bob an e-mail to get the
draft. If the wiki is updated to document this rather surprising and
not very convenient behavior, then there should be no problem for
those who read the manual carefully.
I know very well how the functional approach make life easier for the
library developers. But sometimes state helps to reuse
results. Suppose I needed gradients wrt. y of a multivariate normal
N(y|mu, Sigma) and the Sigma is fixed. Then I guess you'd have to
invert, Cholesky decompose ... Sigma each time I need the
gradient. This is what I could get around if I use the autodiff
library manually.  Do you memoise these things internally? Or is it
just recomputed every time?
As for the using statements: sorry about the confusion. The code
compiles fine without
using stan::math::var;
using stan::math::recover_memory;

and instead
stan::math::var z =...
stan::math::recover_memory()

And regarding the segfault, I created a new issue #1478. It might be related
to the double use of variables.

Do you memoise these things internally?

Essentially.  If the covariance matrix is filled with vars
then we’ll decompose it and push the autodiff through
the decomposition, but if it’s filled with doubles then
we’ll only invert.  And the inversion can be avoided
by using the multi_normal_cholesky distribution which
takes in the Cholesky decomposition directly.
But you can do a similar trick inside any functor to
reuse any intermediate results while still benefiting
from the encapsulation.


Added resizing to channels to get them to match for ST

Overview

Style Transfer requires all of the channels to be of size 3 as the network depends on this.

Solution

Calling the resize method in image_utils get's us this functionality
It was added upstream in the data loader because that's where the data for the style transfer model is prepared.

Fixes #2720

This won't work for ARGB, since resize_image only supports pair-wise conversions among Grayscale, RGB, and RGBA (https://github.com/apple/turicreate/blob/master/src/core/data/image/image_util_impl.cpp#L55). While not a 6.0 blocker, could you:

Open an issue tracking the lack of support for ARGB image format,
Add guidance in our Userguide for (at least) Style Transfer on what users should do if they have an ARGB image (maybe give them a code snippet or a task-based procedure to convert it to a format we support)

I'm not sure what you mean. The function does convert RGBA to RGB, and we don't support ARGB layouts anywhere.


Could support kerberos hdfs?

Could smart_open read kerberos hdfs data?

I cannot answer that question definitively. Are you able to try it and find out for yourself?


fix OVCasualLM model inference without generate

What does this PR do?
fix position_ids initialization for first inference stateful models

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Handle cases when DisplayMetrics report incorrect xdpi and ydpi

Expected behavior
Images get scaled properly even if the device reports incorrect xdpi and ydpi by using the device's density as a comparison.
Actual behavior
Due to missing checks, the scaling of images is very small.
Steps to reproduce

Grab a Nokia 6.1
Install any custom OS like LineageOS: Website, GitHub, Downloads in my case.
Notice that the device reports incorrect xdpi and ydpi while rest information is correct.

Affected devices
Nokia 6.1, 420 DPI, Custom OS only
Affected images
Any images or apps that use this library are affected. Apps like Tachiyomi, Sync for Reddit, Boost for Reddit are notable examples.
Information reported by the custom OS on the affected device
DisplayMetrics{density=2.625,width=1080,height=1920,scaledDensity=2.625,xdpi=4.031,ydpi=4.031}

Expected fix
Use the device density as a condition to compare the reported xdpi and ydpi before scaling the image and use the best one possible.

Relevant Issue: https://github.com/davemorrissey/subsampling-scale-image-view/issues/505
I opened an issue for this in Tachiyomi as well which is an affected app: https://github.com/inorichi/tachiyomi/issues/4131

This a bug in the custom OS, has it been reported to them? Any app that uses xdpi or ydpi will be broken by this so it seems better to fix the root cause.

I won't say that this is a custom OS issue but a device firmware issue. Other than mine, none of the other devices I am aware of are affected but again this is also a fact that the only device from Nokia that is supporting custom ROMs right now is mine. I noticed some other devices overriding framework values to report an expected xdpi and ydpi:

Cristian0808/halium_device_samsung_gtexswifi

Then there are devices that are using emulator density property to fix this issue:

https://github.com/naobsd/cm_device_rockchip_rk2818/commit/9d360199c1ed2d0f3430858a1acb6471166905c1

You can notice that in the last commit, the date is from 2011, so I can say that this issue exists for a way long time in devices running custom OS.
For now, I have also decided to use the emulator property to set DPI which overrides the value in the framebuffer and makes the apps using the xdpi and ydpi values works but again it is better to have a fallback in the library in my opinion?

https://github.com/LineageOS/android_device_nokia_PL2/commit/674cca945c3a7c3c4b33a0b02e957230e361a18c

Hence, closing this issue.


Remove broken urls from free-courses-ru.md

What does this PR do?
Remove resource(s)
For resources
Description
Removed resources which are not available now. Status:404
Why is this valuable (or not)?
The resources are now not available for use. This will enhance the repo by displaying only available resources.
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

that's quite a few links. Thanks!

that's quite a few links. Thanks!

Yes, I basically targeted the resources which are not available now (404 Status Code), and excluded other cases. How should I proceed with other changes now? Whether I should remove all the resources which range from 400 (Not available or forbidden to access) to 500 status codes (They might be available but the server is currently not able to handle those requests.)

404s are more reliably bad and easier to double check. I would encourage you to work on them first. But do them in easy-to-review chunks - maybe 10 at a time?


Select code block not working fine when the code is folded.

When a code block is folded it is expected to skip the code within the block and select that code block all at once. But when we're trying to do the same it's going through every line within the folded block and selecting it and therefore it's giving a feel that the selection is not working fine or it's stuck.

VSCode Version: 1.33.0
OS Version: Windows_NT X64 10.0.17134

Does this issue occur when all extensions are disabled?: Yes

Can you add a code sample and steps? Please name where the cursor initially is and the name of the commands you execute ( expand selection)

For example, consider folding this code below. Place the cursor at the bottom of the code and try to select the code using the CTRL + SHIFT +  LEFT ARROW KEY in windows.

                                                <button
                                                    type="button"
                                                    class="account-avatar border-primary btn btn-white dropdown-toggle rounded-0"
                                                    data-toggle="dropdown"
                                                    aria-haspopup="true"
                                                    aria-expanded="false">

                                                    Abhishek Prakash
                                                </button>

                                                    Shade Solutions.

                                            <form class="searchform">
                                                <input class="form-control form-control" type="text" placeholder="Search here...">
                                            </form>

Messages

You should use Shift + Alt + Right Arrow Key. This work on me.

Im not sure if i get it right.


Can't set up LND on Mac

Background
I'm trying to set up LND on my Mac
Describe your issue here.
I can't set up lnd on my system
Your environment

version of lnd
Latest Version
which operating system (uname -a on *Nix)
Mac
version of btcd, bitcoind, or other backend
Latest Bitcoind
any other relevant environment details

Steps to reproduce
Tell us how to reproduce this issue. Please provide stacktraces and links to code in question.
bitcoin.conf
server=1
Network Options
testnet=1
[testnet]
RPC Options
rpcport=18443
rpcauth=bitcoinrpc:ac4c865bceeee79a79d367387f8dd1ea$b1c714b0fd17ff25c67313ee33eaa889a4bccb72b1c9e3782b8860109fb2b856
ZMQ Options
zmqpubrawblock=tcp://<IP_ADDRESS>:28332
zmqpubrawtx=tcp://<IP_ADDRESS>:28332
Set fallback fee for every transaction
fallbackfee=0.00072
lnd.conf
[Bitcoin]
bitcoin.active=1
bitcoin.testnet=1
bitcoin.node=bitcoind
[Bitcoind]
bitcoind.rpcuser=bitcoinrpc
bitcoind.rpcpass=y6Cmqpo0UattZkMb4w-5aVAVqPNDgeJASxm8Qn83TC0=
bitcoind.zmqpubrawblock=tcp://<IP_ADDRESS>:28332
bitcoind.zmqpubrawtx=tcp://<IP_ADDRESS>:28333
Expected behaviour

Lnd should be running

Actual behaviour

error creating wallet config: unable to create partial chain control: status code: 401, response: ""

Resolved it, Bitcoin Core wasn't running with my authetication


place all pages in the same intermediate output directory

Description
The isolation is unnecessary and we can reuse files when we share directories
Testing Instructions
Open multiple pages without client-side navigation in multiple tabs concurrently.

Non-determinism in graph traversal need to be fixed first before merging that


Bluetooth: controller: Fix disabling LE Encryption support

Symbols without prompt cannot be configured from application configuration file.
warning: BT_CTLR_LE_ENC (defined at subsys/bluetooth/controller/Kconfig:198) was assigned the value
'n' but got the value 'y'.  This symbol has no prompt, meaning assignments in configuration files
have no effect on it. It can only be set indirectly, via Kconfig defaults (e.g. in a
Kconfig.defconfig file) or through being 'select'ed or 'imply'd (note: try to avoid Kconfig
'select's except for trivial promptless "helper" symbols without dependencies, as it ignores
dependencies and forces symbols on). You can check symbol information (including dependencies) in
the 'menuconfig' interface (see the Application Development Primer section of the manual), or in the
Kconfig reference at http://docs.zephyrproject.org/reference/kconfig/CONFIG_BT_CTLR_LE_ENC.html
Signed-off-by: Szymon Janc<EMAIL_ADDRESS>

Codecov Report

Merging #9094 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #9094   +/-   ##
=======================================
  Coverage   52.42%   52.42%
=======================================
  Files         199      199
  Lines       25034    25034
  Branches     5236     5236
=======================================
  Hits        13125    13125
  Misses       9789     9789
  Partials     2120     2120

Continue to review full report at Codecov.

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

we also have option to disable SMP, if we have SMP disabled there is no point in having encryption support in controller


Update Akropolis Space

Hi! What is your PR about?

[x] Add images for your space
[ ] Add custom domain for your space
[ ] Add alias for migrate your space
[ ] Add or edit a skin
~Edit your space with GitHub?~ (deprecated) Please migrate your space to ENS https://docs.snapshot.page/spaces/migrate
~Create your space with GitHub~ (deprecated) Create your space with ENS instead https://docs.snapshot.page/spaces/create

@AlexanderMazaletskiy Could you open 2 PR, one for editing your existing space and another one to create your new space with ENS? Thank you.

Closing this PR for now, feel free to open it again once you've done the changes.


Added more device types

keykoard really? 😄

Yea, I have some really awful 3rd party keyboards that are "USB Keykoard".


New version: MusicBrainz.Picard version 2.70000.0

ARP entries are correct.
Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 1113
Microsoft Reviewers: Open in CodeFlow

Did they change their versioning scheme? Or is it just this one?


[TASK] Only setup neos with neos distributions

If this distribution is a flow distribution, it will not have the Neos packages.
So, only setup Neos if this is a neos distribution.

:+1: by reading


Support storing into a specific list

I am happy to see somebody already started the work I wanted to do 😊
(create an opensource OneTab, with additional features; because OneTab is not updated since a year and there is no way to contact the author or to contribute to the project).
But better-onetab lacks an important feature: being able to send the tabs to a specific list, by name, or (less important) to a new named list.
E.g. having a list "funny articles" with some entries, I would like to quickly add a link/tab to it, like:

click the extension icon to show the simple list popup
click a store-in-this-list icon (by default stores selected-tabs; alternatively allows to store all-tabs-in-window, tabs-to-right, tabs-to-left)

rather than:

storing the selected tab
go into better-onetab tab
drag'n'drop the new tab into my "funny articles" list
close better-onetab tab

Ideally the simple-list would allow the most useful operations over existing lists, and allow to create a list with a specific name.
Let me know if it makes sense to you, if you want to add it in the roadmap, and if I can eventually help with implementing this (I see you use VUE, and I was actually interested in learning it; so could be a good opportunity 😉).

Hi,
This was in my roadmap for a long time (I wrote it on the projects page as Chinese :joy: ). Because I usually make the feature mentioned by users or fix bugs first, I lay it aside to now. It is very nice if you are willing to implement it.
There are two ways in my idea.

Add it in the context menu similar with the way to implement of onetab.
Add a button on every item in the simple list.

I am not sure which way is better and easy to implement, but I hope both of them could be implemented finally.
Both of them need to make some changes to the storeTabs method in src/common/tabs.js first to allow store tabs to a specific list.
For the first plan, it should make changes in setupContextMenus method in src/background.js and call it in the handler of storage changed event. The second need to make some changes to src/page/Popup.vue.
If you have any other ideas It is welcome to share them.
Thank you.

I've added this feature in v1.3.10. It is welcome to submit a new issue if there are any problems.


[FLINK-4534] Fix synchronization issue in BucketingSink

What is the purpose of the change
Fix lacking of synchronization in BucketingSink#close method.
Verifying this change
This change is a trivial work without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)

Documentation

Does this pull request introduce a new feature? (no)

lgtm

This PR has conflicts, I will fix soon.

This PR is ready for review again now.

Taking into account the last comment from @kl0u in Jira issue,
we can close this PR and create another if needed to remove all synchronized (state.bucketStates) in BucketingSink.


link: Update build script to include rpath into LC_RPATH

Add library path into LC_RPATH, don't need to update global rpath.
$ otool -lL callpy
Load command 16
          cmd LC_RPATH
      cmdsize 56
         path /Users/lijie/miniforge3/envs/py312/lib (offset 12)
...
 datasize 536
        @rpath/libpython3.12.dylib (compatibility version 3.12.0, current version 3.12.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1336.0.0)

Before:
 ./callpy
dyld[13582]: Library not loaded: @rpath/libpython3.12.dylib
  Referenced from: <FC4DE790-C3E6-305A-BD65-4FFB8CB042F8> /Users/lijie/source/goplus/llgo/_pydemo/callpy/callpy
  Reason: no LC_RPATH's found
[1]    13582 abort      ./callpy

After:
./callpy
sqrt(2) = 1.414214

Just easy to use, maybe not a good point.


How to control usage text width

Is it possible to control the width of the printed usage width. I've noticed that by default it doesn't usa all available screen size.

This is on the roadmap (#159) but not supported yet.
I just added some notes to that ticket with some thoughts on what functionality to provide and what the API for these could look like. Please take a look and let me know your thoughts. If you feel like providing a pull request, that would be great!

Sure thing, I'll do. Thanks.
(I've have a few other questions, is GitHub the proper place to place them?)

Oops, I saw your comment on #159 first and asked the same question twice. Sorry.  :-)
GitHub is fine for any questions/bug reports/feature requests. Go for it!

Do you mind if we close this ticket as a duplicate of #159?

No problem!


uwsc gets stuck seeking to SEEK_CUR then exits

I'm just using an ev_timer and sending a static/compiled string every 20 seconds.
Here's an strace of what eventually happens after about 10 minutes.
open("/dev/urandom", O_RDONLY|O_LARGEFILE) = 102
readv(102, [{iov_base="\226\234\325", iov_len=3}, {iov_base="\5{0mk\354~WF\333\307\227\307\352,\222\203\247\32\0030\5\204o\235\232n\242<\nR,"..., iov_len=1024}], 2) = 1027
_llseek(102, -1023, [0], SEEK_CUR)      = 0
close(102)                              = 0
rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1 RT_2], [], 16) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 16) = 0
rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1 RT_2], [], 16) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 16) = 0
rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1 RT_2], [], 16) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 16) = 0
rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1 RT_2], [], 16) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 16) = 0
_llseek(6, -285, [227], SEEK_CUR)       = 0
_llseek(99, -285, [227], SEEK_CUR)      = 0
_llseek(97, -285, [227], SEEK_CUR)      = 0
_llseek(95, -285, [227], SEEK_CUR)      = 0
_llseek(93, -285, [227], SEEK_CUR)      = 0
_llseek(91, -285, [227], SEEK_CUR)      = 0
_llseek(89, -285, [227], SEEK_CUR)      = 0
_llseek(87, -285, [227], SEEK_CUR)      = 0
_llseek(85, -285, [227], SEEK_CUR)      = 0
_llseek(83, -285, [227], SEEK_CUR)      = 0
_llseek(81, -285, [227], SEEK_CUR)      = 0
_llseek(79, -285, [227], SEEK_CUR)      = 0
_llseek(77, -285, [227], SEEK_CUR)      = 0
_llseek(75, -285, [227], SEEK_CUR)      = 0
_llseek(73, -285, [227], SEEK_CUR)      = 0
_llseek(71, -285, [227], SEEK_CUR)      = 0
_llseek(69, -285, [227], SEEK_CUR)      = 0
_llseek(67, -285, [227], SEEK_CUR)      = 0
_llseek(65, -285, [227], SEEK_CUR)      = 0
_llseek(63, -285, [227], SEEK_CUR)      = 0
_llseek(61, -285, [227], SEEK_CUR)      = 0
_llseek(59, -285, [227], SEEK_CUR)      = 0
_llseek(57, -285, [227], SEEK_CUR)      = 0
_llseek(55, -285, [227], SEEK_CUR)      = 0
_llseek(53, -285, [227], SEEK_CUR)      = 0
_llseek(51, -285, [227], SEEK_CUR)      = 0
_llseek(49, -285, [227], SEEK_CUR)      = 0
_llseek(47, -285, [227], SEEK_CUR)      = 0
_llseek(45, -285, [227], SEEK_CUR)      = 0
_llseek(43, -285, [227], SEEK_CUR)      = 0
_llseek(41, -285, [227], SEEK_CUR)      = 0
_llseek(39, -285, [227], SEEK_CUR)      = 0
_llseek(37, -285, [227], SEEK_CUR)      = 0
_llseek(35, -285, [227], SEEK_CUR)      = 0
_llseek(33, -285, [227], SEEK_CUR)      = 0
_llseek(31, -285, [227], SEEK_CUR)      = 0
_llseek(29, -285, [227], SEEK_CUR)      = 0
_llseek(27, -285, [227], SEEK_CUR)      = 0
_llseek(25, -285, [227], SEEK_CUR)      = 0
_llseek(23, -285, [227], SEEK_CUR)      = 0
_llseek(21, -285, [227], SEEK_CUR)      = 0
_llseek(19, -285, [227], SEEK_CUR)      = 0
_llseek(17, -285, [227], SEEK_CUR)      = 0
_llseek(15, -285, [227], SEEK_CUR)      = 0
_llseek(13, -285, [227], SEEK_CUR)      = 0
_llseek(11, -285, [227], SEEK_CUR)      = 0
_llseek(9, -285, [227], SEEK_CUR)       = 0
_llseek(7, -285, [227], SEEK_CUR)       = 0
exit_group(0)                           = ?
+++ exited with 0 +++

What's this all about?

This is just what happens when the example returns -1 on the wss connect function.


add getter for tbsResponseData and signatureAlgorithm on OCSP_BASICRESP

fixes #7081
I added some documentation as well, but please let me know if there's anything I've missed.

@reaperhulk thanks for supplying the pr for the missing getters. To fix the ci build failures, you need to run 'make update' on your local copy, which will add the two new symbols to libcrypto.num. Add the change as a fixup commit to your branch and push it to your github repo. (You don't need to amend your existing commit, the commits can squashed in the end).
diff --git a/util/libcrypto.num b/util/libcrypto.num
index d69a6dcf68..1506d632e6 100644
--- a/util/libcrypto.num
+++ b/util/libcrypto.num
@@ -4572,3 +4572,5 @@ EC_POINT_set_affine_coordinates         4525      1_1_1   EXIST::FUNCTION:EC
 EC_POINT_get_affine_coordinates         4526   1_1_1   EXIST::FUNCTION:EC
 EC_GROUP_set_curve                      4527   1_1_1   EXIST::FUNCTION:EC
 EC_GROUP_get_curve                      4528   1_1_1   EXIST::FUNCTION:EC
+OCSP_resp_get0_tbs_sigalg               4529   1_1_1   EXIST::FUNCTION:OCSP
+OCSP_resp_get0_respdata                 4530   1_1_1   EXIST::FUNCTION:OCSP

@mspncp thanks, done

While looking at OCSP_resp_find_status.pod, I noticed that OCSP_resp_get0_signature() is undocumented, too. While you're at it, would you mind adding docs for this function? (There may be even more, I didn't check systematically).

I noticed that was missing -- I'm happy to add it to this PR if you'd like or I can put in another PR after this.

Same pr is fine. I would leave it as separate commit and only squash the first two.

But feel free to do the rebasing and squashing yourself. It's only a small pr.

@reaperhulk, I added the 1.1.0 label for backporting.
Note: cherry-picking of docs to OpenSSL_1_1_0-stable normally fails, because the paths have been renamed. After increasing the merge.renamelimit to 32768 as recommended by git on the first failed attempt, the cherry-pick succeeds.
warning: you may want to set your merge.renamelimit variable to at least 16141 and retry the command.

I ask because I am not yet familiar with this, but given that this is a bugfix for 1.1.0 that should also got to 1.1.1, does it make any difference about symbol numbering to make the make update in the 1.1.0 tree and then cherry pick it to 1.1.1?
Or is this the preferred way?

@romen  my understanding is that (a) the numbers for the symbol numbers need to be equal if the symbols exist in both branches and (b) the symbols in 1.1.0 will in general be a subset of the numbers in master. Consequently, if you run make update in OpenSSL_1_1_0-stable, you will very likely get a collision with an already existing symbol on master. So IMHO it is better to run make update on master and cherry-pick to 1.1.0, not vice versa.
On the other hand, as @FdaSilvaYY pointed out, the third column indicates the version in which the symbol was introduced. So it is necessary to change it manually to 1_1_0<letter> if one intends to backport the symbol. (@levitte please correct me if I am talking rubbish).


feat(list): add icon support

r: @jelbourn
Avatars and icons need slightly different styling (icons need to be smaller). This PR adds support for default styling for icons.

LGTM


Include a catch all for the :accept handler

I don't think it's good practise to use catch all errors. by all means if you have seen a specific error we can handle then add that clause. but by default a completly unexpected return value is a reason to crash.
In the future we might use dialyzer to ensure that case clauses cover all outcomes.

True, but I cannot recall the specific error that was being thrown


Best multiple stream run practice(usage advice)

For my example of using lsquic library it's required to download sequentially pairs of web pair resources, but for the same hostname. So after downloading first 2 urls in parallel there is the next pair. Should I use the same created pair of "lsquic_stream"s? Or is it better after reading 0 bytes from http_client_on_read event, close used streams and create new ones for next pair of urls?

A single stream corresponds to a single HTTP request/response exchange.  You cannot reuse a stream in the fashion you describe.  If the next pair of URLs is for the same host, create new streams; otherwise, you will need to create a new connection.

Thanks for answer. That is what I was looking for.