Please include using Events API Health data can be queried up to 1 year using the parameter QueryStartTime

[Enter feedback here]
https://docs.microsoft.com/en-us/azure/service-health/resource-health-overview#history-information
You can access up to 30 days of history in the Health history section of Resource Health.
Please include Events API can be used and data can be queried up to 1 year using the parameter QueryStartTime.
https://docs.microsoft.com/en-us/rest/api/resourcehealth/events/list-by-subscription-id
Mutliple customer has approached support to get this information.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: aee61956-ad7e-4573-3bbb-461f3043bcb1
Version Independent ID: cdf50dff-210a-54d9-cc3c-717dc690d4b3
Content: Azure Resource Health overview - Azure Service Health
Content Source: articles/service-health/resource-health-overview.md
Service: service-health
GitHub Login: @rboucher
Microsoft Alias: robb

@SauravB-MS Thanks for your comment! We will review and provide an update as appropriate.

@SauravB-MS I have verified and updated the document as required. The update should go live in some time i.e., in less than 24 hours. Thanks again!


⚠ ClamAV has degraded performance

In a44455d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 247 ms

Resolved: ClamAV performance has improved in a3a9f0b after 10 minutes.


Lexical search added

very very simple lexical search

please rename the lexical search files to lexical_search rather than lexical-search

please rename the lexical search files to lexical_search rather than lexical-search

done


Update default colors to "light mode"

Expected Behavior
Without any extra configuration, the colors should match the comp in LLK/scratch-gui#1
Actual Behavior
The default colors of the workspace and toolbox are "dark mode"

Possibly linked to #714 and #295

This was fixed.


Implement a CMS

First start off with a CMS that has the ability to add content pages and a roaster to the database. Content pages are pretty straight forward. We should also have the ability to create a "roaster detail page" from the CMS.
Each roaster should have the following information:MVP

Name
Location
Short Description
Logo or Featured Image

Done here: https://github.com/danigirl329/local-roasters/commit/edfe4d165421d2f3569e466cb2e05eaffb20280a


Make listTests always print to console.log

Summary
Always print the output of the --listTests option to console.log, even when using --json flag (which is otherwise redirected to stderr) or the --stdErr flag.
See issue: https://github.com/facebook/jest/issues/4388
Test plan
Updated the existing test

Updated 😄 I wanted to see the results from CI because I'm on Windows at the moment and some tests are unstable.

The test passes on my WIndows machine... Will try again on my mac but only have access to it tomorrow!

Seems like the test is failing on AppVeyor.

Yeah - I noticed the same on my Windows pc at home. The test output is different on Win/Mac. I'll investigate further when I have both machines available at the same time 😄
But it seems like for Windows there's an additional \n added?

Sorry for the additional commits, but it was the fastest way for me to test between Mac/Windows. If you want me to squash them, let me know.
I eventually ended up finding a way that the test passes on both machines, though I do not understand how it worked before. The issue (I think) is that in the test files we were splitting and joining with EOL from the os package (which probably was different for the Windows tests).
AppVeyor now started failing on some other tests - but that seems not to be related to my changes? Is it possible to restart?

Thank you.


Make data size a criteria for batches when writing with bigqueryio.

Respecting bigquery's 10MB API limit
Making errors from bigquery API more debuggable

Please add a meaningful description for your change here

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.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

R: @lostluck

Hmmm...  not quite ready. Either I'm not calculating the size right or there is a lot of additional overhead for sending this data.

OK. I've updated the size estimation a little bit. I'm likely still undercounting, but having some size constraint seems strictly better than none.

Thanks for the comments! With regards to the size computation, I'd really like your recommendation on how to proceed. This is the best I could think of.

 It seems like master is having the same problem.

That's a wholely unrelated issue under separate investigation. Apparently providing the same input in the same order to MD5 hashing can lead to different results somehow.
LGTM to me.
@aaltay Please merge. Thanks!

Run Go Postcommit


Refactor: define CLI with click

Closes #29
Completely rewrites the CLI commands away from manual argparse construction to use @click.command and @click.group definitions.
This lead to a massive simplification of the tests as well :relaxed:

Used the newly refactored CLI to do the hours download and conversion today -- worked without any issues :+1:


Support the ability to parse IdP XML metadata (remote url or file) + extend MultiCert support

Adding more test to #139.
Modify how multiple cert support works. Now getIdpx509certMulti only returns the cert registered as Multi following the description that had the method.
Add multiCert support on LogoutRequest and LogoutResponse

Reference: #139 and #101

Hi @pitbulk, do you have some news about the release of the new version?
Thanks


What is the test contract for Drip to test it?

Do you have a sandbox for the drip to test this application?
Srikanth
<EMAIL_ADDRESS>

We do not have any sandbox for the drip smart contracts.


Move package.base_path to main API

Hi
Hoping to use package's base_path property to make it easier to find, say, a README.md in uploaded datapackage in datapackager..
I note though that the property mentions its use is deprecated?
Any chance this warning was meant just for default_base_path?
Just want to make sure I'm using the right reference. Thanks in advance.

@mattRedBox
It was deprecated as a part of API simplification.
Because there is a clear use case (https://github.com/frictionlessdata/ckanext-datapackager/issues/60) let's move it to the main API.
Anyway you can safely use it while it exists in actual API and we have this issue

Fixed by #217

Release is blocked by https://github.com/frictionlessdata/specs/issues/616


[Bug]: Docker container vue-spree-frontend-1 fails to find rifraf command

Expected Behavior
I'd expect the instructions to use the dockerized setup to run both the backend and the frontend explained at https://github.com/vuestorefront/spree#running-vue-storefront--spree-in-docker to work
Actual Behavior

the bin/setup and bin/seed work as expected
for bin/start there is a problem
** the docker-compose for the spree backend starts and runs (I can access http://localhost:4000/).
the docker-compose for the vue frontend fails

$ docker-compose ps
vue-spree-frontend-1   "docker-entrypoint.s…"   frontend            exited (127)
$ docker-compose logs
vue-spree-frontend-1  | yarn run v1.22.5
vue-spree-frontend-1  | $ yarn build:api-client && yarn build:composables && yarn build:theme
vue-spree-frontend-1  | $ cd packages/api-client && yarn build
vue-spree-frontend-1  | $ rimraf lib server && rollup -c
vue-spree-frontend-1  | /bin/sh: 1: rimraf: not found
vue-spree-frontend-1  | error Command failed with exit code 127.
vue-spree-frontend-1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
vue-spree-frontend-1  | error Command failed with exit code 127.
vue-spree-frontend-1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
vue-spree-frontend-1  | error Command failed with exit code 127.
vue-spree-frontend-1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
vue-spree-frontend-1  | yarn run v1.22.5
vue-spree-frontend-1  | $ concurrently "yarn:dev:*" --hostname <IP_ADDRESS>
vue-spree-frontend-1  | /bin/sh: 1: concurrently: not found
vue-spree-frontend-1  | error Command failed with exit code 127.
vue-spree-frontend-1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Possible Solution
No response
Steps to reproduce

stock debian 11
install docker + docker-compose from official (docker-ce) packages

What version of Spree integration are you using?
d1c7335e476b44d3b306e7872b71c065805af7f1
What version of Node.js are you using?
14.15 (defined by Dockerfile.development)
What browser (and version) are you using?
Firefox, but doesn't matter
What operating system (and version) are you using?
Debian 11
Relevant log output
vue-spree-frontend-1  | yarn run v1.22.5
vue-spree-frontend-1  | $ yarn build:api-client && yarn build:composables && yarn build:theme
vue-spree-frontend-1  | $ cd packages/api-client && yarn build
vue-spree-frontend-1  | $ rimraf lib server && rollup -c
vue-spree-frontend-1  | /bin/sh: 1: rimraf: not found
vue-spree-frontend-1  | error Command failed with exit code 127.
vue-spree-frontend-1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
vue-spree-frontend-1  | error Command failed with exit code 127.
vue-spree-frontend-1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
vue-spree-frontend-1  | error Command failed with exit code 127.
vue-spree-frontend-1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
vue-spree-frontend-1  | yarn run v1.22.5
vue-spree-frontend-1  | $ concurrently "yarn:dev:*" --hostname <IP_ADDRESS>
vue-spree-frontend-1  | /bin/sh: 1: concurrently: not found
vue-spree-frontend-1  | error Command failed with exit code 127.
vue-spree-frontend-1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

same issue

Fixed it by adding RUN yarn global add rimraf rollup to Dockerfile.development
FROM node:14.15

WORKDIR /app
ADD . /app/

RUN yarn global add rimraf rollup
RUN yarn

EXPOSE 3000
CMD './docker-entrypoint.development.sh'

And yarn install in docker-entrypoint.develooment.sh
#!/bin/sh
yarn install
yarn build
yarn dev --hostname <IP_ADDRESS>

Not sure it is the right way to do it though.

Hi @Con607 - interesting issue, we haven't run into it before. Technically rimraf is included in package.json so it should be installed already. Let me try to reproduce it on a clean install.

Hi @Con607 @yangyao I ran a fresh container based on the readme and it launched fine without any issues.
Does it happen for you on a freshly cloned git repo?

@rafalcymerys I can confirm this happens on a freshly cloned git repo.  @Con607's workaround works insofar as getting the application running

The Dockerfile's both run yarn, but they should probably run yarn install to install rimraf and such which are listed as dev dependencies.

The issue is still valid.

Interesting. What if you just create a dummy .git directory as a part of the Dockerfile? It may be slightly better than including the full repo in the container image


About disclosureIndicatorImage

How Can I change disclosureIndicatorImage position When I change headheaderComponents title?

Hello @MourinhoLove! This is not supported currently, and I don't plan to add this feature in nearest future, sorry.

I am also in favor of this as I want the arrow to be directly right after my text. My text displayed is dynamic so a predefined width won't always work.

@MourinhoLove Here is what worked for me. When creating a new drop down menu with dynamic text, calculate the size of the string as follows:
let size = (title as NSString).size(attributes: customTextAttributes)
let dropdownMenu = MKDropdownMenu(frame: CGRect(x: 0, y: 0, width: size.width + 35, height: 44))

Notice I add +35 to the width. This is because I want the disclosureIndicatorImage to fit into the bounds as well. This could be slightly smaller/larger depending on the size of your indicator image.
Hope this helps!

@Daltron  Thank you for your answer. Its help me.

I would also find this very useful. I'm not sure I want to recreate the menu every time a menu item is selected.

@keithburgoyne +1

@Daltron do you have the obj-c code for that? I need to have the image next to the text.
Thanks


Add timestamp to Yugatool reports

I have built yugatool with this feature.
The test-binary is available on lincoln: ~/vinay/yugatool
The output looks like this:
` bin/yugatool --master-addresses=$MASTERS   cluster_info  --skiphostverification    | head -15
[ ReportInfo ]
DATE                 HOSTNAME                 TOOLS_VERSION                        TOOLS_BUILD
2022-12-13T05:10:03.266346966Z   kachand-yb   d9fcda2039ce3aae2e92f9731b084db9f15965fd   2022-12-12T21:09:05-08:00
[ Cluster ]
CLUSTER_UUID               LIVE_REPLICAS                      ZONES                      VERSION
d89e6b62-8afb-4310-8e13-db7bf482afa6   3               ["us-west1-a" "us-east1-b" "us-central1-a"]   23
...
`
Please test.

Output looks good. Do you have this checked into a branch somewhere for a quick code review?

Output date is now better formatted:
[ ReportInfo ]           DATE              HOSTNAME                 TOOLS_VERSION                        TOOLS_BUILD  2022-12-14T04:23:10 UTC   kachand-yb   3241615a8e28be50941705e316073e71e8af2593   2022-12-13T19:30:36-08:00
Checked in to add-report-header branch.
Also updated the output of --version to include build date.

Resolved by #45


Run a ROS buildfarm deployment on a single host.

🚧 🚧 🚧 This is a work in progress and is neither functioning nor ready for test or production deployments.
Opening this pull request now so I can talk to myself during development and track individual side effects of these changes. There are detailed commit messages for most changes that are more involved than typos or fixups.
This pull request will add a third role module to the puppet source and will link to a forthcoming companion pull request in ros-infrastructure/buildfarm_deployment_config that will add the role to the configuration scripts.
During the updates from Trusty to Xenial I started a process to refactor the puppet modules to improve code sharing between the buildfarm roles and reduce the maintenance burden. This pull request refactors the puppet modules further in support of making the different profiles co-habitable. In most cases this involves pushing resource declarations into dedicated modules so they can be included without redeclaration in each profile.
This will resolve #42

This work has fallen off of my priority queue and I don't know when it will climb back up. I've moved the PR to an untargeted milestone and am going to close it but leave the standalone-host branch around.


problem with custom query and postgreSQL

hi all im trying use this query
$users = (new Query())
    ->select([
        'date(to_timestamp(created_at)) as dateResult',
        'array_agg(DISTINCT id) as ids','count(*) as count'
    ])
    ->from(User::tableName())
    ->groupBy(['date(to_timestamp(created_at))'])
    ->orderBy(['dateResult' => SORT_DESC])
    ->limit(10)->all();

but i get this error
The SQL being executed was: SELECT date(to_timestamp(created_at)) as dateResult, array_agg(DISTINCT id) as ids, count(*) as count FROM "user" GROUP BY date(to_timestamp(created_at)) ORDER BY "dateResult" DESC LIMIT 10

and testing in PGADMIN 3, the problem is "dateResult"  and the correct sintax is dateResult, is a bug in yii2 ?

but i get this error

It's not a text of error, it's just the executed query. Could you show the error?

SQLSTATE[42703]: Undefined column: 7 ERROR: no existe la columna «dateResult»
LINE 1: ... GROUP BY date(to_timestamp(created_at)) ORDER BY "dateResul...
^
The SQL being executed was: SELECT date(to_timestamp(created_at)) as dateResult, array_agg(DISTINCT id) as ids, count(*) as count FROM "user" GROUP BY date(to_timestamp(created_at)) ORDER BY "dateResult" DESC LIMIT 10
Error Info: Array
(
[0] => 42703
[1] => 7
[2] => ERROR:  no existe la columna «dateResult»
LINE 1: ... GROUP BY date(to_timestamp(created_at)) ORDER BY "dateResul...
^
)
↵
Caused by: PDOException
SQLSTATE[42703]: Undefined column: 7 ERROR: no existe la columna «dateResult»
LINE 1: ... GROUP BY date(to_timestamp(created_at)) ORDER BY "dateResul...
^
in C:\xampp\htdocs\vendor\yiisoft\yii2\db\Command.php at line 837

->orderBy(['date(to_timestamp(created_at))' => SORT_DESC])

@SilverFire  thanks, im translating my app mysql to postgreSQL, and im testing in pgadmin 3 and is a little hard find postgresql information for yii2

There is nothing special you must know in Yii to use PostgreSQL. You error does not relates Yii and it might be easily googled - there is a bunch of similar questions on SO.
Please note, GitHub issues is designed for bugs, not for questions and support. Try to dig into problem a little, instead of asking someone for a answer - you will earn much more experience.
http://www.yiiframework.com/doc-2.0/guide-start-looking-ahead.html


merging latest changes from Master back in to Oct2019updates branch

Docs Build status updates of commit 82a4e95:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/mixed-reality, working directory: W:\a404-s, target branch: HEAD, target branch commit: 67fbd66301ab09e079046d2084bc2160d3786e3f, source commit: 82a4e9549cb9d65ab196e098e201c2f5c710b77b.

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.

Docs Build status updates of commit 775462f:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/mixed-reality, working directory: W:\wbgz-s, target branch: HEAD, target branch commit: afc91e6d1c914e9902c5267a3cb0912f5211c49b, source commit: 775462f493e0ad7f71d99ee91ed3501df5f11dbd.

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.

Docs Build status updates of commit db68990:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/mixed-reality, working directory: W:\vw3n-s, target branch: HEAD, target branch commit: afc91e6d1c914e9902c5267a3cb0912f5211c49b, source commit: db689902f3934c3a346550360fcc58f52ddd5459.

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.

Docs Build status updates of commit f5d87e4:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/mixed-reality, working directory: W:\o5if-s, target branch: HEAD, target branch commit: afc91e6d1c914e9902c5267a3cb0912f5211c49b, source commit: f5d87e44497b978d656948ad3a6eb61413529b03.

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.

Docs Build status updates of commit 02f3dfe:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/mixed-reality, working directory: W:\rmxj-s, target branch: HEAD, target branch commit: afc91e6d1c914e9902c5267a3cb0912f5211c49b, source commit: 02f3dfe79f93291499be4194b717520d8ac57de4.

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.

Docs Build status updates of commit 6d48362:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/mixed-reality, working directory: W:\m4fi-s, target branch: HEAD, target branch commit: afc91e6d1c914e9902c5267a3cb0912f5211c49b, source commit: 6d48362004babcf3f8e1f4ccf1741a7ea8773a0a.

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.

Docs Build status updates of commit ddc56bc:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/mixed-reality, working directory: W:\k0oq-s, target branch: HEAD, target branch commit: afc91e6d1c914e9902c5267a3cb0912f5211c49b, source commit: ddc56bc0aeb4c3391b5e2913d7cff524b47748cb.

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.

Docs Build status updates of commit ddc56bc:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/mixed-reality, working directory: W:\0kms-s, target branch: HEAD, target branch commit: afc91e6d1c914e9902c5267a3cb0912f5211c49b, source commit: ddc56bc0aeb4c3391b5e2913d7cff524b47748cb.

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.

Docs Build status updates of commit 90d5884:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/cursors.md
:warning:Warning
View
Details

mixed-reality-docs/gaze-in-unity.md
:warning:Warning
View
Details

mixed-reality-docs/mrtk-getting-started.md
:bulb:Suggestion
View
Details

mixed-reality-docs/mrtk-porting-guide.md
:bulb:Suggestion
View
Details

mixed-reality-docs/scene-understanding-SDK.md
:bulb:Suggestion
View
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

mixed-reality-docs/Configure-Unity-Project.md
:white_check_mark:Succeeded
View

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded
View

mixed-reality-docs/app-patterns-landingpage.md
:white_check_mark:Succeeded
View

mixed-reality-docs/camera-in-unity.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-expanding-the-design-process-for-mixed-reality.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-expanding-the-spatial-mapping-capabilities-of-hololens.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-looking-through-holes-in-your-reality.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-representing-humans-in-mixed-reality.md
:white_check_mark:Succeeded
View

mixed-reality-docs/case-study-using-the-stabilization-plane-to-reduce-holographic-turbulence.md
:white_check_mark:Succeeded
View

mixed-reality-docs/design.md
:white_check_mark:Succeeded
View

mixed-reality-docs/development.md
:white_check_mark:Succeeded
View

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

mixed-reality-docs/directx-development-overview.md
:white_check_mark:Succeeded
View

mixed-reality-docs/focus-point-in-unity.md
:white_check_mark:Succeeded
View

mixed-reality-docs/gestures-and-motion-controllers-in-unity.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hand-eye-in-unit.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hands-free.md
:white_check_mark:Succeeded
View

mixed-reality-docs/hologram-stability.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-100.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-101.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-101e.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-210.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-211.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-212.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-220.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-230.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holograms-240.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-frame.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-create-host.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-create-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-custom-data-channels.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-secure-connection.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-troubleshooting.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-version-history.md
:white_check_mark:Succeeded
View

mixed-reality-docs/index.md
:white_check_mark:Succeeded
View

mixed-reality-docs/install-the-tools.md
:white_check_mark:Succeeded
View

mixed-reality-docs/interaction-fundamentals.md
:white_check_mark:Succeeded
View

mixed-reality-docs/locatable-camera.md
:white_check_mark:Succeeded
View

mixed-reality-docs/managed-debugging-with-unity-il2cpp.md
:white_check_mark:Succeeded
View

mixed-reality-docs/map-sharing.md
:white_check_mark:Succeeded

mixed-reality-docs/mixed-reality-213.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mixed-reality-250.md
:white_check_mark:Succeeded
View

mixed-reality-docs/mrlearning-asa-ch3.md
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

mixed-reality-docs/cursors.md

Line 93: [Warning] Invalid file link: 'gaze-targeting.md'.

mixed-reality-docs/gaze-in-unity.md

Line 59: [Warning] Invalid file link: 'gaze-targeting.md'.

mixed-reality-docs/mrtk-getting-started.md

Line 6: [Suggestion] Invalid date format for 'ms.date': '05/15/19'. Must be a date in format MM/DD/YYYY, no more than ten days from today. NOTE: This Suggestion will become a Warning on 11/25/2019.

mixed-reality-docs/mrtk-porting-guide.md

Line 6: [Suggestion] Invalid date format for 'ms.date': '10/14/19'. Must be a date in format MM/DD/YYYY, no more than ten days from today. NOTE: This Suggestion will become a Warning on 11/25/2019.

mixed-reality-docs/scene-understanding-SDK.md

Line 6: [Suggestion] Invalid date format for 'ms.date': '07/08/19'. Must be a date in format MM/DD/YYYY, no more than ten days from today. NOTE: This Suggestion will become a Warning on 11/25/2019.

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.


_pickle.UnpicklingError: pickle data was truncated

When I run train_net I got this.My datasets are coco2014.
Traceback (most recent call last):
File "tools/train_net.py", line 171, in
main()
File "tools/train_net.py", line 164, in main
model = train(cfg, args.local_rank, args.distributed)
File "tools/train_net.py", line 53, in train
extra_checkpoint_data = checkpointer.load(cfg.MODEL.WEIGHT)
File "/home/huanran/anaconda3/envs/maskrcnn_benchmark/maskscoring_rcnn/maskrcnn_benchmark/utils/checkpoint.py", line 61, in load
checkpoint = self._load_file(f)
File "/home/huanran/anaconda3/envs/maskrcnn_benchmark/maskscoring_rcnn/maskrcnn_benchmark/utils/checkpoint.py", line 133, in _load_file
return load_c2_format(self.cfg, f)
File "/home/huanran/anaconda3/envs/maskrcnn_benchmark/maskscoring_rcnn/maskrcnn_benchmark/utils/c2_model_loading.py", line 155, in load_c2_format
return C2_FORMAT_LOADER[cfg.MODEL.BACKBONE.CONV_BODY](cfg, f)
File "/home/huanran/anaconda3/envs/maskrcnn_benchmark/maskscoring_rcnn/maskrcnn_benchmark/utils/c2_model_loading.py", line 146, in load_resnet_c2_format
state_dict = _load_c2_pickled_weights(f)
File "/home/huanran/anaconda3/envs/maskrcnn_benchmark/maskscoring_rcnn/maskrcnn_benchmark/utils/c2_model_loading.py", line 124, in _load_c2_pickled_weights
data = pickle.load(f, encoding="latin1")
_pickle.UnpicklingError: pickle data was truncated.
I don't know why.

Hi, have you put the pre-training model in the pretrained_models directory?

Hi, have you put the pre-training model in the pretrained_models directory?

yes,I put the pre-training model in the pretrained_models directory.The model is R-50.pkl,is right?

Could you show more details? Such as your running scripts.

Could you show more details? Such as your running scripts.

log.txt just like this:
2019-04-18 16:20:52,353 maskrcnn_benchmark INFO: Using 1 GPUs
2019-04-18 16:20:52,353 maskrcnn_benchmark INFO: Namespace(config_file='configs/e2e_ms_rcnn_R_50_FPN_1x.yaml', distributed=False, local_rank=0, opts=['SOLVER.IMS_PER_BATCH', '2', 'SOLVER.BASE_LR', '0.0025', 'SOLVER.MAX_ITER', '720000', 'SOLVER.STEPS', '(480000, 640000)', 'TEST.IMS_PER_BATCH', '1'], skip_test=False)
2019-04-18 16:20:52,353 maskrcnn_benchmark INFO: Collecting env info (might take some time)
2019-04-18 16:20:55,244 maskrcnn_benchmark INFO:
PyTorch version: 1.0.1.post2
Is debug build: No
CUDA used to build PyTorch: 9.0.176
OS: Ubuntu 16.04 LTS
GCC version: (Ubuntu 4.9.3-13ubuntu2) 4.9.3
CMake version: version 3.5.1
Python version: 3.7
Is CUDA available: Yes
CUDA runtime version: 9.0.176
GPU models and configuration: GPU 0: GeForce GTX 1070 Ti
Nvidia driver version: 390.87
cuDNN version: Probably one of the following:
/usr/local/cuda-9.0/lib64/libcudnn.so.7
/usr/local/cuda-9.0/lib64/libcudnn.so.7.1.4
/usr/local/cuda-9.0/lib64/libcudnn_static.a
Versions of relevant libraries:
[pip] Could not collect
[conda] pytorch                   1.0.1           py3.7_cuda9.0.176_cudnn7.4.2_2    pytorch
[conda] torchvision               0.2.2                      py_3    pytorch
Pillow (5.4.1)
2019-04-18 16:20:55,245 maskrcnn_benchmark INFO: Loaded configuration file configs/e2e_ms_rcnn_R_50_FPN_1x.yaml
2019-04-18 16:20:55,245 maskrcnn_benchmark INFO:
MODEL:
META_ARCHITECTURE: "GeneralizedRCNN"
WEIGHT: "catalog://ImageNetPretrained/MSRA/R-50"
PRETRAINED_MODELS: 'pretrained_models'
BACKBONE:
CONV_BODY: "R-50-FPN"
OUT_CHANNELS: 256
RPN:
USE_FPN: True
ANCHOR_STRIDE: (4, 8, 16, 32, 64)
PRE_NMS_TOP_N_TRAIN: 2000
PRE_NMS_TOP_N_TEST: 1000
POST_NMS_TOP_N_TEST: 1000
FPN_POST_NMS_TOP_N_TEST: 1000
ROI_HEADS:
USE_FPN: True
ROI_BOX_HEAD:
POOLER_RESOLUTION: 7
POOLER_SCALES: (0.25, 0.125, 0.0625, 0.03125)
POOLER_SAMPLING_RATIO: 2
FEATURE_EXTRACTOR: "FPN2MLPFeatureExtractor"
PREDICTOR: "FPNPredictor"
ROI_MASK_HEAD:
POOLER_SCALES: (0.25, 0.125, 0.0625, 0.03125)
FEATURE_EXTRACTOR: "MaskRCNNFPNFeatureExtractor"
PREDICTOR: "MaskRCNNC4Predictor"
POOLER_RESOLUTION: 14
POOLER_SAMPLING_RATIO: 2
RESOLUTION: 28
SHARE_BOX_FEATURE_EXTRACTOR: False
MASK_ON: True
MASKIOU_ON: True
DATASETS:
TRAIN: ("coco_2014_train", "coco_2014_valminusminival")
TEST: ("coco_2014_minival",)
DATALOADER:
SIZE_DIVISIBILITY: 32
SOLVER:
BASE_LR: 0.02
WEIGHT_DECAY: 0.0001
STEPS: (60000, 80000)
MAX_ITER: 90000
2019-04-18 16:20:55,245 maskrcnn_benchmark INFO: Running with config:
DATALOADER:
ASPECT_RATIO_GROUPING: True
NUM_WORKERS: 4
SIZE_DIVISIBILITY: 32
DATASETS:
TEST: ('coco_2014_minival',)
TRAIN: ('coco_2014_train', 'coco_2014_valminusminival')
INPUT:
MAX_SIZE_TEST: 1333
MAX_SIZE_TRAIN: 1333
MIN_SIZE_TEST: 800
MIN_SIZE_TRAIN: 800
PIXEL_MEAN: [102.9801, 115.9465, 122.7717]
PIXEL_STD: [1.0, 1.0, 1.0]
TO_BGR255: True
MODEL:
BACKBONE:
CONV_BODY: R-50-FPN
FREEZE_CONV_BODY_AT: 2
OUT_CHANNELS: 256
DEVICE: cuda
MASKIOU_LOSS_WEIGHT: 1.0
MASKIOU_ON: True
MASK_ON: True
META_ARCHITECTURE: GeneralizedRCNN
PRETRAINED_MODELS: pretrained_models
RESNETS:
NUM_GROUPS: 1
RES2_OUT_CHANNELS: 256
RES5_DILATION: 1
STEM_FUNC: StemWithFixedBatchNorm
STEM_OUT_CHANNELS: 64
STRIDE_IN_1X1: True
TRANS_FUNC: BottleneckWithFixedBatchNorm
WIDTH_PER_GROUP: 64
ROI_BOX_HEAD:
FEATURE_EXTRACTOR: FPN2MLPFeatureExtractor
MLP_HEAD_DIM: 1024
NUM_CLASSES: 81
POOLER_RESOLUTION: 7
POOLER_SAMPLING_RATIO: 2
POOLER_SCALES: (0.25, 0.125, 0.0625, 0.03125)
PREDICTOR: FPNPredictor
ROI_HEADS:
BATCH_SIZE_PER_IMAGE: 512
BBOX_REG_WEIGHTS: (10.0, 10.0, 5.0, 5.0)
BG_IOU_THRESHOLD: 0.5
DETECTIONS_PER_IMG: 100
FG_IOU_THRESHOLD: 0.5
NMS: 0.5
POSITIVE_FRACTION: 0.25
SCORE_THRESH: 0.05
USE_FPN: True
ROI_MASK_HEAD:
CONV_LAYERS: (256, 256, 256, 256)
FEATURE_EXTRACTOR: MaskRCNNFPNFeatureExtractor
MLP_HEAD_DIM: 1024
POOLER_RESOLUTION: 14
POOLER_SAMPLING_RATIO: 2
POOLER_SCALES: (0.25, 0.125, 0.0625, 0.03125)
POSTPROCESS_MASKS: False
POSTPROCESS_MASKS_THRESHOLD: 0.5
PREDICTOR: MaskRCNNC4Predictor
RESOLUTION: 28
SHARE_BOX_FEATURE_EXTRACTOR: False
RPN:
ANCHOR_SIZES: (32, 64, 128, 256, 512)
ANCHOR_STRIDE: (4, 8, 16, 32, 64)
ASPECT_RATIOS: (0.5, 1.0, 2.0)
BATCH_SIZE_PER_IMAGE: 256
BG_IOU_THRESHOLD: 0.3
FG_IOU_THRESHOLD: 0.7
FPN_POST_NMS_TOP_N_TEST: 1000
FPN_POST_NMS_TOP_N_TRAIN: 2000
MIN_SIZE: 0
NMS_THRESH: 0.7
POSITIVE_FRACTION: 0.5
POST_NMS_TOP_N_TEST: 1000
POST_NMS_TOP_N_TRAIN: 2000
PRE_NMS_TOP_N_TEST: 1000
PRE_NMS_TOP_N_TRAIN: 2000
RPN_HEAD: SingleConvRPNHead
STRADDLE_THRESH: 0
USE_FPN: True
RPN_ONLY: False
WEIGHT: catalog://ImageNetPretrained/MSRA/R-50
OUTPUT_DIR: models/
PATHS_CATALOG: /home/huanran/anaconda3/envs/maskrcnn_benchmark/maskscoring_rcnn/maskrcnn_benchmark/config/paths_catalog.py
SOLVER:
BASE_LR: 0.0025
BIAS_LR_FACTOR: 2
CHECKPOINT_PERIOD: 10000
GAMMA: 0.1
IMS_PER_BATCH: 2
MAX_ITER: 720000
MOMENTUM: 0.9
STEPS: (480000, 640000)
WARMUP_FACTOR: 0.3333333333333333
WARMUP_ITERS: 500
WARMUP_METHOD: linear
WEIGHT_DECAY: 0.0001
WEIGHT_DECAY_BIAS: 0
TEST:
EXPECTED_RESULTS: []
EXPECTED_RESULTS_SIGMA_TOL: 4
IMS_PER_BATCH: 1
2019-04-18 16:20:57,746 maskrcnn_benchmark.utils.checkpoint INFO: Loading checkpoint from catalog://ImageNetPretrained/MSRA/R-50
2019-04-18 16:20:57,747 maskrcnn_benchmark.utils.checkpoint INFO: catalog://ImageNetPretrained/MSRA/R-50 points to https://s3-us-west-2.amazonaws.com/detectron/ImageNetPretrained/MSRA/R-50.pkl
2019-04-18 16:20:57,747 maskrcnn_benchmark.utils.checkpoint INFO: url https://s3-us-west-2.amazonaws.com/detectron/ImageNetPretrained/MSRA/R-50.pkl cached in pretrained_models/R-50.pkl

So Do you know how to deal with this problem?

Do you install it according to INSTALL.md?

Did you fix it @yehuanran

@anshumankmr How did you fix it? I met the same problem.


Release v1 - MVP

To be updated..
CMS

[x] Manage episodes, seasons, shows, lists and sections.
[x] Fill with data from old database.
[x] Continuous sync with the old database.
[ ] #9

Gql API

Will not be included in the first version.

Releasing to prod

[ ] Infra deploy
[ ] Mediapackage setup
[ ] Sync everything into new DB
[ ] Verify sync to legacy is working correctly

[ ] Switch deploy to tags
[ ] Log based alerts for Ingest (OPS)
[ ] Scale Up DB for Prod
[ ] Enable Backups, Failover on prod DB


How to handle resources?

Hi all,
I come from the dependency injector library, and recently I've been exploring another library to see if it could potentially replace dependency injector altogether.
I find it quite interesting, but I still have some doubts. For instance, how can I manage resource releases with this new library?
Let's consider a scenario where I have a client that needs to be released in a certain time (out of scope, raising an exception or at the end of a job to clean all resources):
def get_sqs_client_gen() -> Generator[SQSClient, None, None]:
    client: Optional[SQSClient] = None

    try:
        client = get_sqs_client()
        yield client
    finally:
        if client:
            client.close()

Is there a provider within this library to handle such resources, or should I manually handle acquisition and release by passing it as a context manager?
Thank you for your support!

I unfortunatly didn't have time to look into this myself yet. But there seems to be a similar, already resolved issue covering release of resources: https://github.com/python-injector/injector/issues/119

Yeah, thank you for your reply, I ended up using fastapi-injector even out of the "Fast API context". Thanks to the custom scope that this library offers.

Hey @mario-gazzara,
Yeah, there's no built-in mechanism for what you need here. I'd suggest going the explicit context manager route (or similar) for the time being.
I'm not opposed to introducing a mechanism for this, it's just that I haven't had a need for this in the past so my understanding of the use cases is likely poor and I don't quite have the motivation to do it myself.
@bschnitz linked to something that I think we could put in the library's documentation.

@jstasiak: I tried to create a minimal example for the documentation. I'm not sure if I did it correctly. It works, but there may be misunderstandings. Please have a look: https://github.com/python-injector/injector/pull/252

The pattern I tend to use for cleaning up resources boils down to providing an [Async]ExitStack singleton:
from contextlib import ExitStack
from dataclasses import dataclass

import injector

@dataclass
class DepA:
    def __post_init__(self):
        print("Initialized:", id(self))

    def cleanup(self):
        print("Cleaned up:", id(self))

@injector.inject
@dataclass
class App:
    a0: DepA
    a1: DepA
    a2: DepA

    def run(self) -> None: ...

class LifecycleModule(injector.Module):
    def configure(self, binder: injector.Binder) -> None:
        binder.bind(ExitStack, ExitStack, scope=injector.SingletonScope)

class SomeOtherModule(injector.Module):
    @injector.provider
    def a(
        self,
        builder: injector.ClassAssistedBuilder[DepA],
        exit_stack: ExitStack,
    ) -> DepA:
        a = builder.build()
        exit_stack.callback(a.cleanup)
        return a

def run_app():
    di = injector.Injector([LifecycleModule, SomeOtherModule])

    with di.get(ExitStack):
        app = di.get(App)
        app.run()

if __name__ == "__main__":
    run_app()

Nice example. However I'm using hundreds of classes and heavily depend on autowiring and I can't see how to get that to run with your example. Seems like I would have to a provider for every class which needs to have a cleanup. So I'll stick with my method ;).


pythonbible package exceed memory(Process running mem=660M(129.0%)) usage on Heroku server

Process running mem=660M(129.0%) when using this package on heroku

How can i resolve this issue?

Can you provide a code example that causes this memory issue? Thanks.

My guess is that it is due to overly aggressive caching within the pythonbible library. We need to do some real profiling to determine what the optimal max size of the cache ought to be. Currently, it is set to None, which means that the cache can grow indefinitely. For a quick fix, I'm going to change that to be the default max size (128 entries, I think), and will release that change shortly. For a long-term fix, I'll create a project to determine the optimal max size of the cache based on profiling exercises as well as possibly allowing for configurable cache settings.

I have released a hotfix that might help with this issue. Please upgrade to the latest version of pythonbible and try it out and let me know whether or not it resolves your specific issue. You can upgrade to the latest version by running either:
pip install -U pythonbible
or
pip install pythonbible==0.4.1
Thanks.

My guess is that it is due to overly aggressive caching within the pythonbible library. We need to do some real profiling to determine what the optimal max size of the cache ought to be. Currently, it is set to None, which means that the cache can grow indefinitely. For a quick fix, I'm going to change that to be the default max size (128 entries, I think), and will release that change shortly. For a long-term fix, I'll create a project to determine the optimal max size of the cache based on profiling exercises as well as possibly allowing for configurable cache settings.

Yes


Update fork

Updating from official repository.

Updating personal fork, yay.

Updating personal fork, yay.


Feature: implement snowflake export function #156

Description
This pull request implemented the snowflake export function to export the selected data to the local dir in parquet format.
export flow:

Use the snowflake "COPY INTO..." command to convert the selected data into parquet format and stored in the user stage. This request will have a UUID generated by Snowflake, we will append this unique id to the stage file name to prevent concurrent copy requests with the same name which Snowflake will throw an error.
Use the snowflake "GET ..." command to download the parquet file stored in the user stage to the local directory. We Use the "pattern" parameter in this command and filter out the file with the unique id.
Use the snowflake "Remove ..." command to remove the parquet file in the user stage to avoid increasing costs. We Use the "pattern" parameter in this command and filter out the file with the unique id.

Issue ticket number
issue #156
Additional Context

The encoding type of columns in the parquet file seems can not be specified in Snowflake.
We add a query Id (a uuid generated by snowflake) in our stage file name and allow partition when reach the file size limit
We set the max file size of each file to the maximum of snowflake setting (5GB)
The max file size does not have a lower bound, but the minimum file size is 1 Mb though. (found when developing)
the partition file will have a subfix in the file name like "\d{1,2}\d{1,2}_\d{1,2}.parquet"

The COPY command does not validate data type conversions for Parquet files.  see Usage Note.
The GET command will auto-decrypt the parquet file with the key that is used when encrypting., see Usage Note
Still can not get the proper encoded type in column after adjusting the session parameter ENABLE_UNLOAD_PHYSICAL_TYPE_OPTIMIZATION , see Note(May encounter invalid parquet type when reading parquet file using parquetjs or derivative package like parquets)

Result
Use parquet-cli to view the downloaded parquet file

Codecov Report
Patch coverage: 76.08% and project coverage change: +0.06 :tada:

Comparison is base (d80a255) 92.97% compared to head (588711c) 93.04%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #163      +/-   ##
===========================================
+ Coverage    92.97%   93.04%   +0.06%
===========================================
  Files          289      277      -12
  Lines         4398     4125     -273
  Branches       582      564      -18
===========================================
- Hits          4089     3838     -251
+ Misses         200      194       -6
+ Partials       109       93      -16

Flag
Coverage Δ

build
95.01% <ø> (ø)

cli
?

core
93.95% <0.00%> (-0.05%)
:arrow_down:

extension-dbt
97.43% <ø> (ø)

extension-debug-tools
98.11% <ø> (ø)

extension-driver-bq
85.21% <ø> (ø)

extension-driver-duckdb
97.53% <ø> (-2.47%)
:arrow_down:

extension-driver-pg
96.11% <ø> (ø)

extension-driver-snowflake
89.18% <77.77%> (-5.41%)
:arrow_down:

integration-testing
96.15% <ø> (ø)

serve
90.04% <ø> (ø)

test-utility
∅ <ø> (∅)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

packages/core/src/models/extensions/dataSource.ts
87.50% <0.00%> (-5.84%)
:arrow_down:

...on-driver-snowflake/src/lib/snowflakeDataSource.ts
84.81% <77.77%> (-5.67%)
:arrow_down:

... and 13 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Nothing happened after finishing the script

I followed all the steps in https://manual.grid.tf/documentation/developers/grid_deployment/grid_deployment_full_vm.html#access-the-grid-services to deploy my own stack, created a domain and VM, installed the prerequisites, and filled in the environment file. Then I ran the script, and after finishing downloading and installing, it just did nothing.
This is the script logs.
logs.txt

What should I do now?

root@vmv1nju:~/grid_deployment/docker-compose/devnet# docker compose --env-file .secrets.env --env-file .env config
WARN[0000] /root/grid_deployment/docker-compose/devnet/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
name: devnet
services:
  caddy:
    container_name: caddy
    depends_on:
      grid_dashboard:
        condition: service_started
        required: true
    environment:
      DOMAIN: domain.dev.harby.gridtesting.xyz
    image: caddy:2.8.4
    networks:
      tfgrid_bknd: null
    ports:
      - mode: ingress
        target: 80
        published: "80"
        protocol: tcp
      - mode: ingress
        target: 443
        published: "443"
        protocol: tcp
    restart: unless-stopped
    volumes:
      - type: bind
        source: /root/grid_deployment/docker-compose/devnet/Caddyfile
        target: /etc/caddy/Caddyfile
        bind:
          create_host_path: true
      - type: bind
        source: /srv/caddy/data
        target: /data
        bind:
          create_host_path: true
      - type: bind
        source: /srv/caddy/config
        target: /config
        bind:
          create_host_path: true
      - type: bind
        source: /srv/caddy/log
        target: /var/log/caddy
        bind:
          create_host_path: true
  grid_activation_service:
    container_name: grid_activation_service
    depends_on:
      grid_relay:
        condition: service_started
        required: true
    environment:
      ACTIVATION_AMOUNT: "1000000"
      KYC_PUBLIC_KEY: somekey
      MNEMONIC: search vague feature catch correct drama involve hello swallow lend orchard resemble
      URL: ws://tfchain-public-node:9944
    image: ghcr.io/threefoldtech/tfchain_activation_service:2.7.0-rc4
    networks:
      tfgrid_bknd: null
    restart: unless-stopped
  grid_dashboard:
    container_name: grid_dashboard
    depends_on:
      grid_proxy:
        condition: service_started
        required: true
    environment:
      ACTIVATION_SERVICE_URL: https://activation.domain.dev.harby.gridtesting.xyz/activation/activate
      BRIDGE_TFT_ADDRESS: GDHJP6TF3UXYXTNEZ2P36J5FH7W4BJJQ4AYYAXC66I2Q2AH5B6O6BCFG
      GRAPHQL_URL: https://graphql.domain.dev.harby.gridtesting.xyz/graphql
      GRIDPROXY_URL: https://gridproxy.domain.dev.harby.gridtesting.xyz
      MANUAL_URL: https://manual.grid.tf/
      MODE: dev
      NETWORK: custom
      PLAYGROUND_URL: https://play.domain.dev.harby.gridtesting.xyz
      RELAY_DOMAIN: wss://relay.domain.dev.harby.gridtesting.xyz
      STATS_URL: https://stats.domain.dev.harby.gridtesting.xyz
      STELLAR_NETWORK: test
      SUBSTRATE_URL: wss://tfchain.domain.dev.harby.gridtesting.xyz
      VERSION: 2.5.2
    image: ghcr.io/threefoldtech/playground:2.5.2
    networks:
      tfgrid_bknd: null
    restart: unless-stopped
  grid_proxy:
    container_name: grid_proxy
    depends_on:
      grid_activation_service:
        condition: service_started
        required: true
    environment:
      MNEMONICS: search vague feature catch correct drama involve hello swallow lend orchard resemble
      POSTGRES_DB: tfgrid-graphql
      POSTGRES_HOST: processor_db
      POSTGRES_PASSWORD: postgres
      POSTGRES_PORT: "5432"
      POSTGRES_USER: postgres
      RELAYURL: wss://relay.domain.dev.harby.gridtesting.xyz
      SERVER_PORT: :443
      TFCHAINURL: wss://tfchain.domain.dev.harby.gridtesting.xyz
    image: ghcr.io/threefoldtech/tfgridproxy:0.15.15-dev
    networks:
      tfgrid_bknd: null
    restart: unless-stopped
  grid_relay:
    command:
      - --domain
      - relay.domain.dev.harby.gridtesting.xyz
      - -r
      - redis://redis-rmb:6379
      - -s
      - ws://tfchain-public-node:9944
      - -u
      - "1000"
      - -w
      - "500"
      - -l
      - <IP_ADDRESS>:80
      - --debug
    container_name: grid_relay
    depends_on:
      redis-rmb:
        condition: service_started
        required: true
    environment:
      RMB_DOMAIN: relay.domain.dev.harby.gridtesting.xyz
      SUBSTRATE_URL: ws://tfchain-public-node:9944
      USER_PER_WORKER: "1000"
      WORKERS: "500"
    image: ghcr.io/threefoldtech/rmb-relay:v1.3.1
    networks:
      tfgrid_bknd: null
    restart: unless-stopped
  grid_stats:
    container_name: grid_stats
    depends_on:
      grid_proxy:
        condition: service_started
        required: true
    image: ghcr.io/threefoldtech/stats:2.5.2
    networks:
      tfgrid_bknd: null
    restart: unless-stopped
  indexer_db:
    command:
      - start-single-node
      - --insecure
      - --cache=.45
      - --max-sql-memory=.45
    container_name: indexer_db
    depends_on:
      tfchain-public-node:
        condition: service_started
        required: true
    image: cockroachdb/cockroach:v22.2.15
    networks:
      tfgrid_bknd: null
    restart: unless-stopped
    ulimits:
      nofile:
        soft: 82920
        hard: 82920
    volumes:
      - type: bind
        source: /srv/indexer/
        target: /cockroach/cockroach-data
        bind:
          create_host_path: true
  indexer_db-init:
    command:
      - /setup_db.sh
    container_name: indexer_db-init
    depends_on:
      indexer_db:
        condition: service_started
        required: true
    entrypoint:
      - /bin/bash
    image: cockroachdb/cockroach:v22.2.15
    networks:
      tfgrid_bknd: null
    restart: on-failure
    volumes:
      - type: bind
        source: /root/grid_deployment/docker-compose/devnet/setup_db.sh
        target: /setup_db.sh
        bind:
          create_host_path: true
  indexer_explorer:
    container_name: indexer_explorer
    depends_on:
      indexer_db-init:
        condition: service_completed_successfully
        required: true
    environment:
      DB_HOST: indexer_db
      DB_NAME: defaultdb
      DB_PORT: "26257"
      DB_TYPE: cockroach
      DB_USER: root
    image: subsquid/substrate-explorer:firesquid
    networks:
      tfgrid_bknd: null
    restart: unless-stopped
  indexer_gateway:
    command:
      - --database-url
      - postgres://root@indexer_db:26257/defaultdb
      - --scan-max-value
      - "50000"
    container_name: indexer_gateway
    depends_on:
      indexer_db-init:
        condition: service_completed_successfully
        required: true
    environment:
      DATABASE_MAX_CONNECTIONS: "5"
      RUST_LOG: actix_web=info,actix_server=info
    image: subsquid/substrate-gateway:2.7.0
    networks:
      tfgrid_bknd: null
    restart: unless-stopped
  indexer_ingest:
    command:
      - -e
      - ws://tfchain-public-node:9944
      - -c
      - "20"
      - --out
      - postgres://root@indexer_db:26257/defaultdb
      - --types-bundle
      - /configs/typesBundle.json
    container_name: indexer_ingest
    depends_on:
      indexer_db-init:
        condition: service_completed_successfully
        required: true
    image: subsquid/substrate-ingest:1
    networks:
      tfgrid_bknd: null
    restart: unless-stopped
    volumes:
      - type: bind
        source: /root/grid_deployment/docker-compose/devnet/typesBundle.json
        target: /configs/typesBundle.json
        bind:
          create_host_path: true
  processor:
    command:
      - yarn
      - process
    container_name: processor
    depends_on:
      processor_db:
        condition: service_started
        required: true
    environment:
      ACTIV_SERV_IMG: 2.7.0-rc4
      CADDY_IMG: 2.8.4
      DASHBOARD_IMG: 2.5.2
      DB_HOST: processor_db
      DB_NAME: tfgrid-graphql
      DB_PASS: postgres
      DB_PORT: "5432"
      DB_USER: postgres
      INDEXER_DB_IMG: v22.2.15
      INDEXER_ENDPOINT_URL: http://indexer_gateway:8000/graphql
      INDEXER_EXPL_IMG: firesquid
      INDEXER_GW_IMG: 2.7.0
      INDEXER_INGEST_IMG: "1"
      POLL_INTERVAL_MS: "300"
      PROC_DB_IMG: "16"
      PROC_IMG: 2.12.2
      PROC_QUERY_IMG: 2.12.2
      PROXY_IMG: 0.15.15-dev
      RMB_IMG: v1.3.1
      RMB_REDIS_IMG: 7.2.3
      SQD_DEBUG: sqd:processor:*
      START_HEIGHT: "0"
      STATS_IMG: 2.5.2
      TFCHAIN_IMG: 2.9.0
      TYPEORM_LOGGING: error
      WS_ENDPOINT: ws://tfchain-public-node:9944
      WS_URL: ws://tfchain-public-node:9944
    image: ghcr.io/threefoldtech/tfchain_graphql_processor:2.12.2
    networks:
      tfgrid_bknd: null
    ports:
      - mode: ingress
        target: 44233
        published: "44233"
        protocol: tcp
    restart: unless-stopped
  processor_db:
    container_name: processor_db
    depends_on:
      indexer_explorer:
        condition: service_started
        required: true
    environment:
      POSTGRES_DB: tfgrid-graphql
      POSTGRES_PASSWORD: postgres
      POSTGRES_USER: postgres
    image: postgres:16
    networks:
      tfgrid_bknd: null
    restart: unless-stopped
    volumes:
      - type: bind
        source: /srv/processor/
        target: /var/lib/postgresql/data
        bind:
          create_host_path: true
  processor_query_node:
    container_name: processor_query_node
    depends_on:
      processor:
        condition: service_started
        required: true
    environment:
      ACTIV_SERV_IMG: 2.7.0-rc4
      CADDY_IMG: 2.8.4
      DASHBOARD_IMG: 2.5.2
      DB_HOST: processor_db
      DB_NAME: tfgrid-graphql
      DB_PASS: postgres
      DB_PORT: "5432"
      DB_USER: postgres
      INDEXER_DB_IMG: v22.2.15
      INDEXER_ENDPOINT_URL: http://indexer_gateway:8000/graphql
      INDEXER_EXPL_IMG: firesquid
      INDEXER_GW_IMG: 2.7.0
      INDEXER_INGEST_IMG: "1"
      PROC_DB_IMG: "16"
      PROC_IMG: 2.12.2
      PROC_QUERY_IMG: 2.12.2
      PROXY_IMG: 0.15.15-dev
      RMB_IMG: v1.3.1
      RMB_REDIS_IMG: 7.2.3
      START_HEIGHT: "0"
      STATS_IMG: 2.5.2
      TFCHAIN_IMG: 2.9.0
      TYPEORM_LOGGING: error
      WS_ENDPOINT: ws://tfchain-public-node:9944
      WS_URL: ws://tfchain-public-node:9944
    image: ghcr.io/threefoldtech/tfchain_graphql_query-node:2.12.2
    networks:
      tfgrid_bknd: null
    restart: unless-stopped
  redis-rmb:
    container_name: redis-rmb
    depends_on:
      processor_query_node:
        condition: service_started
        required: true
    image: redis:7.2.3
    networks:
      tfgrid_bknd: null
    restart: unless-stopped
  tfchain-public-node:
    command:
      - --node-key
      -<PHONE_NUMBER>9286e0ad9cd523a11de64e041c2949ae223ceaf80426331901bf49
      - --base-path
      - /storage
      - --chain
      - /etc/chainspecs/dev/chainSpecRaw.json
      - --port
      - "30333"
      - --bootnodes
      - /ip4/<IP_ADDRESS>/tcp/30333/ws/p2p/12D3KooWRdfuKqX8hULMZz521gdqZB2TXJjfrJE5FV71WiuAUrpk
      - --rpc-cors
      - all
      - --prometheus-external
      - --rpc-max-connections=148576
      - --pruning
      - archive
      - --telemetry-url
      - wss://shard1.telemetry.tfchain.grid.tf/submit 1
      - --rpc-methods=Safe
      - --rpc-external
    container_name: tfchain-public-node
    image: ghcr.io/threefoldtech/tfchain:2.9.0
    networks:
      tfgrid_bknd: null
    ports:
      - mode: ingress
        target: 30333
        published: "30333"
        protocol: tcp
    restart: unless-stopped
    volumes:
      - type: bind
        source: /srv/tfchain/
        target: /storage
        bind:
          create_host_path: true
networks:
  tfgrid_bknd:
    name: tfgrid_bknd
    ipam:
      driver: default

And I also tried the manual deploy command and got this
root@vmv1nju:~/grid_deployment/docker-compose/devnet# docker compose --env-file .secrets.env --env-file .env up -d
WARN[0000] /root/grid_deployment/docker-compose/devnet/docker-compose.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion
[+] Running 77/16
 ⠏ tfchain-public-node [⣿⣿⣿⣿⣿] 59.69MB / 61.1MB  Pulling                                                                                22.0s
 ⠏ grid_activation_service [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 364.7MB / 371.7MB Pulling                                                                                22.0s
 ⠏ indexer_explorer [⠀] Pulling                                                                                22.0s
 ✔ grid_proxy Pulled                                                                                10.1s
 ⠏ grid_dashboard [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 13.91MB / 15.73MB Pulling                                                                                22.0s
 ⠏ indexer_db Pulling                                                                                22.0s
 ✔ grid_relay Pulled                                                                                3.3s
 ⠏ processor Pulling                                                                                22.0s
 ⠏ caddy [⣿⣿⣿⣿] 18.63MB / 18.63MB Pulling                                                                                22.0s
 ⠏ indexer_gateway [⠀⠀⠀] Pulling                                                                                22.0s
 ⠏ indexer_db-init [⣿⣿⣿⣄⣿⣿] 83.43MB / 140MB   Pulling                                                                                22.0s
 ⠏ processor_query_node [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿]  91.3MB / 92.91MB Pulling                                                                                22.0s
 ⠏ redis-rmb [⣶⣿⠀⠀⠀⠀⠀] Pulling                                                                                22.0s
 ⠏ indexer_ingest [⠀⠀⠀⠀⠀⠀] Pulling                                                                                22.0s
 ⠏ processor_db [⣿⣿⣶⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 143.9MB / 153.4MB Pulling                                                                                22.0s
 ⠏ grid_stats [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿] 16.59MB / 21.46MB Pulling                                                                                22.0s
failed to register layer: lsetxattr security.capability /usr/bin/caddy: operation not supported

Issue related to https://github.com/threefoldtech/zos/issues/2420 not to the installation script itself.
instead of using ubuntu 24 try using ubuntu 22.

@A-Harby There is another work around if you installed docker-io, instead of installing docker-ce .
Then rerun the installation script again it will work

@A-Harby it's not safe to share your wallets private keys on a public repo even if it was for a testing env.

@A-Harby There is another work around if you installed docker-io, instead of installing docker-ce .

Then rerun the installation script again it will work

Okay will try with docker-io.

First, I tried the same steps and script with Ubuntu 22 and still got the same error.
Then tried the docker io but also couldn't run it.

Is there something wrong I did?

Is there something wrong I did?

No, not regarding this error. It is related to running docker on ubuntu on grid vm's. None grid vm's don't have this issue. It's not related to running the grid backend directly.
See: https://github.com/threefoldtech/zos/issues/2420#issuecomment-2355154280

After the help of @PeterNashaat, I was able to deploy the stack successfully.

But unfortunately on IPV6 not on IPV4, so I wasn't able to do any further testing (IPV6 is blocked here) and should be able to continue once https://github.com/threefoldtech/tf_operations/issues/2760 is done.
But found 2 issues:

[ ] The script is not working correctly; it downloads and installs everything, then gets stuck.

[ ] Manually installing isn't clear enough, and I still get another error.

[ ] https://github.com/threefoldtech/grid_deployment/issues/74

[ ] https://github.com/threefoldtech/grid_deployment/issues/75

@A-Harby for the second issue "Manually installing" what are the steps you took so i can reproduce this issue ?.

The first issue is not stuck issue, it's this command tar -I pigz -xf tfchain-mainnet-latest.tar.gz -C /srv/tfchain/chains/tfchain_mainnet/db/, which is decompressing a 222G tfchain-mainnet snapshot which will take some time to finish.

The second issue here as you were trying to start the env manually you didn't/forgot to create the needed config files which is Caddyfile for the caddy contianer, so after doing command cp Caddyfile-example Caddyfile, containers starts with no errors.

After the help of @PeterNashaat, I was able to deploy the stack successfully.
But unfortunately on IPV6 not on IPV4, so I wasn't able to do any further testing (IPV6 is blocked here) and should be able to continue once threefoldtech/tf_operations#2760 is done.
But found 2 issues:

[ ]  The script is not working correctly; it downloads and installs everything, then gets stuck.

[ ]  Manually installing isn't clear enough, and I still get another error.

Tried to reinstall tfchain-public node with a new snapshot download and found out that the disk size in not the same as the required space needed for installation

VM disk has to be 1000GB, and vm is installed with 436GB disk only which is not enough.

@A-Harby Please recreate the vm with proper specs and run the script again and wait for it to finish.

Ok, done https://github.com/threefoldtech/tf_operations/issues/2767 Bert added 2 500 GB disks, but I had to find a way to merge the 3 physical disks into one big disk, 1.5 TB, and I did it using LVM.

Found the issue you are running the docker containers from dir /srv/.. , and all snapshots are downloaded and extracted in dir /mnt/merged_disk/srv/

The disk as well is full.

setup will be redeployed after instructions


WIP: Make mini gallery appear under each function documentation on website

As described in #113

Codecov Report

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

@@           Coverage Diff           @@
##           master     #114   +/-   ##
=======================================
  Coverage   98.87%   98.87%
=======================================
  Files          27       27
  Lines         446      446
=======================================
  Hits          441      441
  Misses          5        5

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 164b908...a09f46f. Read the comment docs.

Still doesn't work :(

Your templates are in  doc/_templates/class.rst, which means that they will not be automatically detected by autosummary. You either need to pass :template: every time you want to autodoc a class (pain) or move these to doc/_templates/autosummary/class.rst / function.rst as we do in MNE-Python (automagical, easier)

Woohoo it works! Thanks @larsoner and @agramfort


Routes

[x] Use React Router.
[x] Use styles in a React app.

thank you so much, this kind of little comment inspires me.❤


Todo Create button to copy personal url

Make a button to copy the personal url do transfer area.

This feat was completed in commit feat(url) add btn copy to Clipboard but need improvement a


Does this support projects?

Hello!
This looks excellent and I would like to use it, however I don't workspaces for most of my projects. Will this work for projects too?

@ryan-blunden In its current state, SwiftCPR won't work for project files. However, this shouldn't be too hard to add 😄 I'll try to get to it this week / early next week!

Let me know if I can help with testing or documentation.
On Tuesday, 24 May 2016, Jasdev Singh<EMAIL_ADDRESS>wrote:

@ryan-blunden https://github.com/ryan-blunden In its current state,
SwiftCPR won't work for project files. However, this shouldn't be too hard
to add 😄 I'll try to get to it this week / early next week!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/tumblr/SwiftCompilationPerformanceReporter/issues/1#issuecomment-221015306

--
Cheers,
Ryan
http://www.linkedin.com/in/ryanblunden
http://ryanblunden.com

@ryan-blunden Finally got around to this! Some of the build steps had to change with the latest SDKs, but I updated the README accordingly. Let me know if you run into any issues and I'll re-open this 😄

Thanks @Jasdev! I'll give this a shot for a project I'm currently working on.


PDF Printing changes

Hi @an-pavlovych
Here are my changes. The main change I've done here is to split the big print.less between the different component, in order to separate the concerns: the pdf-mode display of a component should be managed directly by the component concerned.
I've also activated the impac logo in the dev workspace, removed the bootstrap's print.less, and added a few things here and there.
Don't hesitate to get back to me if any question


feat: run tests in GitHub Actions

What changed? Why?

Setup GitHub Actions to run make build, make tests, and make integration
Use localstack 2.3.2 to run make integration
Setup cache for go build
Setup dependabot for GitHub Actions

How did you test the change?

https://github.com/bestmike007/chainstorage/actions/runs/6479456128

Hey @jiezhang , since this is merged, can you add test and integration to the branch protection rules?


Move CBMC proofs to FreeRTOS+ directory

PR to move +TCP CBMC proofs to correct directory (i.e. FreeRTOS-Plus).
Description
This PR moves the +TCP proof which exist in the FreeRTOS directory to FreeRTOS-Plus/Test directory.
The other supporting files are duplicated with this PR. This will remain so till a common place for the CBMC-setup files is decided.
Added changes to Makefiles to reflect the change in the directory structure.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks

/bot run checks

/bot run checks

/bot run checks

/bot run checks

/bot run checks


improve token handling. related to #317, #318, and #319.

Codecov Report
Attention: 17 lines in your changes are missing coverage. Please review.

Comparison is base (a107d84) 39.45% compared to head (b42414c) 39.62%.

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

Files
Patch %
Lines

R/authenticate_sb.R
33.33%
16 Missing :warning:

R/current_session.R
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #320      +/-   ##
==========================================
+ Coverage   39.45%   39.62%   +0.17%
==========================================
  Files          23       23
  Lines         839      853      +14
==========================================
+ Hits          331      338       +7
- Misses        508      515       +7

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Agent movement in Z is not considered in reward function

Because the reward function doesn't consider movement in Z, agents can stumble sideways as they walk forward. Would it perhaps be more appropriate to consider the velocity in (x,z) == (3,0)? Or use some kind of other penalty for wandering off in Z axis.
I realize this is a comment not a bug, but wanted to highlight this issue.

That's what we intended for the first round as defined here http://osim-rl.stanford.edu/docs/nips2018/evaluation/ but indeed it brings some confusion, we will reconsider it (and maybe include in the next release since it's still early enough for such change). Thanks for bringing it up.


webgl instancing / instanced rendering

( core and renderer )
add support for webgl instancing / instanced rendering

2x VODescriptor's for instances and base

done


pcm-memory:mainloop: Always flush cout

Flushing cout in cvs mode is also useful when the output is a pipeline
using the values to display in real time. As such, always flush the cout
buffers at the start of the main loop.
Signed-off-by: Warner Losh<EMAIL_ADDRESS>

thanks for the patch, this is useful. But to reduce the overhead for non-interactive mode when sampling with a higher frequency the flushing should be avoided in csv mode. The flushing should be optional like in pcm-iio: https://github.com/opcm/pcm/blob/58039287e0ee63edcaa60bdbf837d536e4e417da/src/pcm-raw.cpp#L74 Could you please implement it similarly?

please make the flushing optional

has been implemented in the latest release


NIFI-9642 Update Admin Guide and User Guide with correct nifi.propert…

…ies default values
Initial issues were found with nifi.flowfile.repository.checkpoint.interval and nifi.provenance.repository.rollover.time properties, but noticed others to either fix or add default values for. Also removed duplicate entry for nifi.web.max.access.token.requests.per.second.

Merging, thanks @andrewmlim


[CMS-532] Terminus conversion command to import a site to Pantheon

Tested with your fixture archive dump file, got working site, but missing files and styles:
https://dev-umami-import.pantheonsite.io/
I presume you just removed assets from the archive dump to save space.

Tested with your fixture archive dump file, got working site, but missing files and styles:
https://dev-umami-import.pantheonsite.io/
I presume you just removed assets from the archive dump to save space.

Yes, you are correct


Support for .php files

Hi, php icon support could be nice.
I don't like it, but 🥹

Let's see if this one is fancy enough 😄


Additional entry in addition to active, fallback and recovery

Provide an option to enki with a cmdline (or a list) as input.
enki would generate then an extra entry/EFI file into the installer and the kairos system should have the entry installed in the system in addition to active, fallback and recovery .
Notes:
For Kairos reset flow, I need to add a single boot menu entry, with an additional cmdline "kairos.reset".
Adding it as extend cmdline loses the option to stay in recovery image, because it will always reset and reboot to active.
And, if i add it as generic cmdline that will create 6 EFIs into installed system 3 with default cmdline and 3 with this kairos.reset cmdline.
What we need is an option to add a cmdline for  very specific usecase like reset, and have just one EFI instlled into the system alongwith active, fallback and recovery, This  EFI will only be for this specific use case and we dont need fallback.recovery for this.

We should be able to provide this directly via conf file like we do with active/passive/recorey currently, no need for another entry:
Copy an extra conf for autoreset: https://github.com/kairos-io/kairos-agent/pull/267
Return autoreset state for uki: https://github.com/kairos-io/kairos-sdk/pull/74
Trigger autoreset service on autoreset state: https://github.com/kairos-io/packages/pull/762
Set proper sentinel to autoreset: https://github.com/kairos-io/immucore/pull/259

reopening as we need still to tackle the changes in enki, however the autoreset entry is added

@Itxaka are you already working on the enki changes? I've just synced with Vipin and this is low prio atm

Nope, haven't touched this other than adding the autoreset @mudler

What does loses the option to stay in recovery image, because it will always reset and reboot to active mean?
We currently have 2 flags:

extend-cmdline  -> adds the provides parameters to all the cmdlines (active, passive, recovery)
extra-cmdline -> creates an additional entry for each one of active, passive, recovery with the provided parameters

If I understand correctly, we want an option that will only add the parameters to one specific entry? Or do we want an option that will create an additional entry (only one) with the provided parameters. If the latter is true, the efi file would have to be defined as well for the additional entry.

All merged now. Docs at the bottom of this page: https://kairos.io/docs/installation/trustedboot/ (will appear as soon as the docs site is built)


feat: Add core-common-config-bootstrapper service to compose files

closes #320
Note this PR is dependent on https://github.com/edgexfoundry/edgex-go/pull/4300 so that this works properly in secure mode.
Signed-off-by: Leonard Goodell<EMAIL_ADDRESS>

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-compose/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)
TBD

Testing Instructions
Run the following compose builder commands from this branch

make pull

Non Secure Mode

make run no-secty
Verify core-common-config-bootstrapper service logs show the following.

level=INFO ts=2023-01-23T15:12:28.3485979Z app=core-common-config-bootstrapper source=main.go:52 msg="Core Common Config is starting"
level=INFO ts=2023-01-23T15:12:28.3486855Z app=core-common-config-bootstrapper source=main.go:66 msg="Secret Provider created"
level=INFO ts=2023-01-23T15:12:28.3486979Z app=core-common-config-bootstrapper source=main.go:74 msg="Got Config Provider Access Token"
level=INFO ts=2023-01-23T15:12:28.348706Z app=core-common-config-bootstrapper source=main.go:75 msg="Core Common Config Ready for stage two"
level=INFO ts=2023-01-23T15:12:28.348714Z app=core-common-config-bootstrapper source=main.go:76 msg="Core Common Config exiting"

Verify the core-common-config-bootstrapper service container is still running.
Run make clean to stop all the services.

Secure Mode

make run
Verify core-common-config-bootstrapper service logs show the following.

Script for waiting on security bootstrapping ready-to-run
Mon Jan 23 15:54:53 UTC 2023 Executing waitFor with ./entrypoint.sh waiting on tcp://edgex-security-bootstrapper:54329
level=INFO ts=2023-01-23T15:54:53.6034935Z app=security-bootstrapper source=config.go:396 msg="Loaded service configuration from /edgex-init/res/configuration.toml"
level=INFO ts=2023-01-23T15:54:53.6038998Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.SecretStoreSetup.Tokens.ReadyPort' by environment variable: STAGEGATE_SECRETSTORESETUP_TOKENS_READYPORT=54322"
level=INFO ts=2023-01-23T15:54:53.6039694Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.Registry.Port' by environment variable: STAGEGATE_REGISTRY_PORT=8500"
level=INFO ts=2023-01-23T15:54:53.6039807Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.BootStrapper.Host' by environment variable: STAGEGATE_BOOTSTRAPPER_HOST=edgex-security-bootstrapper"
level=INFO ts=2023-01-23T15:54:53.6039873Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.KongDB.ReadyPort' by environment variable: STAGEGATE_KONGDB_READYPORT=54325"
level=INFO ts=2023-01-23T15:54:53.6039931Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.Registry.ReadyPort' by environment variable: STAGEGATE_REGISTRY_READYPORT=54324"
level=INFO ts=2023-01-23T15:54:53.6039994Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.BootStrapper.StartPort' by environment variable: STAGEGATE_BOOTSTRAPPER_STARTPORT=54321"
level=INFO ts=2023-01-23T15:54:53.6040068Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.SecretStoreSetup.Host' by environment variable: STAGEGATE_SECRETSTORESETUP_HOST=edgex-security-secretstore-setup"
level=INFO ts=2023-01-23T15:54:53.6040183Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.Ready.ToRunPort' by environment variable: STAGEGATE_READY_TORUNPORT=54329"
level=INFO ts=2023-01-23T15:54:53.6040286Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.Registry.Host' by environment variable: STAGEGATE_REGISTRY_HOST=edgex-core-consul"
level=INFO ts=2023-01-23T15:54:53.6040619Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.Database.ReadyPort' by environment variable: STAGEGATE_DATABASE_READYPORT=6379"
level=INFO ts=2023-01-23T15:54:53.6040764Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.KongDB.Port' by environment variable: STAGEGATE_KONGDB_PORT=5432"
level=INFO ts=2023-01-23T15:54:53.6041116Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.Database.Port' by environment variable: STAGEGATE_DATABASE_PORT=6379"
level=INFO ts=2023-01-23T15:54:53.6041219Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.KongDB.Host' by environment variable: STAGEGATE_KONGDB_HOST=edgex-kong-db"
level=INFO ts=2023-01-23T15:54:53.6041286Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.Database.Host' by environment variable: STAGEGATE_DATABASE_HOST=edgex-redis"
level=INFO ts=2023-01-23T15:54:53.6041341Z app=security-bootstrapper source=variables.go:377 msg="Variables override of 'StageGate.WaitFor.Timeout' by environment variable: STAGEGATE_WAITFOR_TIMEOUT=60s"
level=INFO ts=2023-01-23T15:54:53.6041877Z app=security-bootstrapper source=config.go:551 msg="Using local configuration from file (15 envVars overrides applied)"
level=INFO ts=2023-01-23T15:54:53.6042523Z app=security-bootstrapper source=command.go:119 msg="Security bootstrapper running waitFor"
level=INFO ts=2023-01-23T15:54:53.6043577Z app=security-bootstrapper source=command.go:144 msg="Waiting for: [tcp://edgex-security-bootstrapper:54329] with timeout: [1m0s]"
level=INFO ts=2023-01-23T15:54:53.6053865Z app=security-bootstrapper source=command.go:209 msg="Problem with dial: dial tcp <IP_ADDRESS>:54329: connect: connection refused. Sleeping 1s"
level=INFO ts=2023-01-23T15:54:54.606196Z app=security-bootstrapper source=command.go:209 msg="Problem with dial: dial tcp <IP_ADDRESS>:54329: connect: connection refused. Sleeping 1s"
level=INFO ts=2023-01-23T15:54:55.6080185Z app=security-bootstrapper source=command.go:209 msg="Problem with dial: dial tcp <IP_ADDRESS>:54329: connect: connection refused. Sleeping 1s"
level=INFO ts=2023-01-23T15:54:56.6091847Z app=security-bootstrapper source=command.go:209 msg="Problem with dial: dial tcp <IP_ADDRESS>:54329: connect: connection refused. Sleeping 1s"
level=INFO ts=2023-01-23T15:54:57.610026Z app=security-bootstrapper source=command.go:209 msg="Problem with dial: dial tcp <IP_ADDRESS>:54329: connect: connection refused. Sleeping 1s"
level=INFO ts=2023-01-23T15:54:58.6117218Z app=security-bootstrapper source=command.go:209 msg="Problem with dial: dial tcp <IP_ADDRESS>:54329: connect: connection refused. Sleeping 1s"
level=INFO ts=2023-01-23T15:54:59.6125696Z app=security-bootstrapper source=command.go:209 msg="Problem with dial: dial tcp <IP_ADDRESS>:54329: connect: connection refused. Sleeping 1s"
level=INFO ts=2023-01-23T15:55:00.613436Z app=security-bootstrapper source=command.go:209 msg="Problem with dial: dial tcp <IP_ADDRESS>:54329: connect: connection refused. Sleeping 1s"
level=INFO ts=2023-01-23T15:55:01.6143914Z app=security-bootstrapper source=command.go:209 msg="Problem with dial: dial tcp <IP_ADDRESS>:54329: connect: connection refused. Sleeping 1s"
level=INFO ts=2023-01-23T15:55:02.6154804Z app=security-bootstrapper source=command.go:214 msg="Connected to tcp://edgex-security-bootstrapper:54329"
Mon Jan 23 15:55:02 UTC 2023 Starting ./entrypoint.sh ...
level=INFO ts=2023-01-23T15:55:02.6307245Z app=core-common-config-bootstrapper source=main.go:52 msg="Core Common Config is starting"
level=INFO ts=2023-01-23T15:55:02.6307995Z app=core-common-config-bootstrapper source=secret.go:65 msg="Creating SecretClient"
level=INFO ts=2023-01-23T15:55:02.6311709Z app=core-common-config-bootstrapper source=variables.go:377 msg="Variables override of 'SecretStore.Host' by environment variable: SECRETSTORE_HOST=edgex-vault"
level=INFO ts=2023-01-23T15:55:02.6312052Z app=core-common-config-bootstrapper source=variables.go:377 msg="Variables override of 'SecretStore.Port' by environment variable: SECRETSTORE_PORT=8200"
level=INFO ts=2023-01-23T15:55:02.6313Z app=core-common-config-bootstrapper source=secret.go:159 msg="SecretStore information created with 2 overrides applied"
level=INFO ts=2023-01-23T15:55:02.6313475Z app=core-common-config-bootstrapper source=secret.go:75 msg="Reading secret store configuration and authentication token"
level=INFO ts=2023-01-23T15:55:02.6313655Z app=core-common-config-bootstrapper source=secret.go:200 msg="load token from file"
level=INFO ts=2023-01-23T15:55:02.6315243Z app=core-common-config-bootstrapper source=secret.go:93 msg="Attempting to create secret client"
level=INFO ts=2023-01-23T15:55:02.6359284Z app=core-common-config-bootstrapper source=secret.go:104 msg="Created SecretClient"
level=INFO ts=2023-01-23T15:55:02.6360208Z app=core-common-config-bootstrapper source=secret.go:109 msg="SecretsFile not set, skipping seeding of service secrets."
level=INFO ts=2023-01-23T15:55:02.6360468Z app=core-common-config-bootstrapper source=main.go:66 msg="Secret Provider created"
level=INFO ts=2023-01-23T15:55:02.6363416Z app=core-common-config-bootstrapper source=secrets.go:276 msg="kick off token renewal with interval: 30m0s"
level=INFO ts=2023-01-23T15:55:02.6502685Z app=core-common-config-bootstrapper source=secrets.go:148 msg="successfully generated Consul token for service core-common-config-bootstrapper"
level=INFO ts=2023-01-23T15:55:02.6503653Z app=core-common-config-bootstrapper source=main.go:74 msg="Got Config Provider Access Token"
level=INFO ts=2023-01-23T15:55:02.6503831Z app=core-common-config-bootstrapper source=main.go:75 msg="Core Common Config Ready for stage two"

Verify the core-common-config-bootstrapper service container is still running.
Run make clean to stop all the services.

recheck

recheck

recheck

@cherrycl , this PR should not impact the TAF tests. I see the daily runs are also failing. Please confirm. THX!

recheck

@cherrycl , this one is failing but has no impact on TAF. Just adding new service that currently no other services are dependent one. Sometimes one test fails and some time two tests fail. Is there a timing issue with those tests?

recheck

recheck


new UI not showing the correct Pods amounts (> 100%)

Internal reference: SURE-5541
Reported in 2.6.9
Issue description:
New UI not showing the correct Pods amounts compared to old UI. Wrong Monitoring may cause wrong hardware resources available
Repro steps:

open UI
-> select a cluster -> Nodes ->  select a node -> check PODS Used
open on same Rancher old UI by using /g in URL
-> select a cluster -> Nodes ->  select a node -> check PODS Used

In this case
new UI: 178 of 110 / 162 %
old UI:     64 of 110 /   58 %
It looks like completed pods were also counted to the number of active pods in the new UI that may explain more than 100% active pods. That may explains why the UI shows a wrong amount of pods like 178 that is much higher than the total amount of pods 110.

I need to check with those who worked on this since the older reported number may have been wrong in the first place.

Somehow this didn't make it to QA. I'll check the Zube workflow here but I'll move this To Test.

retest passed
tested on HA local, 2.7head 8062f1e
retest steps:

stoop up a local
navigate to -> select a cluster -> Nodes -> select a node -> check PODS Used
confirmed the pod's used reporting section only counts running pods and does not display metrics for completed pods/


Use Vue.js (or other framework) for front-end?

Hi!
As Laravel 5.3 are coming, it gives us better support of JavaScript frameworks. Laravel recommends Vue.js
So, maybe is a good time to use it in MyBB 2.0? I'm a very big fan of that solutions, it gives us optimized requests (Servers just loves it), faster and easier solutions than pure jQuery methods and more.

Hi,
The JS is going to be rewritten (and using modern ES6 standards), but we've not yet settled on a  framework. I've looked at Vue and it has some nice features, but is still quite young as a framework which could cause some problems should it stop being actively developed during 2.0's lifetime.

Vue is used by Alibaba [0], Baidu, Tencent and Xiaomi. I wouldn't be surprised if they would jump in if the development should come to a halt.
[0] http://alibaba.github.io/weex/#subscriptionWeex

Thanks @coniurare, that's good to know. At the minute, I'm rewriting some of our core JS classes (Spinner, cookie handling, etc.) to use TypeScript. I'll look at Vue further and see if I can wrap my head around it.

I'd strongly suggest using Vue or Angular they're both extremely strong frameworks with lots of documentation and a good development team behind them.

Vue.js ships with Laravel 5.3+. It's not going anywhere anytime soon.

@QWp6t I'm aware of that, I still need to look into it, as I said 2 comments above :wink:

Did this ever make any progress?

There still hasn’t been any consensus. Currently the focus is on 1.10 to try and bridge the gap between new and old (or current in this case). There have been some discussions about possibly heading down the route of a SPA, but there are a couple of hurdles that would need to be jumped over such as allowing views to be easily edited in the ACP without incurring the penalty of parsing performance at run time.

On 4 Dec 2017, at 16:34, Ian<EMAIL_ADDRESS>wrote:
Did this ever make any progress?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok cool, well I guess I could add an opinion on the topic then?
I would advise against Vue for the frontend, it adds a lot of work for both you guys, the core team and the developers. Yes it's great, however by adding a JS framework such as Vue to MyBB you will cut out quite a lot of devs I reckon. Take Flarum for example, brilliant idea, but then they shoved a whole bunch of JS and made developing incredibly time consuming.
MyBB is a PHP forum software, please keep it that way. jQuery, Ajax etc sure. But please don't add a huge framework like Vue/React/Knockout.


Feature request: Run a selected set of binaries.

The request is to add some way to build and run a selected set of binary targets.
The motivation (which depends on https://github.com/daedaleanai/dbt/issues/86) is that it would be very nice to be able to find and run all tests (assuming their names end "Test"). I can kind of do that by using "dbt build ..." and then parsing the output (assuming no failures), but it would be nice to have an extended target syntax, so I could write something like:
dbt run "**/*Test" cc-toolchain=mytoolchain

or with a regexp that filters targets:
dbt run ... -target-match ".*Test" cc-toolchain=mytoolchain

The extended target syntax should probably apply everywhere it makes sense, which currently means for "dbt build".

I think the regexp filtering is better (since it is well defined) than coming up with our own wildcard syntax. Would you expect the regexp to be applied to the whole target path (e.g. foo/bar/BazTest) or only the name (BazTest)? The problem with the former is that there is that targets can be referenced by their relative path or their absolute path. So if only matching the target name is sufficient, I think that will be easier (both to implement and understand as a user)


[Changelog] Update for Sprint 117

[skip ci]

@miq-bot add_label documentation

@carbonin as time permits, can you review/merge.


Fix Cineon building on Windows

On Windows stdint.h header is present only in Visual Studio 10. Older version of VS don't have it. This patch fix the problem by typedefing used types

LGTM.  I will merge it.

Wait, are you sure this is right?  If MSC_VER is defined but is >= 1600, it will neither include stdint.h, nor will it define the types.

Ok, I corrected the code, everything should be ok now.

LGTM now.