启动报错

⠿ rasa-core Pulled                                                                                4.0s
⠿ dbf6a9befcde Already exists                                                                                0.0s
⠿ 3805270d692e Already exists                                                                                0.0s
⠿ 6214d5facb77 Already exists                                                                                0.0s
⠿ 72e79ac92225 Already exists                                                                                0.0s
⠿ bb0cbea8a793 Already exists                                                                                0.0s
⠿ 9e952b6124bb Already exists                                                                                0.0s
⠿ 4f4fb700ef54 Already exists                                                                                0.0s
⠿ 6a9541aaa5f0 Already exists                                                                                0.0s
[+] Running 5/5
⠿ Network rasagpt_chat-network     Created                                                                                0.1s
⠿ Network rasagpt_default          Created                                                                                0.1s
⠿ Container chat_rasa_credentials  Started                                                                                0.4s
⠿ Container chat_rasa_actions      Started                                                                                3.2s
⠿ Container chat_rasa_core         Started                                                                                3.5s
make[2]: Leaving directory '/home/house365ai/xxm/RasaGPT'
Error response from daemon: Container 801beb0d327cf7f94e0bb013eccae74663bfb872d49575c468ec39250d289c91 is not running
make[1]: *** [Makefile:291: rasa-train] Error 1
make[1]: Leaving directory '/home/house365ai/xxm/RasaGPT'
make: *** [Makefile:57: install] Error 2

Try this:
Edit /app/rasa/actions/Dockerfile and add USER root  before  RUN pip install python-dotenv rasa-sdk requests
Also, edit docker-compose.yml, add user: "root:root" to rasa-core, rasa-actions, and rasa-credentials
Also, in rasa-action changer this lines:
      context: ./app/rasa
      dockerfile: ./actions/Dockerfile

To:
      context: ./app/rasa/actions
      dockerfile: ./Dockerfile

it does not work!!!

so try docker logs 801beb0d327cf7f94e0bb013eccae74663bfb872d49575c468ec39250d289c91  (use the container ID from your current log) to see what is your problem

also, docker system prune can help clear your cache

支持本地模版吗？

Support for local models?

it works ,thx


Add build check which verifies source code contain ASF 2.0 license header

This pull request adds a build check which verifies that all the source code files contain ASF 2.0 license header.
It also adds header to the files which were missing it.
We used to have this check set up a long time ago when we were still using buildbot, but it looks like it got lost when we moved to Travis CI.

Codecov Report

Merging #1316 into trunk will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##            trunk    #1316      +/-   ##
==========================================
- Coverage   86.25%   86.25%   -0.01%
==========================================
  Files         365      367       +2
  Lines       75250    75252       +2
  Branches     6882     6882
==========================================
  Hits        64909    64909
- Misses       7568     7569       +1
- Partials     2773     2774       +1

Impacted Files
Coverage Δ

libcloud/container/drivers/gke.py
75.4% <ø> (ø)
:arrow_up:

libcloud/compute/drivers/onapp.py
94.8% <ø> (ø)
:arrow_up:

libcloud/test/compute/test_gce.py
97.77% <ø> (ø)
:arrow_up:

libcloud/compute/constants.py
100% <ø> (ø)
:arrow_up:

libcloud/test/storage/test_dummy.py
100% <ø> (ø)
:arrow_up:

libcloud/test/conftest.py
40% <ø> (ø)
:arrow_up:

libcloud/compute/drivers/maxihost.py
78.49% <ø> (ø)
:arrow_up:

libcloud/test/loadbalancer/test_ninefold.py
100% <ø> (ø)
:arrow_up:

libcloud/common/vultr.py
69.56% <ø> (ø)
:arrow_up:

libcloud/test/dns/test_nsone.py
94.7% <ø> (ø)
:arrow_up:

... and 19 more

Continue to review full report at Codecov.

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


[eas-cli] rollouts websupport

Why
small nit in developer preview logger to say website support is coming soon for rollouts

/changelog-entry chore logger to say website support is coming soon for rollouts


tests for get_insertions_and_reads

@mwakok I have look into ways to import pytest.fixtures across files but I did not succeed in that , do you know how to do it? it would be  really helpful for refactoring  the tests..


[Bug]: Upload image with no file chosen should not be possible

Contact Details
No response
What happened?
On the Profile page:

Choose no file
Click the upload button

Expected:

Upload button should not be clickable when no file is chosen

What browsers are you seeing the problem on?
No response
Relevant log output
No response

Fixed with #265


[Bug] ldap create user bug fixed

[Bug] ldap create user bug fixed
What changes were proposed in this pull request
Issue Number: close #2051

Brief change log

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): no

cc @MonsterChenzhuo @1996fanrui PTAL, thanks

LGTM


Added Material Design inspired theme

Thank you!

We will need to spend some time on the colours as they are a bit all over the place

What do you want to change?


my commit

hello mathcodes, I  just added my data to the db.json and my avatar link to the readme file like everybody else did. And just as you told me to do.. thanks for your response

Thank you for the opportunity 🙏🏾


Improve UI for Order Box and Issue Reporting Buttons

What is the motivation for adding/enhancing this feature?
The buttons for Order Box and Issue Reporting are displayed within the same segment, leading to confusion among users. This layout makes it challenging for users to distinguish between the two functionalities.
What are the acceptance criteria?
Improve the user interface by separating the buttons for Order Box and Issue Reporting. Providing a clearer visual distinction between these functions will enhance user experience and reduce confusion.

[ ] ...

Can you complete this feature request by yourself?

[ ] YES
[ ] NO

Additional information
Refer this UI: https://www.figma.com/file/wK5FMs4z2zXQR9VfHV9ycE/Dhiraj's-Ionic-6-Material-UI-Kit-(Community)?type=design&node-id=28867%3A152486&mode=design&t=TRefPw85hfMzAOD5-1

closed due to new rejection UI being rolled out


import/export: Support references to missing content

Allow importing/exporting archives which doesn't have all the referenced blobs.
This allows to export/import an image with only some of the platforms available locally while still persisting the full index.

The blobs directory MAY be missing referenced blobs, in which case the missing blobs SHOULD be fulfilled by an external blob store.

https://github.com/opencontainers/image-spec/blob/v1.0/image-layout.md#blobs

/ok-to-test

FYI, the last force push is just reverting an unneeded signature change:
-func getRecords(ctx context.Context, store ContentProvider, desc ocispec.Descriptor, algorithms map[string]struct{}, brOpts *blobRecordOptions) ([]tarRecord, error) {
+func getRecords(ctx context.Context, store content.Provider, desc ocispec.Descriptor, algorithms map[string]struct{}, brOpts *blobRecordOptions) ([]tarRecord, error) {


Fix React 15.5 deprecation warnings

Fix the following deprecation notices :
Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead.

React.createClass is deprecated and will be removed in version 16. Use plain JavaScript classes instead. If you're not yet ready to migrate, create-react-class is available on npm as a drop-in replacement.

Supersedes #52

Cool, merged. Thanks for your contributions!


Add special test suite to probe all precondition combinations

This PR adds the measurement part of the precondition framework.
To measure which preconditions are running and where this PR implements a special test suite.
The test suite is configured to being able to run with all Test.class based tasks.

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

I've triggered a build for you. Click here to see all failures if there's any.

Your PR is queued. See the queue page for details.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

Currently, the following commands are supported:
@bot-gradle test <BuildTrigger1> <BuildTrigger2> ... <BuildTriggerN>

A trigger is a special build for this PR on TeamCity, common triggers are:

SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/PullRequestFeedback/ReadyForNightly/ReadyForRelease
Shortcuts: SC/CA/QFL/QF/PRF/RFN/RFR
Specific builds:

BD: BuildDistributions/BuildDocs so that you can preview the generated docs/distribution.
PT: PerformanceTest, all performance tests for Ready For Nightly stage.
APT: AllPerformanceTest, all performance tests, including slow performance tests.
AST: AllSmokeTestsPullRequestFeedback
AFT: AllFunctionalTestsPullRequestFeedback
ASB: AllSpecificBuildsPullRequestFeedback
ACC: AllConfigCacheTestsPullRequestFeedback
ACT: AllCrossVersionTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle test and merge

queues this PR for testing and merges if all tests pass by:

Creating a merge commit from your PR branch HEAD and the target branch
Running a ReadyForNightly build against the merge commit
When it passes, fast-forward the target branch to this merge commit (i.e. merge the PR)

The merge commit is called a pre-tested commit, which means that it fully tests the integration
of your branch HEAD and latest master, instead of only testing your branch HEAD.
@bot-gradle cherrypick to <branch>

Cherrypicks the current PR to another branch.
A new PR will be created and a build will triggered automatically if there is no conflict.

@bot-gradle cancel

cancel a running pre-tested commit build or remove it from queue

@bot-gradle clean

clear the conversation history

@bot-gradle help

display this message

To run a command, simply submit a comment.  For detailed instructions see here.

Pre-tested commit build failed.

@bot-gradle cancel

I've triggered a build for you. Click here to see all failures if there's any.

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.

Pre-tested commit build failed. Click here to see all build failures.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you. Click here to see all failures if there's any.


remove license test

remove our antiquated automated license audit test that predates our
open sourcing of the gem

Closed in favor of #1214

@tannalynn #1214 retains the check for the license header and only gets rid of the "scary" terms test
@kaylareopelle If we want to revisit the removal of the need for a license header at the top of each file (something I'd like to revisit with all agent teams), we can bring in the open source team at that time. For now, I think #1214 is ready to go.

Thanks to you both for your help!

@fallwith - I think discussing the need for a license header would be timely for an upcoming Agents council, given this week's meeting's focus on the WIP Quality Standards Document (Internal).
That document also raises a concern about removing the "scary" license terms. I've tagged you in a comment on that doc with the reference.
I also have a vague memory of you mentioning there could be another way to automate "scary" license terms checking. Do you remember that too, and/or do you have other ideas?

@kaylareopelle thanks, I've responded on that internal doc in agreement with the recommended approach.
There are 3 license related concerns in play:

New Relic's desire to put a license blurb at the top of every single distributed file, in addition to having a repo wide LICENSE file
[Distribution] Preventing content with an incompatible license from hitting the repository
[Distribution] Preventing content with an incompatible license from hitting the distributed payload at build/package time

For item 1, I think it's a bit silly to do so but we are arguably in good company by doing so because Apache does this. Apache's own internal guidelines for distributing content calls for a commented out blurb to be included with each file. A wild guess is that New Relic borrowed this guideline from Apache when it came time to open source the agents. We'll keep doing this for now and keep automating checks that enforce doing so consistently. #1214 delivers a rewrite of the check. One example of an improvement there is that it no longer slurps in the content of every single Ruby file into memory, only the comments at the top of each.
For item 2, this specific Ruby agent repository doesn't currently contain any relevant third party content. It did in the past when we included an SSL cert. Should we ever start including such content in the repo again in the future, we can revisit the need for an automated check. But we definitely don't need one now and my expectation is that our current PR review process is sufficient for keeping any such content out unless it is properly disclosed.
For item 3, the Ruby agent does not bring in any third party content during the packaging process of creating our 2 Ruby gems. So for us, we're completely non-applicable here. Our dependencies declared by the 2 gemspec files (a combined list that currently only contains "grpc") is the closest we come to distributing content, but given that the consumers of our gems will themselves pull down that content, we're safe here.
My long ago suggestion of using an automated tool was essentially a call to use a pre-existing, open source tool to enforce items 2 and 3. I think doing so would be helpful for New Relic on the whole but for this repo specifically we're okay until we start distributing anything that isn't of our own authorship.

Thanks for explaining this, @fallwith! Now I understand. The idea of a pre-existing, open source tool escaped my imagination. I agree that adding a tool like this could be beneficial for New Relic on the whole.


Merge commits not in newest release?

Disclaimer: I am not sure how the updates of crouton are supposed to work.
I updated crouton to check that #3410 and #3514 had indeed been fixed. However, the "real" installer downloaded by crouton still contains the older versions of croutonclip etc.
If this is as intended, then please close this issue.
Kapil.

@kapilhp,
Show us the output of sudo edit-chroot -all
If you reboot you're sure to get a fresh copy 'crouton'.
Hope this helps,
-DennisL

Output of sudo edit-chroot -all:

name: min
encrypted: yes, unlocked
Entering /mnt/stateful_partition/crouton/chroots/min...
crouton: version 1-20171119224248~master:c73e7a80
release: buster
architecture: amd64
xmethod: xiwi
targets: extension,xiwi,x11
host: version 10032.39.0 (Official Build) beta-channel cyan
kernel: Linux localhost 3.18.0-16283-gde9f7f8596fa #1 SMP PREEMPT Tue Nov 14 22:07:19 PST 2017 x86_64 GNU/Linux
freon: yes

Your suggestion does not work for the following reason.
Running
curl -# -L --connect-timeout 60 --max-time 300 retry 2 https://github.com/dnschneid/crouton/raw/releases/crouton > crouton
gives the "real" installer. At the end of this script is a .tar.bz2 consisting of the scripts to be installed. These are the "old" scripts not the new ones.
My guess is that the contents of "raw.github.com/dnschneid/crouton" have not been updated after the latest commit. Since this should be automatic, I am puzzled.
Alternatively, since I am behind a web proxy, it is possible that it has incorrectly cached the older version of the installed and is giving me that. I will check.
Kapil.

I downloaded the real installer from a few other sites that I have access to and found that the installer is the same. So as far as I can see the update has not propagated to the installer.
Kapil.

Maybe because I somehow pushed a release that didn't include the latest merge :(
Sorry about that.  The most obvious way to tell is by going to the network graph and seeing how the release branch relates to master.  release should always be to the right of master, and if you mouse-over the release commit, the bit after the tilde will be the hash of the related master commit.  If you then mouse-over a commit on master, you can see the hash in low-contrast gray in the top-right corner of the pop-up, truncated one character further than the hash in the release message.


Why are there two initial holding potentials in patch clamp experiment list?

@stripathy, The second one meant to be the holding potential, and the first one the initial step.
Will change the verbose names in the model.


example_setup - no service providers listed after login to IDP

This is based on the code in master on 2/11/2022.
I followed the example_setup instructions to create the docker containers and they both started up.  No problems there.  I created the superuser and then tried to do IdP initiated login.  I was able to login to the IDP with the superuser and saw the list of user attributes but there was no link at the bottom of the page to perform a login to the SP.  I could chase this down further if there was a suggestion on what to look at.
My observation should be straightforward to reproduce just based on following the instructions and trying an IdP-initiated login.
Thank you, this is a great project, along with djangosaml2.

Looked into this a bit further, the service provider table doesn't have any rows in it (so no service provider configuration).  Maybe the example_setup needs to be updated due to the change in the latest release in 2020 which moved the service provider configuration to the DB.

I got the example working with the 0.6.3 idp and 0.7.X sp

Just in case anyone else has problems using the docker example. I upped pysaml2 to 7.1.2. When using the remote fetch url, make sure to use http://sp:8000/saml2/metadata/ and that all configurations mirrors the SP settings. requests_signed: true ... You can find them in sp/settings.py. Else you can always go to http://localhost:8000/saml2/metadata/ and copy the xml and paste it under the remote url. You also have to create a user account with the same name in you SP, otherweise you get access denied, IDP only handles authentication not authorization.

Thank you really helpful, it's working now using containers. I didn't update the pysaml2.

@Vidski Can you explain how to create the user account with same name in SP because I am getting access denied error.

I have created the persistent Ids for the user, but I am still getting Access denied error. The error printed in console is Signature Error: {'message': 'Signature verification failed. Invalid document format.',


[german] de_basics_storage-classes

German reviewer roulette: @stonemaster would you have time to act as a second pair of eyes on this translation?


Time-out unresponsive section of code?

Currently what paren-soup does with a statement is it evaluates it until the statement is finished, even when it might take a while to finish. For example:
(defn fibonacci [n]
  (if (< n 2) n
    (+ (fibonacci (- n 1)) (fibonacci (- n 2)))))

(fibonacci 200)

Obviously that will take a long time to finish, but the whole section that I tested the code on became unresponsive. Is it better to either time the function out after a certain period of time, or to listen for a change to the statement (e.g. a backspace on the 200 to become 20) for re-evaluation?

You are talking about the instaREPL, right? Currently it can only timeout things that use recur underneath, like loop and doseq. I'll have to figure out another way to timeout other long-running functions. I was hoping browsers would eventually throw an exception due to consuming too much stack space, but that doesn't appear to be the case.

Any news on this as of late?

I haven't developed any solution to this yet.


how do i do unix socket or time out connection?

how do i do unix socket or time out connection?

SSDB doesn't support Unix domain socket.
Some client API provide options, see the docs.


add custom authentication type

adds the custom authentication type

Is there a spec for this?
On Wed, Nov 3, 2021, 6:18 PM Spencer Chang @.***> wrote:

adds the custom authentication type
You can view, comment on, or merge this pull request online at:
https://github.com/coda/packs-sdk/pull/1512
Commit Summary

add new custom auth type
https://github.com/coda/packs-sdk/pull/1512/commits/148d24a44a5f428bee5be4e553d5b82da09085a5
add custom auth type
https://github.com/coda/packs-sdk/pull/1512/commits/820744d6f56b29ddeac18fc2e2d42d386c5b39fe
fix types
https://github.com/coda/packs-sdk/pull/1512/commits/193985babb3956a16749e1fcf415e135377757c9
fix more stuff
https://github.com/coda/packs-sdk/pull/1512/commits/fdfe507fceba1b666d6dc8da0775bc806bc13803
build things
https://github.com/coda/packs-sdk/pull/1512/commits/a099b8dc3d59ef4fcbcb77ef5031e519670a9649

File Changes
(29 files https://github.com/coda/packs-sdk/pull/1512/files)

M bundles/thunk_bundle.js
https://github.com/coda/packs-sdk/pull/1512/files#diff-4f31ba12aa8aac95174fe7790d75714590495c2befdedc6e6609fa4418a7cfbe
(1)
M dist/bundle.d.ts
https://github.com/coda/packs-sdk/pull/1512/files#diff-82fba8e81b1f79345d8550b7738888d35106d7b53d3eeb3b1310fde5fce59f59
(42)
M dist/bundle.js
https://github.com/coda/packs-sdk/pull/1512/files#diff-6ecfd94d835672a8b7d66cf9645300ed71ad13333bcc963ee6db8f3982a05f21
(4)
M dist/bundles/thunk_bundle.js
https://github.com/coda/packs-sdk/pull/1512/files#diff-c5a7c9be3263d6ea82cd36e88b442eceaf9604327a8663e88a0be749b8c1465d
(1)
M dist/testing/auth.js
https://github.com/coda/packs-sdk/pull/1512/files#diff-0c4c65eb37ee1ca3401ecb00d4e0c08d3179dcbb850446306a030c10cb7cb814
(16)
M dist/testing/auth_types.d.ts
https://github.com/coda/packs-sdk/pull/1512/files#diff-770945173e0d64e7a7ef5e7c9c0b3e0ffd76a2836e95cd1eb437d8cf5689c098
(7)
M dist/testing/fetcher.js
https://github.com/coda/packs-sdk/pull/1512/files#diff-94964ccf1f512105fc92046604fa0a01b85f592c2c35abe7f8ddc5924d261122
(19)
M dist/testing/upload_validation.js
https://github.com/coda/packs-sdk/pull/1512/files#diff-90d6a64a59447bdc3806b6fa7887eeb4d15fe71e84caf0d267cfa3fa8443e46d
(16)
M dist/types.d.ts
https://github.com/coda/packs-sdk/pull/1512/files#diff-2ced07f8b2c350e949e1e20cf8b67a74ca3f22cf0c66c4b10d6f2e1d0d256b97
(42)
M dist/types.js
https://github.com/coda/packs-sdk/pull/1512/files#diff-ee9e82298a65c3e2016f277255f30547723eb5757f5f7cc4aa86ad0505086d3d
(5)
M docs/reference/sdk/classes/PackDefinitionBuilder.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-62038cbd619ee2dbdd690c66cb8cac8293892a7e3905b3fdcfd9f0af0c43a517
(2)
M docs/reference/sdk/enums/AuthenticationType.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-a1fcc3717770d87f49a79f65d167e578342783d3a2bdd9da5472af4a7468b858
(15)
M docs/reference/sdk/enums/DefaultConnectionType.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-a37da275cf9535f86f97cc2beb2ad29aa10fd01117dfbd788213ad7815398350
(6)
M docs/reference/sdk/enums/PostSetupType.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-ba0e69f618e0b3146a6a26dc5c3de56e3e7237992de9d5d315c4ab7c4f0b640c
(2)
M docs/reference/sdk/interfaces/ExternalPackVersionMetadata.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-692b54ebf97e78d0b049047eea3e72ce5e29132bc03c97143e19dbbbd2925eda
(6)
M docs/reference/sdk/interfaces/Format.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-2075f0d1c64d5a59b3b7be0c4fe9a91b884c880aa6f3d4e891731d3adcb5400f
(14)
M docs/reference/sdk/interfaces/OAuth2Authentication.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-edaa81e48d73f4a03cbaa9c54d41b7693f3d0391b1886a41b04446bd033d07b0
(30)
M docs/reference/sdk/interfaces/PackDefinition.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-095f6fc4697181b7ff9d987970c86a7de6289cfcdd447c8316a1f9a925c8a026
(44)
M docs/reference/sdk/interfaces/PackFormatMetadata.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-09292fa911a1366c435eccc21cfa1e40e6de1bc46e187788f7d669c9f678dd4f
(12)
M docs/reference/sdk/interfaces/PackVersionDefinition.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-438a0b09d0a855a897b3c52c15c6020be06986c855b35adaf790e222ac5111e7
(16)
M docs/reference/sdk/interfaces/WebBasicAuthentication.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-ed32bbc9d038e5bb4b7097957f6f2d3c59673bd274b8dc32052e18c0d6248ac8
(18)
M docs/reference/sdk/types/Authentication.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-28152222949f257eed68188f35f0fa3d88c259b1161f9af8d3aa13d149cfa880
(4)
M docs/reference/sdk/types/BasicPackDefinition.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-0a3277685475ffef2eef1cbbdcc8b52f16ab3171b4ad42fbec6679793abf0d5c
(2)
M docs/reference/sdk/types/SystemAuthentication.md
https://github.com/coda/packs-sdk/pull/1512/files#diff-85fb7d3868392b01342c2cc14bddd954c9c45a286113902daaab1c4934f62ca0
(4)
M testing/auth.ts
https://github.com/coda/packs-sdk/pull/1512/files#diff-6104a9427ba025814f79286c37a7c9f3463c9c78106f5a010792bf8f50c37dca
(17)
M testing/auth_types.ts
https://github.com/coda/packs-sdk/pull/1512/files#diff-40f0202daa67ebe0bc2c32fcc0759103ec2ea3d455846bfc7ede2f29ae6f5431
(5)
M testing/fetcher.ts
https://github.com/coda/packs-sdk/pull/1512/files#diff-fcc2afe5000154b9bb9d931f7496b27f1a10188f1a6ebc710dea457c0bf20e74
(25)
M testing/upload_validation.ts
https://github.com/coda/packs-sdk/pull/1512/files#diff-8f115faeb93eef8da8c710afe7051c558275f28ab6015e1a6bd21f2f7a599f51
(22)
M types.ts
https://github.com/coda/packs-sdk/pull/1512/files#diff-8033e9b81c9757b4f6b0dffdbd5f34f7fbc5a59761f876c863768a9da20ea1b7
(43)

Patch Links:

https://github.com/coda/packs-sdk/pull/1512.patch
https://github.com/coda/packs-sdk/pull/1512.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/coda/packs-sdk/pull/1512, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKW5KYMQWNKC2X3Z3K2NF3UKHUPJANCNFSM5HKJ5AFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Can we make sure we sniff the response from the server and remove any copies of the auth material in the body & headers?  That way we protect against reflection attacks to get the auth data.  Would love to see a threat model on this.

Can we make sure we sniff the response from the server and remove any copies of the auth material in the body & headers? That way we protect against reflection attacks to get the auth data. Would love to see a threat model on this.

There isn't actually any new functionality here, we're just taking what was already done for WebBasic and making a separate auth type enum for it so that's clearer.

Can we make sure we sniff the response from the server and remove any copies of the auth material in the body & headers? That way we protect against reflection attacks to get the auth data. Would love to see a threat model on this.

There isn't actually any new functionality here, we're just taking what was already done for WebBasic and making a separate auth type enum for it so that's clearer.

Agreed that functionality already exists, but what's new is we're opening this up to third parties and could therefore be susceptible to an attack.

Can we make sure we sniff the response from the server and remove any copies of the auth material in the body & headers? That way we protect against reflection attacks to get the auth data. Would love to see a threat model on this.

There isn't actually any new functionality here, we're just taking what was already done for WebBasic and making a separate auth type enum for it so that's clearer.

Agreed that functionality already exists, but what's new is we're opening this up to third parties and could therefore be susceptible to an attack.

That makes sense.
We already sanitize every response header except for a small list of well-known headers from a runtime config, for all authentication types. For this template replacement thing, we sanitize the body before we ever log it: https://github.com/coda/coda/blob/main/modules/server/calc-server/private/authentication_helper.ts#L208. When we first added it, we did some threat modeling all together that led us to use the unique invocation token to protect against injection attacks.
The remaining risk would be if services echo back secrets in response bodies. I can't think of a great reason why any service would do this or why services that require this template replacement would be more likely than other services to do this. I suppose they could echo back the request body as part of the response. In which case, if we really want to be cautious, should we just do a find-and-replace of the secrets in the body?

Can we make sure we sniff the response from the server and remove any copies of the auth material in the body & headers? That way we protect against reflection attacks to get the auth data. Would love to see a threat model on this.

There isn't actually any new functionality here, we're just taking what was already done for WebBasic and making a separate auth type enum for it so that's clearer.

Agreed that functionality already exists, but what's new is we're opening this up to third parties and could therefore be susceptible to an attack.

That makes sense.
We already sanitize every response header except for a small list of well-known headers from a runtime config, for all authentication types. For this template replacement thing, we sanitize the body before we ever log it: https://github.com/coda/coda/blob/main/modules/server/calc-server/private/authentication_helper.ts#L208. When we first added it, we did some threat modeling all together that led us to use the unique invocation token to protect against injection attacks.
The remaining risk would be if services echo back secrets in response bodies. I can't think of a great reason why any service would do this or why services that require this template replacement would be more likely than other services to do this. I suppose they could echo back the request body as part of the response. In which case, if we really want to be cautious, should we just do a find-and-replace of the secrets in the body?

Yeah, that sounds perfect (and should be pretty trivial to add I think?).  If this ends up being painful to build or maintain, then may not be worth it in the end.

Works for me. @spencer-codaio for this auth type, want to just do a find-and-replace for each of the secret values on the body before returning/parsing it?

@jonathan-codaio yeah sure i can follow-up on this. Where would that need to happen?

This may be more of a UI problem, but do we give the user any indication of what they're actually authenticating to / where their credentials are going?
Looking at the example image in https://github.com/coda/coda/pull/63879, I see that we prompt the user for their Auth Token  / Auth Secret / Auth Parameter, but we don't tell them how these credentials are being used.

This may be more of a larger UI discussion, but do we give the user any indication of what they're actually authenticating to / where their credentials are going?
Looking at the example image in coda/coda#63879, I see that we prompt the user for their Auth Token / Auth Secret / Auth Parameter, but we don't tell them how these credentials are being used. Wondering if it's possible for a pack author to setup a dummy domain that collects credentials using this auth type.

The user would get this screen in response to installing a specific named pack, and normally it would have the icon of the pack on it (that screenshot just has our default icon). So for example when you install the Shopify pack and it asks you for an API key, it's really clear that you're providing Shopify credentials for use with a Shopify integration.
One thing we plan to do but haven't done is show and emphasize the networkDomains from the pack def, so it's clear what domain your credentials will be used on.

One thing we plan to do but haven't done is show and emphasize the networkDomains from the pack def, so it's clear what domain your credentials will be used on.

Displaying networkDomain is what I had in mind; something similar to how iOS will prompt the user that an app is attempting to load another site to sign in. My understanding is that the pack author controls the icon, so it doesn't seem like something users can rely on.

One thing we plan to do but haven't done is show and emphasize the networkDomains from the pack def, so it's clear what domain your credentials will be used on.

Displaying networkDomain is what I had in mind; something similar to how iOS will prompt the user that an app is attempting to load another site to sign in. My understanding is that the pack author controls the icon, so it doesn't seem like something users can rely on.

Yeah, the networkDomain is our central security feature so we do plan to emphasize it pretty widely. Haven't done it though, but feel free to hold us accountable on this if you think we should be farther along on this.


nixos/smartd: fix description for docbook

Motivation for this change
escape opening tags
follow up from: #91432
Things done

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

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

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

docbook now runs again:
[16:18:45] jon@jon-desktop /home/jon/projects/nixpkgs (fix-smartd-docbook)
$ nix-build nixos/release.nix -A manual.x86_64-linux
/nix/store/gqlpwaj92rm8my1vjavx62n035y962nj-nixos-manual-html

actually, it looked hideous with it completely escaped. Fixed elements

I believe this was the author's original intention, going to merge once successful


ProjectRootRegex should be stripped by default

When using projectrootregex we should strip the matching regex from the filename by default.

Moved into next PHP improvements milestone.


Fix transform_values deprecation in Rails 6

Do not require transform_values if ActiveSupport is version 6 or higher

Fix for #227

CHANGELOG please

@rodrigopinto Is there a reason why you didn't merge? I was just trying to help out.

Thanks @yads!


Better scrollbar and progressbar

I want to make better scrollbarand progress bar that looks good with the website UI
please assign me with hacktoberfest, gssoc24-ext label.
Thankyou!

@srishti023 Thanks for creating the issue in BuddyTrail!!! The issue has been assigned to you.
Before you start working on your PR, please make sure to:

⭐ Star the repository if you haven't already.
Pull the latest changes to avoid any merge conflicts.
Attach before & after screenshots in your PR for clarity.
Include the issue number in your PR description for better tracking.

Contributors will start at Level 1, and their level will increase based on the quality and quantity of their contributions. The more effort and value you bring, the faster you'll progress. Put forth your best effort to unlock new levels and opportunities!
I'm excited to see your contribution as part of GSSOC EXTENDED 2024! 🎉
Don't forget to follow me on GitHub for more updates.
Happy open-source contributing! 🚀

Please assign this issue to me

Hi @PriyaGhosal,
I wanted to let you know that I’ve added the new better scroll bar and progress bar to the website. please let me know if you want any change else accept my pull request!
Thank you
Best Regards!


⚠ Samsung has degraded performance

In bea9079, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2280 ms

Resolved: Samsung performance has improved in 5448b77.


Enable Running an image - Proposal

Acr tasks only allows running a task file from a context and we want to enable storing the task file running without a context.
There are 2 primary scenarios here

Running a task with an image or encoded or stored file.
Creating a Task with an image or encoded task file.

Running a task with an image

Description
Command
Notes

Running an image
az acr run --cmd hello-world

Image with Args
`az acr run --image bash echo "hello-world"
Arguments follows image similar to docker run

Image with timeout
az acr run --timeout 100 --cmd nginx
run properties come before image args`

Creating a Task with an Image or task file without a Source or GIT context

Description
Command
Notes

Create a task without context
az acr task create -f task.yaml --values --import
Used to import values file from local context.

Create a task with an image
az acr task create  --image task  -c .
This can run an image against a and args as a file if needed. The source context is used to only discover the files

I really like the acr run —cmd


Add user survey link to docs

This PR adds a link to the user survey to our documentation (analogous to https://github.com/dask/dask.github.io/pull/12). Currently this PR adds a note to the top of each page, like so:

Is this something we want to add temporarily to bring attention to the survey? Is adding it to every page overkill (e.g. should we just add a link to index.rst)?

Seems like a good idea. My preference would be for just index.rst.
On Sat, Jun 29, 2019 at 8:53 PM James Bourbeau<EMAIL_ADDRESS>wrote:

This PR adds a link to the user survey to our documentation (analogous to
dask/dask.github.io#12 https://github.com/dask/dask.github.io/pull/12).
Currently this PR adds a note to the top of each page, like so:
[image: Screen Shot 2019-06-29 at 8 39 00 PM]
https://user-images.githubusercontent.com/11656932/60391220-e0527c80-9aae-11e9-8e7a-4d03ef312a11.png
Is this something we want to add temporarily to bring attention to the
survey? Is adding it to every page overkill (e.g. should we just add a link
to index.rst)?
You can view, comment on, or merge this pull request online at:
https://github.com/dask/dask/pull/5026
Commit Summary

Adds user survey link to docs [skip ci]

File Changes

M docs/source/conf.py
https://github.com/dask/dask/pull/5026/files#diff-0 (8)

Patch Links:

https://github.com/dask/dask/pull/5026.patch
https://github.com/dask/dask/pull/5026.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/5026?email_source=notifications&email_token=AAKAOIW6IRNMLKEODW26J6DP5AG3BA5CNFSM4H4LR54KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G4PAVXQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKAOISIHIBTBTDKTJ46F3LP5AG3BANCNFSM4H4LR54A
.

Planning to merge later today if no objections

Thanks @jrbourbeau
These are both live:

https://dask.org
https://docs.dask.org/en/latest/


Refactoring base64 logic for JWT

Import base64 logic from https://github.com/Code-Hex/firebase-auth-cloudflare-workers/blob/main/src/base64.ts
Decoding speed will be faster almost 2x
Accept to encode RFC 3548 examples
This PR is created at YAPC::Japan::Kyoto 2023 🔥

I fix them 🙏

@yusukebe I passed all tests in middleware
 PASS  src/middleware/etag/index.test.ts
 PASS  src/middleware/bearer-auth/index.test.ts
 PASS  src/middleware/pretty-json/index.test.ts
 PASS  src/middleware/cors/index.test.ts
 PASS  src/middleware/basic-auth/index.test.ts
 PASS  src/middleware/compress/index.test.ts
 PASS  src/middleware/html/index.test.ts
 PASS  src/middleware/cache/index.test.ts
 PASS  src/middleware/powered-by/index.test.ts
 PASS  src/middleware/jsx/index.test.tsx
 PASS  src/middleware/jwt/index.test.ts
 PASS  src/middleware/logger/index.test.ts

Hi @Code-Hex !
Looks good to me!
@akiym Can you review it?:)

Thanks @akiym !
I'll add you as a co-author for this PR.


fix issue #2775

Fix the issue that Redis maxConnLifetime parameter not working.
Fixes #2775.

将 "github.com/go-redis/redis/v8" 库的IdleCheckFrequency选项由默认的1分钟改为10秒, 此参数用于检查空闲连接的频率, 如果gf redis client的MaxConnLifetime默认值设置成了30s(小于1分钟), 那么为使其生效, IdleCheckFrequency选项的值应该小于MaxConnLifetime才可以.

Codecov Report
Patch coverage: 100.00% and project coverage change: -0.36 :warning:

Comparison is base (41c0dde) 79.13% compared to head (f60280b) 78.78%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2777      +/-   ##
==========================================
- Coverage   79.13%   78.78%   -0.36%
==========================================
  Files         632      632
  Lines       52014    52015       +1
==========================================
- Hits        41161    40979     -182
- Misses       8820     9010     +190
+ Partials     2033     2026       -7

Flag
Coverage Δ

go-1.15-386
?

go-1.15-amd64
?

go-1.16-386
?

go-1.16-amd64
?

go-1.17-386
?

go-1.17-amd64
?

go-1.18-386
78.74% <100.00%> (-0.02%)
:arrow_down:

go-1.18-amd64
78.76% <100.00%> (-0.01%)
:arrow_down:

go-1.19-386
?

go-1.19-amd64
?

go-1.20-386
79.12% <100.00%> (+<0.01%)
:arrow_up:

go-1.20-amd64
79.08% <100.00%> (-0.03%)
:arrow_down:

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

Impacted Files
Coverage Δ

contrib/nosql/redis/redis.go
89.15% <100.00%> (+0.13%)
:arrow_up:

... and 7 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.


Add Python 3 support

This PR brings nearly full compatibility for Python 3, while maintaining Python 2 compatibility.
The sole exception is the R-markdown test, which for me is failing on master as well. The failures on master and on this PR match.

Thanks for doing this :)
All tests are passing for me on master though. The R test does fail for me with this PR.
The knitr calling has always been a bit fragile so it might be something to do with that.

Done! Let me know if this works! This still shows the same failure for me, but might be something weird with my R install. (It's a bit neglected these days!)

Thanks. Python 2 and 3 both passing for me now.
The default for the temp files is 'w+b', which is the cause of the problem on
python 3.
Remaining things to do:

[ ] update 442bbb as above (open tmp file as 'w+' and remove the 'rb' for
the template file)

[ ] squash all of the file IO commits together (the last two and 442bbb) -
together I think they should amount to just setting mode='w+' for each
of the temp files.

[ ] add six to the install_requires in setup.py

Re your failing R test: Does Knitr work for you from the command line? i.e. if
you run
notedown r-examples/r-example.Rmd --knit --to markdown

do you get sensible looking markdown? And if you run
notedown r-examples/r-example.Rmd --knit --rmagic

is the result the same as r-examples/r-example.ipynb? (less the outputs,
which you can generate with --run)

Hey @aaren, what do you mean "442bbb"? From context it sounds like you're talking about 37e4b25? There is no commit 442bbb in this history...

Well, I'm assuming you meant 37e4b25, which I have now reverted and squashed in with all the knitr changes, as well as added six to the requirements, so we should be all good!
As to Knitr, no, not working. Here's my output to notedown r-examples/r-example.Rmd --knit --rmagic:
{
 "cells": [
  {
   "cell_type": "code",
   "execution_count": null,
   "metadata": {},
   "outputs": [],
   "source": [
    "%load_ext rpy2.ipython"
   ]
  }
 ],
 "metadata": {},
 "nbformat": 4,
 "nbformat_minor": 0
}

The first command, notedown r-examples/r-example.Rmd --knit --to markdown, produces no output at all.

Merged. Thanks again for doing this.
Do you definitely have knitr installed? i.e. you don't get and error if you
start the R interpreter and then do require(knitr)?

No worries! My workflow now depends on this and I really want to move to Python 3 full time so it's a very self-interested PR! =) Nonetheless, happy to help!
btw, do you think you might cut a release with this so I don't have to install from github? (not that it's a huge deal, just slightly less elegant.)
Finally, re: knitr, indeed I don't have it installed, so that explains a few things. =P It might be worth raising an error when knitr can't be found, rather than failing silently. But I'll leave that to you. I don't need knitr right now so I'm not worried about this!

Sorry, meant to do that already. I've just released notedown 1.4.0.
Yes, raising an error would be preferable. Have opened #18.
On Tue 14 Apr, Juan Nunez-Iglesias wrote:

No worries! My workflow now depends on this and I really want to move to Python 3 full time so it's a very self-interested PR! =) Nonetheless, happy to help!
btw, do you think you might cut a release with this so I don't have to install from github? (not that it's a huge deal, just slightly less elegant.)
Finally, re: knitr, indeed I don't have it installed, so that explains a few things. =P It might be worth raising an error when knitr can't be found, rather than failing silently. But I'll leave that to you. I don't need knitr right now so I'm not worried about this!

Reply to this email directly or view it on GitHub:
https://github.com/aaren/notedown/pull/15#issuecomment-93221907


[CUDA] Multi-GPU for CUDA Version

This is to integrate multi-GPU support for CUDA version, with NCCL.

@guolinke This is almost ready. You may review this when you have time. Thanks.

are there any tests for the multi-GPU training?


GlobalHeaderProfile: invalid DOM nesting

Version: 0.8.10
The following generates invalid li DOM nesting:
<GlobalHeader>
  <GlobalHeaderProfile/>
</GlobalHeader>

Apologies for the late reply. Here's the SLDS component it's modeled after https://www.lightningdesignsystem.com/components/global-navigation/ if you'd like to submit a pull request.


Fixes carthage build

I've made the BentoKit scheme not-shared so we don't longer need ReactiveCocoa in Cartfile (as @mluisbrown suggested).
It should solve https://github.com/Babylonpartners/Bento/issues/163
It's a hotfix only. We should remove BentoKit completely from the repo in a future release.
The hotfix/0.4.1 branch has been created form master.
EDIT:
I also had to update CircleCi config

Is the plan to move BentoKit to a separate repo?

I think "yes". However, the fact you asked the question I'm not sure now 😅

Does CI only work with shared schemes? It’s a pity we have to lose CI for BentoKit with this fix for Carthage :/

yeah, you are right @mluisbrown. I was saying to myself "I can delete it because we delete the BentoKit".... but we still use it internally :/
In that case I don't know if we should do this. I don't know CircleCI so much, however it has reported that test has failed for BentoKit in this PR.
script/test iphonesimulator "platform=iOS Simulator,name=iPhone 6,OS=12.2" BentoKit
^D^Dxcodebuild: error: The workspace named "Bento" does not contain a scheme named "BentoKit". The "-list" option can be used to find the names of the schemes in the workspace.
Exited with code 65```

Having thought about this some more, my view is that we should not make this change at all. The issue was conflicting versions of RAC. The user had 10.0.0 in their Cartfile, whereas BentoKit was requresing 9.0.0.
I think the correct "resolution" to the issue would have been to inform the user that, for the time being at least, if you use Bento, you have to use RAC 9.0.0.
If we keep BentoKit in this repo, then this will be, IMO, a minor issue for some users. You will just have to always use the same version of RAC that BentoKit requires 🤷♂
If we move BentoKit to a separate repo, that would solve the problem entirely.


Remove explicit help

nodenv 1.0 handles --help for subcommands automatically

as this relies on nodenv 1.0, which just hit homebrew on Jan 22, don't want to merge this quite yet. giving nodenv 1.0 maybe a month lead time on homebrew?


Using a retry with back off for auth refreshing.

The Credential retrieval has occassional issues under load.  Dataflow, for example, will start a whole bunch of jobs that need to get credentials at the same time, and we've seen intermittent failures because of that issue; the retry should fix, or at least improve, those types of situations.

Sounds like awesome!
This scenario we saw for sure and any kind of improvment is highly welcome

I have no problem retrying getting credentials on IOException. If this is intended to fix issue: https://github.com/GoogleCloudPlatform/cloud-bigtable-client/issues/475, we need to make sure retrying will actually help.

LGTM, some nits


Added Norwegian

I added Norwegian, I'll add more languages

why did you translate the comments as well 😟 ? did you just run this through a translator..

no, i translated because i felt a bit bored.

but why would you translate the comments


Refine standardrb configuration

After running standardrb --fix I still get this repeating error. I don't feel I understand this well enough to mess with it.
(base) simonc@Simons-15-MBA-225 ruby-flightplans % standardrb
standard: Use Ruby Standard Style (https://github.com/standardrb/standard)
  lib/bcf/flight_plans/dsl.rb:9:26: Lint/Syntax: unexpected token tAMPER (Using Ruby 3.2 parser; configure using `TargetRubyVersion` parameter, under `AllCops`)
  lib/bcf/flight_plans/dsl.rb:43:7: Lint/Syntax: unexpected token kEND (Using Ruby 3.2 parser; configure using `TargetRubyVersion` parameter, under `AllCops`)
  lib/bcf/flight_plans/dsl.rb:50:5: Lint/Syntax: unexpected token kEND (Using Ruby 3.2 parser; configure using `TargetRubyVersion` parameter, under `AllCops`)
  lib/bcf/flight_plans/dsl.rb:61:28: Lint/Syntax: unexpected token tAMPER (Using Ruby 3.2 parser; configure using `TargetRubyVersion` parameter, under `AllCops`)
  lib/bcf/flight_plans/dsl.rb:75:9: Lint/Syntax: unexpected token kEND (Using Ruby 3.2 parser; configure using `TargetRubyVersion` parameter, under `AllCops`)
  lib/bcf/flight_plans/dsl.rb:79:26: Lint/Syntax: unexpected token tAMPER (Using Ruby 3.2 parser; configure using `TargetRubyVersion` parameter, under `AllCops`)
  lib/bcf/flight_plans/dsl.rb:111:7: Lint/Syntax: unexpected token kEND (Using Ruby 3.2 parser; configure using `TargetRubyVersion` parameter, under `AllCops`)
  lib/bcf/flight_plans/dsl.rb:116:5: Lint/Syntax: unexpected token kEND (Using Ruby 3.2 parser; configure using `TargetRubyVersion` parameter, under `AllCops`)

I've discarded some of what it wanted to do, @joshuacoles is better qualified to decide if what it wants is ok. So running it again will show more issues.

I believe I have resolved this issue. It was due to misapplication of the Style/ArgumentsForwarding rule. I have disabled this rule for now


Forms - Horizontal Checkboxes: Update spacing to 24px between options

Created a duplicate in Trello. Will continue progress/conversation there.


Create and manipulate comments on post data

User Stories

As a user, I can leave a comment on another user's post

As a user, I can see comments other users leave on my posts

As a user, I can delete a comment on a post

Last push adds this feature


Ak0702 expire

FIXME: Expired campaigns should have gray scale images and stop being bored should be gray. https://github.com/DoSomething/product/blob/master/LetsDoThis/Screens/Discovery/Main Feed Expired.png


Chinwendu Agbaetuo - potfolio URL fix

Changed URL profile link

Hi Chinwendu! Would you please update your commit to add yourself to the list alphabetically by surname? Thank you!

Hi Chinwendu! Would you please update your commit to add yourself to the list alphabetically by surname? Thank you!

Okay, I will do that


Please help with a bricked pixhack

Hi,
I have a cuav Pixhack - the fmu-v2 version -, I was uploading ArduPlane chibios firmware to it and it seems to fail at erasing stage or so on - maybe due to bad USB cable.
Now the device doesn't boot at all, it's not even recognized on windows when I connect it, no com port or USB device is recognized.
Please help me to recover it.

i think you need a ftdi conection

but, forget it, cuav dont help no one here,
I never buy from this brand again, it has no guarantee or quality that will work correctly its products, besides having a very high price

@Raviu8 The use of these products can be directly linked to shop after sale.


[Questionnaires] Adding the ability to save QuestionnaireResponse as In Progress

Describe the feature

Currently, when a user exits a form without saving they are only presented with the dialog letting them know that the form content will be discarded.

We however want to give the user the ability to save the  QuestionnaireResponse as In Progress instead of discarding the form content.

Proposed Technical Implementation

[x] Add a boolean canSaveDraft to the method launching the Questionnaire.

[x] This boolean will be false by default.

[x] If the canSaveDraft is set to true then the dialog that appears when a user exits the form will update to have 2 options.

[x] Save Partially -- Allows the user to save the questionnaire partial by setting the QuestionnaireResponse QuestionnaireResponse.status property to in progress, then redirects to the screen before the questionnaire render.
[x] Discard -- This discards all the inputs on the form and closes the Questionnaire render page, then redirects to the screen before the Questionnaire.

[x] Resource extraction should only be done when the QuestionnaireResponse.status == completed

Related SDK Issue

https://github.com/google/android-fhir/issues/1608

Related Discussion

https://github.com/opensrp/fhircore/discussions/1557

Cool, and these would get synced to server, and then down to other devices?

Cool, and these would get synced to the server, and then down to other devices?

@pld this is interesting. With the current sync setup yes. I see situations where these don't need to be synced.
We might want to add a configurable way to mark resources that shouldn't be synced up to the server.

K yea maybe, it's not necessarily bad, it's a feature we've seen requested, it does make me wonder about increased risk of conflicts

@allan-on Any feedback on this?

@dubdabasoduba The implementation is done and the associated PR is under review.
A couple of things came up during the implementation.

The confirmation dialog has 2 options i.e. Discard (changes) or Save partially  (draft). Ordinarily, the dialog would have Cancel as an option to return back to the form. With that option not available when saving a draft, to achieve the same, AlertDialog implementation is refactored to allow showing a dismissable one so that one can click outside the dialog to dismiss it and get back to the form.

SDC QuestionnaireResponse validation is skipped when saving the response since the QuestionnaireResponse would most times be incomplete but a custom validation implementation avoids saving completely empty responses.

@allan-on how do we specify if the Questionnaire needs to check for in progress? or is this default for all questionnaires now?

Had a conversation w @jingtang10.
It's not possible to prevent certain resources getting sync to the server, we don't have the API to do that yet.
But it's a reasonable thing to add.
Our use case is: Prevent in-progress Questionnaire Response to sync up

We should do it by using local-only resources, which the sync API will ignore in all its jobs. And when the local-only resouce needs to be synced, we should have an API that allows the app to "flip" the local-only flag, and the sync API should pick it up.

@jingtang10 yeah, that's the simplest way to do it 👍

For our current use-case we don't need to prevent the sync up because the in-progress QuestionnaireResponse is not extracted yet to the output resources e.g. Patient, Person e.t.c
The feature will come in handy though when we want to implement some sort of edit window after data is collected on the device before a sync up.


Easy Issue (React.js)  #1590

Pull Request Type
What kind of change does this PR introduce?
[✔ ] Solved an issue/task
What is the current behavior?
 A new card component in react
Issue Number: [ #1590]
What is the new behavior?
 A simple card with image, title, and description.
Other information

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


consider Evil Mode

The sortedSearch example shows the suffering of having a great tool like new Function(...) but no access to the local context.
Until JS has tools similar to D's template mixins and string mixins, we might consider an optional activation of the One Evil Thing.
For more background, see the discussion on comp.lang.javascript.
Result
Added a .getImplEval method to support eval, as in:
    // First "declare" all functions so that co-dependencies can be
    // solved.
    //
    // Use `mfunD` to debug
    var improveFirst = mfun( improveFirst )
    ,   improveLast  = mfun( improveFirst, improveLast )
    ;

    // Now we can implement them, using evil access to the local
    // lexical scope so that we do not need to write parameters
    // repeatedly 5 times (see above `function sortedSearch(...)`).
    improveFirst = eval( improveFirst.getEvalImpl() );
    improveLast  = eval( improveLast.getEvalImpl() );

For a complete use case see sorted_search_local about here

The first thing would be to check the current behaviour of The Evil One in the current JS engines.

Maybe it's cleaner and easier to do the "half thing", as in:
function sortedSearch(sortedArray, x, /*?fun?*/less, /*?fun?*/equal)
{
     // ....
      return improveFirst(  // UNCHANGED
            sortedArray, x, less, equal, isFirstFound, isLastFound
            , first_found, last_found, i, j, imax, jmin
        );
}

// ...

   // --- Private details

    function improveFirst(  // UNCHANGED
        sortedArray, x, less, equal, isFirstFound, isLastFound
        , first_found, last_found, i, j, imax, jmin
    )
    {
 // ...
  return mret(  // CHANGED
            improveLast
            , fext.__inputArgs__
        );
    }

for a partial use we could also have return mret( otherFun, a, b, c, fext.__restInputArgs );

won't do it for now

won't do the argument macros either, impossible to implement in debug mode

Actually did it, including support for debug mode :)
See top comment of #11, and sorted_search_local use case about here


Support 7.4.2

When specifying 7.4 as version, it installs 7.4.1 instead of 7.4.2. Can this be bumped?

So if you try 7.4.2 as version the 7.4.1 version is found, can i help you to get this fixed?

@prisis This can be done currently by adding a step after setup-php with sudo apt-get update php7.4. In v2 as I said, I will add an input update, when true it will update to the latest patch.

@ruudk @prisis Now the version on the runner is 7.4.2

@ruudk @prisis
Now you can force update to latest patch release
https://github.com/shivammathur/setup-php#force-update

Thanks, will this slow down the builds?

Currently the latest release 7.4.2 is on the runner, so this is not useful. When the next version is released you can use this. It will take extra time then to update the version.
I would advise to use this only if the patch release has fixes which affect your project. It takes GitHub around 1-2 weeks to update the version on the runner after the release, so it is up to you if you want to wait or force update. The option is there now.


Cannot connect to the Docker daemon

Do you want to request a feature or report a bug?
Bug
What did you do?
Traefik was running with the Docker backend when suddenly it is no longer able to talk to Docker over the daemon socket:
time="2018-06-27T18:20:01Z" level=error msg="Failed to retrieve information of the docker client and server host: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"
time="2018-06-27T18:20:01Z" level=error msg="Provider connection error Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?, retrying in 7.365042107s"

After seeing this error in the logs I simply restarted the traefik container (docker restart traefik) and now it is working again.
What did you expect to see?
The Traefik container was working and so should continue to work and not require restarts to be fixed.
What did you see instead?
It suddenly was no longer able to talk to Docker so not being able to communicate with the provider it no longer is able to serve traffic. The docker CLI commands all still worked just fine (e.g. docker ps) indicating that there was nothing wrong with the socket itself. It was broken for several days since this server only serves review apps, but this is concerning since I am considering also using Traefik in production.
Output of traefik version: (What version of Traefik are you using?)

The configuration is very simple, all running on a single Ubuntu 16.04 machine. A wildcard SSL is used for https (traditional, not ACME). Docker version is 17.12.0-ce.
traefik.toml
defaultEntryPoints = ["http", "https"]
[entryPoints]
[entryPoints.http]
address = ":80"
[entryPoints.https]
address = ":443"
[entryPoints.https.tls]
[[entryPoints.https.tls.certificates]]
certFile = "/sslmate/*.example.com.chained.crt"
keyFile = "/sslmate/*.example.com.key"
[retry]
[docker]
endpoint = "unix:///var/run/docker.sock"
domain = "example.com"
watch = true
exposedbydefault = false

docker-compose.yml
version: '3'

services:
  traefik:
    image: traefik:alpine
    command: --logLevel=DEBUG
    restart: always
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./traefik.toml:/traefik.toml
      - /etc/sslmate:/sslmate
    networks:
      - proxy
    container_name: traefik

networks:
  proxy:
    external: true

If applicable, please paste the log output in DEBUG level (--logLevel=DEBUG switch)
Thousands of entries like this:
time="2018-06-27T18:20:01Z" level=error msg="Failed to retrieve information of the docker client and server host: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"
time="2018-06-27T18:20:01Z" level=error msg="Provider connection error Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?, retrying in 7.365042107s"

Hello @colinmollenhour.
Thank you for this report. We have some follow up questions:

Is there any possibility that a system update or service restart may have broken the docker socket connection? As you see in the logs, traefik tries to reconnect to a lost connection, but if it can't reconnect, obviously issues may present themselves.

Could you try using the latest version of traefik (1.6.4)? It has hundreds of improvements over the 1.5.1 version. It is possible whatever caused that issue has already been fixed.

Please let us know. We will hold this ticket open while we await your response.
Thanks!

Hi! I'm Træfiker :robot: the bot in charge of tidying up the issues.
Thanks again for your interest in Træfik!
I'm glad to close the issue because I think that the question has been answered (Yes, I'm quite an advanced AI :smile:)
Join our Slack workspace for more community #support.


Allow escape key to clear input?

I would like to optionally enable the escape key (or another key) to clear the input if and only if the calendar is already closed. This will allow a user to clear the input without using the mouse.
https://github.com/charliekassel/vuejs-datepicker/blob/master/src/components/DateInput.vue#L111

I don't think that is good UI and not consistent with other inputs.

What do other inputs do?

@InstanceOfMichael It's inconsistent because Esc is not semantic for "Clear input". Maybe the Delete key or D could be better.
BUT...
If you want to clear the input with a key press (ex. Delete), add a listener for @kepdown (adjust) to its parent container and call to the clearDate(), via $refs (see https://github.com/charliekassel/vuejs-datepicker/issues/424), when user uses the Delete key (or the key you want). So, when date picker is not focused, you can clear the data programmatically.


Upvoting Issue (appending value instead of adding or deducting)

Hello,
I'm having an issue with upvoting.
When I click the upvote icon, instead of adding a value to the current vote count, it appends a number 1 next to the current votes number.
For example, if comment X has 2 votes and I upvote, instead of showing 3 votes, it shows 21 and if I click that same button again, it displays 20. The +1 and 0 are appending next to the value.
However, this only happens when there is at least one vote for the comment and the current user had not voted yet.
If the count is 0 at the moment of voting, then it works as intended it changes the 0 to a 1. Also, if the current user has already voted and I click the icon, it deducts 1 to the current count.
So, the issue only comes up when there are votes in place and the current user is about to vote. I noticed this behaviour because I had manually inserted votes to the db when testing the vote count query and the current user voted query.
Not sure what could be causing this behaviour.

Nevermind. I fixed the issue by parsing the upvote count as int.
var previousUpvoteCount = parseint(comment model.upvoteCount);
I guess it was picking it up as text rather than a number but it's odd because the upvote value is setup as int in the database.


[BUG] Parser/Linter error: Falco doesnt support calling sub with ()

Falco doesn't accept the following syntax:
sub foo {
  log "1234";
}

sub vcl_recv {

  #Fastly recv
  call foo();
  set req.backend = httpbin_org;

  return (pass);
}

With error:
💥  Missing semicolon
in /Users/sotiris.nanopoulos/dev/falco/examples/default01.vcl at line 35, position 8
 30|}
 31|
 32|sub vcl_recv {
 33|
 34|  #Fastly recv
 35|  call foo()

But fiddle is ok with it:
https://fiddle.fastlydemo.net/fiddle/2a1d3753

If anyone wants to take so be it, otherwise I might be working on it on friday

fixed by https://github.com/ysugimoto/falco/pull/92


Vulkan GPU Memory Leak and Crash

⚠ Issues not using this template will be systematically closed.
Describe the bug
On Windows, when using Vulkan, on some GLTF scenes GPU memory usage increases constantly during execution, leading the application to crash due to running out of memory.
To Reproduce
Steps to reproduce the behavior:

Download the following scene as GLB file from sketchfab:
Test Asset by Pixel
Launch gltf_viewer.exe
Observe the application run out of memory and crash.

Expected behavior
The application memory should stay constant when no new data is created, and should not run out of memory and crash.
Screenshots
As seen in Task Manager:

Desktop (please complete the following information):

OS: Windows 10 22H2
GPU: NVIDIA RTX 4080 OC
Backend: Vulkan

In my brief testing, this issue does not seem to happen on the OpenGL backend.

Any updates on this? Has this issue been reproduced?

I'm still able to reproduce this issue in v1.50.4 - any updates?

Sorry for the delay.  I'll try to repro this week.  It's likely that I'll address this in an upcoming refactor, but it might take a little while more.

This might not be the case anymore after the Vulkan refactor, but last time I checked the pipeline cache, it was using the render target pointer or texture as a key, and if recreating the render target per frame the cache will invalidate per frame, causing it to grow a lot. I think a better option would be to use the RT/Texture descriptors (formats) instead as key, not the pointers directly.

Is there any ETA for a fix for this problem? It's proving to be a massive issue in production.

Still in progress.  No hard ETA unfortunately, but I expect some result in these two weeks.

This seems be resolved in the latest version - at least on my hardware!
Might be worth looking into further, but I think I can close this issue for now.

hmm, interesting.  So the cause might be this: https://github.com/google/filament/commit/d05c61fe9a982035caecfea179896b4111fb28f3
Thanks for the update!

Might have been! It's definitely worth further testing. I'll keep my eye on future releases and re-open the issue if it comes up again.


requestFilter won't filter out body field

Say I want to log the request body most of the times (so I'll add it to the requestWhitelist)
But I also use the requestFilter callback option, and there I'll conditionally return undefined for the body prop (there ARE sensitive bodies!)
We can clearly see in those lines:
https://github.com/bithavoc/express-winston/blob/32a7747dfd32213b8a316b9c2b09becf8f8c7c29/index.js#L338-L344
That the filteredBody will get filled with my unwanted request body props (passing the same requestFilter to the filterObject in order to filter out body props is pointless, because it was intended to filter request props, not body props)
And then, here at those lines:
https://github.com/bithavoc/express-winston/blob/32a7747dfd32213b8a316b9c2b09becf8f8c7c29/index.js#L349-L355
This filteredBody will unconditionally bring back the body to my log-request!
That's not only contradicts the docs:
requestFilter: function (req, propName) { return req[propName]; }, // A function to filter/return request values, defaults to returning all values allowed by whitelist. If the function returns undefined, the key/value will not be included in the meta.

...There is no exception mentioned for the body request value!
That's also not aligned with the behavior of the responseFilter (which will filter-out the response body)
But also, in my opinion, poses a security risk, because people will are using filters to filter out sensitive data.
A fast solution could be just add a condition like that:
if (filteredRequest && filteredRequest.body) {
    if (filteredBody) {
        filteredRequest.body = filteredBody;
    } else {
        delete filteredRequest.body;
    }
}

But I don't sure this "patch" is a good idea, because as said, why pass this requestFilter to filter body props at all...

Seems like a bug, but if we fix it I think is also a breaking change. We're planning a 5.x series, we could fix the inconsistency there. Thoughts?

@bithavoc Thanks for the quick response. To avoid breaking changes, how about adding an explicit boolean option like requestExcludeBody?
It's not the most consistent or elegant solution, but it would allow to avoid the issue by painlessly by just changing line 334 from:
if (req.body !== undefined) {
//...
}

to
if (req.body !== undefined && !options.requestExcludeBody) {
//...
}

That would work, mind including some tests reproducing it and fixing it?

PR is here: #258


How to navigate to previous page without Visual Automation

Hi, how do I navigate forward and backwards on the browser without visual automation? Thanks

Try below (not at laptop now to validate). Below uses dom() to send JavaScript code to browser to run.
r.dom('window.history.back()')
r.dom('window.history.forward()')

Tagging @kompleksanda

Closing issue for now but let me know if above doesn't work. I think some online sources even omit the window base keyword and just use history.back()

Thanks Kensoh!


Copyedit README.md

Purpose

...

Does this introduce a breaking change?

[ ] Yes
[ x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ x] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

@mikebudzynski @shinjiDev - When you have a chance, please review these suggested editorial updates to README.md. Thank you.


fix: disregard calls success/failure and proceed when ens resolves

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


BUG FIX: Reward for each agent in intersection

The reward function for multi-agent scenarios was being calculated using the scaled speed of only the first agent being spawned (self.vehicle instead of the vehicle argument of the method).

Codecov Report

Merging #318 (0dd178f) into master (8ef95c3) will decrease coverage by 0.10%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #318      +/-   ##
==========================================
- Coverage   78.63%   78.53%   -0.11%
==========================================
  Files          45       45
  Lines        4157     4164       +7
==========================================
+ Hits         3269     3270       +1
- Misses        888      894       +6

Flag
Coverage Δ

unittests
78.53% <100.00%> (-0.11%)
:arrow_down:

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

Impacted Files
Coverage Δ

highway_env/envs/intersection_env.py
97.10% <100.00%> (ø)

highway_env/road/regulation.py
86.53% <0.00%> (-5.77%)
:arrow_down:

highway_env/envs/summon_env.py
94.91% <0.00%> (-1.70%)
:arrow_down:

highway_env/vehicle/kinematics.py
91.33% <0.00%> (-0.73%)
:arrow_down:

highway_env/envs/common/action.py
80.32% <0.00%> (-0.35%)
:arrow_down:

highway_env/envs/roundabout_env.py
96.90% <0.00%> (+0.09%)
:arrow_up:

Continue to review full report at Codecov.

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

ok, this is funny. What did I do wrong?
Did I misunderstand the functionality of that function?

No; I think that is absolutely right, good catch! Thanks a lot!
(No idea about codecov complaining, I think this may be related to randomness in the test, meaning that the resulting coverage itself is random. Tests should probably be seeded... The detected changes are unrelated with your PR anyway.)


Add Config option for OUTPUT_NAME?

Whether as a cmake::Config::new("foo").set_property(prop, val) or more specific .output_name(val), it would be handy to be able to set the OUTPUT_NAME - presently I'm running cmake::build("foo") and then having to fs::copy("foo/foo", format!("foo/foo-{}", env::var("TARGET")?)) in order for Tauri to pick it up as the correct build for the current target.
Maybe in most cases this is under the user's control since it can be set in CMakeLists.txt or wherever (I confess I don't really know cmake!) - but I'm compiling a third party binary, using it's own configure script, so I don't want to and can't cleanly mess with it.

Feel free to send a PR for this!

I've had a bit of a look at this, it seems CMake has independent concepts of 'variables', and 'properties'; the latter sub-divided into a number of scopes. OUTPUT_NAME is a property, specifically with the 'target' scope (makes sense - output per target).
It seems that all the.. let's call them options, set today in cmake-rs are variables, e.g. -DCMAKE_BUILD_TYPE.
As far as I can tell there isn't an equivalent CLI flag for setting properties. There is set_property, (and set_target_property) but that is to be used in a makefile (err, CMakeLists.txt?).
I'm not sure that it would be appropriate for cmake-rs to modify this file, or even to somehow merge its own configuration in with it (I looked for but didn't find a built-in way, but assuming commands can simply be appended this could be done in memory or with a temp file)? So unless I've missed a flag, I'm not sure how possible this is, unfortunately.
(An option specifically for OUTPUT_NAME though might be to pretend to support it, or not, but either way do nothing more intelligent than simply moving the real output to wherever's requested, as I'm currently doing with fs::copy after cmake::build.)

Ok in that case yeah seems like this crate can't do this. I would prefer to not get into the business of editing files if possible, but that can always be built as a separate crate!


Fix incorrect results returned by min, max and avg

Fix incorrect results returned by min, max and avg when processing null/missing values only.
Signed-off-by: Yury-Fridlyand<EMAIL_ADDRESS>Description
Before
opensearchsql> select min(int0) from calcs where int0 IS NULL;
fetched rows / total rows = 1/1
+-------------+
| min(int0)   |
|-------------|
|<PHONE_NUMBER>  |
+-------------+

After
opensearchsql> select min(int0) from calcs where int0 IS NULL;
fetched rows / total rows = 1/1
+-------------+
| min(int0)   |
|-------------|
| null        |
+-------------+

Fixed:

min
max
avg

Not fixed:

sum

opensearchsql> select sum(int0) from calcs where int0 IS NULL;
fetched rows / total rows = 1/1
+-------------+
| sum(int0)   |
|-------------|
| 0           |
+-------------+

mysql> select sum(int0) from calcs where int0 IS NULL;

+-----------+
| sum(int0) |
+-----------+
|      NULL |
+-----------+
1 row in set (0.00 sec)

This requires much more changes.
Not affected

var_samp
var_pop
stddev_samp
stddev_pop

Issues Resolved
https://github.com/opensearch-project/sql/issues/817
Check List

[x] New functionality includes testing.

[x] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

What the MySQL result for sum(null)?  Is it supposed to be null or zero?

What the MySQL result for sum(null)? Is it supposed to be null or zero?

mysql> select sum(num0) from calcs where num0 is null;
+-----------+
| sum(num0) |
+-----------+
|      NULL |
+-----------+
1 row in set (0.00 sec)


ROX-18553: Sensor disconnect metric

Description
This PRs adds a new field for SensorHello message (.reconnect) which will be set to true if Sensor is attempting to reconnect to Central rather than doing an initial connection..
As of now there is no special behavior upon reconnects, this will be useful in Offline v2. But for now, we can at least capture a metric for every connection, and mark if it is a re-connection or not.
If displayed on a dashboard, the total number of Sensor restarts for a given cluster could be derived from: sensor_connected (where .reconnect == false) - sensor_connected (where .reconnect == true) - 1 .
A higher number of sensor_connected with .reconnect set to true could be related to network failures or central restarts. Because if connection was broken while Sensor was healthy, it remained up waiting for the connection to be re-established.
Checklist

[ ] Investigated and inspected CI test results
[x] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

Testing Performed

[x] Added new test Test_SensorHello.
[ ] CI

/test ocp-4-13-core-bpf-qa-e2e-tests

/test ocp-4-10-qa-e2e-tests

/retest


WordPress integration: cannot find actor by ActivityPub URI

Our code for:

wait_until_actor_is_following_actor and
wait_until_actor_is_unfollowing_actor and
wait_until_actor_is_unfollowing_actor and
wait_until_actor_is_unfollowed_by_actor

depends on the Mastodon API implementation being able to find the "Account Dict" by the ActivityPub Actor URI (not the @foo@bar webfinger handle).
Example API call: curl -H 'Authorization: Bearer d8dd76c74c63f80653b9c06312d4361e' 'https://wordpress-1.1234.com/api/v1/search?q=https%3A%2F%2Fmastodon-1.1234.com%2Fusers%2Ffeditestadmin&resolve=1'
This search works in Mastodon's own API implementation, but not in the implementation of the API by the WordPress Enable Mastodon Apps plugin.
As a result, the tests looking for followers and followed-by fail.

/cc @akirk @pfefferle in case you have any ideas.

I would say, the tests should focus on ActivityPub instead of the Mastodon API so I would use WebFinger instead: https://swicg.github.io/activitypub-webfinger/#reverse-discovery

The very reason why we pass around https Actor URLs (instead of acct handles) in the tests (random example: https://github.com/fediverse-devnet/feditest-tests-fediverse/blob/develop/tests/fediverse/for0.4/follow.py) is that we want to write tests that are as close to the ActivityPub spec as we can make them.
And to automate control / observation of the application-under-test (such as Mastodon, or WordPress), we need to map those https Actor URLs into the data structures that the Mastodon API requires so we can make the application-under-test "do things". So we use the "search" call to find out what the local data structure is that corresponds to the https Actor URL, which works in Mastodon but not the WordPress app.
P.S. Like everything in the Mastodon API, it does not really specify the semantics that "conformant implementations" must provide. I would argue, though, that searching for the https Actor URL should be one of the things it should find -- irrespective of FediTest. Just a thought ...

The WebFinger endpoint is not limited to acct URIs, you can also pass the Actor-URL: https://webfinger.net/lookup/?resource=https%3A%2F%2Fnotiz.blog%2Fauthor%2Fmatthias-pfefferle%2F
But maybe I do not exactly understand what you are trying to do? But still, I would avoid the Mastodon as much as possible! Why not use the Following endpoint for that?
For example: https://notiz.blog/wp-api/activitypub/1.0/actors/1/followers

We can do certain things with the URLs pointing to the followers collection etc. but not others:

E.g. if the test is: If a Mastodon user follows a WordPress user, and the WordPress user creates a post, the Mastodon user will receive it -- to automate this, we need to use the Mastodon API to make WordPress create a post.
Not all Fediverse software / instances / configurations publish lists of followers.
Some Fediverse software -- like Threads -- only allows access to the Actor URL and everything to be found from there for authenticated clients. To enable FediTest to access those, it would have to be not just a server, but one with a valid DNS entry and TLS cert etc. etc and we try to avoid this for various reasons, including developer experience.

Here's an architecture diagram, in case it is helpful: https://feditest.org/assets/2024-08-08/feditest-dwebcamp-slides/#22 . Note that FediTest itself is not a Node participating as a peer with the Nodes under test.

I see.
But I still would rely on ActivityPub as much as possible. I understand that threads and others do not support some of the endpoints, but most of them do not support the Mastodon API either.
So maybe we need a fallback mechanism here? Something like:

Try ActivityPub
fall back to Mastodon API
fall back to proprietary API

???


Azure IoT Device Certification

Hi! Is that possible to pass the Microsoft Azure IoT Device Certification in the case when we are using your IoT Device Bridge?
As far as I understand this bridge simulate the Azure IoT Hub, but before the strat of the Certification process it is required to authenticate the device via IoT Hub DPS that looks like not possible in a case of usage the IoT Device Bridge.
Thanks!

The current certification program is for devices that can connect directly to IoT Hub/DPS, so unfortunately that doesn't include devices that can only connect through this bridge.
However, we'd be very interested in learning more about the details of your specific use case. Adding @avneet723 here who can give more details.

Thanks!

@peolivei2 @avneet723
I am trying to perform "Azure Certified Device" certification with this Bridge.
It requires setting DPS ID Scope, DeviceId and symmetric key into device code.
Since we use this Bridge to act as Device, we just run the Bridge Deployment with those parameters.

After this, when we call the Register Bridge Endpoint, we see error in Bridge logs, saying:
{ "time": "2021-08-02 09:06:42.5330", "level": "INFO", "message": "Attempting DPS registration for device \"XXXXXX\", model Id NULL", "callsite": "DeviceBridge.Services.ConnectionManager.DpsRegisterInternalAsync, 891", "deviceId": "XXXXXXXX", "modelId": null, "idScope": "YYYYYYYY", "cv": "19ab9b4c-5f38-4b62-9d1b-a0cfc73c35a9" }
{ "time": "2021-08-02 09:06:42.7152", "level": "ERROR", "message": "Response: 500, ", "exception": "{\"errorCode\":401000,\"trackingId\":\"cd8ebc21-8865-441a-9e37-bad06b66af63\",\"message\":\"Unauthorized\",\"timestampUtc\":\"2021-08-02T09:06:42.7039184Z\"}", "callsite": "DeviceBridge.Common.RequestLoggingMiddleware.Invoke, 50", "cv": "7ac5b801-7311-372a-a71f-d58913ee4bd6", "path": "\/devices\/XXXXXXXXXXXXXXXX\/messages\/events", "deviceId": "XXXXXXXXXXXXXXXX" }

Do you have any ideas as, why the Bridge cannot authorize with the DPS?

@AnatoliiStepaniuk the symmetric key in the page you mentioned is a device-specific derived key, since it's trying to verify that this specific device is able to connect. To configure the Bridge, you need an enrollment group symmetric key, which can be used to authenticate multiple devices. That's the type of key you get in an IoT Central app or when you configure a DPS enrollment group manually.


Updates to github label automation tool

The labeler automation tool needs to be updated to support more features for our workflow.

Work with PRs
Automatically set the milestone for a PR to the current month
Avoid labeling PRs that don't point to the master branch
Allow PR authors to flag the PR with a comment that adds the changes-addressed label
More robust decision making system

This work was completed in about 1.5 weeks. V3 of the tool removed all V1 and V2 code.

I upgraded each config file on repositories using the tool to the new schema.
Added a condition system that allows us to easily configure a JMES query to run across the github payload data to decide if we want to continue processing the issue/PR
Now works with PRs and Comment payloads. (must be enabled in the repo config with the webhook settings)
Added more logging
Rewrote Kusto queries to investigate failures.


How to change the scaler when using the Tiny Time Mixer (TTM)

I am implementing TTM by following the tutorial of the tsfm_public package.
However, during evaluation, in the part where I call:
finetune_forecast_trainer.evaluate(test_dataset)
it appears that the eval_loss value is currently calculated based on the standard scaler. However, I would like to know the MSE value on the original scale. Could you provide guidance on how to achieve this?

For inverse scaling, you can use the forecasting pipeline, which makes use of the time series preprocessor for inverse scaling. Some examples can be found here: https://github.com/ibm-granite-community/granite-timeseries-cookbook/blob/main/recipes/Time_Series/Preprocessor_Use_and_Performance_Evaluation.ipynb

Thank you for your kind answer. I have one more question - could you show me how the get_datasets function is structured? When I tried to use it with my data, the length of train_dataset came out as 1, so I'd like to check how this function works.


E118: Too many arguments for function: getbufvar

environment

vim: 7.3
vim-airline: 8.2
OS: Mac OS 10.11.06
Have you reproduced with a minimal vimrc: ???
What is your airline configuration: ???
if you are using terminal:
terminal: 2.6.1
$TERM variable: ???
color configuration (:set t_Co?): didn't change from the begining
if you are using Neovim:
does it happen in Vim: ???

actual behavior
Since I installed airline plugin I started to face this issue that I mentioned in the title
Would appreciate help of fellow comrades of this community
Thanks in advance
expected behavior
????
screen shot (if possible)

Your  vim is too old is my guess. Please show the complete error message.

Am 09.10.2020 um 20:04 schrieb lakrau<EMAIL_ADDRESS>
environment
vim: 7.3
vim-airline: 8.2
OS: Mac OS 10.11.06
Have you reproduced with a minimal vimrc: ???
What is your airline configuration: ???
if you are using terminal:
terminal: 2.6.1
$TERM variable: ???
color configuration (:set t_Co?): didn't change from the begining
if you are using Neovim:
does it happen in Vim: ???
actual behavior
Since I installed airline plugin I started to face this issue that I mentioned in the title
Would appreciate help of fellow comrades of this community
Thanks in advance
expected behavior
????
screen shot (if possible)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Error detected while processing function airline#extensions#branch#get_head..air
line#extensions#branch#head..63_update_untracked..airline#async#vcs_clean..
airline#async#vim7_vcs_clean..84_set_clean_variables:
E118: Too many arguments for function: getbufvar
Here, thank you for your prompt response
also could you tell me how can I upgrade my Vim so it all would work without any problem?
Thanks

This depend on your system which you did not tell

Am 09.10.2020 um 21:04 schrieb lakrau<EMAIL_ADDRESS>
Error detected while processing function airline#extensions#branch#get_head..air
line#extensions#branch#head..63_update_untracked..airline#async#vcs_clean..
airline#async#vim7_vcs_clean..84_set_clean_variables:
E118: Too many arguments for function: getbufvar
Here, thank you for your prompt response
also could you tell me how can I upgrade my Vim so it all would work without any problem?
Thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.


Issue 38

This PR:

Fixes a stackoverflow error in HelpDoc
Implements the HelpDoc.toHTML method
Provides some basic CSS to render the HelpDoc in HTML

@jdegoes :  Here's a screenshot generated by outputting the HTML of the following HelpDoc
      HelpDoc.h1(HelpDoc.Span.text("Title (h1)")) +
      HelpDoc.p(HelpDoc.Span.text("Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.")) +
      HelpDoc.h2(HelpDoc.Span.text("A Title (h2)")) +
      HelpDoc.p(HelpDoc.Span.text("Contrary to popular belief, Lorem Ipsum is not simply random text.  Richard McClintock, a Latin professor at Hampden-Sydney College in Virginia, looked up one of the more obscure Latin words, consectetur, from a Lorem Ipsum passage, and going through the cites of the word in classical literature, discovered the undoubtable source. Lorem Ipsum comes from sections 1.10.32 and 1.10.33 of \"de Finibus Bonorum et Malorum\" (The Extremes of Good and Evil) by Cicero, written in 45 BC. This book is a treatise on the theory of ethics, very popular during the Renaissance. The first line of Lorem Ipsum, \"Lorem ipsum dolor sit amet..\", comes from a line in section 1.10.32.")) +
      HelpDoc.h3(HelpDoc.Span.text("A Title (h3)")) +
      HelpDoc.p(HelpDoc.Span.text("It is a long established fact that a reader will be distracted by the readable content of a page when looking at its layout. The point of using Lorem Ipsum is that it has a more-or-less normal distribution of letters, as opposed to using 'Content here, content here', making it look like readable English. Many desktop publishing packages and web page editors now use Lorem Ipsum as their default model text, and a search for 'lorem ipsum' will uncover many web sites still in their infancy. Various versions have evolved over the years, sometimes by accident, sometimes on purpose (injected humour and the like).")) +
      HelpDoc.p(HelpDoc.Span.code("""
      |package zio
      |
      |import zio.internal.Platform
      |
      |trait BootstrapRuntime extends Runtime[ZEnv] {
      |  val environment: ZEnv = ZEnv.Services.live
      |
      |  /**
      |   * The platform of the runtime, which provides the essential capabilities
      |   * necessary to bootstrap execution of tasks.
      |   */
      |  val platform: Platform = Platform.default
      |}
      |""".stripMargin))

Looks nice!


Favicon Added

resolved #1
Favicon is added in a web page.

how should i undo the spin png feature please tell ?

done !

Thanks you 😊😊✨


Not being able to compile projects

when I try to compile I get this Message
rashid@192 lang_1_buggy % defects4j compile
Running ant (compile)...................................................... FAIL
Executed command:  cd /Users/rashid/Desktop/S2/lang_1_buggy && /Users/rashid/Desktop/S2/defects4j/major/bin/ant -f /Users/rashid/Desktop/S2/defects4j/framework/projects/defects4j.build.xml -Dd4j.home=/Users/rashid/Desktop/S2/defects4j -Dd4j.dir.projects=/Users/rashid/Desktop/S2/defects4j/framework/projects -Dbasedir=/Users/rashid/Desktop/S2/lang_1_buggy -Dbuild.compiler=javac1.7  compile 2>&1
/Users/rashid/Desktop/S2/defects4j/major/bin/ant: line 12: /Library/Internet: No such file or directory
Cannot compile sources! at /Users/rashid/Desktop/S2/defects4j/framework/bin/d4j/d4j-compile line 82.
Compilation failed in require at /Users/rashid/Desktop/S2/defects4j/framework/bin/defects4j line 195.

This is the output of my environment
rashid@192 lang_1_buggy % java -version
java version "1.8.0_361"
Java(TM) SE Runtime Environment (build 1.8.0_361-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.361-b09, mixed mode)
rashid@192 lang_1_buggy % echo $JAVA_HOME
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
rashid@192 lang_1_buggy % cd ..
rashid@192 S2 % echo $JAVA_HOME
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
rashid@192 S2 % locale
LANG=""
LC_COLLATE="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_ALL="en_US.UTF-8"

@aca20rma, could you please run the following command
cat /Users/rashid/Desktop/S2/defects4j/major/bin/ant

and paste here the output?

this is my output
#!/bin/sh
BASE="dirname $0/.."
if [ -z "$JAVA_HOME" ]; then
CMD="java"
else
CMD="$JAVA_HOME/bin/java"
fi
$CMD
-XX:ReservedCodeCacheSize=256M
-XX:MaxPermSize=1G
-Djava.awt.headless=true
-Xbootclasspath/a:$BASE/config/config.jar
-jar $BASE/lib/ant-launcher.jar -Dbuild.compiler=javac1.7 $*

You can't compile any bug because your JAVA_HOME points to a path with empty spaces
rashid@192 S2 % echo $JAVA_HOME
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home

I guess you've to quote the $CMD on line 11, so that the command executed is
"/Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java"

instead of
/Library/Internet

Please let me know if my suggestion fixes this issue.

Additionally, I've also noticed that your major/bin/ant file ends as
    -jar $BASE/lib/ant-launcher.jar -Dbuild.compiler=javac1.7 $*

and the official one as
    -jar $BASE/lib/ant-launcher.jar $*

Why have you added -Dbuild.compiler=javac1.7 to the major/bin/ant file?


Adding Ecole Centrale Paris

Institution/School Name
Ecole Centrale Paris
Instiution/School Website
http://www.ecp.fr/lang/en/homepage
Email Users
@student.ecp.fr
Please place an x between the square brackets if yes

[X] Students
[ ] Academic/Teaching Staff
[ ] Other/Support Staff

Education Levels
Please place an x between the square brackets if yes

[ ] Post-graduate research
[X] Graduate School
[ ] College (University) or Undergraduate School or equivalent
[ ] Community College or equivalent
[ ] High School or equivalent
[ ] Elementary School or equivalent

Hi,
It would appear that you have opened a pull-request containing commits from JetBrains/swot which is a fork of this repository (leereilly/swot).
If you intended to create a pull request for JetBrains/swot, may I suggest you create a pull request there.
We cannot accept your pull request if it contains more than one institution, as is the case here.
If you want your institution to be included please follow the following steps:

Delete your fork of swot
Create a new fork of swot based upon this repository
Create the file (and directories if necessary) to add the institution to your fork
Open a new pull request against this repository to merge your fork.

I am closing this pull request, as it is for the wrong repository.