How does DownsampleToViewSize  work?

I cant find detailed information about what are the pros and cons of DownsampleToViewSize ?
1 ) Does it cache the internet image as defined width and height? so I use same image on 1 page 48x48 and other page 64x64, I will have total 2 cached image? This is expected to increase cache size on the other hand, it should increase image load time because of it is pre-rendred. Is it Correct?
2) if my assumption in 1st is correct, I guess this doesnt make sense to use in UWP desktop application as user may resize the application? It should be similar problem changing between portrait and landscape modes.  It causes pixels to be lost I believe.
What exact benefits do I get using DownsampleToViewSize ?

Hi @EmilAlipiev,
Some explanation is on our WIKI page: https://github.com/luberda-molinet/FFImageLoading/wiki/Xamarin.Forms-API#downsampletoviewsize-bool-default-false
Feel free to update it (everyone can do it).

What exact benefits do I get using DownsampleToViewSize ?

If set to true image will resize to an image view size. Please note: this could not work on some layouts (eg. absolute layouts without RequestWidth/RequestWidthHeight specified, LayoutOptions.Fill in some specific scenarios, etc). Algorithm for choosing size: First View.Width/View.Height is checked, if it’s ⇐ 0 it falls back to: View.RequestWidth/View.RequestHeight, if it’s ⇐ 0 it falls back to using DownsampleWidth/DownsampleHeight properties. It’s not the best option for image views that have no initial size defined. For that you should use DownsampleWidth or DownsampleHeight properties and set your downsample size manually.

Does it cache the internet image as defined width and height? so I use same image on 1 page 48x48 and other page 64x64, I will have total 2 cached image? This is expected to increase cache size on the other hand, it should increase image load time because of it is pre-rendred. Is it Correct?

Yes, you will have two cached images (in memory cache) as we add downsampling size to the cache keys. That's why you have access to both approaches. If you use the same downsampling sizes on both images, you would use/cache only one image version.

if my assumption in 1st is correct, I guess this doesnt make sense to use in UWP desktop application as user may resize the application? It should be similar problem changing between portrait and landscape modes. It causes pixels to be lost I believe.

Resizing windows is not used as often and memory cache is recycled all the time, so no harm here. It's still useful in cases like listviews, when you have the same image appearing many times.


Enum properties cannot be decoded

Only builtins are decoded, enum properties throw an error.

Could you maybe provide a failing unit test?

I found the problem: https://github.com/LIonWeb-org/lioncore-typescript/blob/main/src/deserializer.ts#L96
Just haven't fixed it yet ;) A (now still-)failing unit test would nevertheless be helpful because this happens on M1-level which has more degrees of freedom.

I made the exisiting unit tests fail in the PR above. Is this the preferred way of contributing?

I don't know about any preferred way of contributing, but it's certainly a fine one: thanks! :)
I'm thinking about how/when to merge this: stay tuned.

I suspect that the serialization of enums also already didn't work.

(And neither did the Ecore import w.r.t. enums.)

Found a more fundamental problem: the runtime/in-memory representation of enum literals is, in general, entirely free, so this needs an explicit 2-way conversion for (de-)serialization.

Yeah, already thought so indeed. You are free to have a string-enum, number-enum, const enum or whatever so there is no single way of deserializing to an enum from the client-domain. For deserialization it would probably need something like: this in the ModelAPI?
enumLiteralFor: (literal: EnumerationLiteral) => any

Exactly, and a symmetric one for serialization.

Should be fixed by PR #60 : could you also check/review, @woppa684 ?


spec: remove the restriction on if/for at toplevel

The Starlark-in-Go implementation performs a static check that a program doesn't contain if or for statements at top level (outside any function), and I added language to this effect to spec.md, from which the current Skylark spec doc is derived. It occurs to me that this check is unnecessary, and I propose we get rid of it. Removing it would not change any fundamental invariants of the interpreter.
Of course, Bazel can (and must) continue to implement this check on the syntax of BUILD and .bzl files prior to executing them; the necessary logic is simple and efficient. In effect, we would be moving the check from core Starlark to the Bazel build language dialect, similar to the way that the build language disallows 'def' at top-level in a BUILD file.
Not every application that embeds Starlark wants the restriction, and I have encountered several for which it is undesirable.

Any comments on my comment?

Given that Bazel already must make a static pass over the syntax tree to reject def and **kwargs in BUILD files, and if/for at top level in .bzl files, and literally every other client of Starlark finedswants to use if/form

@laurentlb Can we document Bazel's static check for top-level for/if statements in the correct place, which is next to where we document its check for **kwargs and def statements in BUILD files, and remove the unnecessary complexity from the spec and implementation?

It's still unclear to me how this interacts with the "single assignment at top-level" rule.
for i in f():
    var = i

In this example, i and var are still global variables? So they are exported? But they're also reassigned during the evaluation?
Do we allow this?
for i in f():
    var = i
    var = var + 1

I propose that if and for-loops be allowed at top-level, and that the rejection of these features be moved into Bazel proper alongside its rejection of def and f(**kwargs)in BUILD files.
Regarding multiple assignments at top-level: we need to be careful to distinguish static ("binding") operations from dynamic ("variable update") operations. In your first example, the variables i and var are bound exactly once each, but are assigned zero or more times. In your second example, var is bound twice. Clearly we need to permit repeated dynamic assignments because that is what if and for mean. If Bazel wants to reject top-level rebinding (along with if/for-loops), we can make that the default behavior, though for most users of loops, top-level rebinding will be desirable, so I think it should remain a dialect option, as today in the Go implementation. I suspect few or no customers beside Bazel would want it. (As a matter of fact, even Bazel doesn't seem to want it: Bazel-as-documented may reject rebinding, but Bazel-as-implemented has always permitted it.)


suggest change primary name

Can we call this
GO:0051455	attachment of spindle microtubules to kinetochore involved in homologous chromosome segregation
GO:0051455	attachment of spindle microtubules to meiosis I  kinetochore

(this  is a bit shorter, seems to align more with how the users describe the process,  and the  homol ch. seg. is a given)

The user suggested this differentia
meiotic kinetochores
positive regulation of attachment of spindle microtubules to kinetohcore prior to meiosis I
but hey hadn't found the  "omologous chromosome segregation" term, only a parent

I'm happy to swap names & synonyms in FYPO, but a lot of this ticket looks aimed at GO ...

did some swapping & additional synonyms; will close this as the rest is for GO
edit file: 7c615f5578aaecbdaa42544f62f445982125c8af
release: 0c8676b23f5b26a53a6a44b80c518e11d337ef09

ok on my list to do the GO


Follow GNOME HIG

Even though this may not currently be within the scope of the project, I would think it is a good idea to try to stay as close to the guidelines as possible.
Here is a list of things I have noted that are in contradiction of the HIG:

Symbolic icon (#397), and also making sure that the colors used in the icon come from the palette
Adapt to accessibility settings and improve compatibility with such options: https://developer.gnome.org/hig/guidelines/accessibility.html
tooltips
keyboard shortcuts

Feel free to add any others, I'm not a coder so I can't comment on internals.

Thanks for the issue!
I was thinking of redoing the icon myself, (it doesn't have a dev variant either and it blends in with the dash) though nothing came out of this yet.
I'd love to have an a11y audit of Spot, for example, large text didn't work properly until very recently, so it'd be nice to be more consistent in that area. Feel free to test it out and leave issues concerning this.
Same with tooltips - it'd be great to be more consistent there.
There are some keyboard shortcuts but they aren't exposed in the UI. I don't think we have mnemonics either.

Good list of things to do :) we should have a few dedicated issues once we identify specific things that need to be adressed.
We already have a few shortcuts and tooltips, but we're a missing a few that's for sure!

for example, large text didn't work properly until very recently
I'm assuming this fix has not made its way to stable, as one thing I noted was the absence of large text support.

We already have a few shortcuts and tooltips, but we're a missing a few that's for sure!

I haven't noticed any tooltips, care to point me to them?

We already have a few shortcuts and tooltips, but we're a missing a few that's for sure!

I haven't noticed any tooltips, care to point me to them?

Just the playback controls really... :blush:

I'm assuming this fix has not made its way to stable, as one thing I noted was the absence of large text support.

Yeah, it's just on development branch so far.


Enable publishing for any SoftwareComponent with maven-publish

See issue #3390 for a full description.
This PR builds on top of #3399. Only the last 3 commits listed below are specifically related to this issue.

Rebased and merged manually.


Flow types wrong for Field's onFocus Event?

This is a possible bug. Forgive me if it's read as a support issue. I've searched issues/StackOverflow for related issues and came up empty.
What is the current behavior?
I understand from the docs that redux-form supports flow. I am receiving an error when setting a Field's onFocus property.
<Field .... onFocus={myOnFocus} >
Error:
Cannot create `Field` element because `SyntheticInputEvent` [1] is incompatible with
`Event` [2] in the first argument of property `onFocus`.

Callback:
const myOnFocus = (e: SyntheticInputEvent<HTMLInputElement>) => {
  e.target.select();
};

What is the expected behavior?
I believe onFocus should expect a SyntheticInputEvent.
Casting works:
const onDimensionFocus = (e: any) => {
  const event = (e: SyntheticInputEvent<HTMLInputElement>);
  event.target.select();
};

What's your environment?
redux-form 7.4.0, react 16.4, flow-typed 2.4

The same is happening to me with onChange

As a workaround I ended up having to cast through any:
const {
    input,
    ...rest
} = props;

return (
    <MyComponent
        {...rest}
        name={input.name}
        value={input.value}
        onBlur={input.onBlur}
        onChange={(newVal) => { input.onChange(newVal); }}
        onFocus={(e: any) => { input.onFocus(e); }} />
);


[Bug][connector-jdbc] JDBC get primitive type null value bug (#6567)

Purpose of this pull request
According to the JDK JDBC interface, when converting to a primitive type, if the column value was null, the returned values would be the default value of the corresponding primitive type. For example if the value of an type int in MySQL database is null, but in Hive it will be 0. This is a bug.
Does this PR introduce any user-facing change?
No
How was this patch tested?
yes
Check list
No

Thanks @lastbus for open this PR! Could you follow the guide to open ci on your fork repository? https://github.com/apache/seatunnel/pull/6569/checks?check_run_id=23047162515. Also, please add test case for this bug.

cc @mosence

Could you add a negative test case to prove the change worked? You can add it into jdbc e2e test case.

By the way, we try fix it before with https://github.com/apache/seatunnel/pull/5560


Matched Assets

As a user of the Guardian, I want to match emissions and offsets based on rules.

@envisionblockchainpm perhaps we need to make a comment wrt why this ticket was closed? So in the future we don't end up guessing...


Legacy timers should check for presence in global before adding an immediate

Following up #11511:
🐛 Bug Report
With this:
test('foo', () => {
  jest.useFakeTimers('legacy');
  setImmediate(() => {});
});

I get:
=> TypeError: this._timerAPIs.setImmediate is not a function
We're with the jsdom environment.

Got this too after upgrading to v27. I'm not sure why. Adding the following to jestSetup stops it happening:
global.setImmediate = global.setTimeout;

more direct references from the bug:
https://github.com/facebook/jest/issues/11511#issuecomment-855883827
https://github.com/facebook/jest/issues/11511#issuecomment-855946609

Still seeing this with jest 27.0.6

Here's my workaround:
// jest.config.js
export default {
  globals: {
    setImmediate: global.setImmediate
  }
}


[ioredis] Unhandled error event: ParserError: Protocol error, got "\r" as reply type byte. Please report this.

Hi, using current version, I have this error, don't know why?
[ioredis] Unhandled error event: ParserError: Protocol error, got "\r" as reply type byte         at handleError (/.../node_modules/redis-parser/lib/parser.js:190:15)         at parseType (/.../node_modules/redis-parser/lib/parser.js:304:14)

Did you ever discover the cause?

Hey @MariusMez 👋
In my experience, most of the time this error is due to some proxies or customized Redis servers. could this be your cause?

Hi @luin thank you for your answer, I have a standard install on my mac using homebrew.
I don't know why this error occurs, but seems solved for now (maybe an update of redis solve this, current version installed : 7.0.3).
I can close the issue, thanks


Add sensor_locations

Codecov Report

Merging #19 (51acfbd) into develop (51acfbd) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 51acfbd differs from pull request most recent head f635cdc. Consider uploading reports for the commit f635cdc to get more accurate results

@@           Coverage Diff            @@
##           develop      #19   +/-   ##
========================================
  Coverage    86.97%   86.97%
========================================
  Files           20       20
  Lines         1589     1589
========================================
  Hits          1382     1382
  Misses         207      207

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


[openvpn] option "block-outside-dns" as checkbox wanted

Hello there.
Since there is a DNS Leak in Windows10 with OpenVPN:

https://github.com/ValdikSS/openvpn-fix-dns-leak-plugin

https://community.openvpn.net/openvpn/ticket/605?__cf_chl_jschl_tk__=a6f7e219f2b7eea6fc3ca6b90a4110db5a79564c-1601904949-0-ARrwznt-ux1J9GjbUS8gszDZBI0hn28Dd0jy2ikTJxVf41p3aezfcUpfH25Ej8iSQAZtUu_HJtAeIloJIhyCbk_N7JPQ9WOOO7lXJiGRJu6a4e2xuzHFOzpQlGyO7yy6eHHqaHdg8tlO7J6qBdJ5-bXUeLq1bAb4PP1Cc8QQbgT1e8fJ2OdREtjaSsrA6pO5KmT0GCkXMOAW7xI_wakhhi7q_1biJQ0Fwu7kG9XDkEUB827hH6J7ildMj6KCdsKnuAGyjJ35xiFb-Vs78FSlrCi8AbrOIKG_o3B_NHK95U4n

https://redmine.pfsense.org/issues/6719

it appears that our roadwarrior clients do not use our DNS server,
if they have a faster IPV6 (DNS) address in their cache.
We can fix this by adding:
push "block-outside-dns"
at:
Setting OpenVPN Server > Adv Options > Custom Options
Well this works quiet good, but we try to avoid using this field,
duo to security. Although this field is going to be removed in the future.
So it would be nice to have a checkbox for that command at the server config.
It would be really great, if you could implement that option.
:)
kind regards

@mpl1ma best open a feature request in core (using our template) https://github.com/opnsense/core/issues/new?assignees=&labels=&template=feature_request.md&title=


Add subscribe topic methods

Add subscribe to topic methods using the instance-id server API. See the README new section
TODO -  the rspecs. I will do it if the idea is well received :-)
@sabman, @kashif, @willnet, @yuki24, @takezou621

Any reviewers have a chance to look at this? Looks like a really nice feature to have.


activity-log alert create for Administrative category requires additional conditions

When I try to create an activity-log alert for the Administrative category, I get UnsupportedCondition error. Please document what additional conditions for this category are needed.
$category = "Administrative"
az monitor activity-log alert create -n "$category activity $rg" -g $rg --condition category=$category
Specify additional conditions for this category: Administrative. [Code: "UnsupportedCondition"]

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

ID: 8d2421be-dcd7-4418-9518-e884b7190a96
Version Independent ID: eb40fdf2-0776-bee3-3f8d-5e5f042f2504
Content: az monitor activity-log alert action-group
Content Source: src/command_modules/azure-cli-monitor/azure/cli/command_modules/monitor/_help.py
Service: monitoring-and-diagnostics
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Since this is the error that comes back from the service, they would need to take a look at improving it.
The documentation for activity log alerts is here and may provide some assistance:
https://docs.microsoft.com/en-us/azure/azure-monitor/platform/alerts-activity-log
However, you may find it easiest to create your activity log alert in the portal and then create the CLI equivalent.

Confirming, the error occurs as the rule condition is too broad. As stated in our Activity Log alert document :

#please-close

Apologies for replying to such an old thread.  The warning you've highlighted is no longer present on that page.  Is it still relevant?
I'm troubleshooting this error:
Alert Rule with category 'Administrative' and subscription scope must have at least one additional filtering condition.
Google brought me here, and if I understand correctly it seems we cannot have a rule that matches category = administrative, and any-of operationName = abc, operationName = xyz.   We must create an alert rule for each operation name.
Is that correct?  Should the docs be updated to reflect this limitation?


How to change address in the memory viewer

I'm feeling quite stupid for asking this, but how do you change the address in the memory viewer? I can't figure it out.

You'll want to run the "Go To Address" command. The default keybinding for this is Alt+G. You can write either an actual address, or any expression that the debugger could normally evaluate in e.g. the watch window.
Basically all actions in the debugger like this can be found in the command lister/palette - you can open it up by hitting F1 (by default - you can change this hotkey too).

Thanks.
I think it would make sense to have a dropdown here where you can fill in the memory (such as in vs) it's also useful to have a dropdown if you want to switch between locations (and doesn't want a full new view for it)

This also really confused me. This should be added to the readme since it's such a common task. I expected to be able to right-click a variable (either in the code, or in the watch window) and do "go to memory address" or similar. When that didn't work, I expected to be able to double-click the current address in the memory window and paste a new value.


shared_preferences -- No implementation found for method getAll ...

Steps to Reproduce
I’m having a nightmare with:
package:shared_preferences
and this error …
No implementation found for method getAll on channel plugins.flutter.io/shared_preferences
I’ve read literally 100's of SO answers & github issues trying to solve this and it still fails … I suspect it’s because I’m reading SP too early (I’ve been storing the user auth-token there for auto-login)
if I work around the shared_preferences problem by calling:
SharedPreferences.setMockInitialValues({});
then, another of my plugins (sign_in_with_apple) starts reporting the same error
I’m nearing my wits end … any suggestions??
Does anyone know about problems reading from disk too early in the startup lifecycle??
Would I be better off reading/writing a local file??

[✓] Flutter (Channel beta, 2.0.1, on macOS 11.2 20D64 darwin-arm, locale en)
• Flutter version 2.0.1 at /Users/dgaedcke/flutter
• Framework revision c5a4b4029c (4 days ago), 2021-03-04 09:47:48 -0800
• Engine revision 40441def69
• Dart version 2.12.0
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/dgaedcke/Library/Android/sdk
• Platform android-30, build-tools 30.0.3
• Java binary at: /Applications/Android Studio 4.2 Preview.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
✗ Android license status unknown.
Run flutter doctor --android-licenses to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.4, Build version 12D4e
• CocoaPods version 1.10.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio
• Android Studio at /Applications/Android Studio 4.2 Preview.app/Contents
• 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 11.0.8+10-b944.6916264)
[✓] VS Code (version 1.54.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.20.0
[✓] Connected device (2 available)
• moto g 7 (mobile) • ZY225DPWVL • android-arm64  • Android 9 (API 28)
• Chrome (web)      • chrome     • web-javascript • Google Chrome 88.0.4324.192
! Error: dgiphone is not connected. Xcode will continue when dgiphone is connected. (code -13)

As a Flutter newcomer, not that I would be able to help, but what do you mean, "too early"? Like calling the package's methods in initState vs. didChangeDependencies or elsewhere? Or initializing the package in main() before runApp()? If you recently upgraded Shared Preferences, have you maybe tried downgrading to 0.5.12+4 and see if the issue persists?

Hi @dgaedcke
I see there's an open issue (https://github.com/flutter/flutter/issues/66833) addressing the case you described.
Please follow up on that issue, I'm closing the current one as a duplicate.
Also see https://github.com/flutter/flutter/issues/75416.
If you disagree, please write in the comments and I will reopen it.
Thank you


SymmetricBlock: Harden

Optionally disable mirroring as part of this constraint definition

This is completed and merged to master.


Refactor node pasting into code editor

Follow-up to https://github.com/godotengine/godot/pull/81708
Refactors the logic for pasting nodes to remove duplicated code, bring it in-line with the resource dropping, and account for empty lines.

Closing for now because I realized it needs rebasing with https://github.com/godotengine/godot/pull/81708


Why don't use ADA in this implementation?

I tried both diffaug and ADA in other stylegan2 model, and the performance when using ADA was better.
Do you think it's better to use fastgan than to use ADA due to lack of data?
Or because of the following problems?
https://github.com/lucidrains/stylegan2-pytorch/issues/223#issuecomment-922794046
https://github.com/NVlabs/stylegan2-ada-pytorch/issues/175#issue-989112485

You can also use ADA with FastGAN if you wanted to. But, we tried both, and usually, diffaug would return slightly better results.
So the standard setting is: PG + diffaug + FastGAN/StyleGAN2 generator

WOW! speed answer! thanks 👍


Migrate from ignition to gz

Precisely what the title says. Ignition is now Gazebosim, and we need to accomodate changes.

This only migrates namespaces in C++ API and Protobuf messages, enough to get it building with latest Garden. Shall we move forward with the rest now? Ie. replace the ignition term for gz everywhere.

CI will fail until we've migrated the LRAUV controller codebase (and update our Docker image).


Removing blog post per ContribEx and Docs

SIG Docs co-chairs, SIG ContribEx co-chairs, and SIG ContribEx Comms Leads determined this blog post, to a large extent, includes AI-generated text by a large-scale language model (LLM). As is the policy for Kubernetes localization teams across the project, AI-generated text must include substantial human adaptations, changes, and review.
Co-chairs of SIG Docs, SIG ContribEx, and ContribEx Comms Suproject Leads have used the external tool CopyLeaks to verify the substantial presence of AI-generated text in this post. As a result, it will be removed from the Kubernetes blog and Contributor Site.

See https://github.com/kubernetes/contributor-site/pull/504

If we want a custom “article deleted” page, we can serve one. See https://github.com/kubernetes/website/pull/46323 for a hint about how to do that.

/hold
/approve
/lgtm
OK to unhold once the other removal PR has LGTM and approval.

/hold cancel

LGTM from me!

@sftim As much as I would love to implement this, wouldn't it be simpler to have a Content Removed 404 page that we can redirect/alias off to? There's a strong desire to take these posts down sooner rather than later. Also, I would like to see this process documented.

As much as I would love to implement this, wouldn't it be simpler to have a Content Removed 404 page that we can redirect/alias off to? There's a strong desire to take these posts down sooner rather than later. Also, I would like to see this process documented.

Best discussed elsewhere I think. I wrote the suggestion before I knew the context for the removal.


methods cannot be composed in testes

edit: code in the results branch
I'm trying to write the result operator such that the following test works
as you might expect:
  block:
    ## assignment shim with constant
    r = 0
    proc bar(a: int): int {.cps: Cont.} =
      inc r
      noop()
      return a * 2

    proc foo() {.cps: Cont.} =
      inc r
      let x = ... bar(4)  # ie. resolve the continuation
      inc r
      check x == 8

    trampoline foo()
    check r == 3

The ... should resolve the result stashed in the continuation into x.
I get the following error message because my output (a statement list)
does not allow me to raise the method definition to top level. I don't
expect a statement list to be a level, per se, and I don't know how a
macro could ever return more than a single method unless this limit
is lifted.
/home/adavidoff/git/cps/tests/taste.nim(48, 1) template/generic instantiation of `testes` from here
/home/adavidoff/git/cps/tests/taste.nim(539, 31) template/generic instantiation of `cps` from here
/home/adavidoff/git/cps/cps/environment.nim(214, 16) Error: 'method' is only allowed at top level

For clarity, here's a tree dump of the before/after AST.
=== .cps. on bar(original)  === /home/adavidoff/git/cps/tests/taste.nim(539, 6)
ProcDef
  Sym "bar"
  Empty
  Empty
  FormalParams
    Sym "int"
    IdentDefs
      Sym "a"
      Sym "int"
      Empty
  Empty
  Empty
  StmtList
    Command
      Sym "inc"
      Sym "r"
      IntLit 1
    Call
      Sym "noop"
    ReturnStmt
      Asgn
        Sym "result"
        Infix
          Sym "*"
          Sym "a"
          IntLit 2
  Sym "result"
nnkIdentDefs	a: int
storing type env_402657855
next type env_402657858
=== .cps. on bar(transform) === /home/adavidoff/git/cps/tests/taste.nim(539, 6)
StmtList
  MethodDef
    AccQuoted
      Ident "..."
    Empty
    Empty
    FormalParams
      Ident "int"
      IdentDefs
        Ident "continuation"
        Ident "env_402657855"
        Empty
    Pragma
      Sym "cpsLift"
    Empty
    DotExpr
      Call
        Ident "env_402657855"
        Ident "continuation"
      Ident "result_402657854"
  TypeSection
    TypeDef
      Ident "env_402657855"
      Empty
      RefTy
        ObjectTy
          Empty
          OfInherit
            Ident "Cont"
          RecList
            IdentDefs
              Ident "result_402657854"
              Ident "int"
              Empty
            IdentDefs
              Ident "a_402657856"
              Ident "int"
              Empty
  ProcDef
    Ident "afterCall_402657857"
    Empty
    Empty
    FormalParams
      Ident "Cont"
      IdentDefs
        Ident "continuation"
        Ident "Cont"
        Empty
    Pragma
      Sym "cpsLift"
    Empty
    Empty
  ProcDef
    Ident "afterCall_402657857"
    Empty
    Empty
    FormalParams
      Ident "Cont"
      IdentDefs
        Ident "continuation"
        Ident "Cont"
        Empty
    Pragma
      Sym "cpsLift"
    Empty
    StmtList
      CommentStmt "saften at 866 of cps.nim"
      StmtList
        Asgn
          DotExpr
            Call
              Ident "env_402657855"
              Ident "continuation"
            Ident "result_402657854"
          Infix
            Ident "*"
            DotExpr
              Call
                Ident "env_402657855"
                Ident "continuation"
              Ident "a_402657856"
            IntLit 2
        ReturnStmt
          Empty
      CommentStmt "omit return call from nnkStmtList"
  ProcDef
    Ident "bar"
    Empty
    Empty
    FormalParams
      Sym "Cont"
      IdentDefs
        Ident "continuation"
        Sym "Cont"
        Empty
    Pragma
      Ident "cpsCall"
    Empty
    StmtList
      CommentStmt "saften at 539 of taste.nim"
      StmtList
        CommentStmt "saften at 540 of taste.nim"
        Command
          Ident "inc"
          Ident "r"
          IntLit 1
        StmtList
          CommentStmt "re-use the local continuation by setting the fn"
          Asgn
            DotExpr
              Ident "continuation"
              Ident "fn"
            Ident "afterCall_402657857"
          ReturnStmt
            Call
              Ident "noop"
              Ident "continuation"
      CommentStmt "omit return call from nnkStmtList"
  ProcDef
    Ident "bar"
    Empty
    Empty
    FormalParams
      Ident "Cont"
      IdentDefs
        Ident "a"
        Ident "int"
        Empty
    Empty
    Empty
    StmtList
      Asgn
        Ident "result"
        ObjConstr
          Ident "env_402657855"
          ExprColonExpr
            Ident "fn"
            Ident "bar"
          ExprColonExpr
            Ident "a_402657856"
            Ident "a"

So, yeah, it works if you're not a nimpleton who's trying to write tests using a unittest framework that might move methods out of toplevel because, what the fuck, why not?

So, yeah, it works if you're not a nimpleton who's trying to write tests using a unittest framework that might move methods out of toplevel because, what the fuck, why not?


describe the testing environement

[x] 1. Development Environment: A local environment for developers to run unit tests and perform integration testing using their preferred tools and libraries. README
[ ] 2. Staging Environment: An isolated, pre-production environment where system tests, performance tests, security tests, and UATs can be conducted before deploying the application to production. This will allow any issues or bugs to be resolved without impacting live users. #19
[ ] 3. Production Environment: The actual cloud service running in a live environment with real users accessing the software. requires #1

required in #26
Docs:
https://medium.com/@alexeusgr/devex-testing-plan-cb81d193dba8
https://medium.com/p/d89010c420c7/edit?source=your_stories_page-------------------------------------

write a systems testing plan for a cloud service in Rust.
Introduction
This document outlines the system testing plan for a cloud-based application developed using Rust. The primary focus of this plan is to ensure that the software meets its intended functionality, is scalable, and maintains high levels of maintainability throughout its development lifecycle. This will be achieved through comprehensive testing strategies, including unit tests, integration tests, system tests, performance tests, security tests, and user acceptance tests (UAT).
Objectives

Ensure the software meets its intended functionality and requirements.
Verify that the application is scalable to accommodate future growth in users, data, and resources.
Confirm that the codebase is maintainable for developers throughout the development lifecycle.
Identify any potential performance bottlenecks or security vulnerabilities.
Validate user acceptance of the software through UATs.
Test Strategy
Unit Tests: Develop and execute unit tests to ensure individual components, modules, and functions work as intended. This will be done using Rust's built-in testing framework, cargo test.
Integration Tests: Combine multiple units into larger subsystems for end-to-end verification of functionality. These tests will focus on verifying the interaction between different components within the system and ensuring that they work together seamlessly.
System Tests: Test the entire application as a whole, including all its features and functionalities. This will involve simulating real-world scenarios to ensure the software performs as expected under various conditions.
Performance Tests: Measure the performance of the cloud service by testing its response time, throughput, and resource utilization under different workloads. This will help identify any bottlenecks or optimizations needed for scalability.
Security Tests: Perform security tests to ensure that the application is protected against potential threats such as unauthorized access, data breaches, and denial of service attacks.
User Acceptance Tests (UAT): Conduct UATs with real users to gather feedback on usability, user experience, and overall satisfaction with the software. This will help identify any issues that may have been missed during development and ensure that the application meets end-user expectations.
Test Environment
Development Environment: A local environment for developers to run unit tests and perform integration testing using their preferred tools and libraries.
Staging Environment: An isolated, pre-production environment where system tests, performance tests, security tests, and UATs can be conducted before deploying the application to production. This will allow any issues or bugs to be resolved without impacting live users.
Production Environment: The actual cloud service running in a live environment with real users accessing the software.
Test Schedule
Unit Tests: Concurrently with development, ensuring that all new code is covered by unit tests before being merged into the main branch.
Integration and System Tests: After completing major features or milestones, integrate components for end-to-end testing to ensure proper functionality.
Performance and Security Tests: Periodically throughout the development process, as well as after significant changes are made to the application.
User Acceptance Testing: Conduct UATs with real users at regular intervals during the development lifecycle to gather feedback and make necessary improvements.
Test Reporting and Monitoring
Automated Reports: Use continuous integration tools, such as GitLab CI/CD or Travis CI, to generate automated test reports for each commit, pull request, and deployment. This will help developers identify issues early in the development process.
Manual Test Results: Document UAT results and user feedback in a centralized location for easy access by all team members.
Monitoring Dashboard: Create a dashboard to track performance metrics, security alerts, and test coverage over time to ensure that the application remains scalable and maintainable throughout its development lifecycle.
Conclusion
This testing plan outlines a comprehensive approach for ensuring the quality of a cloud service developed in Rust. By focusing on scalability and maintainability, this plan will help deliver an efficient, reliable, and user-friendly software solution that meets end-user expectations.

Prompt: write testing plan for system tests for a cloud service in Rust

Test Objectives

Verify that all functionalities are working as expected.
Identify any performance issues or bottlenecks in the system.
Ensure compatibility with different operating systems, browsers, and devices.
Test for security vulnerabilities and ensure data privacy.

Test Scope

Functional testing: Verify that all functionalities of the cloud service are working as expected. This includes both positive and negative test cases to cover edge cases and error handling scenarios.
Performance testing: Measure the system's performance under different loads, such as high concurrency or large data sets. Identify any bottlenecks or areas for optimization.
Compatibility testing: Test that the cloud service works on various operating systems (Windows, macOS, Linux), browsers (Chrome, Firefox, Safari), and devices (desktops, laptops, mobile phones).
Security testing: Perform penetration tests to identify any potential security vulnerabilities. Ensure data privacy by verifying that sensitive information is properly encrypted and stored securely.

Test Environment

Set up a test environment with the same infrastructure as the production environment, including the cloud provider (e.g., AWS, Google Cloud), operating systems, browsers, and devices.
Use tools like Docker for isolation and reproducibility of tests across different environments.

Test Strategy

Use a combination of manual and automated testing to cover all aspects of the system. Automated tests can be written using Rust's test framework or third-party libraries, while manual testing is useful for exploratory testing and edge cases.
Prioritize critical functionalities and high-risk areas (e.g., security) for thorough testing.

Test Deliverables

Test plans: Document the objectives, scope, environment, strategy, and deliverables of each test phase.
Test cases: Write detailed steps to reproduce specific scenarios or edge cases.
Test scripts (if applicable): Automated tests written in Rust's test framework or other languages like Python for browser-based testing.
Defect reports: Document any issues found during testing, including steps to reproduce and potential solutions.

Test Schedule

Break down the testing process into phases (e.g., unit tests, integration tests, system tests) with clear milestones and deadlines.
Allocate sufficient time for each phase based on its complexity and risk level.

Test Risks

Identify potential risks that could impact the testing process or results (e.g., unstable infrastructure, incomplete test coverage). Develop mitigation strategies to address these risks.

Communication Plan

Keep all stakeholders informed about the progress and results of the system tests through regular meetings, reports, and updates on the project management tool (e.g., Jira, Trello).

Review and Retesting

Review the test results to ensure that all issues have been addressed before moving forward with deployment. If necessary, retest affected areas or perform additional tests based on feedback from stakeholders or new requirements.

https://medium.com/p/d89010c420c7/edit?source=your_stories_page-------------------------------------

[ ] An option to generate a highly opiniated axum web application stack.

https://github.com/fission-codes/rust-template/tree/main/.github

[ ] https://github.com/aleeusgr/efected-coto-emmory/tree/efected-cotoemory/src
[ ] https://github.com/aleeusgr/efected-coto-emmory/tree/efected-cotoemory/benches
[ ] https://github.com/aleeusgr/efected-coto-emmory/tree/efected-cotoemory/tests

Imports diagram

Develop testing environment.
for #22 I need to perform a test that will relate somehow to the deliverables we are testing in #26
Functionality, Performance, Stability.
The goal of the new environment is to model the functionality of the service: to work with video feeds.
Primaries:

[ ] https://www.reddit.com/r/rust/comments/vvrmaw/video_axum_development_live_stream_recordings_web/
[ ] https://lib.rs/crates/axum-streams
[ ] https://users.rust-lang.org/t/axum-streaming-data-to-multiple-http-clients-with-bounded-memory-usage/94668

Alternatives:

[ ] https://lib.rs/crates/camera_capture
[ ] https://github.com/Zacchaeus-Oluwole/RUST-PROJECTS/tree/main/real-time_webcam_streaming_server/rcvweb
[ ] https://www.sea-ql.org/SeaStreamer/
[ ] https://users.rust-lang.org/t/rtmp-live-streaming-in-rust/16869

In the latest version the testing environment is a real time streaming service using axum

https://carlosmv.hashnode.dev/getting-started-with-axum-rust


Point memory leak

SWIG says:
swig/python detected a memory leak of type 'gip::Point< double > *', no destructor found.

This should be remedied by adding %template(Pointd) gip::Point< double >; to gippy/core.i.
Testing.

Fixed: d8320be


Add git merge rule

This should fix #629.

The tests are failing because each rule is required to be listed in the README, so you just need to add it right after git_help_aliased.


Autcmd "format on save" gives error with :wq

I'm using the autocmd you suggest to format on save:
vim.api.nvim_exec([[
augroup FormatAutogroup
  autocmd!
  autocmd BufWritePost *.js,*.rs,*.lua FormatWrite
augroup END
]], true)

When I use :wq I always get this error when I'm back on my terminal:
Formatter: Buffer changed while formatting, not applying formatting
When I use just :w I get that same error the 1st time, but if I repeat the command then it works without complaining.
Any idea why this could be happening? Thanks!

You can't use :wq. Because formatting is done asynchronously, Neovim will already be closed by the time the formatting results come back.
This could be fixed with something like #109, but it is not currently possible.
That you get Formatter: Buffer changed while formatting, not applying formatting with just :w probably means that something else is also formatting the buffer on write.

OK then. Thanks for the explanation anyway!


Question about DDIM loss

Hi, thanks for your wonderful work!
When I was reading the code, I noticed that you took the time embedding on the feature extracted from the RGB images. I am wondering if it is better to take the time embedding on the depth output by the decoder (namely 'refined_depth' defined in your code), or just annotated depth with masks.
Thanks for your work and codes again!

Hi, thanks for your question.
At that time our thinking is more like to add the time embedding on a dense and consistent feature. This way is closer to the original diffusion model. I haven't try to put time embedding directly on depth map.
Have you got any attempts on that? If the results are positive, I'm keen to have a improved version with you.


generated cst_encode_list_Uuid has compile error

Describe the bug
In generated frb_generated.io.dart, the function
  @protected
  ffi.Pointer<wire_cst_list_Uuid> cst_encode_list_Uuid(List<UuidValue> raw) {
    // Codec=Cst (C-struct based), see doc to use other codecs
    final ans = wire.cst_new_list_Uuid(raw.length);
    for (var i = 0; i < raw.length; ++i) {
      ans.ref.ptr[i] = cst_encode_Uuid(raw[i]);
    }
    return ans;
  }

has the following compile error:
A value of type 'Pointer<wire_cst_list_prim_u_8_strict>' can't be assigned to a variable of type 'wire_cst_list_prim_u_8_strict'.
Try changing the type of the variable, or casting the right-hand type to 'wire_cst_list_prim_u_8_strict'.

Steps to reproduce
Use the uuid feature, have some data and functions with Uuid, and run flutter_rust_bridge_codegen generate
Logs
N/A

Expected behavior
No response
Generated binding code
No response
OS
No response
Version of flutter_rust_bridge_codegen
Generated by flutter_rust_bridge@ 2.0.0-dev.24.
Flutter info
Flutter (Channel beta, 3.19.0-0.1.pre, on macOS 14.2.1 23C71 darwin-arm64, locale en-US

Version of clang++
No response
Additional context
No response

Looks like a bug, feel free to PR to fix it! Or, I will fix it in the next batch (hopefully within a week).
It has a workaround: If you set full_dep: false, it will use SSE codec by default, which does not have this issue (which is CST-codec-only).

Thanks for the workaround!


Contribute back to FreeOTP

Hey @helloworld1,
can you contribute those features back to https://github.com/freeotp/freeotp-android?

There is a reason export feature is not part of most OTP apps. Allowing export allows anyone you borrow your phone to for a few minutes to copy your tokens without you even knowing. Not allowing export was a conscious decision and that is why this can't pushed to Free OTP. Also this app should really warn users about the security tradeoff this feature has.

Yes, it is true, I think this does make the security worse that a person could export and view all the 2FA secrets without rooting your phone if he gain access to the phone.
Well, it is a trade off for convenience especially for those who frequently changes phone and have a lot of 2FA code to migrate.
Probably I can add a PIN lock screen and also fingerprint access to the app. The PIN can also be used to encrypt all the credentials.

@helloworld1IMO this is a great idea. A fingerprint lock does not lessen convenience much, but keeps the casual attacker away 🙂

Probably I can add a PIN lock screen and also fingerprint access to the app. The PIN can also be used to encrypt all the credentials.

Make this a priority pretty please 😄


Remove extra code and correct syntax

Please provide some more context what you have done!

when i open the project in  remote system then in src/Components/Footer/index.js have the extra code and there is no gape between the year and all right reserved so I added the gape.


SHA that appears on published pages does not exist in /wptd/testruns-index.json

As show in:

This: e511e5e8af is not present in https://storage.googleapis.com/wptd/testruns-index.json

Re: https://github.com/GoogleChrome/wptdashboard/issues/73#issuecomment-320740030, there's nothing that regularly updates the index yet.

I just ran the script again so today's results should be in there. Until #73 is resolved, though, it won't be updated regularly.

Sorry, I should've closed it yesterday when I read that ticket—this is a duplicate


Cluster custom data

How do I cluster custom data like
use linfa::traits::Transformer;
use linfa_clustering::Dbscan;

struct Face {
    id: i64,
    vector: [f32; 128],
}

impl Face {
    fn distance(a: &Self, b: &Self) -> f32 {
        let mut r = 0.0;

        for (a, b) in a.vector.iter().zip(b.vector.iter()) {
            let c = a - b;
            r += c * c;
        }

        r.sqrt()
    }
}

fn main() {
    let faces = vec![
        Face { id: 1, vector: [0.1; 128] },
        Face { id: 2, vector: [0.2; 128] },
        Face { id: 9, vector: [0.9; 128] },
    ];

    let clusters = Dbscan::params(3)
        .tolerance(0.6)
        .transform(&faces);
}

good question, you can achieve that by prior transforming your faces to a similarity matrix (see Array2::from_shape_fn):
let similarity_faces = Array2::from_shape_fn((faces.len(), faces.len()),
    |dims| Face::distance(faces[dims[0]], faces[dims[1]]));

@bytesnake could you please tell more about shape (faces.len(), faces.len()) what is it?

yes the shape (faces.len(), faces.len()) is a tuple for a quadratic matrix, which defines the distance of each face, see also https://en.wikipedia.org/wiki/Distance_matrix


discriminator loss goes to infinity

Hi,
I'm trying to train the cvivit on a set of 10000 images. The vae-loss keeps going down, but the discriminator loss keeps rising infinity. It's easy to fool :)
Any idea what the problem is?

hmm maybe 10k images is not enough
are you doing any augmentations?

No augmentations.

Check the gradients and output values at every step of the way to see where it starts to go wrong.

Thanks. It starts to jump dramatically already at step 500.

@065294847 what is your batch size and learning rate?

Just the defaults, batch size 4, lr 3e-4

Try it with a dataset that's known to work and converge. Just to rule it out.

Thanks, I'll experiment a bit and report back

Thanks, I'll experiment a bit and report back

@065294847 try lowering your learning rate, or increase your effective batch size (either increase batch_size or grad_accum_every)

@065294847 get more data too, 10k is nothing... try 100k or a million

Yes of course, just wanted to do a quick test first :)


Pittsburgh PA Traffic accidents

Someone has requested help on a data project:
Submission notes
Is there any way you can get me traffic accidents by location in Pittsburgh? If I could get a count of accidents in Black and white neighborhoods or areas, I could see if police traffic stops are higher in Black neighborhoods compared to white areas with same traffic accident rate. Higher traffic stop rates for Black would not be justified if driving is no more dangerous in the Black neighborhoods
Location
Pittsburgh Police - PA
Requirements
Traffic accidents
How to help
Leave a comment if you'd like to help. Do you have ideas, questions, or need any more information to get started?

connected with a collaborator for analysis, and shared crash data: https://data.wprdc.org/dataset/allegheny-county-crash-data


Temporarlily fix module problem.

This is a temporary fix for module visibility problem in tests.
Proper solution to be pursued in https://github.com/Azure/azure-sdk-for-java/issues/29245 .

/azp run java - search - tests


lots of HTML parsing errors when combined with Thymleaf

when taking this template to Thymleaf framework (http://www.thymeleaf.org/) then many errors are reported by Thymleaf.
most errors are for not closing tags.
for example
<meta charset="utf-8">
should be
<meta charset="utf-8" />
``` and there are many more.

it would be great if the sb-admin-2 fixed that.

Since you are getting the errors and have the software, it maybe better for you to fix them and submit a pull request. Without being able to reproduce the errors it would be impossible for everyone to fix them all.

I hope i did the "pull request" right, please review #57
I've tested #57 locally, with Spring and Thymleaf. All pages are rendered correctly.


Selected sidebar item doesn't respect theme colors

Describe the bug
Setting theme.color.lightest and theme.color.inverseText doesn't impact the color of selected items in the sidebar (they remain #FFFFFF regardless)
From the sidebar component, it looks like theme.color.lightest should effectively color the component but it it looks like it is overridden by div#accordion--skeleton for some reason.
https://github.com/storybooks/storybook/blob/a28c59592ee5d43152b684958ee83b8fc55adbcd/lib/ui/src/components/sidebar/SidebarItem.js#L73
To Reproduce
Steps to reproduce the behavior:

Update all of the values for colors in a theme to black.
The selected text remains #FFFFFF no matter what

Expected behavior
The selected item should have text according to the theme value that is used in the sidebar item component when selected (theme.color.lightest)
Screenshots
If applicable, add screenshots to help explain your problem.

Code snippets
addParameters({
  options: {
    theme: {
      ...theme,
      color: { ...theme.color, lightest: 'red', inverseText: 'red' },
    },
  },
});

System:

Browser: Firefox
Framework: react
Version: [e.g. 5.0.5]

Additional context
Trying to use a lighter secondary color for the selected items but finding it impossible to change the color of the selected items.

I looked into this issue a bit. As you see in the ThemeVars interface below, theme.color.lightest is not a property you can set.
https://github.com/storybooks/storybook/blob/ed9bcff0d88da47c4f014ea78eb8fcb6458e5821/lib/theming/src/base.ts#L97-L131
The color.lightest is always #FFFFFF because the base theme definition is used for this attribute. I think there are two possible solutions here:

Infer the color.lightest attribute from an already existing ThemeVars attribute.
Create a new attribute in ThemeVars to set the the color.lightest (and maybe other) attributes.

I don't think option 1 is the best solution as it will change the look of the site quite a bit by inferring color.lightest from an already existing ThemeVars attribute.
Is there a particular reason why the underlying theme properties aren't customisable? Or am i totally wrong here by saying that it is not customisable? I get that it is convenient for creating themes that have a consistent style, but the option would be nice.
Since this is my first time fixing an issue for storybook i would like some input before moving forward.

It seems like it should use the inverseText theme property or a new property all together.

When #4169 drops we'll support full custom theme options, including this property.


The message "unexpected token '['' appears in decorator.

Environment data

Language Server version: 0.5.59
OS and version: Windows 10 19042.685
Python version  3.9.1

Expected behaviour
Do not display the message "unexpected token '['.
Code Snippet
The following code reproduces the issue:
def make_decorators():
    def decorator0(func):
        def inner_func0(*args):
            print('decorator 0')
            return func(*args)
        return inner_func0

    def decorator1(func):
        def inner_func1(*args):
            print('decorator 1')
            return func(*args)
        return inner_func1
    return [decorator0, decorator1]

decorators = make_decorators()

@decorators[0]
def hello():
    print('hello')

@decorators[1]
def goodbye():
    print('goodbye')

hello()
goodbye()

(Note that this is a new feature in Python 3.9, see PEP 614.)

(Note that this is a new feature in Python 3.9, see PEP 614.)

The parser for MPLS would need to be updated for 3.9, something I don't know if we have the time to do. Pylance at least supports everything new in 3.9, if you haven't yet tried it.

The parser for MPLS would need to be updated for 3.9, something I don't know if we have the time to do. Pylance at least supports everything new in 3.9, if you haven't yet tried it.

@jakebailey Thank you for your reply. I have switched the language server to Pylance and confirmed that it does not happen .

@jakebailey Thank you for your reply. I have switched the language server to Pylance and confirmed that it does not happen .


IE11 renders flex item height incorrectly, with column direction and 0% flex-basis

In IE11, direction: column, flex item basis 0%, the flex item height seems not automatically stretching along with the content height:
Demo: http://codepen.io/hanhpho/pen/KdPZOa?editors=110
Chrome:

IE11:

If I set flex-basis to auto, IE11 works fine.
It seems a flexbox bug with IE11, anyone ran into the same thing?

I've seen this happen in several situation for IE, though I haven't gotten around to documenting it.
From what I can tell, this happens anytime you set a percentage flex-basis when the flex container's main size is indeterminate (meaning its size is based on the size of content), so it happens a lot for column flex containers, but it also happens for inline flex containers, floated flex containers, and nested flex containers.
The main solution/workaround/advice I have for now is to not use a relative flex-basis value (like a percentage) when the flex container's main size isn't definite.

I found the similar tracking issue here https://github.com/philipwalton/flexbugs/issues/58. Mark this as duplicated should be good :)


Add callback doc

Is this pull request associated with an issue(s)?
This PR is to complete the work in PR 128.
Description
Design documentation on finalize callbacks in the RuntimeView class is added. A simple example on how to set the callbacks is also presented.
TODOs
[X] To test callbacks in downstream repos.

🚀 [bumpr] Bumped! New version:v0.1.22 Changes:v0.1.21...v0.1.22


Middleware should do the right thing with X-Sandstorm-Username

Right now, the middleware correctly creates-and-authenticates a user when it finds the X-Sandstorm-User-Id header. This is great!
It should also (optionally?) set the user.first_name field to X-Sandstorm-Username.
@paulproteus, thoughts?

I think that is an excellent plan. I also think that clobbering the existing request.user.first_name is A-OK.

This is done!


tape.jacobian doesn't work in the TensorFlow interface

The following program:
import tensorflow as tf
import pennylane as qml

dev = qml.device("default.qubit", wires=1)

@qml.qnode(dev, interface="tf")
def circuit(params):
    qml.RX(params[0], wires=0)
    qml.RY(params[1], wires=0)
    return qml.probs(0)

params = tf.Variable([0.1, 1.0])

with tf.GradientTape() as tape:
    res = circuit(params)

print(res)
jacobian = tape.jacobian(res, params)
print("Jacobian (TF):", jacobian)

will result in an exception when calculating the Jacobian, as the tensor used during backpropagation does not have a .numpy() method, which we assume exists within the TensorFlow interface to the QNode:
def grad(grad_output, **tfkwargs):
    """Returns the vector-Jacobian product"""
    # evaluate the Jacobian matrix of the QNode
    variables = tfkwargs.get("variables", None)

    jacobian = qnode.jacobian(args, kwargs)

    # perform the vector-Jacobian product
    if not grad_output_np.shape:
        temp = grad_output_np * jacobian
    else:
        temp = grad_output_np.T @ jacobian

    # restore the nested structure of the input args
    grad_input = unflatten(temp.flat, args)

    if isinstance(grad_input, list):
        grad_input = [tf.convert_to_tensor(i, dtype=dtype) for i in grad_input]
    elif isinstance(grad_input, tuple):
        grad_input = tuple(tf.convert_to_tensor(i, dtype=dtype) for i in grad_input)
    else:
        grad_input = tf.convert_to_tensor(grad_input, dtype=dtype)

    if variables is not None:
        return grad_input, variables

    return grad_input

The solution here is to not convert the grad_output argument to a NumPy array, but rather keep the computation in pure TensorFlow:
def grad(grad_output, **tfkwargs):
    """Returns the vector-Jacobian product"""
    # evaluate the Jacobian matrix of the QNode
    variables = tfkwargs.get("variables", None)
    jacobian = qnode.jacobian(args, kwargs)
    jacobian = tf.constant(jacobian, dtype=dtype)
    grad_input = tf.matmul(tf.transpose(tf.reshape(grad_output, [-1, 1])), jacobian)
    grad_input = tf.reshape(grad_input, [-1])

    if variables is not None:
        return grad_input, variables

    return grad_input

While this allows the Jacobian example to work, as the unflattening is no longer occuring, we cannot support QNode arguments outside of 1D tensors.
One possible solution is to have a TF-specific unflattening function, that avoids any casting to NumPy arrays.

See #612 for an unflattening solution that avoids casting to NumPy arrays.


LANG-1276

Fix issue of buf using nonupdated buffer in StrBuilder replaceImpl
Avoid array OoB error by keeping variable buf consistent with buffer

Coverage increased (+0.02%) to 93.57% when pulling 0dd44493d70188ed6145cdb130537532cbc68522 on andyklimczak:LANG-1276 into e2dbe55d56bd6c1209276050f527d36717e33e1d on apache:master.

Coverage increased (+0.02%) to 93.57% when pulling 0dd44493d70188ed6145cdb130537532cbc68522 on andyklimczak:LANG-1276 into e2dbe55d56bd6c1209276050f527d36717e33e1d on apache:master.

Thanks! :+1:


Position and orientation of end-effector

I'm working with the frank panda robot:
Nb joints = 11 (nq=16,nv=15)
  Joint 0 universe: parent=0
  Joint 1 root_joint: parent=0
  Joint 2 panda_joint1: parent=1
  Joint 3 panda_joint2: parent=2
  Joint 4 panda_joint3: parent=3
  Joint 5 panda_joint4: parent=4
  Joint 6 panda_joint5: parent=5
  Joint 7 panda_joint6: parent=6
  Joint 8 panda_joint7: parent=7
  Joint 9 panda_finger_joint1: parent=8
  Joint 10 panda_finger_joint2: parent=8

When I do:
pin.forwardKinematics(model, data, q)
pin.updateFramePlacements(model,data)

then data.oMf.tolist() contains 25 frames. model.frames[19] corresponds to panda_hand_joint, and model.frames[20] corresponds to panda_hand -- which of these should I look at for the end-effector position? Thanks!

It seems you've added a free-flyer joint to your robot. Is it on purpose?

For control, you should always refer to the parent joint (frame.parent) quantity to get the closest supporting joint.
Is it answering your question?

But model.frames[frame_id].parent for frame_id in [15:20] is 8 -- which of these do I look at?

model.joints[8] corresponds to the supporting joint.

That gives me:
JointModelRZ
  index: 8
  index q: 13
  index v: 12
  nq: 1
  nv: 1

What would the frame_id be? Sorry I'm not following.

What is the name of your end-effector? This is on your side that you should know this information.

Got it, thanks!

Perfect.


Update to xbee quirks to account for changes in zigpy

Changes in zigpy caused these quirks to no longer report status changes of DIO pins and resulted in the following error.
ValueError: too many values to unpack (expected 2)
This corrects the return of the deserialize functions and renames the handle_cluster_general_request to handle_cluster_request.
Tested the reading and writing pin states, did not test the additional serial/event functionality.

I new i missed something...

You may want change https://github.com/dmulcahey/zha-device-handlers/blob/f5fcd55bd3d991388e8bb11207b7814cab2012e8/zhaquirks/xbee/xbee3_io.py#L207 to
hdr.frame_control.is_reply = commands[hdr.command_id][2]

and https://github.com/dmulcahey/zha-device-handlers/blob/f5fcd55bd3d991388e8bb11207b7814cab2012e8/zhaquirks/xbee/xbee3_io.py#L231 to
hdr.frame_control.is_reply = foundation.COMMANDS[hdr.command_id][1]

otherwise looks good to me

Makes sense, I'll update the PR when i return later this week.

@prairiesnpr make sure to run black on the code too

This is funny. I was about to create the same PR when I found this one.
You know, I will do it anyway because I have some more changes to suggest.


It does not change color at the label.

Bootstrap 3
Bootstrap 4

Works fine in the docs: http://v4-alpha.getbootstrap.com/components/forms/#validation
Please post a JS Bin or JS Fiddle instead of a screenshot.

i'm using
gem 'bootstrap', git: 'https://github.com/twbs/bootstrap-rubygem'

Need to see the exact HTML you're using. Please post a JS Bin or JS Fiddle using the CSS from https://github.com/twbs/bootstrap/blob/v4-dev/dist/css/bootstrap.css

https://jsfiddle.net/vx7ufkzc/

It seems your Bootstrap CSS is different from the last V4 CSS.
With the correct one the problem doesn't occure

Bootstrap master
Bootstrap v4-dev

.control-label is gone in Bootstrap v4. Now it's named .form-control-label.
Filed a bug to note this change in the v4 migration docs: #17781


Resolve Conformance Tested Endpoints that show as Untested in APISnoop

Description of the Issue:
PR #89753 Merged a Conformance test for 5 x NamespacedEvent Endpoints.
Issue #86288 and PR #89753 showed that the endpoints will be covered by the proposed test.
It was discovered that the Endpoints are not covered by conformance tests.
Endpoint list:
listCoreV1EventForAllNamespaces
readCoreV1NamespacedEvent
patchCoreV1NamespacedEvent
deleteCoreV1NamespacedEvent
createCoreV1NamespacedEvent
Initial discovery:

The Endpoints showed up in the mock test template query as untested.
The Endpoints was targeted for conformance testing, when it was discovered that they should be cover by PR#89753
The Endpoints was checked against the APISnoop website, where they also showed "Untested" with "No Conformance Tests".

Target outcome for this issue:
Step 1:

[ ] Determine the technical reason why the Endpoints are not shown as conformant in APISnoop in spite of PR #89753 being merged
[ ] Determine how to correct the failure and get the Endpoints to show as conformant
[ ] Assign the task for correction or create an Issue in K/K if it require SIG Architecture intervention

Step 2:

[ ] Determine if this failure mode could affect other Endpoints that have valid conformance tests and still show up as untested
[ ] If applicable, list affected Endpoints and correct the conformance status conflict.

More endpoints was identified the was Promoted to conformance and is not showing as conformance tests in SnoopDB or APISnoop

Meta data update, endpoints does not show up in APISnoop yet.

https://apisnoop.cncf.io/conformance-progress/endpoints/1.20.0?filter=old-covered-by-new

We now shows those missing endpoints! Great work!

We are still missing:
deleteCoreV1CollectionNamespacedEvent
listCoreV1NamespacedEvent

ok, leaving this open.

These two endpoints now show as tested, after increasing the test runs we pull our logs from:

deleteCoreV1CollectionNamespacedEvent
listCoreV1NamespacedEvent

Are we good to close this, @Riaankl ?

I was adding it to my list of this to revisit this week and check.
Thanks for beating me to it.
/close


gnunet: 0.14.0 -> 0.14.1; gnunet-gtk 0.13.1 -> 0.14.0

Motivation for this change
Otherwise gnunet-setup will not pick up plugins. See:
https://git.gnunet.org/gnunet-gtk.git/tree/README?id=5034ca084258d6653b2986b00167c736a9cd93ed#n19
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Sorry for ignoring this. I wasn't pinged, somehow. I'll have a look at it this weekend.

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

1 package failed to build:

gnunet-gtk

ping @fricklerhandwerk

Yep, I’m alive and remember, haven’t gotten to it yet, sorry.

Am 21.03.2021 um 21:17 schrieb Sandro @.***>:

ping @fricklerhandwerk
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@SuperSandro2000 @davidak Weird, I cannot reproduce with nixpkgs-review. Was already surprized there was a failure at all, because it built and ran locally in sandbox mode.

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

1 package marked as broken and skipped:

gnunet-gtk

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

@fricklerhandwerk the PR didn't change since january, but master did. So that might be the reason why it fails now.
Can you rebase and test again?

gnunet upstream seems to have added a dependency to libsodium, therefore configure check failed - it tried to compile the header.

@davidak @SuperSandro2000 All good now?

_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0
       > checking for gnutls... --with-gnutls not specified
       > checking gnutls/abstract.h usability... yes
       > checking gnutls/abstract.h presence... yes
       > checking for gnutls/abstract.h... yes
       > checking for gnutls_pubkey_import in -lgnutls... yes
       > checking for GNUnet core... /nix/store/7nccbpwifxivnjvd26p5p1i1rky92zdf-gnunet-0.14.0
       > checking for GNUnet util library in /nix/store/gal466zyk6zxlrv7c3jwmj5p504dj72v-gnunet-gtk-0.13.1... checking for gnunet/gnunet_util_lib.h... no
       > checking for gnunet/gnunet_conversation_service.h... no
       > configure: error: gnunet-gtk requires GNUnet
       For full logs, run 'nix log /nix/store/0xm6h4jb6jv3hwchchrab9hbc0ac1wgc-gnunet-gtk-0.13.1.drv'.

Oh my, this is so embarrassing. Sorry for wasting your time.  It even disappeared from my development machine, nothing in git reflog either, only the updated commit message is correct. Please check again, for me nixpkgs-review pr 110606 was successful.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110606 run on x86_64-linux 1

2 packages built:

gnunet
gnunet-gtk

@SuperSandro2000 I'll note to do it first thing next time I touch this. Right now I would like this to get merged, as refactoring will be more work for everyone without much immediate benefit.

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

2 packages built:

gnunet
gnunet-gtk


Peer to peer review

You made a great job so far by implementing required functionalities to the project. In addition there might be little changes in:

[ ] You can work on the design to improve it.
[ ] You can mark the completed issues to follow the production progress easier.

Hi @mertkantaroglu ,
Thanks for the feedback. I have made the necessary changes.
Best Regards,
K. Inoulen Shanongba


Link thumbnail displaying Times

This may already be captured in another issue but double checking
https://next.carbondesignsystem.com/assets/components

@jeanservaas I found 8 that need fixed, including breadcrumb. I don't know how we haven't caught and fixed these yet.

@mattrosno the grid svg doesn't have any type in it. This is what I have as "grid.svg"

I've attached all of the svgs here, including grid, just in case
type_outlines.zip


lychee.toml JSON schema

Is there a schema for the lychee.toml config file? I pass config schemas for toml config files to get autocomplete using taplo https://taplo.tamasfe.dev/configuration/directives.html#the-schema-directive

There is not, and I didn't know that was a thing, but I'd be thankful for a pull request to add one.

There is not, and I didn't know that was a thing, but I'd be thankful for a pull request to add one.

I'll happily contribute. Is there an example config file that uses all fields possible?

Hm, the most complete one is probably https://github.com/lycheeverse/lychee/blob/master/fixtures/configs/smoketest.toml.
Would that work?
Alternatively, all the options are here: https://github.com/lycheeverse/lychee/blob/13f4339710d76831d9daf961584d796cee4847d2/lychee-bin/src/options.rs#L152

Perhaps schemars could be used to get this more or less "for free," in that future additions to Config would automatically be added to the schema.

Oh yeah, that's definitely nice. How would we build the schema? We could have a separate build target for that, which would store the schema in a file:
let schema = schema_for!(Config);
println!("{}", serde_json::to_string_pretty(&schema).unwrap());

let mut file = File::create("lycheee-schema.json").expect("Unable to create file");
file.write_all(json_output.as_bytes()).expect("Unable to write data");

Ideally, we would do that automatically during the build process, to avoid that the schema runs out of sync with the code. Not sure if we could do that with a build.rs, but it gets hairy because we'd have to use include! to get access to the types from the build.rs. Any other ideas?

Sadly I know less about rust than schema!
A test-driven might be:

add a lychee --schema that prints it out
add a test that compares the file-at-rest to the generated file

if it fails, encourage a developer to refresh it

Another test could verify that everything has the amount of docs that would be useful to a user, e.g. everything has a description, all strings have at least an format, enum, pattern or example.
Again from a user perspective, it's pretty important that the versioned file ends up somewhere publicly hosted and versioned, but https://raw.githubusercontent.com/lycheeverse/lychee/v0.15.1/docs/schema.json isn't the worst.

Alternatively, you could add a hidden (or not) subcommand to the CLI to print out the schema, and then call that in your documentation site build or release process.
If you don't want to add such infrastructure, I think the @bollwyvl's test approach is pretty good.
Oh, or you could do schema-first, generating Rust code for the schema. Or maybe that would be a lossy refactor; I'm not familiar with the code.


Replace DOM events w/ new global Raven events

The DOM events weren't compatible w/ React Native (no document).
This PR is against 3.x since this is a breaking API change.

Closing because against wrong branch.


set up node.js and typescript

Have Yarn, Node.js and Typescript set up for the repository

This change is

Reviewed 7 of 7 files at r1, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @billyao021031)

.editorconfig line 0 at r1 (raw file): Was this created from yarn init?

I think we could remove it as it does not affect anything else other than IDE formatting.
package.json line 2 at r1 (raw file):

{
  "name": "minerva-rewrite",

This might be jumping the gun a bit but it might be good to set up a build script so we can transpile our TypeScript using yarn build
Suggestion:
  "name": "minerva-rewrite",
  "scripts": {
    "build": "tsc -p ."
  },
  "packageManager"<EMAIL_ADDRESS>


[Feature Request] Implementation of mip-splatting rasterizer

Thank you for providing the supersplat tool! It's been very helpful.
I have a question regarding future development plans: Do you have any plans to implement a mip-splatting rasterizer, similar to the modifications made to the original Gaussian Splatting renderer?
If you're open to contributions from the open-source community to help with this implementation, could you please provide some guidance on which parts of the code would need to be modified to achieve an effect similar to the diff-gaussian-rasterization forward in Gaussian Splatting?
Thank you for your time and consideration!

Hi @walsvid ,
We will implement GS rendering using compute shaders at some point in the future (we currently only use vertex and fragment shaders) at which point we could consider adding mip-splatting.
This probably won't happen in the near future though.
Thanks!

Thank you for your reply, and look forward to seeing SuperSplat add this feature in the future. I'll close this issue for now.


api: extension-api-client throws Error invoking remote method error if returned HTTP code is not StatusOK

After so loooooooooooong time of debugging, I finally figured it out why I'm getting the following error:
Uncaught (in promise) Error: Error invoking remote method 'furkan_hello-docker-extension-backend-request': [object Object]

That's because I was returning http.StatusInternalServerError. But... @docker/extension-api-client only works as expected in cases we return http.StatusOK.
Works:
func hello(ctx echo.Context) error {
	return ctx.JSON(http.StatusOK, HTTPMessageBody{Message: "hello"})
}

Does not works:
func hello(ctx echo.Context) error {
	return ctx.JSON(http.StatusInternalServerError, HTTPMessageBody{Message: "hello"})
}

My expected case is that extension-api-client should successfully handle all request/response regardless of the HTTP status code.
Versions:
Extensions SDK
Client Version: v0.2.4
Server API Version: 0.2.3

Docker Desktop
Version: 4.8.2 (79419) (macOS Intel)
Engine: 20.10.14
Compose: 1.29.2
Credential Helper: v0.6.4
Kubernetes: v1.24.0
Snyk: v1.827.0

Sorry, forgot to add an example function of the SDK:
const result = await ddClient.extension.vm.service.get('/hello');

Return a non-200 response:
func hello(ctx echo.Context) error {
	return ctx.JSON(http.StatusInternalServerError, HTTPMessageBody{Message: "hello"})
}

Expect the same error.

I managed to reproduce thanks @Dentrax

@Dentrax a fix for that will be available in 4.10.0 that is around the corner ;)

This has been shipped now, closing this (feel free to re-open if there are still issues getting the error)


Human Action Recognition

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : Human Action Recognition
:red_circle: Aim : Create a DL model which will identify the actions made by the humans.
:red_circle: Dataset : https://www.kaggle.com/datasets/meetnagadia/human-action-recognition-har-dataset
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Email ID :
Participant ID (if applicable):
Approach for this Project :
What is your participant role? (Mention the Open Source program)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Name: Siddhi Mankar
Github link:- https://github.com/sid6602
Email Id<EMAIL_ADDRESS>Approach: To detect different actions of human being
role: contributor

@sid6602 Issue assigned to you. Try experimenting with different dl algorithms. See what gives a better result.

Thank you @sankalp-srivastava

@sid6602 updates please.

Hello @abhisheks008, I am working on this issue. Will update you as soon an algorithms will be ready. Sorry for inconvenience.

Updates please @sid6602

@abhisheks008 Pull Request created.

Full name : Khushi Agarwal
GitHub Profile Link : https://github.com/Khushi771
Email ID<EMAIL_ADDRESS>Approach for this Project :  Create a model which will identify the actions with good accuracy.
What is your participant role? Contributor

Issue assigned to you @achrekarom12


Cannot JSON.parse response - goes over Node heap size

Two recent high level advisories - mixin-deep and set-value blocked my CI even though I am running audit-ci --critical. The issue being that it fail on memory while trying to parse a huge JSON output containing each and every path where these two are dependencies, basically reaching a default Node heap size of ~1.4M.
Output starting with:
$ yarn run audit
yarn run v1.13.0
$ audit-ci --critical
Yarn audit report summary:
ERROR: Cannot JSON.parse response:
{"type":"auditAdvisory","data":{"resolution":{"id":1012,"path":"jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>jest-util>@jest/fake-timers>jest-message-util>micromatch>extglob>snapdragon>base>cache-base>set-value","dev":false,"optional":false,"bundled":false},"advisory":{"findings":[{"version":"2.0.0","paths":["awesome-typescript-loader>micromatch>braces>snapdragon>base>cache-base>set-value","awesome-typescript-loader>micromatch>extglob>expand-brackets>snapdragon>base>cache-base>set-value","awesome-typescript-loader>micromatch>
...

...and ending with:
ERROR: Cannot JSON.parse response:
<--- Last few GCs --->
ERROR: Cannot JSON.parse response:
[19713:0x40f5e30]    10373 ms: Mark-sweep 1396.4 (1439.9) -> 1396.4 (1439.9) MB, 100.2 / 0.0 ms  (+ 27.5 ms in 2 steps since start of marking, biggest step 21.4 ms, walltime since start of marking 128 ms) (average mu = 0.116, current mu = 0.003) allocatio[19713:0x40f5e30]    10498 ms: Mark-sweep 1396.4 (1439.9) -> 1396.4 (1439.9) MB, 125.5 / 0.0 ms  (average mu = 0.065, current mu = 0.001) allocation failure scavenge might not succeed
Unexpected end of JSON input
Exiting...
ERROR: Cannot JSON.parse response:
<--- JS stacktrace --->
ERROR: Cannot JSON.parse response:
Cannot get stack trace in GC.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: Job failed: exit status 1

This issue is also crippling our builds:
❯ yarn audit-ci -m
yarn run v1.15.2
$ /Users/mario/Projects/Fractal/fangtooth/node_modules/.bin/audit-ci -m
Yarn audit report results:
ERROR: Cannot JSON.parse response:
{"type":"auditAdvisory","data":{"resolution":{"id":1012,"path":"jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/fake-timers>jest-message-util>micromatch>braces>snapdragon>base>cache-base>set-value","dev":false,"optional":false,"bundled":false},"advisory":{"findings":[{"version":"2.0.0","paths":["jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/fake-timers>jest-message-util>micromatch>braces>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/fake-timers>jest-message-util>micromatch>extglob>expand-brackets>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/fake-timers>jest-message-util>micromatch>extglob>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/fake-timers>jest-message-util>micromatch>nanomatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/fake-timers>jest-message-util>micromatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>anymatch>micromatch>braces>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>anymatch>micromatch>extglob>expand-brackets>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>anymatch>micromatch>extglob>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>anymatch>micromatch>nanomatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>anymatch>micromatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>jest-util>@jest/fake-timers>jest-message-util>micromatch>braces>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>jest-util>@jest/fake-timers>jest-message-util>micromatch>extglob>expand-brackets>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>jest-util>@jest/fake-timers>jest-message-util>micromatch>extglob>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>jest-util>@jest/fake-timers>jest-message-util>micromatch>nanomatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>jest-util>@jest/fake-timers>jest-message-util>micromatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>micromatch>braces>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>micromatch>extglob>expand-brackets>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>micromatch>extglob>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>micromatch>nanomatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>micromatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>sane>anymatch>micromatch>braces>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>sane>anymatch>micromatch>extglob>expand-brackets>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>sane>anymatch>micromatch>extglob>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>sane>anymatch>micromatch>nanomatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>sane>anymatch>micromatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>sane>micromatch>braces>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>sane>micromatch>extglob>expand-brackets>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>sane>micromatch>extglob>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>sane>micromatch>nanomatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-haste-map>sane>micromatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-util>@jest/fake-timers>jest-message-util>micromatch>braces>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-util>@jest/fake-timers>jest-message-util>micromatch>extglob>expand-brackets>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-util>@jest/fake-timers>jest-message-util>micromatch>extglob>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-util>@jest/fake-timers>jest-message-util>micromatch>nanomatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>jest-util>@jest/fake-timers>jest-message-util>micromatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>micromatch>braces>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>micromatch>extglob>expand-brackets>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>micromatch>extglob>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>micromatch>nanomatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/environment>@jest/transform>micromatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/transform>jest-haste-map>anymatch>micromatch>braces>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/transform>jest-haste-map>anymatch>micromatch>extglob>expand-brackets>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/transform>jest-haste-map>anymatch>micromatch>extglob>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/transform>jest-haste-map>anymatch>micromatch>nanomatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/transform>jest-haste-map>anymatch>micromatch>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/transform>jest-haste-map>jest-util>@jest/fake-timers>jest-message-util>micromatch>braces>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/transform>jest-haste-map>jest-util>@jest/fake-timers>jest-message-util>micromatch>extglob>expand-brackets>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/transform>jest-haste-map>jest-util>@jest/fake-timers>jest-message-util>micromatch>extglob>snapdragon>base>cache-base>set-value","jest>jest-cli>@jest/core>@jest/reporters>@jest/transform>jest-haste-map>jest-util>@jest/fake-timers>jest-message-util>micromatch>nanomatch>snapdragon>base>cache-bas
ERROR: Cannot JSON.parse response:
<--- Last few GCs --->
ERROR: Cannot JSON.parse response:
ze[73584:0x103800000]    10000 ms: Mark-sweep 1389.0 (1436.8) -> 1389.0 (1438.3) MB, 63.1 / 0.0 ms  (+ 16.7 ms in 5 steps since start of marking, biggest step 16.1 ms, walltime since start of marking 81 ms) (average mu = 0.183, current mu = 0.086) finalize [73584:0x103800000]    10077 ms: Mark-sweep 1390.5 (1438.3) -> 1390.4 (1436.3) MB, 56.8 / 0.0 ms  (+ 14.3 ms in 5 steps since start of marking, biggest step 12.9 ms, walltime since start of marking 72 ms) (average mu = 0.142, current mu = 0.093) finalize
ERROR: Cannot JSON.parse response:
<--- JS stacktrace --->
ERROR: Cannot JSON.parse response:
==== JS stack trace =========================================
ERROR: Cannot JSON.parse response:
Security context: 0x3cab1a49e6e9 <JSObject>
ERROR: Cannot JSON.parse response:
    0: builtin exit frame: stringify(this=0x3cab882839c1 <Object map = 0x3cabb60fe641>,0x3cabcee026f1 <undefined>,0x3cabcee026f1 <undefined>,0x3cabff307c79 <Object map = 0x3cabf7b32771>,0x3cab882839c1 <Object map = 0x3cabb60fe641>)
ERROR: Cannot JSON.parse response:
    1: arguments adaptor frame: 1->3
ERROR: Cannot JSON.parse response:
    2: stringify [0x3cab196b9ee9] [/usr/local/Cellar/yarn/1.15.2/libexec/lib/cli.js:~103993] [pc=0x1119c8e59e5c](this=0x3cabc3f9...
Unexpected end of JSON input
Exiting...
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

We're also getting failing builds due to the truncated JSON response.

Might be the real issue: https://github.com/facebook/jest/issues/8682

Fixed with release #100, v2.2.0 is released.


Bug: Unnecessary permissions

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
The bug is that the Deployment kubewarden-controller in the charts has too much RBAC permission than it needs. The service account of kubewarden-controller is bound to a role (rbac.yaml#L46) with the following permissions:

update verb of the deployments resource (Role)
list verb of the secrets resource (Role)
ptach verb of the services resource (Role)

After reading the source code of kubewarden-controller, I didn't find any Kubernetes API usages that require these permissions. Besides, some of these unused permissions may have potential risks. For example, if malicious users gain control of a Kubernetes node running a kubewarden-controller pod, they can use the "update deployments" permission to edit existing workloads, create privileged containers with malicious container images.
Therefore, for security reasons, I suggest checking these permissions to determine if they are truly unnecessary. If they are, the issue should be fixed by removing the unnecessary permission or other feasible methods.
Expected Behavior
No response
Steps To Reproduce
Use helm charts with default values.
Environment
- OS:
- Architecture:

Anything else?
No response

Thanks for the report. We've recently changed the code a bit and this lead to some of these permissions to be not needed.
I've already verified the list permission for Deployment is not needed.
As for the Secret and Service permissions, their permissions are defined inside of the same RBAC block as ConfigMaps (see here)
I think these resources should have similar verbs. We have to do some double checking and probably replace some CreateOrUpdate with CreateOrPatch statements.
@Yseona: I've seen you've opened similar issues against other open source projects. What kind of tool are you using to automate the auditing? It would be useful for us too

Listing of secrets and other resources is required by the k8s' client-go cache

We have a mix of CreateOrUpdate and CreateOrPatch, I've made sure we are only using CreateOrPatch and then I removed the update verb from deployments, configmaps, secrets and services.
Everything seems to be working fine.
However... if you have patch verb you can still change the contents of one of these resources, hence there's no real benefit in removing the update verb.
To recap:

list: needed for the client-go cache to work as expected
update: theoretically not needed with a small changes, but being pragmatic it doesn't make any difference from the security POV since we must leave the patch verb around. Hence, it's still possible to alter the contents of these resources

I would personally close this issue without changing the RBAC criteria we currently have. I would just consolidate the codebase to use only CreateOrPatch.
What do you think?

I'm fine with the standardization of the 'CreateOrPatch' usage. I like it.  Furthermore, keep in mind that the actual RBAC roles deploy is in the helm-chart repository. And they can be out of sync sometimes because of the manual process of updating it. I've recently updated the controller repo to follow the helm-chart values (at least, most of them). Therefore, if we did this change, remember to update both places.

Closing after having discussed the implications with the rest of the team.


elasticsearch query to vespa query translator

some kind of helper tool that translates from an Elasticsearch / Solr / Lucene query to YQL / query API, possibly combined with supporting documentation in https://vespa.ai/migrating-from-elastic-search-to-vespa - this will make it easier to do apples-to-apples comparisons for users doing evaluations

Is there any way we can perform a yql search query by boosting a term like in lucene.
https://lucene.apache.org/core/2_9_4/queryparsersyntax.html

@107dipan yes, multiple ways to accomplish this
{
  "query": "jakarta!400 apache",
   "type": "any",
    "yql": "select * from sources * where userQuery()",
    "ranking.profile": "someprofile-with-nativerank"
}

The above will weight the term jakarta 4x more than the term apache (default term weight is 100) but you need a ranking profile which uses nativeRank https://docs.vespa.ai/documentation/nativerank.html.
You can also adjust weights via YQL annotations and use YQL only:
{
"yql": "select * from sources * where (default contains "apache" OR default contains ([{"weight": 400}]"jakarta"));",
"ranking.profile": "someprofile-with-nativerank"
}

See https://docs.vespa.ai/en/reference/query-language-reference.html
Also there is the rank query operator which allows you to retrieve using one set of terms and produce ranking features by others which does not impact recall but only precision. In the below example we retrieve documents with apache and produce matching ranking features for the term jakarta.
{
"yql": "select * from sources * where rank(default contains "apache", default contains ([{"weight": 400}]"jakarta"));",
"ranking.profile": "someprofile-with-nativerank"
}

Great!!
What about Fuzzy search and proximity search for string fields?

See https://github.com/vespa-engine/vespa/issues/9371 on Fuzzy. Proximity see onear/near in the YQL doc @107dipan

Thanks a lot!

@107dipan Did you want to give it a shot to write a query translator or just general interest?

I am planning on writing the query translator. Wanted to map different lucene functionalities with equivalent vespa yql before starting.

Great! Keep us posted @107dipan if you have questions.

Hi @jobergum ,
Does "query": "jakarta!400 apache", still work if I am using a hybrid rank profile, say, as defined as below-
with app.syncio(connections=1) as session:
  query = "How Fruits and Vegetables Can Treat Asthma?"
  response:VespaQueryResponse = session.query(
    yql="select * from sources * where title contains \"vegetable\" and rank({targetHits:1000}nearestNeighbor(embedding,q), userQuery()) limit 5",
    query=query,
    ranking="fusion",
    body = {
      "input.query(q)": f"embed({query})"
    }
  )

Source - https://pyvespa.readthedocs.io/en/latest/getting-started-pyvespa-cloud.html#Hybrid-search-with-filters

The query parameter accepts the simple query language and jakarta!400 lucene will add 400 weight to the term jakarta (default is 100) - but, the term weight is not used in all text ranking features. It is used in nativeRank, nativeFieldMatch, but not in bm25.
So the answer is, yes, you can pass weights using the simple query language, but how it impacts ranking, depends on which text ranking features you are using.

Hi, just checking if a query translator was added. We'd like to move from Elasticsearch to Vespa and any tools to do this would be helpful.

Sorry, no translator in public domain yet. We know of several teams have created this and are trying to get them to open source ...


fix nil pointer panic when pvc has no storageclass

What this PR does / why we need it:
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Codecov Report

Merging #1143 (45455fb) into main (ae188d2) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main    #1143   +/-   ##
=======================================
  Coverage   38.83%   38.83%
=======================================
  Files          25       25
  Lines        1970     1970
=======================================
  Hits          765      765
  Misses       1103     1103
  Partials      102      102

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Collapser metrics

Addresses #14.  Any thoughts on naming, @benjchristensen / @KoltonAndrus / others?

NetflixOSS » Hystrix » Hystrix-pull-requests #4 FAILURE
Looks like there's a problem with this pull request

Hystrix-pull-requests #243 SUCCESS
This pull request looks good

Hystrix-pull-requests #244 SUCCESS
This pull request looks good

NetflixOSS » Hystrix » Hystrix-pull-requests #5 SUCCESS
This pull request looks good

Replaced by #576