[TypeChecker] Diagnose key paths with contextual type but no leading dot

If a Swift key path has root type inferred but does not have a leading dot, then diagnose it, because it's not valid. For example:
struct Foo {
  let property: [Int] = []
  let kp: KeyPath<Foo, Int> = \property.count // error
}

Resolves SR-12290
Resolves rdar://problem/59874355

@theblixguy @dan-zheng This is a modified version of https://github.com/apple/swift/pull/30164 which got reverted because Tensorflow relied on implicit type expressions. I think this problem should be addressed now because KeyPathExpr implicit generated for KeyPathIterable fields could set hasLeadingDot to true which would avoid a diagnostic. WDYT?

@swift-ci please smoke test

I think we’d want to keep information about the leading dot just to avoid mismatches in the future.

@swift-ci please test source compatibility


How to visualize the attention map in the paper?

The author adds a self-attention module in Sec3.3 of the paper. I want to visualize the attention map like Fig. 1. How to do it? Could you share the code?

We use the tool “pytorch_grad_cam” to display GradCAM, and you can refer to the code: "gradcam_display.py" and this repository: pytorch_grad_cam for details.


feature: use type exports in task service

Part of #212835
For testing, I enabled isolatedModules in src/tsconfig.json and checked that no error is shown anymore in taskService.ts.

Moved to https://github.com/microsoft/vscode/pull/212913


Add minutes of 18th April 2023 meeting

Signed-off-by: Gowtham Suresh Kumar<EMAIL_ADDRESS>

Since the context is a document on GitHub, I think that makes sense.

Yeah makes sense to me. Maybe I'll keep the name and next to it add the github usernames in brackets?


chore: add codespell to check typos

Add codespell to check typos
Add tox run -e lint script to run ruff & codespell
Fix finded by codespell typos
Run ruff check --fix
Update contributing.rst
correct integrations/base.py types

I like the proposed changes for pyproject.toml, also thank you for fixing typos, and some signature fixes look good. But I cannot agree with other changes, especially those which only affect code formatting


Add StackForge to Built With section

After jumping around to a few different frameworks, I decided that Semantic-UI-React is what I want to use. It completely powers the whole site from the server side rendered landing / marketing page all the way to the application itself.
Thanks for all the work you guys do!
https://www.stackforge.co

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1607   +/-   ##
=======================================
  Coverage   99.74%   99.74%
=======================================
  Files         141      141
  Lines        2398     2398
=======================================
  Hits         2392     2392
  Misses          6        6

Continue to review full report at Codecov.

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

Very cool, glad to have you!


🎛 Add initial contributor documentation for building Stimulus controllers

Now that there are a few Stimulus Controllers in the core code and more coming, it would be good to add a starting documentation for core team and other contributors to make more.
Pertinent section of the Wagtail docs
https://docs.wagtail.org/en/stable/contributing/ui_guidelines.html
New section between JavaScript & Multi-lingual about Stimulus.
Focus: It should not be a Stimulus guide, let's only link to the official documentation, it should be how Wagtail code uses Stimulus.
Contents: Should be based on RFC proposed documentation: https://github.com/wagtail/rfcs/pull/78/files
Audience: Confident with TypeScript, Jest, has read the Stimulus Docs at least once in full, has contributed at least two or more JS/TS changes to the core code.
Additional details
Attributes ordering

id, class and then data attributes
data-controller should be first, then data-action and then alpha sorting of all other data attributes
Wrap attributes to a new line if it is getting too long to be practical to read (however, be careful with failing unit tests)

This is the preferred approach, but will not be enforced at the linting level.
This way it is more readable - the primary goal here.
Areas to cover:

Add mention of Stimulus being a thing (with links to Stimulus website)
Comparing Stimulus usage with our other approaches (jQuery, React) (very simple)
When to use Stimulus - this may be tricky to define, see the RFC content
For reference, proposed docs in RFC: https://github.com/wagtail/rfcs/blob/main/text/078-adopt-stimulus-js.md#appendix-2---potential-documentation
Controller naming - keep it short, one word is best, but clarity is better
Think carefully about actions driving method usage and moving more 'control' over behaviour to what methods get called instead of things like 'modes' or 'options' too much in the controller values
Link to Jest and JS testing section of other docs page https://docs.wagtail.org/en/stable/contributing/developing.html#unit-tests-for-javascript

Assigning to myself to do a good first draft, and then @Lovelyfin00 will review / expand.


[WIP] Pull repo

@mihaidma I just want to find that appVeyor issue so adding this wip PR to let it run. It takes a while, lets look at this tomorrow.

@mcdonnelldean there was a generator test failing, not ready for PR yet as I want to update also the docs and add some tests

@mihaidma Good stuff so :D

@mcdonnelldean made changes, ready for PR

This is nice!


infracost: 0.10.37 -> 0.10.38

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/infracost/versions.
meta.description for infracost is: Cloud cost estimates for Terraform in your CLI and pull requests
meta.homepage for infracost is: https://infracost.io
meta.changelog for infracost is: https://github.com/infracost/infracost/releases/tag/v0.10.38
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.10.38 with grep in /nix/store/9w0xz8nchzynrfjvgd3d3lln7czbqfjg-infracost-0.10.38
found 0.10.38 in filename of file in /nix/store/9w0xz8nchzynrfjvgd3d3lln7czbqfjg-infracost-0.10.38

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

infracost

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9w0xz8nchzynrfjvgd3d3lln7czbqfjg-infracost-0.10.38 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A infracost https://github.com/r-ryantm/nixpkgs/archive/b6ad1fdba5927526eeca8c457ee8b3bc8964e0ad.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b6ad1fdba5927526eeca8c457ee8b3bc8964e0ad#infracost

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9w0xz8nchzynrfjvgd3d3lln7czbqfjg-infracost-0.10.38
ls -la /nix/store/9w0xz8nchzynrfjvgd3d3lln7czbqfjg-infracost-0.10.38/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

infracost

Maintainer pings
cc @davegallant @06kellyjac @kashw2 for testing.

Result of nixpkgs-review pr 323919 run on x86_64-linux 1

1 package built:

infracost


Consider a composite component API

I'd like to keep composite components as regular Python functions, but then it's difficult to display them in dev tools. In addition, it may be useful way to support content projection for these composite components as this provides a more flexible way of composing components together.

Done.


correct usage of bool arguments from command line

Description
When trying to convert any non empty string to bool, python returns True.

bool('False')
True

This means if a bool argument (--shuffle) has a default value of True, then passing --shuffle False will not set it to False.
Correcting this by converting the string argument given to bool with a custom function.
This is a fix with minimal change on user's end. Alternative (and the proper way) would be --shuffle and --no-shuffle. But that would require significant changes to the examples.
 I finished coding on this PR)
[x] All changes have test coverage
[x] For user-facing API changes, API doc string has been updated. For new C++ functions in header files, their functionalities and arguments are well-documented.
[x] To my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Comments

Refer description above
Fixes issues people have raised like https://github.com/apache/incubator-mxnet/issues/8875

I think the right way to do this is to use action=store_true

Updated

Rebased

Looks good to go in, right?


workspace not indexed in meilisearch

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: linux
- Continue: master( commit 503e0ebae446d528d44b15e0a90ad080ba9903bf)

In /server/continuedev/libs/index/indices/meilisearch_index.py I have added following debug

     async def add_chunks(self, chunks: List[Chunk], index: Index, offset: int):
-        await index.add_documents(
-            [
+        print("add_chunks ****", index, offset)
+        documents =             [
                 self.chunk_to_meilisearch_document(chunk, j + offset)
                 for j, chunk in enumerate(chunks)
             ]
-        )
+        task_status = await index.add_documents(documents)
+        print("task_status", task_status)

Output
...
task_status task_uid=33 index_uid='rootplaycontinuesite_base_ctrhel9' status='enqueued' task_type='documentAdditionOrUpdate' enqueued_at=datetime.datetime(2023, 12, 5, 20, 45, 20, 63998)
XXXXXXXXXXXXXXXXXXXXXXXX DONE BUILD_INDEX

curl http://localhost:7700/tasks/33  | jq
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   735  100   735    0     0   717k      0 --:--:-- --:--:-- --:--:--  717k
{
  "uid": 33,
  "indexUid": "rootplaycontinuesite_base_ctrhel9",
  "status": "failed",
  "type": "documentAdditionOrUpdate",
  "canceledBy": null,
  "details": {
    "receivedDocuments": 15,
    "indexedDocuments": 0
  },
  "error": {
    "message": "The primary key inference failed as the engine found 2 fields ending with `id` in their names: 'id' and 'document_id'. Please specify the primary key manually using the `primaryKey` query parameter.",
    "code": "index_primary_key_multiple_candidates_found",
    "type": "invalid_request",
    "link": "https://docs.meilisearch.com/errors#index_primary_key_multiple_candidates_found"
  },
  "duration": "PT0.001105517S",
  "enqueuedAt": "2023-12-05T20:45:20.063998599Z",
  "startedAt": "2023-12-05T20:45:20.06468686Z",
  "finishedAt": "2023-12-05T20:45:20.065792377Z"
}

### Description

_No response_

### To reproduce

_No response_

### Log output

_No response_

thanks for sharing this. Meilisearch currently isn't critical to the codebase retrieval so this will likely have minimal effect, but we are also working on finding alternatives. I'll keep this issue updated as that progresses, but it might end up solved via subtraction

Also on the master version i think that is a mistake:
https://github.com/continuedev/continue/blob/main/server/continuedev/libs/index/indices/meilisearch_index.py#L22
actual id is document_id + :: + chunk index
https://github.com/continuedev/continue/blob/main/server/continuedev/libs/index/indices/meilisearch_index.py#L76 ()
but when added
id = int(chunk.digest, 16)

@victorserbu2709 We've now removed the dependency on meilisearch as of our latest VS Code pre-release, which means that this bug won't be possible.
It played such a minimal role in indexing (and wasn't improving performance) that it made more sense to use a native javascript library to power the @ files dropdown feature instead.


Including router which has a Mount on "/" does not work

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
from fastapi.applications import FastAPI
from fastapi.responses import FileResponse
from fastapi.routing import APIRouter
from starlette.routing import Route

frontend_router = APIRouter()

async def index_fallback(request):
    return FileResponse("static/index.html")

frontend_router.mount("/", Route("/", index_fallback))

app = FastAPI()
app.include_router(frontend_router)

Description
I expect being able to include a router which has applications mounted at the root.
The problem seems to be that starlette strips any leading slashes from Mounts such that the resulting path is "". For starlette itself this is no problem and it can handle those fine.
When calling include_router on a FastAPI instance it is however checked that either the prefix starts with (1a) and does not end with (1b) a slash or that every route has a non-empty path (2). The mount with an empty path is in violation of 2. Passing a prefix would solve this issue in most cases however when the router should not have a prefix this is not possible as a prefix of / would violate 1b.
https://github.com/tiangolo/fastapi/blob/f0388915a8b1cd9f3ae2259bace234ac6249c51a/fastapi/routing.py#L645-L657
Operating System
Linux
Operating System Details
Output of uname -a
Linux thinkpad-e570 5.15.13-200.fc35.x86_64 #1 SMP Wed Jan 5 16:39:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
FastAPI Version
0.72.0
Python Version
Python 3.10.1
Additional Context
The minimal example is obviously not close to real world usage. My concrete use case is that I would like to mount StaticFiles to a router which has a few other routes to override some special paths.

Minimized variant of my use case
from fastapi.applications import FastAPI
from fastapi.responses import FileResponse, PlainTextResponse
from fastapi.routing import APIRouter
from fastapi.staticfiles import StaticFiles
from starlette.routing import Route

api_router = APIRouter()

@api_router.get("/users/{username}")
async def user(username: str):
    return PlainTextResponse(f"Hello '{username}'")

frontend_router = APIRouter()

async def index_fallback(request):
    return FileResponse("static/index.html")

# one example for a path which should not be served by StaticFiles
# in this case html=True could be passed to StaticFiles but in our case there are other paths
# for which this would not work
frontend_router.mount("/", Route("/", index_fallback))
frontend_router.mount("/", StaticFiles(directory="static"), name="static")

app = FastAPI()
app.include_router(api_router, prefix="/api")
app.include_router(frontend_router)

Mounting the StaticFiles instance to the app works around this issue though it is not an optimal solution.
Furthermore it is possible to archive the same result in starlette without any problems or workarounds.

Starlette implementation of the above
from starlette.applications import Starlette
from starlette.responses import FileResponse, PlainTextResponse
from starlette.routing import Mount, Route, Router
from starlette.staticfiles import StaticFiles

async def user(request):
    return PlainTextResponse(f"Hello '{request.path_params['username']}'")

api_router = Router(
    routes=[
        Route("/users/{username}", user),
    ]
)

async def index_fallback(request):
    return FileResponse("static/index.html")

frontend_router = Router( # this works without any problems
    routes=[
        Route("/", index_fallback),
        Mount("/", StaticFiles(directory="static"), name="static"),
    ]
)

app = Starlette( # this also works without any problems
    routes=[
        Mount("/api", api_router),
        Mount("/", frontend_router),
    ]
)

@septatrix You are correct that you cannot do this through a router, but you can just add a route to the application itself and define it to use \.   The example can be seen here: https://fastapi.tiangolo.com/tutorial/first-steps/

What about adding avaluating the len of path? It seems to be working fine
from typing import Any, Callable

from fastapi import APIRouter as FastAPIRouter
from fastapi.types import DecoratedCallable

class APIRouter(FastAPIRouter):
    def api_route(
        self, path: str, *, include_in_schema: bool = True, **kwargs: Any
    ) -> Callable[[DecoratedCallable], DecoratedCallable]:
        if path.endswith("/") and len(path) > 1:
            path = path[:-1]

        add_path = super().api_route(
            path, include_in_schema=include_in_schema, **kwargs
        )

        alternate_path = path + "/"
        add_alternate_path = super().api_route(
            alternate_path, include_in_schema=False, **kwargs
        )

        def decorator(func: DecoratedCallable) -> DecoratedCallable:
            add_alternate_path(func)
            return add_path(func)

        return decorator

add_api_route instead of mount  like frontend_router.add_api_route('/', index_fallback) because add_api_route` create Route object internally and mount method not overrided by fastAPI ist come from starlette

use add_api_route instead of mount like frontend_router.add_api_route('/', index_fallback) because add_api_route create Route object internally and mount method not overrided by fastAPI its come from starlette

Thanks, but that does not seem to support arbitrary ASGI apps. It not clear to me why the prefix check disallows my above example and I cannot think of a case where it would lead to problems if it were to accept the conditions in my example.

mount method need ASGI app not Route object, if you try with ASGI app it is work
from fastapi import FastAPI
app = FastAPI()

@app.get("/test")
async def test():
    return 'test'

app2 = FastAPI()

@app2.get("/test2")
def testapp2():
    return 'test2'

app.mount("/", app2)

mount method need ASGI app not Route object, if you try with ASGI app it is work

Yes but if I mount an ASGI app on "/" of an APIRouter and then include that router in the app it will raise an exception.

i got it, mount object return blank path and include_router raise that. i try something here: https://github.com/tiangolo/fastapi/pull/5371

fixed in this pr: https://github.com/tiangolo/fastapi/pull/5373

@BilalAlpaslan mounting on root works for me - at least the functional part of the API. In the Swagger UI docs however, I can't see the operations of the subapplication when mounting on root.


fix: Invalid function argument error when using lookup method

Description
Use try rather than lookup method to avoid default value type error
Motivation and Context
If we want to use merge or ternary expression to conditionally declare endpoints, lookup method would raise an error due to a null value will be returned, which is a different type of default value []

Breaking Changes
No breaking changes
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

please start with a reproduction

please start with a reproduction *in an issue

Hi @bryantbiggs , thanks for your prompt response. I've opened an issue and included the code that reproduces the problem. Additionally, the reproduction code has been added to the examples in this PR. Please take another look and review it if you think it warrants attention. Thanks!


[BUG] Constants defined in .pxd are not available in .pyx?

Describe the bug
As title.
To Reproduce
# test_def_scope.pxd

DEF MY_CONST = 25
cdef int my_const = MY_CONST
my_const2 = 25

# -------------------
# test_def_scope.pyx

# distutils: language = c++

def get():
    print(my_const)
    print(my_const2)

On command line:
$ cythonize -i -3 test_def_scope.pyx
$ python -c "import test_def_scope; test_def_scope.get()"

I got an unexpected output:
0
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "test_def_scope.pyx", line 5, in test_def_scope.get
    print(my_const2)
NameError: name 'my_const2' is not defined

Expected behavior
The output should be
25
25

I hope I am not being silly due to staying up late...😅
Environment (please complete the following information):

OS: Linux
Python version: 3.8.10
Cython version: 0.29.24

I believe this issue is:
cdef int my_const = MY_CONST

is a C declaration - it declares a C level variable with an initial value of MY_CONST.
my_const2 = 25

is an executable bit of Python code. It creates the Python variable my_const2 by assigning to the module dict. It is not something that Cython can usefully use at compile time, and therefore it doesn't belong in a .pxd file.
cdef object my_const2 = 25

would probably work fine (I haven't tested it though), but wouldn't be accessible from Python.
Essentially it's the usual issue that Cython is a weird mix of run-time and compile-time features and it's sometimes hard to know which one you're using.
I'll tag this as "error reporting" since we should probably tell you that it shouldn't be in the pxd.

Hmmm... That's odd @da-woods, I am getting more confused. Quoting your notes from our earlier discussion:

Module-level cdef variables can always be cimported
Module-level variables defined in the normal Python way (abc = "something", no cdef) can always be imported, and are Python objects.

I'd expect both my_const and my_const2 to work. What makes the situation different?

Note: I also tried creating another module (say test_def_scope_blahblah.pyx) and cimporting/importing my_const/my_const2 from test_def_scope, and the result is the same.

What makes the situation different?

The .pxd file is only for things that can be  cimported. It does not generate any code that is run at module import time[*]. Therefore the Python variable my_const2 is never initialized.
[*] This isn't 100% true, but is pretty close.

Thanks, @da-woods. This is very subtle. Also, the reason that my_const is still unclear to me.
Moreover, @kmaehashi has kindly reminded me that if I declare my_const as an enum, so instead of
cdef int my_const = MY_CONST

we do
cdef enum: my_const = MY_CONST

it'd work just fine. Something must be wrong here...

I think I'd missed the point slightly and thought that the my_const part of the example did work.... Sorry! I'd have to look and work out what's happening, but it could be that Cython splits it into declaring the variable at compile time, then running the assignment in the module init function at runtime (and the latter doesn't happen in a pxd)
The enum should definitely be fine - that has to be set at compile-time.
If the others don't work then we probably should be diagnosing them better - it's obviously unhelpful to accept code then ignore it


Create settings page

Description

Create the settings page
Acceptance Criteria

[ ] Settings page UI should be consistent with mocks
[ ] Settings page should be responsive
[ ] All settings page endpoints should be hooked up (NOT including "log out" - this should be part of the auth issue )
[ ] Settings page toggles dark/light mode

Implementation details

Log out should be done with an Auth issue, or if not, done by the person who did the auth issue.
Testing notes

Please add tests to ensure all of the above A/C works as intended

@lanxdrey19 please review ticket

LGTM :) Sorry for late reply.


Add pytest workflow

Workflow yml copied from: https://github.com/ministryofjustice/rd-service-catalogue/blob/main/.github/workflows/test_pkg.yml
No changes to code functionality, the code changes are only linting.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Fix Vagrant/Ansible provision

This patch does a number of things:

Uses RVM's ansible-galaxy role to install MRI 2.3.2
Installs rvm as a global command (can be run as any user, including as vagrant)
Makes sudo usage opt-in behaviour, rather than default
Removes deprecated sudo: usage and replaces it with becomes:

There's also a committed whitespace whoopsie in Vagrantfile. Sorry about that. 😕

Lovely work!


Question: Why does WinUI use so much memory?

Based on the tests done here: https://github.com/Noemata/XamlBenchmark
WinUI uses vastly more memory than WPF or UWP.  It also appears to leak memory resources to a significant degree.
For the same test WPF uses 100MB, UWP uses 45MB and WinUI tops out at 700MB without relinquishing most of what was taken.
Why?

I think there was a mention of a few MB more memory as WinUI has to render to a Swapchain rather than the OS compositor layer.

@mdtauk , I suggest you have a look at the benchmark rather than speculate.  WinUI is leaking a lot with exactly the same code used by UWP, and very similar code to WPF.  Just one problematic detail.  A 10x memory utilization increase over UWP is unsustainable.  45MB versus 700+MB is not a few MB difference!
We need more hard facts and less speculation in these discussions.  It's like the Pivot discussion, no facts just a lot of speculation and unsubstantiated declarations, when it would be very easy for Microsoft to publish stats of usage on GitHub or concrete details about development resources required for supporting a given feature.

What's also noteworthy, Microsoft is not reaching out to the community for support.  The Pivot control just happens to be a really good example of that.  Microsoft could have given the code and styles out to the community, as is.  We would have happily taken on the task of updating the styles and improving the code for reintegration were it truly such a large resource drain for Microsoft.  Obviously, Microsoft internal politics, motivations and objectives were more important criteria to appease than the needs of UWP/WPF developers.
I don't think the community can help itself beyond shining a light on what's important until Microsoft decides to be Open (Source).

I suspect that a big portion of this is the known C#winrt leak. @Scottj1s

I'll be missing .NET Native a lot...

@mdtauk , I suggest you have a look at the benchmark rather than speculate. WinUI is leaking a lot with exactly the same code used by UWP, and very similar code to WPF. Just one problematic detail. A 10x memory utilization increase over UWP is unsustainable. 45MB versus 700+MB is not a few MB difference!
We need more hard facts and less speculation in these discussions. It's like the Pivot discussion, no facts just a lot of speculation and unsubstantiated declarations, when it would be very easy for Microsoft to publish stats of usage on GitHub or concrete details about development resources required for supporting a given feature.

I wasn't doubting your findings, just mentioning that the team has mentioned a slight increase, so that is what we should be expecting, not the 10 times increase you are seeing.

@mdtauk , looks like I've gotten a tad too accustomed to pushback from one specific source.  Sorry for the reactionary reply.

if you're seeing these numbers from C# it's likely to be the cswinrt leak

@asklar , hopefully it's just that.  The working set seems significantly bigger too (cursory observation).  We'll see.  It's easy to compare with this benchmark, so the next release of WinUI should be significantly better on perf and memory footprint.

@StephenLPeters , any word on when this will get resolved?  The GA release is still leaking memory in a big way.

@Noemata the memory leaks have been fixed in C#/WinRT 1.2, and will be part of an upcoming update.
https://github.com/microsoft/CsWinRT/issues/413

@angelazhangmsft , fantastic!


[Internal] Hierarchical Directories for Components

Overview of Proposed Changes
We should add hierarchical directories for the components to remove any issues that arise from identical naming and also to prevent all components being dumped in the same folder. This will allow for a better organisation structure that will be easier to maintain in the future.
Details
Highest Level Folders in the Components directory should refer to different pages, and subsequent component hierarchy should be represented in sub-folders as needed.

Could you provide an example of a file tree with your proposed changes?

Could you provide an example of a file tree with your proposed changes?

Components:
|   Home Page:
|   Content Viewer Page:
|   Side Bar:
|   Content Viewer:
|   Header:
|   Title.js
|   Date.js
|   Contributor.js
Something like this.
For sub-directories for issues, it would be upto whoever is working on the issue to devise if sub-directories are needed. So for the Content Viewer, I might add a Header Directory as it might make sense to further group components inside the Content Viewer.

It might also make sense to include a matching hierarchical structure in the Style folder for the style sheets, since the same naming and organisational issue would arise there.


Testing results in simulation

Hey @j96w
Awesome paper
I am trying to imitate my own choice of tasks
I am done with data collection and training, and now I want to emulate it in simulation before trying it out on actual leap hand.
Any thoughts on how one can test DexCap results in simulated environment (something like Issac, Gazebo..)?
Thanks

Hey,
Just to give you an update,
I went ahead with using Webots.
I'm done with the Webots and controller setup, and now looking to attach a ROS node for inference.
https://github.com/j96w/DexCap/assets/46760063/7eac9e0a-d354-4295-ad18-2afb63c0dfa1
If you have any suggestions, please let me know :)
Thanks

Hi @0xcuriousapple, thanks for sharing these! A simulator is definitely helpful. We also considered it earlier, but since DexCap collects human data in the real world, we would need an additional process to build a "digital twin" in the sim to replay the collected human data. How do you plan to handle the real-to-sim gap? Or are you just looking for a teleoperation setup in the sim? DexCap is designed to collect data without a robot (so it's not directly designed for teleop).


Separate definition of padding length

I'm working to implement the parameter sets specified in the draft version of NIST Special Publication 800-208.
The reference implementation of XMSS currently assumes that n bytes of padding is used for the prefix in the functions prf, hash_message, thash_h, and thash_f. While this is the case for all of the parameter sets in RFC 8391, the draft version of NIST Special Publication 800-208 specifies parameter sets in which the amount of padding is different than n.
This PR allows for the padding length for a parameter set to be specified separately from n.

Thanks! Looks good to me!


Some images cannot be displayed correctly when use app:srcCompat=

As shown in Image 1, FlutterFragmentActivity extends FragmentActivity instead of AppCompatActivity, therefore, in our code, we should use android:src= instead of app:srcCompat= to load images.

Hi @Waylon-Firework,
Could you please provide a completed and minimal reproducible code sample so that we may verify this? Also, please provide the output of flutter doctor -v as well.
Thank you!


Limit file size to 75 kb

File content may only be send for files <= 75 kb (76800 bytes).
Previously a limit of 1 megabyte was used.

Done in #188.


Memory session is not persisted (on RPi Arm)

Hi, I have an issue with the memory session.
It works when I am testing on Ubuntu at x64, however it does not on Arm Raspberry.
I am using a simple password only authentication to protect the view with the MemoryStore:
let store = MemoryStore::new();
let secret = rand::thread_rng().gen::<[u8; 128]>();
let session_layer = SessionLayer::new(store, &secret);

(i guess it is straight from the examples)
Then in my login endpoint I simply do:
session.insert("auth", true)
        .expect("Session write error!");

And the expect is not called - so the session mechanism works. (which I confirmed by printing it to the console at this point).
But, when I try to read the session in the protected endpoint I get a None value:
    if !session.get("auth").unwrap_or(false) {
        return Redirect::to("/login").into_response();
    }

(on Raspbian, on Ubuntu it is fine - I get the proper session state)
I am not sure if the issue is not coming from the async-session crate - but have no idea at the moment how to figure it out.
I wonder what are the differences between those platforms that can cause that. I mean probably on the Pi the memory state is dropped or not properly shared between the async calls (?)

You may want to try to set a debug brakepoint after the insert call and check if the memory is modified. Then another one next to the get and check if the same memory is read.

let secret = rand::thread_rng().gen::<[u8; 128]>();

This generates a new secret upon each run of the application--this probably isn't what you want if you plan to restart the process and continue with prior sessions.

Please let us know if setting your secret to a static value does not resolve this, otherwise I'll close this for now.


HW2

Questions 1 and 2 are uploaded.

hi @Mahsa-kz, the changes in this pull request is empty.
https://github.com/fangq/BIOE5060_Fall_2024/pull/16/files
I am closing this one - please do not create new pull requests. just go back to your patch-2 branch, and continue making changes - make sure you add the missing files and push your changes to your github. It should then show up in #14

hi @Mahsa-kz, the changes in this pull request is empty.
https://github.com/fangq/BIOE5060_Fall_2024/pull/16/files
I am closing this one - please do not create new pull requests. just go back to your patch-2 branch, and continue making changes - make sure you add the missing files and push your changes to your github. It should then show up in #14

Hi,
I was not able to access patch-2 again, but I had uploaded everything in the main branch. Is that okay?

hi @Mahsa-kz, the changes in this pull request is empty.
https://github.com/fangq/BIOE5060_Fall_2024/pull/16/files
I am closing this one - please do not create new pull requests. just go back to your patch-2 branch, and continue making changes - make sure you add the missing files and push your changes to your github. It should then show up in #14

Hi, I was not able to access patch-2 again, but I had uploaded everything in the main branch. Is that okay?

I am sorry to ask, but can you see my uploads in the main branch or I should have requested a pull there?

what branch are these changes made? you need to create a pull request from that branch against my repository.
because your previous Pull request #14 is from branch branch-2, so, alternatively, if you can add your changes to branch-2, then, the #14 will show your changes automatically.

additional tutorials on creating PR can be found here
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
https://www.youtube.com/watch?v=nCKdihvneS0&t=108s
https://www.youtube.com/watch?v=jRLGobWwA3Y

what branch are these changes made? you need to create a pull request from that branch against my repository.
because your previous Pull request #14 is from branch patch-2, so, alternatively, if you can add your changes to branch-2, then, the #14 will show your changes automatically.

These were made to the main branch. I just requested a pull request for it.
Sorry for the inconvenience and thanks for your replies.

additional tutorials on creating PR can be found here
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
https://www.youtube.com/watch?v=nCKdihvneS0&t=108s
https://www.youtube.com/watch?v=jRLGobWwA3Y

Thank you. I will go through them.


Docs code example sidescroll on mobile

Describe the bug
When browsing the sveltekit docs on mobile I can not sidescroll the code example blocks.
Reproduction
Go to https://kit.svelte.dev/docs/accessibility#focus-management on an iphone. Try to sidescroll a code example.
Logs
No response
System Info
Ios 16.1.1

Severity
annoyance
Additional Information
No response

Even https://kit.svelte.dev/docs/modules#$app-navigation-goto on desktop overflows and can't be read


should treat React static defaultProps a non-null value

We already provide a default value if the props don't have this value, but flow still treats it as an optional type.
// Developing a React Native app
const deviceScreen = Dimensions.get('window');

class Foo extends React.Component {

  props: {
    offset?: number
  };

  // We provide a non-null default value for props if it is `undefined`.
  static defaultProps = {
    offset: deviceScreen.width * 0.75,
  }

  animate = () => {
  // We already provide a default value if the props don't have this value, but flow still treats it as an optional type.
  const value = this.props.offset - 70;
  //            ^^^^^^^^^^^^^^^^^ undefined. The operand of an arithmetic operation must be a number.
  }

  // ...
}

Check docs section about this.
"Note: You don’t have to mark your defaultProps as optional properties in your props. Flow knows how to handle them properly.".

@agentcooper thanks for the info. I missed it.
BTW, IMOH, I think flow should correct this issue if there is a default value for the optional type, doesn't it?
Developers might only check the type of the props to use a React component. If a prop is optional, the developer knows that he/she won't have to pass a value to the component.


feat: support stride in array_slice, change indexes to be0 based

Which issue does this PR close?

Closes #8784
Rationale for this change

What changes are included in this PR?
support array_slice with stride argument
array_slice(make_array(1, 2, 3, 4, 5), 1, 5, 2) --> [1, 3, 5]

Are these changes tested?

Are there any user-facing changes?

stalled until #8847 fixed

CI seems broken on this PR

stalled until #8847 fixed

Marking as draft to make it clear this PR is not waiting on review

Looks good to me @Weijun-H -- thank you
Can you confirm the behavior change to be 0 based indexes rather than 1 based indexes is intentional? I updated the PR title but I wanted to double check

array_slice is 1-index, not 0-index, which aligns with PostgreSQL and DuckDB. @alamb

Looks good to me @Weijun-H -- thank you
Can you confirm the behavior change to be 0 based indexes rather than 1 based indexes is intentional? I updated the PR title but I wanted to double check

array_slice is 1-index, not 0-index, which aligns with PostgreSQL and DuckDB. @alamb

Fixed


Request to Contribute to Documentation for v0.23.0 Changes (with Examples and Guides)

Hello,
I would love to contribute by updating the documentation to reflect the recent changes in PocketBase v0.23.0. I understand from the PocketBase project board that there is a task titled "New documentation reflecting the v0.23.0 changes (+ maybe section for examples/guides)." This task seems to be about enhancing the documentation with updated content related to the new release.
I’d be happy to take on this task and would like to ask if you can assign it to me. It would be really helpful if you could also clarify exactly what you're looking for in the documentation update.
What I Plan to Do:

Update the main documentation to reflect all significant changes introduced in v0.23.0.
Add a section with practical examples and guides, focusing on common use cases and best practices, to help users implement the new changes more effectively.
Provide any additional explanations on breaking changes or performance improvements in v0.23.0 that might affect developers.

Questions I Have:

Are there any specific areas of the documentation that you want me to focus on more than others (e.g., API changes, new features, migration guides)?
What are the most important points you would like highlighted in the examples and guides?
Are there any existing resources or guidelines I should follow to align with the project’s documentation style?

I believe these updates will greatly enhance the user experience and help both new and existing developers better understand and adopt the latest features of PocketBase.
Please let me know if I can be assigned to this task and any additional details or instructions you would like to include. I'm looking forward to contributing to the project!
Best regards,
Defree Harold

Thank you but I'm already working on the new documentation and I don't need help with it.
Providing guides and explanations how something should be done often takes more time than doing it on my own, especially when I'm not sure whether you are going to stick maintaning the changes in the long run (most users just abandon their opened issues and PRs; additionally I don't feel comfortable asking users to do work for me especially when I'm not paying for it).
Contribute because you want/need it, not just for the sake of the contribution.
Once the documentation for v0.23.0 is released (there are no ETAs yet) you are free to open PRs for the things you think that could be improved but don't expect me to create tasks for you.

Hello Ganigeorgiev,
Thank you for your prompt response and for clarifying your current work on the documentation. I completely understand your perspective and appreciate the effort you’re putting into it.
I want to assure you that my intention to contribute comes from a genuine desire to help improve the PocketBase project, not just for the sake of making a contribution. I recognize the challenges of collaborating in open-source projects, and I respect your decision to manage the documentation on your own.
If there are any specific areas in the future where you feel additional input could be beneficial, please don’t hesitate to reach out. I’m committed to supporting the project in any way I can, whether that’s through documentation, testing, or other contributions.
Thank you again for your hard work, and I look forward to the release of v0.23.0. I’ll keep an eye out for opportunities to contribute once the documentation is available.
Best regards,
Defree Harold


Correct content_hash in pdm.lock

Description
Correct content_hash in pdm.lock. Incorrect hash was merged by https://github.com/openshift/lightspeed-service/pull/485.
Type of change

[ ] Refactor
[ ] New feature
[x] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

/lgtm

/approve

to be clear this doesn't fix the fundamental problem we have which is that "make install-deps" should not be updating the lock file, it should be using the deps indicated in the lock file.
updating the lock file to pick up new deps(or new versions of existing deps) should be an explicit step someone has to undertake.


pcre: Fix postFixup script to resolve libs on darwin

Things done

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

[ ] NixOS
[x] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

At first I didn't realize the basic version isn't affected by this. Larger rebuilds should only be through qt5.

@discordianfish: I suppose you did test this works well on Darwin (even though you haven't checked the box)?

@vcunat Yes, I've just tested it and it builds. But now run into another issue so not sure if something was actually build against it yet.

Even if it doesn't, this change will most likely be useful anyway.

I tend to forget the Darwin differences, having no access to any myself...


Don't add Providers to injected ComponentRegistry if any concrete ins… [run-systemtest]

…tances exist.
This will break for users that depend on Providers being added to the component registry, but sounds very unlikely to affect anyone in practice.

My assessment was wrong. We are relying upon this functionality ourselves, where Container.requestHandlerRegistry contains both "concrete" handlers and  those created via a Provider. Definitely not unthinkable that a user app that takes all instances of a type assumes the same thing.


Thank you for sharing this excellent CNAB quickstarter for Mattermost! Interested in a guest blog post at mattermost.com/blog?

@MikeLarah @JamesDawson @squillace This is an unconventional reachout, but with a good intention :)
First and foremost, thank you for open sourcing this excellent CNAB quickstarter for Mattermost. I found about it through this tweet by you, Ralph Squillace: https://twitter.com/ralph_squillace/status/1296829626455658496
I'd love to promote your work with the Mattermost community. I'm curious if you were open to writing a guest blog post for mattermost.com/blog about the this package you built? Alternatively, I'd be happy to meet briefly and write a short article based on our conversation (with your reviews if preferred, of course).
This would make it easier for us to share your work with others who are looking for a quick package to get started on Azure.
Let me know if you're open to it?

@jasonblais thanks for reaching out - happy to discuss this further. I've followed you on twitter so we can carry on the conversation over DM.


[PE-D][Tester B] Meeting times that cross over from sunday to monday are invalid

Meeting times that start on sunday and end on the following monday are considered invalid.

Labels: severity.Low type.FeatureFlaw
original: Originalidk/ped#11

Update UG to mention limitation of weekly schedule.


Setup GitHub actions

Codecov Report

Merging #125 (41440c7) into develop (6e36ac9) will decrease coverage by 1.49%.
The diff coverage is 50.00%.

@@             Coverage Diff             @@
##           develop     #125      +/-   ##
===========================================
- Coverage    94.35%   92.85%   -1.50%
===========================================
  Files            8        8
  Lines         1470     1470
  Branches       253      253
===========================================
- Hits          1387     1365      -22
- Misses          44       66      +22
  Partials        39       39

Impacted Files
Coverage Δ

src/snps/resources.py
94.69% <50.00%> (-0.38%)
:arrow_down:

src/snps/ensembl.py
31.70% <0.00%> (-39.03%)
:arrow_down:

src/snps/snps.py
94.60% <0.00%> (-0.93%)
:arrow_down:

Continue to review full report at Codecov.

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


Is it correct to define concatAll for Magma?

Looking at the code for concatAll for Magma here, is it correct to define concatAll for Magma? This is how it is implemented right now in fp-ts:
export const concatAll =
  <A>(M: Magma<A>) =>
  (startWith: A) =>
  (as: ReadonlyArray<A>): A =>
    as.reduce((a, acc) => M.concat(a, acc), startWith)

The definition of Magma is only mentioning that concat ing 2 elements of a Set, should result in an element in that Set (Set is closed under the concat operation). But it doesn't necessarily an Associative operation. In that case we can have a scenario for Magma that:
concat(x, concat(y, z)) !== concat(concat(x, y), z)

If that is so, then from the definition of Magma, it seems that we cannot define a concatAll because the order of way we concat elements matter and we cannot abstract over it using a function! because function at the end of the day needs to concat elements in some specific order.
Do we even care for Magma s in TypeScript? I cannot think of any Magma s which are not already a Semigroup in TypeScript!
I really like to see what everyone thinks.

because function at the end of the day needs to concat elements in some specific order.

Outside of typeclass methods, the type signature of a function and its documentation is all that (softly) binds it.
What would a semigroup constraint/dependency change? The function could be - uselessly and misleadingly, but validly - defined as follows either way:
const concatAll = <A>(_M: Semigroup<A>):
  (constVal: A) => (ignored: Array<A>) => A => constant

Do we even care for Magma s in TypeScript? I cannot think of any Magma s which are not already a Semigroup in TypeScript!

I'd tend to agree with that. I've found no use for it except tripping up beginners.

@samhh Maybe I'm missing your point here. What is the constant in the concatAll generic function? Maybe constVal right? We cannot use anything else because that's the only A we have here for this generic function. But as you said this is not useful, and we are putting it in the library as a general tool (with an incorrect function name saying we are concatenating-all-of-something).
The way I look at it is, Magma has a concept that comes with its name. By having a concrete implementation of concatAll using function, we are implicitly assuming Associativity rule to it's definition, which then it's not a Magma anymore, and makes it a Semigroup.
In another words, to my opinion we cannot implement a concatAll function for Magma, unless we assume this Magma is a Semigroup, or we assume that this implementation is one of many ways to implement concatAll for a Magma. (compared to Semigroup which concatAll is a unique thing no matter how we implement it)


Fsdp inference checkpoints

Adding converter script for converting FSDP sharded state dict to HF model for inference.

Please add steps used for testing this out, including below along with output of your test for verification:

command to run and generate the pure fsdp checkpoint
command for converting the checkpoint to HF format for inference
command for running the inference

done.


1.21.3 Javacord unhandled exception upon Discord message

I'm currently testing 1.21.3 for production deployment and have come across an exception each time a Discord message is sent.
This exception occurs any time:

A user sends a message in the Discord channel.
The bot sends a message in the Discord channel.
A webhook message is sent in the Discord channel.

[19:23:10] [Javacord - Central ExecutorService - 1/ERROR]: Unhandled exception in a listener thread for <server name here>!
java.lang.NoSuchMethodError: 'void net.minecraft.server.MinecraftServer.method_18858(java.lang.Runnable)'
        at knot/net.replaceitem.discarpet.script.events.DiscarpetEventsListener.callEventOnGameThread(DiscarpetEventsListener.java:108) ~[discarpet-1.20.5-1.5.5.jar:?]
        at knot/net.replaceitem.discarpet.script.events.DiscarpetEventsListener.onMessageCreate(DiscarpetEventsListener.java:45) ~[discarpet-1.20.5-1.5.5.jar:?]
        at knot/org.javacord.core.util.event.EventDispatcher.lambda$dispatchMessageCreateEvent$272(EventDispatcher.java:9168) ~[org_javacord_javacord-core-3.8.0-732e24faa0947882.jar:?]
        at knot/org.javacord.core.util.event.EventDispatcherBase.lambda$dispatchEvent$12(EventDispatcherBase.java:215) ~[org_javacord_javacord-core-3.8.0-732e24faa0947882.jar:?]
        at knot/org.javacord.core.util.event.EventDispatcherBase.lambda$checkRunningListenersAndStartIfPossible$20(EventDispatcherBase.java:289) ~[org_javacord_javacord-core-3.8.0-732e24faa0947882.jar:?]
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
        at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]

Let me know if you would like or need further information.
As always, thank you for maintaining and updating this wonderful mod!

Just needed a rebuild because intermediary mappings changed. I just checked for 1.21.3 whether discarpet still works, and it did, so i just bumped the tagged version on modrinth. Turns out the old jars don't.
https://modrinth.com/mod/discarpet/version/OJii3RPI


Wrong ARP replies on second interface

Hi we have problem, our nodes have two interfaces: eno1 and eno1d1.
In simple configuration the second one is not used and have no ip-address, but it is up:
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback ce:b8:b2:5e:ec:7a brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether c6:54:0d:d6:6c:f0 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::f603:43ff:fedf:aa59/64 scope link
       valid_lft forever preferred_lft forever
3: eno1d1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 56:88:ec:cb:dc:08 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::5488:ecff:fecb:dc08/64 scope link
       valid_lft forever preferred_lft forever

When I install romana on this machine, this interface start answers on any arp's who-has requests from our network, example:
ARPING <IP_ADDRESS>
60 bytes from 56:88:ec:cb:dc:08 (<IP_ADDRESS>): index=0 time=675.037 msec
60 bytes from 56:88:ec:cb:dc:08 (<IP_ADDRESS>): index=1 time=130.956 msec
60 bytes from 56:88:ec:cb:dc:08 (<IP_ADDRESS>): index=2 time=690.810 msec
60 bytes from 56:88:ec:cb:dc:08 (<IP_ADDRESS>): index=3 time=470.697 msec
60 bytes from 56:88:ec:cb:dc:08 (<IP_ADDRESS>): index=4 time=98.594 msec
60 bytes from 56:88:ec:cb:dc:08 (<IP_ADDRESS>): index=5 time=302.442 msec
60 bytes from 56:88:ec:cb:dc:08 (<IP_ADDRESS>): index=6 time=598.341 msec

I'll repeat that this interface does not have any IP address at all.
But this behavior continues until I shut it down:
ip link set eno1d1 down

But even if I remove any romana containers, cleanup routes and iptables, then set this interface up, it is continue flooding our network.

Hi @kvaps Guessing that an interface without an IP  is confusing the Romana installer,  or its possible that this is just a bug or situation Romana does not handle properely. Any chance you can put an IP on this interface to see how it behaves? @cgilmour and/or @flashvoid might have some other suggestions.

Hi @chrismarino, thank for quick reply,
I was added IP from another subnet before setup, then installed romana. The result the same, nothing changed second interface eno1d1 continue flooding my network by fake replies.

@kvaps I don't know exactly how this can happen. Quite strange. Probably an iptable rule that's not set/working right. When you said you cleaned up iptables, did you delete table 10? That's where the Romana rules are set.

@chrismarino What was done after issue:
systemctl stop kubelet
docker stop `docker ps -q`
systemctl stop docker
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
ip route flush table 10
ip rule del from all lookup 10
ip link del romana-lo
ip link del dummy0

And this behavor is still there after all of this actions.

Hmmm.....way past my ability to diagnose. Need to hear back from others for more suggestions. Sorry. Send an email to<EMAIL_ADDRESS>if you want to get on Slack for lower latency replies.

I think romana can add some hidden ip <IP_ADDRESS>/0 on this interface in some different namespace.
Or somehow switch it to brodcast mode, I have no idea what is exactly romana doing with this interface and why - is second question ;)

Thanks, I'll do this!

I've tested debian and ubuntu with few kernels.
The problem ocurrs only with debian installation.
# uname -a
Linux m5c3 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux
# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Steps for reproduce:
kubeadm init
kubectl apply -f https://raw.githubusercontent.com/romana/romana/master/containerize/specs/romana-kubeadm.yml


Python 3 UTF-8 decode issue

Hi, we've found an issue with awsauth.py in get_canonical_string and created a patch downstream:
https://github.com/ceph/ceph/pull/21794

closed. duplicate.


Adjust code to start to use required fields logic that ffb added.

Helps address: https://www.pivotaltracker.com/story/show/186994206

removes a few input templates that were unused (duedate, fulldate, householdCheckboxFieldset)
removes text.html template from this code base and lets us default to the one in ffl (and therefore get required field functionality)
small tweak to the selectHelpNeeded.html to move some text into the card header.

For some reason this is not showing as required.


Merge interrupt history from Kubernetes into k8s.io/utils

This utility package is used by both server and client components to ensure
a critical region for execution can handle termination and other process
signals in a deterministic fashion. It is being moved out of k/k in order
to facilitate future moves of kubectl and other components out of tree.

@sttts @deads2k moved from
https://github.com/kubernetes/kubernetes/pull/68421

@smarterclayton compare commits. Something broke with your branch.

something broke on what?  the CLA?

@smarterclayton "my" github shows 13 commits, some from 2016 and 2017.

Yes, I'm preserving the history as requested in the HOW_TO_MOVE doc.

This interrupt handling meets the bar for complexity and utility from https://github.com/kubernetes/utils/blob/master/README.md .  I remember we debated unit tests for this at the time too and found that testing interrupts was impractical.
/lgtm
@smarterclayton gotta do something to pass the CLA.

All I really need is docs - I feel like this repo is a "promotion" of
sorts in our commitment to supporting the API, so we should be extra
pedantic here.  As someone familiar with UNIX, I would be surprised to
find HUP here, but it's OK as long as it is documented.  what you say
is right, a user could choose to not abend on HUP
On Tue, Sep 11, 2018 at 9:50 AM Clayton Coleman
<EMAIL_ADDRESS>wrote:

@smarterclayton commented on this pull request.

In interrupt/interrupt.go:

+See the License for the specific language governing permissions and
+limitations under the License.
+*/

+package interrupt
+
+import (

"os"
"os/signal"
"sync"
"syscall"
+)

+// terminationSignals are signals that cause the program to exit in the
+// supported platforms (linux, darwin, windows).
+var terminationSignals = []os.Signal{syscall.SIGHUP, syscall.SIGINT, syscall.SIGTERM, syscall.SIGQUIT}
I agree it should be configurable, but if you have a final handler you can do whatever you want by default (including not exiting) which is kind of the point of the final handler. So it's already configurable in that degree.
I'll change the docs to mention it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Added docs

Gentle ping


History Does not Load, or disappear

https://app.staging.crisiscleanup.io/incident/254/work/228328
Click "History". Bug: No history loads.
Click another case. Bug: The new case does not load. Bug: The History modal does not disappear.

Update:

https://app.staging.crisiscleanup.io/incident/254/work/228328
Fixed: History now appears.
Not fixed: Click another case. The new case does not load, and the existing history does not disappear.

Looks good!


Backport KAFKA-5742 support ZK chroot in system tests

backport of KAFKA-5742 (#3677) to 0.11.0

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/6858/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/6844/
Test PASSed (JDK 8 and Scala 2.12).

LGTM

@xvrl This is merged, can you close the PR since asfbot only closes PRs against master?


your slack invitation link doesn't work

https://join.slack.com/t/plexdrive/shared_invite/MjM2MTMzMjY2MTc5LTE1MDQ2MDE4NDQtOTc0N2RiY2UxNw
Updated main page.


Adds MDL Back

Removed in #70 due to gem conflicts. Upstream developers updated, so we can enable again.

Oh, wait. This isn't ready.
-    jekyll (4.0.0)
+    jekyll (3.8.6)


Separate build install readme

As discussed in the DAGMC community meeting today.
The Readme contains more advanced build instructions that the average user will not need.
Therefore the README has been split into two parts, one for simple installation and one for the more complex build.
The testing section was also in need on a split and the more advanced part of the testing is has been moved to the test_plugin folder where it will render as the main readme for that url
Just worth mentioning that the README files have links between them which will not work on this PR as they link to the develop branch version of themselves :-)

Those failing test should not hold the merge of this as it is documentation change only

Perhaps this documentation update is ready to merge

Thanks @Shimwell - This one is definitely ready to merge! (documentation is asymptotic - we can always find things to tweak, and then PR's languish)


Inability to choose local backup in a single markdown file: Current system creates separate markdown files for each note. Users want an option to have all notes updated in a single file.

Summarized Feedback from<EMAIL_ADDRESS>Inability to choose local backup in a single markdown file, because the current system creates a separate markdown file for each note. Users want an option to have all notes updated in a single file.

try exporting as json?


Off By One Wand Use

There's been a consistent issue that I've encountered, where, after some use of the wand, (I think centered around the Destroy mode with a block in offhand) that causes the wand to reverse in placement vs display.
Essentially, after the bug is triggered, the preview shows when the wand will not trigger, and doesn't show preview when it will. Somehow the preview and the actual action get desynched/reversed.
I use the same wand for Destroy and Replace, and I find this issue shows up often when I forget to un-equip the replacement block from my off hand and switch to Destroy, and the wand errors, saying the action is "restricted to offhand block: [blockname]." After that, I remove the block from my hand, and the wand is now reversed compared to the preview.
If you then replace the "filter block" in your offhand, and trigger the error again, the situation resolves itself, but only if you trigger the error again.

Oh, and this was 1.18.2 / Fabric / Modver c2.6.3_release.

I'll investigate the issue, thanks

I wasn't able to  reproduce the issue. can you provide a series of steps that reproduce the bug consistently? I'll keep investigating

Being with a Destroy Wand, and a block in the offhand. This block should not be of a type that is in the set of blocks you're going to destroy (Stone Bricks, usually in my case.)
Attempt to Destroy a 2 by 2 range of blocks of Dirt.
You'll get a "restricted to offhand block: Stone Bricks" error message.
Remove the Stone Bricks from your offhand.
Preview and Action are now reversed.

Video: https://youtu.be/dLEsaEpqxjs

I think  I know what's happening, for now just clear the wand after removing the offhand block, by right clicking on the air.


[IntelliJ Plugin] No service template available for services other than HTTP

Although Ballerina supports several service types such as HTTP, JMS, File etc. when creating a new Ballerina file, of type 'Ballerina Service' (please refer image below), it creates a skeleton service of type 'HTTP'. It would be better if Ballerina asks to choose from all of the supported service types.

Moved the issue to correct repo:
https://github.com/ballerinalang/plugin-intellij/issues/643
Sorry about the inconvenience.


npm install: 3 high severity vulnerabilities

Vulnerabilites report from npm install:
$ npm i @cloudflare/wrangler -g

added 34 packages, and audited 35 packages in 14s

3 high severity vulnerabilities

To address all issues, run:
  npm audit fix

Run `npm audit` for details.

node & npm version
$ node --version
v15.5.0
$ npm --version
7.3.0

You can see the details if you run npm audit from within the npm directory of the project:
# npm audit report

axios  <0.21.1
Severity: high
Server-Side Request Forgery - https://npmjs.com/advisories/1594
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/axios
  binary-install  <=0.1.0
  Depends on vulnerable versions of axios
  node_modules/binary-install

npm  <=6.14.5
Severity: high
Symlink reference outside of node_modules - https://npmjs.com/advisories/1436
Global node_modules Binary Overwrite - https://npmjs.com/advisories/1437
Sensitive Data Exposure - https://npmjs.com/advisories/1543
npm Token Leak - https://npmjs.com/advisories/98
fix available via `npm audit fix`

3 high severity vulnerabilities

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

I don't think we need to worry about the SSRF in axios. Not sure about the npm vulnerabilities either.


The flow is just being closed automatically

Hello, I’m facing some strange problem with userflow. The flow is just being closed automatically, anytime it wants. Every time differently, sometimes it works till the end just fine, sometime just disappeared. Below are 3 screenrecords, which show the 2 occurrences of that problem and 1 normal one;
Userflow.js version is 2.4.0
Initialization:
    userflow.init("ct_***");

    ...

    if (!userflow.isIdentified()) {
        console.log("rendered isIdentified");
        void userflow.identify(profile.user.id);
        userflow.setResourceCenterLauncherHidden(true);
    }
    ...

https://user-images.githubusercontent.com/5887811/162435892-9d1ff016-2a0a-41ae-8eae-ddcc522ae12d.mov
https://user-images.githubusercontent.com/5887811/162435911-ec371b19-52c1-4c53-9562-5e1fc66831ee.mov
https://user-images.githubusercontent.com/5887811/162435937-9ca0ef71-d7ee-452a-8a73-a260ff612316.mov

Hello there :). Did you figure this out?

Yeap) It was a silly situation :)
It was due to another person with same profile who had been logged in to another our project with different subdomain. My preview request was shown to him also and he was closing it.
I was sure that preview will be checked by the URL which I've set, but it was exposed to other subdomains also where with users with same id


Fix build due to updated decimal library

Codecov Report

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

@@          Coverage Diff          @@
##           master   #102   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          19     19
  Lines         645    645
=====================================
  Hits          645    645

Impacted Files
Coverage Δ

goshopify.go
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Extra server required

As mentioned in Kurimizumi/Honeybee-Hive#4, this module will serve as a way to allow users to contribute to projects with their browser.
However, websockets is a protocol over TCP, whilst we use raw TCP sockets (our own protocol). There is a workaround, and that is websockify. This converts a WebSocket to a raw TCP socket, meaning that we can still connect to the Hive server.

Scrap this. The Hive now contains a websocket server


Server Side Rendering won't work with default styles

Server side rendering won't work. I get the same error as described in rackt/react-tabs/issues/39.
Tabs.js:81 [object Object].componentWillMount
[app]/[react-tabs]/lib/components/Tabs.js:81:37

Are react-tabs supposed to work on the server side? If not, any plans on supporting them?

Disabling default styles solves the issue.
ReactTabs.Tabs.setUseDefaultStyles(false);

So the way https://github.com/ryanflorence/js-stylesheet is used within Tabs component seems to be the fault in this case: https://github.com/rackt/react-tabs/blob/master/lib/components/Tabs.js#L60-L64

Why isn't this just a prop?

Because most probably you want to disable the styles globally for all instances of the tabs on your site.
This issue was fixed btw in 0.5


fix: regex parsing on clang++/MacOS fix

This PR fixes the below error message
RuntimeError: The expression contained an invalid character range, such as [b-a] in most encodings.

Signed-off-by: Rajdeep Roy Chowdhury<EMAIL_ADDRESS>

@viig99 could you please let me your thoughts on this?


TensorFlow Resnet50 v1.5 Pre-trained in NCHW data format

Hi, could you please provide the TensorFlow Resnet50 v1.5 Pre-trained in NCHW data format to run the inference located at inference/cloud/image_classification/?
Also could you please confirm what is the precision mode of the pre-trained model https://zenodo.org/record/2535873/files/resnet50_v1.pb
Thanks,
Vilmara

https://zenodo.org/record/2535873/files/resnet50_v1.pb was trained as fp32
Should be visible to publish a NCHW flavor, let me check with a few people first (it is easy for resnet50 but in theory we might need to do the same for other models).

When I try to run inference on with with a NCHW model I get the following error.
2019-05-04 13:45:18.523575: I tensorflow/compiler/xla/service/service.cc:150] XLA service 0x562c16a7e780 executing computations on platform Host. Devices:
2019-05-04 13:45:18.523609: I tensorflow/compiler/xla/service/service.cc:158]   StreamExecutor device (0): <undefined>, <undefined>
ERROR:main:execute_parallel thread: Cannot feed value of shape (1, 224, 224, 3) for Tensor 'data:0', which has shape '(1, 3, 224, 224)'
ERROR:main:execute_parallel thread: Cannot feed value of shape (1, 224, 224, 3) for Tensor 'data:0', which has shape '(1, 3, 224, 224)'

I do understand it is complaining about the NCHW format while it expects the NHWC format but do not know where to change this. Changing the model could be one option, but I want to make mlperf work with NHWC
Any help is much appreciated!

If you are using https://github.com/mlperf/inference/blob/master/cloud/image_classification/python/main.py it is pretty easy:
by default we use the backend's preferred data-format, ie. for tensorflow we use NHWC, for onnx we
use NCHW.
You can override it in the command line with --data-format NCHW

hi @guschmue, I ran the test with the flag --data-format=NCHW but the system has thrown the below error:
ERROR:main:execute_parallel thread: Cannot feed value of shape (1, 3, 224, 224) for Tensor 'input_tensor:0', which has shape '(?, 224, 224, 3)'
Traceback (most recent call last):
  File "python/main.py", line 382, in <module>
    main()
  File "python/main.py", line 353, in main
    report_result("check_accuracy", 0., final_results, result_list, result_dict, check_acc=True)
  File "python/main.py", line 201, in report_result
    buckets = np.percentile(result_list, percentiles).tolist()
  File "/opt/anaconda3/lib/python3.6/site-packages/numpy/lib/function_base.py", line 3707, in percentile
    a, q, axis, out, overwrite_input, interpolation, keepdims)
  File "/opt/anaconda3/lib/python3.6/site-packages/numpy/lib/function_base.py", line 3826, in _quantile_unchecked
    interpolation=interpolation)
  File "/opt/anaconda3/lib/python3.6/site-packages/numpy/lib/function_base.py", line 3405, in _ureduce
    r = func(a, **kwargs)
  File "/opt/anaconda3/lib/python3.6/site-packages/numpy/lib/function_base.py", line 3941, in _quantile_ureduce_func
    x1 = take(ap, indices_below, axis=axis) * weights_below
  File "/opt/anaconda3/lib/python3.6/site-packages/numpy/core/fromnumeric.py", line 189, in take
    return _wrapfunc(a, 'take', indices, axis=axis, out=out, mode=mode)
  File "/opt/anaconda3/lib/python3.6/site-packages/numpy/core/fromnumeric.py", line 56, in _wrapfunc
    return getattr(obj, method)(*args, **kwds)
IndexError: cannot do a non-empty take from an empty axes.

Does MLPerf expect to release the TensorFlow Resnet50 v1.5 Pre-trained model in NCHW data format to run the benchmark with GPU support?

syedaffanhamdani's issue:
Cannot feed value of shape (1, 224, 224, 3) for Tensor 'data:0', which has shape '(1, 3, 224, 224)'
he feeds NHWC but the model is NCHW

The fix for his model is --data-format NCHW

Your model:
Cannot feed value of shape (1, 3, 224, 224) for Tensor 'input_tensor:0', which has shape '(?, 224, 224, 3)
You feed NCHW bit the model wants NHWC

basically don't use  --data-format NCHW

If you want a NCHW model we need to publish one.


[Bug]: Disconnect from git causes the git modal to come back up

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When I disconnect an app from git, though it disconnects the app successfully, it brings up the git modal back up
Steps To Reproduce
https://jam.dev/c/39e463d7-1442-41b8-aad2-7a8aafab9f87
Public Sample App
No response
Environment
Deploy Preview
Severity
High (Blocker to building or releasing)
Issue video log
No response
Version
Cloud

Tested and found to be fixed in the latest DP


ModuleNotFoundError: No module named 'jyotisha.panchaanga'

from jyotisha.panchaanga.spatio_temporal import City, annual, periodical
from jyotisha.panchaanga.temporal import ComputationSystem
from jyotisha.panchaanga.temporal.time import Date
city = City('Chennai', "13:05:24", "80:16:12", "Asia/Calcutta")
panchaanga = annual.get_panchaanga_for_civil_year(city=city, year=2021, computation_system=ComputationSystem.TEST, allow_precomputed=False)
print(panchaange)

ModuleNotFoundError                       Traceback (most recent call last)
 in ()
----> 1 from jyotisha.panchaanga.spatio_temporal import City, annual, periodical
2 from jyotisha.panchaanga.temporal import ComputationSystem
3 from jyotisha.panchaanga.temporal.time import Date
4 city = City('Chennai', "13:05:24", "80:16:12", "Asia/Calcutta")
5 panchaanga = annual.get_panchaanga_for_civil_year(city=city, year=2021, computation_system=ComputationSystem.TEST, allow_precomputed=False)
ModuleNotFoundError: No module named 'jyotisha.panchaanga'

Can you prove that you have properly installed this package? (Run a suitable command and paste it's output here.)

pip install jyotisha -U
Requirement already up-to-date: jyotisha in /usr/local/lib/python3.7/dist-packages (0.0.9)
Requirement already satisfied, skipping upgrade: indic-transliteration in /usr/local/lib/python3.7/dist-packages (from jyotisha) (2.1.1)
Requirement already satisfied, skipping upgrade: scipy in /usr/local/lib/python3.7/dist-packages (from jyotisha) (1.4.1)
Requirement already satisfied, skipping upgrade: pyswisseph in /usr/local/lib/python3.7/dist-packages (from jyotisha) (2.8.0.post1)
Requirement already satisfied, skipping upgrade: pytz in /usr/local/lib/python3.7/dist-packages (from jyotisha) (2018.9)
Requirement already satisfied, skipping upgrade: pandas in /usr/local/lib/python3.7/dist-packages (from jyotisha) (1.1.5)
Requirement already satisfied, skipping upgrade: sanskrit-data in /usr/local/lib/python3.7/dist-packages (from jyotisha) (0.8.3)
Requirement already satisfied, skipping upgrade: icalendar in /usr/local/lib/python3.7/dist-packages (from jyotisha) (4.0.7)
Requirement already satisfied, skipping upgrade: regex==2020.10.11 in /usr/local/lib/python3.7/dist-packages (from indic-transliteration->jyotisha) (2020.10.11)
Requirement already satisfied, skipping upgrade: typer==0.3.2 in /usr/local/lib/python3.7/dist-packages (from indic-transliteration->jyotisha) (0.3.2)
Requirement already satisfied, skipping upgrade: selenium==3.141.0 in /usr/local/lib/python3.7/dist-packages (from indic-transliteration->jyotisha) (3.141.0)
Requirement already satisfied, skipping upgrade: backports.functools-lru-cache==1.6.4 in /usr/local/lib/python3.7/dist-packages (from indic-transliteration->jyotisha) (1.6.4)
Requirement already satisfied, skipping upgrade: numpy>=1.13.3 in /usr/local/lib/python3.7/dist-packages (from scipy->jyotisha) (1.19.5)
Requirement already satisfied, skipping upgrade: python-dateutil>=2.7.3 in /usr/local/lib/python3.7/dist-packages (from pandas->jyotisha) (2.8.1)
Requirement already satisfied, skipping upgrade: toml==0.10.1 in /usr/local/lib/python3.7/dist-packages (from sanskrit-data->jyotisha) (0.10.1)
Requirement already satisfied, skipping upgrade: bcrypt==3.2.0 in /usr/local/lib/python3.7/dist-packages (from sanskrit-data->jyotisha) (3.2.0)
Requirement already satisfied, skipping upgrade: six in /usr/local/lib/python3.7/dist-packages (from sanskrit-data->jyotisha) (1.15.0)
Requirement already satisfied, skipping upgrade: qtoml in /usr/local/lib/python3.7/dist-packages (from sanskrit-data->jyotisha) (0.3.0)
Requirement already satisfied, skipping upgrade: jsonpickle==1.4.1 in /usr/local/lib/python3.7/dist-packages (from sanskrit-data->jyotisha) (1.4.1)
Requirement already satisfied, skipping upgrade: yurl==1.0.0 in /usr/local/lib/python3.7/dist-packages (from sanskrit-data->jyotisha) (1.0.0)
Requirement already satisfied, skipping upgrade: jsonschema==3.2.0 in /usr/local/lib/python3.7/dist-packages (from sanskrit-data->jyotisha) (3.2.0)
Requirement already satisfied, skipping upgrade: click<7.2.0,>=7.1.1 in /usr/local/lib/python3.7/dist-packages (from typer==0.3.2->indic-transliteration->jyotisha) (7.1.2)
Requirement already satisfied, skipping upgrade: urllib3 in /usr/local/lib/python3.7/dist-packages (from selenium==3.141.0->indic-transliteration->jyotisha) (1.24.3)
Requirement already satisfied, skipping upgrade: cffi>=1.1 in /usr/local/lib/python3.7/dist-packages (from bcrypt==3.2.0->sanskrit-data->jyotisha) (1.14.5)
Collecting attrs<20.0.0,>=19.3.0
Downloading https://files.pythonhosted.org/packages/a2/db/4313ab3be961f7a763066401fb77f7748373b6094076ae2bda2806988af6/attrs-19.3.0-py2.py3-none-any.whl
Requirement already satisfied, skipping upgrade: importlib-metadata in /usr/local/lib/python3.7/dist-packages (from jsonpickle==1.4.1->sanskrit-data->jyotisha) (4.0.1)
Requirement already satisfied, skipping upgrade: pyrsistent>=0.14.0 in /usr/local/lib/python3.7/dist-packages (from jsonschema==3.2.0->sanskrit-data->jyotisha) (0.17.3)
Requirement already satisfied, skipping upgrade: setuptools in /usr/local/lib/python3.7/dist-packages (from jsonschema==3.2.0->sanskrit-data->jyotisha) (57.0.0)
Requirement already satisfied, skipping upgrade: pycparser in /usr/local/lib/python3.7/dist-packages (from cffi>=1.1->bcrypt==3.2.0->sanskrit-data->jyotisha) (2.20)
Requirement already satisfied, skipping upgrade: typing-extensions>=3.6.4; python_version < "3.8" in /usr/local/lib/python3.7/dist-packages (from importlib-metadata->jsonpickle==1.4.1->sanskrit-data->jyotisha) (<IP_ADDRESS>)
Requirement already satisfied, skipping upgrade: zipp>=0.5 in /usr/local/lib/python3.7/dist-packages (from importlib-metadata->jsonpickle==1.4.1->sanskrit-data->jyotisha) (3.4.1)
ERROR: datascience 0.10.6 has requirement folium==0.2.1, but you'll have folium 0.8.3 which is incompatible.
Installing collected packages: attrs
Found existing installation: attrs 21.2.0
Uninstalling attrs-21.2.0:
Successfully uninstalled attrs-21.2.0
Successfully installed attrs-19.3.0

Now, can you show the output of python -c "from jyotisha.panchaanga.spatio_temporal import City, annual, periodical"?

python -c "from jyotisha.panchaanga.spatio_temporal import City, annual, periodical"
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'jyotisha.panchaanga'

python --version ?

!python --version
Python 3.7.10

No idea then. If you figure out what the problem was, let me know. Till then, I will close this thread as a non-reproducible bug.


chore: 1.5 release notes

cc @bartlomieju @ry

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: lucacasonato:white_check_mark: bartlomieju:x: ryYou have signed the CLA already but the status is still pending? Let us recheck it.


[x] Are you working against an Issue?

Closes #428

Microsoft Reviewers: Open in CodeFlow

/azp run


Update list command to work for Qt6

Signed-off-by: Hiroshi Miura<EMAIL_ADDRESS>

Failed test is not caused by here, so we can merge.

Failed test is not caused by here, so we can merge.


Unable to activate slather-1.8.1, because xcodeproj-0.28.2 conflicts with xcodeproj (~> 0.26.2)

Hi,
It seems that after updating Cocoapods to the latest version breaks slather, because it is depends on an older version of xcodeproj.
If there a way to fix this without downgrading Cocoapods ?
Error loading the plugin with path `/Users/nghimbovschi/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/slather-1.8.1/lib/cocoapods_plugin.rb`.

Gem::ConflictError - Unable to activate slather-1.8.1, because xcodeproj-0.28.2 conflicts with xcodeproj (~> 0.26.2)
/Users/nghimbovschi/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rubygems/specification.rb:2112:in `raise_if_conflicts'
...

Hey,
I have noticed this too. There is a pull request for that https://github.com/venmo/slather/pull/105

:+1: thanks !

Fixed in #106 #109

Thanks!

Although I can see the PR were merged and a new version was released (1.8.2). I still can't install the new version by running gem install slather. I just can't run pod install because it uses slather, what can I do to fix it?

gem install specific_install
gem specific_install -l https://github.com/venmo/slather.git

Somebody would have to publish a new gem version. As far as I know @marklarr did this in the past.

+1

Basically my solution was to merge some existing PR from this repo, and build my own slather gem.
https://github.com/xfreebird/slather
Note: use sudo only if you use default system Ruby
sudo gem install specific_install
sudo gem specific_install https://github.com/xfreebird/slather

@xfreebird, you didn't have to, the PR is already merged, but there wasn't a new gem release. I followed @haifengkao instructions I was good to go.

I know, but I also merged the PR related to new code converage #99 because I really needed :)


Remove option to provide the client id

There is no point in using client ids that are created by us, since they will not work (see this)
The client id provided is the one that's used in youtube-dl and streamlink, I guess they got it from the official site, and for now, it works perfectly.

Apologies for delays.


Should all receivers be moved into the completion signals?

I don't know if this makes any difference in the wording, but there's currently quite a mix of how receivers are passed into completion signals:

C-style cast (related: https://github.com/brycelelbach/wg21_p2300_std_execution/issues/379):
https://github.com/brycelelbach/wg21_p2300_std_execution/blob/e3627f3b90e914591cdf2d0a93aae98aa252eb27/std_execution.bs#L4520
No move/cast:
https://github.com/brycelelbach/wg21_p2300_std_execution/blob/e3627f3b90e914591cdf2d0a93aae98aa252eb27/std_execution.bs#L4962
Move:
https://github.com/brycelelbach/wg21_p2300_std_execution/blob/e3627f3b90e914591cdf2d0a93aae98aa252eb27/std_execution.bs#L5242

Should they all just be std::moved? Or something else? I'll happily attempt to clean this up (including #379).

The answer depends. When the algorithms mention out_r, what they should be saying is that they are manipulating an rvalue (or xvalue to be more precise) that refers to a copy of out_r that lives in . ("" most likely is within the operation state.) If for the sake of the specification, you give that rvalue a name like out_r', then out_r' can appear in a set_[value|error|stopped] expression without a cast or a move, because it is already an rvalue.
Also see #403.

I'll happily attempt to clean this up (including #379).

Oh, and in case it wasn't clear ... YES PLEASE. :-) #403 also, while you're at it.


Unable to position window

I watched a video that showed you can change the position of the shortcut popup. This doesn't exist when I run the program. Did this get removed?

I double click the icon in the status bar, and the configuration window showed up.

Just tried this program today, and it's pretty great for what I need. Hope this helps!

Sometimes it remembers the last displayed position. However, if you switch or use different monitor before, the window position may out of visible range.
Please try:
https://www.howtogeek.com/howto/windows/bring-misplaced-off-screen-windows-back-to-your-desktop-keyboard-trick/


Long form documentation

[x] Why SuperDuperDB?

[x] Common issues in model development, model management, databases
[x] Opportunities for DB users with latest AI
[x] SuperDuperDB's vision
[x] What SuperDuperDB is not

[x] Common usage-patterns

[x] Getting started with a SuperDuperDB instance
[x] Inserting data
[x] Defining models via .predict
[x] Linking models together via .predict
[x] Querying data
[x] Using the output of models to query data
[x] Training models via .fit
[ ] Standalone mode and cluster mode

[ ] Setting up a SuperDuperDB deployment
[ ] High level roadmap and detailed vision
[ ] Notebook examples see #359 worked in via nbsphinx

Solved by release v0.0.4


allow for chaning arcade screen size on sim

Allows to modify the screen size in the simulator using userconfig flags.

@mmoskal looks good to me, undraft?

Add this to your project to change the size:
namespace userconfig { export const ARCADE_SCREEN_WIDTH = 320; export const ARCADE_SCREEN_HEIGHT = 240 }


Ideal changes for smarty sampler

I have a pull request open already, #198 that is addressing changes to the smarty original and elemental sampler.
In the process of investigating the best way to setup the elemental sampler, I've come across a few other minor issues that I will fix in this pull request, I wanted to have a list of them in an issue for prosperity sake.

It seems that we were not consistent in creating atomtype lists. Some were created as list of tuples and others as list of lists. @davidlmobley is there a preferred form for this? They all have the same general format as a list containing pairs of SMARTS and labels for a created atomtype.

When choosing a random atomtype, the index is chosen randomly, then the atomtype at that index is taken.
If you use the random module from numpy, then the random choice option expects a list in 1 dimension and it won't choose a random choice for a list of lists or a list of tuples.
In the smarty samplers though, we are using the stand alone random module, not the one that comes with numpy. When you use that random.choice with a list of lists it returns a sub list (or sub tuple if you use a list of tuples).

@davidlmobley
I'm also noticing there are some things being imported that don't seem to be used, maybe we need them somewhere I'm not familiar with, or maybe Camila or John used them while testing. Here are the modules, I'm not seeing being used:
sys
string
math
optparse is imported in the sampler.py, but is only used by cli_smarty.py does it need to be imported here too?

There is some inconsistency with method doc strings I'm trying to repair as well

Sorry for the delay, @bannanc . Responses:

It seems that we were not consistent in creating atomtype lists. Some were created as list of tuples and others as list of lists. @davidlmobley is there a preferred form for this? They all have the same general format as a list containing pairs of SMARTS and labels for a created atomtype.

No, I don't think so.
Regarding potentially unused modules sys, string, and math, I am not aware of using these. Simplest would probably be to grep the main code for their use, or just remove them and ensure things still work.
Regarding optparse - it should only be imported where it is needed, so if it's imported elsewhere that's unnecessary.

I decided to use tuples, I think all atomlists are now lists of tuples.
I removed any of the imported modules not used in the smarty and smirky sampler. The tests seem to be passing so I assume they really were unnecessary.
I have also updated the doc strings (mostly in the smarty sampler).

updated in pull request #198


DB first issue with Index giving one-to-one instead of one-to-many relationship

Hi,
When running database first migration using Scaffold-DbContext the some of the models generated are linked by one-to-one relationships, when in actual fact they are one-to-many and I'm not getting any errors or exceptions.
Basically I have a table of jobs and a table of appointments.
A job can have multiple appointments and each of these appointments can have difference statuses e.g.
Active
Cancelled

So in my crude example above, Job1 has 3 appointments linked to it.
The thing that seems to be causing the issue I'm experiencing is an index I have on one of the tables which was recently added.
Previously without the index when Scaffold-DbContext was run the Job model looked something like this
        public Job()
        {
            Appointment = new HashSet<Appointment>();
            // more code
        }

        [InverseProperty("Job")]
        public virtual ICollection<Appointment> Appointment { get; set; }

But now with the index I am getting.
        public Job()
        {
            // more code
        }

        [InverseProperty("Job")]
        public virtual Appointment Appointment { get; set; }

When I remove the index it generates the models and the relationships correctly between Job and Appointment.
The index below is there to prevent multiple Active Appointments on a single Job at any given time.
CREATE UNIQUE NONCLUSTERED INDEX [IX_Appointment_JobId_NotActiveStatus_Unique] ON [Appointment] ([JobId] ASC) WHERE[StatusId] != 'Cancelled'
I'm not sure if there is anything to tell the scaffolding to ignore the index in this particular case?
Any help would be greatly appreciated.
Many thanks,
Jeremy

Notes for triage: support for filtered indexes in SQL Server was added in 5817 and  #6866. I'm not sure off the top of my head how far this permeates into the stack. It feels like in this case we should at least try to interpret the index to not mean the relationship is 1:1, and if we can also add support to reverse engineer the filtered index correctly that would be great. Let's discuss in triage.

EF Triage: Minimal fix is to not reverse engineer this to a unique index. Ideally, the index should be reverse-engineered into the model retaining the filter information. If that is a lot of work, then we can have a new bug for it outlining the work that is needed and we will triage that separately.

@jjklee121 What version of EF packages do you have? I do see the above behavior in 1.1.1, but this is already fixed in 2.0.0 (@ajcvickers this includes retaining the filter info on indexes). Closing as already fixed, but please feel free to re-open if you can see it using the 2.0.0 packages.

@lajones Thanks for getting back to me.
I have EntityFrameworkCore 1.1.0 and EntityFrameworkCore.DynamicLinq <IP_ADDRESS> installed. (I should've mentioned the versions in my initial post)
I will get these updated and see if that fixes my issue.

I've just hit what I think is the same issue as posted above but I'm using version 2.0.2 of the Microsoft.EntityFrameworkCore.Tools and Microsoft.EntityFrameworkCore.SqlServer packages, which would suggest that the issue hasn't been entirely resolved in 2.x. Should I open a new issue or post details to this thread?

@bwalters3 Yes, please open a new issue.


Should beans.xml be on generator

The beans.xml is listed on the generator page. I am wondering how useful it is.
Does people change the setting or bother to choose anything different other than the default?
Does people understand the consequence of choosing a different value for bean discovery mode?
I wonder whether displaying beans.xml add more confusion or white noise to the generator. Should we choose a sensible default and stay with it and remove the beans.xml entry?
Thoughts?

I felt the same way the first time I had a look at the website. All the rest of the options are extremely high-level (what java version, what technologies do you want to use, what app server).
The beans.xml is a very low-level detail in comparison to the other items, and feels out of place.
+1 for just giving the user the default

For somebody that is using the starter in the first place, the prompt for the beans.xml is overkill and confusing.  Default it and skip the the prompt.

I suggest to generate a beans.xml with the bean-discovery-mode="all" so that any additional classes added will work without any issues. The generated classes should have the correct bean-defining annotations specified as they are now. Thoughts?

I do not agree with putting the discovery mode to all. It takes all classes (which meet the CDI requirements) as CDI beans which are probably many more than actually needed.
This puts additional processing and memory requirements on the applications which is undesired.
We have now the implicit value as default chosen and should keep it when the user no longer can select the value.
As you mentioned, lets try to keep the generated application to a minimum as you also mentioned https://groups.google.com/d/msg/microprofile/kKsrLKLPEN8/lBVeVEGADgAJ.

Thanks @rdebusscher for digging out the previous conversation! Reconsidered this.
Both approaches have advantage and disadvantages.

Not generate beans.xml

Any newly added classes need to have bean-defining annotations. Otherwise, the injection will not work.

less files, bean-defining annotations are carefully considered and added to a particular resource.

Generate beans.xml with bean discovery mode with "all"

more files are generated and the relevant scopes might not be considered.

All injection will work.

I am kind of ok with either way. What other people think?
Interested in what others think.

See forum discussion https://groups.google.com/forum/#!msg/microprofile/eJimS3UhLSg/pVJr9kN7CQAJ

Decision : Generate the beans.xml with mode all.


failed to install on Mac OS X 10.9.5

while trying to make swagxample, I encounter this error:
Processing dependencies for Swagxample==<IP_ADDRESS>
Searching for sqlalchemy-login-models
Reading https://pypi.python.org/simple/sqlalchemy-login-models/
Couldn't find index page for 'sqlalchemy-login-models' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
No local packages or download links found for sqlalchemy-login-models
error: Could not find suitable distribution for Requirement.parse('sqlalchemy-login-models')
make: *** [install] Error 1

That package is currently only hosted on github.
https://github.com/deginner/sqlalchemy-login-models
The requirements.txt file has the correct link, so if you run pip install -U -r requirements.txtit should install the correct version. I also fixed setup.py so it won't require this until it is in pypi.
That being said, I don't have a Mac available for testing so I will leave this open pending your approval.


npx create-remix fails in empty git repo directory

What version of Remix are you using?
1.17.1
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
> mkdir temp
> cd temp
> git init
> npx create-remix .
🚨 The project directory must be empty to create a new project. Please clear the contents of the directory or choose a different path.

I think a directory with nothing but .git/ can safely be considered empty.  This allows folks to start first with the git repo.
Original issue raised by @jacobparis in discord:

My dev workflow is repo first
I make a new repo, then open it in a cloud dev environment and start mucking with it there
There’s no time where I have any dev tools installed before the repo is created

My workflow involves using direnv to specify a node version that the project will use. That means I need to set up a .envrc in the directory before I even run npx. It would be great if there were just an argument like --overwrite that would suppress this error and have remix simply overwrite any files which already exist.

I'd be happy with that solution as well

cc @markdalgleish who has been doing some work on the create-remix CLI recently - let's sync up on this sometime next week


Can I be part of the group

Fine thanks
On Tue, Jun 7, 2022, 10:33 David Rubinstein @.***>
wrote:

Closed #12 https://github.com/spotify/basic-pitch/issues/12 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/spotify/basic-pitch/issues/12#event-6758613261, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AX2DFHNRM2XZGN7SH47JV6LVN33MZANCNFSM5X5KUAXQ
.
You are receiving this because you authored the thread.Message ID:
@.***>