Feature request: Enhanced Top Level Power/Energy Flow Dashboard

Monitoring of all EMS Power/Energy Flows in one view is basic and mandatory in future:

Merging is possible but only after heavy adaptation of sensor naming conventions ...
I strongly disagree on your actual sensor namings.
My approach: To be much close to the nameing conventions provided by @wlcrs huawei_solar and all other integrations I needs to synchronize:

huawei_solar
epexspot
tibber
sun
sun2
solcast
emhass
myVaillant
dwd_DeutscherWetterdienst
Shelly
...

It works as visible in above screenshoots!
For sure tons of bugs and a lot of improvement - but I need clear readable and short sensor names for proper debugging on all integration dependencies ...

I've made a quick and dirty review of your code.
My view:

Very complex
Hardly to maintain
Not closely enough to @wlcrs naming convention

My conclusion:

I will step out

Sorry for the noise ...

Presentation in Lovelace is very individual, but it would be great to biuld a base for people to start with. It has not been my main priority. It’s on the roadmap.


feature request - optional add version into file name when download workflow

希望可以在保存的文件名后面加上版本号呦

also always show the current version dropdown: "v1" in the screenshot

咋close了 还没做呢 in planning

哈哈 我以为beta的要上线了

还在测呢。你试了吗 有遇到什么问题吗～

From: Cyber Dick Lang @.>
Sent: Wednesday, March 6, 2024 7:53:35 PM
To: 11cafe/comfyui-workspace-manager @.>
Cc: Weixuan Fu @.>; State change @.>
Subject: Re: [11cafe/comfyui-workspace-manager] feature request - optional add version into file name when download workflow (Issue #198)
哈哈 我以为beta的要上线了
―
Reply to this email directly, view it on GitHubhttps://github.com/11cafe/comfyui-workspace-manager/issues/198#issuecomment-1980704287, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEMEEOLVDBZU227Q4VOZKQ3YW37T7AVCNFSM6AAAAABDO6MSYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBQG4YDIMRYG4.
You are receiving this because you modified the open/close state.Message ID: @.***>


Option to install specific version of docker

Is there option to install specific version of docker e.g. using env variable?

Not at this time. What are you trying to achieve that necessitates
environment variables?
On Monday, October 26, 2015, Martin Micunda<EMAIL_ADDRESS>wrote:

Is there option to install specific version of docker e.g. using env
variable?
—
Reply to this email directly or view it on GitHub
https://github.com/angstwad/docker.ubuntu/issues/73.

--
-Paul
Sent from my iPhone

I am using another docker-compose role and there is option to specify version of docker-compose and as docker-compose kind of depends on docker I was thinking it would be nice to specify exactly version of docker.

You can use the parameter docker_pkg_name and set it to docker-machine=1.8.3-0~trusty, or some other valid version of docker-machine or docker.io as required.
To see the available versions, use apt-cache showpkg docker-engine or the right package as required.


handle IDs that are numbers

If the ID value is a number, the casting to a String fails.

From https://jsonapi.org/format/#document-resource-object-identification:

The values of the id and type members MUST be strings.

Have you also considered the case where id might be nil as stated in the exception here?
https://jsonapi.org/format/#document-resource-objects

Any update on this @Truba ? We need this support as well.


Strange results from spike_aggregation alert

I want to alert when the average build time (fields.duration) over the past 24 hours, is 20% or more larger than the average build time from the day before (48 hours ago - 24 hours ago). To do this I'm using the spike_aggregation rule. I tested it with elastalert-test-rule and it seems to work, but now that it's running in production I'm getting strange results. I got an email alert yesterday that told me the following:

Mean Build Time Spike - Day over day
An abnormal avg of fields.duration (716482623.0) occurred around 2020-01-11 14:02 PST.
Preceding that time, there was a avg of fields.duration of (520382860.86) within 1 day, 0:00:00
formatted_time: 2020-01-11T22:02:18.014445Z
num_hits: 19
num_matches: 2
reference_count: 520382860.8595236
spike_count: 716482622.999998
tags.name.keyword: redacted

How can I validate this exactly? I went through Kibana and the actual averages during these timeframes are around 2 million, where these numbers are saying spike of 700 millioon, and the reference window average was 520 million. These numbers are WAY off and I have no idea where they're coming from.
This is my config.yaml:
rules_folder: rules
run_every:
  minutes: 5
buffer_time:
  days: 1
es_host: hostname
es_port: 9200
writeback_index: elastalert_status
writeback_alias: elastalert_alerts
alert_time_limit:
  days: 2

And my rule yaml:

es_host: hostname
es_port: 9200
name: Mean Build Time Spike - Day over day
type: spike_aggregation

index: telegraf-jenkins*
timestamp_field: formatted_time
timeframe:
    days: 1
buffer_time:
    days: 1

metric_agg_key: fields.duration
metric_agg_type: avg

query_key: tags.name.keyword

### Minimum 1 minute build time to rule out build log pipeline and fast running jobs
threshold_ref: 60000

min_doc_count: 1

spike_height: 1.20

spike_type: "up"

filter:
   - query_string:
       query: "_exists_:fields.duration"

Is there some problem with my configuration? Any help would be greatly appreciated!

Yelp/elastalert is no longer maintained. Please use jertel/elastalert2.
https://github.com/jertel/elastalert2


Aktualisierung

This also includes some deletions that have been missed earlier.

As I have stated in my previous PR, I do not want to implement an automatic approach for this, at least not within GitHub Actions, because with the planned proper generation of law-update-commits, this code would be useless very soon. These manual updates are only something that I can offer for the time being, until we implement the automation properly. If you do not want this, feel free to close this PR.
During these updates, I keep getting problems which require manual fixing, so an automated approach is not possible, even if I wanted to.
To straighten most of these problems, which occur in the gesetze-tools repository, I am planning on a writup to suggest a different strategy of the tools, but this writup requires some time. Until then there are some minor updates/changes that I can roll-out , first of which is this PR for example https://github.com/bundestag/gesetze-tools/pull/49 .


Incorrectly inferred object property as string literal value

TypeScript Version:  3.9.2

Search Terms:
incorrectly inferred string index type
inferred object property in function return type
Expected behavior:
The key values in each Variation should be inferred as string not the literal string value
Actual behavior:
The key values in each Variation are inferred as the literal string value of the first object

Related Issues:
Possibly related: https://github.com/microsoft/TypeScript/issues/38759,
Code

type Variation = {
    [testDescription: string]: () => void;
}

export type VariationProvider = {
  variations: Variation[];
};

export type VariationProviderFactory = (extras: object) => VariationProvider;

export function createVariationProvider(factory: VariationProviderFactory) {
  return factory;
}

createVariationProvider(() => {
  return {
    variations: [
      {
        foo: () => {}
      },
      {
        broken: () => {}
      },
    ]
  }
})

Output
export function createVariationProvider(factory) {
    return factory;
}
createVariationProvider(() => {
    return {
        variations: [
            {
                foo: () => { }
            },
            {
                broken: () => { }
            },
        ]
    };
});

Compiler Options
{
  "compilerOptions": {
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "strictPropertyInitialization": true,
    "strictBindCallApply": true,
    "noImplicitThis": true,
    "noImplicitReturns": true,
    "useDefineForClassFields": false,
    "alwaysStrict": true,
    "allowUnreachableCode": false,
    "allowUnusedLabels": false,
    "downlevelIteration": false,
    "noEmitHelpers": false,
    "noLib": false,
    "noStrictGenericChecks": false,
    "noUnusedLocals": false,
    "noUnusedParameters": false,
    "esModuleInterop": true,
    "preserveConstEnums": false,
    "removeComments": false,
    "skipLibCheck": false,
    "checkJs": false,
    "allowJs": false,
    "declaration": true,
    "experimentalDecorators": false,
    "emitDecoratorMetadata": false,
    "target": "ES2017",
    "module": "ESNext"
  }
}

Playground Link: Provided

@ahejlsberg the optional object literal property detection logic isn't quite doing the right thing here

A more distilled version
type VariationProviderFactory = () => Record<string, () => void>[]

const variationProviderFactory: VariationProviderFactory = () => [
  {
    foo: () => { }
  },
  {
    broken: () => { }
  },
]

const vars: Record<string, () => void>[] = [
  {
    foo: () => { }
  },
  {
    broken: () => { }
  }
];

const variationProviderFactory2: VariationProviderFactory = () => vars

The object literal
[
    { foo: () => {} },
    { broken: () => {} }
]

has the widened type
[
    { foo: () => void, broken?: undefined },
    { broken: () => void, foo?: undefined }
]

The optional properties are a result of object literal normalization (#19513), which is part of type widening. So, we have the unfortunate situation that the unwidened form of the object literal is assignable to Record<string, () => void>, whereas the widened form of the object literal isn't. The examples then simply reveal when widening is or isn't performed. And, basically, we widen function return expression types unless the containing function has an explicit type annotation--and the examples don't.
Anyway, I think the best fix is to change the Record<string, () => void> type to Record<string, (() => void) | undefined> which really is more correct. You could even argue that we're finding a potential bug, except we're not particularly consistent about it.


New steps

Description

Add new step
Add a new xml that accommodates the inverse kinematics order used by seq ikpy
Change nmf physics hyper parameter (actuator kp, tarsus stiffness and damping) to match the fly behaviour
Change unittest to accommodate high kp
Note: All notebooks are compatible with the new steps except the hybrid controller

Types of changes

[ ] Bugfix
[x] New feature
[ ] Refactor / Code style update (no logical changes)
[ ] Build / CI changes
[ ] Documentation Update
[ ] Other (explain)

Does this address any currently open issues?
[]

Also, the collision parameter is back under compiler options in the XML. Why didn't this break MuJoCo 3.x.x? Are the CI tests still working? Did MuJoCo allow this again for backward compatibility in 3.1.2? I will check this.

Also, the collision parameter is back under compiler options in the XML. Why didn't this break MuJoCo 3.x.x? Are the CI tests still working? Did MuJoCo allow this again for backward compatibility in 3.1.2? I will check this.

Hi @sibocw, this branch is only 2 commits behind main, so it includes MuJoCo 3.x.x compatibility fix.

Also, the collision parameter is back under compiler options in the XML. Why didn't this break MuJoCo 3.x.x? Are the CI tests still working? Did MuJoCo allow this again for backward compatibility in 3.1.2? I will check this.

Hi @sibocw, this branch is only 2 commits behind main, so it includes MuJoCo 3.x.x compatibility fix.

Hi @stepanove, thanks for the note! What I meant was that the new XML file that @stimpfli added has collision="predefined" again in the compiler options. This should have been removed for mujoco 3.
However, the automated tests passed despite mujoco-3.1.2 being installed. This confused me.
But I've just realized that the tests were, in fact, still using the old XML file. I will fix this.

Let's not merge into main until the tutorials are also updated. This will prevent the docs website from being updated prematurely when the new release is not out yet.
I updated the develop branch to sync it with main. Let's aim to merge everything into develop first, then update the docs website, and then merge develop into main.
@tkclam if you want to change anything before the COBAR course starts again, please also merge it into develop instead of main.

All the parts that I understand make sense.

Is there anything unclear?

What happened to the vision part (except form changing the ball speed?)

The steering drive is updated every tau seconds where tau != dt of the physics simulation (or the interval at which the visual input is updated). Previously, when the steering drive needs to be updated, it uses the latest visual input. Now, it uses the median visual input during the tau=0.02sec period.
PS. I accidentally named mean_visual_input when it's in fact the median. I will change it.


Statistics finder - Filters not persistent across tabs

Steps to recreate

Go to https://www.gov.uk/government/statistics
Select filter for Department (or anything)
Select "Upcoming"

Expected result
Filters persist across tabs
Actual result
All filters have been removed

statistics finder has since been moved to finder-frontend and the interface no longer has tabs, so closing this


Please include a crud generator or a tutorial on doing crud with vue.

Is your feature request related to a problem? Please describe.
In order to rapid development, A crud generator (front end) would be great.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
It can be documentation about generating basic crud.
Additional context
I'm not sure wether this is within the framework scope, but I just want to get flask behind.
This, and user/permission management are maybe the only  2 things lacking. IMHO.

I know TypeSystem can do form rendering
https://www.encode.io/typesystem/forms/
I wonder if this can be achieved with pydantic

Thanks, yes, I've been thinking about this (I think we discussed it on Linkedin). I plan on building a Vue.js CRUD admin for OpenAPI.
It would not be tightly coupled to FastAPI, as it would be compatible with OpenAPI in general, but would be made to be easily added/pluggable as the current docs pages.
I have to first build the pieces, Vue components that render correctly data to be viewed in a "details" section (for one item), in list (for multiple items), and edition mode. And then, automatic sections based on tags. And then, I have to see how to solve handling the relationships between different models/schemas. I also have to see how to integrate it with security. I already have OAuth2 with password scheme (that's already in the project generators), but maybe that can be generalizable to other schemes.

@tiangolo right now FastAPI is still not as productive as Django Rest Framework because of the lack of user-registration/management workflow. The generator is nice but it's too tightly coupled. Would be nice to have a proper CRUD generator/admin story. You mentioned not wanting to include a ORM but without one a lot of time is wasted on shipping CRUD code, fiddling with migrations etc. If nothing, at least include Django's ORM to make life easier.
ref: https://www.reddit.com/r/Python/comments/b0zxa9/introducing_fastapi/eikicdj/

Hey @tiangolo I'd be glad to start working on this. I might make a proof of concept in the following weeks, is there any specific functionality you'd be looking for?
The way I see it rendering the following input types would be enough for a POC:

string
number
date
choices(enum)
foreign key (with a link to the resource)

What do you think? would that help? Also, I am planning to use vuetify for this if that is ok.

I am also interested at building a admin. I'd like to use fastapi, mongodb, vue and vuetify. And I want to have a RBAC authentication too. But I'am not an experienced programmer.
I need some advice / best practice about how to implement those. Especially:

automatic sections based on tags
@tiangolo Can you share your idea about how to implement it? Should I just read and parse http://<IP_ADDRESS>:8000/openapi.json by hand or is there any great npm package to do it?

How to implement RBAC for FastApi?
What represent the permission?
For example,
@app.put("/items/{item_id}", response_model=Item)
async def update_item(item_id: str, item: Item):
    update_item_encoded = jsonable_encoder(item)
    items[item_id] = update_item_encoded
    return update_item_encoded

What will be the permission name? How to identify it with code?
Should I use FastAPI's dependency system to verify role and permission?

I use mongoengine to create model and create event handlers to connect and disconnect multiple connection from the mongodb(@app.on_event("startup"), @app.on_event("shutdown")) (refer the document)
I wish there a tutorial about how to use mongoengine with FastAPI.

@jlugao Can you share your work of crud with vue?

Recommend my admin dashboard fastapi-admin,based on fastapi and tortoise-orm and rest-admin,hope a star~😁

I don't like the idea on an ORM being incorporated into a project like this, what makes fastapi great IMO is it's focus on doing what it does extremely well.  Async python routing with strict typing, and openapi generation.  The docs detail how to incorporate an ORM.  It would totally be cool to see some kind of vue frontend rendered from the OpenAPI with knowledge of the Pydantic models they come from for sure.

@tiangolo suggestion to close this issue. This would be pretty awesome, but probably a whole new project, and eventually not part of the FastAPI core code.

I'd suggest that https://github.com/awtkns/fastapi-crudrouter meets this need so would agree with closing the issue.

Hello everyone! As several have pointed out, this would actually be an independent project. If it's just based on OpenAPI, it would be a new frontend. If it's also dependent on the database, it would also depend on a specific type of database (e.g. SQL or NoSQL) and ORM, so again, another project.
The idea is of course still valid, and some of the projects mentioned here can do a great job. But to keep issues clean, and because this would really belong in an external project(s), I'm gonna close this one now. Thanks for all the interactions and discussion!

Sorry for the long delay! 🙈  I wanted to personally address each issue and they piled up through time, but now I'm checking each one in order.


A prototype of first-class functions

Tackles the issue #3405 but closes once support for njit decorated functions is implemented.
The middle-level description of the first-class function model is as follows:

A function, as an instance of the first-class type, is represented by its address, signature, and a pointer to a parent python object. The address enables accessing the compiled implementations of the function as well as to enable using function instances as items within njitted functions. The signature enables constructing the LLVM IR level call to the compiled functions. The parent object is used as a reference to the high-level implementation (python function, for instance) that enables compiling the function for a different set of argument types in just-in-time manner as well as it is used as return value of the first-class function.
Wrapper address protocol: When a first-class function is passed into a njitted function, it needs to be "unboxed". The unboxing requires a method for acquiring the address of the compiled function. For instance, if the input argument is a numba.cfunc(<signature>) decorated function (of type CFunc), then the address is readily available via its _wrapper_address attribute. This PR introduces so-called wrapper address protocol (see https://github.com/numba/numba/pull/4967/files#diff-275bdd7060d042bc811293de00e7878dR115-R143 for the definition and support) that enables interpreting arbitrary python objects as first-class functions when passed to a njitted function as an argument. For instance, to retrieve a function address from a python object such as CFunc, the function numba.function._get_wrapper_address(obj, signature) is called from the unboxing procedure. The implementation of the _get_wrapper_address for the CFunc objects would be as simple as (assuming that CFunc instance is compiled against a correct signature):

def _get_wrapper_address(obj, signature):
    return obj._wrapper_address

Extensibility: The wrapper address protocol model allows for extending first-class function model to arbitrary objects (not just for cfunc decorated functions). For instance, one can implement caching of compiled functions as an independent method to numba jit caching model, or one can call arbitrary library functions from njitted functions (as long as one is able to determine the pointer values of the library functions, one can use ctypes for that). See https://github.com/numba/numba/pull/4967/files#diff-75b50def42de3256e721ce2c6e79c47dR282-R322 for an example of how to call a libc function time from a njitted function.

Current status:

[next PR] Pass functions as arguments to njitted functions:

[x] cfunc decorated functions
[x] njit decorated functions
[next PR] pure Python functions
[next PR] ctypes functions

[next PR] Use functions as items within njitted functions:
Both constant (available via namespace lookup) and passed in functions (available as arguments of njitted functions)

[x] cfunc decorated functions
[x] njit decorated functions
[next PR] pure Python functions
[next PR] ctypes functions

[next PR] Use functions as return values from njitted functions
Both constant and passed in functions

[x] cfunc decorated functions
[x] njit decorated functions
[next PR] pure Python functions
[next PR] ctypes functions

[next PR] Overload function calls within njitted functions
Both constant and passed in functions

[next PR] cfunc decorated functions
[x] njit decorated functions

[next PR] Constuct function signatures

[x] int64 arguments
[x] other argument types
[next PR] tests, partially blocked by Signature vs FunctionType issue

[x] Unit-tests
[next PR] Documentaton

Example:
from numba import cfunc, njit, int64

@cfunc(int64(int64))
def a(i):
    return i + 1

@cfunc(int64(int64))
def b(i):
    return i + 2

@njit
def foo(f, g):
    i = f(2)
    seq = (f, g)
    for fun in seq:
        i += fun(i)
    return i

a_ = a._pyfunc
b_ = b._pyfunc
assert foo(a, b) == a_(2) + a_(a_(2)) + b_(a_(2) + a_(a_(2)))

/AzurePipelines run

The current PR implements first-class function type support from cfunc decorated functions.
Some features work also for njit decorated functions but the full support will be implemented in a separate PR.
@sklam , please review.
The

@sklam @stuartarchibald I have addressed all Siu's notes:

replace test_all method with explicit test methods.
eliminate numbatype function as not needed here.
signatures are expected to be given as Signature instances
The PR is ready for review.

Thanks @pearu I've marked it as such. I'll hopefully be able to look at it in the next day or so.

Current (local) status of njit-decorated first-class function support:
    @nb.njit
    def a(x):
        return x + 1

    @nb.njit
    def b(x):
        if x < 0:
            raise ValueError('expected non-negative input')
        return x + 2

    @nb.njit
    def foo(f, x):
        return f(x)

    assert foo(a, 0) == 1  # compiles foo and a
    assert foo(b, 0) == 2  # compiles b
    assert foo(a, 1) == 2  # no compilations
    assert foo(b, 1) == 3  # no compilations

    r = foo(b, -5)  # prints exception to stderr, r value is arbitrary (0)

    ##################
    @nb.njit
    def c(x):
        return x + 3

    @nb.njit
    def bar(f, x):
        return x

    print(bar(a, 123))  # compiles bar, reuses `a` compile result
    print(bar(c, 567))  # compiles c
    # calling bar(c, 567) before (bar(a, 123) results failure because there is no type info re `c`. Ideally, `c` should be ignored..

@sklam @stuartarchibald, please review:

rebased to master,
removed signature from __wrapper_address__ method.

Note that PR #5287 adds the jit-decorated functions support on the top of this PR.
So, if preferred, this PR can be shelved and we can proceed working with PR #5287 only.

I have some suggestions at https://github.com/numba/numba/pull/5307.  https://github.com/numba/numba/pull/5307/commits/8156a197554e8612534467b27e03110db8520565 would simplify the logic for .get_call_type()'s casting rule.

I have some suggestions at #5307. 8156a19 would simplify the logic for .get_call_type()'s casting rule.

Thanks, applied the suggestion to #5287 .

Note to self. Check docs. @sklam approves code.

If https://github.com/numba/numba/pull/5287 is replacing, can this be closed now?

yes, this can be closed.


Release

Should this follow sway's release or just make its own release cycles.
Release is mostly for the packaging and testing.

Hi,
whether you're following sways release or make your own release cycles - it would be great if you would start with a release greater than 1.8.1. We packaged grimshot in Debian with that version number - and as far I can see we are not the only ones

My idea is using Calendar Versioning. Or just wait for the sway 1.9 release, but I think it would be better to make its own cycles.
Or copy this https://github.com/hyprwm/contrib/releases, but it's lower than 1.8.1.
Would there be a problem with Debian packaging if I use Calver?

Would there be a problem with Debian packaging if I use Calver?

no, not at all, there is a lot of software that uses Calver packaged in Debian. If the version starts with 24 or 2024 that will be fine, because its greater than 1

Hi, is there a new release planned as sway 1.10 is released?

@fossdd Yeah, I was busy for a while. I will try release it in this week.


Why VS 2016? -.-

Pal...I know you will close this issue, but for God's sake. I'm spending HOURS trying to make this thing compile with VS2010, currently stuck with an internal compiler error related to your "negatable_left_shift" template magic, C interface with C++11 internal implementation...seriously...fuck you!

I hear you.  I'm sorry that code is causing you trouble.
In fact that negatable_left_shift template magic is already a workaround to various frustrating compiler differences. We support Darwin, Linux x86-64, Windows, MinGW-for-windows (32 and 64 bits), and 7 different Android ABIs.
Unfortunately we don't support VS2010.
I'll leave this issue open in case someone can propose a good fix that still meets our portability constraints.
As for the last point, C interface with C++ internals, I refer you to the following blog post and follow-on  Cppcon talk:
http://blog.sduto.it/2014/05/a-c-error-handling-style-that-plays.html
http://www.slideshare.net/StefanusDuToit/cpp-con-2014-hourglass-interfaces-for-c-apis and also
Thank you for your interest in this project!

I ended up calling the assembler executable with ShellExecuteEx(). Duh...
Anyway here is a possible solution for this negatable left shift (compiles, but not tested tho):
  template <int_type N>
  struct negatable_left_shift {
    static uint_type val(uint_type val) {
      if (N < 0) {
        uint_type newN = (uint_type)(-N);
        return static_cast<uint_type>(val >> newN);
      }

      uint_type newN = (uint_type)N;
      return static_cast<uint_type>(val << newN);
    }
  };

I'm going to close this as wont fix. It's been 2 years since it was opened, newer compilers are out, 2010 is very old at this point.


⚠ Bofrost.be has degraded performance

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

HTTP code: 200
Response time: 1340 ms

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


Retain dots from the module name

before

after

honestly im not entirely sure of the difference between .name and .getFriendlyFullName(). it appears as though .getFriendlyFullName() is a wrapper around .name with some magic? do you want the magic frm getFriendlyFullName() too or no? idk which is better 🤷♂
code from typedoc in my node_modules for the getFriendlyFullName() func
/**
     * Return the full name of this reflection, with signature names dropped if possible without
     * introducing ambiguity in the name.
     */
    getFriendlyFullName() {
        if (this.parent && !this.parent.isProject()) {
            if (this.kindOf(kind_1.ReflectionKind.ConstructorSignature |
                kind_1.ReflectionKind.CallSignature |
                kind_1.ReflectionKind.GetSignature |
                kind_1.ReflectionKind.SetSignature)) {
                return this.parent.getFriendlyFullName();
            }
            return this.parent.getFriendlyFullName() + "." + this.name;
        }
        else {
            return this.name;
        }
    }

use case that prompted this: investigating using TypeDoc for https://github.com/zloirock/core-js with module names like array.at or object.assign or similar. those got mangled due to the .split(".") stuff
https://github.com/felipecrs/typedoc-plugin-rename-defaults/blob/b34891030e6ba1e3e545672469d374299e35a717/index.js#L43

before

after

 Submitted with StackBlitz Codeflow.

Ok, in fact this brings a regression on test5 (https://github.com/felipecrs/typedoc-plugin-rename-defaults/pull/4).
Do you have any ideas on that?
Previous

After

Maybe we should retain the dots if a explicit jsdoc is used like test9, but otherwise discard the dots when none is set (which probably comes from the file name).

BTW, I like the usage of getFriendlyFullName, but we have to consider support for older versions of TypeDoc.
I don't mind bumping the minimum needed TypeDoc version though.

given discussion in #14 and #15 i dont think this is as good of an idea as when i opened this lol. especially this:

When using the module name we stumble upon https://github.com/felipecrs/typedoc-plugin-rename-defaults/pull/4 again. I really don't know what is the best way to handle this, but it is indeed a valid use case (when using Angular and Nest conventions).


Top-of-the-window menu spacing problem when the browser is just the right width

I just installed netbox 1.5.2 and my browser window was just wide enough to make the top menu bar shift to double-spaced, but not so narrow that it caused it to be replaced by the menu. The ensuing partially-missing components confused me so I thought it was that Chrome was broken, because the display was fine on Firefox (although I did get bit by bug #507). It turns out, my Firefox was simply wider.
Here's a screenshot:

If I pull the window wider, the display looks fine. If I pull the window narrower, it jumps to the menu. If the window is juuuust right... 2 lines, and partially covered up screen components. See this shot for another view:

This problem came about because my screen is in portrait orientation, so it's 1200 pixels wide. I imagine that a person with a 1280x1024 screen with a browser window that's just slightly narrower than full width would see this issue.

same problem going on #507 and #511

This should be fixed in v1.6.0. The menu now collapses entirely in the screen is less than 1200px wide.


Certain languages are not being properly detected by flutter_localizations (eg. Simplified Chinese)

Steps to reproduce

Create a basic flutter app with localizations including English and Simplified Chinese
Change the device language from English to Chinese

Expected results
The app's locale is set to zh and all the localized text uses the chinese translations. The print statement in the localeListResolutionCallback should be ordered [zh, en, ...]
Actual results
The app's locale is set to english and uses the wrong translations. The print statement in the localeListResolutionCallback is ordered [en, zh, ...]
Code sample
Code sample
class Main extends StatelessWidget {
  final _logRouteObserver = LogRouteObserver();

  @override
  Widget build(BuildContext context) {
    return MultiProvider(
      providers: ProviderModule.providers,
      child: OverlaySupport(
        child: MaterialApp(
          title: '',
          theme: MaterialThemeModule.build(),
          debugShowCheckedModeBanner: false,
          navigatorKey: NavigatorUtil.key,
          navigatorObservers: <NavigatorObserver>[
            FirebaseAnalyticsObserver(analytics: FirebaseAnalytics.instance),
            _logRouteObserver,
          ],
          initialRoute: RouteNames.Boot,
          onGenerateRoute: RouteModule.onGenerateRoute,
          routes: RouteModule.routes,
          localizationsDelegates: AppLocalizations.localizationsDelegates,
          supportedLocales: AppLocalizations.supportedLocales,
          localeListResolutionCallback: (locales, _) {
            print(locales);
            return null;
          },
          scaffoldMessengerKey: SnackbarUtil.key,
        ),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration

Logs
Logs
<Redacted>

Flutter Doctor output
Doctor output
[√] Flutter (Channel stable, 3.24.3, on Microsoft Windows [Version 10.0.22621.4317], locale en-US)
    • Flutter version 3.24.3 on channel stable at C:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2663184aa7 (2 months ago), 2024-09-11 16:27:48 -0500
    • Engine revision 36335019a8
    • Dart version 3.5.3
    • DevTools version 2.37.3

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\David Snyder\AppData\Local\Android\sdk
    • Platform android-34, build-tools 31.0.0
    • Java binary at: C:\Program Files\Android\Android Studio5\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-b2043.56-10550314)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.7.0)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.7.34003.232
    • Windows 10 SDK version 10.0.22621.0

[√] Android Studio (version 2023.1)
    • Android Studio at C:\Program Files\Android\Android Studio5
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-b2043.56-10550314)

[√] VS Code (version 1.92.2)
    • VS Code at C:\Users\David Snyder\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.100.0

[√] Connected device (4 available)
    • SM S918B (mobile) • R5CX10B92GL • android-arm64  • Android 14 (API 34)
    • Windows (desktop) • windows     • windows-x64    • Microsoft Windows [Version 10.0.22621.4317]
    • Chrome (web)      • chrome      • web-javascript • Google Chrome 129.0.6668.101
    • Edge (web)        • edge        • web-javascript • Microsoft Edge 128.0.2739.42

[√] Network resources
    • All expected network resources are available.

• No issues found!

This sounds similar to https://github.com/flutter/flutter/issues/64264. Do you see localeListResolutionCallback fire multiple times when language changes?
If it's not similar, can you provide a completed and minimal reproducible code sample that doesn’t include 3rd party plugins or complex production code?
Please also check https://github.com/flutter/flutter/issues/100857#issuecomment-1559653376 if it helps.

This sounds similar to #64264. Do you see localeListResolutionCallback fire multiple times when language changes?
If it's not similar, can you provide a completed and minimal reproducible code sample that doesn’t include 3rd party plugins or complex production code?
Please also check #100857 (comment) if it helps.

Thanks for the response. I checked and localeListResolutionCallback doesn't fire multiple times, I also tried the solution from the linked comment and that didn't fix it. I'm working a better minimal reproduction.

Minimal Reproducible
main.dart
import 'dart:async';

import 'package:customer_mobile/utils/navigator.util.dart';
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';
import 'package:flutter_gen/gen_l10n/app_localizations.dart';
import 'routes.dart';

Future main() async {
  // https://stackoverflow.com/questions/57689492/flutter-unhandled-exception-servicesbinding-defaultbinarymessenger-was-accesse
  WidgetsFlutterBinding.ensureInitialized();
  runApp(Main());
}

class Main extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: '',
      initialRoute: RouteNames.Boot,
      routes: RouteModule.routes,
      navigatorKey: NavigatorUtil.key,
      localizationsDelegates: AppLocalizations.localizationsDelegates,
      supportedLocales: AppLocalizations.supportedLocales,
      localeListResolutionCallback: (locales, _) {
        print('locales reset');
        print(locales);
        return null;
      },
    );
  }
}

navigator_util.dart
import 'package:flutter/widgets.dart';

class NavigatorUtil {
  static final key = GlobalKey<NavigatorState>();
  static NavigatorState get state {
    return key.currentState!;
  }

  static BuildContext get context {
    return key.currentContext!;
  }
}

boot.dart
import 'package:customer_mobile/utils/localization.util.dart';
import 'package:flutter/material.dart';

class BootScreen extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Builder(
        builder: (BuildContext context) {
          return Align(
            child: Text(L10n.instance.claimingBluetoothUnavailableFull),
          );
        },
      ),
    );
  }
}

en_US.arb
{
  "@@locale": "en",
  "claimingBluetoothUnavailableFull": "Either turn on Bluetooth or manually claim a device."
}

zh_Hans.arb
{
  "@@locale": "zh",
  "claimingBluetoothUnavailableFull": "打开蓝牙或手动搜索设备。"
}

routes.dart
import 'package:customer_mobile/screens/boot.dart';
import 'package:flutter/material.dart';

class RouteNames {
  RouteNames._();

  static const String Boot = '/';
}

class RouteModule {
  static final routes = <String, WidgetBuilder>{
    RouteNames.Boot: (context) => BootScreen(),
  };
}

l10n.yaml
template-arb-file: en_US.arb

pubspec.yaml
name: test
description: A new Flutter project.
publish_to: none

version: 1.0.0+20241125

environment:
  sdk: ">=3.3.0-0 <4.0.0"
  flutter: ">=3.3.0 <4.0.0"

dependencies:
  flutter:
    sdk: flutter
  flutter_localizations:
    sdk: flutter
  intl: ^0.19.0

dev_dependencies:
  flutter_test:
    sdk: flutter

flutter:
  # Adds code generation (synthetic package) support
  generate: true

I/flutter (31697): locales reset
I/flutter (31697): [zh_Hans_CN, en_US, pt_BR, wae_CH, de_DE, en_GB, fi_FI]

Hi @david-snyder-induro, are you only seeing this on Samsung devices? On my Pixel 7, the order appears to be correct. Also, do you get the same experience in a native android sample app? I think flutter only returns the list in the order in which the android OS sends it back to flutter.

I'm seeing on more than just Samsung devices, it's happened on a Pixel 6a. I haven't tried with a native android sample app yet

@danagbemava-nc
I'm seeing this on a Pixel 6a as well. I maintained my system language while setting my app language to Chinese. I notice the print statement says: [en_US, zh_Hans_CN]

Hi @kevin-induro, @david-snyder-induro can you try the sample below to see if the locales are returned in the order you expect them? You can create a new android project in android studio and test it out. The code sample below is based on how flutter resolves the locales from the android system.
package com.example.locale

import androidx.appcompat.app.AppCompatActivity
import android.os.Bundle
import android.widget.TextView

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.activity_main)

        val textView = findViewById<TextView>(R.id.textView)

        val localesList = applicationContext.resources.configuration.locales

        val size = localesList.size()

        var locales = ""

        for (i in 0..<size) {
            locales += "${localesList.get(i).language}-${localesList.get(i).country}\n"
        }

        textView.text = locales.split("\n").joinToString(",")
    }
}

PS: @kevin-induro, if you're maintaining your device language, that is likely why it is appearing first because as the screenshot indicates, it is preferred first.

I fixed the issues by removing this line from my build.gradle that I forgot to include in the minimal reproducible code comment.
resConfigs "en", "fr", "ja", "de", "nl", "zh", "es"


Valid certificate results in VC_HC_CBOR_DECODING_FAILED

Avoid duplicates

[x] Bug is not mentioned in the FAQ
[x] Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[x] Bug is not already reported in another issue

Technical details

Device name: Samsung J5 2017, Samsung M31
Android version: 9, 10
App version: 2.3.2

Describe the bug

I have a EU Digital COVID certificate issued in Poland. The certificate, according to the Android App is not valid and results in an error code: VC_HC_CBOR_DECODING_FAILED
The same certificate can be successfully imported in the iOS version of the application.
I tried two different certificates, on different Android phones and the result is the same.
Steps to reproduce the issue

Scan the certificate

Expected behaviour

Certificate is correctly imported, same as on the iOS version of the app.

Internal Tracking ID: EXPOSUREAPP-7776
VC_HC_CBOR_DECODING_FAILED
Internal Tracking ID: EXPOSUREAPP-7829
CovPassCheck does not accept Polish/Bulgarian DCC shown on CWA

I also have this problem with a Bulgarian vaccination certificate. I get the same error message and the following detailed trace:
de.rki.coronawarnapp.vaccination.core.certificate.InvalidHealthCertificateException: CBOR decoding failed. de.rki.coronawarnapp.vaccination.core.certificate.InvalidHealthCertificateException: CBOR decoding failed. at de.rki.coronawarnapp.vaccination.core.qrcode.VaccinationQRCodeExtractor.extract(VaccinationQRCodeExtractor.kt:51) at de.rki.coronawarnapp.vaccination.core.qrcode.VaccinationQRCodeExtractor.extract(VaccinationQRCodeExtractor.kt:1) at de.rki.coronawarnapp.vaccination.core.qrcode.VaccinationQRCodeValidator.validate(VaccinationQRCodeValidator.kt:5) at de.rki.coronawarnapp.vaccination.ui.scan.VaccinationQrCodeScanViewModel$onScanResult$1.invokeSuspend(VaccinationQrCodeScanViewModel.kt:12) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:3) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:15) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:1) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:12)
Out of the 4 QR codes at https://github.com/eu-digital-green-certificates/dgc-testdata/tree/main/BG the app only accepts the 3rd one labeled "Vaccinated DGC - schema errors fixed", all others report the same error.
I do not have an iOS device to test that app. If one the devs wants to take a look, I can send you my QR code.

@thomasaugsten
Do you know if CovPass App and CWA Android use the same code base (i.e., CovPass "forked" from CWA)?

Bulgaria app will be fixed tomorrow
CovPass and CWA not sharing a code base

@stgeo Do you have any "special character" in your name or address or another field, like @ltekieli has in its name: Ł in Łukasz ?

@stgeo

Out of the 4 QR codes at https://github.com/eu-digital-green-certificates/dgc-testdata/tree/main/BG the app only accepts the 3rd one labeled "Vaccinated DGC - schema errors fixed", all others report the same error.

As the first two have schema errors, an error while decoding can be expected. The 3rd one is corrected, and the 4th one is a recovery certificate, that is not yet accepted by CWA afaik.
Did you try only with these 4 or did your intial error come up with a valid certificate issued to you?

@vaubaehn

Do you have any "special character" in your name or another field, like @ltekieli has in its name: Ł in Łukasz ?

No special characters in my latinized name or address - all ASCII - but the originals are in Cyrillic, I don't actually know what's encoded in the QR code. There is actually no address printed on the certificate and all names are in both Curillic and Latin.

Did you try only with these 4 or did your intial error come up with a valid certificate issued to you?

The initial error was with my personal certificate.

A fix for Bulgaria and Poland will be delivered tomorrow with Android v2.3.4

Hi @thomasaugsten , I understood the underlying problem of this issue as follows:
There is no bug in the platform specific implementation, but some issuing authorities want to stay a little bit, er, flexible on how to use some data fields. This would require all scanning and validating apps to be as lenient/relaxed to the data as the issuing authorities make use of it.
By chance, CWA iOS was already relaxed enough to decode CBOR without crashing. But neither CWA Android nor CovPass App were similarly lenient.
Is my interpretation correct?
If my interpretation is correct, are you in contact with CovPass to forward these findings?
And what will be future consequences? Will all issuing instances (European-wide) with their own interpretation of data field contents/formats needed to be notified to correct their use? Or will all app developers (European-wide) need to adapt for any anticipated possible divergence of expected data formats?
If not, many travellers may experience bad surprises, when they travel only with their digital certificate, that was successfully scanned by their relaxed wallet app, but cannot validated by a verifier app that uses the consented constraints for data fields...

I can confirm all points.
There is a schema definition and some country add the time to date and now the schema definition needs to relax the checking on this
This is reported back to the EU and they will inform all apps and adjust the schema definition.

@thomasaugsten Thank you! Let's hope the best then.

Thanks for the fast response! I'll try with v2.3.4 when it rolls out on Google Play and I'll check back in with the results.

@stgeo  @ltekieli  The v 2.3.4 is available for download please retest the version with your QR-Codes

@stgeo @ltekieli The v 2.3.4 is available for download please retest the version with your QR-Codes

Works fine for me, thanks!

@ltekieli
Could you please try with CovPassCheck App if your QR presented with CWA is accepted? You will need a second phone to achieve this...

@ltekieli
Could you please try with CovPassCheck App if your QR presented with CWA is accepted? You will need a second phone to achieve this...

CovPassCheck fails to validate the CWA generated QR code, with message "Prüfung nicht erfolgreich".
I installed CovPassCheck both on Android and iOS, it fails the same way.

@stgeo @ltekieli The v 2.3.4 is available for download please retest the version with your QR-Codes

Also works for me, thanks! I actually think it was already fine on Friday after update to 2.3.3.

Could you please try with CovPassCheck App if your QR presented with CWA is accepted? You will need a second phone to achieve this...

Version 0.160.3 of CovPassCheck also failed for my certificate with "Es ist ein unerwarteter Fehler aufgetreten."

@ltekieli and @stgeo Thank you so much for your support!
@chiljamgossow and @d4rken
How are the scanned DCC data persisted inside CWA for generating a QR code at a later time for presentation to a verifier app?
Exactly bit by bit like they have been scanned? Then this would mean, that the generated QR code has a valid PKI signature, but the CovPassCheck (and possibly all other verifier apps) refuse the wrong field format introduced by the issuing authority.
Or is the scanned data sanitized (i.e., the superflous timestamp is eliminated) and persisted? That would break the PKI signature upon presentation, and lead to refusal in all verifier apps, now and in future.
Pinging @mlenkeit here, also pointing to https://github.com/corona-warn-app/cwa-app-android/pull/3403#discussion_r649057138 :
It looks like the whole approach how to handle correctly signed DCCs with issues in their JSON fields need to be re-evaluated.
In discussions with @thomasaugsten I understood, that ehn will adapt schemas that also will retain backwards compability. But for now I don't see any hint that they will be able to incoorporate all potential issues.
Maybe it would be good to mirror back the problems and your findings back to the EU taskforce in charge asap, and to find a solution that can also account for the already faulty issued DCCs in a coordinated approach.
Thomas mentioned the "business rule runner", but after having a look into the related schema repos, I have my doubts that a rule runner can solve all these problems.

After looking into https://github.com/eu-digital-green-certificates/dgc-testdata/issues/298 and to other issues reported in that repo, I'm wondering if it is useful at all for the time being to have ANY wallet app and verifier app live and in production.
It becomes obvious, that many issues already exist, and by adjusting schemas and their validation rules new issues may be introduced.
As far as I understand the whole current approach, it will work only reliably for users/travellers from that only moment on, when
a) wallet apps nearly accept anything for importing, storing and later presentation of DCCs/QR codes, and
b) verifier apps everywhere work without any issue, meaning they are working that flexible that they can update their validation rules at any time.
For now, for me it looks like we're still far away from that point.
If wallet apps like CovPass but also CWA are already offering their service, we'll probably see much more often problems like reported in this issue.
This may result in
a) users, who are irritated why their DCCs are not imported to CWA (any other wallet app) or not being successfully approved by any/some verifier apps, and
b) likely much headache on our developers side, to continuously catch up with necessary adjustments caused by implementation problems all over the EU.
The only useful application of DCCs with wallet apps and verifiers, I can only see at the national level for this point in time, as single code adjustments to the apps (if necessary at all) can be controlled by far more easy. (To achieve this, CWA could refuse any non-DE DCC, until the EU DCC system works reliably).
If we leave the situation like it is for now, then at least CWA should present a warning to the user, that it cannot be guaranteed that the imported DCC is valid/approved at all points of verification.
I'd be happy to hear/read your thoughts - maybe I'm wrong or perceiving the problem bigger than it actually is?

Good morning @ltekieli @stgeo @vaubaehn, Thanks for reports and latest discussion. Internally tracked:
Internal Tracking ID: EXPOSUREAPP-7829
CovPassCheck does not accept Polish/Bulgarian DCC shown on CWA

Follow-up: I also placed some of the above questions here: https://github.com/eu-digital-green-certificates/dgc-testdata/issues/298#issuecomment-860619264

How are the scanned DCC data persisted inside CWA for generating a QR code at a later time for presentation to a verifier app?
Exactly bit by bit like they have been scanned?

We store the original QR code and decode on-the-fly when necessary.
See (for 2.4.x):
https://github.com/corona-warn-app/cwa-app-android/blob/e1d100bf8959cdb4bbc7ee29cb86c593a8cdee52/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/covidcertificate/vaccination/core/qrcode/VaccinationQRCodeExtractor.kt#L29-L42
https://github.com/corona-warn-app/cwa-app-android/blob/e1d100bf8959cdb4bbc7ee29cb86c593a8cdee52/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/covidcertificate/common/qrcode/DccQrCode.kt#L7-L16
https://github.com/corona-warn-app/cwa-app-android/blob/e1d100bf8959cdb4bbc7ee29cb86c593a8cdee52/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/covidcertificate/vaccination/core/repository/storage/VaccinationContainer.kt#L20-L23

@d4rken

We store the original QR code and decode on-the-fly when necessary.

Great, and thanks for the pointer into the code.
So biggest headache/challlenge for CWA then seems to be how to incorporate all other known and still unknown deviations from the schema (currently 1.3) to allow for a basic but relaxed validation for accepting and decoding DCC.
And let's see how the verifier apps will do.

@ltekieli
We have fixed this bug in CWA hotfix release 2.3.4. Please retest with the current app version.

Corona-Warn-App Open Source Team

@ltekieli
We have fixed this bug in CWA hotfix release 2.3.4. Please retest with the current app version.
Corona-Warn-App Open Source Team

Yes, we already checked and the 2.3.4 works fine.
FYI, the Polish wallet app https://play.google.com/store/apps/details?id=pl.nask.mobywatel&hl=pl&gl=US is now supporting the certificates. What I noticed is that my certificates were regenerated and now have a different identification number. This certificate is now correctly scanned by the CovPassCheck application.

@ltekieli

What I noticed is that my certificates were regenerated and now have a different identification number.

Do I understand correctly:

you imported the troubled Polish certificate to the Polish wallet app
At some point in time, your DCC was regenerated with correct field formats and pushed into your wallet app actively by the related health authority?

@heinezen
For a short sum-up: Not only the Polish DCC (@ltekieli ) was affected from not being imported into CWA due to wrong usage of allowed field formats by the issuing institutions, but also the Bulgarian DCC (@stgeo ). There is a certain likelihood that more issues may pop up with other DCCs in the future, too.
CWA devs could handle that gracefully by adapting JSON field parsing and validating.
But then there was the problem, that verifier apps (here: CovPassCheck-App) had the same problem in not being able to correctly parse the DCC, and in result not accepting them. That part of the problem is also tracked in this issue, and here: https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-7829
So the still open problem in this issue is, how CWA should handle similar DCC flaws in the future. If CWA devs adapt quickly to accept DCCs with flaws, it could be, that users may import generally valid DCCs into CWA, but later be rejected at border control, because their verifier apps have not been updated that fast.
The minimalst solution could be, to provide a warning to the user inside CWA, that there is no guarantee that the DCC will be accepted at border control.
The best solution would be, that all wallet apps and verifier apps could rely on a centrally maintained and updated config that can be used for a more dynamic and flexible field parsing, and that would need to be implemented into CWA as well (note: this is not the business rule runner that has a different aim. I'm not sure if maybe CertLogic introduced by @dslmeinte could solve the problem?).
As long it's unclear which way CWA should go and we'll receive feedback here, I'd suggest to leave this Issue open.

Do I understand correctly:
* you imported the troubled Polish certificate to the Polish wallet app

* At some point in time, your DCC was regenerated with correct field formats and pushed into your wallet app actively by the related health authority?

No, the polish wallet received the certificate synchronization just today. It does the import automatically from the polish health portal. So I imported the certificate and noticed it has a different ID. I also download the PDF directly from the health portal and it now contains a new ID as well.
So the DCC was regenerated at some point.

@ltekieli
Thanks for your explanation. Sounds like a great approach how it was designed in Poland. Maybe one day we get Germany digitized as well...

But then there was the problem, that verifier apps (here: CovPassCheck-App) had the same problem in not being able to correctly parse the DCC, and in result not accepting them. That part of the problem is also tracked in this issue, and here: https://jira-ibs.wbs.net.sap/browse/EXPOSUREAPP-7829

That was a different issue than the one in CWA, in the CovPassCheck app (which got fixed).

The best solution would be, that all wallet apps and verifier apps could rely on a centrally maintained and updated config that can be used for a more dynamic and flexible field parsing, and that would need to be implemented into CWA as well (note: this is not the business rule runner that has a different aim. I'm not sure if maybe CertLogic introduced by @dslmeinte could solve the problem?).

As far as I know that already exists (or is planned). You can request the individual schemas the countries use through the DCC API. Using the correct schema is mostly the responsibility of the verifier app.

Anyway, I suggest opening a new discussion/question issue for schema validation in cwa-documentation if that needs more input for discussion because it is out of scope for this specific Android issue. The bug is fixed and all related tickets have been completed already.
I'll close here and we can either mirror the relevant comments or link them in the new issue.

Corona-Warn-App Open Source Team


Make StopContainer RPC idempotent

Similar to container removal, the stop of a container should be a noop if the container has not been found.
Found during: https://github.com/kubernetes-sigs/cri-tools/pull/1536

/cherrypick release/1.6

/cherrypick release/1.7

/cherrypick release/1.7
(I'm fairly sure this automated cherry-pick will fail as there have been significant differences in the CRI files; 1.7 has 2 separate CRI implementations and 1.6 has only the legacy one which is not present in 2.0.  Manual backports are likely going to be required here.)

/cherrypick release/1.6


chore(package): update rollup to version 1.19.4

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add 'now' and 'soon' markers to event cells

If the Events page is viewed at a time where there are events on the page that are in progress (start time < current time < end time) those events should indicate their in-progress state.
Ideally this feature would be supported by a bit of JS that at a minimum hides the 'now' marker when it goes stale; even better would be to keep the 'now' markers current throughout the day without reloading the page.
Same idea for "soon' markers: A visual indicator for events that are starting in the next (30 mins? 60 mins?) to help users quickly find an event about to start that they might be interested in.
Note that unlike this issue, these UI elements aren't interactive.

Added banners, and there is now JS that updates the banner states throughout the day. A user could load the Events page and keep it open, and the event cells should update themselves all day.


fix: useFetchInit() hook calls same amount every render

Fixes #1101 .
Motivation

useFetchInit() can call hooks, so we need to ensure it is called only from top level and not conditionally
Solution

Hoist all endpoint calls to top level.
Validated against example usage from https://github.com/coinbase/rest-hooks/issues/1101
Open questions
We should think about suggesting use-prefix for endpoints that use this to ensure linter helps avoid these scenarios.

Adding tests now


Support CDH5.7.2?

I would like to ask this support CDH5.7.2 ?

Cloudera Labs has a release of Phoenix 4.7 for CDH 5.7, please see http://archive.cloudera.com/cloudera-labs/phoenix/parcels/latest/

@apurtell thanks


Information is partially invisible at 1366x768

Left column of the table is usually invisible when viewing in a browser at 1366x766 - it is covered by right floating-like area/panel with page content:
https://i.ibb.co/km5Z95J/2020-07-06-Visual-Studio-Community-component-directory-1366x768-Firefox.png
And there is no horizontal scrollbar.
There are 10%-like marging at left and right edges, which are just a waste of space.
You cannot hide the tree-like structure, which eats a lot of space, but is useless when you reviewing the page content.
Checked browsers: Vivaldi 2.11.1811.47, Opera 67.0.3575.79, Firefox 74.0
Workaround: you can bring hidden information into view with the mouse - left-click and drag as if selecting some text.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4891ebc9-fdea-c376-94f6-17295ca275d7
Version Independent ID: ccc61918-cc18-a7ff-cc6c-8659d6c9c78a
Content: Visual Studio Community workload and component IDs
Content Source: docs/install/workload-component-id-vs-community.md
Product: visual-studio-windows
Technology: vs-installation
GitHub Login: @ornellaalt
Microsoft Alias: ornella

@Anton-V-K -- thank you for your feedback; we appreciate it. You can submit issues related to overall site experience, or suggestions for improved site functionality or design, at https://aka.ms/sitefeedback/.


add homebrew formula

It would be cool for us to have a homebrew formula so that on new releases, folks using Mac OSX can just type
$ brew install drive

@shaggytwodope and the other kind Linux folks already have support for Linux PPAs e.g https://github.com/shaggytwodope/drivedebpackage.

(by extension, you might end up with a working linuxbrew and or chromebrew package too)

That'll be interesting. I hadn't heard of chromebrew till you mentioned it.

Moving this to the Unreleased milestone, as it is low priority and no one has asked for it yet.

@odeke-em would love to see this happen. see related issue: https://github.com/odeke-em/drive/issues/988

It's kinda sad that we still don't have this :(


[Backport 1.3] Bumps snakeyaml to 2.0

Manual backport of https://github.com/opensearch-project/OpenSearch/pull/6511 to 1.3

Codecov Report

Merging #6600 (90972b6) into 1.3 (5be0bd2) will increase coverage by 0.07%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##                1.3    #6600      +/-   ##
============================================
+ Coverage     77.89%   77.97%   +0.07%
- Complexity    63422    63500      +78
============================================
  Files          4454     4454
  Lines        274963   274963
  Branches      41167    41167
============================================
+ Hits         214188   214395     +207
+ Misses        43854    43674     -180
+ Partials      16921    16894      -27

Impacted Files
Coverage Δ

...ava/org/opensearch/action/NoSuchNodeException.java
0.00% <0.00%> (-50.00%)
:arrow_down:

...rch/index/engine/RefreshFailedEngineException.java
50.00% <0.00%> (-50.00%)
:arrow_down:

...h/index/engine/EngineCreationFailureException.java
50.00% <0.00%> (-50.00%)
:arrow_down:

...adcast/BroadcastShardOperationFailedException.java
55.55% <0.00%> (-44.45%)
:arrow_down:

...java/org/opensearch/threadpool/ThreadPoolInfo.java
56.25% <0.00%> (-37.50%)
:arrow_down:

.../opensearch/client/indices/CloseIndexResponse.java
41.97% <0.00%> (-34.57%)
:arrow_down:

...va/org/opensearch/client/sniff/SnifferBuilder.java
72.72% <0.00%> (-27.28%)
:arrow_down:

...repositories/gcs/GoogleCloudStorageRepository.java
68.57% <0.00%> (-20.00%)
:arrow_down:

...luster/settings/ClusterUpdateSettingsResponse.java
81.39% <0.00%> (-18.61%)
:arrow_down:

...rch/repositories/gcs/GoogleCloudStoragePlugin.java
81.81% <0.00%> (-18.19%)
:arrow_down:

... and 457 more

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

@naveentatikonda I labeled backport-1.x, if that fails care to do it manually please?

@naveentatikonda I labeled backport-1.x, if that fails care to do it manually please?

Sure. Looks like it didn't create a new PR. So, did it fail?


Presence of 'clone' stack in flamegraph

This might not be an issue, and arguably off-topic, but I am puzzled by the presence of a 'clone' stack in a flamegraph of a Java application (see below).
Does the graph indicate that the 'clone' method is using a significant part of the total CPU cycles, but that the callers of the 'clone' method do not?
Also, why would 'clone' call 'start_thread'?

This is not a Java method Object.clone, but rather a system clone function. In Linux, clone syscall is used to create a new thread. Basically, every thread except the primordial one starts with clone - that's why you see it at the very bottom of the graph.
The red part on the right side of the graph presumably belongs to VM threads, particularly, GC and JIT compiler threads. And yes, GC and JIT compilation make take significant amount of CPU time. I suggest installing JDK debug symbols in order to see exact JVM function names instead of just libjvm.so.

Makes sense. Thank you, Andrei.


remove user input option for controlling maximum number of messages

Review #320 first

Add this to failed graph too

Ok noted. I will remove this once I add the slider for the graph.


Usability - HaT "Crit Rate"

Is your feature request related to a problem? Please describe.

HaT's "Crit Rate" field is a bit unintuitive. Just my opinion, others may disagree, but wanted to put my stick on the pile.
Describe the solution you'd like
I know it's trivial math to use the field as is, but I think it would be more intuitive to say ComboPoints / sec for the setting title / input (Or, "time between combo points"). I feel like most people will have a much more immediate grasp on what is being calculated if it were framed that way.

Reflecting on this further, I think that what is listed is fine, after using it a discussing different numbers for a default.


Migrating Font Bakery scripts into Google Fonts Tools

Font Bakery from now on will be focused on a sigle purpose:
a Quality-Assurance automated testing framework for font families.
(issue #3 and https://github.com/googlefonts/fontbakery/issues/1639)
Please leave this open while I work on the full migration.

Thank you Felipe!


Roadmap

[ ] Implement NLogViewer.Server
[ ] Implement NLogViewer.Webinterface
[ ] Implement NLogViewer.ClientApplication

NLogViewer.Server
.NET server application which can handle the NLogViewerTarget (https://github.com/NLog/NLog/wiki/NLogViewer-target) and provides the NLogViewer.Webinterface
NLogViewer.Webinterface
Provides an extension method to add an webinterface to your .NET Server application.
Example call in your Startup.cs
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
	app.UseNlogViewerWebinterface(new NLogViewerWebinterfaceOptions()
	{
		Path = "/nlogviewer"
	});
}

NLogViewer.ClientApplication
Standalone application which can handle the NLogViewerTarget.

Please feel free to contribute

The web interface should be like the swagger ui? enbebend into the the assembly and independent from the host web site?

Hi Daniel,
Thank you for your feedback signal.
I think the look of the UI would be secondary in my opinion. I regularly run a .net server application and also a client application. In order to evaluate the logs on the server, I have to access the server remotely and read the logs there using Sentinel.
It would be easier and more comfortable to start Firefox/Chrome and use https://serverIP/nlogviewer to look at the logs.
The communication between server and client is already web-based.


envoy: fix panic writing accesslog without L7 tags

PR #24649 removed the deprecated support for adding fallback HTTP log tags if the access log entry wasn't of type HTTP, Kafka or GenericL7.
This removal leads to panics when the l7Tags function (nil) is called while trying to enrich the log entry.
Therefore, this commit changes the behaviour by defaulting to an noop l7Tags function if no specific L7 information are present.
Needs backport to v1.14 & v1.13 (#26722)
Fixes: #27442

/test


FR: test dataset

I'd like to add a genome-, annotation-, size- and index file containing the first 100.000 or so nt of chromosomes 1 & 2. Together with several tiny fastq files, both paired- and single-ended, stranded and non-stranded, with (sythethic) features for replicate merging and DE contrast design.
This would speed up Jenkins tests (as files only need to be downloaded for the download test), and allows for more robust testing.
Improved testing would allow us to implement the conda version-upgrading bot

Stranded PE RNA-seq data added with #189.


Add APIs to control carbon-cache flushing

This patch adds APIs that control carbon-cache mermoty flushing

/metrics/persist-cache
This allow to ask carbon cache instances to dump their cache memory to disk. This action is executed during carbon-cache shutdown
and at regular interval. This can be force with this API
Sample : curl "http://localhost/metrics/persist-cache" -X POST

metrics/flush-cache?metric=
This allow to ask carbon cache instances to flush queues matching the given regexp
The current cache write strategy is hold during this operation, and restore after all matching queues are flushed
This operation can be cancel by calling the API with DELETE method (without parameters)
Sample : (start flushing) curl "http://localhost/metrics/flush-cache?metric=^carbon" -X POST
(stop flushing)  curl "http://localhost/metrics/flush-cache" -X DELETE

Note: This patch requires a patch in carbon-cache (https://github.com/graphite-project/carbon/pull/419)

Tried both calls with corresponding Carbon patch - LGTM, both works. :+1:

I've just update the PR to include a new API that allow to change some carbon cache settings online.
The following settings are supported :

CACHE_WRITE_STRATEGY
CACHE_WRITE_TUNED_STRATEGY_LARGEST
CACHE_WRITE_TUNED_STRATEGY_RANDOM
CACHE_WRITE_TUNED_STRATEGY_OLDEST
CACHE_PERSIST_INTERVAL
MAX_UPDATES_PER_SECOND
Sample :
curl localhost/metrics/set-param -X POST -d '{"key":"CACHE_WRITE_STRATEGY","value":"tuned"}'
curl localhost/metrics/set-param -X POST -d '{"key":"MAX_UPDATES_PER_SECOND","value":"1"}'

Note: changes are not persistant. If process is restarted, settings from configuration file will be restored

@llicour I have the same response here as in https://github.com/graphite-project/carbon/pull/419; this looks like a neat addition but it belongs in master. I'm going to close these PRs down but I'd really like to see them submitted again against the master branch.

@llicour - I'm using this functionality internally anyway... Will you mind if I port it to master ?

@deniszh Please try to cherry-pick them from @llicour's branch, if possible.


General Functionality Pose Annotator

Not entirely sure what happened with the committing, but it said I added 439 lines, which isn't correct. I added lines 74-80, 319-370.

Closing this PR as it's pretty mangled. (Check the "files changed" tab: there are uncorrected merge errors and so forth.) I assume the next PR is cleaner?


Aggregate functions should take a wildcard to work on all columns

As a shortcut in the query language, it would be great to be able to aggregate all columns with a given function. Like this:
select sum(*), mean(*) from some_series group by time(10m)

Where it would expand the query out into a sum for each column. Previously, we didn't have a definition of what columns existed over all time for a series. Now that metadata is in Raft, we know the columns by just looking it up.
This would have to have some intelligent failure logic to deal with column types where it doesn't make sense like strings. In that case it should just omit that from the results.

:+1: It would also be great if the resulting data could be grouped by the column name (eg. for making lines in grafana)

+1!

Seems less relevant with 0.9.0 data structure. Closing.

It could be very useful for continues queries; so i could put one query to back all my high precision 1 day retention data, into lower precision 1 week retention data.
something like:
CREATE CONTINUOUS QUERY rp1w_query ON mydb BEGIN
SELECT max() INTO "rp1w1".:MEASUREMENT FROM /./ GROUP BY time(1m)
END

closing in favor of https://github.com/influxdb/influxdb/issues/4708


Apply @JsonFlatten to all types referenced in flattened types

Including properties, base types, sub types, etc

Closing as flattening isn't really recommended and with the move to azure-json this annotation won't be used in the future.


Adding travis ci

Created a simple version of  .travis.yml.
I left commented out a config for adding codecov (coverage) after the build if one day you want to include it.
Issue #2

thx


Depth generated image is all noise on rgb or infra obtained from Gazebo simulated d435

Great work! Results look promising! I am facing an issue with data obtained by gazebo. I am simulating a realsense d435 and I want to have a noisy depth image simulating the real one.
I have obtained 2 rgbs from 2 cameras 5cm to each other, and also 2 infra images obtained from infra1 and infra2 of the same camera.
Both output me the same result with simsense:

And inputting infras of the same camera:

RGBS of 2 different cameras at 5cm.

Any clue? I am using my custom
    k_l = np.array([
        [1386.41, 0.0, 960.0],
        [0.0, 1386.41, 540.0],
        [0.0, 0.0, 1.0]
    ])

for the rgb and another custom for the infras.

Hi, to get reasonably good result you should use IR images simulated with active light pattern of D435. If you take a look at the test images simsense used, the scene has been exposed with IR light. Without active light it's hard for stereo matching to get correct depth, especially for inputs with flat texture like yours. If you are interested in how to simulate IR images with active light I recommend you take a look at sapien.

Thank you very much for the quick reply! I thought it would also be possible with just rgb images. Right now I do not want to migrate all my workflow to Sapien as I am using Gazebo. If I manage to solve my issue, I will definitely test Sapien with a similar workflow! If there is nothing else I can try, feel free to close the issue! Thanks again for your time @angli66


[com.google.fonts/check/glyphsets/shape_languages] output is overly repetitive

(NOTE: Please include the check-id in the issue's title.)
Observed behaviour
The same error is output multiple times, even for the same language.
For example, when testing SIL's Doulos font, v6.200, excerpt of the output for Mundani language is:
           mnf_Latn (Mundani)                           Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0268.sc
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0268.Dotless.sc
           ^                                            Shaper didn't attach uni0327 to uni0268.Dotless.sc
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0268.Dotless.sc
           ^                                            Shaper didn't attach uni0327 to uni0268.Dotless.sc
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0268.Dotless.sc
           ^                                            Shaper didn't attach uni0327 to uni0268.Dotless.sc
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0254.sc
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0254.sc
           ^                                            Shaper didn't attach uni0327 to uni0254.sc
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0254.sc
           ^                                            Shaper didn't attach uni0327 to uni0254.sc
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0254.sc
           ^                                            Shaper didn't attach uni0327 to uni0254.sc
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0186
           ^                                            The locl feature did not affect Eng

Expected behaviour
Errors should be output only once, or at most once per language. Removing redundant lines from the above and sorting yields only 6 unique messages related to Mundani:
           mnf_Latn (Mundani)                           Shaper didn't attach uni0327 to uni0186
           ^                                            Shaper didn't attach uni0327 to uni0197
           ^                                            Shaper didn't attach uni0327 to uni0254.sc
           ^                                            Shaper didn't attach uni0327 to uni0268.Dotless.sc
           ^                                            Shaper didn't attach uni0327 to uni0268.sc
           ^                                            The locl feature did not affect Eng

Resources and steps needed to reproduce
Doulos SIL, v6.200, downloadable from https://software.sil.org/doulos/download/
Command:
fontbakery check-googlefonts -c com.google.fonts/check/glyphsets/shape_languages DoulosSIL-Regular.ttf | more

(Mundani is the 2nd language mentioned in the output)
fontbakery from source at tag v0.12.1
python 3.10.12
ubuntu 22.04

Excellent!  Thanks.

you're welcome ;-)


how to modify the converted color of the semantic segmentation sensor

I am using semantic_segmentation sensor and I do not want so many classes, how I can modify the converted color, for example, I want to modify the color of the Fence (original color is (190, 153, 153)) to the Unlabeled class (0,0,0).
Thank you

I have two ways to do it.

Util/ImageConverter/label_pixel_converter.h
you can modify this code

// Someday this will be in a config file or something.
constexpr static Color LABEL_COLOR_MAP[] = {
{  0u,   0u,   0u}, // None         =   0u,
{ 70u,  70u,  70u}, // Buildings    =   1u,
{190u, 153u, 153u}, // Fences       =   2u,
{250u, 170u, 160u}, // Other        =   3u,
{220u,  20u,  60u}, // Pedestrians  =   4u,
{153u, 153u, 153u}, // Poles        =   5u,
{153u, 153u, 153u}, // RoadLines    =   6u,
{128u,  64u, 128u}, // Roads        =   7u,
{244u,  35u, 232u}, // Sidewalks    =   8u,
{107u, 142u,  35u}, // Vegetation   =   9u,
{  0u,   0u, 142u}, // Vehicles     =  10u,
{102u, 102u, 156u}, // Walls        =  11u,
{220u, 220u,   0u}  // TrafficSigns =  12u,
};

Deprecated/PythonClient/carla/image_converter.py

def labels_to_cityscapes_palette(image):
"""
Convert an image containing CARLA semantic segmentation labels to
Cityscapes palette.
"""
classes = {
0: [0, 0, 0],         # None
1: [70, 70, 70],      # Buildings
2: [190, 153, 153],   # Fences
3: [72, 0, 90],       # Other
4: [220, 20, 60],     # Pedestrians
5: [153, 153, 153],   # Poles
6: [157, 234, 50],    # RoadLines
7: [128, 64, 128],    # Roads
8: [244, 35, 232],    # Sidewalks
9: [107, 142, 35],    # Vegetation
10: [0, 0, 255],      # Vehicles
11: [102, 102, 156],  # Walls
12: [220, 220, 0]     # TrafficSigns
}
array = labels_to_array(image)
result = numpy.zeros((array.shape[0], array.shape[1], 3))
for key, value in classes.items():
result[numpy.where(array == key)] = value
return result


Chroma doesn't output highlighting in a table

I've been using the highlighting shortcode (eg {{< highlight ini "linenos=table" >}})  to output line numbers into one column and code into another, so I can style numbers separately. Is this feature gone forever unless I fallback to Pygments?

I don't know that it's "gone forever", but it's not supported currently.  Keep in mind that Chroma is brand new, as in, 4 months old.  I think the Hugo team only heard about it a few weeks ago.  Give Alec and the community time to add features, and we'll see how this plays out.

@mckern, please see Alec's comment: https://github.com/alecthomas/chroma/issues/45#issuecomment-332383732.

@mckern, if you set pygmentsUseClasses = true in your site config, you should get something like this that you can style:

1interface Tunnel0
2description GRE tunnel to other location
3ip address <IP_ADDRESS> <IP_ADDRESS>
4tunnel source FastEthernet0/0
5tunnel destination <IP_ADDRESS>
6crypto map tunnel-ipsec-map

Thank you for the suggestion. I tried that but it doesn't work for what I specifically want. Here's an example of what I'm doing -- I use the linenos=table the table has the benefit that line numbers are not copied into the buffer if someone copies lines out of a code block. I can keep using Pygments -- the speed isn't a problem for me. But the incompleteness of the Chroma paired with it being the new default (instead of an option to disable) is frustrating.

@mckern,
Can you use the user-select: none style to accomplish the same thing?

@mckern I do want to add table support, for the exact reason that copy+pasting is much more convenient. It's on The List™.

Also note that I kept the options syntax identical between Chrome and Pygments (for several reasons), but that also means that you should just transparently and eventually "get more".

Hey, just chiming in to say thanks for this. The constant iteration and improvement on Hugo is so impressive, and turning around something like this in less than a month? It's amazing. Thanks again.


Controls are messed up.

Describe your bug here.
The controls have been messed up by the 1.0 update.
In the menu:
Every button other then E appears to do either nothing, or the wrong thing. For isntance, Up is A, Down is Z, Left and Right appear to do nothing, and I can't figure out what ABXY do.
In game:
Left = Down
Down = Up
Up = Nothing
Right = Left
I even tried having the game re-download assets, and eventually reinstalling, and the issue persists.
Crash Log or logcat logs (if existing)
No response
Are you modding a build from source or with Lua?
I am not modding
What is your build target?
Android
Which psych engine version you're on?
1.0 (Final)
Did you edit anything in this build? If so, mention or summarize your changes.
No.

fully reinstall


Fix ENABLE_ENHANCED_RESOURCE_SCOPING bug

Please provide a description of this PR:
Fix #42173
when ENABLE_ENHANCED_RESOURCE_SCOPING enabled, namespace selected/deselected we should  trigger full push so that the CRs within the namespace will be handled correctly

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
9a1e3edf653e021da816f10690402adad79727d5
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thank you @hzxuzhonghu :)
I will verify the fix on my end and let you know asap

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
f0c19bcd65bd78f3a3cb3249fbf96e0463d0b5f0
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
8371bb5351f253efd98c174d7a128408ef0fd4e9
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
dd373257aee77dba7aeafed7a27fb27be4528c7f
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
dd373257aee77dba7aeafed7a27fb27be4528c7f
link
true
/test unit-tests-arm64

unit-tests_istio
dd373257aee77dba7aeafed7a27fb27be4528c7f
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
dd373257aee77dba7aeafed7a27fb27be4528c7f
link
true
/test unit-tests-arm64

unit-tests_istio
dd373257aee77dba7aeafed7a27fb27be4528c7f
link
true
/test unit-tests

integ-basic-arm64_istio
dd373257aee77dba7aeafed7a27fb27be4528c7f
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
dd373257aee77dba7aeafed7a27fb27be4528c7f
link
true
/test unit-tests-arm64

unit-tests_istio
dd373257aee77dba7aeafed7a27fb27be4528c7f
link
true
/test unit-tests

integ-basic-arm64_istio
dd373257aee77dba7aeafed7a27fb27be4528c7f
link
true
/test integ-basic-arm64

release-test_istio
dd373257aee77dba7aeafed7a27fb27be4528c7f
link
true
/test release-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Sorry didn't get a chance to take a look yet, maybe @ramaraochavali can. Or I should be less busy next week (oncall this week)

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
cd69a6ff248ed89d212b4a6d54d9598889b39829
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for all your reviews

In response to a cherrypick label: #42188 failed to apply on top of branch "release-1.16":
Applying: Fix bug: when discovery selector change or namespace label change caused ns selected/deselected, we should trigger full push because CRs need to be selected/deselected too
Applying: add release note
Applying: redundant trigger for namespace add event
Applying: Add test
Using index info to reconstruct a base tree...
M	pilot/pkg/serviceregistry/kube/controller/controller_test.go
Falling back to patching base and 3-way merge...
Auto-merging pilot/pkg/serviceregistry/kube/controller/controller_test.go
CONFLICT (content): Merge conflict in pilot/pkg/serviceregistry/kube/controller/controller_test.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0004 Add test
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #42330


Cannot set admin password in WebUI on 1.1.0

There does not appear to be a way to set the admin user's password on a fresh install of 1.1.0 when using ldap_auth. Is there a way to set this credential from the command line, or what is the new method for changing this password?
Thanks!

It's a bug and will fix it soon.

I upgraded to 1.1.1-rc1 but still cannot see how to change the admin user's password when LDAP is enabled - how can I do this?

please make sure that you are running 1.1.1-rc1, and click admin's user name, change password option is above about

It appears to be working now - I'm not sure if had some caching going on in my browser or what the problem was yesterday, but I can see the "Change Password" link on the admin account now. Thanks!


Prepare new revision of Scrapple

Coverage increased (+0.14%) to 36.53% when pulling dbfe14de04d033241974f537ba0faab69703a8d3 on AlexMathew:scrapple into 2944669fc805569ea00186a2ac881e0c10888472 on scrappleapp:master.

Coverage increased (+0.14%) to 36.53% when pulling dbfe14de04d033241974f537ba0faab69703a8d3 on AlexMathew:scrapple into 2944669fc805569ea00186a2ac881e0c10888472 on scrappleapp:master.


Decimal(20, 0) seems misencoded

Currrently converted to Binary and schema Decimal(20, 0):

Spark displays it right:

But ParquetViewer displays it wrong:

Needs to be confirmed with datafactory behavior

SPD_INP_ORDER contains a BigDecimal >18:

Which is converted to string during parquet-ization:

Wrapped into String type in legacy-acl:

Then casted into IntegerType:

Based on this analyse, I suggest to keep this behavior to reduce rework side effects. But this library might not be copmpliant to parquet-format documentation


fix: delete unwrap

add check on nill

This change looks good for me, but can you please add a line in changeLog describing why you need this fix?
To fix a crash I guess :)

Similar fix has already be merge, then let's close this PR.
Let me know if it needs to be reopened


Does this work with a mocha html test runner?

Well, actually I'm not sure, because it uses istanbul cover and mocha command line executables, so it won't catch anything that is ran inside a browser.

Is this going to be part of the plugin someday or is not in the roadmap?
Thanks

this would requiring using both libraries programatically inside the task instead of relying on the command line, I guess would make it less flexible and more error prone

this would require another version of the task, using PhantomJS. I recomend using Karma for browser testing and coverage reports, which can generate coverage report just fine


Try cmake build and osx-arm64

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

This approach would need a cross-emulator, would it not? Zig via CMake uses a 3 stage process, first build zig1, which is used to create the zig2.c file

No idea! But it worked locally on osx-arm64 ... there was also some variable for finding LLVM without a running llvm-config. I just wanted to try :)

Oh right, but conda does not have an arm64 runner, we can only cross-compile for now, but there no emulator, afaik

Yep. I think what we should probably do is install zig using mamba inside the build process, and then use that to (cross-)compile the osx-arm64 zig and skip the whole CMake stuff here. I'll not be able to hack on that tonight though :) Maybe I'll give it a shot tomorrow but I also saw that you might already have solved it in the other PR?!
I did something similar recently for ruby: https://github.com/conda-forge/ruby-feedstock/blob/05d7453a068f542a4e198ff1c933ff4e23230851/recipe/build.sh#L8-L9
But maybe I also copied that from your SBCL work :)

Sure, that's what I am doing here: https://github.com/conda-forge/zig-feedstock/pull/35 - But because zig does not always build itself (0.12.0 cannot build 0.13.0), I use the binary that they distribute

That recipe becomes way too complex, I am getting lost. I am thinking to separate the builds for each specific platform rather than trying to make it fit together in one script

@wolfv This can be closed, correct?

@wolfv This can be closed, correct?

OMG, yes, I have been away for too long. Thx. Closing


Prevent AsyncBearerTokenCredentialPolicy deadlock

threading.Lock is not re-entrant, so it can cause a deadlock when used by coroutines (as seen in #11543):

coroutine A acquires the lock
A awaits another coroutine, yielding to the loop
coroutine B attempts to acquire the lock
threading.Lock.acquire() blocks the thread and thus also the loop
B never yields, A never resumes, the lock is never released

/check-enforcer evaluate


Use of ApiMachinery Sets with structs containing references

@skriss noticed while we were evaluating https://github.com/kubernetes-sigs/gateway-api/pull/1702 that some of the conformance test code wasn't working for him, particularly https://github.com/kubernetes-sigs/gateway-api/pull/1692#discussion_r1099010300 where the sets functionality from apimachinery was used with a struct with nested references. Sets does not currently support accurate Has(obj) functionality for structs with nested pointers, and so this test can not proceed properly.
Thank you @skriss! :partying_face:

/assign @arkodg

(@arkodg is working on this :+1: )


Docker error regarding 'version' in docker-compose.yml

OS: CentOS Linux release 7.5.1804 (Core)
Docker version: docker.x86_64                                                            2:1.13.1-63.git94f4240.el7.centos                                                            @extras
When attempting to follow the instructions to start the container :
# docker-compose up
ERROR: Version in "./docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the `services` key, or omit the `version` key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/

From some googling, I tried changing the following:
version: '2.3'

to
version: '2'

And this appears to have worked.

after looking at the docker docs it's not quite clear what the actual syntax should be for version, single or double quotes.

I believe this is a function of the docker-compose version. @BioSehnsucht mind sharing that version?

for instance these are my versions and the version string in docker-compose.yml works fine