Implement public and logged in user views of opening a Facility

Definition of Ready

[x] Does this meet the INVEST criteria? (Independent, Negotiable, Valuable, Estimate-able, Small, Testable)
[x] Does this have a clearly defined user?
[ ] Does this have an estimate?
[x] Does this have acceptance criteria?
[ ] Does this have sufficient context (wireframes, business rules, etc.)?
[x] Is this traceable to a feature, epic, or PI?

User Story
As a user, I want to open a Facility, so that I can view its Monitoring Plan.
Acceptance Criteria:
Given the user is not logged in
When the user would like to open a Facility by clicking "Open"
Then the system displays a view only version of the Facility's Monitoring Plan.
See PD Board Scenario 1A of public view of the Facilities page. The only available action is the "Open" button.
Given the user is logged in
When the user would like to open a Facility by clicking "Open"
Then the system displays a view only version of the Facility's Monitoring Plan.
See PD Board Scenario 2B of logged in view of the Facilities page. The two available actions are "Open" and "Lock".

OBE


Review of ANS student conf paper revisions

This Issue can be closed once @katyhuff reviews my ANS student conf paper revisions.

I merged all the commits.


visualizations

https://www.youtube.com/watch?v=U6dyIRolIhI&ab_channel=SophiaYang
These types of visualizations

[ ] test
[ ] test II


CI: Mdbook link checker

#555 closed to change target branch. All links fixed, link checker can be integrated into CI.
The remaining links were actually way less effort than I thought, but the last link fix session scared me of finishing this ^^.
Looking forward to no more broken links inside the book.
Maybe open follow up issue to enable external link check.
Weird ci error
Basics

[x] I added a line to /doc/CHANGELOG.md
[x] The PR is rebased with current master.

[x] References to issues, e.g. close #X, are in the commit messages.
[x] The buildserver is happy.

Checklist

[x] I have installed and I am using pre-commit hooks
[x] I fully described what my PR does in the documentation
(not in the PR description)
[ ] I fixed all affected documentation
[ ] I fixed all affected decisions
[ ] I added unit tests for my code
[ ] I added code comments, logging, and assertions as appropriate
[ ] I translated all strings visible to the user
[ ] I mentioned every code or binary not directly written or done by me in reuse syntax
[ ] I created left-over issues for things that are still to be done
[ ] Code is conforming to our Architecture
[ ] Code is conforming to our Guidelines
(exceptions are documented)
[ ] Code is consistent to our Design Decisions

Review

[ ] I've tested the code
[ ] I've read through the whole code
[ ] Examples are well chosen and understandable

Jenkins build please

The link check is happening with mdbook build, a follow up issue was created for enabling external link checks.

I think this is mergable for now and we just open up two issues. One for external link checks (which already exists) and one to eventually reach "warning-policy: error", which I will go open now.

Thx! :heart:

Ok I will use please merge to communicate when pr's are ready.
I thought please merge is maybe a more urgent one.

You understood correctly but in your case nearly everything is somewhat "urgent" because as long as build checks are missing things might go wrong on master.


Acccheck.md

create acccheck.md

被采用了？一开始没注意群主之前写过这文章，第一次用github完全晕乎
在 2017-03-19 11:23:40，"Jack-Liang"<EMAIL_ADDRESS>写道：
Merged #19.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


fix(next): only set payload theme preference headers within '/admin' namespace

When these headers are set globally, they interfere with the lighthouse CI tool. It forces a redirect that adds 600-800ms to the total load time on mobile.
By only setting the headers for the /admin section of the site, which is where they are used, it resolves the problem for other sections of the site where performance is critical.
Description

[x] I have read and understand the CONTRIBUTING.md document in this repository.

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Steps to test

Pull down the latest version of the payload 3.0 demo
Run the site in prod mode: pnpm build && pnpm start
Run a lighthouse audit using the cli tool: npx lighthouse@latest http://localhost:3000 --view --chrome-flags="--headless" --verbose
Observe this line in the report:

Steps to confirm the fix

Open the file<EMAIL_ADDRESS>Apply the change from this PR by changing source: '/:path*' to source: '/admin/:path*'
Re-run build and run the site: pnpm build && pnpm start
Re-run the lighthouse check: npx lighthouse@latest http://localhost:3000 --view --chrome-flags="--headless" --verbose
Observe that the redirect perfomance penalty has been resolved

Checking in on this. Is there anything more that needs to be done for this to be merge-able?

This is definitely still relevant


sync to live

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

File
Status
Preview URL
Details

windows-iotcore/develop-your-app/AppInstaller.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/dragonboard.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/qualcomm.md
:white_check_mark:Succeeded

windows-iotcore/windows-iot.md
:white_check_mark:Succeeded

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


PR https://github.com/Azure/ms-rest-nodeauth/pull/126 introduces a broken change

related PR
https://github.com/Azure/ms-rest-nodeauth/pull/126
issue code
https://github.com/AzureAD/azure-activedirectory-library-for-nodejs/commit/362a00e5d34186e052728932d8f87a527b788bd8#diff-7a7a2457283d142ea9659e12006bbc85204c3a6c89e9990b8375b35f6cb27e91
background
upgrade the adal from 0.18.x to 0.22.x will break all the proxy settings.
workaround
const HttpsProxyAgent = require('https-proxy-agent');
const axios = require('axios')
axios.defaults.proxy = false
axios.defaults.httpsAgent = new HttpsProxyAgent('http://MY_PROXY:8888')

good to have

update the readme file to state the proxy issue
check the PR carefully next time
rollback the adal upgrade

proxy issue with axios

https://github.com/axios/axios/issues/2072#issuecomment-567473812

Thanks for reporting @AlphaWong!
Do you have any pointers to any official recommendation from the adal team?
@sadasant, Please consult with the adal team to confirm the right next steps here

Thanks for reporting @AlphaWong!
Do you have any pointers to any official recommendation from the adal team?
@sadasant, Please consult with the adal team to confirm the right next steps here

emm, as my working environment is behind proxy. And we are enterprise user of Azure.
The change from request to axios is really surprise our devops team.
Also, then version number remain at 0.2.x that we believe it will not introduce a broken change.

Hello @AlphaWong, we’re still working on this. I’m planning to write back this week with more information.

@AlphaWong Hello! I need to be able to narrow this down for the Adal team. What error are you getting exactly? do you have a minimal example that reproduces the issue?

@AlphaWong Thank you for reporting this. I am from the adal-node team and. @sadasant and @ramya-rao-a raised this issue for us. Apologies for the inconvenience.
This is a side effect we did not see coming when we moved from npm request to axios as the package of choice for httpRequests for adal-node. To give you a brief background, we are currently making only security fixes for all of our adal libraries and were asked to upgrade from request to any other network package for adal-node early this year. Since we fully expected axios to support all the use cases request does including the proxies we have changed it under the hood and did not expect to break it.
We only discovered later that axios has a problem. supporting proxies by default and the same issue is tracked in our new library msal-node. Since we are not pushing any changes to adal-node and soon archiving the repo, we decided we will fix this in msal-node going forward.
I will make sure we add this info in the adal-node repo for anyone using it. We are soon moving all our older repos to a single mono repo and I will upgrade the docs once we conclude that activity.
Thank you for root causing this helping us catch this use case.

Added a PR in adal-node repo here

Thanks @sameerag!
@sadasant Let's add a similar note to the readme in this repo as well

On the other hand, I pushed some changes to the PR @AlphaWong had already created. See https://github.com/Azure/ms-rest-nodeauth/pull/131

Version 3.1.0 of the @azure/ms-rest-nodeauth package will include a note on the known proxy issue in the readme


[BEAM-9252] Update to vendored gRPC without problematic module-info.class and Main.class

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

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @iemejia @amaliujia
CC: @sunjincheng121

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit


Fixed Polish translation

Please rebase your branch. They conflict with master.

Ok, done.

Thanks for your contribution! I merged your changes manually with https://github.com/minetest-mods/moreblocks/commit/8b10e0721e78799e2abe64eb0c8625485577d49b.


connecting to more than one thread network at the same time.

Does any one knows if its possible to join one network and than move the node to another network that uses same masterkey and same PANID and connecting to that network without having to rejoin in that network ?
Just to be more clear: I have a threadnetwork in my house and another at the office. I want to move a device from my house to the office without having to rejoin to that network. Both networks has same panid, both commissioners have same masterkey.

Are there other Thread Network parameters that differ between the home and office networks? If the Thread network parameters are the same, then there should be no issue. In fact, from a Thread network perspective, the home and office are simply two different partitions of the same Thread network.

@jwhui
I can build both networks with same `parameters as those networks do not see each other. I'll test and see how it works thanks.


Rename LICENCE file to LICENSE

Typo in the LICENSE file name. With this patch also matches what the makefile expects.

Thanks!


Can't read the .json from the backup folder

I'm trying to get this running. Using docker-compose in a fresh ec2 instance (so should be be minimal conflicts)
Running docker compose, mostly works, I see the running 'embed', 'php' and nginx container in 'docker images', but the manticore one never starts (stuck in a restart loop)
Manticore 6.3.7 626b32779@24091010 dev (columnar 2.3.1 f9ef8b9@24090411) (secondary 2.3.1 f9ef8b9@24090411) (knn 2.3.1 f9ef8b9@24090411)
Copyright (c) 2023-2024, Manticore Software LTD (https://manticoresearch.com)

Manticore Backup version: 1.3.9
Copyright (c) 2023-2024, Manticore Software LTD (https://manticoresearch.com)

Manticore config file:
Backup dir: /
2024-12-27 18:30:11 [Info] Stored versions: {"backup":"1.3.9","manticore":"6.3.7 626b32779@24091010 dev","columnar":"2.3.1 f9ef8b9@24090411","secondary":"2.3.1 f9ef8b9@24090411","knn":"2.3.1 f9ef8b9@24090411","buddy":"2.3.13"}
2024-12-27 18:30:11 [Info] Current versions: {"backup":"1.3.9","manticore":"6.3.7 626b32779@24091010 dev","columnar":"2.3.1 f9ef8b9@24090411","secondary":"2.3.1 f9ef8b9@24090411","knn":"2.3.1 f9ef8b9@24090411","buddy":"0.0.0"}
2024-12-27 18:30:11 [Info] Starting to restore...

Manticore config
  endpoint =  http://<IP_ADDRESS>:9312
2024-12-27 18:30:11 [Info] Restoring config files...
2024-12-27 18:30:11 [Error] copyFile: failed to read the path: /docker-entrypoint-initdb.d/config/var/lib/manticore/manticore.json

I think (dont have any experience with manticore-backup) that means it read the versions.json from the backup folder (guessing that that what the 'stored versions' is showing)
I did restore the backup.tar.gz file (following instructions in README.md), so I think have the file
$ find -name manticore.json -ls
201326787      4 -rw-------   1 ec2-user ec2-user       70 Dec  4 09:00 ./containers/manticore/backup/config/var/lib/manticore/manticore.json

which seems to match where the volume is mounted
111-    volumes:
112-      - image-search-manticore-storage:/var/lib/manticore:rw
113:      - ./containers/manticore/backup:/docker-entrypoint-initdb.d:rw

Because the container never starts, I can't figure out how to login to it, to diagnose.

Oddly, if rename the volume in docker-compose.yaml (add test at start of folder name)
   volumes:
      - image-search-manticore-storage:/var/lib/manticore:rw
      - ./containers/manticore/backup:/test-docker-entrypoint-initdb.d:rw

That allows the manticore container to start. As no loner matches
https://github.com/manticoresoftware/docker/blob/master/docker-entrypoint.sh#L245
I can then login to the container, and run restore manually (having first removed files from data folder)
root@manticore:/var/lib# mv manticore/*  manticore.old/
root@manticore:/var/lib# ls -al manticore/
total 4
drwxr-xr-x. 4 manticore manticore  56 Dec 27 20:11 .
drwxr-xr-x. 1 root      root       27 Dec 27 20:11 ..
drwxr-xr-x. 3 manticore manticore 183 Dec 27 18:16 .extra
-rw-r--r--. 1 manticore manticore   8 Dec 27 18:16 .extra.installed
drwxr-xr-x. 2 manticore manticore 131 Dec 27 18:16 .mcl
root@manticore:/var/lib# manticore-backup --force --backup-dir='/' --restore='test-docker-entrypoint-initdb.d'
Copyright (c) 2023-2024, Manticore Software LTD (https://manticoresearch.com)

Manticore config file:
Backup dir: /
2024-12-27 20:11:45 [Info] Stored versions: {"backup":"1.3.9","manticore":"6.3.7 626b32779@24091010 dev","columnar":"2.3.1 f9ef8b9@24090411","secondary":"2.3.1 f9ef8b9@24090411","knn":"2.3.1 f9ef8b9@24090411","buddy":"2.3.13"}
2024-12-27 20:11:45 [Info] Current versions: {"backup":"1.3.9","manticore":"6.3.7 626b32779@24091010 dev","columnar":"2.3.1 f9ef8b9@24090411","secondary":"2.3.1 f9ef8b9@24090411","knn":"2.3.1 f9ef8b9@24090411","buddy":"0.0.0"}
2024-12-27 20:11:45 [Info] Starting to restore...

Manticore config
  endpoint =  http://<IP_ADDRESS>:9312
2024-12-27 20:11:45 [Info] Restoring config files...
2024-12-27 20:11:45 [Info]   config files - OK
2024-12-27 20:11:45 [Info] Restoring state files...
2024-12-27 20:11:45 [Info]   state files - OK
2024-12-27 20:11:45 [Info] Restoring data files...
2024-12-27 20:11:56 [Info]   tables' files - OK
2024-12-27 20:11:56 [Info] The backup '/test-docker-entrypoint-initdb.d' was successfully restored.
2024-12-27 20:11:56 [Info] Elapsed time: 11.53s
2024-12-27 20:11:56 [Info] Done

... this doesnt work, because the restore happens while searchd is running. restarting the container manticore.json is rewritten without any indexes.

ok, for now found a way to get it running. I stopped the container, and the copied the file into the volume from the host.
sudo cp /home/ec2-user/manticore-image-search/docker/containers/manticore/backup/config/var/lib/manticore/manticore.json /var/lib/docker/volumes/docker_image-search-manticore-storage/_data/manticore.json
/home/ec2-user/manticore-image-search is where used git clone to download the repo.
So

change the volume folder in docker-compose.yaml
use docker-compose up to start the cluster
login to the 'manticore' container docker exec -it $container /bin/bash
remove the manticore.conf, manticore.json and the rest of files in /var/lib/manticore
run manticore-backup --force --backup-dir='/' --restore='test-docker-entrypoint-initdb.d'
exit the container, and stop it `docker stop $container
overwrite manticore.json from the repo into the volumn
star the container again
demo seems to be running!

(Just posting this in case helps others - but will try to diagnose why it didnt work out the box, once gain more experience!)


Option 'quiet' is actually supposed to be 'silent'

I was unable to get quiet to work, however adding silent: true worked.
NOTE: this is a ticket moved from gulp-livereload

After checking the code and testing it a few times, I came to the conclusion that quiet works, but silent however doesn't. Also, the word silent isn't even part of the code, so it's probably related to your own setup, rather than the plugin.
Regarding quiet: Could it be possible that you've tried quiet: false instead of quiet: true?

Ah interesting. I did try quiet: true, however it didnt work then. I remember finding the "silent" word from somewhere (another source the task relies upon??), and the task didnt surface the quiet correctly. If its working for you, go ahead an close. :)
If you are planning on maintaining this, ill switch our projects over here.
thanks!!

@TrevorJTClarke Okay! :blush:

If you are planning on maintaining this, ill switch our projects over here.

Yep, I'm maintaining from now on. Sounds like an awesome idea!


Xcode8 & swift 2.3 TransitionAnimation  class "ElevateTransitionAnimation" build Error

Xcode8 & swift 2.3 TransitionAnimation  class ElevateTransitionAnimation build Error
Line 88, 98 error
Cannot assign value of type "ElevateTransitionAnimation" to type "CAAnimationDelegate?"
Line 104 error
Method does not override any method from its superclass

TransitionAnimation, 3.0.4
TransitionTreasury, 3.0.4

Help me please
Thank you

Well ~
I will update as soon.

@DianQK  thanks

I have push new tag 3.1.0 for Swift 2.3.


Simple web service to return everything we know about a given reimbursement

Specially for internal reports (e.g. something strange found during analyses, needing further investigation before public reports), a web service to return everything we know about a specific record from the Quota for Exercising Parliamentary Activity would come in handy.
By everything we know, I mean the following:

Record as reported by Chamber of Deputies (e.g. dataset.iloc[0] with dataset being pd.read_csv('data/2016-08-08-current-year.xz').
Image of the receipt (check related work in #33).
Detailed information about the company receiving the payment (#19 is creating such dataset).

This short notebook could be replaced by a URL to this web service, with 5621548 (document_id) or<PHONE_NUMBER>0107 (cnpj_cpf) as parameter.

I can code an API that serves these info as JSON (I'd do it in Django or Flask if there is no objection).
What I need:

[ ] Any option to host it for free? (Postgres free plan at Heroku list the database o 10k rows) 😁
[ ] Anyone willing to work on the visual design and front-end? People from Telegram that said you would like to contribute to a website, I need you 🤘

@cuducos, I would like to learn more about Python, if you've some time to pair, let me know :grin:

If we're building an interface can we consider to have it together with the
project website (the one initially discussed on Telegram)? I think it would
be great to have everything in one place.
2016-09-02 19:09 GMT-03:00 flp<EMAIL_ADDRESS>
@cuducos https://github.com/cuducos, I would like to learn more about
Python, if you've some time to pair, let me know 😁
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/datasciencebr/serenata-de-amor/issues/34#issuecomment-244498910,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABISK3RYfZhWnCw-EGwBpVTG5FRIF839ks5qmJ6rgaJpZM4Jz94m
.

--
Bruno Pazzim
http://brunopazzim.com
+55 (51) 8187 3076

we will discuss about the contents of the site?
done that , we can get the prototypes.

Ok, after the discussion from the chat yesterday, I'm taking the following path:

Having an API/web service ASAP will free @Irio some valuable time to be spent on the exploration of the datasets, proof of concept, and proper AI, so I'm coding this simple API ASAP today or tomorrow, maximum on Monday.
I think we can integrate this in a web site for the project, but as this will take time, let's work in the institutional and more portal-like in parallel with no ASAP mood.
If the stack I choose to this ASAP API doesn't fit whatever we decide to do later, there's a great trash bin in my desktop and I don't mind throwing away my work there if (I'll be happy knowing it served its purpose for a while and that something better took its place); if we decided to integrate the institutional, portal-like and API in a single repo later, I also would be happy to be part of the team. TL;DR whatever we decide later, I'm in.

I'm probably using Python and Django for the backend and, Bourbon family for the front-end; raw Javascript or Elm (only if needed).
I'd love to pair, so feel free to get in touch if you wanna code together one of these days. Probably it will be something quick, just a few hours is enough — Drop a line if you wanna join me.

Quick follow up:

We have a working version of the JSON API ready to use, including query URL parameters for filtering (it's documented here)
We have a limited visual interface that only allows searching by document_id
The all the ~2 million records from the datasets are already loaded in the web service database

I believe we can close this issue as soon as I add more searching features to the visual version — and any further improvements could be added as issues in Jarbas repo, ok?

It's already enough for now, @cuducos. Mission accomplished. Let's move new features to its own issue tracker. 💯


Yetus should be accessible outside pull requests

Please implement a way to run Yetus checks on our code changes before we create a pull request. Right now, we submit a PR, and then come to know about Yetus errors as part of the checks.  We end up wasting circleCI bandwidth in iterating over Yetus failures, and becomes a time hurdle in code reviews.
What would be good is to have a way to run Yetus on our local EVE repository, so that we can validate Yetus in our laptop before we even create a PR.

One easy workaround is to install the tools that yetus uses internally (revive, shellcheck, hadolint, pylint) in your development environment. There are editor plugins, modules, packages which can be added which show one the errors/warnings as you type.
Regards,
Chirag Kantharia.
On 10 Aug 2019, 12:13 PM +0530, cshari-zededa<EMAIL_ADDRESS>wrote:

Please implement a way to run Yetus checks on our code changes before we create a pull request. Right now, we submit a PR, and then come to know about Yetus errors as part of the checks. We end up wasting circleCI bandwidth in iterating over Yetus failures, and becomes a time hurdle in code reviews.
What would be good is to have a way to run Yetus on our local EVE repository, so that we can validate Yetus in our laptop before we even create a PR.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

This approach will not work. How do we make sure everybody runs the same set of checks and they are in sync with the Yetus configuration?
Thanks
Hari

On 10-Aug-2019, at 7:21 PM, Chirag Kantharia<EMAIL_ADDRESS>wrote:
One easy workaround is to install the tools that yetus uses internally (revive, shellcheck, hadolint, pylint) in your development environment. There are editor plugins, modules, packages which can be added which show one the errors/warnings as you type.
Regards,
Chirag Kantharia.
On 10 Aug 2019, 12:13 PM +0530, cshari-zededa<EMAIL_ADDRESS>wrote:

Please implement a way to run Yetus checks on our code changes before we create a pull request. Right now, we submit a PR, and then come to know about Yetus errors as part of the checks. We end up wasting circleCI bandwidth in iterating over Yetus failures, and becomes a time hurdle in code reviews.
What would be good is to have a way to run Yetus on our local EVE repository, so that we can validate Yetus in our laptop before we even create a PR.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/lf-edge/eve/issues/183?email_source=notifications&email_token=ALXSTFL2Z4NRU6JLESVO3RLQD3BXHA5CNFSM4IKYXOI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4AN5TQ#issuecomment-520150734, or mute the thread https://github.com/notifications/unsubscribe-auth/ALXSTFIMMBAQR7ZRJWD3DYTQD3BXHANCNFSM4IKYXOIQ.

@cshari-zededa two points, first of all, you can run yetus easily on your own. Just follow the same steps outlined in our .circleci config yaml https://github.com/lf-edge/eve/blob/master/.circleci/config.yml#L46
Also, personally I have no problems with using PR mechanism to run yetus -- sure your first PR is likely to fail, but that's not that big of a deal and you can always follow up with a change that takes care of yetus feedback.

I can sympathize here. If I have to wait for a PR test run to report success or failure, it is going to slow down dev cycles. That has led to my personal preference (not always realistic, but preference nonetheless) for my CI config files to always do make <something>, so that I can run the same thing locally just as easily.
Can we perhaps have a docker image built that contains everything yetus needs (auto-correct keeps changing that to "fetus", which is odd - "contains everything fetus needs"?), so that both circleci and a normal user can just run make ci or even make yetus and get the exact same output quickly?

I can sympathize here. If I have to wait for a PR test run to report success or failure, it is going to slow down dev cycles. That has led to my personal preference (not always realistic, but preference nonetheless) for my CI config files to always do make , so that I can run the same thing locally just as easily.

I actually don't get it: for me this is the other way around -- PRs are cheap and fire-and-forget. I typically work on a few issues in parallel anyway so while one PR is testing I can spend time doing something else. In fact, this is much easier than to try and run things locally. Once yetus posts its feedback on a PR -- fixing it is typically super straightforward as well.

Can we perhaps have a docker image built that contains everything yetus needs (auto-correct keeps changing that to "fetus", which is odd - "contains everything fetus needs"?), so that both circleci and a normal user can just run make ci or even make yetus and get the exact same output quickly?

We already have that container and how to run it specified in a circleci config. If you want to hook it up to Makefile -- sure that'd be fine, but personally I have no need for it so it'll have to be one of you guys actually doing the work ;-)

I actually don't get it: for me this is the other way around -- PRs are cheap and fire-and-forget. I typically work on a few issues in parallel anyway so while one PR is testing I can spend time doing something else

Different strokes for different folks and all that. :-)

We already have that container and how to run it specified in a circleci config. If you want to hook it up to Makefile -- sure that'd be fine, but personally I have no need for it so it'll have to be one of you guys actually doing the work ;-)

Consider it done. If it makes life easier for some people, happy to see it done. See #185

FWIW, a make yetus rule got added when #195 was merged, so this issue may deserve to be closed. There may be some bugs with the implementation, but those probably should be filed as new issues.

Agreed. If there are bugs, they should be under new issues. If the way to run it isn’t sufficient, then we need a new issue describing such improvement.
Closing.


How to clear the canvas as we do in js?

The only way is to draw a canvas size rectangle with background color?But default background color is transparent, and I tried using transparent bgColor,but has no effect.
Annother question is about fyne.After I added the c.content() into container,I used ctx to change the canvas(add more lines),then I tried to refresh it using "c.content().refresh()",but it didn't work.

Regarding your first question, if you use the Canvas renderer, you can call c.Reset() to clear the canvas. If you directly use another renderer (such as the rasterizer) this is usually not possible and you'd need to draw a rectangle the size of the canvas of white (default color is black, you need to set the fill color to white). In the case of the Fyne renderer you can however, since it is a wrapper around Canvas. You can thus do something like:
package main

import (
	"fyne.io/fyne/v2"
	"fyne.io/fyne/v2/app"
	"github.com/tdewolff/canvas"
	canvasFyne "github.com/tdewolff/canvas/renderers/fyne"
)

func main() {
	c := canvasFyne.New(200.0, 100.0, canvas.DPMM(10.0))
	ctx := canvas.NewContext(c)
	if err := canvas.DrawPreview(ctx); err != nil {
		panic(err)
	}

        c.Reset() //  THIS WILL CLEAR THE CANVAS

	a := app.New()
	w := a.NewWindow("Canvas")
	w.Resize(fyne.Size{800, 400})
	w.SetContent(c.Content())
	w.ShowAndRun()
}

Thanks for your answer.
I tried c.reset(),it worked very well.
But in fyne, I tried to update the c.content(),failed again.
Because I need more elements in the main fyne window,so I used Window.Canvas().Overlays().Add(c.content())
After that ,after some events,I need to redraw the canvas,but I can't refresh the content.

I don't understand what your problem is. Honestly I'm not a Fyne expert, but if there is a bug with Canvas I'd be happy to help.

I found a way to solve it.
I used a fyne.canvas.RasterFromImage,and the RasterFromImage has a generator which can be modified.
myRaster.Generator = func(w, h int) image.Image {
return c.Content().(canvas.Image).Image
}
after I changed the canvas content =>myRaster.Refresh()=>Done!
My project need to render ATC map with route/waypoints, when nesseary, map need to be transformed and refreshed by user.In the past I did this using js and html5.Recently,I switch my project to golang for 'goroutine',but golang dosen't offer many choices for me to draw the UI which need high 2d redering performance.Thanks very much for you canvas project,it's very helpful!
By the way ,any other suggestion to generate the canvas.content( canvas.image).Image faster?Using another renderer?

Great! Unfortunately you're stuck with a rasterizer (slow) and probably sampling in Fyne. Not sure if there's a way to directly draw to the screen with Fyne, but the rasterizer is hard to optimize, it is already using a high-performance implementation. You could draw to a smaller canvas size and stretch the result, or use (way) less path commands, or increase the PixelTolerance value.

I Set the canvas size = display area size, 1:1 for pixel, I don't know if it will help.
And I split the map into several layers and use go routine to update the content .
I will try use image rederer in fyne since you said it has better performance.


Suggestion to simplify Dockerfile

Thank you for your work, this is a really useful tool!
I have a minor suggestion to simplify the Dockerfile:
FROM instrumenta/conftest:v0.18.2
LABEL MAINTAINER Steven Wade<EMAIL_ADDRESS>COPY policies/* /policies/
ENTRYPOINT ["/conftest", "test", "-p", "/policies"]

# Usage: docker run --rm -v $PWD/demo:/demo deprek8ion:latest /demo

This would make the install.sh unnecessary. I can create a PR if you're interested.
One more thing: would it be possible to also host the container on docker hub - it has a very straight-forward GitHub integration and isn't down currently...

@chgl a PR for this would be much appreciated.
I am planning to move this over to gcr.io in the coming week.

Closed as part of #14