State of Croppy

Hi guys!
Unfortunately at the moment I'm extremely busy with work projects. I don't have enough time to check on issues/pull requests. I've however noticed that there's quite a lot of activity around the package, which I didn't initially expect :P
Very sorry for that. At the moment I don't have an exact timeline as to when I'll be able to work on the package. The reason as to why I can't commit hours working on this is that this package was developed as a part of our application, and currently it perfectly fits our usecase.
Many thanks to all the people who're submitting pull requests - I'll try to look through those and merge them on July 20. As for other issues - no estimate yet.
In the future I have a refactor planned for this package as well as a couple of big new features (video support?)
Special thanks to @talamaska who's been active in helping out other people with this package from the beginning.

Thanks everyone for the pull requests! I've merged all of them and deployed version 1.2.0 with a couple of more fixes.
As for the prevalent theme issue - I've added a temporary solution that allows you to pass ThemeData/CupertinoThemeData when pushing the cropper. I've fixed the theme auto-generation, so now it should properly respect the incoming primary color and generate the appropriate theme.
If the auto-generated theme still looks off, you can pass a custom Theme like so:
final result = await showMaterialImageCropper(
  context,
  imageProvider: const NetworkImage('MY_IMAGE_URL'), // Or any other image provider
  themeData: ThemeData(...),
);

final result = await showCupertinoImageCropper(
  context,
  imageProvider: const NetworkImage('MY_IMAGE_URL'), // Or any other image provider
  themeData: CupertinoThemeData(...),
);


Maint: missing pytables dependency and find all unit tests

pytables was always a dependency of app_common. It was missed because some tests was being missed by unittest's test searching.

Trivial. Self-merging...


Routable pods

Out for eng review, so WIP. Will need to go into the 1.2 branch.

@mjgutermuth Feedback from review is done. Ready for editing on your end and merge for 1.2.1. Thanks.


Declare Expect of single variable without validation.

Expectation required to be executed before end of the story.
If we expect substory to define variable, which will be used in further steps, it would be nice to have a way describe it in the contract.
from stories import story, Argument, Variable, Expect

class Action:
    @story
    def do(I):
        I.one
        I.two
        I.three

    def one(self, state):
        state.baz = state.foo + state.bar
        return Success()

    def three(self, state):
        if state.quiz:
            ...
        return Success()

    def __init__(self, two):
        self.two = two

Action.do.contract({
    'foo': Argument(),
    'bar': Argument(),
    'baz': Variable(),
    'quiz': Expect(),
})

In the example above quiz variable should be assigned in two substory.

Superseded by #627


[CI] Temporarily disable macOS CI due to pybind issue

pybind is no longer available for mac in conan center.
See:
https://github.com/conan-io/conan-center-index/pull/11075
https://github.com/pybind/pybind11/issues/3081

@feltech I've also removed the PR merge requirement for the macOS CI check.


feat(migration-graph): report and logger

Expose MigrationStrategy.report that contains the logged messages from the migration-graph creation process.
This implementation passes through and down logger references from the top level migration-graph package.

Should I be using Winston logger here or is that overkill?

Should I be using Winston logger here or is that overkill?

@wondersloth what specifically are you thinking about for the migration-graph report and logger? eg. what would it look like to the user?
wrt logger: if we were to propagate something from the migration-graph into Listr you would need access to the ListrContext eg. like we do here. If we just want to have access to the logs for debug purposes I would just use the DEBUG module.
wrt report: you would need access to the reporter eg. like we do here
You shouldn't need Winston logger at all.

Should I be using Winston logger here or is that overkill?

@wondersloth what specifically are you thinking about for the migration-graph report and logger? eg. what would it look like to the user?
wrt logger: if we were to propagate something from the migration-graph into Listr you would need access to the ListrContext eg. like we do here. If we just want to have access to the logs for debug purposes I would just use the DEBUG module.
wrt report: you would need access to the reporter eg. like we do here
You shouldn't need Winston logger at all.

Ok, so I think I am going to convert my existing console.log or logger statements in this PR to just a DEBUG module call.
There is some value in maybe adding some interactivity to the ember service discovery code, but I don't think that needs to be addressed.
I need to

[ ] Remove logger from this PR.
[ ] Replace logger calls with DEBUG_CALLBACK calls.
[ ] Rewrite tests to spy on DEBUG to validate those cases.


Manufacturer URLs generate 404 error

Manufacturer URLs generate 404 error with Friendly URLs enabled:
/index.php?controller=manufacturer&id_lang=1&id_manufacturer=0 works just fine...
/manufacturers/blablabla gives 404 error
In the Module settings is the following: "brands/{rewrite}" :(
Please see images attached...

Hi,
please report your PS and module versions.
Will investigate asap
Thanks for your feedback

@devdesco-ceo is suppliers working fine instead??

I do not have suppliers enabled. PS <IP_ADDRESS>, latest updated zzCleanURLs

OK started working on ..  each manufacturer is now working on https://github.com/ZiZuu-store/zzCleanURLs/tree/fix-manufacturer-supplier .. still have to fix the manufacturers/ listing


Added filter utility classes

I have added 'opacity-', 'hue-rotate-', 'saturate-', 'contrast-', 'blur', 'brightness-' options.
Please let me know if this is right path to add more utility classes.  Perhaps the backdrop option could/should be added to.  Sorry PR became a bit messy due to linting.

Thanks. It looks good.


Iss

Helper

but

On Sun, Dec 20, 2020 at 1:56 PM Nikolay Igotti<EMAIL_ADDRESS>wrote:

Closed #204 https://github.com/JetBrains/compose-jb/issues/204.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/compose-jb/issues/204#event-4133576810, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASDGYVDMVEQGWBGGJV45U7TSVZCGRANCNFSM4VCJ3OOA
.

What’s this?

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


enhance: remove duplicated Function.

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.72 seconds
load time: 496 seconds
storage size:<PHONE_NUMBER>7 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230129060138_clickbench_pr_86013.html


chore(ci): speed up build with static make cache

What this PR does / why we need it:

Uses make to cache static assets
Which issue(s) this PR fixes:

Does this PR require a test?

Does this PR require a release note?

Does this PR require documentation?

The failure is a flake and unrelated to the change. Merging


[BG] Fix a typo

Fixes a trival typo for Bulgarian

Fixes a trival typo for Bulgarian

Thank you for Your contribution and fix!


Fix day of year defaulting for round up parser

Description
This change fixes the conflict gets when trying to round up input date ranges, specifically for the format "yyyy-DDD'T'HH:mm:ss.SSS".  For this input format, we default day of year to 1 else default month of year and day of month to 1
Issues Resolved
#4285
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #4620 (d15b7bd) into main (3ef0046) will decrease coverage by 0.03%.
The diff coverage is 54.60%.

:exclamation: Current head d15b7bd differs from pull request most recent head 31ee1ae. Consider uploading reports for the commit 31ee1ae to get more accurate results

@@             Coverage Diff              @@
##               main    #4620      +/-   ##
============================================
- Coverage     70.64%   70.60%   -0.04%
- Complexity    57294    57528     +234
============================================
  Files          4617     4642      +25
  Lines        275479   276792    +1313
  Branches      40328    40502     +174
============================================
+ Hits         194602   195431     +829
- Misses        64581    64906     +325
- Partials      16296    16455     +159

Impacted Files
Coverage Δ

.../java/org/opensearch/client/RequestConverters.java
85.02% <0.00%> (+2.19%)
:arrow_up:

...ava/org/opensearch/client/RestHighLevelClient.java
41.75% <0.00%> (-0.66%)
:arrow_down:

...va/org/opensearch/common/settings/KeyStoreCli.java
0.00% <ø> (ø)

...rc/main/java/org/opensearch/plugins/PluginCli.java
0.00% <ø> (ø)

...main/java/org/opensearch/plugins/PluginHelper.java
100.00% <ø> (+9.09%)
:arrow_up:

...va/org/opensearch/geometry/GeometryCollection.java
92.85% <0.00%> (-3.44%)
:arrow_down:

...le/customsettings/ExampleCustomSettingsConfig.java
29.03% <ø> (ø)

...le/customsettings/ExampleCustomSettingsPlugin.java
9.09% <ø> (ø)

...igheuristic/CustomSignificanceHeuristicPlugin.java
0.00% <0.00%> (ø)

...ch/example/customsigheuristic/SimpleHeuristic.java
86.66% <ø> (ø)

... and 613 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@Vishalks : It seems you need to rebase your changes against main ?

@Vishalks : It seems you need to rebase your changes against main ?

Yeah, trying to clean up the mess that DCO created. Will suspend this PR and create a new one


Problem with SAS Volumes

Heads Up: I had to add a couple of extra steps to get this to work correctly. Apparently failover clustering by default will assume all SAS volumes are meant to be shared cluster storage and try to commandeer them, which makes SQL unable to come up because its data and log volumes aren't mounted. Workaround is essentially to release them with the Failover Cluster Manager and then bring them online with Disk Management:
https://blog.sqlauthority.com/2016/11/08/sql-server-added-new-node-windows-cluster-alwayson-availability-databases-stopped-working/
https://support.microsoft.com/en-za/help/2813005/local-sas-disks-getting-added-in-windows-server-2012-failover-cluster

@tmustain I'm getting a similar issue. Was able to get it to manually work.

I apologize for not responding sooner, we recently made some updates to this Quick Start. Can you verify if you see this issue still existing? We did drop support for Windows 2012 in the quick start, and support Windows 2019. Please let us know if this still exist.


Migration tracking

Following up on #726, here is the meta-issue to track projects migration.

GFX <- https://github.com/csherratt/genmesh/issues/17: genmesh
GFX <- https://github.com/gfx-rs/gfx-rs/issues/125: gfx_scene
? <- gfx_pipeline
Piston <- gfx_debug_draw
Piston <- gfx_text

All @gfx-rs/developers are invited to vote.

I want to express my support to the library owner to decide, because that is the person who invested the greatest amount of time into the library. So my vote counts as a double vote of the library owner, in the case of gfx_scene this is @kvark . I support Gfx having policy for migration, but since @kvark is one of the best people to understand Gfx and have probably thought a lot about the future, I reach the same conclusion.

@bvssvni thanks for your support and votes! You clearly don't want to bother yourself with a case-by-case basis ;)
genmesh has been moved now, thanks @csherratt ! We'll take good care of it.
As for gfx_scene, I'm glad it wasn't moved to gfx-rs earlier. I had my arms untied and was able to iterate on major changes quickly. It's not stable yet (for instance, we still need a good way to re-use culling results with multiple phases), but it's certainly more robust to major changes now, and I'm ready to experiment with these in PRs, without breaking API too often ;)
There seem to be some sort of approval from the team, however it would be really nice if someone actually tried using it and looking into the architecture. @csherratt had some ideas of making it work with VR, so this gives a good chance. Besides, there is an upcoming talk on Friday, which will allow everyone to get a better vision on it. I believe we can make a decision next week.

Closing due to inactivity


Use backup of yum.repos.d to identify added repositories

Fixes #1135

Can you add entry to changelog? On develop there should be an entry for 061 already.

Can you add entry to changelog? On develop there should be an entry for 061 already.

Good point, added.


Added UserAgent parsing via mobi and android string match

Fixes #17

This isn't properly detecting UC Browser on iOS or Windows mobile user agents that come with Chrome's dev tools but does work for Android.
Doesn't detect UC Browser for iOS as mobile:

UC Browser has 3% market share, mainly for China:

Date
Chrome
Safari
Firefox
Opera
Samsung Internet
IE
Edge
UC Browser

2019-04
63.16
15.37
5.09
2.58
3.17
2.58
2.25
3.07

So I'm not sure if this is a dealbreaker. We do properly detect this browser using the other method in PR #22

Needs further discussion. This is potential enhancement but does not block any releases going forward.


Implement Pushsecrets updatePolicy: IfNotExists for AWS

Describe the bug
Just tried to push a secret and did not work. v0.9.15-2
To Reproduce
apiVersion: external-secrets.io/v1alpha1
kind: PushSecret
metadata:
  name: postgresql
  namespace: controlplane
spec:
  updatePolicy: IfNotExists
  deletionPolicy: Delete
  refreshInterval: 168h
  secretStoreRefs:
    - name: default
      kind: ClusterSecretStore
  selector:
    secret:
      name: postgresql
  data:
    - match:
        remoteRef:
          remoteKey: controlplane/postgresql-smg

Expected behavior
The secret to be pushed
Screenshots
{"level":"error","ts":1713276193.4958684,"msg":"Reconciler error","controller":"pushsecret","controllerGroup":"external-secrets.io","controllerKind":"PushSecret","PushSecret":{"name":"postgresql","namespace":"controlplane"},"namespace":"controlplane","name":"postgresql","reconcileID":"8012f29d-4fe7-4c13-a811-d08d54b51574","error":"could  not verify if secret exists in store: not implemented","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.2/pkg/internal/controller/controller.go:329\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).proc  essNextWorkItem\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.2/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.2/pkg/internal/controller/controller.go:227"}    {"level":"info","ts":1713276208.7876587,"logger":"provider.aws","msg":"using aws session","region":"eu-west-1","external id":"","credentials":null}

Jus tried with SecretStore instead of ClusterSecretStore and got the same error:
apiVersion: external-secrets.io/v1beta1
kind: SecretStore
metadata:
  name: aws-secretsmanager
  namespace: controlplane
spec:
  provider:
    aws:
      service: SecretsManager
      region: eu-west-1
---
apiVersion: external-secrets.io/v1alpha1
kind: PushSecret
metadata:
  name: postgresql
  namespace: controlplane
spec:
  updatePolicy: IfNotExists
  deletionPolicy: Delete
  refreshInterval: 168h
  secretStoreRefs:
    - name: aws-secretsmanager
      kind: SecretStore
  selector:
    secret:
      name: postgresql
  data:
    - match:
        remoteRef:
          remoteKey: controlplane/postgresql-smg

│ {"level":"error","ts":1713278342.1391892,"msg":"Reconciler error","controller":"pushsecret","controllerGroup":"external-secrets.io","controllerKind":"PushSecret","PushSecret":{"name":"postgresql","namespace":"controlplane"},"namespace":"controlplane","name":"postgresql","reconcileID":"31091df3-9a45-4696-a43d-6bd2b4ef8c6f","error":"could │
│  not verify if secret exists in store: not implemented","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.2/pkg/internal/controller/controller.go:329\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).proc │
│ essNextWorkItem\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.2/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.2/pkg/internal/controller/controller.go:227"}

updatePolicy: IfNotExists -> this is not yet available for some stores. Please remove it. It should work after that.

@gusfcarvalho I have made an attempt to implement this for the secret store. I did test the change locally and works fine when a secret is pushed however pushing the whole secret is still not implemented so that won't work.
I also need to check if similar implementation should be done for the aws parameter store?

@gusfcarvalho I have made an attempt to implement this for the secret store. I did test the change locally and works fine when a secret is pushed however pushing the whole secret is still not implemented so that won't work.
I also need to check if similar implementation should be done for the aws parameter store?

Having only AWS SM is fine


What happens if multiple CUDA GPUs are available?

We very probably never tested this. So what happens?

According to the documentation, the CUDA runtime creates a context for what it thinks is the fastest device if you need only one. So very likely having more than one CUDA device is uncritical.


Terraform SAP provider 500 error while provisioning multiple resources

Is there an existing issue for this?

[X] I have searched the existing issues

What type of issue are you facing
bug report
Describe the bug
I have written a terraform code for different BTP resources and then created a main.tf file where I am calling modules for provisioning of BTP resources. When I have added 3-4 resources then I was not getting any error but when I have completed with incorporating all eight resources module for provisioning then it gives an error of 500. Sample error
"Error: unableToCreateClient
│
│   with module.role.provider["registry.terraform.io/sap/btp"],
│   on Modules/prod/produs/btp/role/provider.tf line 10, in provider "btp":
│   10: provider "btp" {
│
│ received response with unexpected status [Status: 500; Correlation ID: 718fcf36-1b2e-f6de-759b-07ed33b543d9]"
Terraform version used: 1.8.5
Expected Behavior
While running terraform plan and apply this error is coming unexpectedly. but expected behaviour is that terraform plan and apply command will run without any error.
Steps To Reproduce
No response
Add screenshots to help explain your problem

Additional context
No response

Closing this as duplicate to https://github.com/SAP/terraform-provider-btp/issues/840. You find the answer to your question there


Lanteglos by Fowey CON

Please move any search records attached to the PARMS entry to the entry as an alternative to Lanteglos Highway. Leave the PARMS entry where it is.
Geoff

Done


Paper

###Tasks

[ ] Release the code (#8)
[ ] Work with Matt
[ ] Where to submit (e.g., ApJS)?

Example Papers

yt
Trident
Galaxy Cluster Merger Catalog

ApJS-yt
ABSTRACT

Why they developed yt.
Functionality and usage of yt.
How yt is structured and its underlying numerical methods and algorithms.
Key words.

INTRODUCTION

Why developed yt and its position in analytical tools.
Timeline and revolution of yt.
Brief introduction and advantages of yt.

Programming language.
Where will you use yt.
What platform does yt runs on.
Used example and production run.

Structure of this paper.

Outline of the Paper
ABSTRACT
1. INTRODUCTION

Why develop libyt?
Advantage and usage of libyt?
Introducing libyt:

libyt originated in Enzo.
Basic idea of libyt.
libyt is built with C++ and Python. It is aimed for all C++ simulation codes that are supported by yt.
Show libyt has already and can be implemented in simulation codes.

Gamer
Enzo

Example.

A time series of very big data sets.

Supoprted yt functionalities.

Basically all...

Outline of this paper.

2. MECHANISMS FOR DOING INLINE-ANALYSIS IN PARALLEL
2.1 Embedding Python in C++ Application

Brief description of Python and NumPy API.
Creation of libyt Python module.
How it loads data from C++ to Python.
Building C++ extended Python methods.
Loading user's inline Python script.

2.2 Connecting libyt to yt

View libyt as another yt frontend.
How libyt inherit other frontend's field definitions.

2.3 Parallelism

How libyt is paralleled is heavily rely on yt.

Some distribute jobs according to where the grids data are stored. (ex: Projection)
Others. (ex: Slice)

How to deal with getting non-local data.

3. CODE METHOD
3.1 Supporting In-Memory Field Data and Collecting Grid Information

Collecting hierarchy from each rank.
Connect in-memory field data to Python.

Supporting ghost zone.

3.2 Supporting Derived Fields

Definition of derived fields.
Why do we need this?

Some calculations cannot be done in yt. (ex: EoS, #19 )
Save memory space. (ex: MHD face-centered to cell-centered.)

How required data is generated and passed back to Python.

3.3 Supporting Particle Data

Particle data type may be discrete and is not a contiguous array in memory space.
How to collect discrete data and pass back to Python.

4. DEMONSTRATION: HOW TO IMPLEMENT LIBYT TO SIMULATION CODE

libyt is aimed for all frontends supported by yt.
A C++ library for yt.

4.1 Initialization
4.2 Setting yt Parameters
4.3 Setting Code Specific Parameters
4.4 Setting Fields Information
4.5 Setting Particles Information
4.6 Setting Local Grids Information
4.7 Commiting Your Settings
4.8 Performing Inline-Analysis

How to use yt_inline and yt_inline_argument
How to convert your post-processing script to inline script.

4.9 Freeing Resource
4.10 Finalization
5. PRODUCTION RUN AND PERFORMANCES

#19
Time Consumption - Number of Nodes graph.

6. FUTURE DIRECTIONS

Support Fortran (ex: FLASH).
Support ParaView for inline-rendering. libyt has the potential to give another way for simulation codes to support inline-analysis in ParaView.


Enable address verification while on-chain records are pending

Instead of waiting for on-chain records to be confirmed (up to several minutes) to verify a crypto address, allow the user to verify while they wait for confirmation. Much smoother user experience, which is now enabled by new backend logic.

/gcbrun


feat(odd): add running protocol screen

Overview
Add Running Protocol screen
robot-server has a key issue. As a result CurrentRunningCommand only works for the first run.
This will be solved soon.
I avoid merging edge into this branch temporary since that may break the remote dev tools.
RCORE-

Test Plan

Send a Protocol to an OT-3/dev kit
All Protocols -> Tap the protocol you sent
Tap Run protocol
Tap play button

Changelog

add Running Protocol page
add CurrentRunningProtocolCommand
add RunningProtocolCommandList
add RunningProtocolSkelton

Review requests
This PR is using CommandText that the Desktop app uses, but the style is different and currently passing styleProp to expand the style for the ODD. If there is any better way, please let me know.
Also the running test might be not enough since protocol files I have is very limited. If you can run your own protocol file, that will be awesome.

Risk assessment
low

also this can be rebased on edge now that the dev tools PR is merged right?


Unable to sign-in to GitHub using VSCode

Extension version: 0.13.0

VSCode Version: 1.40.0

OS: Windows 10

Steps to Reproduce:

The issue is resolved.


[BUG] Static files broken

Describe the bug
I want to expose api endpoint from which I can download static directory. I get 2 unexpected behaviors:

When I want to reach my endpoint <IP_ADDRESS>/static I see No operations defined in spec!
From tutorials(mentioned below) I understood it takes file from my app directory? Unless I copy it to root of my OS I get error raise RuntimeError(f"Directory '{directory}' does not exist").

This is really important for my home project to make sense so any input is really appreciated because I'm stuck on this.
To Reproduce
Code:
from starlette.staticfiles import StaticFiles
from fastapi import FastAPI

app = FastAPI(title="static_api")
app.mount("/static", StaticFiles(directory="static"))

Dockerfile:
FROM python:3.7
RUN pip install aiofiles fastapi uvicorn python-multipart
EXPOSE 80
COPY ./app /app
COPY ./static /static

CMD ["uvicorn", "app.main:app", "--host", "<IP_ADDRESS>", "--port", "80"]

I use docker build -t myimage . and docker run -p 80:80 myimage.
Expected behavior
Download static directory(or at least any file from this dir) from <IP_ADDRESS>/static
Environment:
Docker above.
Already viewed and tried issues/tutorials
https://fastapi.tiangolo.com/tutorial/static-files/
https://www.starlette.io/staticfiles/
https://github.com/tiangolo/fastapi/issues/130

Even if this answer comes a little late, maybe it helps others, because I got into the same problem in the beginning.
I am not sure if this is a bug either?
Because it's called static file and not static directory.
So you won't be able to request a folder, only a file, which has to be explicit.
<IP_ADDRESS>/static/exisiting_file
if you want to get files as folder you could zip your files to one file
<IP_ADDRESS>/static/exisiting_files.zip
If the error result is that the folder was not found, then a wrong specification must have happened. The following should run, if you want static inside you app-folder:
from starlette.staticfiles import StaticFiles
from fastapi import FastAPI

app = FastAPI(title="static_api")
app.mount("/static", StaticFiles(directory="app/static"))

So you don't need to copy the static folder in dockerfile additionaly.

Thanks @dmontagu for the help here!
I think that should answer the question, right @MLman99 ?

I have the same issue. I am running this fullstack template (https://github.com/Zaffer/fastapi-fullstack) then trying to implement Jinja2 templating as per this page (https://fastapi.tiangolo.com/advanced/templates/). Code looks like this:
from typing import Any, List

from fastapi import APIRouter, Depends, HTTPException, FastAPI, Request
from fastapi.responses import HTMLResponse
from fastapi.staticfiles import StaticFiles
from fastapi.templating import Jinja2Templates
from sqlalchemy.orm import Session

from app import crud, models, schemas
from app.api import deps

router = APIRouter()

router.mount("/static", StaticFiles(directory="static"), name="static")

The logs return the following:
backend_1       | Traceback (most recent call last):
backend_1       |   File "/usr/local/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
backend_1       |     self.run()
backend_1       |   File "/usr/local/lib/python3.7/multiprocessing/process.py", line 99, in run
backend_1       |     self._target(*self._args, **self._kwargs)
backend_1       |   File "/usr/local/lib/python3.7/site-packages/uvicorn/subprocess.py", line 62, in subprocess_started
backend_1       |     target(sockets=sockets)
backend_1       |   File "/usr/local/lib/python3.7/site-packages/uvicorn/main.py", line 390, in run
backend_1       |     loop.run_until_complete(self.serve(sockets=sockets))
backend_1       |   File "uvloop/loop.pyx", line 1494, in uvloop.loop.Loop.run_until_complete
backend_1       |   File "/usr/local/lib/python3.7/site-packages/uvicorn/main.py", line 397, in serve
backend_1       |     config.load()
backend_1       |   File "/usr/local/lib/python3.7/site-packages/uvicorn/config.py", line 278, in load
backend_1       |     self.loaded_app = import_from_string(self.app)
backend_1       |   File "/usr/local/lib/python3.7/site-packages/uvicorn/importer.py", line 20, in import_from_string
backend_1       |     module = importlib.import_module(module_str)
backend_1       |   File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module
backend_1       |     return _bootstrap._gcd_import(name[level:], package, level)
backend_1       |   File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
backend_1       |   File "<frozen importlib._bootstrap>", line 983, in _find_and_load
backend_1       |   File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
backend_1       |   File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
backend_1       |   File "<frozen importlib._bootstrap_external>", line 728, in exec_module
backend_1       |   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
backend_1       |   File "./app/main.py", line 4, in <module>
backend_1       |     from app.api.api_v1.api import api_router
backend_1       |   File "./app/api/api_v1/api.py", line 3, in <module>
backend_1       |     from app.api.api_v1.endpoints import items, login, users, utils, tests
backend_1       |   File "./app/api/api_v1/endpoints/tests.py", line 14, in <module>
backend_1       |     router.mount("/static", StaticFiles(directory="static"), name="static")
backend_1       |   File "/usr/local/lib/python3.7/site-packages/starlette/staticfiles.py", line 55, in __init__
backend_1       |     raise RuntimeError(f"Directory '{directory}' does not exist")
backend_1       | RuntimeError: Directory 'static' does not exist

the static folder is in the same directory as this python file.
Please help.

I figured it out by getting the correct path with:
from os import path

logging.basicConfig(level=logging.INFO)
logger = logging.getLogger(__name__)

router = APIRouter()

path_str = path.dirname(path.realpath(__file__))
logger.info("relative path of static folder: %s", path_str)

router.mount("/static", StaticFiles(directory="/app/app/api/api_v1/endpoints/static"), name="static")

I just had the same problem when I was doing unit testing and solved it as follows:
from pathlib import Path
BASE_DIR = Path(file).resolve().parent
app.mount("/static", StaticFiles(directory=Path(BASE_DIR, 'static')), name="static")

The following line should work too
app.mount("/static", StaticFiles(directory="../static"), name="static")

I have the same problem.
Solution
Replace your code: app.mount('/static', StaticFiles(directory='static'), name='static')
with blew code
import os
app.mount('/static', StaticFiles(directory=os.path.join(current_dir, 'static')), name='static')


Relax httpPayload constraints

Using smithy-model 1.3.0 :
The problem:
The httpPayload trait is currently constrained to target a member that itself points to  :

a structure
a blob
a string
a union
a document

I'm trying to translate a couple of my organisation's APIs to smithy semantics, to assess whether it'd work for us as an IDL. We have several endpoints (think rest-json) that return maps/lists in the body of the responses, which is currently not possible to describe in smithy (using out-of-the-box features) due to the constraints on the httpPayload trait.
And educated guess tells me that the constraints on the httpPayload trait come from the xml-based protocols which AWS uses. Imho, these constraints should not be inherent to the trait, but rather tied to protocol-specific validation logic.
Obvious, I'd prefer not having to define my own http-bindings set of traits, as piggybacking on the ones provided out of the box drastically lowers the effort required for building tooling.
My questions :

Would AWS consider relaxing the constraints on the httpPayload trait ?
Is there a current workaround I could use short-term that would let me override the constraints, either via pure-smithy semantics, or via a service-provider ? (NB : I'm using a different build-tool than Gradle and the smithy-build.json semantics are of no use to me, currently anyway)

PS : I'm greatly enjoying prototyping tooling around smithy, keep up the good work 😄

Thanks for raising this issue. I think we'd be open to expanding the httpPayload trait to support lists, maps, and sets. We'll do more research to see what the estimated effort for this would be in AWS SDKs and our internal frameworks.

The more I think about this the more I think we should do it. OpenAPI does seem to allow it, and technically a Document shape could be any json-like data so it kind of already is allowed. I still need to do some research to see if it breaks any AWS tooling (and if so, how we mitigate that) but one way or another I think it should be done.

Are there any plans to update the HTTP spec documentation and add tests to the rest-json-1 protocol test suite to exercise this new functionality?

Are there any plans to update the HTTP spec documentation and add tests to the rest-json-1 protocol test suite to exercise this new functionality?

As the documentation introduced in #683 indicates, the AWS protocols do not support this behavior at this time.

As the documentation introduced in #683 indicates, the AWS protocols do not support this behavior at this time.

We'll do new documentation build once this goes out in a release

We'll do new documentation build once this goes out in a release

Thank you.

Thank you.


Installation of appsvcs fails

Environment

Application Services Version: 3.24.0
BIG-IP Version: BIG-IP v<IP_ADDRESS> (Build 0.0.5), BIG-VE Azure Marketplace image

Summary
Installation of appsvcs fails, isn't usable.
Steps To Reproduce
Steps to reproduce the behavior:

Followed the steps to install appsvcs using the BIG-IP Configuration Utility (https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/userguide/installation.html#success)

Attempted to verify the installation by sending a GET to the /mgmt/shared/appsvcs/info endpoint, but received the following:

{
  "code": 404,
  "message": "Public URI path not registered. Please see /var/log/restjavad.0.log and /var/log/restnoded/restnoded.log for details.",
  "referer": "<IP_ADDRESS>",
  "restOperationId": 6073118,
  "errorStack": [
    "com.f5.rest.common.RestWorkerUriNotFoundException: Public URI path not registered. Please see /var/log/restjavad.0.log and /var/log/restnoded/restnoded.log for details.",
    "at com.f5.rest.workers.ForwarderPassThroughWorker.cloneAndForwardRequest(ForwarderPassThroughWorker.java:572)",
    "at com.f5.rest.workers.ForwarderPassThroughWorker.access$000(ForwarderPassThroughWorker.java:44)",
    "at com.f5.rest.workers.ForwarderPassThroughWorker$1.completed(ForwarderPassThroughWorker.java:314)",
    "at com.f5.rest.workers.ForwarderPassThroughWorker$1.completed(ForwarderPassThroughWorker.java:311)",
    "at com.f5.rest.workers.EvaluatePermissions.completeEvaluatePermission(EvaluatePermissions.java:150)",
    "at com.f5.rest.workers.EvaluatePermissions.evaluatePermission(EvaluatePermissions.java:78)",
    "at com.f5.rest.workers.ForwarderPassThroughWorker.onForward(ForwarderPassThroughWorker.java:342)",
    "at com.f5.rest.workers.ForwarderPassThroughWorker.onGet(ForwarderPassThroughWorker.java:753)",
    "at com.f5.rest.common.RestWorker.callDerivedRestMethod(RestWorker.java:1230)",
    "at com.f5.rest.common.RestWorker.callRestMethodHandler(RestWorker.java:1148)",
    "at com.f5.rest.common.RestServer.processQueuedRequests(RestServer.java:1401)",
    "at com.f5.rest.common.RestServer.access$000(RestServer.java:48)",
    "at com.f5.rest.common.RestServer$1.run(RestServer.java:329)",
    "at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)",
    "at java.util.concurrent.FutureTask.run(FutureTask.java:262)",
    "at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)",
    "at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)",
    "at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)",
    "at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)",
    "at java.lang.Thread.run(Thread.java:748)\n"
  ],
  "kind": ":resterrorresponse"
}

Expected Behavior
Expected appsvcs to start, but it didn't.
Actual Behavior
appsvcs isn't available after the installation, noticed the following logs in "/var/log/restnoded/restnoded.log"
Thu, 10 Dec 2020 15:25:36 GMT - severe: [f5-service-discovery: restWorkerTask.js] {"killed":false,"code":1,"signal":null,"cmd":"tmsh -a list ltm data-group internal /Common/ServiceDiscovery/tasks"}
Thu, 10 Dec 2020 15:25:36 GMT - severe: [RestWorker] [RestWorker] worker failed to start: Error: Command failed: tmsh -a list ltm data-group internal /Common/ServiceDiscovery/tasks
:shared/service-discovery/task

Thu, 10 Dec 2020 15:25:37 GMT - severe: [appsvcs] {"message":"Failed to complete startup. Error: Command failed: tmsh -a create sys folder /Common/appsvcs\n\n    at ChildProcess.exithandler (child_process.js:202:12)\n    at emitTwo (events.js:87:13)\n    at ChildProcess.emit (events.js:172:7)\n    at maybeClose (internal/child_process.js:854:16)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)","level":"error"}
Thu, 10 Dec 2020 15:25:37 GMT - severe: [RestWorker] [RestWorker] worker failed to load state: [object Object]:shared/appsvcs

@edarzins what user are you using to install the RPM. Please can you try admin user

Closing for inactivity. If you are still encountering issue, please reopen this ticket for a file a new one.


AVS not giving response through 3.5mm jack in raspberrypi 3

Hi,
i have installed updated avs sdk version in raspbian strech.alexa is responding but it's not giving voice output through 3.5mm jack.
I have tried in different ways but it's not doing .any suggestions?

I experienced same situation, though when I tested the speaker sepately, it
worked just fine.
On Fri, Mar 30, 2018, 03:59 jay7583<EMAIL_ADDRESS>wrote:

Hi,
i have installed updated avs sdk version in raspbian strech.alexa is
responding but it's not giving voice output through 3.5mm jack.
I have tried in different ways but it's not doing .any suggestions?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/alexa/avs-device-sdk/issues/591, or mute the thread
https://github.com/notifications/unsubscribe-auth/AF3g9KiKu_ylHO1fmlhI7L58SOWNpbNmks5tjfQAgaJpZM4TBeCw
.

3.5 mm jack is working i checked with audacity and other applications. it's giving output except for avs-sdk

Agreed, appears the issue is with avs-sdk.
On Fri, Mar 30, 2018, 08:31 jay7583<EMAIL_ADDRESS>wrote:

3.5 mm jack is working i checked with audacity and other applications.
it's giving output except for avs-sdk
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/alexa/avs-device-sdk/issues/591#issuecomment-377524664,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF3g9I_IWV5LwPDyAgjzVTdYa7VEsBPaks5tjjPAgaJpZM4TBeCw
.

Hi,
We have seen this issue on few raspberry pi's. Have you be able to play with USB/HDMI headset.
Can you provide your ~/.asoundrc settings.
Thanks
Priya

Hi @jay7583, please look at the "No audio output from SDK" section in https://github.com/alexa/avs-device-sdk/wiki/Troubleshooting-Guide and see if it helps.  Thanks!

Please also see #577, #517 and #516 where this was solved by other users.  I'll close this for now - please re-open if you require further guidance.


⚠ Bofrost.be has degraded performance

In d641f4b, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1028 ms

Resolved: Bofrost.be performance has improved in 8a15807 after 6 minutes.


Local pull request success status testing

Docs Build status updates of commit fbb1560:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

E2E_DocsBranch_Prod_Dynamic/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Feature/refactor importer

@etagwerker @mauro-oto this reduces codeship code duplication issues. check it out! cheers 🎉

@etagwerker what do you think about the latest changes? I moved the calculation to a seperate concern and included it in the leaderboard model.

@schmierkov :+1:


Added support for middleware activation via IMiddlewareFactory

Fixes #754
IMiddlewareFactory and IMiddleware are new extensiblity points for
activating and authoring middleware. Under the covers, middleware is still
very much just a function. This just provides a nice way to get a per request
activated middleware instance that is created and released via the IMiddlewareFactory (this critical for non conforming containers, see https://github.com/dotnetjunkie/Missing-Core-DI-Extensions/blob/7efd3c3f1aa6330d303d0a3e2d28fdc43687b9f4/src/SampleApplication.SimpleInjector/Startup.cs#L52-L55 for more details).
The caveats are that middleware needs to be registered in the container (by default)
and that not possible to explicitly pass arguments directly via UseMiddleware.
Added tests

/cc @Tratcher @halter73 @pakrym

🆙 📅

What does the perf look like for middleware with the various lifetimes? E.g. singleton vs scoped.

What exactly are you asking? What he cost of resolving middleware instances per request is? What will that data change?

If there's a high overhead to resolve middleware per request then it will be hard to recommend this to anyone.

Please read the PR description outlining the reason we're adding this in the first place (non conforming containers). On top of that, mvc controllers are created once per request so are many other objects along the request pipeline. The DI container is also extremely efficient at creating new objects so I'd be extremely suprised if this causes any real problems. People have to do this today if they anyway if they want to use a non conforming container (see the code sample in the PR description).

Were you planning to convert any of our middleware?

Nope. Although maybe we should use it somewhere so we can have something validating this code path.

:shipit:


Pass query elements into Query constructor.

Compute encrypted query elements, and pass in as part of query
construction rather than adding them afterwards to an existing query.
Other minor tidy-up, using interfaces, renaming boolean returning
methods for exp tables.

+1 LGTM

+1 - will merge now


[enhancement][CI] Add go install command in Travis

Now the build in Travis CI only checks the code style and run test cases, I think we should add go install github.com/tensorflow/k8s/cmd/tf_operator to ensure that the binary could be built successfully.
WDYT @jlewi @jose5918

Seems reasonable.
What is the plan with respect to what we use Travis for as opposed to what we use Prow for?
I think it would be nice to converge on a single system. I don't think travis is sufficient to run our E2E tests but prow could probably be used to run unittests pretty easily.
We already use Prow to run pyunittests. We'd just need to add a step to our prow workflows to run the relevant go commands.

@gaocegege The slowness of our tests has nothing to do with prow but what the test is doing. Our tests are slow because we are creating a GKE cluster and then running TFJobs on them with/without GPUs. That's the slow part.
So if we want to have a bunch of smoke tests (e.g. check code builds, run unittests) we should be able to do this with prow and have it execute reasonably fast. I don't think we necessarily need travis just to do that.
Travis is convenient though so I don't think there's any urgency to move tests out of travis to prow.

Then LGTM, I think we could remove Travis, since it is not in high priority.

Then LGTM, I think we could remove Travis, although it is not in high priority.

Travis can be used to run unit tests and it is quite handy for that.

kubeflow/testing#33 adds a simple prow job that just runs lint and python unittests. Its an example of how we could use prow to replace  Travis for this. (That prow job is more useful than just e2e testing because it ensures changes to kubeflow/testing don't break our prow test infrastructure).
My hope is that we can define a standard workflow that does a bunch of basic checks

lint (go, python, mark down)
unittests (go, python)

And then we could just add that workflow to every repository.


generate more actions - login

@keybase/react-hackers this is ready. please test out this code since it touches the login flow a bit


fix(TDI-40596):tSalesforceOutput upsert return wrong rejected records when using extend insert

What is the current behavior? (You can also link to an open issue here)
For JIRA: https://jira.talendforge.org/browse/TDI-40596
What is the new behavior?
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[x] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Pull request test result: success :star:
Sonar results

Pull request test result: success :star:
Sonar results


TrustKit was initialized with a different network policy than the one configured in the App's manifest.

Hi @Speed-stack ,
As far as I know, TrustKit can not be initialized with different network policy. It throws an exception.
Could you give the steps you followed to conclude that TrustKit was initialized with a different network policy?

cc: @sachin-chauhan-dev


Is there a way to list exiting boxes and check if a certain box exists?

Didn't find api for:

Getting list of existing/not empty Hive boxes
Checking by box name if it has bern created before (and/or is not empty)

Are there any options? Thanks

Getting list of existing/not empty Hive boxes

I think this feature have not yet implemented into hivedb.

Checking by box name if it has bern created before (and/or is not empty)

Did you tried using .boxExists method for checking exists boxes?
bool exists = await Hive.boxExists('boxName');

Thanks. It seems the way to check for existing boxes is to list *.hive files in app's direcotry (they are named after boxes' names).
P.S.: the use case for listing existing boxes is to keep track of potential grabage and clean it

Thanks. It seems the way to check for existing boxes is to list *.hive files in app's direcotry (they are named after boxes' names).
P.S.: the use case for listing existing boxes is to keep track of potential grabage and clean it

Yes you can list exists boxes by listing *.hive files. This was not implemented in hive because user may store hive files in any directory not just app's data dir.


question

Bro, Did you use "test token" as RAINDROP_TOKEN?
And second question is, what do I need to put in collection id? Because I've more than 1 collection.

Hey, sorry for late reply, and yes I used the test token for auth.
You can fetch all of your collections with this single endpoint. Just update your collection id.
'https://api.raindrop.io/rest/v1/raindrops/0?perpage=50&collectionId=yourCollectionID"

Hey @XahidEx,
I have found a new solution to fetching Raindrop API's. I used to fetch all the data from the API but it was not good for my scenario. I update the method to fetch for only relevant collection. You can find the example in here.


feat: Entity explorer - page container resize, fluid typography

Description
This PR includes the responsive font size for entity explorer and page container resize changes.
Fixes #11284
Type of change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Tested in chrome dev tools for fluid typography changes

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: feat/entity-explorer-resize-page-fluid-typography

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
56.62 (0)
38 (0)
36.17 (0.02)
56.84 (0)

:red_circle:
app/client/src/pages/Editor/Explorer/Entity/index.tsx
91.67 (-0.09)
85.71 (0)
83.33 (-0.88)
91.25 (-0.11)

:green_circle:
app/client/src/pages/Editor/Explorer/Pages/index.tsx
84.29 (1.24)
73.08 (-1.92)
47.06 (4.2)
83.82 (0.77)

:red_circle:
app/client/src/utils/autocomplete/TernServer.ts
52.71 (-0.23)
40.83 (-0.84)
36.21 (0)
56.74 (-0.25)

:sparkles: :new:
app/client/src/utils/hooks/useResize.tsx
45.95
40
66.67
48.39

/ok-to-test sha=66378e0

/ok-to-test sha=27d2634

/ok-to-test sha=dda00cb

/ok-to-test sha=f3708e4

/ok-to-test sha=3371dc2

/ok-to-test sha=8ff4a38

/ok-to-test sha=308cb2f

/ok-to-test sha=86e7560

/ok-to-test sha=6b2a8af

/ok-to-test sha=596ba5b

/ok-to-test sha=a92fa4d

/ok-to-test sha=97a8a82

/ok-to-test sha=d624288

/ok-to-test sha=b575456

Closing this PR as the issue has been fixed in #13576


license for pds-tools?

Hey so there were some good ideas revolving around exceptions in the cspyce codebase that has been removed a few commits ago that I want to use in spiceypy. Is there a license for the project that I can list or is the code considered public domain? I think by default it is all rights reserved with github so could the code be relicensed to be free?

cspyce has been moved to its own repo https://github.com/SETI/pds-cspyce. It is licensed under Academic Free License ("AFL") v. 3.0.


k8s login 403

when request /api/login, response 403 forbidden

@sunerlin why close?

@sunerlin I also met this question. Can you answer it

Similar as: https://github.com/casdoor/casdoor/issues/1273


Switch to CC0 public domain license

See https://www.mozilla.org/en-US/MPL/license-policy/
This is to facilitate reuse of this example code.

When adding a license file to any project it is recommended that we document the permission of previous contributors to ensure that they understand and agree to the license.
So if you've contributed to this repository (all users included in the list below) and agree to give permission for us to switch this to CC0, please add the following comment to this issue:

I give my permission to license under the MPL 2 any contributions I have made to the debugger.html code base.

Contributors:

[ ] @irfanhudda
[ ] @abhishekg785
[ ] @jbhoosreddy
[ ] @ThomasCrevoisier
[ ] @arthur801031

@captainbrosset Yes of course, no problem for me :)

I give my permission to license under the CC0 any contributions I have made to the debugger-examples code base. :)

I give my permission to license under the CC0 any contributions I have made to the debugger-examples code base.

I give my permission to license under the CC0 any contributions I have made to the debugger-examples code base.

I've reached out to @abhishekg785 by email too last week and I have received no replies.
Let's land this.


[question] Is it better replacing downloading k8s components from googleapis with apt-install from aliyun mirrors in allinone_aliyun.sh?

Question

The kubernetes deployment steps on ubuntu in allinone_aliyun.sh need to download components from https://storage.googleapis.com/kubernetes-release. This site couldn't be visited normally in some cases.:) So why don't replace it with apt-installing from aliyun mirrors. The same as in doc pouch_with_kubernetes_deploying_aliyun.
If need, i am glad to handle with it.

@mathspanda welcome ~ just don't hesitate to file pr.
cc @manlge
ping


swagger-zod produces wrong tuple syntax

What version of kubb is running?
HEAD
What platform is your computer?
WSL
What version of external packages are you using(@tanstack-query, MSW, React, Vue, ...)

What steps can reproduce the bug?
According to my understanding of the zod spec, tuples do not support min and max. Hence, the schema snippet below produces invalid syntax. My IDE also concludes the same:

schema:
    PetTuple:
      maxItems: 2
      minItems: 2
      prefixItems:
        - type: string
        - type: string
      title: Attributes
      type: array
      description: Tuple of exact length 2

produces
export const petTuple = z.tuple([z.string(), z.string()]).min(2).max(2)

How often does this bug happen?
None
What is the expected behavior?
export const petTuple = z.tuple([z.string(), z.string()])

Swagger/OpenAPI file?
No response
Additional information
See #1017

This will be fixed with v2.19.2

It works for the test case provided, but when the tuple is a property within an object, it fails again:
 FAIL  packages/swagger-zod/src/SchemaGenerator.test.tsx > Zod SchemaGenerator > 'PetTupleObject'
Error: Snapshot `Zod SchemaGenerator > 'PetTupleObject' 1` mismatched

- Expected
+ Received

  "export const petTupleObject = z
-   .object({ tupleProperty: z.tuple([z.string(), z.string()]).optional() })
+   .object({ tupleProperty: z.tuple([z.string(), z.string()]).min(2).max(2).optional() })
    .describe('Tuple of exact length 2 nested in an object')
  "

@helt Released another version that will work in objects: v2.19.3


Turbo Issue with Livewire

when navigating from one page to another page with Turbo on livewire full page component, the page load well but prevent livewire function from working, E.g the wire:click="" stop working and mount function as well

Are you using the Livewire Turbolinks bridge?

thank you it work well now with Livewire Turbolinks bridge


[C4GT] Discovery of Beckn Platform via Search Technology

Description
This proof of concept is to evaluate how search engines can be used to index beckn websites and make them discoverable. It is an alternate model to a central registry based mechanism.
Goals
Bpp

[ ] Bpp to host a signed beckn descriptor file on their domain issued by a certification authority.
[ ] Search engines should be able to verify this descriptor and index their catalogue.
[ ] Bpps should be able to push changes to their catalog incrementally to the search engine(s).

Bap

[ ] Bap can also host a signed beckn descriptor file on their domain issued by a certification authority.
[ ] Baps can discover Bpps and their products via search engines (like beckn gateway)
[ ] Bpps should be able to verify Baps signatures using the bap's beckn descriptor.

Expected Outcome
Peers should be able to verify each other and transact as an open network with no central controlling facilitator.
Acceptance Criteria

[ ] Beckn reference Gateway to be enhanced to function as a search engine.
[ ] A Reference Bpp should be able to push catalog changes to the gateway
[ ] Reference Bap should be able to choose the gateway as a search engine for discovery purposes.

Implementation Details

A github repo consisting of certification authorities ,search engines and their Public keys.
Beckn.json (beckn descriptor) file can be signed by one of the authorities.
The authority may host the beckn registry for validating endpoints and keys.
*.  Once validated, the apps will be issued a beckn.json file affixed with their signature.
Lucene to be used for indexing the catalog.
/search of gateway to look into local indexed catalog
unsolicited /on_search from bpp to be used to push full/part catalog

Mockups / Wireframes
[Include links to any visual aids, mockups, wireframes, or diagrams that help illustrate what the final product should look like. This is not always necessary, but can be very helpful in many cases.]

[Please note that the below section of the ticket has to be in the format as mentioned as it is key to enabling proper listing of the project. Please only choose the options mentioned under the headings wherever applicable.]
Product Name
Beast - Beckn Application discovery via search technologies.
Project Name
Beast - Beckn Application discovery via search technologies.
Organization Name:
Beckn
Domain
Trade and Commerce
Tech Skills Needed:
Java, React
Mentor(s)
[@venkatramanm] [@raviprakash]
Complexity
Medium
Category
Poc
Sub Category
API, FrontEnd, Backend, SEO, Research

hello @venkatramanm , @raviprakash , can I work on this issue?
Could you please assign this and mentor me?

hey there, i have gone through it can i please contribute to this project

Hello this comment is part of the DMP review @SaumyaSamagra @dmp24-c4gt
May I suggest including links to a) beckn documentation, and b) the definitions of BPP and BAP
My feeling is that this issue has quite a bit of initial ramp-up from reading and understanding, but once that's done the implementation should be doable within the timeframe of the DMP

Do not ask process related questions about how to apply and who to contact in the above ticket. The only questions allowed are about technical aspects of the project itself. If you want help with the process, you can refer instructions listed on Unstop and any further queries can be taken up on our Discord channel titled DMP queries.


WIP: TimeoutExtender: Auto-extend the VisibilityTimeout of unhandled messages

This is a work-in-progress PR for initial review only. Tests are still being polished.
This feature is a breaking change, as it requires the full Squiss Message object to be passed to Squiss.deleteMessage and Squiss.releaseMessage, whereas those functions could previously operate on just a receiptHandle. It also requires the Message object to be passed to Squiss.handledMessage, whereas this function did not previously require any arguments. Therefore, the release following this merge will require a major version update.

Looks good minus the time issues. Not seeing any tests, assuming maybe to get this out quicker, but seems solid from just reading through with the knowledge I have of SQS.

Thanks! Still working the tests-- see the first line of the PR description ;-)

Haha, glanced right past that.

🍪


contribute

docs(readme): mission
docs(readme): commit
docs(readme): contribute

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Style/NestedParenthesizedCalls autocorrect breaks code

Code before rubocop -a is run:
Dalli::Client.new(
  Settings.get! :memcached_url,
  serializer: self
)

Expected behavior
Dalli::Client.new(
 Settings.get!(:memcached_url),
 serializer: self
)

Actual behavior
Dalli::Client.new(
  Settings.get!(:memcached_url,
  serializer: self)
)

(spacing corrupted by copy-paste to github, the relevant misbehaviour is the wrongly place parenthesis)
Steps to reproduce the problem
Run rubocop -a on the first snippet.
RuboCop version
Include the output of rubocop -V or bundle exec rubocop -V if using Bundler. Here's an example:
$ [bundle exec] rubocop -V
0.77.0 (using Parser <IP_ADDRESS>, running on ruby 2.6.2 x86_64-linux)

This is an expected behavior. The coupling for each parentheses position is as follows.
% ruby-parse -e 'foo(bar :arg, key: value)'
(send nil :foo
  (send nil :bar
    (sym :arg)
    (hash
      (pair
        (sym :key)
        (send nil :value)))))

% ruby-parse -e 'foo(bar(:arg, key: value))'
(send nil :foo
  (send nil :bar
    (sym :arg)
    (hash
      (pair
        (sym :key)
        (send nil :value)))))

The above two are the same result. If parentheses are added to the method call of the first argument, the result will be different.
% ruby-parse -e 'foo(bar(:arg), key: value)'
(send nil :foo
  (send nil :bar
    (sym :arg))
  (hash
    (pair
      (sym :key)
      (send nil :value))))

And an executed example is as follows.
% cat example.rb
def foo(arg, **options)
  puts "foo(#{arg}, #{options})"
end

def bar(arg, **options)
  puts "bar(#{arg}, #{options})"
  :bar
end

puts '## Case 1'
foo(bar 'hello', key: :value)
puts '## Case 2'
foo(bar('hello', key: :value))
puts '## Case 3'
foo(bar('hello'), key: :value)

% ruby example.rb
## Case 1
bar(hello, {:key=>:value})
foo(bar, {})
## Case 2
bar(hello, {:key=>:value})
foo(bar, {})
## Case 3
bar(hello, {})
foo(bar, {:key=>:value})

Thanks for your reply. I'll bookkeep this as you describe it.

BTW the actual Ruby behavior depends on the kind of the last argument.
Rubocop's behavior would be the same as Ruby's view if the last argument was only self. In the above case however, we have serializer: self which alters Ruby's behavior and binds the argument to the get! method, which lead me to creating this issue.
I assume that Rubocop does not differenciate between self and serializer: self. In any case, the code in the first block above should be avoided in any Ruby program since it is ambiguous.


Rework state management

See https://www.reddit.com/r/emacs/comments/kqutap/selectrum_prescient_consult_embark_getting_started/gi77l5e/?context=3
@clemera I took the freedom to create an issue here regarding this in order to keep it in mind.

Good idea, thanks!

Good idea, thanks!

Declare all variables as defvar-local if they are only intended to be used in the minibuffer. This makes their scope more clear.

Declare all variables as defvar-local if they are only intended to be used in the minibuffer. This makes their scope more clear.

For some variables we needed the first (global) value but when selectrum-repeat can be replaced by something better as discussed on the embark side this might not be the case anymore.

This will fix all recursive minibuffer issues forever!

I wonder if there an easy way to retrieve local values from the previous minibuffer session?

For some variables we needed the first (global) value but when selectrum-repeat can be replaced by something better as discussed on the embark side this might not be the case anymore.

This will fix all recursive minibuffer issues forever!

I wonder if there an easy way to retrieve local values from the previous minibuffer session?

I wonder if there an easy way to retrieve local values from the previous minibuffer session?

I only know the general way, find minibuffer-buffers and extract the local value from them. Why do we need this? I would like the recursive sessions to be independent! Is this not possible or not desired in some cases?

I wonder if there an easy way to retrieve local values from the previous minibuffer session?

I only know the general way, find minibuffer-buffers and extract the local value from them. Why do we need this? I would like the recursive sessions to be independent! Is this not possible or not desired in some cases?

I don't think we need it but it can be handy at times, I don't remember exactly where I have seen it unfortunately. One benefit of the let bound variables was that the values are available whatever buffer is selected, when removing this we have to make sure to always query the values from the minibuffer.

I don't think we need it but it can be handy at times, I don't remember exactly where I have seen it unfortunately. One benefit of the let bound variables was that the values are available whatever buffer is selected, when removing this we have to make sure to always query the values from the minibuffer.

One benefit of the let bound variables was that the values are available whatever buffer is selected, when removing this we have to make sure to always query the values from the minibuffer.

I don't understand this. You are also using setq-local at some places so you can never be sure. This is something I am very much against. This is like some kind of Heisen state, maybe being available maybe not.

One benefit of the let bound variables was that the values are available whatever buffer is selected, when removing this we have to make sure to always query the values from the minibuffer.

I don't understand this. You are also using setq-local at some places so you can never be sure. This is something I am very much against. This is like some kind of Heisen state, maybe being available maybe not.

Happy to close this issue! Thank you for tackling the state management, @clemera :+1:

Thank you, too for the discussion and help!


Issue with parameter 'location' and unitesstates instead of unitedstates

Just tried to export Office 365 Configuration using Export-O365Configuration function.
I just selected Teams on the selection screen and process failed without any further details from the command line but this details from the log file:
"Cannot validate argument on parameter 'Location'. The argument "unitedstates" does not belong to the set "canada,unitesstates,europe,asia,australia,india,japan,unitedkingdom,unitedstatesfirstrelease,southamerica,france,usgov" specified by the ValidateSet attribute. Supply an argument that is in the set and then try the command again."
It seams, unitedstates argument is just written as unitesstates in the ValidateSet Attribute.
OsName               : Microsoft Windows Server 2019 Standard
OsOperatingSystemSKU : StandardServerEdition
OsArchitecture       : 64-bit
WindowsVersion       : 1809
WindowsBuildLabEx    : 17763.1.amd64fre.rs5_release.180914-1434
OsLanguage           : en-US
OsMuiLanguages       : {en-US}
office365DSC version: <IP_ADDRESS>5

@ngeorgeault , yes there is clearly an error with the export of the allowed values in the PPPowerAppsEnvironment resource. However, this should not affect the Teams Workload, and should not be thrown when doing an Export. I will create a PR to have this fixed. In the meantime, try an unattended extract of Teams:
$creds = Get-Credential
Export-TargetResource -GlobalAdminAccount $creds -Quiet -Workloads Teams

Fixed


Deprecation warning in actions_secrets_parser

When running a deployment through GitHub actions to my app service, it shows the following warning in the logs:
(node:1733) [DEP0128] DeprecationWarning: Invalid 'main' field in '/home/runner/work/_actions/azure/webapps-deploy/v2/node_modules/actions-secret-parser/package.json' of 'lib/index.js'. Please either fix that or report it to the module author
This has been logged for future fixing.

It has been fixed as part of #280  and will go in next rollout which will be 2nd week of February.


Focussed Extension description is almost unreadable in default light theme

Issue Type: Bug
Select default light theme
Select some Extension in extensions list
Try to read text on Extension item
VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:19:29.629Z)
OS version: Linux x64 3.13.0-166-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz (3 x 3000)

GPU Status
2d_canvas: disabled_softwarechecker_imaging: disabled_offflash_3d: disabled_softwareflash_stage3d: disabled_softwareflash_stage3d_baseline: disabled_softwaregpu_compositing: disabled_softwaremultiple_raster_threads: disabled_offnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwaresurface_synchronization: disabled_offvideo_decode: disabled_softwarewebgl: disabled_offwebgl2: disabled_off

Load (avg)
1, 1, 1

Memory (System)
7.80GB (0.14GB free)

Process Argv
--unity-launch

Screen Reader
no

VM
100%

Extensions (4)

Extension
Author (truncated)
Version

QML
bbe
1.0.0

code-settings-sync
Sha
3.2.5

code-spell-checker
str
1.6.10

org-mode
too
0.5.0

@LaRusCat Can you please provide a screenshot of what you are seeing?

Yes of course!

Yes of course!

@LaRusCat Which theme are you using? And do you have any colour customisations in your settings? Also try to disable all extensions and check?

@sandy081 I am using "Light+ (default light)" theme.
And I don't have any color customization.
And this issue is reproducible after disabling all settings.
I can try to reset all setting (remove all configs or something like this). Or try to reinstall it completely.

@sandy081 looks like there is some problems in my configs(but I don't know how I broke this theme, because I didn't customize any themes, just switch between light and dark themes). I tested VSCode from an other user and theme works well.
I think I can close this issue.
Thanks!


Updated .openpublishing.redirection file

Docs Build status updates of commit 8de9cd9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit f17c9fa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Allow a web page to open new windows

Currently there is no handling for opening new windows/tabs. Tabs probably won't be implemented but it should be possible to allow web pages to open a new window. Make this configurable.

Implemented/fixed with 3b4cf2b.


Feature/fix installation

Modifies readme to describe local installation for testing with pytest, mention examples and python requirement.
Removes python 3.6 from travis script

Codecov Report

Merging #58 into develop will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop      #58      +/-   ##
===========================================
- Coverage    99.14%   99.13%   -0.01%
===========================================
  Files            6        6
  Lines          233      232       -1
===========================================
- Hits           231      230       -1
  Misses           2        2

Impacted Files
Coverage Δ

peridynamics/integrators.py
100.00% <0.00%> (ø)

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 f7d0699...2dc2de7. Read the comment docs.


cilium-node-init fails for AKS-nodes

Bug report
On AKS (tested with k8s 1.19.9 and k8s 1.20.5) the nodeinit container doesnt restarted unmanaged (kubenet managed) pods. It gives the following output:
Restarting kubenet managed pods
bash: line 59: docker: command not found
find: '/var/lib/cni/networks/': No such file or directory
Ensuring azure-vnet is configured in 'transparent' mode...
Node initialization complete
!!! startup-script succeeded!

General Information

Cilium version (run cilium version): 1.10.0
OS: Ubuntu 18.04.05 with containerd
Orchestration system version in use (e.g. kubectl version, ...):
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-13T13:23:52Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.9", GitCommit:"6c90dbd9d6bb1ae8a4c0b0778752be06873e7c55", GitTreeState:"clean", BuildDate:"2021-03-22T23:02:49Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
Link to relevant artifacts (policies, deployments scripts, ...): https://github.com/cilium/cilium/blob/v1.10.0/install/kubernetes/cilium/templates/cilium-nodeinit-daemonset.yaml

How to reproduce the issue

create an AKS cluster with Kubernetes 1.19.9 or 1.20.5
Install cilium on it with recommended settings and enable nodeinit with restartPods: true, e.g. for helm:

nodeinit:
  enabled: true
  restartPods: true

scale you cluster manually to add a node and move pods to it or restart your cluster with azure-cli: az aks stop/start ...
check that there are "unmanaged nodes":

CIL_ENDPOINTS=$(k get ciliumendpoints -A | grep -v ENFORCEMENT)
K8S_PODS=$(kubectl get pods --all-namespaces -o custom-columns=NAMESPACE:.metadata.namespace,NAME:.metadata.name,HOSTNETWORK:.spec.hostNetwork,STATUS:.status.phase --no-headers=true | grep '<none>' | grep 'Running')
echo "CILIUM MANAGED ENDPOINTS: $(echo $CIL_ENDPOINTS | wc -l)"
echo "K8S PODS (WITHOUT HOST NETWORKING): $(echo $K8S_PODS | wc -l)"

CIL_ENDPOINT_NAMES=$(echo $CIL_ENDPOINTS | awk '{print $1" "$2}')
K8S_POD_NAMES=$(echo $K8S_PODS | awk '{print $1" "$2}')

diff <(echo $CIL_ENDPOINT_NAMES) <(echo $K8S_POD_NAMES)

This issue has not seen any activity since it was marked stale. Closing. Feel free to re-open a new issue if it is still persisting. Thank you.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_b4j1x6h8zf/clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_b4j1x6h8zf/clone/recipe/meta.yaml:23: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_b4j1x6h8zf/clone/recipe/meta.yaml:49: missing_dev_url: The recipe is missing a dev_url
ERROR: /tmp/abs_b4j1x6h8zf/clone/recipe/meta.yaml:49: missing_license_family: The recipe is missing the about/license_family key.
WARNING: /tmp/abs_b4j1x6h8zf/clone/recipe/meta.yaml:49: missing_description: The recipe is missing a description
ERROR: /tmp/abs_b4j1x6h8zf/clone/recipe/meta.yaml:49: http_url: http://github.com/mdomke/schwifty is not https
Errors were found


reference count settings to bump performance a bit

definitely not an emergency, I just felt like it needed to be done eventually.
Also fixed a couple of docs that I missed.

Oh hm do we need to do this actually? I figured we had enough lifetimes we could just borrow everything?

Later, new Serializer objects are created in SerializeSeq, which means that Settings has to be cloned.
We could change the pretty API so the Settings object is a separate builder that one passes into a settings method or something. Then it could be a reference.

So, the rustdoc command is failing in rust 1.15 because it apparently won't recognize that the code block is toml not rust... is it really necessary that rustdoc is backwards compatible?
https://travis-ci.org/alexcrichton/toml-rs/jobs/258811878

I wonder could we have something like an internal split? Perhaps something like:
pub struct Serializer<'a> {
    // what it is today
}

struct BorrowedSerializer<'a, 'b> {
    settings: &'b Settings,
    // same fields as `Serializer`
}

and then Serializer would just delegate everything to BorrowedSerializer?

that sounds doable, I'll see what I can do

By "internal split" I assume you mean that it is not exposed to the user which would work fine if our public API was just to_string, to_string_pretty, etc.
However, that is NOT our public API.
I guess I could probably do a macro to make this not TOO painful. That sounds pretty boiler-platy to me, just want to make sure that's what you had in mind.

Hm yeah I guess if it requires that much boilerplate it's probably not worth it, I was hoping I guess that it wouldn't require so much!

Ok, let's merge now and if necessary we can work with borrows later


KAFKA-13394: Topic IDs should be removed from PartitionFetchState if they are no longer sent by the controller

With KAFKA-13102, we added topic IDs to the InitialFetchState and the PartitionFetchState in order to send fetch requests using topic IDs when ibp is 3.1.
However, there are some cases where we could initially send topic IDs from the controller and then no longer to do so (controller changes to an IBP < 2.8). If we do not remove from the PartitionFetchState and one broker is still IBP 3.1, it will try to send a version 13 fetch request to brokers that no longer have topic IDs in the metadata cache. This could leave the cluster in a state unable to fetch from these partitions.
This PR removes the topic IDs from the PartitionFetchState if the log contains a topic ID but the request does not. This means that we will always handle a leader and isr request if there is no ID in the request but an ID in the log.
Such a state should be transient because we are either

upgrading the cluster and somehow switched between a new IBP controller and an old one --> and will eventually have all new IBP controllers/brokers.
downgrading the cluster --> will eventually have all old IBP controllers/brokers and will restart the broker/delete the partition metadata file for them.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@jolshan A few tests failed in the last build and they seems related to changes done in the PR. Could you check them please?

I think I saw these earlier and took a look. They are likely not related to the PR and due to flakiness with the test. This test always seems to work locally. This is the replica alter log dirs test which has been a bit flaky in the past. (I think it may be due to the move completing before we can even check the ID. Based on the stack trace it seems that the fetch state being defined is what is failing.) I can try to add more data to the log dir so it takes longer? What do you think?

It is a bit suspicious that the same test failed in all the builds.... I haven't check it myself so I can't really say.

@dajac The test didn't fail on all the builds on the previous build. I will try upping the amount written to the log, but if it's only causing issues on Jenkins I don't know how to test much beyond that.

The flaky tests are unrelated to this PR. Going to merge to trunk and 3.1.

@jolshan Let's try to address that flaky test separately as it is not related to this PR.


Just found this. Is it dead?

I was looking at the Dashing repo and stumbled across Radiate. Is it not being developed anymore?

Hi @dubstrike, since CSS Grid has been implemented in a variety of browsers over the past couple of weeks I've been working on a few updates but have yet to push them up.
The project certainly isn't dead but has definitely been neglected over the past few months.


Try fixing build wheels (#31115)

This needs cherry-picked since the release branch commits are run against that branch

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @Abacn


Enable fedora-33

This branch can only merge after commit
https://github.com/hashicorp/vagrant/commit/b6aebeacae8eb4c35970700d328a85d64e0c4ab1
makes it into a release. Possibly v2.2.11
Signed-off-by: Ganesh Maharaj Mahalingam<EMAIL_ADDRESS>

vagrant releases 2.11 onwards have the fix and this patch is good to merge.


added NEXTAUTH_URL in .env

Thank you for submitting a pull request!
Description
trying to fix the following server error.
2023-01-20T20:25:41.646444114Z [auth][error][UntrustedHost]: Read more at [https://errors.authjs.dev#untrustedhost](https://errors.authjs.dev/#untrustedhost)
2023-01-20T20:25:43.006388122Z UntrustedHost: Host must be trusted. URL was: https://dev.undpgeohub.org/api/auth/session
2023-01-20T20:25:43.006437024Z     at assertConfig (file:///home/site/wwwroot/node_modules/@auth/core/lib/assert.js:22:16)
2023-01-20T20:25:43.006443324Z     at Auth (file:///home/site/wwwroot/node_modules/@auth/core/index.js:65:29)
2023-01-20T20:25:43.006448024Z     at async getSession (file:///home/site/wwwroot/server/chunks/hooks.server-b1dda119.js:15:20)
2023-01-20T20:25:43.006452325Z     at async load (file:///home/site/wwwroot/server/chunks/0-8cf311d0.js:3:14)
2023-01-20T20:25:43.006456425Z     at async load_server_data (file:///home/site/wwwroot/server/chunks/index-f19a6567.js:1086:18)
2023-01-20T20:25:43.006460625Z     at async respond_with_error (file:///home/site/wwwroot/server/chunks/index-f19a6567.js:1970:27)
2023-01-20T20:25:43.006464925Z     at async resolve (file:///home/site/wwwroot/server/chunks/index-f19a6567.js:3219:16)
2023-01-20T20:25:43.006469125Z     at async respond (file:///home/site/wwwroot/server/chunks/index-f19a6567.js:3088:22)
2023-01-20T20:25:43.006473125Z     at async Array.ssr (file:///home/site/wwwroot/handler.js:21781:3)

added NEXTAUTH_URL in .env
https://next-auth.js.org/configuration/options
https://github.com/nextauthjs/next-auth/issues/6113
Type of Pull Request

[ ] Adding a feature
[x] Fixing a bug
[ ] Maintaining documents
[ ] Others ()

Verify the followings

[ ] Code is up-to-date with the develop branch
[ ] No build errors after pnpm build
[ ] No lint errors after pnpm lint
[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check
[ ] Make sure all the existing features working well

Changesets

[ ] If your PR makes a change under packages folder that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Refer to CONTRIBUTING.MD for more information.

I saw this in @auth.js's discussion. added trustHost in hooks.server.ts. Let's see how it works...
https://github.com/nextauthjs/next-auth/discussions/6071


Configurable data location

Running Watcharr as a service on NixOS requires changing the data directory path since the nix store (where the binary is located) is read-only.
Changes made
I'm simply reading the path from an environment variable if set with a fallback to the default ./data if not. I've also updated the places where the directory was hard-coded to use the DataPath var.

Thank you for the kind words and the fast merge even though i can't spell the name of the project properly :)


Add monster by yaosobi

Song Name
niwa
Artist Name
yaosobi
Source
Youtube
Youtube Link
https://youtu.be/z6sN0CCO4Hg?si=FfeSfQ9QO19ZqRjC
Direct File Link
No response
Song ID
233860
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 90899769

accept


Added the Pedantic dependency rules through GitHub Actions

Related Issue

When someone raising the PR, that person should follow all the rules of Pedantic dependency, then that person's all checks will successful while making the PR.

Closes: #77
Describe the changes you've made
I will create the ci.yml file in the .github/workflows/ directory in the project.
Type of change
What sort of change have you made:

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Mention any unusual behaviour of your code (Write NA if not)
Any unusual behaviour of your code
Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[] I have commented my code, particularly whereever it was hard to understand.
[x] My changes generate no new warnings.
[] Any dependent changes have been merged and published in downstream modules.

Additional Info (optional)
Any additional information you want to give

@hiashutoshsingh Please review and merge this PR!


Option for closing files with scipy backend

This is the same as #468, which was accidentally closed. I just copied and pasted my comment below
This addresses issue #463, in which open_mfdataset failed when trying to open a list of files longer than my system's ulimit. I tried to find a solution in which the underlying netcdf file objects are kept closed by default and only reopened "when needed".
I ended up subclassing scipy.io.netcdf_file and overwriting the variable attribute with a property which first checks whether the file is open or closed and opens it if needed. That was the easy part. The hard part was figuring out when to close them. The problem is that a couple of different parts of the code (e.g. each individual variable and also the datastore object itself) keep references to the netcdf_file object. In the end I used the debugger to find out when during initialization the variables were actually being read and added some calls to close() in various different places. It is relatively easy to close the files up at the end of the initialization, but it was much harder to make sure that the whole array of files is never open at the same time. I also had to disable mmap when this option is active.
This solution is messy and, moreover, extremely slow. There is a factor of ~100 performance penalty during initialization for reopening and closing the files all the time (but only a factor of 10 for the actual calculation). I am sure this could be reduced if someone who understands the code better found some judicious points at which to call close() on the netcdf_file.
This option can be accessed with the close_files key word, which I added to api.
Timing for loading and doing a calculation with close_files=True:
count_open_files()
%time mfds =  xray.open_mfdataset(ddir + '/dt_global_allsat_msla_uv_2014101*.nc', engine='scipy', close_files=True)
count_open_files()
%time print float(mfds.variables['u'].mean())
count_open_files()

output:
3 open files
CPU times: user 11.1 s, sys: 17.5 s, total: 28.5 s
Wall time: 27.7 s
2 open files
0.0055650632367
CPU times: user 649 ms, sys: 974 ms, total: 1.62 s
Wall time: 633 ms
2 open files

Timing for loading and doing a calculation with close_files=False (default, should revert to old behavior):
count_open_files()
%time mfds =  xray.open_mfdataset(ddir + '/dt_global_allsat_msla_uv_2014101*.nc', engine='scipy', close_files=False)
count_open_files()
%time print float(mfds.variables['u'].mean())
count_open_files()

3 open files
CPU times: user 264 ms, sys: 85.3 ms, total: 349 ms
Wall time: 291 ms
22 open files
0.0055650632367
CPU times: user 174 ms, sys: 141 ms, total: 315 ms
Wall time: 56 ms
22 open files

This is not a very serious pull request, but I spent all day on it, so I thought I would share. Maybe you can see some obvious way to improve it...

@shoyer and @rabernat - what do we want to do with this?

I considered this more of a proof of concept than a serious PR. It was incredibly slow, but it circumvented the ulimit restriction. Probably not the best solution.

@rabernat, thanks for sharing.  I think this will come in handy for #798.

Really? I figured this was a doomed concept.
@pwolfram it looks like you are doing the hard work that I did not have the time or expertise for. This will pay off big time once the distributed backend is working.

@rabernat, feel free to checkout my comment at the end of https://github.com/pydata/xarray/issues/798.  Please let me know if you see any problems with the outline.  It is quite possible I am missing something and I'd rather know sooner than later.  The basic idea is that we can use a cached dict (LRU) to limit the number of opened files.  This should limit the number of opens/closes that are required.  If no one can poke a conceptual hole in the outline I'll implement it.

Something like this is still worth exploring (the LRU cache), but this isn't quite the right solution. So I'm closing this PR, just to clean up the list of outstanding PRs :).


Lost connections while scaling

Description
flowchart LR
  client --> web --> webrtc-server
  client <--> stunner <--> webrtc-server
  subgraph kubernetes
    web & webrtc-server & stunner
  end

I'm developing a media server. Users communicate by exchanging offers, ice through the webserver and relaying turns through the stunner.
I'm using this well, but I've run into a problem when scaling the pods dynamically. In a small development environment, this is fine, but when scaling up and down a large number of replicas, the stunner loses connectivity.
Steps to Reproduce
Rolling updates to a small number of webrtc servers or scaling to a small number of webrtc servers will not cause any issues. Scaling to dozens of webrtc servers or rolling updates to a large number of webrtc servers is easily reproducible.
Expected behavior: Connectivity should be maintained during scale. webrtc server will gracefully terminate.
Actual behavior: The stunner loses the connection.
Versions
This is reproduced in both 1.18.0 and 1.19.0.
Info
The gateway generates logs like the one below while losing connectivity.
06:03:06.058863 reconcile.go:180: stunner INFO: new dataplane status: somenamespace/gateway-udp:{logLevel="all:INFO",health-check="http://:8086"}/static-auth:{realm="stunner.l7mp.io",username="<SECRET>",password="<SECRET>"}/["somenamespace/gateway-udp/turn-udp-listener":{turn://<IP_ADDRESS>:28751,public=<IP_ADDRESS>:28751,cert/key=-/-,routes=[somenamespace/somewebrtcserver]}]/["somenamespace/somewebrtcserver":{type="STATIC",protocol="UDP",endpoints=[<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>,<IP_ADDRESS>]}]/allocs:3/status=READY
06:03:06.061402 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited (suppressed 2 log events)
06:03:06.138467 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited
06:03:06.201200 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited
06:03:07.139439 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited (suppressed 12 log events)
06:03:08.138308 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited (suppressed 13 log events)
06:03:09.122805 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited (suppressed 13 log events)
06:03:10.062079 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited (suppressed 12 log events)
06:03:11.138560 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited (suppressed 14 log events)
06:03:12.123254 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited (suppressed 13 log events)
06:03:13.138399 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited (suppressed 13 log events)
06:03:14.138346 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited (suppressed 13 log events)
06:03:15.061727 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited (suppressed 12 log events)
06:03:16.138819 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited (suppressed 14 log events)
06:03:17.062617 server.go:202: turn ERROR: Failed to handle datagram: unable to handle ChannelData from <IP_ADDRESS>:1314: failed writing to socket: peer port administratively prohibited (suppressed 12 log events)

Gateway API status
Operator logs
Basically, I followed this tutoral and there is nothing unusual about the operator and api status.

This is not a STUNner issue per se. We've seen this problem several times and the reason is the way your load-balancer ingests UDP traffic into the cluster. Unfortunately some K8s load-balancers do not create conntrack state for UDP connections (which would make sure connections are pinned to a specific pod) but rather use a dumb stateless hash function to assign a specific STUNner pod for each UDP packet separatly. When you add/remove pods, hash-ranges change and connections get rerouted. Some LBs use consistent hashing, but that is still amenable to rare connections losses during scaling.
I'm afraid the only solution is to use TCP instead of UDP (this is suboptimal but TCP connections are always lod-balanced using per-connection conntrack state) or migrate to another k8s provider and/or LB that implements a smarter UDP ingress. May I ask how you're hosting your testbed?

I'm using AKS. Is there any documentation that summarizes the load balancer compatibility of hosted Kubernetes services?

Thanks. We're currently compiling a compatibility matrix, hope to release it soon. The last time we checked the GKE UDP LB was working fine.
Closing this for now, feel free to reopen if anything comes up.

@rg0now But I'm a little curious, I didn't scale the gateway (1 replicas), just the server that webrtc communicates with. Is this also affected by the loadbalancer, even though there is only 1 pod that the loadbalancer is connected to?

Oh, I"m terribly sorry I completely misunderstood, thanks for clarifying. If it is scale-down that breaks then maybe you're hit by this issue. This problem has been fixed here but you must run a fairly recent dev release to have that fix. If this affects scale-up, can you specify the steps to reproduce this?

I changed the image tags for stunnerd and stunner operator to dev, but the error seems to happen the same.
I don't see anything particularly strange in the gateway logs when scaling up. (This may not be an issue with the stunner).

I tried my best to reproduce this, to no avail.
The offending error log indicates that your client is trying to send to a backend IP that is no longer part of the backend Service (the one in the UDPRoute backendRefs). This may happen if you scale the corresponding backend pod down (don't do that) but forget to tell the client to do an ICE restart (try to avoid this). Scaling webrtc servers is difficult, see some background here.
I am going to close this in preparation for the v1 release. Feel free to reopen if you find a simple way to reproduce this. We have had some issues with STUNner graceful shutdown and it would be critical we get this right...


Analyzer Conversion Docs

Description

Adds documents detailing how to use CSharp analyzers to convert WinUI2 projects to WinUI3

/azp run

/azp run

@MadEste could you please merge the master branch into your branch? A change went into the repo this morning that will make it so we don't need to run the build and tests on your change since it only has MD and png file changes. We can save a bit of azure resources that way.

@StephenLPeters  Should be up to date with master now.

/azp run

Is this tool already available? If not since this is getting checked in now should we make it clear that this is not available until... some release

@StephenLPeters  The NuGet Package is only available on the internal feed. I've added a note to the docs.

/azp run

/azp run

@MikeHillberg and @MadEste its been a while since this has been updated? is it ready to go in? can we get sign off?

@stevenbrix too

Documentation Changed as Analyzers are moving to the try-convert repo. Closing this request.


⚠ Bofrost.at has degraded performance

In 1373109, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2471 ms

Resolved: Bofrost.at performance has improved in 67fac24.