Bug: Fixed responsiveness fixed in code preview tabs successfully issue 520

Pull Request Resolves [ #520 ]
Title: Fixed responsiveness fixed in code preview tabs successfully.
Description

In frontend, I used the react icons for creating the icons and converted the javascript to JS.
The design is responsive.

Related Issues
Fixes #520
Changes Made
Bug fixes: Fixed responsiveness fixed in code preview tabs.
Screenshots

I certify that I have carried out the relevant code of conduct and provided the requisite screenshot for validation by submitting this pull request.
Thank You for this contribution.

Owner

Ok got It 👍

@VaibhavArora314 Done 👍


Pointer to pointer?

Sorry if this is a silly question.  On the following line:
https://github.com/kellydunn/golang-geo/blob/develop/google_geocoder.go#L122
You are getting a pointer value to the address of the struct, so a pointer to a pointer.  Is it necessary to have this for proper unmarhsalling or would a single pointer suffice?

you're correct, the following should suffice:
res := &googleGeocodeResponse{}
err := json.Unmarshal(data, res)

I can fix this now, if you'd like.

Feel free to fix.
I am bit confused on how the json.Unmarshal function still works even with the extra indirection.

This is very interesting and I wouldn't have expected json.Unmarshal would work in this case, but it does!
So under the covers Unmarshal work via reflection. You can think of that second argument to json.Unmarshal as a way to feed json with Type information on what to attempt to cast the byte slice to. For example, json.Unmarshal(data, &int{}) instructs json package to populate an int with the bytes stored in data.
Okay, so how is the value resolved? Over simplification, Interfaces are pointers to type information and the underlying value. So in either case of indirection, the same value is being pointed to whether it's *type or **type.
http://play.golang.org/p/LHo3k0oYr_
The final piece is how does json know that *type and **type are equivalent, when they are not? json does this work by inspecting the type data in retrieved via reflect.TypeOf. When a pointer is encountered, it unwraps this pointer via reflect.Value.Elem() here. The type has to be addressable which is why we must always pass pointer to json.Unmarshal. This reflection makes it possible to serialize structs like type A struct{ int* Prop }
There's a great writeup here about reflection: http://blog.golang.org/laws-of-reflection and links to more about interfaces here: http://research.swtch.com/interfaces

Thanks for the detailed response @drewwells - so from I what i gathered from your explanation have the extra pointer does not have any negative consequences in this situation (i.e. it does not cause any subtle / hard to detect bugs).

Not in this case apparently!
On Mon, May 4, 2015 at 2:56 PM Mo<EMAIL_ADDRESS>wrote:

Thanks for the detailed response @drewwells https://github.com/drewwells

so from I what i gathered from your explanation have the extra pointer
does not have any negative consequences in this situation (i.e. it does not
cause any subtle / hard to detect bugs).

—
Reply to this email directly or view it on GitHub
https://github.com/kellydunn/golang-geo/issues/37#issuecomment-98832945.

@drewwells :+1: for the explanation as well!  Definitely interesting to learn more about how reflection is used internally for language features :)

Closing, as #38 has been merged.


TypeError with route_scope in endpoints.py

Hi,
Here is a very small example when I try to construct an API with starlette-api but I get an error, could you tell me where my error is?
Thank you
import pytest
from marshmallow import Schema
from marshmallow import fields
from starlette.testclient import TestClient
from starlette_api.applications import Starlette
from starlette_api.endpoints import HTTPEndpoint
from starlette_api.routing import Router

class RunnerSchema(Schema):
    id = fields.Integer()
    name = fields.String()
    token = fields.String()

class RunnerEndpoint(HTTPEndpoint):
    async def get(self) -> RunnerSchema():
        return {"id": 1, "name": "name", "token": "token"}

def create_app():
    app = Starlette(
        components=[],
        title="Foo",
        version="0.1",
        description="Foo",
        schema=False,
        docs=False,
        debug=False,
    )

    api = Router()
    api.add_route("/runners", RunnerEndpoint, methods=["GET"])
    app.mount("/api/v4", api)

    return app

@pytest.fixture(scope="function")
def app():
    return create_app()

@pytest.fixture(scope="function")
def client(app):
    return TestClient(app)

def test_get_runners(client):
    response = client.get("/api/v4/runners")

    assert response.status_code == 200
    assert response.json() == {"id": 1, "name": "name", "token": "token"}

Result of pytest
self = <test_app.RunnerEndpoint object at 0x7f5dcb6c5588>, receive = <function _ASGIAdapter.send.<locals>.receive at 0x7f5dcb16d8c8>
send = <function ExceptionMiddleware.__call__.<locals>.app.<locals>.sender at 0x7f5dcb6c7620>

    async def __call__(self, receive: Receive, send: Send):
        request = Request(self.scope, receive=receive)
        app = self.scope["app"]
        kwargs = self.scope.get("kwargs", {})

        route, route_scope = app.router.get_route_from_scope(self.scope)

        state = {
            "scope": self.scope,
            "receive": receive,
            "send": send,
            "exc": None,
            "app": app,
>           "path_params": route_scope["path_params"],
            "route": route,
            "request": request,
        }
E       TypeError: 'NoneType' object is not subscriptable

app        = <starlette_api.applications.Starlette object at 0x7f5dcb6ab860>
kwargs     = {}
receive    = <function _ASGIAdapter.send.<locals>.receive at 0x7f5dcb16d8c8>
request    = <starlette.requests.Request object at 0x7f5dcb702a90>
route      = <bound method Router.not_found of <starlette_api.routing.Router object at 0x7f5dcb6ab978>>
route_scope = None
self       = <test_app.RunnerEndpoint object at 0x7f5dcb6c5588>
send       = <function ExceptionMiddleware.__call__.<locals>.app.<locals>.sender at 0x7f5dcb6c7620>

Version of starlette
starlette==0.11.3
starlette-api==0.5.0

It seems a bug on get_route_from_scope method from Router class so I created a test to reproduce it and it seems fixed now.
I'll push the fix along with the new version today/tomorrow.
Thanks !

Yesterday I pushed version 0.6 that should have a fix for that along with some new features.


Support Python 3

Python 2 is on the way out, get ready for py3.
If this involves dropping py2 support, I'm potentially okay with that.

Many projects have pledged to drop Python 2.7 on or before it's EOL on 2020-01-01:
https://python3statement.org

Yeah, I know. We don't depend on any of those libraries, though, so if the amount of work to be compatible with both is reasonable, I'd prefer to support both 2 and 3. Our lab is still rolling py2 as our "supported" python version — though we do have python3 installed so maybe it's no big deal to deploy a py3-only module internally. I'd need to try it and see.
The biggest challenge to 2+3 compat will, of course, be unicode handling — right now scorify just chokes on non-ascii input (which is terrible) and py2's csv module is obstinately non-unicode-aware.


Add a robolectric test to android-test

Breaking up larger okhttp-android test.
TODO docs, tests

@swankjesse requesting post review, having a test in a robolectric environment seems worthwhile.


No Depictions Selected Dialog has reversed buttons

Summary:
The dialog buttons have the positive action in the negative position and vice versa
Commons app version:
structuredData

One comment about the "No, Go back" button in the dialog. It's possible for someone to read the "Go back" (if they don't read the description) and wonder if this would take them to the previous step. I believe "Submit" and "Cancel" would be a concise pair of words that would avoid this confusion.
Also, a more general doubt. Do we really show a dialog whenever a user does not choose any depictions? Wouldn't that be intrusive? Depictions might be a good to have. Can't we convey that in a more subtle way than prompting them each time using a dialog?

@sivaraam this issue is now merged and I am going to close it, please open a new ticket for discussion on the text/functionality

Ok. I've created #3675 for this.


TLS strict runs into Factory method 'create' threw exception; nested exception is java.lang.NoSuchFieldError: xmss_SHA256ph on tessera v9

We were able to start up tessera v8 with TLS on. However, we are running into issues with the same configuration file when using tessera v9.
Please see exception below
11:25:09.520 [main] INFO  o.s.o.j.LocalContainerEntityManagerFactoryBean - Initialized JPA EntityManagerFactory for persistence unit 'tessera'
11:25:10.182 [main] WARN  o.s.c.s.ClassPathXmlApplicationContext - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'payloadPublisher' defined in class path resource [tessera-core-spring.xml]: Cannot resolve reference to bean 'p2pClient' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'p2pClient' defined in class path resource [tessera-core-spring.xml]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.quorum.tessera.client.P2pClient]: Factory method 'create' threw exception; nested exception is java.lang.NoSuchFieldError: xmss_SHA256ph
11:25:10.182 [main] INFO  o.s.o.j.LocalContainerEntityManagerFactoryBean - Closing JPA EntityManagerFactory for persistence unit 'tessera'
Error creating bean with name 'payloadPublisher' defined in class path resource [tessera-core-spring.xml]: Cannot resolve reference to bean 'p2pClient' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'p2pClient' defined in class path resource [tessera-core-spring.xml]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.quorum.tessera.client.P2pClient]: Factory method 'create' threw exception; nested exception is java.lang.NoSuchFieldError: xmss_SHA256ph

Please see configuration snippet below
{
      "app": "Q2T",
      "enabled": true,
      "serverAddress": "unix:/app/iindev/IIN_Quorum_Migration/instance2/datadir/node.ipc",
      "communicationType": "REST"
    },
    {
      "app": "P2P",
      "enabled": true,
      "serverAddress": "https://<IP_ADDRESS>:9004",
      "sslConfig": {
        "tls": "STRICT",
        "generateKeyStoreIfNotExisted": true,
        "serverKeyStore": "/app/iindev/IIN_Quorum_Migration/instance/datadir/server-keystore",
        "serverKeyStorePassword": "quorum",
        "serverTrustStore": "/app/iindev/IIN_Quorum_Migration/instance/datadir/server-truststore",
        "serverTrustStorePassword": "quorum",
        "serverTrustMode": "TOFU",
        "knownClientsFile": "/app/iindev/IIN_Quorum_Migration/instance/datadir/knownClients",
        "clientKeyStore": "/app/iindev/IIN_Quorum_Migration/instance/datadir/client-keystore",
        "clientKeyStorePassword": "quorum",
        "clientTrustStore": "/app/iindev/IIN_Quorum_Migration/instance/datadir/client-truststore",
        "clientTrustStorePassword": "quorum",
        "clientTrustMode": "TOFU",
        "knownServersFile": "/app/iindev/IIN_Quorum_Migration/instance/datadir/knownServers"
      },
      "communicationType": "REST"
    }
  ],
  "peer": [{"url": "https://<IP_ADDRESS>:9003"} ]

Note: If we are turning off the TLS, then tessera starts up fine.

Hi @saikatsain , the issue is due to conflict in version of bouncycastle library being used. We've created a patch release to fix this.
Please see the referenced PR


Add ability to export check / notification rule / endpoint as templates

Exporting a check should give user opportunity to also export notification rules that would match the statuses generated by the check.
Need to discuss how or whether to include endpoints that contain secrets.

Talk with @lukevmorris about possibly using packages for this


Add MessageListAppearance data class

Yep, just noticed while doing a self review. I've pushed another commit that decouples adapter from K9 dependency further.
I'll give it another look if anything else makes sense to offload to the appearance data class.

Colors and backgrounds extraction also got moved to the appearance class. Hopefully this makes sense to you too.

Colors and backgrounds extraction also got moved to the appearance class. Hopefully this makes sense to you too.

I think that's overdoing it. That way you need to pass dependencies to MessageListAppearance and have logic in there. That makes it no longer a simple data class.
MessageListAdapter is responsible for doing view inflation. I don't see why resolving theme attributes shouldn't also happen there.

Thanks


Fails when importing future as renaming it

Operating system: Darwin horta-ml 17.6.0 Darwin Kernel Version 17.6.0
Python version: Python 3.6.6 :: Anaconda custom (64-bit)
Black version: 18.6b4
Does also happen on master: yes
This works:
# test1.py
from __future__ import absolute_import

This does not work:
# test2.py
from __future__ import absolute_import as _absolute_import

Output:

error: cannot format test2.py:
All done! 💥 💔 💥
1 file failed to reformat.

Looks like this is a bug in how black processes future imports. Thanks for reporting, will fix!


Choosing documentation syntax; rst vs. md?

We have already discussed this in context of docstrings but I think this needs another verification because this affects to all documentation we making in future. Some of our documents are now rst and some are md. I think we need to choose one and keep on that.
Already known is that

rst is default for sphinx while md is default for mkdocs
IPython nbconvert renders good rst and not-so-good md
Lexicon writes md using Markdown.jl
rst has more features than md, like toctree (=structure)
rst is feature richer in all measures, md doesn't have actual "structure"?
rst documents are nicely rendered to pdf
md documents are easier for human eye
numpydoc is some kind of variant from rst
almost all(?) python documentation is documented using rst
julia itself uses rst for documentation
github supports both rst and md (and they have their own "github variation" from original md)

Some links related to this

http://stackoverflow.com/questions/34276/markdown-versus-restructuredtext
http://www.unexpected-vortices.com/doc-notes/markdown-and-rest-compared.html ("Please note that, anywhere I say “Markdown” below, if there’s any ambiguity, I specifically mean “Pandoc Markdown”. Gruber’s original Markdown lacks a number of the modern niceties which Pandoc-Markdown provides.") (this has been already discussed in #5).

Do you have any opinions for this? I personally suggest that we use rst in our documentation, mainly because I don't see any good (enough) reasons to use md.
Consequences:
md -> rst : change filename extensions, fix links, find a way to generate api documentation
rst -> md: change filename extensions, change sphinx -> mkdocs in dgs, fix links, find a way to render notebooks

Same same but different. I vote rst and numpy documentation style.

md -> rst : I think we already at a point where almost everything is rst except the api documentation. I already tried the rst parser solution provided by @MichaelHatherly in https://github.com/JuliaFEM/JuliaFEM.jl/issues/4 but this seems to provide the rendering in REPL (symbol ?). I guess we are looking for the save function which generates the documentation files. Options could be that we'd write the functionality in julia (REPL renderer & save function, this would help the community also) or, since we already discussed about sphinx, write a functionality for sphinx to process julia files (already has rst renderer, has to find the docstring from the source files).
rst -> md : We're already using Lexicon to create api documention (no worries there) but the notebooks are a bit problematic. Ipython nbconvert has a functionality to generate .md but when me and @ahojukka5 tested it, mkdocs it didn't render them quite well (all code parts we more like one long inline function). Is there any other way/program to convert notebooks? Maybe if we convert notebooks straight to html although this causes a bit friction on the server side when we have to manually move files to correct directories. Sounds more like spaghetti than solution :laughing:.
I vote for rst even if it's a bit more work.

Ok, I just wanted to double check this. I updated CONTRIBUTING.md.


I cannot run Realsense-viewer

librealsense
2.53.1 RELEASE

OS
Windows

Intel RealSense Viewer / Depth Quality Tool has crashed with the following error message:
GL_INVALID_VALUE - C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\common\opengl3.cpp:572

Hi @jerry0101224  In past occurrences of this error that have been reported, a solution has been to download and launch an old version of the RealSense Viewer, then close it and launch the most recent Viewer.  This process is described at https://github.com/IntelRealSense/librealsense/issues/10544#issuecomment-1138569631

Hi @jerry0101224  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


Problem with TCP proxy

With a Proxy TCP I can have only one user, using the proxy because they all have the same IP ie the IP of the proxy, how can I fix? or ensure that IP connections are unlimited? @sant0ro

The problem with Proxy is every end-user IP is the same of the Proxy Server IP.
Yupi uses IP Address (END-Point) as Client Identification, and i will not change this as a security issue.
If @TheDoct0r11 knows any other way to make it work, feel free to ask him.

okay I'll try to solve my problem, thanks

@sant0ro That isn't entirely correct. Yupi only uses the IP Address as Identification, not the local endpoint.
We're living in a world with NAT resulting in having multiple computers residing behind the same public IP Address.
It usually makes sense to allow only a few connections from the same network, but to limit it to one per network doesn't make sense, since other players in the same network would have the same IP.
This would prevent users from accessing Yupi with their family members, from public WiFi and maybe even from Mobile Networks (not really sure about those though)
I'm currently refactoring the Sockets System, and once that's done we might consider adding a config option for Reverse TCP Proxies.

I was thinking this, my friend with his laptop he wanted to connect to my retro server but became a spectator could not move or else after entering it the navigator worked. It is a bad thing for an IP user for me.. and i cant use a proxy for security issue

Yes Doctoro you're right.  But Yupi doesn't uses only the IP Address as Identification. Literally uses the End-Point <=> IP Convertion that results into IPv4 + Some Hashes
You can see if you try login. So these Hashes are designed for different machine.
So login into different machine in same network isn't a problem.
The problem is using proxy. since the proxy redirects entirely data for the same machine. The proxy machine. So the hash isn't different ;)

As far as I can see only the IP Address is being used:
Add to ClientManager
Override existing in ClientManager
IP Address to String Conversion
Mono implementation of System.Net.IPAddress#ToString()

boh I have noticed some problems with two different machines .. I do not know


Clearing process dictionary breaks on some keys

ref: https://github.com/phoenixframework/phoenix/issues/5807

The error is from the to_string/1 on the key which can be term, and it's getting a tuple.
https://github.com/mtrudel/bandit/blob/bb159d47a9a6c4d213d42f78d6600a471e21c7b9/lib/bandit/http1/handler.ex#L37

Oh dang. Patching this directly.


Hold position in history on scroll up

Description of the new feature/enhancement
If I have a running process which is rapidly adding output to the terminal, the displayed text often moves too quickly to read easily.
On many other terminals, if I scroll up to view historical output then the position in history will be held in place as new lines are added at the bottom of the output, causing the viewed to text to become stationary and able to be read. If I then scroll back to the very bottom of the output the terminal will continue automatically scrolling down to display new lines as they're added.
That is, while Windows Terminal does currently remember the position I've scrolled back to, I want that position to correspond to a specific line of text in the output even when new lines are constantly being added, so that it's possible for me to read it clearly.

Proposed technical implementation details (optional)
Without knowing much about the implementation details of Windows Terminal, there are a few ways I imagine this could work:

The scroll position is stored as a count of the total number of lines output since the start of the session. When the window is scrolled to the very bottom, the scroll position is automatically incremented as new lines are displayed, and when the window is scrolled up this autoincrement is skipped.

The scroll position is stored as the number of lines back from the final line the user has scrolled, with 0 being the position for a window which has not been scrolled back at all. When this scroll back position is more than 0 and new lines are added to the output, this position is automatically incremented by the number of lines being added, to keep the output displayed on the screen the same.

The scroll position is stored as an offset from the very earliest line of scroll-back history which is stored. When old history is automatically removed from storage while the window is scrolled up, the scroll offset would be automatically decremented to match the number of lines removed, keeping the output displayed on the screen the same.

Hey wadda ya know, this is the topic of heated discussion over in #2529, and it's got a draft implementation in #6062. I'm gonna resolve this as a dup of the original issue:
/dup #980


indexing with T extends keyof  causes OOM if keyof has a number

Ref #23977 and discussion on #24137
Code
Isolated repro (needs dom lib for ElementTagNameMap and associated types):
// @strict: true
// Modified repro from #23977

declare global {
    interface ElementTagNameMap {
        [index: number]: HTMLElement
    }

    interface HTMLElement {
        [index: number]: HTMLElement;
    }
}

export function assertIsElement(node: Node | null): node is Element {
    let nodeType = node === null ? null : node.nodeType;
    return nodeType === 1;
}

export function assertNodeTagName<
    T extends keyof ElementTagNameMap,
    U extends ElementTagNameMap[T]>(node: Node | null, tagName: T): node is U {
    if (assertIsElement(node)) {
        const nodeTagName = node.tagName.toLowerCase();
         return nodeTagName === tagName;
    }
    return false;
}

export function assertNodeProperty<
    T extends keyof ElementTagNameMap,
    P extends keyof ElementTagNameMap[T],
    V extends HTMLElementTagNameMap[T][P]>(node: Node | null, tagName: T, prop: P, value: V) {
    if (assertNodeTagName(node, tagName)) {
        node[prop];
    }
}

Expected behavior:
No crash.
Actual behavior:
OOM crash after a very long delay.
Preliminary investigation shows the OOM occurs when we try to get the distributed form of keyof <Large Union> - namely the process is defined recursively, so when the union has ~170 members, we create 170 intermediate types (flattening one member at a time, while also wasting time recalculating type flags and other bits we will never need) before getting the final, distributed result. Now, picture doing this on every relation comparison operation for P (this distribution is uncached), and multiplying it for V in assertNodeProperty - the complexity is huge. Our fast path doesn't fix this, since the numeric index signatures cause us to bail on the fast path as it currently is.

I ran into this while attempting to write real-world code (I can provide the example if it's of interest).  I have a fix up at #25728.


RtYamlMappingBuilder and unit tests

PR for #24
Left a puzzle for the implementation of YamlSequenceBuilder.

Coverage increased (+0.8%) to 93.289% when pulling c529bb84ade58a97bc10e3142fd5b7981a807630 on 24 into 2bc2c283eea3ddeeff22dbe5a77825b2881368e5 on master.

@rultor merge pls

@rultor merge pls

@amihaiemil OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge pls

@amihaiemil Done! FYI, the full log is here (took me 1min)


Contrrollers spec

Project Milestone: Blog app - controllers specs
In this project, I set up tests on the controllers recently added to the Blog app.
Highlights 🥇

Add RSpec as a gem to your project.
Create a Request spec file for all your controllers.
Make sure that for each action you check:
If response status was correct.
If a correct template was rendered.
If the response body includes correct placeholder text.

Cheers 🥂 and happy reviewing! 👍

Hy @gemmen29 Thank you for approving my work 🙏


Addresses #1908 to create an upper cell type slim

Addresses #1908 to create an upper cell type slim

I have tested the coverage for animal cell (CL:0000548), and it is 90%, so not bad (Full report here:
#####Coverage percentage##### |
-- | --
90.46% |
#####Number of terms covered by each term in the slim##### |
exocrine cell | 23
bone cell | 39
smooth muscle cell | 59
striated muscle cell | 75
endocrine cell | 89
stem cell | 103
connective tissue cell | 206
neural cell | 595
hematopoietic cell | 659
epithelial cell | 721

I think I'd like something a bit more granular

That is closer to my first proposal https://github.com/obophenotype/cell-ontology/issues/1908#issuecomment-1545658060, and then we decided to go to a higher level. I can use that one with some edits discussed with @bvarner-ebi.

This list adds some granularity and still has a coverage above 83%:
#####Coverage percentage##### |
-- | --
83.37% |
#####Number of terms covered by each term in the slim##### |
fat cell | 12
melanocyte | 15
monocyte | 20
exocrine cell | 23
natural killer cell | 28
extraembryonic cell | 29
cell of skeletal muscle | 29
germ line cell | 33
bone cell | 39
glial cell | 41
blood cell | 42
stromal cell | 52
macrophage | 55
smooth muscle cell | 59
retinal cell | 74
dendritic cell | 77
fibroblast | 83
endocrine cell | 89
B cell | 94
stem cell | 103
T cell | 156
neuron | 493
epithelial cell | 721
More work can be done to improve it, but it might be a good first set. Would you be happy to use this subset instead of the previous more general one @dosumis ?


Test Explorer UI updated version (2.20.2) makes Behave Test Explorer not work

Hi,
The new Text Explorer UI update (2.20.2) is impacting Behave Test Explorer on VSCode. In this version the extension is not working properly.
Best regards,

Thanks for submitting the issue, I will have a look at it. For now, if you want to keep using the extension you can downgrade the test explorer UI version in your marketplace.

Here's a log from the debugger:
rejected promise not handled within 1 second: Error occurred during process execution: Error: spawn cd && behave ENOENT
/Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js:5
rejected promise not handled within 1 second: Error: Error occurred during process execution: Error: spawn behave ENOENT
/Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js:5
stack trace: Error: Error occurred during process execution: Error: spawn behave ENOENT
	at behaveTestRunner.<anonymous> (/Users/claudio.mezzasalma/dev/git/lorthirk/vscode-BDD-Python-test-adapter/out/behaveTestRunner.js:29:23)
	at Generator.throw (<anonymous>)
	at rejected (/Users/claudio.mezzasalma/dev/git/lorthirk/vscode-BDD-Python-test-adapter/node_modules/tslib/tslib.js:108:69)
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)

And this is the JS Object contained in the error event at processExecution:53
{
    errno: -2,
    code: "ENOENT",
    syscall: "spawn behave",
    path: "behave",
    spawnargs: [
      "--dry-run",
      undefined,
    ],
    vslsStack: [
      {
      },
      {
      },
      {
      },
    ],
  }

Thanks for posting the logs, I am not able to recreate them. Would you be able to provide a sample project that causes this error?

It's a simple project with pipenv to manage the dependencies, and behave installed as a dev dependency. The ENOENT error makes me think that the command is spawn outside of the environment.
python-playground.tar.gz

I have been trying out the sample project that you have posted and it works completely fine for me on multiple versions of Test Explorer UI. I think it might be your working environment that is causing the bug, could you give me any more information about that?

What information do you need exactly?

I'm having virtually the same issue. I use Anaconda to manage my environments.
Here are my repro steps. Note, you must not have behave anywhere in your PATH.

Install Anaconda (I use mambaforge from https://github.com/conda-forge/miniforge)
The installer updates .bashrc on Linux; you'll need to start your terminal as a login shell or source ~/.bashrc (this assume you're using bash)
If you're on Windows the installer will add a start menu entry which you can use to open a console window set up for Anaconda
Create a new environment
I use mamba, but you can use conda, just swap one for the other
mamba create -y -n repro -c conda-forge --strict-channel-priority behave
Change the current directory to the location of a project w/ behave tests
Launch VS Code from here (simply type code in the console window)
Install the extension
Reload the window (CTRL + R)
View the Runtime Status of the Behave Test Explorer extension.
You should see Error occurred during process execution: Error: spawn behave ENOENT

If you activate the environment from the console window (conda activate repro) and then launch VS Code the extension works just fine.
I think the problem is the extension blindly assumes behave is available on the PATH when VS Code is launched. I wonder if there's a way to leverage Microsoft's Python extension and use the current Python interpreter (you can invoke behave via python -m behave).

Thanks for your step by step explanation @tyrius02 , For now, I implemented the invocation you suggested (python -m behave). If this did not fix it, let me know and I will try to put this on the top of my list.
I abandoned this extension for a while but in the coming month, I will try to update this extension with more improvements.


Prevent show a hidden status bar when opening modals, fix #7474

Motivation
Closes the old #7474, keeping the status bar hidden when displaying a modal
or dialog, this is accomplished by verifying if the activity status bar is hidden or not.
Test Plan
Added a test to RNTester, so it can be tested from there:

Run RNTester project
Go to  tests
Set hidden: true in the StatusBar hidden samples
Set modal visible: true and see the result

Here are some gifs to help see the results:
Before

After

Related PRs
none
Release Notes

[ GENERAL  ]   [ BUGFIX      ]   [StatusBar] - Prevent show a hidden status bar when opening modals

Great job! Looking forward to this being merged!

Hi @janicduplessis, @hramos, can you review this one please :grin:? Thanks so much guys!


Rounding Bug for Last Line of Split (v8)

If you consider to tackle #399, this should do it.
Just realized, this also occurs in Safari, so it might be related to v8 in general.

Hey @naeramarth7 didn't realize you did a PR too :D
I was just about to push for this and I think our best bet is going to be to use ynab.formatCurrency
I should have done this to begin with but we just need to multiply total and currentValue by 1000 and use ynab.formatCurrency(total) on lines 58 and 62

@joshmadewell Sure, give me a sec (:

@joshmadewell Hope the last commit is, what you we're looking for - totally missed L62, since I missed the loop and was just testing my specific case. :p

This looks good man! Nice find! Thanks for the fix!

I'm the one to be thankful for the Toolkit (: - glad I could contribute!

Yup, this is just the joys of floating point in JS in general. Try 0.1+0.2 in your terminal some time. Wat


RyC margins and fix for iPhone X

Codecov Report

:exclamation: No coverage uploaded for pull request base (development@b05f9c9). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             development    #1336   +/-   ##
==============================================
  Coverage               ?   60.38%
==============================================
  Files                  ?      327
  Lines                  ?    24558
  Branches               ?        0
==============================================
  Hits                   ?    14830
  Misses                 ?     9728
  Partials               ?        0

Impacted Files
Coverage Δ

...goSDK/MercadoPagoSDK/ExitButtonTableViewCell.swift
0% <ø> (ø)

...DK/MercadoPagoSDK/ReviewScreenViewController.swift
6.25% <0%> (ø)

...rcadoPagoSDK/PXContainedActionButtonRenderer.swift
0% <0%> (ø)


refactor(typing): reduce type ignores in api.py

This PR is mainly working through type: ignore / TODO comments and fixing what I can.
My primary motivation for this was to be able to use pyright within altair more often.
Despite the existing type: ignore comments, I was getting 46 errors in api alone.
Anywhere that it appears I've made a change unrelated to existing comments, please know it was to solve one of these:

Great improvements! I especially like the type intersection :) Added some questions.

Thanks for the review @binste, I've just finished going through your comments.
No rush, but I'll wait for your response before reverting/making those changes

@binste as https://github.com/vega/altair/pull/3480#discussion_r1681509490 was the last part to resolve, I thought I'd go ahead with it in 21a3e84 (#3480)
Hopefully that will make this easier to close, as you can just revert that commit if needed


Diagonal Movement

Diagonal movement is faster than using the WASD keys for cardinal directions (up, down, left, right) .
If you move one unit to the right and one unit up in a single frame, the plane covers a greater distance diagonally compared to moving one unit solely along the X or Y axis, so maybe we can amend.
Pretty common issue in top-down games with lots of documentation to fix online. (Good first issue fix)

I've experimented with different ways to solve this issue, like cutting the movement speed in half while diagonal movement is being done, issues arise with either the generation or with the coordinates displayed, it also feels somewhat more natural for some reason when the plane moves diagonally in whole intervals. I'm open to PRs changing this.

Closing due to PR https://github.com/Glowstick0017/Little-Plane-Project/pull/40


fix(github): use the new inflight interface modifier

Superseded by https://github.com/winglang/winglibs/pull/199.


StreamGear API Limited Segments Bug

Description

Currently, There's a bug in StreamGear API which only allow limited chunks/segments upto 10 only (controlled by -window_size and -extra_window_size ffmpeg parameter that defaults to 5 each), which results in overwritten chunks after every fixed 10 chunks cycle that doesn't contains any information about previous ones. This behaviour is suitable for low latency Live Streaming (such as from web/pc-camera) in which only requires few of the frames for reference at that very instance, but certainly not suitable for encoding complete video file from beginning to end.
Acknowledgement

[x] I have searched the issues for my issue and found nothing related or helpful.
[x] I have read the Documentation.
[x] I have read the Issue Guidelines.

Environment

VidGear version:  0.2.0-dev
Branch:  Development
Python version:  all
PiP version:  latest
Operating System and version: all

Expected Behavior
There must me separate functionality/mode available in StreamGear for encoding Live and Complete Video Streams.
Actual Behavior

Only LiveStream encoding is available.
Possible Fix

Add a variable to separate this functionality.
Steps to reproduce

Run any StreamGear Example.
Optional
Credit: @leviethung2103

Successfully resolved and merged in commit: https://github.com/abhiTronix/vidgear/commit/e74e2a54a5a5f62c26e069f944a650d3e3afc40a


[FEATURE REQUEST] Newtype support for #[property]

I have a newtype over f64:
#[derive(Debug, Clone, Copy, PartialEq)]
pub enum ScaleRequest {
    FitToAllocation,
    Set(f64),
}

It maps one-to-one to f64 (0. maps to the first item, others map to the second item). I'd like to use it with the properties macro. For GObject it should appear as an f64 property.
Currently this seems to require implementing HasParamSpec, ToValue, From<ScaleRequest> for Value (for some reason?) and FromValue, the last of which requires unsafe code:
#[derive(Debug, Clone, Copy, PartialEq)]
pub enum ScaleRequest {
    FitToAllocation,
    Set(f64),
}

impl From<f64> for ScaleRequest {
    fn from(value: f64) -> Self {
        if value == 0. {
            ScaleRequest::FitToAllocation
        } else {
            ScaleRequest::Set(value.clamp(0., 10.))
        }
    }
}

impl glib::HasParamSpec for ScaleRequest {
    type ParamSpec = glib::ParamSpecDouble;
    type SetValue = Self;
    type BuilderFn = fn(&str) -> glib::ParamSpecDoubleBuilder;

    fn param_spec_builder() -> Self::BuilderFn {
        Self::ParamSpec::builder
    }
}

impl From<ScaleRequest> for glib::Value {
    fn from(value: ScaleRequest) -> Self {
        value.to_value()
    }
}

impl glib::ToValue for ScaleRequest {
    fn to_value(&self) -> glib::Value {
        match *self {
            ScaleRequest::FitToAllocation => 0.,
            ScaleRequest::Set(scale) => scale,
        }
        .to_value()
    }

    fn value_type(&self) -> glib::Type {
        f64::static_type()
    }
}

unsafe impl<'a> glib::value::FromValue<'a> for ScaleRequest {
    type Checker = glib::value::GenericValueTypeChecker<f64>;

    unsafe fn from_value(value: &'a glib::Value) -> Self {
        f64::from_value(value).into()
    }
}

Would be great if this could be representable without unsafe code with some kind of pair of From<f64> for T + From<T> for f64.
It's also worth noting that I could instead implement Property with Value = f64 and custom get and set returning f64. However, that would result in my Rust type having getter and setter working with f64 instead of the real type, which is not as nice.

cc @sdroege @ranfdev

I think what would be nice to have is something like a transform = from attribute on the macro, which would be used together with type. Then you could in your case do type = f64, transform = from and provide From impls in both directions for your enum.
We might want to add other ways of transformation later, not sure. If you can't think of anything else then maybe just a from attribute would be sufficient.

Instead of requiring transform = from, the PR I just pushed always calls From::from. That enables supporting other types which don't implement FromValue, as ThreadGuard.


If the selected test class doesn't exists, raise an error.

I wold like to run only the tests in one class, therefore I run:
bundle exec rake test:unit[MyAwesomeTestClass]

A small issue happens if the class name is misspelled.  In that case the project is still built, and the output looks like:
UnitTests - iPhone 5 iOS 10.2 - Finished executing 0 tests after 0.002s. 0 Failures, 0 Unexpected
UnitTests - iPhone 5 iOS 9.0 - Finished executing 0 tests after 0.001s. 0 Failures, 0 Unexpected
Total - Finished executing 0 tests. 0 Failures, 0 Unexpected

It clearly says Finished executing 0 tests but I would rather prefer a big red error message :P

Good point, I actually run into this myself from time to time, wondering what's happening :).

Fixed via 1b8b21c8c9a9ef697f0b0109b2b30d69e9a859d7


Query filtering on related entities - is it possible?

I set up a one-to-one relationship between two entities like explained in the documentation.
I am able to do queries like below and filter by props of documents object:
query {
  documents (where: { id: "12345" }) {
    id
    dateCreated
    documentObject {
      isRevoked
      isRemoved
    }
  }
}

But I am unable to select, say, all documents whose isRevoked property of one-to-one related documentObject is true.
Is it possible with Graph at all? Other GraphQL implementations have filter or like that to do such kind of queries. I did not find anything similar here.
PS. I can of course swap entities and query for documentObjects { document {} } and filter by documentObjects props. But in that case I am unable to filter by document props or both at once. I also can duplicate data when processing events, but this is suboptimal if I really want to separate entities.
Any ideas?

Somehow related issue: https://github.com/graphprotocol/graph-node/issues/1573

We do not currently support this. It is and long term goal to support this form of filter. The workarounds you mention would be required to achieve this at the moment.
Thank you for the report, but since this is a known limitation I'll go ahead and close it.


Minor getting started page doc update

Hi all,
I'm playing around with 11ty and was working through the docs, which are great by the way.
I came across a minor discrepancy between what the docs say 11ty will output in the terminal, vs what is actually output.
The 11ty command line tool outputs "Processed x files" and not "Wrote x files".
This PR updates the getting started page to reflect this.
Let me know if you need anything else in this PR
Thanks
Ed

Ah, great thank you!


Add contribing guide [skip ci]

Closes #653

OMG I didn't know about the [skip ci] commit message handling. 😮


Unable to build Kha apps from a system with glibc 2.27

Hi!
I'm not sure if this is desired/needed or something that went unnoticed, but appears that now Kha apps can't be build in Linux systems with a glibc version less than 2.29:
Compiling shader 1 of 8 (painter-colored.frag.glsl).
.../Kinc/Tools/krafix/krafix-linux64: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by .../Kinc/Tools/krafix/krafix-linux64)
Compiling shader 1 of 8 (painter-colored.frag.glsl) failed:
Shader compiler error.

Looks to me that this can be the reason, since this was working to me until today → https://github.com/Kode/krafix/commit/7f8fced63382cfef47a60e4a1d21d8271766aa7d .
To be clear, I'm not saying this should be changed back nor anything like that — but I would appreciate some feedback to know if I should update my system or if this is really an unwanted dependency change that went unnoticed.

That commit was done to fix this because GitHub switched to a later Ubuntu version automatically - as you can see, the commit changed it from latest to 18.04. But I had not changed the Kha/Kinc repos yet to point to the latest commits so you're probably still on the earlier version. Did that now.

as you can see, the commit changed it from latest to 18.04

Wow, yes, I totally changed that red/green colors in my mind or something :man_facepalming: — sorry for the noise and thanks a lot for the really quick update :smiling_face_with_three_hearts:


Add link to test results details from TAP list view

We generate TAP results for all tests that we run from this test infrastructure.  Since many different types of test frameworks can be called by this infrastructure, we wanted to have this standardized high-level view of test results.
The many types of test frameworks each produce their own type of test results, which we will also like to show, if they are present. Currently you can see more detailed test output from the console view, but this is not convenient to search through.   When there are extra test results / artifacts, we should try to link to a view of them from the TAP results list view (for each test group).
For testing tests, this means linking to the html (or xml) pages that get created).
For jtreg tests and other types of tests/frameworks, we should determine which output files contain most useful information to link to.
This means we should ensure that test artifacts are kept for the Jenkins test builds that we keep.

What is TAP?

Test Anything Protocol (https://testanything.org/) super simple agreed upon results format... allows us to unify many different types of tests/frameworks under one roof (including 3rd party app tests, perf tests, etc).

Cool thanks! :-)

so the issue with using jenkins artifacts is that the artifacts get replaced every time there is a new build, perhaps we need somewhere to dump all the test artifacts that we can then keep and link to such as an ftp server?

@gdams - How does the current flow work?  Is it: 1.) Jenkins slave builds an OpenJDK binary on say the s390 slave. 2.) That image gets copied back to master? OR stays on the s390 slave? 3.) The s390 'test' host then somehow needs to drag that binary across to itself in order to test it....

the image gets archived which means that it is essentially copied to master

I think I see now - so we have an order of operations issue in teh we want to keep an archive on builds to test against but not display that archive on GitHub under nightly or tagged releases as they're not tested yet.  Jenkins can archive those binaries on master but we'll likely run out of space?

jenkins is already archiving the latest nightly for each platform on master, as long as we test quickly there should be no issue

Could have jenkins store say the last 5 JIC?

Closing this issue, as we will pursue the use of the richer test output options (junit/testng as preference), will open a different issue/enhancement for the work.


Add ImageTxt collection

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
New feature: ImageTxt collection, linked issue #82 (replaces #86)

Depends on #87 and will rebase when merged

1299a53036fde6fb360ddf23f2fea41d843c21e1 and 9c4f970593cead5bf6150b55efd15cdb5314487d could be cherry-picked into oci-layout or main

[ ] Closes #82


Created and updated docs for 1.23-26

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


Data Name Character Limit Applies in C Headers

Using the "-n" argument to input a name in convbin, the name is limited to 8 characters for the appvar in all output formats. This means that even if one passes "-oformat C" and creates a C header file that has no such character limitations, the array name is still subject to the character limit mean for appvars. So the input name "menu_room_tilemap" is converted to "menu_roo" and doesn't throw up any errors or warnings about the name size.

The patch for #10 seems to have broken something else, all projects built with the new convbin fail to build after linking with: "C:\CEdev\bin\convbin.exe: unrecognised option `--uppercase' "
Afterwards it returns convbin -h and "make: *** [bin/DEMO.8xp] Error 1". Reverting back to the older version of convbin works fine.

You are using the wrong release version.

Just checked, I was somehow using version 3.0, not 3.4. Thanks for the help!


Dead white pixels even after convergence

Hi,
Even after convergence, some noisy white pixels remains in the scene:

Is there any workaround ?

mmmm, it's part of the game. You need to bake many and many time to try to
remove the noise. Nvidia have made a optimix algorithm to reduce time an
noise. We need something similar. At the end the noise is normal.
Dario
On Wed., Aug. 26, 2020, 6:59 a.m. Matthieu Garrigues <
<EMAIL_ADDRESS>wrote:

Hi,
Even after convergence, some noisy white pixels remains in the scene:
[image: image]
https://user-images.githubusercontent.com/846584/91312711-d14f8300-e7b4-11ea-9f93-6bfdc62b6c61.png
Is there any workaround ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hoverinc/ray-tracing-renderer/issues/152, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEH36PL2HXFAFVMVULJTJPTSCUINPANCNFSM4QL3PGMQ
.

Thanks for your answer. What do you mean by "bake" ? Do you mean that the noise is supposed to eventually dissapear if we leave the rendering run forever ?

If noise is normal, it seems like we can remove most of it with a simple filter assuming local coherency.

Some information are here:
https://alain.xyz/blog/raytracing-denoising
https://www.scitepress.org/Papers/2018/66558/66558.pdf
http://www.cs.cmu.edu/afs/cs/academic/class/15869-f11/www/readings/parker10_optix.pdf
Without GPU support I think that it is really hard to remove these "white
points", It's part of the problem of the "caustic" approach of path trace.
Optix is really useful in this sense.
I hope to see soon a GPU integration in this project.

Dario Passariello
Principal Software Developer
Trainer and 3D Expert
https://dario.passariello.ca
mobile: +1-778-318-2645
On Wed, Aug 26, 2020 at 9:22 AM Matthieu Garrigues<EMAIL_ADDRESS>wrote:

If noise is normal, it seems like we can remove most of it with a simple
filter assuming local coherency.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hoverinc/ray-tracing-renderer/issues/152#issuecomment-680983131,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEH36PNWTUSWD36NK4K4FILSCUZDXANCNFSM4QL3PGMQ
.

Another node: the white dots seems to increase when we let the rendering run.
Thanks @passariello  for the links, I'll have a look.

Hi,
Even after convergence, some noisy white pixels remains in the scene:

Is there any workaround ?

@matt-42 do you have glass on the scene?

No glass. But I think this is due to a low roughness on material. When I increase it the white dots dissapear...


[RIP-10] Add test cases for QueryMsgByUniqueKeySubCommand

What is the purpose of the change
   Add test cases for QueryMsgByUniqueKeySubCommand

Brief changelog
   Add QueryMsgByUniqueKeySubCommandTest.java

Verifying this change
   run QueryMsgByUniqueKeySubCommandTest.java

Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.1%) to 48.905% when pulling a7c355b3c5765d60d06661b70020825eec17e50d on codefans:develop into 4f8d96c4a753d24dc2c2e8933d5d2908821f922f on apache:develop.

LGTM

This pr add the test case for QueryMsgByUniqueKeySubCommand,but CI code coverage is down.Can you find the reason by looking at the CI code coverate report?


Finite bounds needed for non-finite types.

Finite is not a good name for the interval bound, because it becomes a bound on any generic struct containing an Interval or Selection.

Fixed by removing Finite bound from Default impl.


Nest and Blink Camera take time to load

Home Assistant release with the issue:
84.6
Last working Home Assistant release (if known):
80.x
Operating environment (Hass.io/Docker/Windows/etc.):
Hass
Component/platform:
camera.x (Nest)
Description of problem:
When loading tabs/pages with camera.x listed in groups, it takes the page about 5sec. to load the actual still image of the camera.  Furthermore, the updates of the camera still are extremely slow and it used to be near real time.  Have tried listing only one camera but no luck.  I am not using lovelace.  When you first load the page or tab, the camera boxes are not even shown, typically you see a gray bar w/the name of the camera and then it loads the image/video.  Now it takes a few seconds and some times you have to switch between tabs to get it going.  I have tried clearing out my home-assistant_v2.db and building a new one as well.  The page is then cached and works as it always did until you go back to it after some time (an hour or so), and you witness the slowness again.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
# _configuration.yaml_
nest:
  client_id: !secret nest_id
  client_secret: !secret nest_secret
blink:
  username: !secret blink_user
  password: !secret blink_password
  scan_interval: 360
# _groups.yaml_
cameras1:
  name: cameras1
  entities:
  - camera.front_door
  - camera.blink_garage
  - camera.blink_side_door
cameras2:
  name: cameras2
  entities:
  - camera.living_room
  - camera.blink_front_stairs
  - camera.baby_room

Just wanted to report that this is way more pronounced with "states" view vs. lovelace.  Migrating my hass setup to lovelace has solved 95% of the problem and it's 100% acceptable/tolerable.  Thanks!

Is this still an issue you are experiencing that someone needs to look at? It sounds like this may be resolved, at least to an acceptable point.

On 89.2 with lovelace and it is no longer an issue.  It might be an issue for some if they still use states though?  We can close this.

Thanks for reporting back @ttaidapos!


[#2459] fix (integration-test) Using host.docker.internal to solve the problem of container access to the host network

What changes were proposed in this pull request?
Docker can support the container using host.docker.internal to  access to the host network
https://docs.docker.com/desktop/networking/#use-cases-and-workarounds
Why are the changes needed?
Fix: #2459
Does this PR introduce any user-facing change?
NO
How was this patch tested?
TrinoConnectorIT

It's okay with me, @xunliu , do you need to take a look?


Error in new Release

Hello,
Since this morning when I Try to add NSwag.CodeGeneration from Nuget console in Visual Studio I get an Error that doesn´t let me work.

Do you know how could I install previous versión with Nuget console?
Thank you!

Try add
<#@ import namespace="System.Linq" #>

On top of your T4 template

I got the same error.  There was an import namespace="System.Linq" already in the .tt file so that wasn't it.

What about
  <#@ assembly name="System.Core" #>

?

Can you post your T4 template so that i can reproduce the error? (or better: a sample project?)

I actually have two error that show up.  I am using 7.6.6171.30839.  Both are Compiling Transformation errors:

The name 'Model' does not exist in the current context [Line 1]
The type or namespace name 'Linq' does not exist in the namespace 'System' (are you missing an assembly reference?)  [Line 3]

This is a .Net 4.6.2 console application with no additional references than what comes in normally with a new console project and what comes when I get the NSwag CodeGeneration project.
Template Attached: RequestUrlTemplate.tt.txt

Do you reference the nswag project via nuget or source code/project reference?

It seems that in some way the "RequestUrlTemplate.Extensions.cs" file is missing (where the Model property is defined):

My problem is, that I don't understand how you use the project... If you use the DLLs the tpls are already compiled into the assembly and you shouldn't get these errors.

I have tried with previous version and it works.
I'm not authorized to post my t4 template, but the error occurs when you add the Nswag.CodeGeneration library via Nuget and then compile the project.
My project uses Entity Framework 6 and it's connected to an Oracle Database.

Ah I see, just delete the created CodeGenerators directory in your project...


empty-dir: Fix bug in the way empty-dirs are handled for overlay

With #1485, we moved the default medium empty-dir creation to the
sandbox rootfs. This worked for devicemapper, but in case of overlay
the "local" directory was being created outside the sandbox rootfs.
As a result we were seeing the behaviour seen in #1818.
Fixes #1818
Signed-off-by: Archana Shinde<EMAIL_ADDRESS>

cc @awprice

@jodh-intel @egernst Test added!

/test

Ping @kata-containers/runtime !

Looks this PR make the behavior of overlay identical to DeviceMapper, which is good to me.
While having chatted with @bergwolf, he has some other suggestions.

@bergwolf let's pull in further changes in new PR?


Rename or alias the 'ipc' modules into two different names

The 'ipc' module in electron is actually two different modules depending on whether it is imported from the main process or from a window/render process. When using TypeScript with electron, all of the files in an application are typically compiled at the same time by one invocation of the compiler. Having multiple and conflicting type definitions for the ipc module causes errors.
This problem can be solved by renaming the ipc module with two new names, one for the main process (i.e. 'ipc-main') and another for render processes (i.e. 'ipc-window').

While this is unfortunate, it also is a breaking change, I'd rather create ipc-main and ipc-window and have them be aliases of ipc (perhaps blowing up if you use the wrong one in the wrong context)

Refs #2544.
I'm :+1: on adding new ipc-main and ipc-window modules while keeping the old ipc for compatibility. And in the new ipc-window module we can also add a dummy event argument when emitting events to keep consistency with ipc-main, it is a good chance to fix that.
 Having this fixed will bring help straighten out my build. :smiley:

excellent, thanks.


v1.3 Allysa Add birthday field, conflicts and test fixed

Follows from #154 just fixes conflicts and tests


use recompose, use unix timestamps

Hey, I'm using react-big-calendar and I'm seeing performance hits when using many events and/or many resources.
I noticed that for example a change to the events array will cause a lot of components to update, even though their props don't really change (e.g. TimeSlot); or any prop change will cause all events to recalculate and rerender. This is caused by missing shouldComponentUpdate/PureComponent as well as declaration of arrays and dates inside render functions and handing those to child components as props.
There is a few things that could be optimized:

Outsource expensive calculations out of render (use withPropsOnChange from recompose?) to avoid unnecessary recalculations and unnecessary rerendering of child components
Avoid date types (use unix timestamps +new Date() since they are much easier to compare)
Use PureComponent
Small stuff like avoiding inline functions, object declarations and the likes in render functions

This PR introduces recompose withPropsOnChange, unix date and other small optimizations, but it is only a start. There is many other places that would benefit, but will need to be revisited.
I'd like to use this as a discussion start, so let me know what you think of this.
I've published this packaged as react-big-calendar-opt, so feel free to try it, especially with 4x throttling enabled in chrome devtools.

Thanks for taking the time to put this together. I can't look at it in detail right now but it's appreciated! Honestly I'm always a bit anxious about performance optimizations generally since they often include a bunch of hidden costs but it's always good to explore! Are you noticing any significant improvements or performance with this? Is it solving a specific concern your having? It's helpful to get baseline for starting the discussion :)

Hey, yes, it's making a big difference as soon as you have many cells rendered. Here you see few events, lots of cells; after I click on save, one event is moved to another resource:
Before the changes:

Around 6 seconds UI freeze with console.log on rerender of components (why-did-you-update), 2.5 seconds freeze without logs.
After

Around than 1.5 seconds freeze with console.log, no noticeable freeze without the logs.
I can feel the anxiousness with perf optimizations, especially when implementing shouldComponentUpdate. I found recompose withPropsOnChange very useful since it serves more as a memoization for prop calculations instead of limiting component rerender to specific changes. For example, the calendar gets events but needs to separate allday events from non-allday and filter visible events. Currently this is done inside the render cycle of TimeGrid component. Instead, you could have this:
const enhance = compose(
  withPropsOnChange(
    [
      'events',
      'range',
      'startAccessor',
      'endAccessor',
      'allDayAccessor',
      'showMultiDayTimes',
    ],
    ({
      events,
      range,
      startAccessor,
      endAccessor,
      allDayAccessor,
      showMultiDayTimes,
    }) => {
      let start = range[0],
        end = range[range.length - 1]

      let allDayEvents = [],
        rangeEvents = []

      events.forEach(event => {
        if (inRange(event, start, end, { startAccessor, endAccessor })) {
          let eStart = get(event, startAccessor),
            eEnd = get(event, endAccessor)

          if (
            get(event, allDayAccessor) ||
            (dates.isJustDate(eStart) && dates.isJustDate(eEnd)) ||
            (!showMultiDayTimes && !dates.eq(eStart, eEnd, 'day'))
          ) {
            allDayEvents.push(event)
          } else {
            rangeEvents.push(event)
          }
        }
      })

      allDayEvents.sort((a, b) =>
        sortEvents(a, b, { startAccessor, endAccessor, allDayAccessor })
      )
      return { allDayEvents, rangeEvents }
    }
  )
)
export default enhance(TimeGrid)

There is nothing to loose really, the only downside is the added recompose dependency, but we can always cherry pick the actually used functions instead of importing the whole thing (recompose/withPropsOnChange), so the size difference shouldn't really be noticeable.
I think it would be beneficial to have a stress test in storybooks, so we can actually measure performance differences.

There is nothing to loose really, the only downside is the added recompose dependency

Well and knowledge of how recompose works, which is not something i know, so there is a lot of addition mental overhead for me having to learn a new library (which may not be a bad tradeoff)
I'm still unsure tho what the benefit is practically apart from the metric "the components don't update as much", that isn't necessarily a problem if the "slow updates" are still to fast to notice a delay. I'm not trying to be difficult here, but i want to make sure we are solving a real bottleneck that folks experience.
in terms of the actual changes, it seems like withPropsOnChange isn't much more than a props -> state reducer in CWRP? It might be more accessible for maintainers/contributors to do it the old skool way instead of bringing in a new library (maybe not).
I would also check, btw with changes i've got staged in https://github.com/intljusticemission/react-big-calendar/pull/733 which does add some memoization to the TimeGrid component in places I think suffer the most from over re-calculation. We'd want to make srue the two PR here can work together nicely!
Thanks again for taking the effort here, i'm glad to have more time spent on the perf concerns!

@bkniffler I don't think you need recompose if you are just going to use 1 utility function. Since withPropsOnChange is just a higher order component, there is no reason not to either copy the implementation or create your own for this library. After looking at the function myself, it simply does a shallow check of props and nextProps inside componentWillReceiveProps. I think this is certainly doable and acceptable to add into the project I would think. I haven't experienced the same performance issues as you have but maybe with some revisions and alignment with other open PRs this might become a suitable PR itself.

Personally i am not a big fan also of using lot's of hoc's in all components, but i'm also concern about performance.
Has i had to implement my own agenda view i also took performance as a big point so i end up using getDerivedStateFromProps
I do all my calculations there and store it on state, and only recalculate it again when the needed props change.

I'm having similar issues for calendars with 5 minute slots and more than 5 resources. There is a significant delay on every select / resize / drag & drop action which only gets worse when more resources are added.
Recompose is certainly an option, however, the author mentioned that the library will no longer be maintained, as the functionality is present in React hooks. https://github.com/acdlite/recompose
@jquense
Would you be open to a pull request addressing the re-rendering of slots without the use of external libraries? I'll probably have time to work on this after about 2 weeks.


Question/Idea: Reverse Domain Name Notation Identity via DNS and Public/Private Keys

(I have only been following Sigstore for a couple weeks so apologies if this has already been discussed somewhere!)
My thoughts
As a big fan of Let's Encrypt, I have been very interested in Sigstore ever since I found out about it. However, I always found the email-via-OIDC system quite limited. I see there are multiple discussions about this topic, but so far they all still seem focused around improving the email-based system (which I still fully support!).
My idea is to offer the option of the quite universally recognized identity of a (sub-)domain to sign things. If I imagine a future where Sigstore, or a similar service, truly becomes the "Let's Encrypt of Code Signing", I feel like a domain would be much more intuitive to see in, let's say, a Windows UAC prompt.
Concept:

User owns a domain and has control over DNS records.
User generates a public/private key pair.
User published public key via a TXT record on their domain. (Example: _fulcio-pubkey.myproduct.example.com)
User wants to sign something and attempts to prove their identity to Fulcio with help of the private key.
The TXT record with the public key is checked by multiple geographically separate servers (Similar to how Let's Encrypt does it)
If there are no discrepancies with DNS, the identification attempt is checked against the public key.
If everything checks out, signing commences and the identity is, for the example: com.example.myproduct

Comparison to email based signing:
Pros:

Vendor neutral
Recognizable reverse domain name notation convention
Easy separate signing of different projects. Examples: com.example.myproductA, com.example.myproductB, or even com.example.myproduct.testing, applications can be configured to only accept files signed for the release version of the intended product, more easily recognizable to users than some email address.
Account at DNS provider may be better secured and audited than, for instance, Microsoft or GitHub accounts, which are frequently accessed by the user.

Neutral:

Significantly different to current email-based identities, but both formats should be able to coexist.

Cons:

Vulnerable to compromise of DNS account or provider.
Private key security entirely in the hands of the user.
User needs get a domain and keep paying for it (free domains exist but they are really sketchy)

Potential for better security:

Some type of key rotation mechanism.
Some kind of TTL/caching of the public key to "bridge" DNS compromise (instant revocation method would be required).

Hey! Thanks for the issue. I think we might already support something similar to what you're describing through SPIFFE and SPIRE. It's documented here: https://github.com/sigstore/fulcio/blob/e88278c03c1593ea3f6dc68d7c7144e545a1fb3b/docs/oidc.md#L27
Note that it still goes through the OIDC flow, but it doesn't use emails. You can expose a SPIRE OIDC endpoint at a URL, and we use the DNS from that URL to verify ownership. Then we issue certificates with SPIFFE SVIDs as the subject, rather than email addresses.

@dlorenc This looks interesting but since I don't already use SPIFFE it seems like it might be a big setup just to sign code, but I'll have to try it out.

I like the idea of a domain as subject but I agree its a bit of work to set up a SPIFFE trust domain to get this working. Instead of posting a public key and needing to maintain that private key over time (Like DKIM when you manage an email server) it might be better to think about supporting the DNS challenge ACME challenge like LetEncrypt and use short lived certificates like we currently do.

While it is some work to set up SPIFFE/SPIRE and OIDC, it encourages better security practices than self-management of the private key for a DNS-based approach. I'd love to see folks try out SPIFFE and see where the pain points are, and maybe we can help with tooling to make it simpler to set up.

Closing, would recommend looking into SPIFFE


php-cs-fixer not run

Description
The results of beautification are not what I expect.
Expected Results
The beautified code should have looked like:
<INSERT CODE HERE>

Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code does not look right!

Debug
Here is a link to the debug.md Gist: https://gist.github.com/3f42094a6f6e3caaf76f2864c8b1ae1c
Checklist

[ ] I have tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[ ] I have reloaded (or restarted) Atom to ensure it is not a caching issue
[ ] Searched for existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[ ] Generated debugging information and added link for debug.md Gist to this issue

Original File Path: /home/ujank/.atom/packages/atom-beautify/package.json

Looking at your debug.md, this is not a PHP file and is instead a JSON file being correctly processed.
Please generate a correct debug.md if you still need help.

Original File Path: /home/ujank/.atom/packages/atom-beautify/package.json

Looking at your debug.md, this is not a PHP file and is instead a JSON file being correctly processed.
Please generate a correct debug.md if you still need help.


TLS alert / internal error on connecting to Cloudant with OTP 21.2 OpenSSL 1.1.1a CouchDB 2.3.0

Expected Behavior
With OTP <IP_ADDRESS>, OpenSSL 1.0.2, and CouchDB 1.7.2, I can connect to any HTTPS replication server and have a secure connection to a verified host such as our service at Cloudant.
Current Behavior
Setting up the same configuration with OTP 21.2, OpenSSL 1.1.1a, and CouchDB 2.3.0 works in every other respect than setting up TLS connections to Cloudant (and possibly other secure hosts, but I tried with Cloudant).
couchdb: [error] 2018-12-20T14:15:37.151234Z<EMAIL_ADDRESS><0.974.2> -------- couch_replicator_httpc: auth plugin initialization failed<EMAIL_ADDRESS>{session_request_failed,"https://*****.cloudant.com/_session","*****",{conn_failed,{error,{tls_alert,"internal error"}}}}

Playing around with the [ssl] and [replicator] blocks in local.ini or even lowering security settings (e.g. to not check certificates at all) gave the same result.
Sniffing with Wireshark tells me that the local replicator returns that same error to the remote after it receives the remote certificate.
Workarounds I am thinking about are picking OpenSSL 1.1.0*, or OpenSSL 1.1.0* plus OTP 20.*, but I would rather be sure before I invest more time.
Kind regards,
jer

From @rnewson (with Cloudant):
11:30 <+rnewson> cloudant supports TLS 1.0,1.1,1.2,1.3 for sure, yeah
11:31 <+rnewson> I can't say if any version of erlang works correctly with openssl 1.1.1.
11:31 <+rnewson> (99%+ of replications from couchdb to cloudant are using < TLS 1.3 btw,
                 so it certainly works)
11:32 <+rnewson> only browsers support TLS 1.3 so far, by and large. so we only see TLS
                 1.3 connections for dashboard things.

Erlang itself doesn't have support for TLS 1.3 or OpenSSL 1.1.1 yet:
https://groups.google.com/forum/#!topic/erlang-programming/9sRGyfkK9Io

"no promises but planned for erlang 22"

Not sure there is anything for us to do here since this is an Erlang problem, not a CouchDB problem.
Recommend staying with 1.1.0 or 1.0.2. We'll ensure things work for TLS 1.3 when Erlang 22 is out.

As a reminder, if you are working with Cloudant, and have an issue connecting to cloudant, you can file a support ticket with your account name, etc. - this isn't Cloudant tech support here ;)

I could reproduce this with any HTTPS connection if you like. Cloudant is the factor that did not change.

lib/crypto/c_src/crypto.c:#if OPENSSL_VERSION_NUMBER >= PACKED_OPENSSL_VERSION_PLAIN(1,1,1)
lib/crypto/c_src/crypto.c:#if OPENSSL_VERSION_NUMBER >= (PACKED_OPENSSL_VERSION_PLAIN(1,1,1) -7) \
lib/crypto/c_src/crypto.c:# if OPENSSL_VERSION_NUMBER >= (PACKED_OPENSSL_VERSION_PLAIN(1,1,1))
lib/crypto/c_src/crypto.c:#if OPENSSL_VERSION_NUMBER >= (PACKED_OPENSSL_VERSION_PLAIN(1,1,1)-7)

Perhaps OpenSSL support in OTP 21.2 is incomplete.

CouchDB 2.3.0 explicitly enabled support for OTP 21 but I know of no one actually running that in production yet.
The fact is that any {tls_alert,...} is deep within Erlang's ssl application and there's nothing we can do about it. If you want, you can file an issue upstream with Erlang here: https://bugs.erlang.org/
If you're able to get SSL working with OTP 21 and OpenSSL 1.1.0 then I'd definitely consider that.
The only comment about OpenSSL 1.1.1 support in 21.1/2 is OTP-15133 and  OTP-15094 which enhance the internal Erlang ssh application to support new public key exchange methods. My guess is they didn't test if/how this broke SSL support - which sadly is very common, Erlang has had a number of serious SSL bugs in the past.
FYI TLS 1.3 support was only added to Erlang on 2 Nov as part of OTP-15310, and hasn't made it into any release yet: https://github.com/erlang/otp/commit/9c33f00f78724ce0f68fef1dfc6ab4810d8c45f18 Not sure if this is related.


bug probably BN_is_prime_ex - wrong result for 1486 bit prime

Dear all, I am not sure about the following, but it looks like a bug .. please kindly check :
$ openssl prime -checks 5 -hex 200e937df7097e015a87f4481dd4c8ac693998671b54b40646635b32ec99559659800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004c99d9b
...... is not prime
$ openssl version
OpenSSL 1.0.2j-fips  26 Sep 2016
Tried (attached) is_prime_test.c  in openssl-1.1.0b/test (compiled on Fedora 24 x64 through ./config -fPIC && make)
$ gcc is_prime_test.c ../libcrypto.a ../libssl.a -ldl -lpthread
$ ./a.out
ERRR BN_is_prime_ex ..long..(0)
ERRR BN_is_prime_ex ..long..ctx..(0)
===end===
$ gcc --version
gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
Tested with openssl from git
$ git branch -a

master
and the result is wrong as well.

Please note it works fine with  openssl-1.0.1u/test
$ gcc is_prime_test.c ../libcrypto.a ../libssl.a -ldl
$ ./a.out
===end===
And with python + gmpy2 fine as well :
x = (0x200e937df7097e015a87f4481dd4c8ac693998671b54b40646635b32ec995596598 << 1220)+0x4c99d9b
In [56]: %time gmpy2.is_prime(gmpy2.mpz(x),5000)
CPU times: user 5.12 s, sys: 0 ns, total: 5.12 s
Wall time: 5.13 s
Out[56]: True
is_prime_test.c.zip

When I run you openssl prime command, it always returns "is prime" for me, both with 1.0.2j and 1.1.0b

Your test program also works fine with both 1.0.2j and 1.1.0b

I can confirm openssl-1.0.2j "prime" function returns proper result on my laptop.
It is strange issue, I suspect the reason may be some fancy new instructions or gcc6.x quirks.
$ ldd openssl-1.1.0b/test/a.out
linux-vdso.so.1 (0x00007ffd93561000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f0cd9b18000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f0cd98fc000)
libc.so.6 => /lib64/libc.so.6 (0x00007f0cd9539000)
/lib64/ld-linux-x86-64.so.2 (0x000055d6af480000)
just to be sure, reinstalled shared libs
$ dnf reinstall glibc
The result is still wrong.
CPU with incorrect result
$ grep -E "(flags|name)" /proc/cpuinfo | head -2
model name	: Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp
CPU with a correct result
model name	: Intel(R) Core(TM) i5-3360M CPU @ 2.80GHz
flags	 missing ::: pdpe1gb art sdbg fma movbe abm 3dnowprefetch intel_pt tsc_adjust bmi1 hle avx2 bmi2 invpcid rtm mpx rdseed adx smap clflushopt xsavec xgetbv1 hwp hwp_notify hwp_act_window hwp_epp
flags not present in i5-6600 ::: epb
Skylake bug discovered with Prime95 using AVX instructions may be a connection : https://www.extremetech.com/computing/220953-skylake-bug-causes-intel-chips-to-freeze-in-complex-workloads

Have you run the test suite? Does it report any other issues?
Note that I'm not seeing any issues with gcc 6 myself.

$ make test
make depend && make _tests
make[1]: Entering directory '...../openssl-1.1.0b'
...
skipped: md2, rc5, heartbeats - not supported by this OpenSSL build
...
All tests successful.
Files=86, Tests=464, 26 wallclock secs ( 0.26 usr  0.07 sys + 20.69 cusr  5.92 csys = 26.94 CPU)
Result: PASS

Tested again with latest openssl-1.1.0c
is_prime_test.c does not return ERR on my desktop i5-6600
so this issue can be closed after 1.0.2 is corrected.

Fix was committed to 1.0.2 as 57c4b9f6a2f800b41ce2836986fe33640f6c3f8a. For reference, it was adx thing in /proc/cpuinfo terms. Thanks for report. Closing.


impossible to pass the test 'The anchor tag color should remain black' even though I didn't change it

Hello,
It seems impossible to pass a test "The anchor tag color should remain black, only add CSS rules for the :hover state." I just added a following strings below the existed link styling:
  a:hover {     color: blue;   }
I didn't change anything existed.
Challenge - https://learn.freecodecamp.org/responsive-web-design/applied-visual-design/adjust-the-hover-state-of-an-anchor-tag
Here is a screenshot

Maybe change the hexidecimal #000 to “Black”?

I had to use chromium to pass the test, it wouldn't work in firefox for the same reason as stated in the first post.
I did try changing #000 to black to no avail.

yes! i couln't solve this in firefox but i was able to run this in googl chrome!!

I can vouch I've done the entire Responsive Web Design course on Firefox, and could pass every challenge/project.
I've just tested this solution now, and it's working for me. 🤔
@pandichitra If you have time, would you be able to elaborate on what actually failed for you?

@SethFalco yeah i really don't know why ? But I could find the same problem as mentioned by @KemPavel. Once I tried doing it in chrome it didn't mention any all Passed .

I am going ahead and locking this conversation, because this issue is old, and the platform/tests have changed a lot.
Please feel free to open a topic on the forum, or a new issue. Thank you.


Make tests less brittle w.r.t. function parameter evaluation order

Because of the way that we define the ASTs for tests, e.g. "new If( , , )", the order in which AST elements get created is unspecified. Since most tests rely on comparing Nodes' uniqueID which increments sequentially, this makes the tests very brittle.
The brute-force way of solving this would be to introduce new variables for each parameter, however this would make the code very hard to read.
Instead, a cleaner solution would be to implement a parser that translates an AST from a text file into a C++ Ast object with deterministic initialisation order.

This is also useful for tests that at the moment depend on the result of a visitor (e.g., see 20724c5ea1724b6d9c8c3894fc6410d24c124b2d) as every time the visitor is changed, also the test will break.
We could use the serialization/deserialization feature of the already integrated nlohmann/json library to save and restore ASTs. Probably, this might require to extend the current JSON output by additional information, e.g., node IDs to describe the detailed state.

This has been addressed by the introduction of the parser


An unexpected error occurred during test run

Hello,
I'd like to run test.yaml as a code and I get below error during test execution.
When I run the same test from GUI instead of NeoloadCLI it works.
neoload run --as-code test.yaml --name TestCLI
Do I missed something when using NeoloadCLI ?
Regards
Mateusz
Starting dynamic infrastructure...
Infrastructure starting: 10%
Infrastructure starting: 20%
Infrastructure starting: 20%
Infrastructure starting: 20%
Infrastructure starting: 20%
Infrastructure starting: 20%
Infrastructure starting: 35%
Infrastructure starting: 52%
Infrastructure starting: 52%
Infrastructure starting: 52%
Infrastructure starting: 54%
Infrastructure starting: 62%
Infrastructure starting: 68%
Infrastructure starting: 68%
Infrastructure starting: 72%
Infrastructure starting: 72%
Infrastructure starting: 72%
Infrastructure starting: 83%
Infrastructure starting: 83%
Infrastructure starting: 85%
Infrastructure starting: 86%
Infrastructure starting: 86%
Infrastructure starting: 97%
Dynamic infrastructure started.
Controller preparation
Lock controller nlca-prod-c15fb641-5b7c-4204-8cc0-2cdc3f717c8c-4741-0-vm
Waiting lock for controller nlca-prod-c15fb641-5b7c-4204-8cc0-2cdc3f717c8c-4741-0-vm (0/8)
Load generators preparation
Lock load generators : nllga-prod-c15fb641-5b7c-4204-8cc0-2cdc3f717c8c-4742-0-vm
Waiting lock for load generators nllga-prod-c15fb641-5b7c-4204-8cc0-2cdc3f717c8c-4742-0-vm (0/8)
Sending project to controller
Sending load generators details to controller
Sending additional as-code file
Starting infrastructure and test

An unexpected error occurred
Unlocking controller : nlca-prod-c15fb641-5b7c-4204-8cc0-2cdc3f717c8c-4741-0-vm
Unlocking load generator : nllga-prod-c15fb641-5b7c-4204-8cc0-2cdc3f717c8c-4742-0-vm
java.lang.IllegalStateException: controller exited unexpectedly
at com.neotys.nlweb.bench.runtime.service.task.start.StartBenchCheckingTask.lambda$doExecution$0(StartBenchCheckingTask.java:63)
at rx.internal.operators.CompletableFlatMapSingleToCompletable$SourceSubscriber.onSuccess(CompletableFlatMapSingleToCompletable.java:61)
at rx.Single$18.onNext(Single.java:1911)
at rx.observers.SafeSubscriber.onNext(SafeSubscriber.java:134)
at rx.internal.producers.SingleDelayedProducer.emit(SingleDelayedProducer.java:102)
at rx.internal.producers.SingleDelayedProducer.setValue(SingleDelayedProducer.java:85)
at rx.Single$1$1.onSuccess(Single.java:80)
at rx.internal.operators.SingleOperatorOnErrorResumeNext$2.onSuccess(SingleOperatorOnErrorResumeNext.java:63)
at rx.Single$18.onNext(Single.java:1911)
at rx.observers.SafeSubscriber.onNext(SafeSubscriber.java:134)
at rx.internal.producers.SingleDelayedProducer.emit(SingleDelayedProducer.java:102)
at rx.internal.producers.SingleDelayedProducer.setValue(SingleDelayedProducer.java:85)

Hello,
I think that this error is not related to NeoLoad CLI. To investigate, you should look at NeoLoad controller logs.
But this github repository is not the right place for support, I invite you to create a support case here.
Thank you


Zooming: disallowing any FOV change makes zooming impossible

Description
Using these settings:
<model-viewer
style="width: 100%; height: 100%;"
src="winter_time/scene.gltf"
camera-controls
auto-rotate
camera-target='0m 100m -40m'
min-camera-orbit='auto auto 50m'
max-camera-orbit='auto auto 1000m'
camera-orbit='5.14rad 1.03rad 50m'
field-of-view='60deg'
min-field-of-view='60deg'
max-field-of-view='60deg'

..I am unable to zoom at all. Note that the model, which I can't provide publicly, is quite large (~radius of 2000m/units)
Browser Affected

[x ] Chrome 80
[ ] Edge
[ ] Firefox
[ ] Helios
[ ] IE
[ ] Safari

OS

[ ] Android
[ ] iOS
[ ] Linux
[ ] MacOS
[x ] Windows 10

Versions

model-viewer: at HEAD

Thanks for reporting, @stevesan ! I'm interested to hear what you would expect to happen in this case.
@elalish curious to hear your opinion on this one as well.


Streaming data

I am trying to stream data from Rust to Dart.
I am listening to CAN frames and when I receive one, I post it into Isolate, but the problem is that data is not streamed to Dart, instead it is sent in batch after the function is completed. Because of this kind of behavior, I am trying to use a workaround on Dart's side where I call the function over and over again after I receive data from CAN, but it leads to missing some CAN frames which are really important. Here is the code on the Rust side:
extern crate mio;
extern crate mio_serial;

use allo_isolate::Isolate;
use futures_util::stream::StreamExt;
use tokio_socketcan::{CANSocket, Error};

#[no_mangle]
pub extern "C" fn read_data(isolate_port: i64) {
    read_can(isolate_port);
}

#[tokio::main]
async fn read_can(isolate_port: i64) -> Result<(), Error> {
    let isolate = Isolate::new(isolate_port);

    let mut socket_rx = CANSocket::open("vcan0")?;

    while let Some(Ok(frame)) = socket_rx.next().await {
        let data = frame.data();
        /*
         Here I perform some data manipulation
       */
        isolate.post(format!("{:?}", can_frame_map));
        break; // I had to explicitly add break here since it was not posting any values until function finishes
    }
    Ok(())
}

And here is the data listener class:
class DataListener {
  static setup() {
    native.store_dart_post_cobject(NativeApi.postCObject);
    print("Port listener Setup Done");
  }

  Stream listenData() {
    print('Creating receive port');
    final receivePort = ReceivePort();
    print('Starting listen port');
    native.listen_port(
      receivePort.sendPort.nativePort,
    );
    print('Returning stream');
    return receivePort; //It doesn't matter if I return receivePort and listen to it later or start listening straight away in the function. The behaviour is still the same
  }
}

This is the function on the Dart's side which calls for the listenData function:
static void readData(SendPort sendPort) async {
    DataListener.setup();
    while (true) {
      Stream<dynamic> canStream = DataListener().listenData();
      sendPort.send(await canStream.first); //Sending to another isolate for processing
     // Even without waiting for the first element of the stream, the behavior is the same. It is pretty much just a silly workaround
    }
  }

So I basically want to create an infinite loop for streaming data from Rust to Dart. Or is it even possible to do with Allo isolate?

Maybe this example helps you here on writing streams with allo-isolate
https://github.com/shekohex/rustystream

Maybe this example helps you here on writing streams with allo-isolate https://github.com/shekohex/rustystream

I see how this is working and actually managed to stream data from Rust to Dart, but only when I knew that data is coming and I was just sending some arbitrary data. The thing is that I am trying to stream data from CAN protocol to Dart, but I just want to keep listening to CAN and send it whenever there is data, and when there is no data, just don't do anything.
It looks like this:

I open the CAN socket
I listen to CAN
Whenever there is data on CAN, I send it. If there is no data, I just wait until it comes

I want the loop to be infinite and end whenever the Dart program finishes. I tried doing infinite loops on Dart's side and calling function over and over again, but it didn't help, since there is a small-time to pass data from Rust to Dart and process it in Dart, so in that time some CAN frames are skipped

Nevermind, just spawning another thread worked out :D


Required items in configuration file?

According to the code (e.g., this and this), the items are seemed to be optional. However, yaml-cpp 0.5.2 throws exception for the current implementation of Chimera at here (node.Type()).
yaml-cpp 0.5.2 creates a zombie node if the key doesn't exist (e.g., template_config["prebody"]), and the zombie node throws an exception when Node::Type() is called. This is the cause of the errors reported in #119.
I suggest that we perform the validity check in advance, and, if it's not valid, we print warnings and just return.

We should change the items to be optional.


Performance: Adds a LINQ optimization for member access in LINQ-to-SQL

Pull Request Template
Description
This optimization handles the common case of accessing a member (variable, field, property) in the ambient scope, as shown below:
var bob = "Bob";
users.Where(u => u.Username == bob);

In this scenario, we will attempt to avoid compiling a lambda expression to evaluate bob and instead rely on reflection member access to retrieve the constant value. This helps us avoid the global lock held by System.Reflection.Emit.DynamicMethod while constructing the dynamic method table, which alleviates a serious performance bottleneck on highly threaded systems. In particular, this helps avoid a pathological async-over-sync situation which can lead to thread pool exhaustion and hot-lock thrashing.
The goal of this change is to provide teams who face this problem with a reasonable means of optimizing their query code (use variables which hold pre-computed constants to avoid delegate compilations), instead of forcing them to rewrite their codebases to use stored SQL, or to implement some form of SQL caching.
Type of change

[x] New feature (non-breaking change which adds functionality)

/azp run

/azp run

@khdang and @sboshra and @timsander1 please review this PR.

/azp run

Thanks for getting this merged folks, I suspect this should have a pretty sizeable benefit for our user-base.


Import broken in jspm/systemjs

Not sure what is going on here, but I'm importing xterm.js via SystemJS and it fails horribly:
 GET XHR<EMAIL_ADDRESS>[HTTP/1.1 404 Not Found 1ms]
// many more...

Somehow the browserify bundle doesn't work correctly and it instead calls require from SystemJS.
Not sure what's going here.
To reproduce:

Install jspm
Create a new directory and run jspm init
jspm install npm:xterm
In your index.js, do import Terminal from 'xterm'
Load the page

It works when I use jspm instal github:sourcelair/xterm, in which case jspm doesn't even touch dist/xterm.js. I have absolutely zero idea why, and maybe I should be reporting this against jspm instead.

This seems to be a duplicate of #397, can you please try this using the latest version on master?

Ah, that would explain why it works when installing from GitHub. Thanks! (a new npm release would be great though :)

👍  nice idea: https://github.com/sourcelair/xterm.js/releases/tag/2.2.2


Add Subscribe

fixes #321
This PR adds the subscribing implementaion to the backend and frontend of the website, successfully showing toast for the purpose.

@param-code please increase the level of the PR

Great Job @haseebzaki-07 .

Thank you @param-code


New mwc-button and lit version to use lit 2.0

TemplateResult error when using lit-element 2.x (app-datepicker + mwc < 0.24) and a Lit 2.0 environment mixed
When is it possible to upgrade to Lit 2.0?

@axho Thanks for the issue. Let me work on that.


Hanging on ImageClient()

Ive been doing dev work with PyCharm and this library to work with a o3x100 camera.
IFM Assistant is able to access the camera fine.
Creating the Device object happens without dramas, but the minute I try to create an ImageClient object, python3 hangs until I opt to kill the process.
Have tried tracing it down, but unsure as of yet as to the origin (User error potentially)

The ImageClient has not been adapted yet to the O3X, and it is no surprise that it is not working as the data connections to O3D3xx devices are bidirectional whereas on O3X you cannot send commands to the camera, and that's where the client is hanging.
However, it is not hard to resolve: I have pushed a quick fix to the o3x branch (which I assume you are already using). The ImageClient class and along with it the examples image_grabber.py and image_viewer.py (requires the O3X application to output at least amplitude and distance image) should be working with an O3X.

Thanks for the pointer Christoph, still feeling my way through the dev
environment for this camera!
On Fri, 15 Dec. 2017, 8:22 pm Christoph Freundl<EMAIL_ADDRESS>wrote:

The ImageClient has not been adapted yet to the O3X, and it is no surprise
that it is not working as the data connections to O3D3xx devices are
bidirectional whereas on O3X you cannot send commands to the camera, and
that's where the client is hanging.
However, it is not hard to resolve: I have pushed a quick fix to the o3x
branch (which I assume you are already using). The ImageClient class and
along with it the examples image_grabber.py and image_viewer.py (requires
the O3X application to output at least amplitude and distance image) should
be working with an O3X.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cfreundl/o3d3xx-python/issues/5#issuecomment-351955728,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF0756xjeksKq0HaeYUlCFXsWMwA_CJaks5tAjpQgaJpZM4RC-o_
.


Annotations for rest-parameters are pretty much useless

Currently the extension writes out every annotation for rest parameters like this:

I'd say annotations for rest-parameters could just be disabled or toggled with an option.

It's won't be so irrelevant in TypeScript 4.0 with its labeled tuples


small set of patches

fixed windows symbol exports (e.g. mingw32)
fixed os2 symbol exports
added a watcom makefile targeting os2
added ATOMIC_INCR and ATOMIC_DECR for watcom compiler
eliminated signedness warnings from os2 code.

It's supported in recent MinGW. The proper way would be to rely on CMake to hide all symbols (C_VISIBILITY_PRESET property), it's smarter than a #pragma GCC visibility push(hidden) conditionally added.


In R scripts '\t' and '\n' were revised into '\t' and '\n'

You've done something weird here @chuan-wang - these changes were directly committed to the head SciLifeLab repository in commit e7e3fbc69df5bd9e09160fbe27c0d5960b41c2d7. The changes shown in this PR are also very strange.

I've added restrictions to this repo about who can push to the master branch to avoid this accidentally happening again in the future.


[Feature]: Show latest log when no deployment is active

Describe the feature
Currently, when a deployment is not active:
$ cargo shuttle logs
Error: could not automatically find a running deployment for 'jonaro00-test'. Try passing a deployment ID manually

Instead of having to copy+paste the latest deployment id, simply show the log of the latest deployment. If no deployments, then show the error.
Alternatively, add cargo shuttle logs --latest.
Suggestion or Example of how the feature would be used
No response
Duplicate declaration

[X] I have searched the issues and this feature has not been requested before.

Good idea! I prefer the --latest flag, but either is a big improvement in ergonomics.

/bounty 50

/bounty 50


Web - Forgot Password Page

After communicating with the backend team, we concluded to have the following flow for "Forgot Password" case.

[ ] The user will first request to reset their password. This will send them a mail with a verification URL.
[ ] The user will click on the URL, which will lead them to a "Create New Password" page, where they can simply create a new password and submit.

Both pages are done except for their business logic that connects them to the backend.(Waiting for endpoints)


Use DenseI64ArrayAttr for ops which already specialized the printing/parsing as DenseI64ArrayAttr (copy and update of #1658)

This PR is based on #1658. I rebased the commits onto main, resolved conflicts, and made necessary changes to code that had been added since the last rebase.
Since I was getting a lot of compilation failures after rebasing and I'm new to the project/MLIR, I decided to port each op one at a time and I gave each op its own commit.
Porting slice op required a lot of changes to testdata files. I wrote a Python script that used a regex to make the replacements:
r'(.*?)"stablehlo.slice"(.*?){limit_indices = dense<([^>]+?)> : tensor<(\d)xi64>, start_indices = dense<([^>]+?)> : tensor<(\d)xi64>, strides = dense<([^>]+?)> : tensor<(\d)xi64>}( : .*)'

This change partially implements #1578.
Special note for reviewers: because I split the original commit into multiple commits, I don't know if authorship will be appropriately reflected (the original change was made by @joker-eph). Please advise.

Thanks for doing all the heavy lifting! :)