[Enhancement] Integrate Prometheus and Grafana for monitoring in playground

Description:
To improve the project's observability and monitoring capabilities, it is suggested to integrate Prometheus and Grafana into the playground environment. This would enable easier monitoring of various application metrics.
Objectives:

Prometheus: For collecting and storing application metrics.
Grafana: For visualizing data collected by Prometheus, providing the team with real-time monitoring dashboards.

Implementation Approach:

Add Prometheus and Grafana configurations within the Docker environment.
Set up basic metrics collection, such as application request rate, response time, etc.

I would like to take on this task. I'll start by setting up Prometheus and Grafana within the Docker environment and configuring the basic metrics collection as described. Please let me know if there are any specific requirements or guidelines you'd like me to follow.


Button is not triggering Alexa

Thank you for reporting an issue with AlexaPi.
Make sure you are running the latest version of AlexaPi, and look through issues before submitting.
Check out our Wiki, and make sure to look at Debugging, and Audio debugging in particular before filing an issue.
In order to help troubleshooting, be sure to include the following information:
Output of the audio debugging script.
-- Logs begin at Sat 2017-07-29 20:13:15 PDT, end at Sat 2017-07-29 20:24:59 PDT. --
Jul 29 20:13:19 Bacon321 systemd[1]: Starting Alexa client for all your devices...
Jul 29 20:13:19 Bacon321 systemd[1]: Started Alexa client for all your devices.
Jul 29 20:13:28 Bacon321 python[531]: INFO: Checking Internet Connection ...
Jul 29 20:13:28 Bacon321 python[531]: INFO: Connection OK
Jul 29 20:13:28 Bacon321 python[531]: INFO: AVS token: Requesting a new one
Jul 29 20:13:29 Bacon321 python[531]: INFO: AVS token: Obtained successfully

Your OS (including version) where you are running AlexaPi:
Linux Bacon321 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l GNU/Linux

Your hardware platform and model you are running on:
raspberryPi 3

Python release (python2 --version):
Python 2.7.9

Description of problem:
I installed a button and it is not triggering Alexa

Expected:
Alexa should trigger

Problem-relevant config.yaml entries:

triggers:
  platform:
    enabled: true
    voice_confirm: false

    # one of: oneshot-vad, continuous, continuous-vad
    event_type: "oneshot-vad"

    # only for "continuous" event_types
    long_press:
      # system command to run after pressing the button for _duration_ number of seconds
      # empty to disable
      command: ""

      # duration in seconds
      duration: 10

      # CURRENTLY DISABLED
      # optional audio file to play before executing the command
      # you might wanna use full path to make sure AlexaPi finds it
      # you can use {resources_path} for the path to the AlexaPi "resources" directory
      audio_file: ""

  pocketsphinx:
    enabled: false
    voice_confirm: false

    phrase: "alexa"
    threshold: 1e-10

Steps to reproduce:

Traceback (if applicable):

Additional info:

I've actually got the button working but now neither of the LEDs are working.

I wonder if you made the same mistake I did.
I was having the same issue.
Turned out I hadn't realised that GPIO 18 is not the same as pin 18.
GPIO 18 is pin 12.
So you have to connect pin 12 (GPIO18) to pin 6 (GND), not pin 18 to pin 6.

Thank you! But I've actually figured it out and got it working! The issue was actually (difficult to admit), that the LEDs were dead. Should have tested them but I wasn't at all familiar with electronics. Bought some brand new LEDs and I actually got a different button as the button stopped working shortly after that post. Plugged it all in to the correct pin headers and it worked perfectly!

Seems resolved.


Update MeshUIComponent.js

The console log would provide more specific output regarding which precisely component is missing the state by logging the given name or uid of component. Recently I got thousands lines of warning but did not know which component is a reason.

Hey @sylwesterdigital , thanks for the feedback. You aren't the first to ask that kind of insight.
Idealy, it shouldn't be restricted to only this warning, but for any of them. Lets postpone that for 7.x.x
In the meantime, I have to wait to be back at my desk to merge and release this PR. Could be done saturday

This PR has been merged and released under v6.4.4
Component identification is a legitimate concern, especially during warning or error output.
I just want to let you knwow that in a couple of "time-unit?" Im gonna ask your opinions on proposal for 7.x.x. Thanks


Date constrained reports

The current service reports take all beneficiaries interacted within a time period and compare their latest results with their first ever results, essentially giving a lifetime impact result.
Create a date constrained report, where we just look at the records within a given time period, so organisations can compare year on year performance, including rate of change.
Should build on #97 and #72

 Improved reporting

Completed as part of #98


.github: Generate Code Coverage

Adds code coverage to the GitHub actions and uploads results to Codecov
Fixes: #416

Thanks @dave-tucker All the unit testing should be cleaned up in #432 So if that goes in this should become green

This also fixes https://github.com/bpfd-dev/bpfd/issues/356


How to hide pagination when there is only one page?

@Axighi, sorry there's no way. Maybe I can make this configurable, because you set pagination to true which means you want the pagination so I didn't think about this condition.

Use ignoreSinglePage on <BootstrapTable>.  Update to newest version. Thank 👍

how do I use this?

I wasn't able to hide the page number on the first page when there is only one page using the ignoreSinglePage attribute of . However, I did manage to apply this work around in case anyone else is looking for a solution:
Step 1: Give the pagination attribute a dynamic value, derived from a class method:
    createDataTable = () => {         return (             <BootstrapTable                  ...                 pagination = { this.setPaginationOptions() }                  ...
Step 2: Declare your paginationOptions object:
    paginationOptions = {         sizePerPage: 10,         hidePageListOnlyOnePage: true,         showTotal: false,         hideSizePerPage: true,         onPageChange: (page, sizePerPage) => {             this.paginationOptions.page = page;         },     }
**Step 3: Identify the number of items on your first page (e.g. store that count in state):
               this.setState({ accountCount: response.data.accounts.length });    // response.data.accounts is the result of an AJAX call in my example
Step 4: Declare the setPaginationOptions() method in your React class:
    setPaginationOptions = () => {         if (this.state.accountCount > this.paginationOptions.sizePerPage) {             return paginationFactory(this.paginationOptions);         } else {             return null;         }     }
P.S. thanks @AllenFang for creating this incredible utility!


PTZ Controls Don't work.

Hi there,
With the upgrade I noticed that now the card lets you to pan tilt and zoom the camera stream. However this doesn't work for me. I have amcrest 1041b cameras.
This is the config for go2rtc:
streams:   doorbell:      - rtsp://admin:password@doorbellcamera.asus/cam/realmonitor?channel=1&subtype=0     - ffmpeg:doorbell#audio=opus webrtc:   listen: ":8555"  # address of your local server (TCP)   candidates:     - ip:8555  # if you have dynamic public IP-address ffmpeg:   output: "-user_agent ffmpeg/go2rtc -rtsp_transport tcp -f rtsp {output}" api:     origin: "*"  log:   level: info  # default level   api: trace   exec: debug   ngrok: info   rtsp: trace   streams: error   webrtc: fatal
This is the card config:
`type: custom:webrtc-camera
entity: camera.doorbell
ui: true
mute: true
digital_ptz: true
shortcuts:

name: Show Elevators
icon: mdi:arrow-left-bold
service: switch.toggle
service_data:
entity_id: switch.doorbell_camera_show_elevators
name: Point Down
icon: mdi:arrow-down-bold
service: switch.toggle
service_data:
entity_id: switch.doorbell_camera_show_down
name: Show Right
icon: mdi:arrow-right-bold
service: switch.toggle
service_data:
entity_id: switch.doorbell_camera_show_right
`

I can only double click and zoom and nothing else. Panning and Tilting doesn't work. I'll appreciate your help.

Sorry this was a wrong post. It works as intended. I thought it would actually move the camera.


Add unlisted header option for blog posts, fixes #1393.

Previously, the blog sidebar listed the most recent blog posts sorted by
their publish date. This commit adds the ability to hide a specific blog
post from the sidebar and the feed of all blog posts by adding the
unlisted: true header option.

Motivation
The motivation for this feature is to make it possible to change dates of published posts without breaking the old URL (which might be widely shared).
Concrete example, we published a blog post two weeks ago that is dated for 2020 (https://scalameta.org/metals/blog/2020/04/12/mercury.html). We have closed three PRs fixing the date (https://github.com/scalameta/metals/pull/683, https://github.com/scalameta/metals/pull/670, https://github.com/scalameta/metals/pull/656) but they have all been closed because changing the date of the post would turn the old URL into a 404.
With the ability to unlist posts, I could unlist the 2020 post, create a new posts dated in 2019 and update the unlisted 2020 post to forward to the new 2019 post.
I'm open for alternative solutions to fix that particular problem. I think unlisting is a flexible solution that could be useful in other situations as well, for example when writing a draft post.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
I would appreciate help for testing this change since I'm unfamiliar with jest (and JavaScript in general 😅 ). I created a blog post in __test__/__fixtures__ using unlisted: true and ran yarn test and everything passed but I expected some snapshot tests to fail.
I tested the change manually on our website and it seems to work as expected:

Observe that uncommenting unlisted: true makes the post disappear from both the sidebar and the list of all blog posts while the post is still published under the unchanged URL.
Related PRs
I'm not aware of any.

Thank you for the review! I've renamed "unlisted" into "draft" and incorporated the !item.draft refactoring. Note that there is a difference between draft posts in Jekyll and how they are implemented in this PR.

Jekyll draft posts are ignored during a non-development build and they do not need a date in the filename
draft posts in this PR still require a date in the filename and are published during non-development builds, they just don't appear in the blog sidebar or main blog feed

Is there currently a way for you to view your unlisted/draft posts without toggling the flag?

Not in the current implementation. It would be nice to see draft posts during livereload development but I'm not sure how to implement that.

About unlisted vs draft. The way I would expect "draft" to behave, is not to make the post public, whereas unlisted would be published but not listed in the menu.
To summarize

status
visible in menu
published

draft
no
no

unlisted
no
yes

normal
yes
yes

For this reason, I think 'unlisted' was the appropriate name for the changes included in this PR.

Anything I can do to help unblock this issue? All of the review comments from https://github.com/facebook/Docusaurus/pull/1396#pullrequestreview-231255400 have been addressed, although I believe it's worth considering using unlisted instead of draft due to the reasons mentioned by @gabro in https://github.com/facebook/Docusaurus/pull/1396#issuecomment-487561180

cc @yangshun @wgao19


create list of working devices

I'm planning a new setup and I don't really know which ones work with this lib.
ZKTeco has many devices even in the TFT family, so it would be nice to maintain a list of working devices.

Uhm ... sounds cool
I dont have a lot of hardware, but maybe I can create a table with several models
and classify them in three categories:

Unsupported
Supported and verified (i.e. all basic tests are passing with the given device)
Supported but not verified
So this list may be constructed with contributions from the community


WFLY-17262 - Drop source transformation for jsf subsystem

https://issues.redhat.com/browse/WFLY-17262
Drop source transformation for jsf subsystem

@jasondlee CI failures look related to the PR.

@jasondlee CI failures look related to the PR.

Yup. On it.

Thanks @jasondlee


Combining data from multiple documents

I am having trouble using ldflex to query data of a resource that is spread over several documents. Let me clarify this by a concrete example querying my weblog with ldflex playground:
['https://angelo.veltens.org/profile/card#me'].foaf_weblog
Single Result: https://datenwissen.de#it :tada:
It is no problem to query the homepage of the blog as well:
['https://angelo.veltens.org/profile/card#me'].foaf_weblog.homepage
Single result: https://datenwissen.de :tada:
But this syntax does only provide data that can be found in https://angelo.veltens.org/profile/card. It does not load additional data from https://datenwissen.de
Which leads to:
['https://angelo.veltens.org/profile/card#me'].foaf_weblog.sioc_container_of
No results :sob:
I have to explicitly query like this, to get the results:
['https://datenwissen.de#it'].sioc_container_of
So my first thougt was, just do not chain properties, but this way I will not get data that is only in the first document:
['https://datenwissen.de#it'].homepage
No results :sob:
So there is no generic approach to be sure to get all data from all documents. I am not sure how LDFlex should handle this. Some quick ideas:

Load data from all resources in the chain
['https://angelo.veltens.org/profile/card#me'].foaf_weblog.sioc_container_of

So this would actually request https://angelo.veltens.org/profile/card as well as https://datenwissen.de

Cache results from previous queries

['https://angelo.veltens.org/profile/card#me'].foaf_weblog
['https://datenwissen.de#it'].homepage
So the second query would still get the homepage, because it is in the cache after the first query.

I am having the same issue. Let me elaborate on what I'm saying:
I need to fetch some data from my preferences ttl, for this, I need to first get the .ttl name
[https://joseprod.inrupt.net/profile/card#me][http://www.w3.org/ns/pim/space#preferencesFile]
Single Result: https://joseprod.inrupt.net/settings/prefs.ttl (.ttl name)
Same as with the original issue, this approach just provides data that can be found in my card.
No results when trying to fetch for [https://joseprod.inrupt.net/profile/card#me][http://www.w3.org/ns/pim/space#preferencesFile][foaf:mbox]
So I tried to go directly to my preferences ttl
[https://joseprod.inrupt.net/settings/prefs.ttl][foaf:mbox]
No results
This is where my issue is a little different, my prefs.ttl has a card:me key as a parent of all the preferences  such as [foaf:mbox], therefore, I should be accesing it differently. However, no matter what I try I end up getting no results.
Important
I'm trying this both in the playground and in a web application, I am seeing the prefs.ttl being fetch over the network tab as a plain raw turtle, so that's working.
Would be great to get all data from all documents with this sintax.
Prefs.ttl:
@prefix : <#>.
@prefix dct: <http://purl.org/dc/terms/>.
@prefix c: </profile/card#>.
@prefix terms: <http://www.w3.org/ns/solid/terms#>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
@prefix sp: <http://www.w3.org/ns/pim/space#>.

c:me
    terms:privateTypeIndex <privateTypeIndex.ttl>;
    terms:publicTypeIndex <publicTypeIndex.ttl>;
    foaf:language "en";
    foaf:mbox<EMAIL_ADDRESS><> a sp:ConfigurationFile; dct:title "Preferences file".

This issue is specifically about the Solid configuration of LDflex, and not an issue with the LDFlex language in general. I will track progress in https://github.com/solid/query-ldflex/issues/13.

I am having trouble using ldflex to query data of a resource that is spread over several documents.

Indeed, that is not yet supported in Solid's LDFlex configuration.
Solid will take the first resource of the chain (either user or data[firstResource] as the one document that should be queried).
The goal is to support link-traversal in the future, guided by shapes.
But that base infrastructure is not there yet.

But this syntax does only provide data that can be found in angelo.veltens.org/profile/card. It does not load additional data from datenwissen.de

The syntax is fine; it's just that the underlying query engine is not configured for that behavior.
To get that behavior, you would currently need to
solid.data[await ['https://angelo.veltens.org/profile/card#me'].foaf_weblog].sioc_container_of

A more advance query engine will do the above automatically.

Same as with the original issue, this approach just provides data that can be found in my card.

Also note that this is both a bug an a feature 🙂
In the sense that it is also a matter of trust.
If one of the people in my contacts card has incorrect statements about something, I do not want to assume them as true, or mix them up with true statements.
So @pablo-rodriguez-jd, you will also currently have to do it in pieces, on expression for every file, where the file consulted will be the first one mentioned in an expression (either user or the thing right after data).
This is because LDflex has no knowledge about how data is spread across files. We need to encode that knowledge into shapes.

Closing this here (LDflex language) in favor of https://github.com/solid/query-ldflex/issues/13 (LDflex for Solid).

Thanks Ruben, for your explanation.

To get that behavior, you would currently need to
solid.data[await ['https://angelo.veltens.org/profile/card#me'].foaf_weblog].sioc_container_of

A more advance query engine will do the above automatically.

But than again
solid.data[await ['https://angelo.veltens.org/profile/card#me'].foaf_weblog].homepage

would not give a result, would it? I need one approach set fits both, because the client can not know which properties are accessible at which document.

the client can not know which properties are accessible at which document.

Indeed, and neither can the query engine 🙂

I need one approach set fits both

Fully understand, and that's what we're aiming for. But getting this right is complex and requires some extensive implementation. The specific case sketched here is simple (just query the two documents), but the general case is much more difficult.

@angelo-v We now have support for multiple sources, but sources need to be explicitly listed:
solid.data.from(['https://ruben.verborgh.org/profile/', 'https://data.verborgh.org/people/joachim_van_herwegen'])['https://ruben.verborgh.org/profile/#me'].friends.name


Simplify kuksa-client docker build and reducing resulting image size

This fixes #682
On  a high level

switch to a glibc build
this reduced build times as grpc wheels exist
as a side effect the existing glibc wheels are already small
using pyinstaller only ship the parts of python necessary to run the client, thus reducing size over using a python base image

This fixes the huge size of the arm image, while at the same time even reducing the amd64 image compared to master
Arm64 size now
ttl.sh/kuksa.val/kuksa-client-ff43b39d56fff605c6330c078dea4b383cade50f        latest                 e2dce0b872fd   About a minute ago   73.1MB

I tested secure. lgtm.


waypoints should be invisible for players

i see several options here:

waypoints are kept as implementation detail and never leave the server. this has an issue that /data will be reporting current ship commands in two different formats, depending on whether the target is a waypoint or actual object, which makes it more complicated for the bots.

waypoints are visible to the player, but are filtered to contain waypoints referenced by their own ships only

waypoints have associated owner/creator and can be freely reused by the same player

The dual format is not optimal but any other option imho introduces too much unnecessary complexity.
Also the dual format has to exist anyway because players can use it when sending commands. So it seems okay to have them parse it as well.
That's why 1) seems like the best option to me.

sgtm


Sign official images with sigstore/cosign

Tell us about your request
It would be helpful to support sigstore/cosign to verify official images from Docker. This could be done in addition to other signing solutions to give users the flexibility to use their own preferred signing solution.
Which service(s) is this request for?
Docker Official Images (DOI).
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Verify the authenticity of official images. This can only be done by Docker.
Are you currently working around the issue?
Using images other than DOI or using DOI images without verifying their authenticity.
Additional context
I'll open similar issues for other signing tools.

Linking issues #561 and #563.

duplicates with: https://github.com/docker/roadmap/issues/269

duplicates with: https://github.com/docker/roadmap/issues/269 cc @dentrax

@developer-guy I meant to link that one too. I wouldn't say a duplicate, but certainly related. #269 is asking to add signing capabilities to docker build. I'm asking for Docker Official Images to be signed, which could be done by calling cosign in their build pipeline.

I changed that with related, thanks, this is more accurate 👋

Heavy +1, as a maintainer of a library image.


fix non sudo enable community addon

Summary
This PR fixes issues when non-root user in non-strict environment tries to enable community addons.
Closes #4574
Changes
added temporary setting to git to  ingnore

Testing
enabled and disabled community addon
Possible Regressions
n/a
Checklist

[x] Read the contributions page.
[x] Submitted the CLA form, if you are a first time contributor.
[ ] The introduced changes are covered by unit and/or integration tests.

Notes

I'm not too happy about this workaround, this feels like just masking the underlying issue. The safe directory wildcard also feels too wide, could we deem certain directories as safe instead of any?

How about narowing it to  $SNAP/addons/community/* ?


Fix test_recurring_jobs_when_volume_detached_unexpectedly

Remove the intermediate status check after backup resume.
Add wait for lock expiration before backupstore cleanup.

https://github.com/longhorn/longhorn/issues/2369

Test regression Build#126.


remove plotting

This removes the plotting from pyglider, and from the example processing scripts.
Thinking about the a bit more, I'm of two minds.   The plotting is a pretty decent smoktest of the data.  Maybe we will add the c-proof/cproofutils as a testing dependency.

Self merging so I can get the tests working in #82


findUnique batching performance

Bug description
I want to retrieve 10,000 accounts (by IDs) from the database.
Due to the nature of how GraphQL resolvers work, I can't simply use findMany something like
prisma.account.findMany({
  where: { id: { in: [1, 2, 3 /* ... */ } }
})

Instead, I use the findUnique inside of the resolver which gets called 10,000 times:
// inside a GraphQL resolver
prisma.account.findUnique({
  where: { id: account.id }
})

As per https://www.prisma.io/docs/guides/prisma-guides/query-optimization-performance#solving-n1-in-graphql-with-findunique-and-prismas-dataloader, it shouldn't really introduce a performance bottleneck as the findUnique calls which happen in the same tick should be batched.
From my understanding, it should be almost equivalent to calling the findMany method directly.
Interestingly, if I use the dataloader library in order to create my own batch function (in which I call the findMany method), the performance is almost the same as calling the findMany method directly:
// create a data loader
const accountByIdLoader = new DataLoader<number, Account>((ids) =>
  prisma.account.findMany({
    where: {
      id: { in: ids as number[] },
    },
  })
);

// inside a resolver
accountByIdLoader.load(account.id)

How to reproduce
Full reproduction available on https://github.com/tomdohnal/prisma-dataloader-perf
Running on my machine gives this performance metrics:

Expected behavior
I'd expect the performance of using dataloader library and calling the findUnique method to be similar
Prisma information
Available on https://github.com/tomdohnal/prisma-dataloader-perf
Environment & setup

OS: Mac OS
Database: sqlite, postgres
Node.js version: 12.4
Prisma version: 2.21.0

findFirst does no batching as its just findMany with limit 1.
But I can reproduce our dataloader implementation is slower than just using raw dataloader. We should investigate that.

I'm talking about findUnique not about findFirst :)

Alright, that part is reproducible. Thanks for reporting!

Oh now I've realised that I wasn't really clear about it. I know that findFirst doesn't do any batching. I just included the timings for it as a reference to show that findUnique is faster than findFirst but still much slower than dataloader

Any updates on this? Have there been any releases addressing this issue?

I am also having this issue, do you know if this is plan to be fix ?

Same issue. Any plans on fixing this?

I wasn't able to reproduce this on the versions specified in the issue due to errors, however, updating it to the latest versions yielded results!
yarn ts-node index.ts
yarn run v1.22.22
$ /Users/soph/src/repros/prisma-dataloader-perf/node_modules/.bin/ts-node index.ts
multiple `prisma.findFirst(...)` calls: 414.506ms
multiple `prisma.findUnique(...)` calls: 1.592s
using DataLoader: 47.927ms
`prisma.findMany(...)`: 39.066ms
✨  Done in 2.89s.

findFirst() is still the slowest of the bunch by a significant margine and generally everything got much faster across the board except for the multi findUnique case
the diff is as follows:
multiple `prisma.findFirst(...)` calls: 3052.493ms -> 414.506ms (-2637.987ms) ; 86.4% decrease
multiple `prisma.findUnique(...)` calls: 1663.469ms -> 1592ms (-71.469ms) ; 4.3% decrease
using DataLoader: 219.823ms -> 47.927ms (-171.896ms) ; 78.2% decrease
`prisma.findMany(...)`: 196.678 -> 39.066ms (-157.612ms) ; 80.1% decrease

In the screenshot @tomdohnal shared, DataLoader was ~86.8% faster, and is now ~97% faster on latest versions. So this is definitely still an issue

@Druue My results when running https://github.com/prisma/reproductions/tree/main/gh-6573 are more expected and similar to what was initially reported:
multiple `prisma.findFirst(...)` calls: 74.605ms
multiple `prisma.findUnique(...)` calls: 69.911ms
using DataLoader: 8.553ms
`prisma.findMany(...)`: 9.143ms

It seems to me that during your testing something was off and led to confusing (and highly concerning) results.

Aside: Using 1000 items for a SQLite test has the unfortunate side effect that the query chunking is triggered, as that is set to 999. Only seeding 999 items will lead to a cleaner situation where the batched queries can actually be executed in one query.

Using a remote PostgreSQL database instead of a local SQLite shows how Prisma's batching already leads significant real world improvements in query duration:
multiple `prisma.findFirst(...)` calls: 6.486s
multiple `prisma.findUnique(...)` calls: 422.528ms
using DataLoader: 266.413ms
`prisma.findMany(...)`: 263.304ms

But this again shows that the naive DataLoader is still quite a lot faster - and that is what should be investigated.

@janpio any suggestions in the interim for those of us who want to run findUnique 1000 times without making 1000 calls? Just to confirm, is it expected the following example code should batch (assuming prisma server receives all of these under same tick)?
Promise.all(oneThousandQueries.map(query => this.prisma.someDao.findUnique(query)))


Minor grammar correction to tutorial.md

A wording error on the file.

Hi @Simek
Thank you. I didn't realize it was versioned.
The error are only in version 0.63 and 0.62. I have made the change to both.


failed to solve: process "/bin/sh -c pip install --no-cache-dir -r requirements.txt" did not complete successfully: exit code: 2

failed to solve: process "/bin/sh -c pip install --no-cache-dir -r requirements.txt" did not complete successfully: exit code: 2

@tobeyxp try docker compose up --build again

And if it does not work share complete error logs

@tobeyxp Is this issue resolved?

still not working

I tried via docker but:
Preparing to clone inside a volume
Installing credential helpers...
done
Cloning into '/com.docker.devenvironments.code'...
Detecting main repo language...
Migration: no config.json detected
Migration: no .docker/docker-compose.yaml detected
Unsupported language "Python" - using default base image
2023/06/27 13:07:43 INFO: [core] [Channel #1] Channel created
2023/06/27 13:07:43 INFO: [core] [Channel #1] original dial target is: "npipe:////./pipe/buildkitd"
2023/06/27 13:07:43 INFO: [core] [Channel #2] Channel created
2023/06/27 13:07:43 INFO: [core] [Channel #2] original dial target is: "npipe:////./pipe/buildkitd"
2023/06/27 13:07:43 INFO: [core] [Channel #1] parsed dial target is: {Scheme:npipe Authority: Endpoint:/./pipe/buildkitd URL:{Scheme:npipe Opaque: User: Host: Path://./pipe/buildkitd RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/06/27 13:07:43 INFO: [core] [Channel #2] parsed dial target is: {Scheme:npipe Authority: Endpoint:/./pipe/buildkitd URL:{Scheme:npipe Opaque: User: Host: Path://./pipe/buildkitd RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/06/27 13:07:43 INFO: [core] [Channel #1] fallback to scheme "passthrough"
2023/06/27 13:07:43 INFO: [core] [Channel #1] parsed dial target is: {Scheme:passthrough Authority: Endpoint:npipe:////./pipe/buildkitd URL:{Scheme:passthrough Opaque: User: Host: Path:/npipe:////./pipe/buildkitd RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/06/27 13:07:43 INFO: [core] [Channel #1] Channel authority set to "npipe:////./pipe/buildkitd"
2023/06/27 13:07:43 INFO: [core] [Channel #2] fallback to scheme "passthrough"
2023/06/27 13:07:43 INFO: [core] [Channel #2] parsed dial target is: {Scheme:passthrough Authority: Endpoint:npipe:////./pipe/buildkitd URL:{Scheme:passthrough Opaque: User: Host: Path:/npipe:////./pipe/buildkitd RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/06/27 13:07:43 INFO: [core] [Channel #2] Channel authority set to "npipe:////./pipe/buildkitd"
2023/06/27 13:07:43 INFO: [core] [Channel #1] Resolver state updated: {
"Addresses": [
{
"Addr": "npipe:////./pipe/buildkitd",
"ServerName": "",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}
],
"ServiceConfig": null,
"Attributes": null
} (resolver returned new addresses)
2023/06/27 13:07:43 INFO: [core] [Channel #2] Resolver state updated: {
"Addresses": [
{
"Addr": "npipe:////./pipe/buildkitd",
"ServerName": "",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}
],
"ServiceConfig": null,
"Attributes": null
} (resolver returned new addresses)
2023/06/27 13:07:43 INFO: [core] [Channel #1] Channel switches to new LB policy "pick_first"
2023/06/27 13:07:43 INFO: [core] [Channel #2] Channel switches to new LB policy "pick_first"
2023/06/27 13:07:43 INFO: [core] [Channel #2 SubChannel #4] Subchannel created
2023/06/27 13:07:43 INFO: [core] [Channel #1 SubChannel #3] Subchannel created
2023/06/27 13:07:43 INFO: [core] [Channel #1 SubChannel #3] Subchannel Connectivity change to CONNECTING
2023/06/27 13:07:43 INFO: [core] [Channel #2 SubChannel #4] Subchannel Connectivity change to CONNECTING
2023/06/27 13:07:43 INFO: [core] [Channel #1 SubChannel #3] Subchannel picks a new address "npipe:////./pipe/buildkitd" to connect
2023/06/27 13:07:43 INFO: [core] [Channel #2 SubChannel #4] Subchannel picks a new address "npipe:////./pipe/buildkitd" to connect
2023/06/27 13:07:43 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0009161b0, {CONNECTING }
2023/06/27 13:07:43 INFO: [core] [Channel #2] Channel Connectivity change to CONNECTING
2023/06/27 13:07:43 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000157060, {CONNECTING }
2023/06/27 13:07:43 INFO: [core] [Channel #1] Channel Connectivity change to CONNECTING
2023/06/27 13:07:43 INFO: [core] [Channel #1 SubChannel #3] Subchannel Connectivity change to READY
2023/06/27 13:07:43 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000157060, {READY }
2023/06/27 13:07:43 INFO: [core] [Channel #1] Channel Connectivity change to READY
2023/06/27 13:07:43 INFO: [core] [Channel #6] Channel created
2023/06/27 13:07:43 INFO: [core] [Channel #6] original dial target is: "npipe:////./pipe/buildkitd"
2023/06/27 13:07:43 INFO: [core] [Channel #6] parsed dial target is: {Scheme:npipe Authority: Endpoint:/./pipe/buildkitd URL:{Scheme:npipe Opaque: User: Host: Path://./pipe/buildkitd RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/06/27 13:07:43 INFO: [core] [Channel #6] fallback to scheme "passthrough"
2023/06/27 13:07:43 INFO: [core] [Channel #6] parsed dial target is: {Scheme:passthrough Authority: Endpoint:npipe:////./pipe/buildkitd URL:{Scheme:passthrough Opaque: User: Host: Path:/npipe:////./pipe/buildkitd RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2023/06/27 13:07:43 INFO: [core] [Channel #6] Channel authority set to "npipe:////./pipe/buildkitd"
2023/06/27 13:07:43 INFO: [core] [Channel #6] Resolver state updated: {
"Addresses": [
{
"Addr": "npipe:////./pipe/buildkitd",
"ServerName": "",
"Attributes": null,
"BalancerAttributes": null,
"Type": 0,
"Metadata": null
}
],
"ServiceConfig": null,
"Attributes": null
} (resolver returned new addresses)
2023/06/27 13:07:43 INFO: [core] [Channel #6] Channel switches to new LB policy "pick_first"
2023/06/27 13:07:43 INFO: [core] [Channel #6 SubChannel #7] Subchannel created
2023/06/27 13:07:43 INFO: [core] [Channel #6 SubChannel #7] Subchannel Connectivity change to CONNECTING
2023/06/27 13:07:43 INFO: [core] [Channel #6 SubChannel #7] Subchannel picks a new address "npipe:////./pipe/buildkitd" to connect
2023/06/27 13:07:43 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000916830, {CONNECTING }
2023/06/27 13:07:43 INFO: [core] blockingPicker: the picked transport is not ready, loop back to repick
2023/06/27 13:07:43 INFO: [core] [Channel #6] Channel Connectivity change to CONNECTING
2023/06/27 13:07:43 INFO: [core] [Channel #2 SubChannel #4] Subchannel Connectivity change to READY
2023/06/27 13:07:43 INFO: [core] [Channel #6 SubChannel #7] Subchannel Connectivity change to READY
2023/06/27 13:07:43 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc0009161b0, {READY }
2023/06/27 13:07:43 INFO: [core] [Channel #2] Channel Connectivity change to READY
2023/06/27 13:07:43 INFO: [core] pickfirstBalancer: UpdateSubConnState: 0xc000916830, {READY }
2023/06/27 13:07:43 INFO: [core] [Channel #6] Channel Connectivity change to READY
2023/06/27 13:07:43 INFO: [core] [Server #10] Server created
2023/06/27 13:07:43 INFO: [core] [Server #11] Server created
2023/06/27 13:07:43 INFO: [core] [Server #12] Server created
2023/06/27 13:07:44 INFO: [core] [Server #13] Server created
2023/06/27 13:07:44 INFO: [core] [Server #14] Server created
#1 [celery internal] load .dockerignore
2023/06/27 13:07:44 INFO: [core] [Server #15] Server created
#1 transferring context: 50B done
#1 DONE 0.1s
#2 [gui internal] load .dockerignore
#2 transferring context: 2B done
#2 DONE 0.0s
#3 [gui internal] load build definition from Dockerfile
#3 transferring dockerfile: 134B done
#3 DONE 0.0s
#4 [backend internal] load .dockerignore
#4 transferring context: 50B done
#4 DONE 0.0s
#5 [celery internal] load build definition from DockerfileCelery
#5 transferring dockerfile: 419B done
#5 DONE 0.0s
#6 [backend internal] load build definition from Dockerfile
#6 transferring dockerfile: 541B done
#6 DONE 0.0s
#7 [backend internal] load metadata for docker.io/library/python:3.9
#7 ...
#8 [gui auth] library/node:pull token for registry-1.docker.io
#8 DONE 0.0s
#9 [celery auth] library/python:pull token for registry-1.docker.io
#9 DONE 0.0s
#10 [gui internal] load metadata for docker.io/library/node:lts
#10 DONE 2.7s
#7 [backend internal] load metadata for docker.io/library/python:3.9
#7 ...
#11 [gui 1/5] FROM docker.io/library/node:lts@sha256:19892542dd80e33aec50a51619ab36db0921de240c6a4ff6024d801f84881293
#11 DONE 0.0s
#12 [gui internal] load build context
#12 transferring context: 838.68kB 0.0s done
#12 DONE 0.0s
#13 [gui 2/5] WORKDIR /app
#13 CACHED
#14 [gui 3/5] COPY package*.json ./
#14 DONE 0.0s
#15 [gui 4/5] COPY . .
#15 DONE 0.0s
#16 [gui 5/5] RUN npm ci
#16 ...
#7 [backend internal] load metadata for docker.io/library/python:3.9
#7 DONE 4.0s
#17 [celery 1/8] FROM docker.io/library/python:3.9@sha256:98f018a1afd67f2e17a4abd5bfe09b998734ba7c1ee54780e7ed216f8b8095c3
#17 DONE 0.0s
#18 [celery internal] load build context
#18 transferring context: 56.44MB 0.6s done
#18 DONE 0.7s
#19 [backend internal] load build context
#19 transferring context: 56.44MB 0.6s done
#19 DONE 0.7s
#20 [backend  6/10] COPY . .
#20 CACHED
#21 [backend  4/10] RUN pip install --upgrade pip
#21 CACHED
#22 [backend  5/10] RUN pip install --no-cache-dir -r requirements.txt
#22 CACHED
#23 [backend  3/10] COPY requirements.txt .
#23 CACHED
#24 [backend  7/10] COPY config.yaml ./config.yaml
#24 ERROR: failed to calculate checksum of ref d594d56c-731f-43c2-ade4-62a7effc4879::z4bk8zk73suacp12e95auee1a: "/config.yaml": not found
#25 [celery 2/8] WORKDIR /app
#25 CACHED
#26 [celery 3/8] RUN pip install --upgrade pip
#26 CACHED
#27 [celery 7/8] COPY . .
#27 CACHED
#28 [celery 5/8] RUN pip install --no-cache-dir -r requirements.txt
#28 CACHED
#29 [celery 6/8] WORKDIR /app
#29 CACHED
#30 [celery 8/8] COPY config.yaml .
#30 ERROR: failed to calculate checksum of ref d594d56c-731f-43c2-ade4-62a7effc4879::kz85q3j30bl27nrfx63zllteq: "/config.yaml": not found
#31 [celery 4/8] COPY requirements.txt .
#31 CANCELED
#16 [gui 5/5] RUN npm ci
#16 CANCELED


Vm-mock context helpers for sc developpers

Context
For now, sc developpers are not able to test their protected functions such as their constructor
or even other function they want to protect from public usage.
User flow

The users should be able to mock an 'administrator like context' where they have write access on the contract they are testing.
The users should be able to mock the 'deploy context' where they can interact with their contracts as they would be able to if they just deployed it with another contract.

How to
I propose to implement some vm-mock helper functions:

[ ] 'mockAdminContext()' to give write access
[ ] 'mockDeployContext()' to give write access and emulate deployement
[ ] 'resetContext()' to reset both context

Technical details
To do this, we should expose some AS helper functions, implement their corresponding logic/states in the vm.js file
as well as update 'assembly_script_caller_has_write_access' and 'isDeployingContract' in vm.js to make a good use of the newly created states.
QA testing
To validate these functionnalities we should simply add test cases for both 'assembly_script_caller_has_write_access' and 'isDeployingContract' functions where we should be able to emulate their expected behavior in different context states set by theses new helpers.

@gregLibert what do you think ? This idea came from updating the unit tests of the massa-sc-exemples and from this #228


fix: pass an array to the Spatie TagInput state like taginput

Hello Filament team.
This fix makes the Spatie Tag plugin render like the normal tag input by passing an array like the normal TagInput does.
It seems that when passing a collection it isn't converting to an array. This was confirmed by going to the blade component and rendering the states length  this had 0 as the value when there were tags and with the old code. But adding the toArray to force that being passed down it actually gave a length and showed tags.
So this basically adds the one method call. I haven't noticed any adverse affects from doing this.
Reece

Thank you :)


cacheAsBitmap makes container 'jump'

This issue might intersect with some other cacheAsBitmap issues, but I've got a workaround and working example of it, just in case this will help someone.
If we have a PIXI.Container with some stuff in it, and it's bounds are not integers, and all of it's content positioned somewhere far from 0:0 coordinates, toggling cacheAsBitmap will make this container 'jump': move some pixels up and left. The farther from 0:0 is content, the farther it will jump.
Bug can be seen through comparing bounds of the container before and after cacheAsBitmap toggling. Only in Canvas mode, though: in WebGL mode bounds will be the same, even though the jump is obvious.
Problem seen in pixi.js PixiJS 4.8.1 on both WebGL and Canvas renderers and in Chrome and Firefox browsers for Windows 7.
There is a workaround for this bug: before setting cacheAsBitmap add something to 0:0 of the container. 1x1 pixel transparent Graphics rectangle would do.
Full exmaple with a workaround and explainations:
https://codepen.io/takopus/pen/NoXGMv

Good job! Lets add it to collection and wait when some hero solves all of the issues of generateTexture derivatives. Maybe i'll give it one more shot this year.

Oh yeah, in latest v4 it works , but it CRASHES when i set cacheAsBitmap back to false , lol!

Summary: yeah, i fixed that somewhere v4.x, but cacheAsBitmap was broken for canvas renderer. I've made PR.

Yes, in 4.8.5 it crashes on setting cacheAsBitmap to true for the second time and on getting bounds after setting it to false for the first time. On the other hand, in 4.8.5 my initial bug is gone, there's no jumping around. Looks like a serious bug to me, will have to stick to 4.8.1 for now.
Thank you for update!

I believe this was solved. Thanks @ivanpopelyshev


While adding single Card to StatsOverviewWidget card is displayed to full page size

Package
filament/filament
Package Version
v2.9.8
Laravel Version
v8.80.0
Livewire Version
No response
PHP Version
8.1.1
Bug description
While adding a single Card on Filament\Widgets\StatsOverviewWidget it displays the card for entire page length in PC

Steps to reproduce
Add the widgets class
<?php

namespace App\Filament\Widgets;

use Filament\Widgets\StatsOverviewWidget as BaseWidget;
use Filament\Widgets\StatsOverviewWidget\Card;

class UserCountWidget extends BaseWidget
{
    public static function canView(): bool
    {
        return true;
    }

    protected function getCards(): array
    {

        return [
            Card::make('Unique views', '10'),
        ];
    }
}

Relevant log output
No response

Yeah, this is deliberate. The cards adapt to fill the space they are given. Stats overview widgets span the full width by default, you can change this to only 1 column maybe.

For what it's worth, I tried setting $columnSpan = 1 on a Stats overview widget and it indeed narrows the width of all the cards to one column, but then they don't wrap/float into a grid as one might expect, so you end up scrolling through them. The demo implies that there's a way to have cards take up a smaller width and wrap around each other automatically, but it's not clear how to do that from the docs.

I'd need a screenshot to be able to see what's happening and what you want to achieve instead

@danharrin here are a few showing the desktop view and a smaller responsive view. This is with $columnSpan = 1. In both cases, the hope would be to have the width of the stat card be wide enough to hold the content at its current size but narrow enough to allow for multiple cards per row.

It seems likely I'm just not finding the right syntax. Thanks for any guidance you can offer.

How about overriding getColumns() to return 4.


traversal() throws ClassNotFoundException: Neo4JGraph in Console

I open a gremlin console and provide the following:
      :install com.steelbridgelabs.oss neo4j-gremlin-bolt 0.2.27
      import com.steelbridgelabs.oss.neo4j.structure.providers.*
      import com.steelbridgelabs.oss.neo4j.structure.Neo4JGraph
      import com.steelbridgelabs.oss.*
      import org.apache.tinkerpop.*
      import org.neo4j.driver.v1.*
      driver = GraphDatabase.driver("bolt://<IP_ADDRESS>", AuthTokens.none())
      vertexIdProvider = new Neo4JNativeElementIdProvider();
      edgeIdProvider = new Neo4JNativeElementIdProvider();
      graph = new Neo4JGraph(driver, vertexIdProvider, edgeIdProvider);
      graph.execute("MATCH (n) RETURN COUNT(n)")
==>Record<{COUNT(n): 72404601}>

All goes well, got connection and results!  But when I run :
          graph.traversal()

I get the error
java.lang.IllegalStateException: com.steelbridgelabs.oss.neo4j.structure.Neo4JGraph
        at org.apache.tinkerpop.gremlin.process.traversal.TraversalStrategies$GlobalCache.getStrategies(TraversalStrategies.java:253)
        at org.apache.tinkerpop.gremlin.process.traversal.dsl.graph.GraphTraversalSource.<init>(GraphTraversalSource.java:94)
[...]
Caused by: java.lang.ClassNotFoundException: com.steelbridgelabs.oss.neo4j.structure.Neo4JGraph
        at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:264)
        at org.apache.tinkerpop.gremlin.process.traversal.TraversalStrategies$GlobalCache.getStrategies(TraversalStrategies.java:251)
        ... 48 more

Not sure where I'm doing it wrong...

Sorry for the late response, I have not tried using the library within the gremlin console. It is weird that the class that cannot be found is the actual Neo4JGraph, and it has been loaded already in memory since you were able to issue the previous command.

I have a dockerfile for the setup if this helps.

Any news? How can I help exactly?

Sure, what can I do?
As I said, the steps to reproduce are above:
download the gremlin console, install and import, then call graph.traversal()

Just downloaded the gremlin console, make sure you are using version 3.3.0 since this is the version this library has a dependency on:
         \,,,/
         (o o)
-----oOOo-(3)-oOOo-----
plugin activated: tinkerpop.server
plugin activated: tinkerpop.utilities
plugin activated: tinkerpop.tinkergraph
gremlin> import org.neo4j.driver.v1.*
gremlin> import org.apache.tinkerpop.*
gremlin> import com.steelbridgelabs.oss.*
gremlin> import com.steelbridgelabs.oss.neo4j.structure.*
gremlin> import com.steelbridgelabs.oss.neo4j.structure.providers.*
gremlin> driver = GraphDatabase.driver("bolt://<IP_ADDRESS>", AuthTokens.basic("neo4j","XXXX"))
gremlin> vertexIdProvider = new Neo4JNativeElementIdProvider();
gremlin> edgeIdProvider = new Neo4JNativeElementIdProvider();
gremlin> graph = new Neo4JGraph(driver, vertexIdProvider, edgeIdProvider);
gremlin> graph.execute("MATCH (n) RETURN COUNT(n)")

==>Record<{COUNT(n): 1338802}>

gremlin> graph.traversal()

No errors, notice that I changed the order of the import packages and also imported everything within the com.steelbridgelabs.oss.neo4j.structure package.

I've followed your steps, but same error.
There are only 2 thing that are different.
Plugin installation and AuthTokens (I do not use usr/pwd, but I use .none())
Assuming authetincation being invariant.
How did you install the plugin?
I do not see in your steps the command :install com.steelbridgelabs.oss neo4j-gremlin-bolt 0.2.27
Thanks

Same command as the one you used, after installing the plugin I exit the console and open it again and performed the steps I put on my last post.

Amazing, that's it. After installation the console needs to be restarted. Wow!
I wonder if his was written in the gremlin docs and I've missed it.
Thanks for patience. All solved!


[ASCII-1506] Use backslashes in paths for icacls command

What does this PR do?
Ensure paths given to SetupPermissionsCommand use backslashes, and remove the recursive (/t) flag of icacls.
Which scenarios this will impact?
Windows E2e test using this helper to set file permissions.
Motivation
When using forward slash icacls was behaving very wrongly, reading the wrong path, and entering an infinite loop.
The function changes permissions of a single path so no need to set the recursive flag.
Additional Notes
Ran an e2e test successfully with this change.

/merge


Add documentation for the vision and progress of the library

What is the end state of the library?
What we aim to support, what do we exclude support for?
How is the library intended to be used?

Thanks @decentralgabe for adding this in.
I can tell you for me this is personally pretty important. l help put together the documentation, but bluntly I am trying to understand how much I should bank on the SSI-SDK to leverage for my project vs. what I need to be building myself. Understanding the vision of this project is imperative to making this happen.

This seems to start getting more and more important as time goes on. @decentralgabe what do you think is best way to move this ticket forward? I can maybe submit a draft PR and we can work off of it?

Hi @andorsk happy to get a draft PR. I plan on taking it after my presentation exchange PR.

Fixed in #173


not working on macOS (find: -printf: unknown primary or operator)

Info

Operating System: MacOS Ventura 13.0
Shell:
Terminal: iTerm2
nvim --version: v0.8.0
fzf --version: 0.34.0 (installed via homebrew)

[] The issue is reproducible with mini.sh

fzf-lua configuration

require('fzf-lua').setup({
})

Description
I'm on Mac, and the fuzzy finder does not work at all. It cannot find the -printf option for find (it does not exist for find on Mac). I see the following screen:
find: -printf: unknown primary or operator

I use a basic setup of fzf-lua. I'm quite new to nvim.

It seems you don’t have rg or fd installed, in this case fzf-lua defaults to find and the default opts for fine use printf which requires GNU find.
Either install rg or fd or modify the default find options in setup:

check the below command works in your shell first

require('fzf-lua').setup({
  files = { cmd = 'find -type f' }
})

Wow, it works now. It is blazingly fast also for big projects (compared to Telescope), thanks a lot!


Ontology can't be uploaded with ModelUploader

Just tried to upload the complete ontology with Model Uploader. Unfortunately the '.vscode' subfolder in the 'Ontology' folder, and its *.json files inside, will cause a crash of the ModelUploader.
This can be fixed by removing the '.vscode' subfolder in the 'Ontology' folder or by fixing the ModelUploader tool. I'll work on a PR for that.

Thank you, Jürgen. I validated it via ADT explorer https://explorer.digitaltwins.azure.net. I can remove the .vscode folder now.

I removed it, so please try when you can and let me know if it works with the Model uploader. Thanks again!

Still doesn't work, because of schema issues. PR #57 will fix this


Minimize Images in PR-Diff-View

Images are rendered in a .render-wrapper instead of a .data element

@optionset Thank you for your contribution! Could you clarify what this does? Probably provide screenshots of before/after? Thanks!

Hi @hkdobrev
the effect is that it is possible to minimize (collapse) image files in pull request diff-view. without the change, image files are not collapse, because they are not wrapped in a .data element but in a .render-wrapper element. The current css rule only takes .data elements into account. The added rule also considers .render-wrapper elements when collapsing files.

since screenshots do not include the cursor, I've added them. On both screenshots the file should be collapsed, but as you can see, before the change the file wasn't collapsed.
before:

after:

@sindresorhus @hkdobrev I've added the requested inline comment explaining the rule

LGTM


Performancies improvement

When running on OSX, the Swifter could be a little slow for some intensive functions, like serving big data. This could be easily fixed by changing the running priority and/or using bigger chunks in file serving.
This PR solve this issue by adding these two options, but keeps the default parameters for those who want to keep these.

Thanks man !!


Update s3, sdk-core, sqs to 2.16.79

Updates

software.amazon.awssdk:s3
software.amazon.awssdk:sdk-core
software.amazon.awssdk:sqs

from 2.16.67 to 2.16.79.
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, semver-patch

Superseded by #212.


Production version

How can I generate a production version of the application that need access to Geoserver ?

npm run build or npm run package

The generated application doesn't contain the add button, can't see where is the problem.
The first image of the debug version

And the second when I build it

is your application on the same host and port as geoserver?

Yes

Could it be a problem of the FlatButton? I don't see the button in the demo either.
Or it's linked to a condition?

yes it's linked to several conditions

which ones?
Also when I try to log in it connects to address:8080/geoserver/app/api/Login which doesn't exist in geoserver? Is it something I am doing wrong?
I am new to this syntax, any help will be appreciated.

the login extension is only provided in OpenGeo / Boundless Suite version of GeoServer

The only way I find to see the add button after building the app is by changing its place (I put this after header)
,allowUserInput: true, sources: [{url: '/geoserver/wms', type: 'WMS', title: 'Local GeoServer'}]}} map={map} />
But the problem now is that it doesn't take into consideration the icon I put, it gives by default this
![image](https://user-images.githubusercontent.com/26638437/39129658-51d6d91c-470b-11e8-831f-df4103ccc73a.png)
Also, Is it possible to use this app on phone?
Thanks.


Dependency incompatibilities

Hello,
What version of the dependencies were used to build TChem?  Following the build instructions does not result in a working build.

Tines main does not compile with the most recent Kokkos release, 4.4.1, but the tines-kokkosv4.4.0 branch will compile.
With Kokkos, Tines, and GoogleTest successfully built, TChem will not build.  TChem is seemingly incompatible with Kokkos 4.4.1.

$local_path/tchem/TChem-2.2.1/src/core/TChem_Util.hpp:47:10: fatal error: impl/Kokkos_Timer.hpp: No such file or directory
   47 | #include "impl/Kokkos_Timer.hpp"
      |          ^~~~~~~~~~~~~~~~~~~~~~~

Kokkos_Timer.hpp is not in the impl subdirectory, so I tried deleting impl/.  The header file is then found.
$local_path/tchem/TChem-2.2.1/src/core/TChem_Util.hpp:613:22: error: ‘serial_get_thread_team_dat’ is not a member of ‘Kokkos::Impl’
  613 |       *Kokkos::Impl::serial_get_thread_team_data());
      |                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~

Ok, let's find that function in Kokkos.
$ grep -R serial_get_thread_team_data ../../kokkos/
# nothing
$

That string is not present in Kokkos 4.4.1.  Which version of Kokkos can be used to build TChem?
Thank you!

The main branch of TChem still uses Kokkos version 3.6.
Please try the branch tchem-kokkosv4:
git switch tchem-kokkosv4
Then,
git submodule update --init --recursive
Dependencies with the correct version, required to build TChem, will be cloned into ext


🔐 Enroll AWS Shield Advanced on Production

As per this issue
Enroll Production with PR here

Hey team! Please add your planning poker estimate with ZenHub @ASTRobinson @bagg3rs @kyphutruong @mitchdawson1982 @moontune @mTouhid @wanieldilson

All Technology Services AWS accounts are now enrolled into the non-auto-remediate policy through ministryofjustice/aws-root-account#519.
To make the most of Shield Advanced, in the future we'll need to move this to the auto-remediate policy, which adds empty WAFs for to resources for monitoring DDoS events.
Further, the Modernisation Platform team have put together a user guide on next steps when Enabling AWS Shield Advanced for production applications.

We can use this for the alert
https://github.com/ministryofjustice/modernisation-platform-environments/blob/main/terraform/environments/performance-hub/monitoring.tf#L3

We do not have a repo for defining alerts have created an issue to address this and also we have a spike to look to alert pagerduty which would tie this all together.


react-app: yarn start fails - Incorrect argument type for react-slider's onChange prop

Slider component from rc-slider accepts an onChange prop which is a function whose argument type is number[], however,
timeRangeProps implement this as [number, number] this prevents the code from failing to run upon running yarn start

Thanos, Prometheus and Golang version used:

Object Storage Provider:
What happened:
After updating react and react-dom to v-17.0.0-rc2 and running yarn upgrade, yarn start fails.
What you expected to happen:
yarn start should've launched the development server as usual.
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components:
Logs

     Type '(times: [number, number]) => void' is not assignable to type '(value: number[]) => void'.
     Types of parameters 'times' and 'value' are incompatible.
     Type 'number[]' is not assignable to type '[number, number]'.

Anything else we need to know:
Woking on #3218 requires react version to be updated to v17, that's when this problem arose.

cc @prmsrswt


Fix a bug which occurs on second request

This commit fixes a bug that CloudFlare returns CAPTCHA when I tried second request to same domain(I don't know whether if error occurs when I try second request to other domain).

@LiteHell thanks for fixing this. Could you maybe provide some UTs for this fix?

@codemanki  Look for this: https://github.com/codemanki/cloudscraper/issues/52#issuecomment-373996872


Docker Specific - set initial admin username and password as environmental variables?

Is your feature request related to a problem? Please describe.
Not a problem, just thinking that there exists a very tiny possibility that post-deployment, someone else could login to your portainer container and set the password before you do; more of an inconvience than anything else. Still, would be nice if we could set the password during the build process like the MySQL/MariaDB containers do
Describe the solution you'd like
portainer:
      image: portainer/portainer
      container_name: "portainer-app"
      command: --templates http://templates/templates.json
      networks:
        - local
      environment:
        PORTAINER_ADMIN_NAME: admin
        PORTAINER_ADMIN_PASS: admin
      volumes:
        - /var/run/docker.sock:/var/run/docker.sock
        - /opt/portainer/data:/data

Agree… had a few issues where people deployed Portainer, then forgot to configure it, whilst leaving it exposed to the internet..
Our goal is to make life easy and apply as many best practices as we can transparently to users.. this I consider a best practice. Same like forcing Portainer to use HTTPs too..
From: Lucas Krupinski<EMAIL_ADDRESS>Sent: Tuesday, 21 August 2018 8:34 AM
To: portainer/portainer<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [portainer/portainer] Docker Specific - set initial admin username and password as environmental variables? (#2195)
Is your feature request related to a problem? Please describe.
Not a problem, just thinking that there exists a very tiny possibility that post-deployment, someone else could login to your portainer container and set the password before you do; more of an inconvience than anything else. Still, would be nice if we could set the password during the build process like the MySQL/MariaDB containers do
Describe the solution you'd like
portainer:
image: portainer/portainer
container_name: "portainer-app"
command: --templates http://templates/templates.jsonhttps://urldefense.proofpoint.com/v2/url?u=http-3A__templates_templates.json&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=TKqf8USl138N9mYwpIZhbgu7XhCj2KCagCyvoHYGu8E&s=TxLKPl_b0lvrlrdMAx_vDXn7A2RzIXC7N39bLo_6vLU&e=
networks:

local
environment:
PORTAINER_ADMIN_NAME: admin
PORTAINER_ADMIN_PASS: admin
volumes:
/var/run/docker.sock:/var/run/docker.sock
/opt/portainer/data:/data

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_2195&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=TKqf8USl138N9mYwpIZhbgu7XhCj2KCagCyvoHYGu8E&s=FBD22gPCqCfLUX3pwpD58t-Uo-2jEgrN3HykjFHvgsA&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlUggTVD7tWXruOnstgYKeRCFAyUhks5uSx0rgaJpZM4WEqjH&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=TKqf8USl138N9mYwpIZhbgu7XhCj2KCagCyvoHYGu8E&s=GTrij8kJJJPtZwTaJPGiKiqzeZBVvQ5KNGoSNmCUCco&e=.

We already had this discussion in https://github.com/portainer/portainer/issues/399
You can already set the administrator password via the --admin-password && --admin-password-file, which are compliant with CLI/Compose deployments.

someone else could login to your portainer container and set the password before you do

Giving the possibility to define the username/password via environment variables do not enforce the creation of the creation of the initial administrator user as a user could simply not specify the vars (same for the CLI flags).
If this is the problem that we're trying to solve, we'd need to make these variables mandatory.

One option, set a password automatically (random generate) and expose it in the container STDOUT log… not very user friendly tho..
From: Anthony Lapenna<EMAIL_ADDRESS>Sent: Tuesday, 21 August 2018 9:27 AM
To: portainer/portainer<EMAIL_ADDRESS>Cc: Neil Cresswell<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [portainer/portainer] Docker Specific - set initial admin username and password as environmental variables? (#2195)
We already had this discussion in #399https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_399&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=29yAK6AiPFy4BJ-fEOeUiz3NamC1nQLSDN_OgC-oGCo&s=EtCsA3xL8uTFhQt4cGZhDObwQn0v4tiY4rTNZOgYRi0&e=
You can already set the administrator password via the --admin-password && --admin-password-file, which are compliant with CLI/Compose deployments.
someone else could login to your portainer container and set the password before you do
Giving the possibility to define the username/password via environment variables do not enforce the creation of the creation of the initial administrator user as a user could simply not specify the vars (same for the CLI flags).
If this is the problem that we're trying to solve, we'd need to make these variables mandatory.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_2195-23issuecomment-2D414468960&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=29yAK6AiPFy4BJ-fEOeUiz3NamC1nQLSDN_OgC-oGCo&s=asqDtv-pSNfMO-UTZSs0MB7ch6SQEqIe5hifPLS2R0E&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlTGj1s85il7o4zawwKcyEr4KB80Bks5uSymwgaJpZM4WEqjH&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=29yAK6AiPFy4BJ-fEOeUiz3NamC1nQLSDN_OgC-oGCo&s=6d6qyR7hlYIcDLHL4JfVoegEfZp7moKPFqq0SAZkbrw&e=.

How about:
If there isn't a username set anywhere, then the default behavior occurs where you set the username and password yourself.  If its started with both username and password flags, then those are what it sets.
This is all stored in your persistent data, so if you ever rebuilt the container without destroying the volume, you keep your old passwords.
The remaining issues are if a user tries to build the container with either just a user name or just a password. I'd think if they built it with just a username in the env, then the initial screen would require them to set a password, but without being able to change the username; if build with just a password, it might be better to just discard that and require the user to enter both.
I do agree, though, that dumping a random password in STDOUT is not the right thing to do!

If there isn't a username set anywhere, then the default behavior occurs where you set the username and password yourself. If its started with both username and password flags, then those are what it sets.

This is pretty much the actual behavior. Except that you can only set the administrator password and not the username.

I'm seeing the discussion in the #399, just seems like a more logical place to pass it through is in the environment rather than adding a flag to the command to setting a password from a different file altogether.
Anyways, just a suggestion.

I am trying to stand up Portainer with Docker and specify the admin password. Unfortunately,  Ansible uses docker.py, and docker.py doesn't allow you to pass arbitrary command line variables. docker.py, and thus ansible, does accept environment variables. This is why portainer should accept the admin password as an environment variable.

Well, nevermind. I figured out how to do it with with the command: argument in ansible's module. It looks something like:
      - name: Run a Portainer docker container
        docker_container:
          name: 'portainer'
          image: 'portainer/portainer'
          command: '-H unix:///var/run/docker.sock --admin-password="<redacted>"'
          ports:
            - '8000:8000'
            - '9000:9000'
          restart_policy: always
          volumes:
            - '/var/run/docker.sock:/var/run/docker.sock'
            - 'portainer_data:/data'

That didn't work in my case. Tried on image: portainer/portainer-ce:2.11.0. Is this outdated?

Why is this topic closed? I don't see any definitive conclusion, just some suggestions and options.


automation: Add the iproute package to the docker image

Including the ip toolset in the image for debugging and possible test usage.

Coverage remained the same at 73.425% when pulling 4b8060dbb3fb3be82224c7069903e5065938538d on EdDev:docker-add-iproute into 0a5429a7426dfe9141b55842fdb1cc79da14ca63 on nmstate:master.


Flutter tool should ask before uninstalling old version

Use case
My application has some data synced from server in local database. Initial synchronization can take some time. If I try to run flutter in debug mode and installation fails for some reason (e.g. downgrading version, or using incorrect certificate for debug/release - easilly fixable mistakes) flutter automatically uninstalls old version and tries to install again.
Running Gradle task 'assembleDebug'...
✓  Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app.apk...
Performing Streamed Install
Error: ADB exited with exit code 1
adb: failed to install build/app/outputs/flutter-apk/app.apk:
Uninstalling old version...
Installing build/app/outputs/flutter-apk/app.apk...

This of course wipes all data and settings. Ability to abort installation could prevent this.
Proposal
I think there 2 possible approaches for this.

Adding new run parameter (e.g. --force-installation), that will implement current behavior. IDE plugins could have checkbox for it
Installation should pause with yes/no question whether user wants to uninstall old version (no should be default IMHO as it is more safe)

Yes example:
Running Gradle task 'assembleDebug'...
✓  Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app.apk...
Performing Streamed Install
Error: ADB exited with exit code 1
adb: failed to install build/app/outputs/flutter-apk/app.apk:

Do you want to uninstall old version and install again? (y/N): y

Uninstalling old version...
Installing build/app/outputs/flutter-apk/app.apk...

No example:
Running Gradle task 'assembleDebug'...
✓  Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app.apk...
Performing Streamed Install
Error: ADB exited with exit code 1
adb: failed to install build/app/outputs/flutter-apk/app.apk:

Do you want to uninstall old version and install again? (y/N): n
Failed to install APK

How it works when building native android application?

How it works when building native android application?

adb install fails in these cases. You can uninstall old version manually. There is also -d parameter that allows downgrade for debuggable packages.

Running Gradle task 'assembleDebug'...
✓  Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app.apk...
Performing Streamed Install
Error: ADB exited with exit code 1
adb: failed to install build/app/outputs/flutter-apk/app.apk:

Do you want to uninstall old version and install again? (y/N): n
Failed to install APK

This might works fine when running in Terminal, and what about running in IDEs?

Using adb uninstall -k packageName might handle the trick.


[CMT-420] Add transparency summary [japanese]

I translated about transparency thread. thanks!

i made new pr


Add color encoding column.

i.e. when viewing an individual color each event individually, like in the AE timelines.

requested by @derekjameslawrence


IDE Native configuration for OpenApiReference

Discussion for PR https://github.com/RicoSuter/NSwag/pull/3790
Investigating aproaches (in #3636) for cross-platfrom lightweight configuration I found useful feature in VS. Property window customizable via PropertyPageSchema. This approach already used in Grpc.Tools and Microsoft.Extensions.ApiDescription.Client
I made a small project to prove the concept here
Then I realized that this feature not supported by Rider and open issue on youtrack (likes are welcome).
So at this time customizable property window supported only in Visual Studio but we can change that.

Ref: It would look like this:

Better late than never
Finally I added property page support. You can enable it with property NSwagPropertyPageType=CSharp|TypeScript
Another one feature is compile-time generation for controllers (same as for OpenApiReference). Add property NSwagControllerPropertyPageEnabled=true in project where you want to generate controller.
@RicoSuter  do we need to provide samples for this feature?

How to use this feature (supported only in VisualStudio for Windows but there is issue for Rider)
OpenApiReference

Add OpenApi specification to your project (for example this one)
Add NSwag.ApiDescription.Client package reference to your project  - dotnet add package NSwag.ApiDescription.Client
Add property <NSwagPropertyPageType>CSharp</NSwagPropertyPageType> for csharp generator or <NSwagPropertyPageType>TypeScript</NSwagPropertyPageType> for typescript generator
Change Build Action for OpenApi specification to OpenApi File Reference
Use property page to configure options

NSwagController (same as OpenApiReference just for openapi2cscontroller command)

Add OpenApi specification to your project (for example this one)
Add NSwag.MSBuild package reference to your project  - dotnet add package NSwag.MSBuild
Add property <NSwagControllerPropertyPageEnabled>true</NSwagControllerPropertyPageEnabled>
Change Build Action for OpenApi specification to NSwag Controller File Reference
Use property page to configure options
Also you can specify common properties via project property

Is this available? A bit confused by the above as it makes it sound like it should work in VS. I checked the latest version and latest preview and don't see it; not sure if I just haven't configured it properly or if I'm chasing something that's not there

I did but it didn't work. It's not a big deal though as I got what I needed. I was mainly trying to visualize all of the available options in one place--tracking them down through the docs is an incomplete maze and in some instances requires digging through source. I just ended up using the screenshot from the OP. Thanks

@RicoSuter how to push PR #3790 ? What I have to do?

@hayhay27 are you planning to complete it? it looks very comfortable!
Now we have to use NSwagStudio as a playground, and then transfer the keys manually to OpenApiReference 😔


A non-numeric value encountered in Stacktrace.php

I get string $index and observe "A non-numeric value encountered" error

Please, take a look at my solution. I'm not sure that this is correct fix and the root of the problem

Are you using XDebug or some other debug extension? If so, can you try disabling it and retrying?

@ste93cry Yeah, I have XDebug in my project. When I disabled it, the error disappeared.

The screenshot you provided does not contain the fix by #763, could you make sure you are using the latest version of the library and see if the issue is still there?

The screenshot you provided does not contain the fix by #763

Good catch, I didn’t even noticed it!

I'm going to update dependency on Monday and check the result

@ste93cry Sorry for delay. I updated dependencies and now all works fine. I have the next versions:
sentry/sdk                                2.0.2
sentry/sentry                             2.0.1
Ticket going to be closed.


User-templated text for rich presence caption

Ability to change the long and short text in discord
eg. "▶MyArtist" could be changed to "Artist: MyArtist" by allowing the user to use custom text with variables "Artist: {@Artist}"
Changing 01x04 to {@Disk}x{@Track} or something?
and perhaps being able to toggle between time done and time remaining?

Along with this, it would be nice to have tokens for elapsed time and total time, so it can give a caption like 21:42/43:04 for an episode for example.


allow multiple plugin installation

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of Changes

[x] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update
[ ] Other (Tooling, Dependency Updates, etc.)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

If you added a new component feature (layer, geom, source, etc.), please be sure to update the documentation:

[ ] Add component to output.globals in vite.config.ts
[ ] Create a src/demos/<Component>Demo.vue
[ ] Create a docs/componentsguide/<Category>/<Feature>/index.md containing the Demo and documentation for the component
[ ] Add the docs page to docs/.vitepress/config.ts
[ ] Update the sitemap docs/public/sitemap.xml

Just to understand the problem with the current implementation: what's a reason to install one of the plugins multiple times?

@d-koppenhagen Our webapp consists of multiple vue apps existing in parallel on the same site. They all use maps and are designed as different apps because we individually reuse them in other places. In my opinion this is not an antipattern:
multiple-application-instances
What do you think?

I agree! This should be fine totally. Thanks for your contribution!

@d-koppenhagen Thanks for maintaining this awesome repo!


EVAL_STANDALONE_END documentation missing

Expected behavior
EVAL_STANDALONE_END event is missing from the pseudo code definition in the Composer event doc. It looks like the pseudo code is referring to another name for the even, AFTER_EVAL_ALL which does not seem to exist anymore.
Additional it is not very clear that EVAL_END is called after evaluation on one evaluation dataset, so called several times if there are several datasets.
https://docs.mosaicml.com/projects/composer/en/latest/api_reference/generated/composer.Event.html#composer.Event.EVAL_STANDALONE_END

EVAL_STANDALONE_END event is missing from the pseudo code definition in the Composer event doc

Ah, this is because the doc focuses on the training loop, and this is only run if you call just trainer.eval(...), which we do not provide docstrings for. We'd love a community PR describing the eval loop events after the train loop if you're up for it!

It looks like the pseudo code is referring to another name for the even, AFTER_EVAL_ALL which does not seem to exist anymore.

Ah, it should be EVAL_AFTER_ALL. I'll fix the typo.

Additional it is not very clear that EVAL_END is called after evaluation on one evaluation dataset, so called several times if there are several datasets.

It should be described in the for loop over evaluators in docstring -- is there a better place you'd like a more helpful description?


Discuss task_info.yaml in docs

There's currently no mention of this file at all. I don't know, for example, what are valid roles.

see https://main--openproblems.netlify.app/documentation/create_task/define_task.html

To elaborate a bit further on this:

There's currently no mention of this file at all.

I agree with Kai here, it's already mentioned in the '[Define task](see https://main--openproblems.netlify.app/documentation/create_task/define_task.html)' documentation

I don't know, for example, what are valid roles.

However, I also think this documentation could be expanded upon, because right now the documentation just shows you the format of a task_info.yaml file without describing each of the fields. Let's reopen this until we have more extensive descriptions in place.

Ah, I was looking in https://main--openproblems.netlify.app/documentation/create_task/design_api.html . Might be worth assuming that people won't read the docs end-to-end (e.g. if my task is already well-defined) and putting a mention of this file in the "design the API" section, even if it's just referencing the fact that it was created in the previous step.


Show a prompt character when asking a multiple choice question

Right now, when asking a multiple choice question such as which version to uninstall, there is no indication that a user input is expected:
Which version of vagrant would you like to uninstall?
 1) None [Default - Press Enter]
 2) 1.5.4
 3) 1.6.3
 4) 1.6.5
 5) All versions
1

Adding an input indicator such as the > character would make this clearer:
Which version of vagrant would you like to uninstall?
 1) None [Default - Press Enter]
 2) 1.5.4
 3) 1.6.3
 4) 1.6.5
 5) All versions
> 1

For more details: https://groups.google.com/forum/#!topic/chocolatey/UVncL7PxXRg

Moved to choco repo


✨ Add cluster importer feature and promote addonManagement feature to beta

Summary
Related issue(s)
Fixes #

/assign @zhiweiyin318

/lgtm


On-reaction deletion of bot messages

Feature: Say when someone sends !gh source, the bot will send the github link like normal. But it will react to the message (The message the bot sent) with a (example) trash can. When the original sender of the message reacts to the message with the trash can, it will delete the github link.

We should definitely have this. However, I'd like it to be the default for the bot embeds, instead of being manually applied on every command. There should aslo be a setting to disable the reaction for that specific embed. I wouldn't mind using decorators or any other implementation that you could figure out.

(this is my first issue so i might be a little slow) Are you saying that only embeds have a deletion feature?

Nope. I think this should apply to all bot outputs, but we almost exclusively use embeds.

Cool. When you were talking about decorators are you saying that in the bots code say we had await channel.send we would put (example) @deletable before the message is sent?

Yep, that would be the idea. However, I'm not sure what the best way forward would be.

Yes, I think we exclusively use embeds for bot outputs. However, any output sent in a normal message form will anyway be short and will not take much screen space, and hence not warrant the need for it to be deleted in most cases.

I think #83  will handle the deletable embed issue. However, there has been no correspondence by the author on the issue lately :angry:  .

Sorry for not responding, I had to eat lunch.
But I will look into ways to possibly implement this. And even we don’t have a need for it now, it might come in handy down the road.

I might not have time to implement this as classes are getting weird since a bunch of kids have gotten quarantined. (And I don't know what i'm doing, so I'd have to spend extra time googling.)


Enable test code coverage collection for containers

Enables collection of test code coverage for code running within containers like Controller and Invoker
Description
So far with #3249 we have been collecting test code coverage data from unit and system test for code which need not be running within container. However some of the code paths can only be exercised within a running container. This PR enables collecting test code coverage stats for such code paths.
As explained in #3243 scoverage creates build/scoverage/scoverage.measurements.xxx files (xxx maps to threadId) at runtime to record any code path being hit. Instrumented code has compile time configured paths for the data directory. So for code compiled for coverage data collection on travis the instrumented code would try to write the measurement file under /home/travis/build/apache/incubator-openwhisk/core/controller/build/scoverage
For normal scenario when code is running outside of container such files are written within build/scoverage directory and is accessible when generating reports. However when code runs within container its not possible to access such generated files. To enable that following approach has been taken
Preparing Instrumented Containers
Docker build now supports a distDockerCoverage task which generate a new image for controller and invoker containing instrumented code based on Dockerfile.cov file.
The instrumented container

Is tagged with cov tag e.g. whisk/controller:cov
Adds scoverage runtime jars and replaces existing openwhisk-common etc jars with those generated by scoverage task
Adds symlinks in container for data directory path

Running Instrumented Containers
Further ansible playbooks are modified to look for GRADLE_COVERAGE environment variable to enable some specific tasks. Once enabled the new tasks would

Create specific directory for controller and invoker like /tmp/wskcov/controller
Expose these directory as shared volume with path /coverage

Once running a path like  /home/travis/build/apache/incubator-openwhisk/core/controller/build/scoverage would be symlinked to /coverage/controller which inturn is pointing to /tmp/wskcov/controller/controller
Report Generation
In test module the report generation task would copy all such measurement files from directories under /tmp/wskcov to respective modules. The file names would be changed to ensure that they are unique. Post this report would include stats from code running within containers.
Related issue and scope

[x] I opened an issue to propose and discuss this change (#3243)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[x] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[x] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Codecov Report

Merging #3685 into master will increase coverage by 10.72%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #3685       +/-   ##
===========================================
+ Coverage   74.49%   85.21%   +10.72%
===========================================
  Files         126      126
  Lines        5994     5994
  Branches      392      392
===========================================
+ Hits         4465     5108      +643
+ Misses       1529      886      -643

Impacted Files
Coverage Δ

...n/scala/whisk/core/database/CouchDbRestStore.scala
70.37% <0%> (+0.61%)
:arrow_up:

.../scala/src/main/scala/whisk/core/entity/Exec.scala
84.51% <0%> (+0.64%)
:arrow_up:

...r/src/main/scala/whisk/core/controller/Rules.scala
89.93% <0%> (+0.67%)
:arrow_up:

...cala/src/main/scala/whisk/http/ErrorResponse.scala
90.9% <0%> (+1.13%)
:arrow_up:

...isk/core/controller/actions/PrimitiveActions.scala
88.54% <0%> (+1.52%)
:arrow_up:

...cala/whisk/core/containerpool/ContainerProxy.scala
93.56% <0%> (+1.75%)
:arrow_up:

...re/database/MultipleReadersSingleWriterCache.scala
96.49% <0%> (+1.75%)
:arrow_up:

...on/scala/src/main/scala/whisk/common/Logging.scala
89.65% <0%> (+2.29%)
:arrow_up:

.../scala/src/main/scala/whisk/core/WhiskConfig.scala
94.57% <0%> (+2.32%)
:arrow_up:

...src/main/scala/whisk/core/controller/Actions.scala
93.84% <0%> (+2.56%)
:arrow_up:

... and 31 more

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 8a3b447...1fc0317. Read the comment docs.

@markusthoemmes ping

@chetanmeh sorry this sat for so long - mind resolving the conflict?

Resolved conflicts and rebased to latest master

With this now master coverage stands at 85%


Bring bgnotify plugin up to date with t413/zsh-background-notify

Changes include:

time format now shows h/m/s (only when needed!)
enables only with interactive shells
adds specific kde support (via kdialog)
adds click-through-action for OS X notifications

@andrey-yantsen @shalecreig can you guys +1 this one?

+1

@mcornella you've misspelled @shalecraig's nickname :)
So... @shalecraig can you please +1 this one?

+1 whynot

(thanks, @andrey-yantsen)

:sweat_smile: sorry!
Ok, ready to merge /cc @robbyrussell

Mistakenly closed when trying to update to include @depressiveRobot's fix t413/zsh-background-notify#6. Reopening!


F .\tensorflow/core/kernels/random_op_gpu.h:227] Non-OK-status: CudaLaunchKernel

F .\tensorflow/core/kernels/random_op_gpu.h:227] Non-OK-status: CudaLaunchKernel(FillPhiloxRandomKernelLaunch, num_blocks, block_size, 0, d.stream(), gen, data, size, dist) status: Internal: invalid device function.
pelese help me.thanks

It seems like that it is tensorflow related problems. I don't know much about it, but you can refer to the issues like this: https://github.com/tensorflow/tensorflow/issues/30665.

看来这是与tensorflow相关的问题。我对此了解不多，但是您可以参考这样的问题：tensorflow / tensorflow＃30665。

thanks


DEX-13 - RESOLVER: Pokemon.evolutions

type Evolution {
  id: ID!
  name: String
}

type Pokemon {
  ...
  evolutions: [Evolution]
}

PR: https://github.com/michaelmaysonet74/poke-dex/pull/32


Backend/Homework6/Spring1

Drift video link :
https://video.drift.com/v/ab9mdVDajFUnWQZtqpQMJrgyuifD4adDUhe2coRC8Ebg/

Metric
Value

alert_status
:white_check_mark: OK

bugs
0

code_smells
1

reliability_rating
A (0 Bugs)Note: A being best, E being worst

security_rating
A (0 Vulnerabilities)Note: A being best, E being worst

vulnerabilities
0


runtime: VirtualAlloc of<PHONE_NUMBER> bytes failed with errno=1455 on windows/amd64 go 1.13.4

I just encountered a similar panic to #33716 . I am running Go 1.13.4 windows/amd64. My windows VM has 5GB of RAM. Go tried to allocate 4GB of RAM and crashed. This is a big long running program (had been running for about 24 hours at the point of crash) so no easy repro test case available immediately.
It seems rather unreasonable for Go to ask for that much memory on a 5GB box.
runtime: VirtualAlloc of<PHONE_NUMBER> bytes failed with errno=1455
fatal error: out of memory
runtime stack:
runtime.throw(0x2977e71, 0xd)
c:/go/src/runtime/panic.go:774 +0x79
runtime.sysUsed(0xc280b26000, 0x100000000)
c:/go/src/runtime/mem_windows.go:83 +0x230
runtime.(*mheap).allocSpanLocked(0x4087660, 0x80000, 0x40ab448, 0x1210fda0)
c:/go/src/runtime/mheap.go:1228 +0x203
runtime.(*mheap).alloc_m(0x4087660, 0x80000, 0x101, 0x1210fdd0)
c:/go/src/runtime/mheap.go:1022 +0xd0
runtime.(*mheap).alloc.func1()
c:/go/src/runtime/mheap.go:1093 +0x53
runtime.(*mheap).alloc(0x4087660, 0x80000, 0x10101, 0xc000048000)
c:/go/src/runtime/mheap.go:1092 +0x91
runtime.largeAlloc(0xfffffe00, 0xc000040101, 0xc000056000)
c:/go/src/runtime/malloc.go:1138 +0x9e
runtime.mallocgc.func1()
c:/go/src/runtime/malloc.go:1033 +0x4d
runtime.systemstack(0x0)
c:/go/src/runtime/asm_amd64.s:370 +0x6b
runtime.mstart()
c:/go/src/runtime/proc.go:1146
goroutine 1 [running]:
runtime.systemstack_switch()
c:/go/src/runtime/asm_amd64.s:330 fp=0xc0003e9108 sp=0xc0003e9100 pc=0x464f10
runtime.mallocgc(0xfffffe00, 0x26064a0, 0x1, 0xc0003e91d0)
c:/go/src/runtime/malloc.go:1032 +0x8d4 fp=0xc0003e91a8 sp=0xc0003e9108 pc=0x411344
runtime.makeslice(0x26064a0, 0xfffffe00, 0xfffffe00, 0x0)
c:/go/src/runtime/slice.go:49 +0x73 fp=0xc0003e91d8 sp=0xc0003e91a8 pc=0x44c4b3
bytes.makeSlice(0xfffffe00, 0x0, 0x0, 0x0)
c:/go/src/bytes/buffer.go:229 +0x7e fp=0xc0003e9240 sp=0xc0003e91d8 pc=0x535c2e
bytes.(*Buffer).grow(0xc0003e9368, 0x200, 0x40000000)
c:/go/src/bytes/buffer.go:142 +0x162 fp=0xc0003e9290 sp=0xc0003e9240 pc=0x535562
bytes.(*Buffer).ReadFrom(0xc0003e9368, 0x2e01ce0, 0xc0000060e0, 0x2917ea0, 0xc00006e120, 0xc0001
be8b8)
c:/go/src/bytes/buffer.go:202 +0x52 fp=0xc0003e9300 sp=0xc0003e9290 pc=0x535a12
io/ioutil.readAll(0x2e01ce0, 0xc0000060e0, 0x200, 0x0, 0x0, 0x0, 0x0, 0x0)
c:/go/src/io/ioutil/ioutil.go:36 +0x107 fp=0xc0003e93a0 sp=0xc0003e9300 pc=0x54c927
io/ioutil.ReadAll(...)
c:/go/src/io/ioutil/ioutil.go:45
...

I replied on the other issue, but copying here for visibility:

@glycerine AFAICT your application ran out of memory. It looks like your application tried to read more than 4 GiB from an io.Reader and the OS determined it didn't have enough memory left to satisfy the allocation (note that the bytes.Buffer grows, calling makeSlice with an argument of<PHONE_NUMBER> bytes, which was then rounded up to 4 GiB even because it's allocating at a page granularity).

To be clear, the runtime is asking the OS for 4 GiB of memory on behalf of your application. The request is ultimately coming from there. Please let me know if there are any further issues, though.

I tried running the GC manually more often, and that seems to have fixed it. So closing.


What you expected to happen:
Images would be weeks/days old.
How to reproduce it (as minimally and precisely as possible):
Just deploy KubeVirt.
Anything else we need to know?:
I don't have any Bazel experience myself but this seems to be related to Bazel [0] which would need stamp = true on the container_image definition to allow the use of workspace status variables. Once enabled,  creation_time should be added by default:
String, optional, default to {BUILD_TIMESTAMP} when stamp = True, otherwise 0
[0] https://github.com/bazelbuild/rules_docker/issues/52
Environment:

KubeVirt version (use virtctl version):
Client Version: version.Info{GitVersion:"v0.17.0", GitCommit:"c0f960702dce718419a767f3913669f539229ff0", GitTreeState:"clean", BuildDate:"2019-05-05T08:09:14Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{GitVersion:"v0.17.0-2+9c982f0cb214fd", GitCommit:"9c982f0cb214fdcf040edf674115826b01fc263f", GitTreeState
:"clean", BuildDate:"2019-05-06T16:46:44Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:11:31Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.1", GitCommit:"b7394102d6ef778017f2ca4046abbaa23b88c290", GitTreeState:"clean", BuildDate:"2019-04-08T17:02:58Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}

VM or VMI specifications:

Cloud provider or hardware configuration:

OS (e.g. from /etc/os-release):

Kernel (e.g. uname -a):

Install tools:

Others:

We can set a BUILD_TIMESTAMP in the --workspace_status_command file. stamp is no needed anymore.


Add support of EnvironmentVariables adding bool includeEnvironmentVari...

...ables arguments into Configuration class constructors

Correction of few tests that fail when executed on a not US local culture (date mounth & day order into underlining configuration file definition)

Hey @PhilippeLeveille, thanks for the PR. When I originally opened up the issue to add support for more types of configurations I wasn't aware of the direction that the new aspnet5 stuff was headed. Upon more thoughts, I'm going to close up the issue since those new methods will make this library largely obsolete.
Here's some more info on how it's looking in aspnet5:

https://github.com/aspnet/Configuration
http://gunnarpeipman.com/2014/11/asp-net-5-new-configuration-files-and-containers/