Failing on Windows runners

When running on a Windows action runner with runner: windows-latest, this action fails on index.js line 36:
https://github.com/GoTestTools/gotestfmt-action/blob/65f1d2228f06cc5e828b84597440fbd063d12ea2/index.js#L36

Full Workflow log

```
Run GoTestTools/gotestfmt-action@v[2](https://github.com/norwd/pword/actions/runs/3341225601/jobs/5532217476#step:4:2).1.0
  with:
    token: ***
    org: GoTestTools
    repo: gotestfmt
  env:
    GOROOT: C:\hostedtoolcache\windows\go\1.19.2\x64
Running on OS 'msys_nt-10.0-20[3](https://github.com/norwd/pword/actions/runs/3341225601/jobs/5532217476#step:4:3)[4](https://github.com/norwd/pword/actions/runs/3341225601/jobs/5532217476#step:4:4)8'
Downloading latest stable gotestfmt version starting with v2. from GoTestTools/gotestfmt...
Found release v2.4.1 matching criteria, attempting to download binary...
Examining release asset gotestfmt_2.4.1_checksums.txt at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.1/gotestfmt_2.4.1_checksums.txt ...
Examining release asset gotestfmt_2.4.1_darwin_amd[6](https://github.com/norwd/pword/actions/runs/3341225601/jobs/5532217476#step:4:6)4.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.1/gotestfmt_2.4.1_darwin_amd64.tar.gz ...
Examining release asset gotestfmt_2.4.1_darwin_arm64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.1/gotestfmt_2.4.1_darwin_arm64.tar.gz ...
Examining release asset gotestfmt_2.4.1_linux_3[8](https://github.com/norwd/pword/actions/runs/3341225601/jobs/5532217476#step:4:9)6.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.1/gotestfmt_2.4.1_linux_386.tar.gz ...
Examining release asset gotestfmt_2.4.1_linux_amd64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.1/gotestfmt_2.4.1_linux_amd64.tar.gz ...
Examining release asset gotestfmt_2.4.1_linux_arm64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.1/gotestfmt_2.4.1_linux_arm64.tar.gz ...
Examining release asset gotestfmt_2.4.1_windows_386.zip at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.1/gotestfmt_2.4.1_windows_386.zip ...
Examining release asset gotestfmt_2.4.1_windows_amd64.zip at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.1/gotestfmt_2.4.1_windows_amd64.zip ...
Binary download failed, trying next release. (No release asset matched postfix '_msys_nt-[10](https://github.com/norwd/pword/actions/runs/3341225601/jobs/5532217476#step:4:11).0-[20](https://github.com/norwd/pword/actions/runs/3341225601/jobs/5532217476#step:4:21)348_amd64.tar.gz'.)
Found release v2.4.0 matching criteria, attempting to download binary...
Examining release asset gotestfmt_2.4.0_checksums.txt at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.0/gotestfmt_2.4.0_checksums.txt ...
Examining release asset gotestfmt_2.4.0_darwin_amd64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.0/gotestfmt_2.4.0_darwin_amd64.tar.gz ...
Examining release asset gotestfmt_2.4.0_darwin_arm64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.0/gotestfmt_2.4.0_darwin_arm64.tar.gz ...
Examining release asset gotestfmt_2.4.0_linux_386.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.0/gotestfmt_2.4.0_linux_386.tar.gz ...
Examining release asset gotestfmt_2.4.0_linux_amd64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.0/gotestfmt_2.4.0_linux_amd64.tar.gz ...
Examining release asset gotestfmt_2.4.0_linux_arm64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.0/gotestfmt_2.4.0_linux_arm64.tar.gz ...
Examining release asset gotestfmt_2.4.0_windows_386.zip at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.0/gotestfmt_2.4.0_windows_386.zip ...
Examining release asset gotestfmt_2.4.0_windows_amd64.zip at https://github.com/GoTestTools/gotestfmt/releases/download/v2.4.0/gotestfmt_2.4.0_windows_amd64.zip ...
Binary download failed, trying next release. (No release asset matched postfix '_msys_nt-10.0-20348_amd64.tar.gz'.)
Found release v2.3.2 matching criteria, attempting to download binary...
Examining release asset gotestfmt_2.3.2_checksums.txt at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.2/gotestfmt_2.3.2_checksums.txt ...
Examining release asset gotestfmt_2.3.2_darwin_amd64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.2/gotestfmt_2.3.2_darwin_amd64.tar.gz ...
Examining release asset gotestfmt_2.3.2_darwin_arm64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.2/gotestfmt_2.3.2_darwin_arm64.tar.gz ...
Examining release asset gotestfmt_2.3.2_linux_386.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.2/gotestfmt_2.3.2_linux_386.tar.gz ...
Examining release asset gotestfmt_2.3.2_linux_amd64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.2/gotestfmt_2.3.2_linux_amd64.tar.gz ...
Examining release asset gotestfmt_2.3.2_linux_arm64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.2/gotestfmt_2.3.2_linux_arm64.tar.gz ...
Examining release asset gotestfmt_2.3.2_windows_386.zip at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.2/gotestfmt_2.3.2_windows_386.zip ...
Examining release asset gotestfmt_2.3.2_windows_amd64.zip at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.2/gotestfmt_2.3.2_windows_amd64.zip ...
Binary download failed, trying next release. (No release asset matched postfix '_msys_nt-10.0-20[34](https://github.com/norwd/pword/actions/runs/3341225601/jobs/5532217476#step:4:35)8_amd64.tar.gz'.)
Found release v2.3.1: Bugfixes for go-acc matching criteria, attempting to download binary...
Examining release asset gotestfmt_2.3.1_checksums.txt at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.1/gotestfmt_2.3.1_checksums.txt ...
Examining release asset gotestfmt_2.3.1_darwin_amd64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.1/gotestfmt_2.3.1_darwin_amd64.tar.gz ...
Examining release asset gotestfmt_2.3.1_darwin_arm64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.1/gotestfmt_2.3.1_darwin_arm64.tar.gz ...
Examining release asset gotestfmt_2.3.1_linux_[38](https://github.com/norwd/pword/actions/runs/3341225601/jobs/5532217476#step:4:39)6.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.1/gotestfmt_2.3.1_linux_386.tar.gz ...
Examining release asset gotestfmt_2.3.1_linux_amd64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.1/gotestfmt_2.3.1_linux_amd64.tar.gz ...
Examining release asset gotestfmt_2.3.1_linux_arm64.tar.gz at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.1/gotestfmt_2.3.1_linux_arm64.tar.gz ...
Examining release asset gotestfmt_2.3.1_windows_386.zip at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.1/gotestfmt_2.3.1_windows_386.zip ...
Examining release asset gotestfmt_2.3.1_windows_amd64.zip at https://github.com/GoTestTools/gotestfmt/releases/download/v2.3.1/gotestfmt_2.3.1_windows_amd64.zip ...
Binary download failed, tried 4 times, giving up. (No release asset matched postfix '_msys_nt-10.0-203[48](https://github.com/norwd/pword/actions/runs/3341225601/jobs/5532217476#step:4:49)_amd64.tar.gz'.)
Setup failed.
Error: No release asset matched postfix '_msys_nt-10.0-20348_amd64.tar.gz'.
```

I thought this was possibly related to #4, but now my thinking is that there isn't a binary for windows in the latest release of gotestfmt?

Hi @norwd,
a binary for windows is released (see here). So it is related to #4 - there is no support for windows, currently. gotestfmt-action was written for linux and extended to run on mac previously in #5.
To enable windows is a bit more work, and could roughly be done like this:
First, the determineOS function needs to be extended to also identify windows. Then the downloadRelease function would require changes. If os == windows:

use the .zip, not .tar.gz, to get the compressed binary
use windows specific commands to extract the binary and put it into PATH
Do you want to give it a try? :) @norwd

Absolutely!


Create Jira, github sync for SystemDS repo

https://github.com/apache/spark/blob/9eb45ecb4f39f372e20529da468f304c4ec7c175/dev/github_jira_sync.py#L69-L90
https://help.github.com/articles/creating-a-permanent-link-to-a-code-snippet/

https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/configuring-autolinks-to-reference-external-resources


Add auto-created reply queue to SQS transport

See https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-temporary-queues.html

Going to be a massive PITA, so it's going post-1.0. Have to build queues on the fly for each node, tag a heartbeat to know what's idle, have the leader occasionally clean up. Try to delete queues on shutdown.

Duplicate with #994, and I'm just going to roll this over to that


Added method to execute rawsql with params

Added method to execute rawsql with params.
Example: $findAllSql("Call CheckComment(?), [$id]);

I'm not 100% sure this method fits into ActiveRecordModel. So I leave it for now.
I assume it can be implemented as an method within the model-class itself.
Lets leave it as that, for now.


 If you need any information, please revert back.

Environment summary
Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build) / CLI version (az --version) / OS version / Shell Type (e.g. bash, cmd.exe, Bash on Windows)
azure-cli (2.0.31)
MacOs
bash

Very likely it is #6265 .
az account clear doesn't send out any request on the wire; other than remove 2 files.

FYI, there is a workaround suggested by @troydai
 In the meantime, the customer can temporarily stop telemetry to bypass this issue:
https://docs.microsoft.com/en-us/cli/azure/azure-cli-configuration?view=azure-cli-latest#cli-configuration-values-and-environment-variables

     AZURE_CORE_COLLECT_TELEMETRY=False


added OS versions

Description of Changes
Please check that the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] CI passes

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

@asenkowski Going to submit a separate PR to fix the linter issue

@asenkowski Should be good if you rebase or merge in main


distill::create_post("Title of post") produces template with Zoë's details in

Not sure if this is a bug or a feature really but if you run distill::create_post("Title of post") it produces a post template with Zoë's details in (although the "ë" looks like "Ã«")
Is that what we want? Then we can just edit the template to be whoever is doing the post? Just checking 🙃

That's very strange! It doesn't look like my name is in code that can be found through GitHub (looking for just Zo). The article template from nottshcMethods doesn't have a name https://github.com/CDU-data-science-team/nottshcMethods/blob/main/inst/rmarkdown/templates/distill/skeleton/skeleton.Rmd
Should we be using posts or articles? I get confused. Articles can be called using:
distill::create_article("Creating a post - SOP",
                        package = "nottshcMethods",
                        template = "distill")

But what we really need is a post with a subfolder in /_posts/

create_post(author = ) draws from the previous post automatically according to the documentation. I guess this is the difficulty with the blog site, we've been creating posts but the template is an article.


Synthesizer.h (both of them) have unused instance variable

The Synthesizer.h files in nvpsg and nvacq have a member variable called:
int *fliststore;
No code anywhere sets this or uses it. Maybe we can delete it? Or mark it as an orphan?

Dan, I can just comment out these declarations and be done with it. But they are in nvpsg and nvacq directories. Are we in a position where we don't edit the nvacq code? If so we can just close this ticket.


Please Consider Adding Commercié Root CA to Dodo.

Please Consider Adding Commercié Root CA to Dodo.

This is a Private CA. It's a non production Root CA.


Feat/pupil 449/explanatory text pt 2

User Story
As a pupil completing a lesson,
I want to view explanatory text whilst taking quizzes,
So that I can gain useful context about the questions I am about to complete
Implementation details
Example legacy lesson:
https://www.thenational.academy/pupils/lessons/sonnet-18-the-shakespearean-sonnet-68u62d
https://www.figma.com/file/G7z5ufo2T0CHk14CkadeuB/Pupils-high-fidelity-designs?node-id=3034%3A171415&mode=dev
To test

Go to https://deploy-preview-2274--oak-web-application.netlify.thenational.academy/pupils/lessons/sonnet-18-the-shakespearean-sonnet-68u62d
Take the exit quiz
See that the explanatory text is rendered and the lesson counts remain correct

Acceptance criteria

[x]  rendered during quiz
[x]  not included in the question counts during quiz
[x]  ‘completing’ the explanatory text question does not increase the user’s score by 1
[x]  not included in the question counts for overview and review sections

@kimon-satan I can't view the explanatory text when following the test steps.

I suspect you're looking at production not the preview. Sorry I should have put the full URL in the comments. Fixed now. Click on the link in testing.

:tada: This PR is included in version 1.367.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Use a concatenated vendors.js file

Currently we're concatting all of our Gratipay JS but missing out on our 4 vendor files. I created a vendors.js.spt based on gratipay.js.spt. The main difference is it uses a load-order to not upset any dependencies.
I'm welcome to feedback on the code and potentially moving the common code somewhere else?
See: https://github.com/gratipay/gratipay.com/blob/master/www/assets/gratipay.js.spt

Might not be ready, I need Travis for my ttw tests for now

Ready for review!

Alright I refactored some of the shared code out. Ready for review @whit537 @rohitpaulk

Rebased, was 1038573dd86ee0d93ffb44173b8ebea9c18afc19. S'okay @clone1018 @rohitpaulk?

Rebased (was 9cfd2e8dbc057fd956843048c4caf2b9a1f40315) and added 7903d286396843d7f811e6960102d10158165729. S'okay @clone1018 @rohitpaulk?

Hmm ... those pass for me locally. :-/

Something about a discrepancy due to compile_assets?

We do set GRATIPAY_CACHE_STATIC for Travis, but that's also set locally. :thinking:

Rebased, was 2c9bac3fd1e69c6a75c2cffb58ff363b82903389. Travis still gonna fail?

Single test worked!

lol now we're split 50/50 😆

Ah, npm flakerooniness.

Passing! Pushing Makefile changes off and rerunning bb95eb0aa9cca7da3613836dc771504445687ad5. What gives here?

tests/py/test_hooks.py::Tests2::test_caching_of_assets FAILED
tests/py/test_hooks.py::Tests2::test_caching_of_assets_with_etag FAILED

Access-Control-Allow-Origin is supposed to be set in add_caching_to_response. Is that even getting called?

0359f57b36b6dd512de4a94be36aa1179b252a1f
https://travis-ci.org/gratipay/gratipay.com/builds/235758532#L1558-L1570
----------------------------- Captured stdout call -----------------------------
('etag', '')
pid-7006 thread-47656376080768 (MainThread) 200 OK                               /assets/gratipay.js      ./assets/gratipay.js.spt
  X-Xss-Protection                     1; mode=block
  X-Content-Type-Options               nosniff
  Expires                              0
  Content-Security-Policy-Report-Only  default-src 'self';script-src 'self' assets.gratipay.com 'unsafe-inline';style-src 'self' assets.gratipay.com downloads.gratipay.com cloud.typography.com;img-src *;font-src 'self' assets.gratipay.com cloud.typography.com data:;block-all-mixed-content;report-uri https://gratipay.report-uri.io/r/default/csp/reportOnly;
  X-Gratipay-Version                   2084
  Pragma                               no-cache
  Cache-Control                        private, no-cache, no-store, no-transform, must-revalidate, max-age=0
  X-Frame-Options                      SAMEORIGIN
  Referrer-Policy                      no-referrer-when-downgrade, strict-origin-when-cross-origin
  Content-Type                         application/javascript

Huh. No prints whatsonever in 49f50ac3ef47a8fe84a073cfbfb3f73f5d826441 https://travis-ci.org/gratipay/gratipay.com/builds/235762293.

That's really weird because test_caching_of_assets is reaaalllyy supposed to print. 😳  If there are no headers to print then the test should fail in the next line, but it passes.

Okay, phew.

Derrrrrr. stdout now, includes etag (not '')

64931a9a4e7e11c7c04673ea0f8b379c81c52ef3
https://travis-ci.org/gratipay/gratipay.com/builds/235771610#L927-L941
----------------------------- Captured stdout call -----------------------------
('debug path:', u'/home/travis/build/gratipay/gratipay.com/www/assets/gratipay.js')
('debug etag:', 'IFj5JM2uWBFgWKUkTjUOlQ~~')
('debug response.code:', 200)
pid-7351 thread-47578386815360 (MainThread) 200 OK                               /assets/gratipay.js      ./assets/gratipay.js
  X-Xss-Protection                     1; mode=block
  X-Content-Type-Options               nosniff
  Content-Security-Policy-Report-Only  default-src 'self';script-src 'self' assets.gratipay.com 'unsafe-inline';style-src 'self' assets.gratipay.com downloads.gratipay.com cloud.typography.com;img-src *;font-src 'self' assets.gratipay.com cloud.typography.com data:;block-all-mixed-content;report-uri https://gratipay.report-uri.io/r/default/csp/reportOnly;
  X-Gratipay-Version                   2084
  Etag                                 IFj5JM2uWBFgWKUkTjUOlQ~~
  Cache-Control                        public, max-age=5
  Access-Control-Allow-Origin          https://gratipay.com
  Referrer-Policy                      no-referrer-when-downgrade, strict-origin-when-cross-origin
  Content-Type                         application/javascript
  X-Frame-Options                      SAMEORIGIN

Hypothesis: failing case will hit be hitting the .spt instead of the compiled .js.

Yup!

Alright, so we compile sometimes but not others. Do we want to compile?

Happens here.

It's governed by GRATIPAY_CACHE_STATIC, but that should be invariant between working and non-working cases at Travis. Right?

other_stuff gets called during Application instantiation.

Hah! Application is only instantiated under testing when ClientWithAuth is used.

I hypothesize that that's why we're seeing variation on Travis depending on tests run.

Blorg. Naaawwww, because Harness always instantiates a ClientWithAuth.

Can I repro locally somehow?

make test locally with db891e62cdd2ac2edcad37b37c2e667180a49cd4
tests/py/test_hooks.py::Tests2::test_caching_of_assets ('debug path:', u'/Users/whit537/personal/gratipay
/gratipay.com/www/assets/gratipay.js')
('debug etag:', 'dQuS4mE_hAgoeHJmKxTuPA~~')
('debug response.code:', 200)
pid-5822 thread-140735199290112 (MainThread) 200 OK                               /assets/gratipay.js
  ./assets/gratipay.js
  X-Xss-Protection                     1; mode=block
  X-Content-Type-Options               nosniff
  Content-Security-Policy-Report-Only  default-src 'self';script-src 'self' assets.gratipay.com 'unsafe-i
nline';style-src 'self' assets.gratipay.com downloads.gratipay.com cloud.typography.com;img-src *;font-sr
c 'self' assets.gratipay.com cloud.typography.com data:;block-all-mixed-content;report-uri https://gratip
ay.report-uri.io/r/default/csp/reportOnly;
  X-Gratipay-Version                   2084
  Etag                                 dQuS4mE_hAgoeHJmKxTuPA~~
  Cache-Control                        public, max-age=5
  Access-Control-Allow-Origin          https://gratipay.com
  Referrer-Policy                      no-referrer-when-downgrade, strict-origin-when-cross-origin
  Content-Type                         application/javascript
  X-Frame-Options                      SAMEORIGIN
FAILED

Okay so the unwanted failure is failing because there is no cached asset present. Why is there no cached asset present?

cache_static looks false?
https://travis-ci.org/gratipay/gratipay.com/builds/235806471#L1217
https://travis-ci.org/gratipay/gratipay.com/builds/235806471#L1252

Capturing local output to diff.

[gratipay] $ grep 'cache static' log
cache static: True
[gratipay] $

True in test.env. Why not at Travis?

The test process is seeing a yes in test.env but a no in its environment.

Four env files look as expected. Is layering getting screwed up somehow? Is defaults.env clobbering tests/test.env somehow?

Confirmed!
Okay! Why is config coming from defaults.env and not tests/test.env?

That's a honcho thing.

Are we making the right honcho call? Looks like it. Hmm ... :thinking:

Gosh. Are we running the same version of honcho at Travis and locally? 😳

Yes.

Something about cwd when loading envfiles? But it finds defaults.env!

Maybe something about travis caching and old version of honcho? But we've been on this one for so long!

Purged travis cache and restarting ...

I am not seeing the debug line from 60387cea88a5f159c6faec744795a761e962d51e in the output.

Okay! Getting debug prints from inside honcho.

Clooosssseeerrrr

Wait a second ...
https://travis-ci.org/gratipay/gratipay.com/builds/236100061#L2823-L2824 is the one that matters, and it's set! 😱

Alright, wtf. I'm going to roll back the debug commits from 84639551ca0ad1a5158a7cc74643069ceb710d4e and see if it was just a caching issue.

Squashed all of the debug commits into 6eca8e35e2b222ed3422eb4b0a7bd00a13d1226f.

Pushed that off and now 4529d489935f01bd496ce3fef338c76c1ab07537 is rebuilding.

Alright, back to basics. This was working before my commit 4529d489935f01bd496ce3fef338c76c1ab07537, right?

Yes. 4529d489935f01bd496ce3fef338c76c1ab07537 breaks because it tests dynamic asset endpoints instead of static ones, because we moved static ones underneath the dynamic ones.

I am considering changing the test to avoid hitting a dynamic endpoint, but the point of this PR is to no longer have any non-dynamic js files.

Rebased, was 50a5f29d30040a80703854eff6ceb37f74adbe56.

Changes look great to me, merging.

Deploying


Last Week in Pony - August 26, 2018

Audio from the August 22, 2018 Pony Development Sync is now available:
https://pony.groups.io/g/dev/files/Pony Sync/2018_08_22

OpenBSD support was merged to master!


Added Hello World Program in Different Languages

You just need to add 1 languages Hello world program, please change it.

I have deleted all directories except that of python, please review now @PratishShrivastava

Thank you for contributing


💬 RFC: Management of community plugins list on microsite

🔖 Need
Currently, there's not a solution in place for vetting whether or not community plugins have been abandoned, and/or are no longer maintained.
🎉 Proposal
Primary Behavior
My initial proposal is something to the effect of a flag button to the side of each plugin in the list on the microsite that does the following:

Sends an email or notification to the core development team OR opens a GitHub issue
Allows a user to write in a reasoning for the flag press
Ensure the user means to submit the flag

Optional Behavior

Provides a form popover with detailed reasoning
Vets the user somehow (Probably not possible?)

Reference example image

Relevant issue:
https://github.com/backstage/backstage/issues/25715
〽 Alternatives

Explicitly only provide a GitHub issue template for reporting unmaintained/inactive plugins

Downsides:

Users who are new to backstage who go to the landing page and click "plugins" and see a plugin is dead won't know to go to GitHub to report it.

Upsides:

Easiest to implement
Single source of truth & location for reporting issues

Create a backstage-plugins.io microsite that's hosted @ the community plugins repository

Downsides:

Heavy lift
Requires new development
Breaking change for current microsite

Upsides:

Better UX due to repositories linking to their own respective sites
Better separation of concerns
More closely aligns the repositories data with their business context

❌ Risks
As plugin development accelerates, this will scale into an unwieldy list that many people who visit the micro site will see as a graveyard, specifically the plugins page. This will likely cause decrease in conversions when someone visits the backstage website and looks for support for their various technology stacks. It's often the case that users will not adopt software that has no, or unsupported, integrations with whatever technology they are using.
👀 Have you spent some time to check if this RFC has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

@dragonfleas wanted to move this to the community-plugins repo to get some feedback on this from @backstage/community-plugins-maintainers as this applies to both plugins in this repo as well as 3rd party published ones too :pray:

Just wanted to note that the 2nd alternative - "Create a backstage-plugins.io microsite that's hosted @ the community plugins repository" - assumes all the plugins are in the Community Plugins repo this is not correct. Many plugins are hosted by the author, for examples those by Roadie and PagerDuty.

Just wanted to note that the 2nd alternative - "Create a backstage-plugins.io microsite that's hosted @ the community plugins repository" - assumes all the plugins are in the Community Plugins repo this is not correct. Many plugins are hosted by the author, for examples those by Roadie and PagerDuty.

I thought it was implied that this option would come with moving the /data/plugins directory of yaml files there. As well as notifying 3rd party repo managed plugin teams that the location for their plugin grid item had changed. The goal in my mind, was more to consolidate all information in the community-plugins repository, instead of fragmenting it across two repositories. As a new user, my first instinct was to assume that the plugin data for the micro site was sourced from the community plugins repository.

That's fair, I did not infer that these steps were implied. I was just trying to highlight an incorrect assumption and make sure that we consider self hosted plugins as part of this.
I personally like the 2nd alternative as it would open up other possibilities that have been asked for like tagging, better filtering, inline docs, reviews, etc. Trying to have this as part of a Docusaurus site is a bit limiting. BUT we also need to have Contributors who will help make this a reality and keep it maintained and this part has been a bit harder to find.
My personal thoughts on a plan of actions: first we create a GitHub issue template for being able to submit a plugin that's no longer maintained and this can be just linked in the header section of the Plugin Directory. If someone wants to add a button on each card that would link you to the template even better. From there anyone who's motivated can work on something better as proposed in the 2nd alternative.

Hey! 👋
Nice! I think also key here is what do we consider to be "no longer maintained" could it be "no updates after X period of time?"
I also think we could host something in terms of a plugins page from community-repo as mentioned and I think it would tie in well with a docs site for the plugins which I believe @BethGriggs mentioned in the discord not long ago!
👏

I can say for certain, "Company who maintained the plugin and the platform it integrates with no longer existing" as being representative of at least one criteria, in the case of the plugin in the linked issue. 😛


On Android, appendExt is not being added to the localPath

Here is my code:
export function downloadFile(file, url, contentType, size) {
  return (dispatch, getState) => {
    return RNFetchBlob
      .config({
        session: SESSION_NAME,
        fileCache: true,
        appendExt: 'mp4'
      })
      .fetch('GET', url)
      .then(res =>
        dispatch(addFile(file, res.path(), contentType, size)))
  }
}

The resulting file path on Android is: /data/user/0/com.stitchapp/files/RNFetchBlobTmp_faadb355-e693-45ef-aa6e-f5d18926bfc2.
Notice that .mp4 is missing. This issue does not occur on iOS.

@shilpan , thanks for reporting this issue. I've noticed this problem days ago, I'll publish a beta release contains the fix 😄

I'll be waiting :) it causes an issue when downloading a file locally and  trying to run it with react-native-video

@shilpan , the fix is included in 0.10.0-beta.5 please upgrade the package and verify if it's fixed, thank you 👍

@wkh237  Still not work on 0.10.0-beta.5

@Timehello , is it happenns on Android or IOS ?

@wkh237  Android, ios is ok

works on 0.10.0-beta.6

yes, it works on beta6 !


creation and update times of elements

Tasks
To have some auditability, we want:

[ ] creation time (granularity in seconds)
[ ] creation id (person who created)
[ ] modification time (granularity in seconds)
[ ] modification id (person who modified)

Use cases
All layers that have elements, currently:

[ ] for plants see #476
[ ] for drawing layer see #1165

Furthermore, also following should

[ ] map(s) should have above attributes, to be seen in the map list

Not needed:

seeds are currently private without collaboration

A few comments from @chr-schr and me:

We suggest that modification_time and creation_time are non-null and are the same as creation when a new plant is placed on the map (like in Windows).

For initial values in the migration we propose:

map.owner_id for planting.creation_ids and planting.modification_ids
map.creation_date for planting.creation_time and planting.modification_id

1-3: fantastic suggestions, I agree to all of them.

no, creator=owner, we need to introduce one term in the glossary and should consistently use that term. Changing to which term is less work?

@markus2330 When should map.modified_by and modified_at change? Whenever any api on the map changed something, right? So when we CUD new planting the map should update map.modified_by and modified_at, change the drawing etc...

Exactly, so some guard needs to be added in every modifying operation. Especially the map date modified date gets modified virtually everywhere a write operation happens.


Papersscissors.rock

Solved #136 . Added https://papersscissors.rocks as a PWA. Modified Spock.png to Spock.svg as suggested by @andreasbovens and updated the CSS for it.

Send me an email please<EMAIL_ADDRESS>


Rejection of invalid layouts.

In #1308 there was a conversation about the policy for accepting redundant (unsimplified) layouts. There have been at least two cases (#713, #1308 discussion) where non-simplified layouts produce strange results when passed to high level functions, and until now I've raised these as bugs.
After the discussion with @jpivarski in #1308 I've realised that this is a policy issue, as Awkward functions themselves do/should not produce such layouts. Accepting redundant layouts is transparent in some functions (like ak.unflatten), but not those where the high-level function needs to match a particular layout structure. Such functions are made far simpler by the requirement of simplified layouts.
The take-away is:

Awkward should not produce non-simplified Arrays
Users of the mid-layer should check that they don't produce non-simplified Arrays

To support external users of the mid layer, I think it would be helpful to catch cases where this invariant fails; bugs in the Awkward code-base will more easily found than those in external users' code (because we will have a greater number of users overall).

We discussed the idea of a per-layout flag that determines whether a layout is in its simplest form. This would add a reasonable amount of code to check something that internally should never happen.
A less robust approach would be to tackle #516 at the same time and create a mid-level API that resembles ak._util, e.g.
def wrap(layout, behavior):
    assert_simplified(layout)
    return ak._v2._util.wrap(layout, behavior)

...

The issue with this approach is that it only checks for validity at wrap time, and doesn't remember layouts it has visited before. Users that pass a layout to ak.XXX functions with highlevel=True would then receive Arrays that have not been checked.
The more I think about it, the less confident I am that we want to go to all this trouble. We don't enforce check_valid by default, and that is the same class of error. Maybe we should include a simplification check when check_valid is set to True, and call it a day. Perhaps this is just a documentation problem?
I appreciate that I've gone round in a few circles here, thanks for coming for the ride!

The more I think about it, the less confident I am that we want to go to all this trouble. We don't enforce check_valid by default, and that is the same class of error. Maybe we should include a simplification check when check_valid is set to True, and call it a day.

At least in the two Content subclasses I checked yesterday, the check_valid implementation also checks for this redundancy. So if a user is concerned about the validity of a layout, this option will fix it.
All in all, there are three ways for a layout to be invalid:

Invalid metadata: property types, property value ranges—any state depending on the Content instance itself that is not in any arrays (Indexes or NumpyArray data). Examples: BitMaskedArray lsb_order must be boolean; RegularArray size must be non-negative.
Invalid data: values in Indexes that are out of range, inconsistent with each other, or inconsistent with len(content). Examples: IndexedArray index with values that are negative or greater than or equal to len(content); ListArray stops[i] < starts[i].
Invalid nesting: any two directly nested {IndexedArray, IndexedOptionArray, ByteMaskedArray, BitMaskedArray, UnmaskedArray} or directly nested UnionArray or a UnionArray containing mergeable contents.

All of this discussion is about (3), which could be caught in O(1) time with O(n) flags where n is the number of nodes in a tree (not very large).
However, just as a mid-level user (someone going into the ak.layout.* module) can make a layout that is invalid in way (3), they can make a layout that is invalid in way (2). Making an ak.Array with check_valid=True checks for types (2) and (3) errors. This is opt-in because checking for type (2) is O(N) where N is the number of elements in the array (more expensive).
Type (1) errors are always checked by Content subclass constructors, so it's never possible to make one without knowing about the error. This checking is O(1) in time and memory use.
So it comes down to how much we care about this: we'd be able to check for type (3) errors without requiring user opt-in at the cost of adding O(n) flags (not a big cost). But the layouts could still have type (2) errors. The current policy is that if an operation relies on some type (2) error not being wrong, it has to check for those errors just before using them: for example, checking stops[i] >= starts[i] inside a kernel just before using starts[i] or stops[i], and it should check for a type (3) error just before using it, too. For instance, if an operation needs to assume that two option-type nodes are not nested, it can do the O(1) check for the content directly inside the option-type node in question and raise an error if it is. It does not need to "deal" with it as though it were a valid state.
This PR is about a change in policy to detect type (3) errors more proactively: to raise an error when constructing the ak.Array in a way that users don't have to opt into, because the cost is small and there may be erroneous cases in the wild. There's a positive value to that—it would be better to have this than not have this—but I don't see it as a high priority. If you have other, more pressing items, I'd put this on pause in favor of those.

At least in the two Content subclasses I checked yesterday, the check_valid implementation also checks for this redundancy. So if a user is concerned about the validity of a layout, this option will fix it.

(:facepalm:)∞
You're completely right. I don't know what I was looking at yesterday.
Yes, this issue is about if/when to check (3). The easiest solution is to check this when constructing Array vs doing this in the layout constructor. Whilst users could then have erroneous layouts, they will nearly always end up converting them to Array at some point and then discover the error.
So, this is a wishlist item for when we get around to splitting the structure checking into its own routine.

I think @jpivarski work means that we can close this! We now have an explicit separation between simplified and __init__ that signals intent, and most checks are lightweight.


Make "cssmin" optional for style blocks

Some Context
When specifying animation keyframes to the style block, cssmin appears to destroy the definition of those animations!
Example SVG
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 155 172">
    <defs>
        <style>
            @keyframes spin {
                0% {
                    transform:rotate(0deg);
                }

                100% {
                    transform:rotate(180deg);
                }
            }

            @keyframes dashHide {
                0% {
                    clip-path: circle(35% at 50% 60%);
                }

                100% {
                    clip-path: circle(75%);
                }
            }
        </style>
    </defs>
</svg>

Resulting style block after cssminification
@keyframes spin{0%{transform:rotate(0deg)}to{transform:rotat{transform:rotate(180deg)}}@keyframes dashHide{0%{clip-path:circle(35%}@keyframes dashHide{0%{clip-path:circle(35% at 50% 60%)}to{clip-path:circle(75%)}}{clip-path:circle(75%)}}}

It should, in this single-line form, look like this:
@keyframes spin{0%{transform:rotate(0deg)}to{transform:rotate(180deg)}}@keyframes dashHide{0%{clip-path:circle(35% at 50% 60%)}to{clip-path:circle(75%)}}

My Modest Proposal
Make the usage of cssmin optional! It seems svgo does a pretty good job cleaning up all my whitespace in this style block, and I'd like to remove this functionality seeing as I personally have no use for it and would like to preserve these animations.
I'm happy to make a pull-request adding an option passed via the config to disable, if that would be welcome!

Worth sharing, this is the problematic line in question: https://github.com/jkphl/svg-sprite/blob/master/lib/svg-sprite/shape.js#L728

An option wouldn't hurt, but IMHO cssmin should be replaced with something more maintained and better tested.
svgo itself is using ccso. Personally, I use clean-css but it would probably make more sense to use one of the dependencies that are in the deps tree.

I made #402, currently WIP, but csso is much better maintained and should fix your problem.
That being said, after the above lands, feel free to submit a PR making this configurable allowing enabling/disabling and/or passing custom options.


Unlock buttons "Deploy" and "Edit" on the models screen

Unlock buttons "Deploy" and "Edit" on the models screen

The buttons are not disabled, they have no logic - if you click on them, no function will be called.
It is necessary to describe the scenario and the logic that needs to be implemented by clicking on each of the buttons

For deploy use /api/v1/models/docs#/models/deploy_model_models_deploy_post
For edit use /api/v1/models/docs#/models/update_model_models_update_put
For delete (it is also needed) use /api/v1/models/docs#/models/delete_model_by_id_models_delete_delete
Necessary fields are listed under the buttons

Verified


Update organize-imports to 0.4.3

Updates com.github.liancheng:organize-imports from 0.4.0 to 0.4.3.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.liancheng", artifactId = "organize-imports" } ]

labels: scalafix-rule-update, semver-patch

Codecov Report

Merging #2 (fb1af8d) into develop (10f10f3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop       #2   +/-   ##
========================================
  Coverage    75.00%   75.00%
========================================
  Files            3        3
  Lines           36       36
========================================
  Hits            27       27
  Misses           9        9

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 10f10f3...fb1af8d. Read the comment docs.


Add BoundsClassifier

Coverage remained the same at 94.032% when pulling 6c5d6e48405a02b0651647bf8d84c290050ca2fc on bounds into aa5e837276a9e3f5fe236446b05aca4be325b426 on master.

Coverage remained the same at 94.032% when pulling 853c86c1cc736375b0ff61c6b6e50c202e1d947b on bounds into aa5e837276a9e3f5fe236446b05aca4be325b426 on master.

Coverage remained the same at 94.032% when pulling 86570630c26db7cc8a7c5cad47d258c5c2bd9728 on bounds into aa5e837276a9e3f5fe236446b05aca4be325b426 on master.


Tests fails on builds with disabled terminal feature

Steps to reproduce

disable the terminal feature (./configure --enable-terminal=no)
make
make test

Expected behaviour
An execution of make test will also run the syntaxtests. Since the syntaxtest seems to require the terminal feature to be enabled, these tests will report an error if this feature is disabled.
Would it make sense to skip those tests if the terminal flag is disabled, rather than showing an error?
Version of Vim
9.0.1901
Environment
OS: Gentoo
Terminal: st
TERM=xtern (set for the tests)
Shell: dash
Logs and stack traces
This will be shown after executing the tests:

...
".../vim-9.0.1901/runtime/syntax/testdir/messages" [New File]
".../vim-9.0.1901/runtime/syntax/testdir/messages" ".../vim-9.0.1901/runtime/syntax/testdir/messages" [New File] 4 lines, 176 bytes written
Error detected while processing .../vim-normal/vim-9.0.1901/runtime/syntax/testdir/runtest.vim[64]..function Fatal:
line    1:
Cannot make screendumps, aborting
"testdir/messages" 4 lines, 176 bytes

"testdir/messages" "testdir/messages" 6 lines, 211 bytes written
...

syntax tests require the screendump feature, which requires the terminal. As far as I can see, this is not an error so everything is fine.

Maybe I get this wrong, but if I disable the terminal feature these tests cannot work right?
Since these tests are executed on a normal make test, it will fail.
Is this expected and I rather should skip these tests when the terminal feature is disabled?

yes, this is required. But it doesn't fail. It just outputs that the screendump feature is required. But Make should succeed.

Yes, you right! Sorry mz fault!I just mislead myself a bit, regarding the fatal message!
Now I got it! Thanks and sorry for the noise!


Bump typedoc to 0.20.36, update package-lock.json

Makes npm stop complaining about vulnerabilities.

Coverage remained the same at 95.019% when pulling 0b600e578270337ed058fce86f43191dbdcd5388 on ehm-93:npm-audit-fix into bf3b07d7c81f9e159d239f414c2e347d71d01695 on vpulim:master.


Add support for arm_tizen

Tizen is a Linux flavour, where the difference is only in
float-abi-softfb flag and using gnueabi not gnueabihf toolchain.
To build this change run:
TUV_PLATFORM=arm-tizen TUV_BOARD=artik10 make
The tuvtester was executed on Tizen board with 100% pass rate.
libtuv-DCO-1.0-Signed-off-by: Konrad Lipner<EMAIL_ADDRESS>

@kolipka Hello, this PR looks ok, but you can make changes(ex. makes two commits to one commit) without closing previous PR.

LGTM


[Feature] Implement Selective Commit Merging Option

Currently, when the pull bot creating a Pull Request, all commits associated with the branch are automatically included for merging. However, it would greatly enhance user flexibility and efficiency if there was an option to selectively choose which commits to merge into the target branch.
Proposed Solution:
Introducing a feature where users can toggle/select specific commits within the Pull Request interface would provide greater control over the merging process. This option could streamline the code, especially in cases where certain commits are ready for merging while others require further refinement or testing.
Benefits:

Allows for more granular control over the merging process.
Facilitates easier identification and selection of relevant commits.
Enhances collaboration by enabling contributors to focus on specific changes within a Pull Request.

Hi @atheo89 thanks for the suggestion. I believe what you are proposing is actually against the best git practice for a software development process. I recommend working on different branches instead of picking commits this way. I can foresee issues of merge conflicts and unstable main branch from cherry-picking commits this way. Additionally, since Pull uses GitHub's REST API, I don't think cherry-picking is natively supported. I recommend using git cherry-pick instead for your given workflow.


SPARK-4660: Use correct default classloader in JavaSerializer.

QA tests have finished for   PR 3840 at commit 86bc5eb.

This patch fails unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25059/
Test FAILed.

Jenkins, test this please.

QA tests have started for   PR 3840 at commit 86bc5eb.

This patch merges cleanly.

QA tests have finished for   PR 3840 at commit 86bc5eb.

This patch fails unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25205/
Test FAILed.

This seems to be failing from a known python imports issue in branch-1.1 not related to this patch.

@pkolaczk can you make a version of this pull request against the master branch?

Yes, I can.

@pkolaczk - any luck with the master PR

@pwendell here are pull requests for 1.2 and master branches respectively:
https://github.com/apache/spark/pull/4114
https://github.com/apache/spark/pull/4113
@pkolaczk is on vacation so he asked me to prepare these PRs

Okay I've merged this into all the relevant branches. Can you close this issue?

I cannot, @pkolaczk can do this


refactor(palette): removing text v2

The type of this PR is: Enhancement

This PR resolves []
Description

PR Checklist (tick all before merging)

[ ] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have tested my changes on iOS and Android.
[ ] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[ ] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added an app state migration, or my changes do not require one. (What are migrations?)
[ ] I have added a changelog entry below or my changes do not require one.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

removing a bunch of palette v2 code - pavlos

This PR contains the following changes:

Dev changes (removing a bunch of palette v2 code - pavlos)

  Generated by :no_entry_sign: dangerJS against 96afc474be8ee55b1d5166fe860621338e52d0ee


Log collector keeps test runner from closing if this.skip() is used

Describe the bug
In a Mocha-based testing environment, using Mocha's this.skip() (i.e. command for skipping tests at run-time) holds the test runner back from shutting down, if log collection has been enabled (e.g. if the --record-logs all cli option has been specified).
To Reproduce

[x] I have tested this issue on the latest Detox release and it still reproduces

Create a suite with at least one test that at some point aborts itself using this.skip().
Run the suite on a device (iOS / Android) using Mocha as the underlying test runner. Pass in --record-logs all as one of the cli options to detox.

Upon completion, the test runner will show the summary and will hang forever (i.e. process will not quit).

Environment (please complete the following information):

Detox: 12.10.2
React Native: 0.56.0
Node: 10.15.3
Device: Pixel_API_26
Xcode: -
iOS: -
macOS: Mojave 10.14.3

Device and Verbose Detox Logs
From running Detox' own waitFor suite (over the main test app), with this.skip() integrated into the 2nd test:
detox[62793] INFO:  [DetoxServer.js] server listening on localhost:51203...
  WaitFor
    ✓ should wait until an element is created and exists in layout (2145ms)
    - should find element by scrolling until it is visible
    ✓ should wait until an element is removed (20452ms)

  2 passing (35s)
  1 pending

^ Runner hangs forever and never quits.
Post-invoking why-is-node-running gives these main results:
# PROCESSWRAP
/Users/amitd/dev/Detox/detox/node_modules/cross-spawn/index.js:17                - spawned = cp.spawn(parsed.command, parsed.args, parsed.options);
/Users/amitd/dev/Detox/detox/node_modules/child-process-promise/lib/index.js:90  - cp = method(command, args, options);
/Users/amitd/dev/Detox/detox/node_modules/child-process-promise/lib/index.js:155 - return doSpawn(crossSpawn, command, args, options);
/Users/amitd/dev/Detox/detox/src/utils/exec.js:5                                 - const { escape } = require('./pipeCommands');
/Users/amitd/dev/Detox/detox/src/devices/android/ADB.js:10                       - constructor() {
/Users/amitd/dev/Detox/detox/src/devices/android/ADB.js:8                        -
/Users/amitd/dev/Detox/detox/src/artifacts/log/android/ADBLogcatRecording.js:2   - const DetoxRuntimeError = require('../../../errors/DetoxRuntimeError');

# PIPEWRAP
/Users/amitd/dev/Detox/detox/test/node_modules/spawn-wrap/index.js:91            - return fn.call(this, options)
/Users/amitd/dev/Detox/detox/node_modules/cross-spawn/index.js:17                - spawned = cp.spawn(parsed.command, parsed.args, parsed.options);
/Users/amitd/dev/Detox/detox/node_modules/child-process-promise/lib/index.js:90  - cp = method(command, args, options);
/Users/amitd/dev/Detox/detox/node_modules/child-process-promise/lib/index.js:155 - return doSpawn(crossSpawn, command, args, options);
/Users/amitd/dev/Detox/detox/src/utils/exec.js:5                                 - const { escape } = require('./pipeCommands');
/Users/amitd/dev/Detox/detox/src/devices/android/ADB.js:10                       - constructor() {
/Users/amitd/dev/Detox/detox/src/devices/android/ADB.js:8                        -
/Users/amitd/dev/Detox/detox/src/artifacts/log/android/ADBLogcatRecording.js:2   - const DetoxRuntimeError = require('../../../errors/DetoxRuntimeError');

# PIPEWRAP
/Users/amitd/dev/Detox/detox/test/node_modules/spawn-wrap/index.js:91            - return fn.call(this, options)
/Users/amitd/dev/Detox/detox/node_modules/cross-spawn/index.js:17                - spawned = cp.spawn(parsed.command, parsed.args, parsed.options);
/Users/amitd/dev/Detox/detox/node_modules/child-process-promise/lib/index.js:90  - cp = method(command, args, options);
/Users/amitd/dev/Detox/detox/node_modules/child-process-promise/lib/index.js:155 - return doSpawn(crossSpawn, command, args, options);
/Users/amitd/dev/Detox/detox/src/utils/exec.js:5                                 - const { escape } = require('./pipeCommands');
/Users/amitd/dev/Detox/detox/src/devices/android/ADB.js:10                       - constructor() {
/Users/amitd/dev/Detox/detox/src/devices/android/ADB.js:8                        -
/Users/amitd/dev/Detox/detox/src/artifacts/log/android/ADBLogcatRecording.js:2   - const DetoxRuntimeError = require('../../../errors/DetoxRuntimeError');

A partial yet deeper inspection shows that when skipping tests dynamically, Mocha invokes before and beforeEach callbacks but not any of the after and afterEach ones. This mainly keeps the Detox adapter from ever shutting registered recorders down. Illustrative log:
  WaitFor
BEFORE
    ✓ should wait until an element is created and exists in layout (2145ms)
AFTER
BEFORE
    - should find element by scrolling until it is visible
BEFORE
    ✓ should wait until an element is removed (20452ms)
AFTER

  2 passing (35s)
  1 pending

Well, we can close this since Mocha won't be supported officially by us since Detox 20.


ARROW-3173: [Rust] dynamic_types example does not run

Can't while at the office but will do this weekend, thanks @kszucs.

@kszucs since you're a committer now you should be able to rebase and force push this branch yourself

@sbinet is this a new issue?

Sorry, where is Go failing?
The Travis CI is green :)

That's bizarre, yesterday there were Go failures.  It was the go get -t -v ./.. that was failing I believe, it mentioned something about a path issue with /math.  Sorry if that's vague I can't quite remember and I'm unfamiliar with Go.  @wesm did you see the failure also?
In any case, I guess it's all good now.

I restarted the build, so I guess the failure was transient

Ah, makes sense then, thanks @wesm


manage: Remove timeout in the time consuming engine command

Backup, restore, backup remove, rebuild, snapshot purge shouldn't have a timeout in the manager.

Timeout for backup deletion removed by https://github.com/longhorn/longhorn-manager/pull/357

Wait for https://github.com/longhorn/longhorn/issues/644

@meldafrawi Old timeouts:

Purge (snapshot deletion): 15 minutes
Backup: 6 hours.
Rebuild: 3 hours.
Restoration: No limit, make sure it stays that way.

Best way to simulate purge is to create a few big snapshots, then use Longhorn command line to mark the snapshot as removed, then create a new snapshot in the UI, then delete it. The last step will trigger snapshot purge in Longhorn manager.

Validation: WIP
Steps to test:
(1) backup

In Settings page, make sure that backup target is correctly configured.
Create a volume with large size ~ 200 GB, attach it to a node, format it, mount it to a directory on attached node.
Write a large data file that consumes all/most of volume size ~198 GB
In Volume Details page, create a backup.

Expected result: backup expected to take more than 6 hours (old backup timeout), and should continue progressing after that.


Dynamic frequency connectivity measures

Currently mne support for static connectivity measures via spectral_connectivity. But I notice there is no direct module for Dynamic frequency connectivity measures (Please correct just in case I miss about the existence of such module).
One approach that I can think in order to achieve this is simply by looping the spectral_connectivity over the desired time span.. Say for example, the sliding window is of 2sec width, the code below perhaps can do the task.

import mne
from mne import io
from mne.connectivity import spectral_connectivity
from mne.datasets import sample

data_path = sample.data_path()
raw_fname = data_path + '/MEG/sample/sample_audvis_filt-0-40_raw.fif'
event_fname = data_path + '/MEG/sample/sample_audvis_filt-0-40_raw-eve.fif'
raw = io.read_raw_fif(raw_fname)
events = mne.read_events(event_fname)
ch_names = raw.info['ch_names']
picks = mne.pick_channels(ch_names=ch_names,include=['EEG 001','EEG 002','EEG 003'])
event_id, tmin, tmax = 1, -10, 0
epochs = mne.Epochs(raw, events, event_id, tmin, tmax, picks=picks)
fmin, fmax = 11.,16.
sfreq = raw.info['sfreq']  # the sampling frequency
tmin = 0  # exclude the baseline period
tmax=2
window_time=[-10,-8,-6,-4,-2]

epochs.load_data()
pli_list=[]
for i in window_time:
    epochs_win = epochs.copy ().crop ( tmin=i, tmax=i+2, include_tmax=True )
    con, freqs, times, n_epochs, n_tapers = spectral_connectivity(
        epochs_win, method='pli', mode='multitaper', sfreq=sfreq, fmin=fmin, fmax=fmax,
        faverage=True,mt_adaptive=False, n_jobs=1)
    pli_list.append(con)

But Im curious whether there are mne ways that is much more efficient than the above proposed code, or even better if there is specific mne module that I might be miss out during my search?

Looks like this is the same as #8729 so I'll close this one


FSL : add a file to describe functions and get entities / remove extra activities and derivedFrom / comment attributes / ignore Feat main script

This PR proposes improvements to the FSL parser:

Adding a description file for FSL commands (called description_functions.json). This file is used to retrieve the "used" and "generatedBy" entities.
Example:

[
  {
    "name": "fsl_tsplot",
    "used": ["-i"],
    "generatedBy": ["-o"]
  },
  {
    "name": "cluster",
    "used": ["-i", "-c"],
    "generatedBy": ["-o", "--othresh", "--olmax", -1]
  },
  {
    "name": "cp",
    "used": [1],
    "generatedBy": [2]
  }
  {
    "name": "crtashf",
    "used": [1, "-i"],
    "generatedBy": [2, "--output"]
  },
  {
    "name": "rm",
    "used": ["1:"]
  },
  {
    "name": "mv",
    "used": ["1:-1"],
    "generatedBy": [-1]
  },
  {
    "name": "pngappend",
    "used": ["1:-1"],
    "generatedBy": [-1]
  }
]

It allows entities to be specified by index (e.g. 1 or -1 for the last element), by parameter name (e.g. --output) and by slicing (e.g. 1:-1).
The script also adapts for commands like rm to the presence or absence of a parameter following it. Example rm -f sl?.png highres2standard2.png with the previous json description will retrieve in used: sl?.png and highres2standard2.png. If the command would have been simply rm -f sl?.png highres2standard2.png , the result would have been the same.
Note : this description file has been initialized but is incomplete and some commands are certainly wrong.

Extra activities indicated by wasInfluencedBy have been removed
derivedFrom has also been removed
The attributes of the activities have been commented on as they are not reliable at the moment.
The parser now ignores the Feat main script section.

Thank you @thomasbtnfr! This looks good to me, let's merge!


1.3 Update CLI reference page in docs

Docs need to reflect CLI changes in 1.3.

CLI reference
examples on other pages

@jrcheli
Typo in the actual help:
scope completion bash > /etc/bash_completion.d/scope # Generates and install scope autocompletion for bash
source <(scope completion bash)                      # Generates and load scope autocompletion for bash

In both cases, it should say Generate not Generates.

Notes for review

Wondering whether this works with flags:
scope help [subcommand] [flags]

How should we notate ID arguments? see scope events and scope extract

For scope inspect, what exactly does this mean?
  -p, --prefix string   Prefix to /proc filesystem

What does the last  or  sessions mean?
  -a, --all          Delete all sessions
  -d, --delete int   Delete last <delete> sessions
  -f, --force        Do not prompt for confirmation
  -h, --help         Help for prune
  -k, --keep int     Keep last <keep> sessions, delete all others

ps
need to compare actual help output with docs

not sure we want usage to mention flags if the only flag is help; not sure we want to give an example either if that's the only flag

scope start
Actual help output could benefit from refinements in the docs.

scope stop
Stop scoping all processes and services on the host and in all relevant containers.
What does the last sentence mean?
`scope stop` does the following on the host and in all relevant containers:
  - Remove filter files `/usr/lib/appscope/scope_filter` and `/tmp/appscope/scope_filter`.
	- Detach from all existing scoped processes.
	- Remove the `etc/profile.d/scope.sh` script.
	- Update the relevant service configurations to not `LD_PRELOAD` libscope if already doing so.

style point: /proc rather than proc ... I think

Closing, since we've made this a task in the epic https://github.com/criblio/appscope/issues/1352


Get property by name from schema

Add an ability to get property definition from schema value

Closing de to typing issues.


How to connect to Database robotframework-selenium2library-java

Do we have any keyword to connect to database using robotframework-selenium2library-java. if we dont have any keywork.Please help me to create keyword for database connecttion. please share the example if you have any such.

There are several database libraries for robotframework.
Why add it here??

Am 22.06.2015 um 22:13 schrieb sunil31925<EMAIL_ADDRESS>Do we have any keyword to connect to database using robotframework-selenium2library-java. if we dont have any keywork.Please help me to create keyword for database connecttion. please share the example if you have any such.
—
Reply to this email directly or view it on GitHub https://github.com/MarkusBernhardt/robotframework-selenium2library-java/issues/70.


Unable to see messages or notifications count without the ability to style badges

Description of bug
Unable to see the number of items for messages and notifications in the account header area.
Steps to reproduce
List the steps to reproduce the behavior:

Log into DNN CE site with an account that has messages or notifications
In the header area where the account skin object shows the notifications and messages icons the number of items in each category are very hard to see or make out what the number is and I do not see or know of any way to style the objects.

Current result
Unable to clearly see the total number of messages/notifications
Expected result
Ability to view the number of unchecked messages/notifications in a skin object.
Affected version

[x] 9.3.0
[x] 9.2.2
[x] 9.2.1
[x] 9.2
[x] 9.1.1
[ ] 9.1
[ ] 9.0

Affected browser

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Internet Explorer
[ ] Edge

I agree, the default skin should be improved for this, anything more than 1 digit gets over the icon, the font is also a bit small:


Incorrect reference to org.pmw.runtime in export-package

I'm running into an issue using TinyLog >= 1.1 in OSGI container (1.0.2 works fine), and it seems to be a packaging issue, for example:
org.osgi.framework.BundleException: Unresolved constraint in bundle cv.lecturesight.util [19]: Unable to resolve 19.0: missing requirement [19.0] osgi.wiring.package; (osgi.wiring.package=org.pmw.tinylog.runtime)

It looks like the export-package definition here may be wrong:
https://github.com/pmwmedia/tinylog/blob/v1.3/tinylog/pom.xml#L130
<Export-Package>org.pmw.tinylog, org.pmw.runtime,
  org.pmw.tinylog.labelers, org.pmw.tinylog.policies,
  org.pmw.tinylog.writers</Export-Package>

as it refers to org.pmw.runtime instead of org.pmw.tinylog.runtime ?

It looks like the tinylog MANIFEST.MF also needs to include:
Import-Package: javax.naming
before this all works properly for me.

Yes, you are right. It should be org.pmw.tinylog.runtime instead of org.pmw.runtime. I have fixed it in commit 3cfa38417d2858014acf06c4bb71508118ce776b.
Why should Import-Package: javax.naming be required? This package is part of the Java runtime environment.

Thanks for the quick fix!
I got this error (having first edited MANIFEST.MF manually to change org.pmw.runtime to org.pmw.tinylog.runtime):
g! ERROR: lecturesight-framesource-videofile (25): [lecturesight.framesource.videofile] The activate method has thrown an exception
java.lang.NoClassDefFoundError: javax/naming/NamingException
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:264)
	at org.pmw.tinylog.PropertiesLoader.findImplementations(Unknown Source)
	at org.pmw.tinylog.PropertiesLoader.readWriter(Unknown Source)
	at org.pmw.tinylog.PropertiesLoader.readWriters(Unknown Source)
	at org.pmw.tinylog.PropertiesLoader.readProperties(Unknown Source)
	at org.pmw.tinylog.Configurator.init(Unknown Source)
	at org.pmw.tinylog.Logger.<clinit>(Unknown Source)
	at cv.lecturesight.framesource.videofile.VideoFileFrameSourceFactory.activate(VideoFileFrameSourceFactory.java:51)

so I followed the suggestions from this similar question:
https://stackoverflow.com/questions/15239943/getting-java-lang-noclassdeffounderror-javax-naming-namingexception-error-when
and that made everything work. I'm afraid my OSGI skills are not quite up to telling whether it's TinyLog that should have the import-package, or whether it's some other config issue in the project or other bundles that's causing the NoClassDefFoundError.
The project is here:
https://bitbucket.org/cilt/lecturesight/src/a8652a0ce18682860120a0851163293be08cc500/runtime/bundles/system/?at=t/LS-225-calibration
Tinylog 1.0.2 worked fine.

I have fixed the reported issues and some others that I found while testing the bundles with felix.
@smarquard Could you verify that the bundles are working on your OSGi environment? Afterwards I will release the fixes as version 1.3.2.
Bundles:
jcl-binding-1.3.2.zip
log4j-facade-1.3.2.zip
slf4j-binding-1.3.2.zip
tinylog-1.3.2.zip
tinylog-jboss-1.3.2.zip
tinylog-jul-1.3.2.zip

Thank you! I've tested tinylog-1.3.2.jar and it works fine.


V8.0.3 FAQ - Delete Entry breaks the Save button

http://puu.sh/sU7cc/2c768ff818.png
When adding FAQ items everything goes fine. But when I decide to Delete Entry, I cannot save the edit anymore. Clicking on the Save button has no effect.

I can confirm this.
I believe it is related to this: https://github.com/concrete5/concrete5/pull/4482


Request to set a prior on Tc for a known monotransit planet of unknown period

At present the use of a prior on orbital phase derived from the time of conjunction,Tc,
requires the orbital period to be specified as a parameter of make_prior<Gaussian_from_Tc>
In the case of a known monotransit planet it would be very useful if users could set a prior on the
time of conjunction Tc (say KO_Tcprior) while allowing an uninformative prior on the orbital period, as an
alternative to setting a prior on the mean anomaly at the time of the first observation. For any
individual sample, phi could then be calculated from the current samples of P, Tc, e and omega.

Hi João
That would be great! Let me know if you need a beta-testing volunteer when you
get around to implementing it.
Cheers
Andrew

On 6 Dec 2023, at 10:52, João Faria @.***> wrote:
Hi Andrew!
Indeed, this would be quite useful. I'm thinking of creating a transiting_planet akin to the known_object but which is parameterised directly with Tc instead of the mean anomaly phi. This would then work for mono/duo/multi transits in general.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.>
[ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/j-faria/kima/issues/80#issuecomment-1842635680", "url": "https://github.com/j-faria/kima/issues/80#issuecomment-1842635680", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

%  -----------------------------------------------------------------------
%  Andrew Collier CAMERON, FRSE
%  Professor of Astronomy
%  Centre for Exoplanet Science / SUPA, School of Physics & Astronomy
%  University of St Andrews, North Haugh ST ANDREWS, Fife, KY16 9SS
%  Tel: +44-1334-463147
%  Fax: +44-1334-463104
%  @.***
%  http://star-www.st-and.ac.uk/~acc4/
% The University of St Andrews is a charity registered in Scotland :
% No SC013532
%
———————————————————————————————————

Yes, I could really use the Tc prior capability too for mono/duo transit work.

Hi @accameron, @karenacollins,
The ability to set a prior for $T_c$ is now implemented in the new version of kima that can be found here. There is also a worked through example in the documentation.
I will close this issue for now, but please let me know if you run into any issues with the new version.

Thank you!


Add flag to create IPv6 DNS records which map to the IPv4 address

install-yamls-crc-podified-edpm-baremetal is currently broken with ansible halting on a name resolution failure[1].
The dnsmasq log[1] shows the v4 A record resolves, but the v6 AAAA lookup is delegated to <IP_ADDRESS> which returns NODATA-IPv6, which is what halts ansible execution.
We would need to document this flag to be set in IPv4 only environments.
Other options worth considering for this issue:

Modify the dnsmasq controller to allow setting the --filter-AAAA flag[3] in IPv4 only environments
Modify the ansibleee image to configure ssh with the "-4" flag to avoid attempting IPv6 (I attempted doing this by setting dataplane env ANSIBLE_SSH_COMMON_ARGS or ansibleVars ansible_ssh_common_args but it didn't change the behaviour.

[1] https://logserver.rdoproject.org/60/460/210937ab2df5f884dfdff504d78ceb631f77c66b/github-check/install-yamls-crc-podified-edpm-baremetal/65fec9e/ci-framework-data/logs/crc/pods/openstack_dataplane-deployment-configure-network-edpm-compute-kfms9_4895d0cb-ba5c-4c82-a6e5-3ffbe307ecd3/openstackansibleee/0.log
[2] https://logserver.rdoproject.org/60/460/210937ab2df5f884dfdff504d78ceb631f77c66b/github-check/install-yamls-crc-podified-edpm-baremetal/65fec9e/ci-framework-data/logs/crc/pods/openstack_dnsmasq-dns-695d5c4585-zf9q7_cf80e892-2259-448f-8b08-9938ba532ffa/dnsmasq-dns/0.log
[3] https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html

install-yamls-crc-podified-edpm-baremetal is currently broken with ansible halting on a name resolution failure[1].

@Steve Do you still see the issue locally with latest openstack-operator? That looks like an old job log though. I assume it was when we had the issue with "ansibleee pods not able to reach the metallb endpoints for dns server advertized on the same interface after we attached the ctlplane nad to them". I see jobs passing after that[1]. And dnslogs still show those NODATA-IPV6(?).
Though we can add this flag if we want or modify dnsmasq controller.
[1] https://review.rdoproject.org/zuul/build/e410081b642f4954807820afac87f70f
[2] https://logserver.rdoproject.org/73/473/91b1e4811d3c89deb8ae32b739e657d8dfe2e8fa/github-check/install-yamls-crc-podified-edpm-baremetal/e410081/ci-framework-data/logs/oc_inspect/namespaces/openstack/pods/dnsmasq-dns-695d5c4585-f5rzj/dnsmasq-dns/dnsmasq-dns/logs/current.log

recheck

I'm still seeing this issue locally, but this must be a red herring. Lets see if the job is green on the most recent https://github.com/openstack-k8s-operators/install_yamls/pull/460


Node add service: allow exact match to name in proto file, improve error reporting

This fixes #10080 by allowing users to use the exact name of methods from the proto file instead of the camelCase name when registering method handlers. It also improves the error output when a method is not provided to specify that a camelCase name was expected.

The interop failures are #9937 and #9797


Multiple coordinators chaining

Hello!
I have the flow below:

I have 3 coordinators:

Dashboard Coordinator
Cards Coordinator
Transfer Coordinator

From Transfer screen (Transfer Coordinator) I should be able to present Add a card screen (Cards Coordinator).
Which one is the proper way to achieve this kind of flow?
Please, consider that each flow has it's own viewModel class. For example:

The whole cards flow has a viewModel called CardsViewModel which take at initialisation a router of type CardsRoutes.

The whole transfer flow has a viewModel called TransferViewModel which take at initialisation a router of type TransferRoutes.

Also, dashboard has a viewModel called DashboardViewModel  which take at initialisation a router of type DashboardRoutes.

Thanks! 👍

Hey @AngCosmin,
there are multiple options to chain these coordinators:
1. Extract AddCards flow
Create a separate route/coordinator for the AddCard flow and all subsequent routes, so that there will be a DashboardCoordinator, CardsCoordinator, TransferCoordinator and a AddCardCoordinator. The AddCoordinator can then either be injected with the rootViewController of the CardsCoordinator or create its own rootViewController.
2. Allow CardsCoordinator to specify different initial routes
Modify the CardsCoordinator, so that you can either start with the CardsRoutes.yourCards or the CardsRoutes.addCards route. Then you can use these initial routes respectively in the DashboardCoordinator and the TransferCoordinator.
3. Also have a look at the solutions of this similar issue: https://github.com/quickbirdstudios/XCoordinator/issues/139
I hope, one of these solutions works for you. Please tell us, which of them worked for you and why you chose it, so that others can benefit as well - Thanks in advance!

I'm closing this due to inactivity. Feel free to reopen, if this is still an issue, or add additional comments, e.g. what might have solved the issue.


Fix PoliChek hit: Scotch

User Story https://dev.azure.com/mseng/TechnicalContent/_workitems/edit/2001296
Summary
The term "Scotch" may be used if not referring to people. However, the correct name of the breed is apparently "Scottish terrier."
Fixes #Issue_Number (if available) https://dev.azure.com/msft-skilling/Content/_workitems/edit/14570

#sign-off

Closing as duplicate of #31944


Remove depdencies of win32 and ffi.

Remove depdencies of win32 and ffi.
For previous reques, I make new PR that can make it easy to merge and review.

Released 1.1.1


Measure the time the compiler takes for each phase

The compiler is slower than it could be. As a first step we should measure how much time it takes for each phase in order to direct our optimization effort towards the slowest one.

It might be nice to integrate some sort of regression testing into the Github CI where we compare the compilation time of a select list of benchmark programs (comparing all tests would mean ~ double CI time) using the master branch and the respective PR branch. This way, we would have an easy way to detect performance regressions right at the PR drafting stage, rather than when it is already merged.
I am fairly certain that I have already seen this in other repositories. I will investigate further, if this is deemed worthwhile. I am looking forward to hearing your opinions.


Build

Great project.
Johnny trying to rebuild.
Using Microchip Technology PIC PRO Macro Assembler V1.45 build Cx8.   What did you use?
Not getting a HEX that fits in the 0x1000 for the 16f1454.
I am trying to build the MSD that fits in less than 0x7DB - Do you think this is possible? What could be removed to get it in 0x7DB?
Thank you so much.

Hi Anobium, I also used XC8 V1.45 Pro. Double check I didn't leave a code offset in the project settings for the MSD example. I tested these examples using a USB bootloader. Also double check when you compile that PRO optimisation is actually being used. Not at a computer right now to check it sorry.

Hi Anobium, I also used XC8 V1.45 Pro. Double check I didn't leave a code offset in the project settings for the MSD example. I tested these examples using a USB bootloader. Also double check in the output when you compile that PRO optimisation is actually being used. Check optimise for space. Not at a computer right now to check it sorry.

Very grateful.  Still no progress here.
I am compiling to create this file as follows.  MSD_Examples/MSD_Internal_Example/PIC16F145X.X  I am assuming MSD_examples is correct the code.  Is this correct?
:  ..USB-Stack-master/USB-Stack-master/USB_Stack_Examples/MSD_Examples/MSD_Internal_Example/PIC16F145X.X/dist/PIC16F1454_PRO/production/PIC16F145X.X.production.hex...
I have loaded the HEX into PK2 GUI.  The code is still exceeds 0x1000 as cab be seen in the picture.

If I compare to your HEX....which is correct.

What school boy error am I making?

Hmm, not sure what's doing that. I'd check to make sure your version of XC8 is fully licensed (Pro). That's the most likely cause. Even if you select pro, it may still not be optimised. The output window should tell you after a compilation. The code for PIC16F145X only works on the pro version. The memory is very tight on this chip. In XC8 Global Options->XC8 Linker->Rom Ranges make sure "0-7FF,800-FFF" is there. If your code can't fit in the Rom Ranges it should have an error on compilation. Did an error occur?
Also leave FLASH_SPACE_START = 0x01000 and END_OF_FLASH = 0x02000 in main.c.

Hmm, not sure what's doing that. I'd check to make sure your version of XC8 is fully licensed (Pro), that's the most likely cause. Even if you select pro, it may still not be optimised. The output window should tell you after a compilation. This MSD Internal example for PIC16F145X only works on the pro licensed version of XC8, the memory is very tight on this chip. In XC8 Global Options->XC8 Linker->Rom Ranges make sure "0-7FF,800-FFF" is there. If your code can't fit in the Rom Ranges it should have an error on compilation. Did an error occur?
Also leave FLASH_SPACE_START = 0x01000 and END_OF_FLASH = 0x02000 in main.c.

Cheers.  No progress,
Checked a main():

Checked Rom ranges:

Checked Pro mode:
See outoput.txt.
Check optimisation changes in 1.45 Release note:
No change,
Most odd... what is different?

Very strange. Is this a clean copy of the example or modified? If modified, send me a copy of your project and I'll try work it out.
Since you messaged me I've been in the process of updating this library. I have a version here that support's the latest compiler v2.2.0 and C99. Let me know if that would be helpful.
John.

Best if I share the goal - it will help.
I develop Great Cow BASIC. An Open Source compiler for PIC and AVR.   We have users in, truly, Africa who use Great Cow BASIC for education.  The challenge is providing a solution that is very, very low cost.
So, Great Cow BASIC cannot address beyond 0x1000.  This is a hard coded limitation. Never really thought the Bootload would not sit outside the first page.
This may explain why the ask for 16F1454 that has less functionality, and, looking for a bootloader is about 0x800.
So, if you think that 0x800 is just not achievable then I should give up and not waste anymore of you time.
Your thoughts on the challenge?

Sorry I'm a little lost. So you're wanting to make a bootloader using MSD Internal Example as a starting point? Is it the unchanged example that won't compile lower than 0x1000 or your application/bootloader? Why the limitation of 0x800? Your saying because your compiler can't address beyond 0x1000?  If I understand right, you want 0x000 to 0x800 your bootloader, 0x800 to 0x1000 is user space and 0x1000 to 0x2000 is unusable space due to Cow BASIC limitation? I don't think my USB uC/USB stack can fit in 0x800 words. It was difficult fitting it into 0x1000. I'll have a look tomorrow and see if USB uC bootloader for 16F145X can be made smaller.

Sorry to confuse.
The posts with the reports are the stock downloaded not changed.  So, that an issue here - It may not be be at your end.
The Great Cow BASIC constraints. Great Cow BASIC page handler assumes that page 0 is available.  When Hugh wrote the compiler (11 years ago, he was 13!!) that was his assumption.  So,  0x800 is workable within Great Cow BASIC but I understand this may be difficult.
Thank you for looking.

Hey, I've uploaded the source code for the 145X bootloader on my USB uC repository... I tried to get the code size as small as possible but only achieved down to 3,935 (0xF5F) words used, 161 (0xA1) free. I have my doubts this bootloader could ever fit in less than one page 0x800, especially written in C... I have seen others write really small USB bootloaders in assembly, CDC, HID and DFU in 512 words or less. Quick google search and you'll find them.
Sorry I couldn't be more help.
John.

John,
Thank you so much for trying.  Truly grateful.  I owe you – want a free license to PICKitPlus as a trade for your time?
Option are give up or rewrite a major part of Great Cow BASIC.
Again, thank you.
Evan
To solve your Microchip PIC programming problems – use PICKitPlus for the PICKit2 and PICKt3 programmers.  See  http://www.pickitplus.co.uk www.pickitplus.co.uk
Brain logo with white stroke 100x100
Anobium Business Services Limited - Registered Office: Anobium House, Bramley, Surrey, UK GU5 0DP- Registered in England No: 12232398.
Anobium Business Services Limited -- This message is transmitted to you by or on behalf of Anobium Business Services Limited. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind Anobium Business Services Limited to any order or other contract unless pursuant to explicit written agreement or written initiative expressly permitting the use of e-mail for such purpose.
From: John Izzard<EMAIL_ADDRESS>Sent: 01 July 2020 05:53
To: johnnydrazzi/USB-Stack
Cc: Anobium; Author
Subject: Re: [johnnydrazzi/USB-Stack] Build (#1)
Hey, I've uploaded the source code for the 145X bootloader on my USB uC repository... I tried to get the code size as small as possible but only achieved down to 3,935 (0xF5F) words used, 161 (0xA1) free. I have my doubts this bootloader could ever fit in less than one page 0x800, especially written in C... I have seen others write really small USB bootloaders in assembly, CDC, HID and DFU in 512 words or less. Quick google search and you'll find them.
Sorry I couldn't be more help.
John.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/johnnydrazzi/USB-Stack/issues/1#issuecomment-652189090 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AEI2IQ6WZNSCGBFVROEIJ4DRZK6LHANCNFSM4NF6FH4Q .  https://github.com/notifications/beacon/AEI2IQYSYVRQINXOUHD35ELRZK6LHA5CNFSM4NF6FH42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOE3PZ3IQ.gif


Support skiping implicit type cast checking by using flag --no-implicit-type-cast-check

Hi,
I created this PR to resolve the issue reported in https://github.com/hyperledger-labs/solang/issues/632 where Solang reports errors on implicit type truncation of integers (which Solc can compile well).
In particular, I added a field pub implicit_type_cast_check: bool into the structure Options to capture this flag.
I also move the structure Options from codegen/mod.rs into lib.rs so that the compiler options can be accessed by both sema and codegen modules.
Can you review this PR and advise if my implementation can be merged?
Thank you!

@seanyoung: thank you for the feedback.

The only change that is needed is that when uint256 is converted to Type::Value, then it should be permitted with a warning and a conversion check. Expression::Trunc throws away the higher bits. Optionally there could be an option to suppress the warning output.

Yes, I agree that for the current state of Solang, maybe we only need to check the conversion of uint256 and Expression::Trunc.
Currently, I move the Options data structure to lib.rs so that it can be used by sema (previously it's in codegen modules). Are you OK with this change?

Perhaps Expression::Trunc could have an extra boolean field which signifies that the codegen should check no value is actually being truncated (if the value fits into uint256 and not into uint128).

Do you think this check is dependent on target, e.g., ewasm, solana, ...? If so, we can add the target to Options and check it too.

Issue resolved in #650

Thanks for the update! Yes, your solution is more systematic!


Fast cofactor clearing for BLS12-377

Description
Use the effective cofactor (h_eff) for g1 and psi endomorphism technique described as optimal for BLS12 family in https://eprint.iacr.org/2017/419.pdf. Note that in clearing a cofactor method in g2 we can skip some negations since the curve parameter X > 0 for bls12-377.
Also I cleaned up the equivalent code for BLS12-381 a little, namely some code comments and made the standalone functions and psi-related constants private.
@mmaker

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[x] Wrote unit tests
[x] Updated relevant documentation in the code
[ ] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer

Too fast for me to check lol
One small comment: why cite Wahby and Boneh for BLS12-381 but not Budroni and Pintore in this pull request? I think they deserve to be credited and their work should be cited.


yolov5

Epoch   gpu_mem       box       obj       cls     total    labels  img_size
0%|          | 0/169 [00:02<?, ?it/s]
Traceback (most recent call last):
File "D:/yolov5-5.0/train.py", line 543, in
train(hyp, opt, device, tb_writer)
File "D:/yolov5-5.0/train.py", line 304, in train
loss, loss_items = compute_loss(pred, targets.to(device))  # loss scaled by batch_size
File "D:\yolov5-5.0\utils\loss.py", line 117, in call
tcls, tbox, indices, anchors = self.build_targets(p, targets)  # targets
TypeError: cannot unpack non-iterable NoneType object

I have the same questions,


Renaming and then renaming back files causes errors

Description
Renaming a file causes errors in all files that require it, as expected. However, after renaming the file back again, those require errors still show up!
This issue is split out from #1604.
Expected behavior
The require errors go away when renaming the file back again.
Actual behavior
The require errors never seem to go away. Workaround: restart the watcher.
Here's the test repo: https://github.com/lydell/brunch-notification-overflow
~/src/brunch-notification-overflow master %
❯ brunch w &

~/src/brunch-notification-overflow master %
❯ 31 Dec 13:23:49 - info: compiled 4 files into app.js in 319 ms

~/src/brunch-notification-overflow master %
❯ mv app/utils.js app/helpers.js
31 Dec 13:23:59 - info: compiled helpers.js and 4 cached files into app.js in 73 ms

~/src/brunch-notification-overflow master *%
❯ 31 Dec 13:23:59 - error: Processing of app/one.js failed.

   Cannot read property 'split' of undefined

31 Dec 13:23:59 - error: Processing of app/three.js failed.

   Cannot read property 'split' of undefined

31 Dec 13:23:59 - error: Processing of app/two.js failed.

   Cannot read property 'split' of undefined

~/src/brunch-notification-overflow master *%
❯ mv app/helpers.js app/utils.js
31 Dec 13:24:11 - error: Processing of app/one.js failed.

   Cannot read property 'split' of undefined

31 Dec 13:24:11 - error: Processing of app/three.js failed.

   Cannot read property 'split' of undefined

31 Dec 13:24:11 - error: Processing of app/two.js failed.

   Cannot read property 'split' of undefined

~/src/brunch-notification-overflow master %
❯ 31 Dec 13:24:11 - error: Processing of app/one.js failed.

   Cannot read property 'split' of undefined

31 Dec 13:24:11 - error: Processing of app/three.js failed.

   Cannot read property 'split' of undefined

31 Dec 13:24:11 - error: Processing of app/two.js failed.

   Cannot read property 'split' of undefined

~/src/brunch-notification-overflow master %
❯ touch app/utils.js
31 Dec 13:24:19 - error: Processing of app/one.js failed.

   Cannot read property 'split' of undefined

31 Dec 13:24:19 - error: Processing of app/three.js failed.

   Cannot read property 'split' of undefined

31 Dec 13:24:19 - error: Processing of app/two.js failed.

   Cannot read property 'split' of undefined

I'd expect there to be no errors when renaming the file back to utils.js again.
Environment

Brunch: commit afefc5e7643f37918ed037e3862461624e483425
Node: 6.9.1
NPM: 3.10.8
Operating system: Ubuntu Gnome 16.04

package.json contents
{
  "private": true,
  "devDependencies": {
    "brunch": "github:brunch/brunch#afefc5e7643f37918ed037e3862461624e483425",
    "javascript-brunch": "^2.0.0"
  }
}

brunch config contents
module.exports = {
  files: {
    javascripts: {
      joinTo: 'app.js'
    }
  }
}

Hi, @lydell! Thanks for reaching out!
Your issue is related to problems with deppack module.
Here are other issues: deppack related issues.
We're working on it. I believe we will fix that as soon as it possible.


mktemp: expose functionality for nushell

As per https://github.com/uutils/coreutils/issues/5088#issuecomment-1733828007 I'm opening this ticket to discuss details about how expose mktemp functionality for use in nushell.

Should a new pub fn be created that returns a result of String as I think the current functions just print to stdout. What other considerations are there?

Yes, I think that's a good idea! I think it should be roughly done as follows:

mktemp: returns a path and calls exec and dry_exec
exec and dry_exec should also return the path.
uumain calls mktemp and prints the result.

Otherwise I think this one should be fairly simple. Thanks for picking this up!


Add tests for punctuation on description and 'external' on external urls.

As discussed this morning - please make sure all the tests pass before assigning this back to me to merge.


support image digests - DO NOT MERGE

@posriniv from the image tag/shas meeting, it seems like we would need to set the sha as an environment variable.

Also, @posriniv do we need to update the ClientRegistraton job tag to sha? instance.Spec.ClientRegistration.ImageTag
File: pkg/controller/authentication/job.go

With these changes, two pods for some CRs are being created - one using the image sha and the other using the image tag.
secret-watcher-5b4b5567bd-hlmx8                           1/1     Running                      0          16m
secret-watcher-dcf8fbc7b-dwb22                            0/1     ImagePullBackOff             0          15m
security-onboarding-2whwk                                 0/1     Init:ImagePullBackOff        0          17m
iam-policy-controller-79d9b665-7c4th                      0/1     ImagePullBackOff             0          15m
iam-policy-controller-7c4dfcb94-j4cnk                     1/1     Running                      0          16m
auth-idp-678455c85-pm7g5                                  4/4     Running                      0          15m
auth-idp-7b96bd4684-8srfs                                 0/4     Init:ImagePullBackOff        0          3m45s
auth-pap-857d9cc754-8tzch                                 2/2     Running                      0          16m
auth-pap-86794bc5fb-7n4rc                                 0/2     ImagePullBackOff             0          17m
auth-pdp-5d878c9fd7-gtkpg                                 0/2     Init:ImagePullBackOff        0          17m
auth-pdp-6978bb4498-78q8q                                 2/2     Running                      0          16m

Output from describe pod:
  Normal   Scheduled  <unknown>              default-scheduler                           Successfully assigned ibm-common-services/oidcclient-watcher-844f54b56c-dfd9s to worker0.meow-meow.os.fyre.ibm.com
  Normal   Pulling    46m (x4 over 48m)      kubelet, worker0.meow-meow.os.fyre.ibm.com  Pulling image "quay.io/opencloudio/icp-oidcclient-watcher@sha256:ef1008d0add206466f1a670af06a46c42d8a8e38c5c5561620c969340f2066d9"
  Warning  Failed     46m (x4 over 48m)      kubelet, worker0.meow-meow.os.fyre.ibm.com  Failed to pull image "quay.io/opencloudio/icp-oidcclient-watcher@sha256:ef1008d0add206466f1a670af06a46c42d8a8e38c5c5561620c969340f2066d9": rpc error: code = Unknown desc = Error reading manifest sha256:ef1008d0add206466f1a670af06a46c42d8a8e38c5c5561620c969340f2066d9 in quay.io/opencloudio/icp-oidcclient-watcher: manifest unknown: manifest unknown
  Warning  Failed     46m (x4 over 48m)      kubelet, worker0.meow-meow.os.fyre.ibm.com  Error: ErrImagePull
  Warning  Failed     13m (x150 over 48m)    kubelet, worker0.meow-meow.os.fyre.ibm.com  Error: ImagePullBackOff
  Normal   BackOff    3m11s (x194 over 48m)  kubelet, worker0.meow-meow.os.fyre.ibm.com  Back-off pulling image "quay.io/opencloudio/icp-oidcclient-watcher@sha256:ef1008d0add206466f1a670af06a46c42d8a8e38c5c5561620c969340f2066d9"


Vsix project based on .net core ?

Is there a vsix project that is based on .net core?
If not can I used the already existed vsix project to reference a .net core projects ?
Thanks in advance

Hi @mustafasaaed , this repo is about ASP.NET Core.
To report issues with Visual Studio, use the Report a Problem tool.
If you encounter a problem with Visual Studio, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See here for more details.


docs: change serum discord url to an invite link

If you are logged in to discord, but not a member of the Serum discord and you click the discord link in the docs, you will end up at a page like this

If you use the invite link from the projectserum.com footer (https://discord.gg/zxPsXcB) you will be sent to the Serum discord, but not directly to the #dev-questions channel.

I created the link in this PR, in the hopes that it could invite new users AND direct existing users straight to the #dev-questions channel. I generated by clicking 'create invite' next to the channel and creating a direct invite link there. I set it to never expire, with no limit of users

...but even as a (now) existing member of the Serum discord, it takes me to the #rules page. So I don't know if the problem can be fully solved.

Good catch! Thanks! I changed the invite links to use the new #anchor channel in Discord.