WeGO and impact to DORA metrics

Question
What are 2 or 3 ways WeGO can have a positive impact on users Deployment Frequency, Lead Time For changes, MTTR, Change Failure Rate.
Short description
DORA identified the following metrics as key attributes for measuring a team/product health:

Deployment Frequency
Lead Time For changes
MTTR
Change Failure Rate.

Timebox
3 days

Outcome
Writeup your findings here.  Please include the following (if any have been created) :

Screenshots
Design/architecture diagrams
WEP
PR/FAQ

We may have some pre-existing gitops whitepapers that can be used here.


docs: add contribution guidelines

PR Type

Improvement

Related Links

Inspired by comma.ai's openpilot

Description
Add contribution guidelines to Nebula. This allows easier contributions from the community and provides a clear set of rules and expectations we can refer to.
Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets

CI Checks

Build and test for PR: Required to pass before the merge.

@drwnz Thanks for the many suggestions! I applied them all. Please re-review when you find the time :pray:


Future<T?> network

Greetings, why not return an error instead of null?
When I call an api method from a page, I would like to see the response in order to process it further.
Those answers that I don't want to process individually, the global displayError will do fine.

Hi @lacoste-sochi,
Thanks for the comment.
The network helper is still returning the error from the try and catch (line 68 and 73).
In your API Service, you can handle the response.
I've noticed that the try and catch Exception block is missing the onError callback so I'll create a PR for that.

Hi @lacoste-sochi,
Thanks for the comment.
The network helper is still returning the error from the try and catch (line 68 and 73). In your API Service, you can handle the response.
I've noticed that the try and catch Exception block is missing the onError callback so I'll create a PR for that.

The fact is that handleFailure is useless. DIO error is triggered at the stage
Response response = await request(_api);
It turns out that handleFailure does not work at all, for an error like
Http status error [400]
For example, I need to output errors and buttons for this method to alert, message. I can't assign globally, I have different event reversals

I'll look into this at my earliest convenience.

@lacoste-sochi, thanks for spotting this.
It's been fixed in v3.1.4 🚀
https://pub.dev/packages/nylo_framework


Configure tests with junit style output

With something like https://github.com/jstemmer/go-junit-report. Seems like circle can provide some insights on our if we do this.

i'm going through ancient issues. is this still relevant?
https://github.com/jstemmer/go-junit-report seems like a solution, or we can close this if we don't care anymore.


[Network] BREAKING CHANGE: az network vnet: Deprecate parameter --defer

Related command

az network vnet create/update
az network vnet subnet create
Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Network


Notebook File/Cell Sace and Recover Problem

Issue Type: Feature Request
Hello, I am using jupyter notebook in VScode, I found it diffcult to reason about what I can recover in the cell or the file; I suppose the controlling logic is confusing; If you guys can make it clearer, it will be a great thing to use notebook in VScode! Thanks a lot
VS Code version: Code 1.63.1 (fe719cd3e5825bf14e14182fddeb88ee8daf044f, 2021-12-14T02:13:54.292Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

found it diffcult to reason about what I can recover in the cell or the file

Do you mean undo/redo?

found it diffcult to reason about what I can recover in the cell or the file

Do you mean undo/redo?

Exactly; I found it really difficult to use like when I accidentally delete the whole cell

re-opening since the user provided an answer. Also a suggestion from https://github.com/microsoft/vscode-jupyter/discussions/9846 was just to not put adding the cell in the undo/redo stack.


Implement river forecasting as many to many prediction

When you say "many to many" does this mean river and/or deep-river does not, yet, permit one to have more than one feature on output?
PS: I've spent probably 4 or 5 hours trying to figure out if river and/or deep-river can have more than one feature on the output.  None of the introductory documents say there is this limitation.  If there is this limitation then please state it in the introduction if not the FAQ.

Hello @jabowery
the forecaster module is especially interesting for lstm modules as the support "many to many" . Hopefully they will be included within the next release!

Terminology can be such a nightmare without very careful documentation.
Let's distinguish "many" as in "many features in a single time step" as opposed to "many time steps with a single feature per stream step".  This distinction is absolutely critical for any documentation regarding "streams".
For example, there is another term called "sequence-to-sequence" which is equivalent to "many time steps with a single feature per time step".  e.g. the "sequence" of characters: "Now is the time for all good men to come to the aid of their party." "to-sequence" of characters: "Jetzt ist es an der Zeit, dass alle guten Männer ihrer Partei zu Hilfe kommen."
I'm not asking about that sense of "many".
The sense of "many features" I'm asking about is illustrated by the fact that all of the deep-river example code I've seen has data of the following form:
vector (dictionary) -> scalar
vectors have many scalars whether we call them "dictionaries" or not.
Understand my problem?
But the most general

Hey @jabowery. The answer is that no we don't support dynamical systems. River (and its deep counterpart) are focused on typical machine learning tasks, such as regression and classification. We don't do state-space modeling and Kalman filters. It's not currently on the roadmap.


mathtext:0.0.1

I am submitting

[x] a new package
[ ] an update for a package

I have read and followed the submission guidelines and, in particular, I

[x] selected a name in conformance with the guidelines
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] ensured that my submission does not infringe upon the rights of a third party
[x] tested my package locally on my system and it worked (see https://typst.app/project/rKb66eanDkWAXrJYvP0mtF)
[x] named this PR as name:version of the submitted package
[x] agree that my package will not be removed without good reason

Description: Explain what the package does and why it's useful.

Sneak Peek
Preview

Source
With `mathtext`:

- $textsc("Equation") a x + b y + c = 0$
- $textit("Equation") a x + b y + c = 0$
- $textbf("Equation") a x + b y + c = 0$
- $textrm("Equation") a x + b y + c = 0$

Without `mathtext`:

- $#smallcaps("Equation") a x + b y + c = 0$ does not work at all.
- $italic("Equation") a x + b y + c = 0$ does not use the document font.
- $bold("Equation") a x + b y + c = 0$ does not use the document font.
- $upright("Equation") a x + b y + c = 0$ does not use the document font.

Also, I'm happy to be the first person to submit the Typst package. 😄

As far as I can see this doesn't actually do what it claims to do. It does not use the document font, but some fallback.

As far as I can see this doesn't actually do what it claims to do. It does not use the document font, but some fallback.

Nice catch! I'm always using Linux Libertine and didn't realized it's a Typst's fallback.

I am going to close this because it doesn't work (as already discussed). The font handling is something that needs to be fixed in the compiler.


Optimizing SharePoint Performance before setting root site clarification?

When it says:  Important
Before you launch an intranet landing page at your root site location, we strongly encourage you to review the guidance about optimizing SharePoint performance the link given goes to a page with over 20 links. I read the first 5, and they seem to be all kind of general SP Performance guidelines, most better suited to on-premise rather than online. I didn't see anything that seemed especially to refer to optimizations required before setting a root site.
Rather than point us to a general page with a bunch of links, could you please clarify for us just what we should take into account about setting a root site and the optimization that should be done beforehand?

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

ID: 7a824ca6-37ae-11c4-f04e-5de1ba5551c5
Version Independent ID: b02f6141-9dc9-1e26-8beb-9a1f21dd042e
Content: Modernize your root site
Content Source: SharePoint/SharePointOnline/modern-root-site.md
Service: sharepoint-online
GitHub Login: @kaarins
Microsoft Alias: kaarins

@DS2019  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @DS2019, thank you for your feedback.
My apologies but we cannot provide that as there are several best practices to consider to optimize a portal and all of them have their detailed explanation.
I have verified the links and all of them are for SharePoint Online/Office 365. Also you have a section "Optimize your Performance" with several links.
Hope you understand. Thank you!

Thanks, @dariomws306 - but it seems the information I had posted about has totally changed from a bunch of disparate links to  a new link on "review the guidance about launching healthy portals," and there are helpful links now in a table: https://github.com/MicrosoftDocs/OfficeDocs-SharePoint/blob/live/SharePoint/SharePointOnline/portal-health.md
From looking at the history, the changes were made in Nov 2019 and Dec 2019. So, what I reported on has been fixed, and it has been provided.

@DS2019 Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Add a setting to flip resource display to amount used as opposed to amount available.

Should default to current behaviour. Which is to display amount available.

This is done!


[kong] improve RBAC documentation

What this PR does / why we need it:
Improves existing RBAC docs to better show how to set up the initial super-admin and allow the controller to talk to RBAC-secured instances.
Special notes for your reviewer:

This does not discuss readiness/liveness checks, which also currently require tokens. Intent is to add a custom server block listen to approximate status_listen (and eventually replace it with the standard status_listen), removing the need for admin API status calls. This will be a separate PR.
https://github.com/Kong/charts/commit/ed7e1b609e59a6784a23bd2f75d51fbb32df59cd further adds an example for the controller within values.yaml. None for Kong itself, since that variable should only be in place temporarily.

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] PR is based off the current tip of the next branch and targets next, not master
[x] Title of the PR and commit headers start with chart name (e.g. [kong])

This does not discuss readiness/liveness checks, which also currently require tokens. Intent is to add a custom server block listen to approximate status_listen (and eventually replace it with the standard status_listen), removing the need for admin API status calls. This will be a separate PR.

I might be missing something. Doesn't the existing server block configmap and metrics take care of the health checks? We don't rely on Admin API status checks.


Gaian plugin needs to remove hardcoded userid/password & use config

The userid/password to connect to ranger is currently hardcoded in
open-metadata-implementation/adapters/governance-engines-plugins/gaian-ranger-plugin/src/main/java/org/odpi/openmetadata/adapters/governanceenginesplugins/gaianrangerplugin/RangerPolicyResultFilter.java
Whilst this will allow some initial testing, this needs changing fairly soon as default passwords will not be used in any sensibly configured system - certainly not with externally exposed deployments. I think this is needed soon,and for the MVP/demos.
(search for admin:admin)
re: review https://github.com/odpi/egeria/pull/416

Is this fixed?

Yes - can close.


chore: support ecto 3.5

Resolve #60

Hello could the maintainers of the project please merge this PR and add a new release to hex? The latest version of ex_audit is 0.7 which supports ecto 3.2! I've got a bunch of projects with a dependency of ex_audit and I can't upgrade them.
If it's not going to be merged and released at all then please at least consider telling us so we can fork the project and use our own versions to be able to upgrade ecto!

Hello could the maintainers of the project please merge this PR and add a new release to hex? The latest version of ex_audit is 0.7 which supports ecto 3.2! I've got a bunch of projects with a dependency of ex_audit and I can't upgrade them.
If it's not going to be merged and released at all then please at least consider telling us so we can fork the project and use our own versions to be able to upgrade ecto!

I can only merge if I find the time to fully test if everything continues to work.
However, you can always add override: true to the direct dependencies of your own projects where you're using ex_audit:
{:ecto, "~> 3.2", override: true}

Thank you very much I didn't even know about override: true! Yes, you are right this should be perfect for now :)
Kind regards,
Serafeim

@narrowtux would you mind publishing a new release? In the current one, override: true does not work. So I ended up pointing ex_audit to the github repo, like so:
{:ex_audit, git: "https://github.com/ZennerIoT/ex_audit"},

@narrowtux sorry to bother you, mate, but is there anything we can do to help you to upgrade the lib?

@narrowtux sorry to bother you, mate, but is there anything we can do to help you to upgrade the lib?

Closed because I released 0.8 with support for ecto 3.6.2 manually.
I don't want to do it for every ecto release, most of the time, it is not necessary. in this case, ecto introduced a new function to the repo, so it had to be done. In all other cases, you can fix your deps by adding override: true to your ecto and ecto_sql deps. If you then find bugs, ex_audit needs a new release, but otherwise, it won't.


Daemonizing multiple functions at once

from src import main
from functools import partial

for i in range(6):
	pid = f"/tmp/app_{i}.pid"
	Daemonize(app=f"app_{i}", pid=pid, action=partial(main, some_arg=True), auto_close_fds=False).start()

Could I make something like this work somehow? As of now It will exit after the first iteration.

Use a separate script that utilizes subprocess, which calls your application with args, and parse those args to use in your daemonization.


Recommend to use pip instead of easy_install

From<EMAIL_ADDRESS>on 2013-05-20T04:38:12Z
Spyder Version:  2.2.0
Python Version:  2.7.3
Qt Version:      4.8.1, PyQt4 (API v2) 4.9.1 on Linux
I installed Spyder on Ubuntu 12.04 using easy_install -U spyder .
What steps will reproduce the problem?

Launch spyder
Press the F1 key. What is the expected output? What do you see instead? Expected output: The help file should be displayed.
I see instead: Could not find "/usr/local/lib/python2.7/dis.../lib/spyderlib/doc/index.html".

Please provide any additional information below
.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1399

From ccordoba12 on 2013-07-05T10:12:45Z
Uwe, I verified that our docs are not installed, as you reported, but only when using
easy_install -U spyder
If you use
pip install -U spyder
then there is no problem.
Unfortunately I'm not a setuptools guru, so I don't know how to fix it. Besides, most people recommend these days to use "pip" over "easy_install" because it's a better package manager, so that's my recommendation for you too.
I'm marking this issue as "HelpNeeded" until someone decides to give us a hand and fix it, sorry.
Summary: Spyder documentation is not installed when using easy_install   (was: Help (F1) is not working on Ubuntu 12.04)
Status: HelpNeeded
Labels: -Priority-Medium -MS-v2.2.1 Priority-Low

From ccordoba12 on 2013-06-28T22:04:06Z
Thanks for reporting. I'll see what we can do about it
Labels: MS-v2.2.1 Cat-Miscelleneous

From<EMAIL_ADDRESS>on 2013-07-05T10:55:01Z
I would accept if you mark this issue as fixed (it works for me now), after you have updated the installation hints for Linux at: https://code.google.com/p/spyderlib/wiki/Installation There it is currently suggested to use easy_install.

From ccordoba12 on 2013-07-06T08:38:11Z
Ok, thanks Uwe for the recommendation. I'm going to do it right now.
Summary: Recommend to use pip instead of easy_install   (was: Spyder documentation is not installed when using easy_install)
Status: Accepted
Labels: -Priority-Low Priority-Medium MS-v2.2.1

From ccordoba12 on 2013-07-06T19:08:25Z
This issue was updated by revision 83635bfd2c53 .
Status: Fixed


TREXIO group indirection in HDF5 backend

It may be useful to further namespace trexio data in the case of shared HDF5 files, e.g. /nucleus -> /trexio/nucleus, etc. This may be not required in the event that #117 gets merged.

I thought HDF5 had a functionality to link HDF5 files. It seems cleaner than having one HDF5 file to rule them all. What am I missing?


GIFs/WebP textures don't actually emit light with Lumen

Hello!
So I opened your "UAnimatedTexture5-master" test project that you have provided in UE 5.0.2 and created a new empty level in there, (no light, pitch black), made a plane and a sphere, sphere sitting on top of the plane. Drag and drop any GIF/Webp from your project onto the sphere to create material, plug the texture into emissive and crank the value up. No matter how bright I make it, it doesn't actually light the scene.
With Lumen in UE5, emissive materials actually cast the shadow so if I replace your GIFs/WebP files with any random static jpg/png file in the same material, the sphere now actually lights up the plane meaning Lumen is working and Emissives are casting light otherwise, they just don't do it with animating GIF/Webp files in general.
If I am mistaken or missing something, please do let me know but if it doesn't work on your end as well, I am guessing its a bug. Hoping to hear from you regardless.
Thanks
Indy.

UPDATE: So turns out it isn't your tool but if you take any image in a basic material and set it to emissive, if the material blend mode is set to either Opaque or Masked then Lumen casts light from that material but if you set it to Translucent, which is what I want, then it stops casting any light.
Currently searching for ways to have translucent emissive materials that cast light in the scene.

hi how did you make it work with Ue5
is it 5.02 or Ea?

UPDATE: So turns out it isn't your tool but if you take any image in a basic material and set it to emissive, if the material blend mode is set to either Opaque or Masked then Lumen casts light from that material but if you set it to Translucent, which is what I want, then it stops casting any light. Currently searching for ways to have translucent emissive materials that cast light in the scene.

Found the reason. Any kind of translucent material will not contribute to Lumen lighting and hence will not cast light in the scene if set to emissive. So the solution for now is to set it to Masked until Lumen updates. Hope this helps someone.

hi how did you make it work with Ue5 is it 5.02 or Ea?

Do you mean how I made the GIF importer work in UE5? I am on 5.0.2 and it works out of the box. Download the zip file that contains his UE5 project. Extract it and go to plugins folder and cut the entire folder of Animated Texture and paste it in your projects Root directory the same way it was in his project. Upon launching UE will ask to compile say yes and it should work. Hope it helps.

yes I already do that but my compile is failed
if you success so there are some problems with my - -*


kubectl kudo install $framework fails

What happened:
On a fresh clone and make cli, when attempting to install the Zookeeper framework via:
$ kubectl kudo install zookeeper
I get the following error:
➜  kudo git:(master) k kudo install zookeeper
Error: could not install framework(s): installing single Framework: installing zookeeper-framework.yaml: installing Framework: Framework in version "v1alpha1" cannot be handled as a Framework: unmarshalerDecoder: Object 'Kind' is missing in '{"inline":{"kind":"Framework","apiVersion":"kudo.k8s.io/v1alpha1"},"metadata":{"name":"zookeeper","creationTimestamp":null,"labels":{"controller-tools.k8s.io":"1.0"}},"spec":{},"status":{}}', error found in #10 byte of ...|tatus":{}}
|..., bigger context ...|oller-tools.k8s.io":"1.0"}},"spec":{},"status":{}}
|...

What you expected to happen:
Successful creation of the Zookeeper Framework, FrameworkVersion, and Instance
How to reproduce it (as minimally and precisely as possible):

Clone
make cli
Add kubectl-kudo to $PATH
kubectl kudo install zookeeper

Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version): 1.14.0
Kudo version (use kubectl kudo --version): 0.1.1
Framework: Any
Frameworkversion: Any
Cloud provider or hardware configuration: Minikube
OS (e.g. from /etc/os-release): Alpine

Interesting, when looking at the actual zookeeper-framework.yaml received from https://github.com/kudobuilder/kudo/blob/master/pkg/kudoctl/cmd/install/install.go#L204
it looks like there is indeed no Kind field value:
framework-yaml: &{TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:zookeeper GenerateName: Namespace: SelfLink: UID: ResourceVersion: Generation:0 CreationTimestamp:0001-01-01 00:00:00 +0000 UTC DeletionTimestamp:<nil> DeletionGracePeriodSeconds:<nil> Labels:map[controller-tools.k8s.io:1.0] Annotations:map[] OwnerReferences:[] Initializers:nil Finalizers:[] ClusterName:} Spec:{} Status:{}}

After digging deeper into it I noticed that we changed https://github.com/kensipe/kudo/blame/c372d9d78ebe82c8bfb967576b52774cf8ba48ad/pkg/apis/kudo/v1alpha1/framework_types.go#L43, in particular ,inline to inline - when I compile and run with ,inline it seems to work. Can you verify?


[SPARK-43529][SQL] Support general constant expressions as CREATE/REPLACE TABLE OPTIONS values

What changes were proposed in this pull request?
This PR updates the SQL compiler to support general constnat expressions in the syntax for CREATE/REPLACE TABLE OPTIONS values, rather than restricting to a few types of literals only.

The analyzer now checks that the provided expressions are in fact foldable, and throws an error message otherwise.
This error message that users encounter in these cases improves from a general "syntax error at or near " to instead indicate that the syntax is valid, but only constant expressions are supported in these contexts.

Why are the changes needed?
This makes it easier to provide OPTIONS lists in SQL, supporting use cases like concatenating strings with ||.
Does this PR introduce any user-facing change?
Yes, the SQL syntax changes.
How was this patch tested?
This PR adds new unit test coverage.

Note @MaxGekk @gengliangwang it says the GitHub actions CI failed, but actually this was just an unrelated PySpark flake and they actually passed :)

Update on this: I thought of a simpler way to break apart this work into smaller pieces so we can make gradual improvements. Let me make a commit and then I can ping this thread again.

This is done, I have deferred the constant folding logic to the analyzer. This is ready for another look.

Hi @gengliangwang I implemented your suggestion, the code is simpler now, this is ready for another look.

Note: the CI is actually passing, the pyspark failure is spurious/unrelated.

(Note, this is passing all CI again.)

LGTM except for the last comment. Sorry for the slow response, I was focusing on another project.

No worries, thanks for the careful reviews :)

This has been iterated for many rounds. I will make a follow-up PR to further make the code simpler.
Merging to master.


请问如何使用 PUT 方法上传文件到服务器，翻看了文档，没有相关的介绍

New Issue Checklist

[ ] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
e.g. flutter / ios / android

Platform Version
e.g.  1.5.0 / 12.0 / 9.0

Dio Version
e.g.  2.1.0 / 1.0.17

Android Studio / Xcode Version
e.g. Android Studio 3.3.2 / Xcode 10.2.1

Repro rate
e.g. all the time (100%) / sometimes x% / only once

Repro with our demo prj
e.g. does it happen with our demo project?

Demo project link
e.g. link to a demo project that highlights the issue

Issue Description and Steps
Please fill in the detailed description of the issue (full output of any stack trace, compiler error, ...) and the steps to reproduce the issue.

https://github.com/flutterchina/dio/blob/master/example/formdata.dart
上传文件请用FormData ,post方法换成put即可


Add presubmits for Fuchsia

Check it builds. Bonus points if the tests can be run.

Given that we still haven't found a viable approach to do this on SwiftShader CI testing yet, I see no point keeping this bug open indefinitely.
Will reopen if things change.


Can events be retracted or deleted?

Hi, @jruizgit . I'm trying to use statechart to do some warnings. In my below use-case, a warning will be sent again if i received 3 events larger than 100 in 'dangerous' state.
var d = require('durable');
var m = d.m;
d.statechart('waterValve', {

  // initial state 'init' with two triggers
  init: [{
    to: 'safe',
    whenAll: m.water.lt(100),
    run: function (c) {
      console.log('init-->safe: ' + c.m.water);
    }
  },{
    to: 'dangerous',
    whenAll: m.water.gte(100),
    run: function (c) {
      console.log('init-->dangerous: ' + c.m.water);
    }
  }],

  // state 'safe'
  safe: [{
    to: 'safe',
    whenAll: m.water.lt(100),
    run: function (c) {
      console.log('safe-->safe: ' + c.m.water);
    }
  },{
    to: 'dangerous',
    whenAll: m.water.gte(100),
    run: function (c) {
      console.log('safe-->dangerous: ' + c.m.water);
	  // TODO : warning
    }
  }],

  // state 'dangerous'
  dangerous: [{
    to: 'safe',
    whenAll: m.water.lt(100),
    run: function (c) {
      console.log('dangerous-->safe' + c.m.water);
    }
  },{
    to: 'dangerous',
    whenAll: m.water.gte(100),
    count: 3,
    run: function (c) {
      console.log('dangerous for 3 times' + c.m.length + JSON.stringify(m));
      // TODO : warning
    }
  }
  ],
});

d.runAll();

However, with the following input, events (1)(2) (> 100) will be stored in database and will cause a new warning if i received a event larger than 100 (event 5) after that.
(0)// 'init' to 'dangerous' state
 (0) curl -H "content-type: application/json" -X POST http://localhost:5000/waterValve/event -d '{"water": 20000}'
 (1) curl -H "content-type: application/json" -X POST http://localhost:5000/waterValve/event -d '{"water": 20000}'
 (2) curl -H "content-type: application/json" -X POST http://localhost:5000/waterValve/event -d '{"water": 20000}'
(3)// 'dangerous' to 'safe' state
(3) curl -H "content-type: application/json" -X POST http://localhost:5000/waterValve/event -d '{"water": 50}'
(4)// 'safe' to 'dangerous' state
(4) curl -H "content-type: application/json" -X POST http://localhost:5000/waterValve/event -d '{"water": 20000}'
(5)// send warning again for just one post
(5) curl -H "content-type: application/json" -X POST http://localhost:5000/stateValve/event -d '{"water": 20000}'
I was wondering if events (1) and (2) can be retracted or deleted when i receive event (3) ?
Or is there some other types of rules that can solve my problem?
Thanks!

Thanks for posting the question, let me look into this. Events are retracted before dispatch and should be observed only once.

I understand your scenario now. When moving from dangerous to safe, the events accumulated in the reflexive rule count will not be retracted (this is by design, one important principle: the rules engine never drops events). For this case I recommend you keep track of the count using the context state. For example:
var d = require('../libjs/durable');
var m = d.m, s = d.s;
d.statechart('waterValve', {

  // initial state 'init' with two triggers
  init: [{
    to: 'safe',
    whenAll: m.water.lt(100),
    run: function (c) {
      c.s.count = 0;
      console.log('init-->safe: ' + c.m.water);
    }
  },{
    to: 'dangerous',
    whenAll: m.water.gte(100),
    run: function (c) {
      c.s.count = 0;
      console.log('init-->dangerous: ' + c.m.water);
    }
  }],

  // state 'safe'
  safe: [{
    to: 'safe',
    whenAll: m.water.lt(100),
    run: function (c) {
      console.log('safe-->safe: ' + c.m.water);
    }
  },{
    to: 'dangerous',
    whenAll: m.water.gte(100),
    run: function (c) {
      console.log('safe-->dangerous: ' + c.m.water);
	  // TODO : warning
    }
  }],

  // state 'dangerous'
  dangerous: [{
    to: 'safe',
    whenAll: m.water.lt(100),
    run: function (c) {
      c.s.count = 0;
      console.log('dangerous-->safe' + c.m.water);
    }
  },{
    to: 'dangerous',
    whenAll: m.water.gte(100),
    run: function (c) {
      c.s.count += 1;
      console.log('incrementing count');
      // TODO : warning
    }
  },{
    to: 'dangerous',
    whenAll: s.count.eq(3),
    run: function (c) {
      c.s.count = 0;
      console.log('dangerous for 3 times');
      // TODO : warning
    }
  }
  ],
});

d.runAll();

@jruizgit
Thank you so much for your reply! That was very useful for me.


Lets capture the time it takes to get a list endpoint out.

Changes proposed in this PR

Put a metric on the actual response generation time for the /list API call

Why are we making these changes?

We don't actually metric this user-visible time.

Any suggestions on the best way to test this?

@scrosby I don't think we really test output of metrics.

This was merged with a broken build and master is breaking now, e.g. https://travis-ci.org/twosigma/Cook/jobs/357585822. Can we revert?


Need collision sounds

If I throw something at a wall I expect a sound.
Needs some sort of CD to avoid the sound getting spammed (especially during prediction).

Trying to figure out a generic thud for this...


ETL production level not coming through

production.production_level is empty on etl'd data. needs to be country, site, concession or prject. Thinking it should default to project.

At the moment its always country or project - I can infer that and add it to the import. Done (not pushed) in 941f80e.


assert: Add Error and handle error unwrapping in Equal

@coadler what do you think about adding ...cmp.Options to Equals? I think name is enough for adding detail instead of a ...slog.F.

I could see some benefit in that. Right now we have to truncate all of our time.Times because ones returned from Postgres lose a bit of precision. If we could make a cmd.Option to manually compare them that would help a lot.

@coadler Thoughts on removing google/go-cmp? Do you approve?


Saving updated edge document via ArangoDB UI says 'saved' but an error was generated.

my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[x] 3.1.15

On this operating system:

[x] Linux

[x] Ubuntu 16.04 LTS

I'm issuing AQL via:

[x] web interface with this browser:    Chrome Version 57.0.2987.133 running on Windows 10 Pro

This has happened a few times now and it's worth reporting.
I have an edge collection with only 13 edges, it connects two collections with 4 documents and 12 documents respectively.
The issue is that I login via the ArangoDB UI and open a document within the Edge collection.
When I modify the document for a particular document, in 'Code' view, and click save, the UI shows a green bar on the bottom of the screen that says 'Document saved.'.
When you close the edge document and open it again, the changes were not saved.
If you add attributes to a new edge, it says saved but when you open it the document is empty.
If you use Developer tools in Chrome to see what happened there is an error coming back from the ArangoDB server that the UI is not handling:
This is the PUT request that is generated when I click 'Save'
Request URL: https://myserver:8530/_db/mydatabase/_api/document/myedgecollection
Request method: PUT
Status Code: 202 Accepted
Request Payload:
[{"mykey":{"foo":"bar"},"qaz":"wsx","foo":"bar","_key":"362694866","_id":"myedgecollection/362694866"}]
Response:
[{"error":true,"errorNum":1233,"errorMessage":"edge attribute missing or invalid"}]
Actually, on trying to replicate the issue, I'm unable to modify any documents in any edge collections, regardless of size.
To update them I have to create a Query and write AQL to update the edge by _id.
I suppose there are two issues, one is why the 'edge attribute missing or invalid' is coming back, especially when I can update that edge via an AQL query, and secondly why doesn't the UI capture this error and display something on the UI.

This was an issue in 3.1.15. Please update to 3.1.16 or latest 3.1.X release.

Thanks for that, I upgraded to 3.1.17 and it fixed the problem.  But I noticed that whenever you save a document in 3.1.17, either a vertex or edge document, the javascript console does a console.log output echo of the document contents and document type. It may have been left from troubleshooting an issue.

Yes, you're right. Removed. Thanks 👍


Add more Metadata to Images for besser inspection of parent images

https://github.com/dfki-ric/docker_image_development/issues/19


Personal Portfolio Project: Update Project README

Your project README does not have JavaScript in the tech stack.

Hi @forLoop94
Great Job 👍

Kindly consider adding a contributor to your README file since it was a pair programming exercise.


Scatterplot Radius Issues

Reports that

Scatterplot does not correctly render radius in meters
Scatterplot64 does not handle radius in same way as 32 bit version
Scatterplot documentation needs update

See discussions in #54

Issue addressed in #283

Should be addressed by #353


Clarify Role of Transport Layer

As per discussion in https://github.com/ReactiveSocket/reactivesocket/issues/119#issuecomment-255913582, let's clarify in the spec that the transport layer must be respected:
Comment from: https://github.com/ReactiveSocket/reactivesocket/issues/119#issuecomment-255902289

Re: transport-level flow-control. I am new to reactive-streams, Given that there is no send(T) defined for the publisher API, I think it's OK to consider transport-level flow-control an implementation detail. The doc could be improved though to mention that transport-level control is to be respected at the same time.

Transport behavior and requirements have been clarified in the protocol: https://github.com/ReactiveSocket/reactivesocket/blob/master/Protocol.md#transport-protocol
@tmontgomery Do we need any further clarification of transport-level flow control?

FYI ... Mike from Microsoft and I did some similar work to document HTTP (as a REST protocol)'s dependencies on transports (i.e. tcp as http/1.1, spdy, quic, http/2, ...).
https://github.com/MikeBishop/http-layering  (there are still pending issues)
We missed FCS, which is useful to mention.

I think we should leave this open and less proscriptive. At least at the moment.

@tmontgomery are you suggesting we close this and leave it as is?
@wenbozhu are you saying we need to provide more clarity in the spec? If so, what do you suggest?

I would leave as is. Or if we add some text, be very open with it so that we don't exclude too much at this point in time.

The current text looks good. Flow control is optional, e.g. websockt, being a L7 over TCP, doesn't provide flow-control in itself.

Closing out as we don't have anything actionable to do here.


License

Hi.
I see a license was added in #12.
The added license is not advised for software (Creative Commons iteslf advises not to use it for software). Additionally, it's a proprietary license.
I advise you to opt for Apache 2.0 or a similar open source software license, as advised by Creative Commons. This would make the project maximally useful for others.

Hi,
Thank you for your suggestion.
Unfortunately the choice of license highly depend on my university, so I used the license that my university allow me to use.

Hi.
Understandable.
This is not relevant here, so I apologize. If you are allowed, would you consider an explicit license for your other projects as well? ANYTHING is less restrictive than no license, because licenses can be rejected.

Unfortunately the choice of license highly depend on my university, so I used the license that my university allow me to use.

Do you believe it would be possible to build an argument to make your university more flexible on licensing?
This could really help adoption of your project (which from the examples looks amazing). Without a free license (or open source, which is about the same), it will be almost unusable, leading to unofficial clones being more used than your original.
The same applies to pretty much every other software program and that is why open source is far better for academic projects, as it makes research useful for the public.
If you are not very familiar with software licenses, or arguments for free software, I'd be more than willing to help if I can.

Yeah, do you know why they insisted on a CC license? It seems somewhat nonsensical for software, and I doubt it will actually have whatever the desired effect was.
Nothing against you, I get that you didn't have a choice.

The source code presented here is just a part of the paper, so to me it make sence that it has the same license as a paper. I saw many other papers publish their source code with the same license. So I belive suggestion from my University is valid here.

The source code presented here is just a part of the paper, so to me it make sence that it has the same license as a paper. I saw many other papers publish their source code with the same license. So I belive suggestion from my University is valid here.

Releasing source code and paper under the same license is actually a terrible idea.
That's because they are used for different purposes.
While the paper is only useful for academic purposes, the source code can be used in other fields.
The reason this is important is that it makes research actually useful: we often say that research should get more fundings, but that only makes sense if it contributes to society.
A non-open or non-free license does not contribute to society, unfortunately. It locks research away from everything else.

Either way, it appears it's now being used as an app:
https://apps.apple.com/us/app/avatarify-ai-face-animator/id1512669147


fix(api-client): overflow is added

Problem
This PR solves the issue #3636, authentication entries do not overflow when they have many characters.
Solution

awesome work @ga1az !!!


new(userspace/falco,userspace/engine): rule json schema validation

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area engine
What this PR does / why we need it:
Follow-up to #3302 , validate rule syntax against a json schema.
This PR also adds a --rule-schema CLI option to print the rule schema (just like #3312).
Which issue(s) this PR fixes:
Fixes #3149
Special notes for your reviewer:

moved yaml_helper to engine folder
the validation is done by the engine itself
validation errors are treated as warnings, just like we did for #3302

Example output:
Fri Sep  6 14:57:22 2024: Validating rules file(s):
Fri Sep  6 14:57:22 2024:    ../rules/falco_rules.yaml | schema validation: ok

Example failure:
Fri Sep  6 14:57:55 2024: Validating rules file(s):
Fri Sep  6 14:57:55 2024:    ../rules/falco_rules.yaml | schema validation: failed for <root>[46]: Object contains a property that could not be validated using 'properties' or 'additionalProperties' constraints: 'foo'.

Does this PR introduce a user-facing change?:

new(userspace/falco,userspace/engine): rule json schema validation

Here is how the -V option looks like:
Fri Sep  6 15:09:01 2024: Validating rules file(s):
Fri Sep  6 15:09:01 2024:    ../rules/falco_rules.yaml | schema validation: ok
../rules/falco_rules.yaml: Ok

So, we keep the exact same behavior of the normal rule loading schema validation (and the config schema validation), with $filename | schema validation: $res template.
Another option would be to break the consistency and print:
Fri Sep  6 15:09:01 2024: Validating rules file(s):
Fri Sep  6 15:09:01 2024:    ../rules/falco_rules.yaml
../rules/falco_rules.yaml: Ok | schema validation: ok

Don't really know which is better, i tend to really prefer the consistency of the former.

Also cc @jasondellaluce am not sure whether engine version should really be bumped :thinking:

Here is how the -V option looks like:
Fri Sep  6 15:09:01 2024: Validating rules file(s):
Fri Sep  6 15:09:01 2024:    ../rules/falco_rules.yaml | schema validation: ok
../rules/falco_rules.yaml: Ok

So, we keep the exact same behavior of the normal rule loading schema validation (and the config schema validation), with $filename | schema validation: $res template. Another option would be to break the consistency and print:
Fri Sep  6 15:09:01 2024: Validating rules file(s):
Fri Sep  6 15:09:01 2024:    ../rules/falco_rules.yaml
../rules/falco_rules.yaml: Ok | schema validation: ok

Don't really know which is better, i tend to really prefer the consistency of the former.
cc @leogr

If we assume that a proper message will be printed when the schema validation fails, another option would be not to expose the schema validation: ok when validation passes. In the end, schema validation is part of validation, and if everything is ok, everything is just ok :)

/hold
Working on the -V changes ;)

Rebased on top of master + added schema validation info (-V output) to rule_loader::result as_json and as_string methods.
New output:
Text:
Mon Sep  9 10:53:35 2024: Validating rules file(s):
Mon Sep  9 10:53:35 2024:    ../rules/falco_rules.yaml
../rules/falco_rules.yaml: Ok | schema validation: ok

Json:
Mon Sep  9 10:48:42 2024: Validating rules file(s):
Mon Sep  9 10:48:42 2024:    ../rules/falco_rules.yaml
{"falco_load_results":[{"errors":[],"name":"../rules/falco_rules.yaml","schema":"ok","successful":true,"warnings":[]}]}

Last commit enables yaml_helper to report all schema validation warnings (ie a vector of strings), instead of only the foremost one.
Example outputs:

-V json multiple schema validation issues:

Tue Sep 10 11:19:16 2024: Validating rules file(s):
Tue Sep 10 11:19:16 2024:    ../rules/falco_rules.yaml
{"falco_load_results":[{"errors":[],"name":"../rules/falco_rules.yaml","schema_valid":false,"schema_warnings":["failed for <root>[1]: Object contains a property that could not be validated using 'properties' or 'additionalProperties' constraints: 'conddd'.","failed for <root>: Failed to validate item #1 in array.","failed for <root>[2]: Object contains a property that could not be validated using 'properties' or 'additionalProperties' constraints: 'foo'.","failed for <root>: Failed to validate item #2 in array."],"successful":true,"warnings":[]}]}

-V json single schema validation issue:

Tue Sep 10 11:17:16 2024: Validating rules file(s):
Tue Sep 10 11:17:16 2024:    ../rules/falco_rules.yaml
{"falco_load_results":[{"errors":[],"name":"../rules/falco_rules.yaml","schema_valid":false,"schema_warnings":["failed for <root>[1]: Object contains a property that could not be validated using 'properties' or 'additionalProperties' constraints: 'conddd'.","failed for <root>: Failed to validate item #1 in array."],"successful":true,"warnings":[]}]}

-V json ok schema validation:

{"falco_load_results":[{"errors":[],"name":"../rules/falco_rules.yaml","schema_valid":true,"schema_warnings":[],"successful":true,"warnings":[]}]}

-V text multiple schema validation issues:

Tue Sep 10 11:34:54 2024: Validating rules file(s):
Tue Sep 10 11:34:54 2024:    ../rules/falco_rules.yaml
../rules/falco_rules.yaml: Ok
4 schema warnings: [failed for <root>[1]: Object contains a property that could not be validated using 'properties' or 'additionalProperties' constraints: 'vefgg'. failed for <root>: Failed to validate item #1 in array. failed for <root>[2]: Object contains a property that could not be validated using 'properties' or 'additionalProperties' constraints: 'foo'. failed for <root>: Failed to validate item #2 in array.]

-V text single schema validation issue:

Tue Sep 10 11:33:29 2024: Validating rules file(s):
Tue Sep 10 11:33:29 2024:    ../rules/falco_rules.yaml
../rules/falco_rules.yaml: Ok
2 schema warnings: [failed for <root>[1]: Object contains a property that could not be validated using 'properties' or 'additionalProperties' constraints: 'vefgg'. failed for <root>: Failed to validate item #1 in array.]

-V text ok schema validation:

Tue Sep 10 11:35:28 2024: Validating rules file(s):
Tue Sep 10 11:35:28 2024:    ../rules/falco_rules.yaml
../rules/falco_rules.yaml: Ok

NOTE: in normal run, while validating config and rule files, only foremost warning will be reported, example:
Tue Sep 10 11:52:36 2024: Falco version: 0.39.0-96+272986c (x86_64)
Tue Sep 10 11:52:36 2024: Falco initialized with configuration files:
Tue Sep 10 11:52:36 2024:    ../falco.yaml | schema validation: ok
Tue Sep 10 11:52:36 2024: System info: Linux version 6.8.0-41-generic (buildd@lcy02-amd64-100) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug  2 20:41:06 UTC 2024
Tue Sep 10 11:52:36 2024: Loading rules from:
Tue Sep 10 11:52:36 2024:    ../rules/falco_rules.yaml | schema validation: ok

/unhold

/cc @jasondellaluce

/hold

/unhold

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Any URL to directly download these dataset?

Or we must use this code to generate them?

Thanks for your code, but I can't find how should we get the dataset of peptides . Can you give me some instructions?

Hi,
All the datasets are deposited at Zenodo for a direct download: https://zenodo.org/record/6975830
You can find the PyG dataset loaders in this repo or also in the GraphGPS main repo:
https://github.com/rampasek/GraphGPS/tree/main/graphgps/loader/dataset
These PyG loaders use dropbox- or S3-hosted URLs for faster download than from the Zenodo servers.
I hope this answers your questions!
Best,
Ladislav

Hi,
All the datasets are deposited at Zenodo for a direct download: https://zenodo.org/record/6975830
You can find the PyG dataset loaders in this repo or also in the GraphGPS main repo: https://github.com/rampasek/GraphGPS/tree/main/graphgps/loader/dataset These PyG loaders use dropbox- or S3-hosted URLs for faster download than from the Zenodo servers.
I hope this answers your questions!
Best, Ladislav

Thanks for your nice answer, but there are still a few things I don't understand about pcqm4m-contact dataset.
I found it to be of size (3378606, 1)  which is very confusing to me, according to the paper it should have 529,434 graphs , could you please tell me what format the   pcqm4m-contact dataset organized?

I found it to be of size (3378606, 1) which is very confusing to me, according to the paper it should have 529,434 graphs , could you please tell me what format the pcqm4m-contact dataset organized?

The dataset is derived from the training set of OGB-LSC PCQM4Mv2. We computed the "contact" edges for all those ~3.3M molecules, but for computational limitations, we use the 530k subset of the dataset by using every 6th molecule from the original set. So that is why the full file has 3.3M entries. You can find this in the loaders that I mentioned above, particularly this part:
https://github.com/rampasek/GraphGPS/blob/6305368446275f9d5f3736d44bf265214d4f9a9b/graphgps/loader/dataset/pcqm4mv2_contact.py#L408
Let me know if you have any more questions!


Add LoRA support to HQQ Quantization

Thanks a lot for adding this PR. Would you be so kind to add some tests? It should be enough to copy+paste some existing tests and slightly adjust them for HQQ, see e.g. this one.

@BenjaminBossan is this okay? Sorry if my code is kinda a mess.

is this okay? Sorry if my code is kinda a mess.

Looks great, thanks, not messy at all -- or at least, not messier than the rest of the PEFT code ;-)
I'll give this a test tomorrow and will be back with a proper review.

@BenjaminBossan I'm done fixing it. Could you please test it again?

Quantization error
While working on the additional tests, I plotted the LoRA outputs of the normal model vs HQQ model used in the test and they seem to be highly correlated, but there are a big deviations for individual data points
>>> torch.testing.assert_close(output_normal, output_hqq)
*** AssertionError: Tensor-likes are not close!
Mismatched elements: 223632 / 224000 (99.8%)
Greatest absolute difference: 3.56396484375 at index (0, 3, 1141) (up to 1e-05 allowed)
Greatest relative difference: 41549.37890625 at index (0, 0, 15916) (up to 1.3e-06 allowed)

Probably this is fine, just wanting to check if this is in line with expectations.

I was wondering. The lora that you used for testing, is it trained with base model or with HQQ quantized model? If it's the latter, do other method of quantization also suffer from this kind of error?

Thanks for the additional changes. This looks pretty good already, there are only a few small things, please check my comments.
Furthermore, could you please ensure that make style was run on your code? Also make sure that the ruff version is 0.2.2.
Finally, it would be great to have an entry in the docs for this new quantization method.

I'm sorry. I don't understand what make style means.

I'm sorry. I don't understand what make style means.

In the root directory of your cloned peft repository, there should be a Makefile, right? When you run make style in the terminal, it will use this Makefile to run some commands to the check the code with ruff. Just try it out :)

I'm sorry. I don't understand what make style means.

In the root directory of your cloned peft repository, there should be a Makefile, right? When you run make style in the terminal, it will use this Makefile to run some commands to the check the code with ruff. Just try it out :)

Oh, I got it. I'm currently using Windows so I don't understand what make style means. After moving it to linux, I finally can run it.

I'm currently using Windows so I don't understand what make style means

I didn't know make doesn't work on Windows. There seem to be some solutions. These days, I'd probably use WSL if that's an option.

another nvidia-only feature?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@fahadh4ilyas Could you please run ruff again? We just need an extra new line before dispatch_hqq.

@BenjaminBossan it's done. I think I have to get used to run make style every commit.

I think I have to get used to run make style every commit.

You may want to set up a pre-commit hook as explained here.

Any progress so far, amazing work for the hqq support we want to have a try this feature.

With https://github.com/huggingface/transformers/pull/29637 being merged, let's not forget about this PR. There are some merge conflicts due to the EETQ PR, but they should be easy to fix.

@BenjaminBossan and @younesbelkada please check the current update. Is it okay if the test checking the compatibility of transformers with HQQ first?

Thanks so much @fahadh4ilyas !
Can you elaborate more? What do you mean exactly by

Is it okay if the test checking the compatibility of transformers with HQQ first?

Awesome work @fahadh4ilyas 🙏!

Looks good thankks ! One last comment left, can you make sure the tests you designed pass with transformers built on main?

 Here is the revision.


SLIM-900 Implement selective access for Load Profiles

SonarQube analysis reported 2 issues

 2 major

Watch the comments in this conversation to review them.
1 extra issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 ObisCodeValuesDto.java#L71: Reduce the number of conditional operators (5) used in the expression (maximum allowed 3).

All is well.

SonarQube analysis reported 2 issues

 2 major

Watch the comments in this conversation to review them.
1 extra issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 ObisCodeValuesDto.java#L71: Reduce the number of conditional operators (5) used in the expression (maximum allowed 3).

All is well.

SonarQube analysis reported 2 issues

 2 major

Watch the comments in this conversation to review them.
1 extra issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 ObisCodeValuesDto.java#L71: Reduce the number of conditional operators (5) used in the expression (maximum allowed 3).

All is well.


How do I optimize the connection between the collector and es?

Please answer these questions before submitting your issue.

Why do you submit this issue?
[✅ ] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?
How do I optimize the connection between the collector and es?

Bug

Which version of SkyWalking, OS and JRE?
skywalking ：5.0.0-GA aliyun ecs. ip:<IP_ADDRESS>
The jar package: aliyun ecs. ip:<IP_ADDRESS>
ElasticSearch version: 5.5 aliyun es server
jdk :1.8.0_171

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.

Question1:I read this article https://github.com/SkywalkingTest/Agent-Benchmarks/blob/master/README.md ,But I did not find the collector configuration connection es part, is it the default configuration?

Question2:When I used jmeter to test, the CPU was stable around 25-30 without probes. After adding probes, the CPU in the first test could reach 100 in the first few minutes, and then dropped to about 35-40. The second test was normal, and there was no peak value, was it because of preheating? How do you optimize this?

Requirement or improvement

Please describe about your requirements or improvement suggestions.

Question1:I read this article https://github.com/SkywalkingTest/Agent-Benchmarks/blob/master/README.md ,But I did not find the collector configuration connection es part, is it the default configuration?

This article is using mock backend for performance tests, nothing about backend.

Question2:When I used jmeter to test, the CPU was stable around 25-30 without probes. After adding probes, the CPU in the first test could reach 100 in the first few minutes, and then dropped to about 35-40. The second test was normal, and there was no peak value, was it because of preheating? How do you optimize this?

First, the agent will make CPU a little higher in the first minutes, maybe because

More classes(agent's) loaded into JVM.
Instrumentation(change binary codes) in runtime costs CPU
The first few times access, trigger agent class loader working.
Some JIT works triggered.

@wu-sheng I am worried about whether this online service will kill the previous online service directly, because the CPU is really high.
In addition, do you have real tests instead of mock tests?

I don't understand what you are saying. Which online service?
What is your question? What do you mean kill?

Mock tests are for isolate backend and agents tests. They are real tests.

Can I understand it this way? Does it mean that you only tested the performance difference between agents or not? The collector and es are not in the scope of the test at all

Yes. That depends on Elasticsearch cluster scale and performance. You could learn it from many places.


trakt.tv scrobble

add trakt.tv api

projects to look at:
https://github.com/pouyio/twiso?tab=readme-ov-file
https://github.com/kdemoya/nodeless-trakt
https://github.com/trakt-tools/universal-trakt-scrobbler

make a seperate project for this, make it ez to use on other sites. get me the stars

did some testing, will be very tough to implement and will have many issues. thats probably why no other sites have it.


Coverage report in xml

Current coverage is 46.41%

Branch #6 has no coverage reports uploaded yet.

No diff could be generated. No reports for master found.

Powered by Codecov. Updated on successful CI builds.


Remove output parameter from sf::Image::saveToMemory

Description
This is a textbook use case for a std::optional return value. This operation might return a buffer or it might not. It depends on whether the inputs are valid.

sf::priv::ImageLoader uses output parameters a fair bit as well. If we like this idea then maybe I can add more similar changes to this PR.

It is now impossible to reuse or reserve vector memory upfront to save some memory allocations. No big deal I guess but I just wanted to point it out.


addon template

Signed-off-by: zhujian<EMAIL_ADDRESS>

Hi @deads2k Thank you for reviewing this, the comments have been addressed, could you help to take another look?

Hi @deads2k Thank you for reviewing this, the comments have been addressed, could you help to take another look?

A couple minor comments.  The examples here are great.

lgtm

/approve
/lgtm


Testing actions branch checks

TEST PULL-REQUEST.
I think that the current GitHub Actions branch check should also fail on forked repositories (incorrectly) when making a PR to master from a branch other than dev or patch. Just testing this here.
If I'm right and it does fail, this is fixed in https://github.com/nf-core/tools/pull/554

Oops, made this from dev 🤦♂


Result priority preference

📝 Provide a description of the new feature
What is the expected behavior of the proposed feature?  What is the scenario this would be used?

I hope there's some configurable preference for setting priorities of results in PT run.
For example, I can set the priority of "launch an application" to high, so when I type, say "VSCode", in PT run while there's running instances of VSCode, the result of launching a new window of VSCode will be the first one, rather than switching to the exist VSCode window. Or conversely, set the priority of "switch to a window" to high to make switching to an exist VSCode window always shows at the first place, so I can use PT run as a perfect windows switcher as an instead of alt+tab.
If you'd like to see this feature implemented, add a 👍 reaction to this post.

hi @FlyinCow, great idea! we're tracking this, closing this as a duplicate issue #3169


Enable fedora QEMU/Vbox/OVA on CI

It's currently disabled due to failures that have to be yet investigated. Currently we just build docker images and ISO.

Fedora is not a focus currently


Migrate application settings to model

This PR addresses (or at least attempts to address :) ) https://github.com/OWASP/django-DefectDojo/issues/215.
It adds the model "System_Settings" for keeping system settings in the database, along with views and forms to change them in the web UI.
Also changes have been made to all components using these settings so that they refer to the settings from the model rather than settings.py.
Settings that have been added to the model and migrated in the application are:

Enabling/disabling findings deduplication (ENABLE_DEDUPLICATOIN)
Enabling/disabling JIRA integration (ENABLE_JIRA)
Enabling/disabling S finding severity naming (S_FINDING_SEVERITY_NAMING)
Specifying URL prefix (URL_PREFIX)
Specifying timezone (TIME_ZONE)
Specifying team name (TEAM_NAME)

Settings that are missing from this PR that were part of the original issue:

Mail Server - from what I understand this is used internally by Django so might require another approach to get to work?

Caveats:

Setting url_prefix and time_zone in the web UI needs a restart to take effect.
If the specified url_prefix does not point to a valid defectdojo instance this will render the web UI unusable and correct url_prefix needs to be set directly in the database.
Database will be populated with default settings using a fixture on a new install but I haven't written anything to migrate existing settings in settings.py automatically.

There's, uh, also a couple of additional commits related to look and feel + bug fixes:

I changed the behaviour for help_text to be displayed as a popover over a question mark next to the field name.
The report builder's functionality to add hidden inputs when a user has tried to apply filter terms wasn't marked as safe so was HTML escaped, so any filter terms the user entered would not be applied to the generated report. Fixed by escaping individual parameters from the original query string but marking the final output as safe.
The search was throwing an error due to wrong watson property being called. Fixed by calling the correct property instead. :)

I'm used to straight and honest PR feedback so don't hold back - I'm new at contributing to this project and I'm sure I've gotten a thing or two wrong.

@patriknordlen thank you so much for doing this! Will clone and review shortly.

@patriknordlen just wanted to provide an update. Will be able to clone and review on Wednesday

Cool! Don't sweat it :)

Hi @patriknordlen thank you again for working on this!
The only thing I think would should add is a section in upgrades on readthedocs documenting what folks should due to upgrade their installs https://github.com/OWASP/django-DefectDojo/blob/master/docs/upgrading.rst. I think we should put a date entry so it is easier for people to see in a separate section such as:

July 5th
load the systems settings fixture `python manage.py loaddata system_settings.json'
remove the following from settings.py
I'm happy to merge as is though and due the documentation if that is confusing / you don't want to :)
Also if you would like dojo swag as a reward for knocking this out please email<EMAIL_ADDRESS>with the address to mail to.

Thanks for the review! I'll go make the documentation changes tomorrow and submit, so let's do the merge after that. :)

@devGregA documentation added - please have a look.

There, done!

@patriknordlen merged :)


List if subtitles are already present

Currently, when searching normally we get something like these:
0 subtitle downloaded for Brooklyn.Nine-Nine.S03E23.720p.HDTV.x264-AVS.mkv
0 subtitle downloaded for The.Flash.2014.S02E18.720p.HDTV.X264-DIMENSION.mkv
0 subtitle downloaded for Supergirl.S01E20.720p.HDTV.X264-DIMENSION-BUYMORE.mkv
However, some of them already previous have subtitles, and it would be great to know if those files already have the external/embedded subtitle in them already, so we don't attempt to redownload the subtitles again. I'm hoping if more information is present, or don't even show 0 subtitle downloaded text if they have no need to download. i.e. to show the user difference between 0 download due to subtitles not uploaded, or if subtitles are already detected to be present.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Fixed by 7b55bc0196247e7911a7e12e456adbf5e0c985c1
subliminal --debug download --provider opensubtitles --refiner tvdb --language en "Charmed (2018) - s01e08 - Bug A Boo.mkv"
DEBUG:subliminal.cli:Collecting path Charmed (2018) - s01e08 - Bug A Boo.mkv
DEBUG:subliminal.core:Found subtitles {'Charmed (2018) - s01e08 - Bug A Boo.en.srt': <Language [en]>}
DEBUG:subliminal.core:All languages set([<Language [en]>]) exist
0 video collected / 0 video ignored / 0 error


Non case sensitive

Hi @roshanrahman ,
Could you please make the censor words non case sensitive?
For now, it will censor word f*** but not F***.
Thank you!

Hi @jasonlaw, that's a good idea to provide a non case-sensitive option right in the Filter itself. Meanwhile, you can get similar functionality by passing the string to the filter methods converted to lowercase, like so: 'my string here'.toLowerCase()

Hi @roshanrahman,
I am afraid passing lower case to the filter method doesn't meet my requirement. We need to maintain the original capital case if it is not being censored.
Looking forward for this feature to be built into the filter method.
Thank you very much for this great package.


AutoMoq throws NU1602 Warning in VS2019

When compiling using VS2019, I'm getting the following warning:
Warning	NU1602	AutoMoq 2.0.0 does not provide an inclusive lower bound for dependency Moq (> 4.0.0). An approximate best match of Moq 4.0.10827 was resolved.

install Unity 4.0.1 Install-Package Unity -Version 4.0.1


Fixes parsing of environment dictionary keys

https://github.com/docker/libcompose/issues/296
Verified that this fixes parsing environment dictionary.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "yaml-fix" git@github.com:janeczku/libcompose.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "yaml-fix" git@github.com:janeczku/libcompose.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

I think keys with missing values should be converted to just the key name (VAR, not VAR=). This matches how the feature works when environment variables are specified as an array. Thanks for catching this issue! :smile:

@joshwget Updated the PR to use just the key name without separator (=).

Awesome! LGTM.

I'll check the build locally (we're having some trouble with the CI… it takes time to run and it's failing for some weird reason :sweat: )

LGTM :wink:


cherry-pick(refactor): decouple udevevent from controller

List of PRs included:

https://github.com/openebs/node-disk-manager/pull/609

Codecov Report

Merging #614 (3ca42ef) into v1.6.x (dc2311c) will decrease coverage by 0.90%.
The diff coverage is 19.51%.

@@            Coverage Diff             @@
##           v1.6.x     #614      +/-   ##
==========================================
- Coverage   47.60%   46.70%   -0.91%
==========================================
  Files          79       78       -1
  Lines        3720     3781      +61
==========================================
- Hits         1771     1766       -5
- Misses       1789     1856      +67
+ Partials      160      159       -1

Impacted Files
Coverage Δ

cmd/ndm_daemonset/controller/probe.go
100.00% <ø> (ø)

cmd/ndm_daemonset/probe/mountprobe.go
20.21% <0.00%> (ø)

pkg/udev/common.go
87.30% <ø> (ø)

cmd/ndm_daemonset/probe/udevprobe.go
51.04% <13.55%> (-10.71%)
:arrow_down:

pkg/udevevent/monitor.go
29.29% <25.39%> (+2.76%)
:arrow_up:

cmd/ndm_daemonset/probe/addhandler.go
73.37% <0.00%> (+2.04%)
:arrow_up:

Continue to review full report at Codecov.

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


Rename Some ListView Files and Classes

ie DatabaseTableListView and probably AdminListView, as insertView and updateView are not list views. There should probably be a getListView() or similar instead of indexView()

renamed DTLV to DTV, left ALV as it only contains list view functionality.


copyrights transferred from Tavendo to Crossbar.io Technologies

Current coverage is 56.49% (diff: 100%)

Merging #751 into master will not change coverage

@@             master       #751   diff @@
==========================================
  Files            69         69
  Lines         11202      11202
  Methods           0          0
  Messages          0          0
  Branches       1736       1736
==========================================
  Hits           6329       6329
  Misses         4319       4319
  Partials        554        554

Powered by Codecov. Last update 06d1ed0...b6a224a


[FORMATS-144] Move genotype likelihood fields to doubles.

Resolves #144.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/bdg-formats-prb/164/
Test PASSed.

Thank you, @fnothaft


Ring Smart Lighting Support

Just wondering if this plugin will gain the new smart lighting support.

For anyone interested in Ring Smart Lights, I have them integrated in my homebridge-ring-alarm plugin https://github.com/dgreif/ring-alarm/tree/master/homebridge

This plugin is now DEPRECATED... you will find a vastly superior plugin here!


fix(python-multi-declaration-inline): fix python multi declaration support for inline var

@teddylear
After playing around with it for a bit, this is what I came up with to address #219. Feels a bit hacky to me, not sure if there's a better way to do this. Let me know what you think!

Cool, thanks for the review!


Added ContextualMenu documentation

Q
A

Bug fix?
[ ]

New feature?
[ ]

New sample?
[ ]

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
Guidance

You can delete this section when you are submitting the pull request.
Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to dev branch.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: mmsharepoint sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #57   +/-   ##
=======================================
  Coverage   78.38%   78.38%
=======================================
  Files          10       10
  Lines         347      347
  Branches       72       79    +7
=======================================
  Hits          272      272
  Misses         55       55
  Partials       20       20

Continue to review full report at Codecov.

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

Accidentally not targeted to DEV


Cannot change color of ActivityIndicator on iphone5c

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment

  React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: x64 Intel(R) Core(TM) i5 CPU       M 540  @ 2.53GHz
      Memory: 48.68 MB / 8.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 9.10.0 - /usr/local/bin/node
      Yarn: 1.3.2 - /usr/local/bin/yarn
      npm: 5.6.0 - /usr/local/bin/npm
      Watchman: 4.7.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
      Android SDK:
        Build Tools: 23.0.1, 23.0.2, 23.0.3, 24.0.0, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.0, 27.0.1, 27.0.2, 27.0.3, 28.0.3
        API Levels: 23, 24, 25, 26, 27
    IDEs:
      Android Studio: 3.1 AI-173.4720617
      Xcode: 10.0/10A255 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.0-alpha.8af6728 => 16.6.0-alpha.8af6728
      react-native: 0.57.3 => 0.57.3
    npmGlobalPackages:
      react-native-cli: 2.0.1
      react-native-create-library: 3.1.2
      react-native-git-upgrade: 0.2.7
      react-native-rename: 2.2.2

Description
I recently upgraded from react-native 0.48.3 to react-native 0.57.3. After upgrade ActivityIndicator is not reflecting the colour I pass as props. It is taking default colour which is GRAY.  This is happening only on iPhone 5c.  I tried checking on other models using simulator and it works fine over there.
Here is the common code which I am using for my application :-
const WealthyActivityIndicator = function ({style, color}) {
  return (
    <ActivityIndicator
      animating
      color={color || "blue"}
      style={[styles.loader, style]}
    />
  );
};

We still have clients on this particular model of iPhone so wanted to get it working on this. Can someone please tell why is this breaking and how to fix it? TIA

I have the same issue on Iphone 5 as well

Suffering from this in the version 0.57.8


❗ Announcement to you guys who love this module

I'd like to say to you, appreciate to visit here.
First time I made this module, I didn't expect this popular.
As independent developer, there's many other projects to do currently.
As time goes by, I couldn't spent a time to the 'react-scroll-motion'.
So I'd like to you guys make pull-requests and discuss of it (if you wanna do!)
Maybe this way is best way at now, I guess.
Sincerely appreciate it! ♥

I'm so lucky to find your module randomly on npm. It's saved me so much time in building my portfolio. Thank you!
I also have some ideas, which I will share with you when finishing my portfolio :)))

@NB071 I'm so glad that I can help you! Hope you do everything well on your career :)
I'm more willing to get some ideas any time


[BUG] Conversion of univariate series to Sktime format for shapelet  discovery

Describe the bug

To Reproduce

<Paste your code here>

Expected behavior

Additional context

Versions

Hi I am trying to use shapelet transforms with SkTime, I have a univariate series in a pandas format as in the screen shot, trying to convert it to Sktime format as per the documentation, keep getting errors, tried adding default columns such as caseID etc but got an error : duplicate entries, any help on how to convert this to SkTime format. Stuck on this for several days now.

Thanks!

hi, this looks like a problem with from_long_to_nested rather than shapelets?

hi, this looks like a problem with from_long_to_nested rather than shapelets?

Yes that is correct, this is the same issue while converting data for  some of the other transformers, little guidance or help on the input data format will help open up this entire awesome library for us. Also what is the kind of input you are expecting for shapelets? a pre-discovered set of data with time and location or will a single time series sensor data will do? Thanks !

Shapelets require multiple series and class labels. I'm not really sure about the long format or do I know anyone else who is, but the easiest format is probably a 3d numpy array of shape (n_series, n_dimensions, series_length) if your series are equal length. Since your series is univariate, n_dimensions would just be 1. The labels can just be a 1d numpy array.

thanks ! let me try with this configuration

I don't think this needs to be an open issue any more? I will give it a bit to see if there is any response/concerns still.


Update slick-pg, slick-pg_circe-json to 0.22.1

About this PR
📦 Updates

com.github.tminglei:slick-pg
com.github.tminglei:slick-pg_circe-json

from 0.21.1 to 0.22.1
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.tminglei" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.tminglei" }
}]

labels: library-update, early-semver-major, semver-spec-minor, commit-count:1

Superseded by #390.


haskell.compiler.ghcjs: fix build

Fixes https://github.com/NixOS/nixpkgs/issues/208812
Apply a patch from upstream ghcjs/ghcjs/ghc-8.10 (not yet present in the obsidiansystems fork we follow) to fix a build failure caused by an emscripten update.
As the patch itself modifies patches that are used during configuration (by makePackages.sh), it must be applied in the configured source derivation.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@ofborg build haskell.compiler.ghcjs

Why not contribute the necessary commits to ghcjs upstream?

To be clear, the commit 9fc935f2c3ba6 is a revert commit (of e4cd4232a), the other commits on the fork have already been merged upstream.
Whether this commit should be reverted from upstream is not very clear to me, but I have opened an issue https://github.com/ghcjs/ghcjs/issues/809
It may be good to patch this single revert commit, and use the upstream branch.

BTW, I tried compiling the latest upstream branch ghc-8.10 (commit b7711fbca7 ), and it did not work out of the box. Failed with compilation error in ghc. So there will be some work involved in getting it to work.
ghc/compiler/ghci/ByteCodeAsm.hs:387:39: error:
    • Variable not in scope: bci_PUSH_ALTS_T :: Word16
    • Perhaps you meant data constructor ‘PUSH_ALTS_T’ (imported from ByteCodeInstr)
    |
387 |                                  emit bci_PUSH_ALTS_T


Fix origin access identity

Reference: https://trello.com/c/Tl3gRJxc/1021-cloudfronts3origin-module-defaults-to-being-updated-on-every-run and https://github.com/rackspace-infrastructure-automation/aws-terraform-internal/issues/159

Add conditionals around cloudfront distribution depending on whether or not an origin access identity has been provided.
Modify variable outputs to support resource conditionals.

Have tried setting the s3_origin_config to an empty list instead of creating a separate resource? Something similar to what we have done in other modules.
Swapping between resources like this for a change that should be non destructive worries me, and presents a real risk of unintended downtime.  I just want to make sure we have explored all options before going down this road.

I tried and the module kept complaining that it wasn't set.


Include non-imported assets in deployments

Describe the problem
A reasonably common pattern is for an endpoint to depend on files in the project directory that aren't visible to Vite because there's no import declaration involved — for example database.sqlite or documentation/getting-started.md. These endpoints work during development and in local preview, but as soon as the app is deployed they break, because the files are not included in the build.
Describe the proposed solution
Something like this:
import marked from 'marked';

// src/routes/documentation/[slug].js
export async function get({ params }) {
  const markdown = await import.meta.load(`documentation/${params.slug}.md`);

  return {
    body: marked(markdown.toString())
  };
}

This uses import.meta.load because it's easy to statically analyse and replace with an environment-appropriate implementation. In this case, we see that it's called with the expression `documentation/${params.slug}.md`, and we can easily turn that into a list of files in the project directory that match /documentation\/.+\.md/. An adapter creating lambdas can simply include those files in the function directory and provide a promisified fs.readFile implementation; an adapter creating a Cloudflare Worker could put the file in a KV store and provide an implementation that reads from it.
In some cases, an adapter might not have a way to read those files, and would be able to throw an error at build time rather than failing cryptically at runtime.
We can restrict the expressions that import.meta.load accepts to template literals and string concatenations.
Slightly related: #3850
Alternatives considered
Next.js solves this problem with the (unfortunately-named!) nft package. It statically analyses the build output and figures out which files are needed, including dependencies in node_modules that weren't included in the bundle and assets that are read from the filesystem.
Since static analysis is inherently limited, code needs to be written a certain way for files to be correctly located. nft's static analysis is very good — you can do this...
const cwd = process.cwd();
const file = path.resolve(cwd, `documentation/${slug}.md`);

...and get a list of dependencies that includes all the .md files in documentation. But you can't do this...
const contents = fs.readFileSync(`documentation/${slug}.md`);

...or this...
import { cwd } from './shared.js';
const file = path.resolve(cwd, `documentation/${slug}.md`);

...or this:
import { read } from './utils.js';
const contents = read(`documentation/${slug}.md`);

In addition, since we're using things like path and process, this can only work in Node-like environments, when ideally a SvelteKit app should happily render in an edge function.
This leads me to the conclusion that we're better off using something less idiomatic that will only work if you adhere to the 'rules', and which could theoretically be used across different environments.
It might still be useful to use nft to find external node_modules (in particular native dependencies that can't be bundled by Vite), so that they can be included in lambdas without further configuration. But that's a separate issue.

Another possibility is to use some sort of explicit configuration. Aside from being something of a burden (that doesn't solve the cross-environment problem), it would be difficult to come up with an API that works with function splitting (and doesn't result in all your documentation/*.md files being bundled with unrelated routes).

Finally, because someone is going to suggest it, I don't think we should do this:
import { load } from '$app/fs';

const db = await load('database.sqlite');

This takes us into an uncanny valley where load is sort of a normal function but not really — it looks like you should be able to memoize it or pass it somewhere as an argument, but you can't (at least not without breaking the static analysis guarantees we need).

One thought: if Vite were to start using import.meta.load for something else, it could cause a problem. We could namespace it as import.meta.sveltekit.load but that feels slightly excessive.

How about new URL('./asset.txt', import.meta.url) which is supported by @vercel/nft and other static analysis?

Another suggestion in Discord was to use Vite's existing import.meta.globEager:
+import { load } from '$app/fs';
import marked from 'marked';

+const files = import.meta.globEager('../../documentation/*.md?url');
+
// src/routes/documentation/[slug].js
export async function get({ params }) {
-  const markdown = await import.meta.load(`documentation/${params.slug}.md`);
+  const file = files[`../../documentation/${params.slug}.md?url`];
+  const markdown = await load(file);

  return {
    body: marked(markdown.toString())
  };
}

Pros:

Files can be transformed by Vite plugins
Uses existing idioms
Relative paths are nicer in some situations

Cons:

More verbose
Relative paths are less nice in some situations

To add on the cons, a glob having ?url probably won't work as Vite treats it as a glob pattern naively. This could be improved in Vite though. Also, aliases should work too, like import.meta.glob('$lib/docs/*.md')

I just wanted to mention that Vite features provides importing different type of files in different format.
For example, you can import JSON files directly:
// import the entire object
import json from './example.json'
// import a root field as named exports - helps with tree-shaking!
import { field } from './example.json'

Load assets as strings:
// Load assets as strings
import assetAsString from './shader.glsl?raw'

Vite also supports importing multiple modules from the file system via import.meta.glob function:
const modules = import.meta.glob('./dir/*.js')

And all work on the current SvelteKit.

Would be great if assets in endpoint dirs were automatically added to the bundle. If I have different banner.svgs for all routes in a directory and the +layout.svelte has a
<img src="{slug}/banner.svg" alt="banner" />

it works in dev but errors in build.

Has there been any progress on this? I am currently generating docs and news from markdown files. Works perfectly in dev but ran into the same issues once deploying to Vercel.


Md-list breaks when using with ng-container or ng-template

Bug, feature request, or proposal:
Bug, mdlist & md-nav-list breaks when used with ng-container or ng-template.
What is the expected behavior?
https://i.imgur.com/Iv6pc7q.png
What is the current behavior?
https://i.imgur.com/ca4MC8K.png
What are the steps to reproduce?
<md-nav-list>

Tests

			<ng-container [SubComponent]="test">
			</ng-container>

	</md-nav-list>

Dynamic component or template:
	<md-icon md-list-avatar fontIcon="fa-clock-o"></md-icon>

Time Period

Queries data from cool

Where right now subcomponent is a custom directive that is just a component factory dynamically loading components into the list based on the data repeated # in *ngFor
What is the use-case or motivation for changing an existing behavior?
It doesn't work like most of the things in material2.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Probably all of them.
Is there anything else we should know?
No.

Isn't this an Angular issue?

How would it be an angular issue? Thought md-list & md-nav-list isn't part of angular.
The display breaks because the md-list adds some custom dom & css classes when compiling.

@azarus, I went for an Angular issue, because, by design, ng-template was suposed to work without interfere in the layout (and in Angular docs there are no conditions specified for it to work nor exceptions that would make it brake). Anyway, it's a very superfitial gess of mine as Angular docs itself are still being improved.

Looks like a side-effect of content project only working at the top-level.
list-item content projection
Related discussions:

https://github.com/angular/material2/issues/5263#issuecomment-309916427
https://github.com/angular/material2/issues/5292

It seems like this open issue in angular core (https://github.com/angular/angular/issues/8563) would help in this case, but I'm not certain.

I guess it breaks since the viewchild is not there when the component is being initialized and the dynamic component is not initialized just yet. So the actual content the list is inteded to work with doesn't exists. And there fore it does not sets up the required classes and divs. Probably the best fix would be to make the child elements send a norification to the parent components and request an update on the view.

This is the expected behavior based on how content projection works in Angular; the API for the list calls for the md-line to be a direct child of the item.

@jelbourn my personal user experience is horrible with material2 man

@azarus, as @julianobrasil points out here, you can use ngProjectAs to project whatever you want.
Annoyingly, there doesn't seem to be any official documentation on the subject, but there is a pretty good Medium post on it: https://medium.com/claritydesignsystem/ng-content-the-hidden-docs-96a29d70d11b

Thanks, we hired a second developer to speed up the development of our new frontend since these small issues we found during porting our old code to angular2 just cause huge delays and consume our resources to sort out. We'll check on it.

ok, i just found a workaround:
<mat-list-item>

    <ng-container *ngTemplateOutlet="myTemplate"></ng-container>

</mat-list-item>

to enable mat-multi-line styling (so the item gets css auto height) you have to put 3 dummy matLines:


bench: workload execution type

Add two subcommands to the bench command to enable the following functionalities:

Isolate benchmarking by executing each workload on a copy of the initialized backend
Sequential benchmarking by continuously repeating workloads on the same backend until a specified time or operation limit is reached

The possibility of manually interrupting the execution is out of scope for this PR because it would require some new dependencies (handling ctrl+c), therefore, it will be implemented separately in a follow up pr

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#160  👈
#154
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gabriele-0201 and the rest of your teammates on  Graphite


[#31] [iOS] [UI] As a user, I can see a list of surveys on the home screen

Resolves #31

What happened 👀
Implemented the home screen with a survey lists view.
Insight 📝
From the beginning, I tried with the TabView component instead, but after checking the Figma, I decided to go with adding left right gesture, then update the content based on user actions.
Proof Of Work 📹
https://user-images.githubusercontent.com/19943832/202677751-4617cb81-b12d-4a8f-8ccf-426b44fd132e.mp4

@nkhanh44 Currently, we don't have the sign-out feature, so I prefer to keep the current approach. I will improve later when having the sign-out feature


docs: add WIP readme overhaul

:construction_worker: Purpose
The readme was lacking when it comes to manually setting up Temporal. Closes https://github.com/RTradeLtd/Temporal/issues/389
:rocket: Changes

Update the readme with new sections on installing Temporal.
Adds a script that can be used to build Temporal entirely from source
Adjusts the location the docker-compose file mounts to in order to be more compatible with where the docker image looks for stuff.
Update makefile install target

:warning: Breaking Changes
None

@NukeManDan If you have any input feel free to comment :rocket:


Replaces JibLogger with EventEmitter in RetrieveRegistryCredentialsStep.

Part of #714

Adds a LogEvent that replaces the logging originally done by the JibLogger interface.
Adds a new TimerEvent and accompanying TimerEventEmitter to emit timer events to handle durations
Has RetrieveRegistryCredentialsStep emit LogEvents rather than call JibLogger interface
Has RetrieveRegistryCredentialsStep emit TimerEvents rather than log timing debug messages
Sets the appropriate logback methods on the Maven/Gradle side to handle the LogEvents and TimerEvents
TODO in followup PRs: Replace all uses of JibLogger with emitting LogEvent/TimerEvent and remove JibLogger.

As suggested, reorganized the timer classes by adding TimerEvent and moving the log message generation for the TimerEvents to plugins-common.

Merged master.


[SwiftLanguageRuntime] Be more defensive in face of broken ASTcontexts.

If we have errors, there's no point in keep going, so just stop.
Partially backports a change already on stable.
rdar://problem/42048145

@swift-ci test and merge

This handles my crash

There was another use in FindFunctionPointersInCall that gets the swift_ast and checks that it is not null, but doesn't check !HasErrors.
And GetBridgedSyntheticChildProvider gets types from the scratch SwiftASTContext and only checks !null, it doesn't check !HasFatalErrors.
If we're being complete you might want to fix those two uses as well.


Add example for identification of last stable release to schema guide

Related issues
Refs: #382
Describe the changes made in this pull request

Add an example for a url identifier pointing to a stable release of the work

Review checklist

[ ] Please check if the pull request is against the correct branch
(format/schema/semantic documentation changes: develop; typos, meta files, etc.: main)
[ ] Please check if all changes are recorded in CHANGELOG.md and adapt if necessary.
[ ] Please run tests locally.

cd $(mktemp -d --tmpdir cff.XXXXXX)
git clone https://github.com/citation-file-format/citation-file-format .
git checkout <branch>
python3 -m venv env
source env/bin/activate
pip install --upgrade pip wheel setuptools
pip install -r requirements.txt
pytest
<do other things>

[ ] Check place and content of documentation change

This supersedes #387. I'll also dissect #387 to provide the fixed in it in separate PRs. No idea what happened there, sorry.

Closing, as there will always be a bleeding edge in a repo, and it's really hard to keep any "last" or "latest" persistent version up-to-date.


Event forwarding not working

Event forwarding on native components doesn't seem to work. In the example below Button should be forwarding the tap event so that App can listen to it but when the button is tapped nothing happens.
Button.svelte
<button on:tap>Tap me</button>

App.svelte
<page>
    <Button on:tap={() => console.log('tap')} />
</page>

<script>
    import Button from './Button.svelte'
</script>

Thanks for the report 👍
This has been fixed and deployed in svelte native 0.8.1
The problem was nativescript events use "event.eventName" to dispatch, but svelte uses "event.type". I had a workaround for direct listeners, but the bubble logic wasn't patched.

@halfnelson This still seems to be not working

I can't seem to reproduce with the latest version.
https://svelte-native.technology/repl?version=3.19.2&gist=3fff1d0f0a1a4722845ae6183cfbd081
Do you have a way to reproduce the problem?

Oddly enough looks like it does work for button but, as you'll see below, there are cases it doesn't. For example tapping on a button.
repl
(Note: I tested locally as the repel just hangs on "Connecting...")

I gave it a good dig, and found that gestureEvents on views have their own dispatch mechanism and don't use observable.notify (which I was monkey patching), I found a more elegant way to address this  and shipped 0.8.2 . Your example now works :)

It does appear to be working. Thank you!


Not working as expected on IE

Hi
I'm having problem using flexbox on IE9. Here the scenario:

I'm using postcss flexibility in order to get the -js- prefix.
I'm using bower to get the latest version of flexibility.js which I place just before the end of my  tag. The version I'm using is 1.0.6.

Here my HTML:

Donec ullamcorper nulla non metus auctor fringilla. Nulla vitae elit libero, a pharetra augue. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean lacinia bibendum nulla sed consectetur. Etiam porta sem malesuada magna mollis euismod. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur.

Donec ullamcorper nulla non metus auctor fringilla. Nulla vitae elit libero, a pharetra augue. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean lacinia bibendum nulla sed consectetur. Etiam porta sem malesuada magna mollis euismod. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur.

As you can see there is one parent and 2 childs.
Here my scss:
.flexer {
    display: flex;

    div {
        flex: 1;
    }
}

The output of my scss gives me a -js- prefix but on display: flex only, not on flex: 1.
They divs are one next to each other but they seem to go out of my browser edges, the container doesn't wrap them.
Any idea why?
Also, I tried to use your walk() function but it looks like isn't working at all. The error I'm getting is the following:
Unable to get value of the property '-js-display': object is null or undefined
Thanks

I'm getting this same issue. Anything?

Anyone? Still not working for me! @mphillips @roXet @avpitre @pcrumm maybe?

@jonathantneal any ideas?

The issue here is that flexibility was built for IE and it needs to be more browser agnostic, as the use cases have exploded since this was released.
I spent two weeks re-writing all of the flex calculations based on the spec, including how to handle things like margin auto, which I really wanted to use. It was an intense endeavor and I did it, but it burned me out and made a bit fearful to return to the codebase.
This might be the first time you’ve read of me asking for help to finish it, but I really do need the help. It’s more information than I can process at a time. The calculations are complete. I lose the ability to piece things together once I dive this deep in. If you know anyone who can help, please let me know. I’d love to have flexibility v2 released so people can safely use Flex to its full potential.
And sorry to anyone who sees this and wondered why I stopped being active here.