DSPDC-1154 Consider virtual_path when deduplicating file ingest.

Testing now: https://hca-argo.monster-dev.broadinstitute.org/workflows/hca-mvp/ingest-hca-kjgv7-cbrzh-s6rpj-42p92-6gp4x

Codecov Report

Merging #17 into master will decrease coverage by 0.43%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
- Coverage   60.21%   59.78%   -0.44%
==========================================
  Files           1        1
  Lines          93       92       -1
  Branches        3        3
==========================================
- Hits           56       55       -1
  Misses         37       37

Impacted Files
Coverage Δ

...roadinstitute/monster/hca/HcaPipelineBuilder.scala
59.78% <100.00%> (-0.44%)
:arrow_down:

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 d311350...5f33009. Read the comment docs.

Test run attempt 2! https://hca-argo.monster-dev.broadinstitute.org/workflows/hca-mvp/ingest-hca-kjgv7-cbrzh-s6rpj-42p92-6gp4x-vg2fv

The new logic works (doesn't crash), but it'll be hard to tell if it has any logic bugs until we can reset the dev dataset & re-ingest the universe.

Yup, we'll only dedup on content-hash when the target paths align.


Method [validate] does not exist while adding category, priority and other options

Getting following error:
(1/1) BadMethodCallExceptionMethod [validate] does not exist.
in Controller.php (line 82)
at Controller->__call('validate', array(object(Request), array('name' => 'required', 'color' => 'required')))in CategoriesController.php (line 46)

Based on the other issue you opened after this, I assume you have solved this one.

yes, i have thank you .. the problem was on my part of a controller.


Bump mysql 8.0 versions for 8.0.27

The Problem/Issue/Bug:

Mysql has released minor versions

How this PR Solves The Problem:

Bump to 8.0.27
Bump 5.7 to latest

Manual Testing Instructions:

[ ] Start a project with mysql 8.0 and see it has 8.0.27 (do on both arm64 and amd64)
[ ] Start a project with mysql 5.7 and see it has 5.7.37

Automated Testing Overview:

Related Issue Link(s):
Release/Deployment notes:

Unfortunately, this one can't work until the next release of percona-xtrabackup. xtrabackup releases lag mysql-server releases, and ubuntu 20.04 already has mysql-server 8.0.28, which isn't compatible with percona-xtrabackup 8.0.27, which is all we have right now.


Show errors in Rust test code

The Cargo maker, as currently defined, will only build/check the main binary or library. To also get errors in additional targets (like other binaries) or in tests, the commands that are run must be tweaked a little. If not using cargo check, the right command to run is probably cargo test --no-run, which should build all targets, including tests, but not run anything. When g:ale_rust_cargo_use_check is set, ALE will currently run cargo check with no additional flags. However, this will only check non-test code, and only for the library. To test all targets, cargo check --all should be used.
Unfortunately, --all does not check tests. https://github.com/rust-lang/cargo/pull/4039 attempts adds --tests, but still seems to be some way away from landing. --all is a good half-way point in the meantime though. This is also the conclusion that was reached for neomake in https://github.com/neomake/neomake/issues/843#issuecomment-287451705.

I guess someone can add --all. They might want to check the version of cargo before passing the argument.

Now that https://github.com/rust-lang/cargo/pull/4592 has landed, the thing we want is --all-targets (see also https://github.com/rust-lang/cargo/issues/2495#issuecomment-340608019).

Now cargo check will automatically be used when cargo is new enough, and cargo check --all-targets will be used when cargo is new enough. g:ale_rust_cargo_use_check or g:ale_rust_cargo_check_all_targets can be set to 0 to disable one or both.


Probably cannot use Wifi networks that include a space in their name

I think one of the underlying libs this project includes has very sloppy wifi SSID handling code which truncates the SSID (and passwords too) at the first space char it encounters...
I fixed this in one of my own esp32 projects - it's simple to fix - but if anyone else is wondering why nothing works and the SSID has spaces in it - try again using a new network without spaces...

Thanks for note this. Could you please share your git repo about the esp32 project?

I really like this project - but there's a few things that I think need adding and explaining better as well.
Since the "abutton" does not have any plugs etc on it, an OTA firmware update build should really be released (I have one I did a few years ago that works great) so it can be updated without having to plug anything into it.  Existing settings really should be shown in the setup, other ways to setup might be nice, as well as automatic connection to open wifi and other resilient attempts to connect when things fail or upon setup, serial numbers for the buttons would be handy, details about the battery state (assuming the hardware even supports this at all) should be reported somehow, ... and I'm sure I'll think of more later.  (fixing the space bug in ssid's and passwords is a biggie of course!)


feat: remove backtrace from sql::error::Error

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Removed backtrace from Error enum.
Please explain IN DETAIL what the changes are in this PR and why they are needed:

this is a cleanup task. As per https://github.com/GreptimeTeam/greptimedb/issues/855 most backtraces in sql::error::Error are unnecessary and might hurt performance since the parser would always return them while parsing an invalid SQL.

Checklist

Docs are not needed in this case
Need a bit of a steer with the necessary unit tests and integration tests.

Refer to a related PR or issue link
https://github.com/GreptimeTeam/greptimedb/issues/855

Nice job! @etolbakov The Rustfmt check failed, could you fix it?

Thanks @evenyag 🙏
sorry about the formatting issue! will make sure that it won't be a problem later on.


add fold to types with parens

Hello again.
This one is pretty simple. It just adds fold to multiline types with parens.
In other words...
type Foo = (
    bar: string,
    baz: number,
    qux: any,
) => void;

All of the above is folded.
Let me know if you have any questions or would like me to add a test for this.

Thanks!


CLI behave like a malware

I saw a prompt about it when working with composer.
Out of curiosity, I installed and ran it.
It didn't mention anywhere what it does exactly (thanking other developers is a bit vague). I only found out what it does at the very last time after I ran the code and it starred all the repositories without my permission.
There was no explanation, no permission request, no warning and no undo button. It access my github without my permission (just like a malware would do).

I checked the code, it's pretty clear about the fact this sends github stars, eg "Give thanks (in the form of a GitHub ⭐)"


Issue 17: recognize and update format for Bulgarian numbers

I based this off of http://www.wtng.info/wtng-359-bg.html. I'm open to ideas for improvement. This arose from the need to recognize a specific number for Sofia, Bulgaria as valid.

Coverage increased (+0.9%) to 99.4% when pulling 18f19f8a21fba6f70fba7ee57a4860553a94bef4 on davidkovsky:master into a1f113f5f1d8cf9d65cf9e1c4e8703da0db11eb4 on floere:master.

@davidkovsky Apologies for the late answer, I was holidaying 😅 This looks great, thanks so much!
The only improvement that I can see right now would be to combine some regexes, e.g. match(/^(31)\d{6}$/) >> split(6) | and match(/^(32)\d{6}$/) >> split(6) | into match(/^(31|32)\d{6}$/) >> split(6) |. But otherwise it looks good, loving the many/exhaustive specs 👍
I've already pulled in a smaller PR that improved Sofia, see https://github.com/floere/phony/pull/407, by @SofiaMargariti. I noticed that the local number part is split differently in the sources (+359 2 1234567 vs. +359 2 123 4567). This PR opts to not split (as described in http://www.wtng.info/wtng-359-bg.html), while the other PR does (as described in
https://en.wikipedia.org/wiki/Telephone_numbers_in_Bulgaria). I do tend to prefer rules that do a split for readability.
It's not a big issue, but perhaps any of you has an opinion/data on it? Thanks in advance 😊

Other than the regexp issue and local number splitting… very happy to pull! 🚀

Thanks for the feedback. I'm happy to combine regexes. I was trying to keep it easy to compare lines in the spec with lines in the code. I think my original thought was along the lines of match(/3^(1|2)\d{6}$/) >> split(6) |, which would have been harder to compare with the spec than your suggestion of match(/^(31|32)\d{6}$/) >> split(6) |.
I think consistency is the most important thing for the split rules so I'm happy to follow your preference. I'll try to prepare an update soon.

@floere I pushed to new branch of my repository to keep the history clean. I'm going to close this PR and open a new one from that branch.


SeeAnyOf and SeeAllOf have a few inconsistencies.

With the recent merge of #64, @bandophahita noticed that there are a couple ways that SeeAllOf and SeeAnyOf are inconsistent:

When asserting no tests, SeeAllOf() will pass, while SeeAnyOf() will fail.
When executing tests, SeeAllOf will short-circuit at the first failure, while SeeAnyOf will execute all tests.

I think that the desired behavior is:

When asserting no tests, both should pass.
When executing tests, all tests should be executed (no short-circuiting).

Consider this code:
actor.shall(See(q1, r1))
actor.shall(See(q2, r2))

If the first test fails, pytest will never execute the 2nd test unless they were to wrap it in a try/except.  Shouldn't SeeAllOf mimic that same behavior?

If the first test fails, pytest will never execute the 2nd test unless they were to wrap it in a try/except. Shouldn't SeeAllOf mimic that same behavior?

Maybe that's one reason to use SeeAllOf instead of a series of Sees, so they can perform each test every time to see the result?

After more consideration, i think (personally) that SeeAnyOf() and SeeAllOf() should actually raise an exception for not having any tests. I can only imagine someone put them in like that by mistake, and either a test would be passing when it is missing its assertion or there's just an unnecessary line in their log.
Either way, it doesn't make sense to me that someone would want that intentionally—i think raising an exception to call out the mistake is the best UX.

After more consideration, and more conversation with @bandophahita, we've decided to change course on this:

SeeAllOf and SeeAnyOf should both short-circuit, mimicking Python behavior.
SeeAllOf and SeeAnyOf should both accept 0 tests and pass.

After more consideration, and more conversation with @bandophahita, we've decided to change course on this:

SeeAllOf and SeeAnyOf should both short-circuit, mimicking Python behavior.
SeeAllOf and SeeAnyOf should both accept 0 tests.
SeeAllOf and SeeAnyOf should both accept 1 test.

This is what we merged!


"hub" setting doesn't change hub for images used by components (pause, klipper-lb, etc)

Bug description
Tried installing istio using a couple different profiles (default, and minimal with ingressGateways component turned on) and tried setting the global.hub value, as well as the components.ingressGateways[0].hub value but neither seem to affect images used by istiod (which references docker.io/rancher/pause) and the svclb-ingressgateways pod. (which uses docker.io/rancher/klipper-lb)
My team needs to be able to support offline installations, and previously (with istio 1.4 installed via helm chart) we were able to pre-populate local registries with istio images. However, we have no way to configure where these rancher images are coming from. This was tested with istio 1.6 but may also apply to istio 1.5 as well.
Additionally, the docs don't seem to reference these images at all or acknowledge their use. Searching the istio docs for rancher/klipper-lb returns no results.
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[X] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Expected behavior
Setting global.hub (or another similar setting) should be able to change the domain for infrastructure images
Steps to reproduce the bug
Set global.hub to a local registry pre-populated with istio images (including pilot and proxyv2), disconnect from the internet and install istio. Running a kubectl describe on the istiod pod will report that it cannot download docker.io/rancher/pause.
Events:
  Type     Reason                  Age        From                         Message
  ----     ------                  ----       ----                         -------
  Normal   Scheduled               <unknown>  default-scheduler            Successfully assigned istio-system/istiod-b64f9b96b-4kw5m to k3d-drydock-server
  Warning  FailedCreatePodSandBox  12s        kubelet, k3d-drydock-server  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "docker.io/rancher/pause:3.1": failed to pull image "docker.io/rancher/pause:3.1": failed to pull and unpack image "docker.io/rancher/pause:3.1": failed to resolve reference "docker.io/rancher/pause:3.1": failed to do request: Head https://registry-1.docker.io/v2/rancher/pause/manifests/3.1: dial tcp: lookup registry-1.docker.io: Try again

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
istioctl version --remote
client version: 1.6.4
control plane version: 1.6.4
data plane version: 1.6.4 (18 proxies)

kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0", GitCommit:"70132b0f130acc0bed193d9ba59dd186f0e634cf", GitTreeState:"clean", BuildDate:"2019-12-07T21:20:10Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3+k3s1", GitCommit:"5b17a175ce333dfb98cb8391afeb1f34219d9275", GitTreeState:"clean", BuildDate:"2020-02-27T07:28:53Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
Using istioctl install and various modifications of minimal and default installs
Environment where bug was observed (cloud vendor, OS, etc)
Offline local dev environment

Okay, just leaving this message to let anyone know--this was not an istio issue. I found out shortly after posting this that istio is talking with k3s. k3s references a pause image, which is the docker.io/rancher/pause image, and k3s also deploys using servicelb, which is where the klipper-lb image is coming from.


Doc-3386

resource allocation logic
troubleshooting resource limits

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

The parallel step yaml should be below:
              - step:
                  type: Run
                  name: Run_1
                  identifier: Run_1
                  spec:
                    connectorRef: account.CItestDockerConnectorU43rVdZgSs
                    image: alpine
                    shell: Sh
                    command: top -d 10
                  timeout: 10m
              - step:
                  type: Run
                  name: Run_2
                  identifier: Run_2
                  spec:
                    connectorRef: account.CItestDockerConnectorg2M0YFNaR2
                    image: alpine
                    shell: Sh
                    command: |-
                      i=0
                      while [ $i -lt 10 ]
                      do
                          df -h
                          du -sh *
                          sleep 10
                          i=`expr $i + 1`
                      done
                  timeout: 10m

In your pipeline's YAML, add the following step immediately after your failing step:
This point can be removed.

Also add a note to set appropriate timeout in the above yaml so that issues can be identified when the pipeline fails.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Remove forceable resolution strategy on bcel after spotbugs upgrade

Description
Remove forceable resolution strategy on bcel after spotbugs upgrade

Category (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Maintenance
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

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

@cwperks The security check seems to believe that this change will introduce the bcel vulnerability back into the codebase. I see that it was commented that the line could be removed after spotbugs was upgraded, but it is not clear why the whitesource check is then failing.


Feature/testing vic5

This is the start of the VIC test module.
Notable Features

Travis is now compiling using gcc and clang, builds are passing for both compilers.
All tests are run from the run_tests.py script.
No changes were made to the VIC source code
The directory tests/test_data/will not be included in the repository but is available for preview here.  I'm still adding a few pieces to this but the general structure is now in place.
Currently, the system tests are the most built out but with the test structure I've put together, more can be easily added.

Test Module Structure:

unit:  function level tests.
system: tests that aim to address model runtime issues.  These tests are generally very quick.

configuration errors - tests that address model startup and error checking.
restart:  tests that address model state and restart capacity.
I/O:  tests that address model input and output functionality.

forcings come out the way the come in
parameter files are appropriately read in allocated.

science:  tests that aim to assess the model's scientific skill.  Many of these tests are compared to observations of some kind.
examples:  a set of examples that users may download and run.
release:  longer, full domain simulations performed prior to release demonstrating model output for a final release.

Areas in need of further development:

[ ] Science Tests: comparisons with observations
[ ] Image Mode Driver Tests:  currently all tests use the classic driver
[ ] Standard test comparing image and classic drivers.
[ ] Tests datasets for lesser used options:

[ ] Blowing snow,
[ ] Precipitation correction,
[ ] Lakes and wetlands, and
[ ] Carbon cycle.

This could be merged now or we could wait until we've added more tests.  Since there are no changes to the source code of VIC, the only downside to merging now is that there will need to be more pull requests in the future.
fixes #79.

No code review at this stage, but will accept pull request to get this started and since it lives in its own directories


fix(Questionnaire): Align Privacy Consent render

This aligns with how the consent is rendered on the candidate site, including ignoring descriptionHtml

Candy:

This PR:


CLOUDP-70018: mongocli iam team(s) create

Proposed changes

Jira ticket: CLOUDP-70018

Checklist

[x] I have signed the MongoDB CLA
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added any necessary documentation (if appropriate)
[x] I have run make fmt and formatted my code

Further comments

waiting for https://github.com/mongodb/mongocli/pull/394


feat: Les services systemes sont installés lors de la provision du server

:tada: This PR is included in version 1.57.0 :tada:
The release is available on:

v1.57.0
GitHub release

Your semantic-release bot :package::rocket:


support Bevy 0.13

Great, thanks!
Can you add a version bump at the bottom of the README - 0.3?
I'll publish a new version once the code is merged.


wasm-wip  too many arguments in call to js.NewEventCallback when compiling against recent golangweekly lazyblogger wasmgo example

https://blog.lazyhacker.com/2018/06/go-with-webassembly-early-examples.html
https://github.com/lazyhacker/wasmgo
Sorry I meant lazyhacker.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
$ set|grep GO
GOPATH=/home/dma2/Code/go
GOROOT=/home/dma2/mywasmtest/go
$ /home/dma2/mywasmtest/go/bin/go version
go version devel +1caa06299c Tue Jun 19 16:39:52 2018 +0000 linux/amd64
Does this issue reproduce with the latest release?
no just the tip which is the only one with neelance's wasm-wip merges.

A complete runnable program is good.
A link on play.golang.org is best.
What did you expect to see?
compile successfully.
What did you see instead?

Refer to the documentation here - https://tip.golang.org/pkg/syscall/js/?GOOS=js&GOARCH=wasm#NewEventCallback.

You are misunderstanding the situation.  I submitted a bug about this with neelance and he told me to submit it to golang/go.  Here I am.  Also, the error in question was not code that I wrote.  It is sample code I am familiarizing myself with in order to start using go js/wasm compiler for which I have no sample code for.  This sample will be one of first I have tried with the golang/go merged js/wasm compiler.  I thought it would be polite to alert you that code was was compiling with neelance wasm-wip as experienced by lazyhacker and blogged last week no longer compiles here.
I am not a js expert nor am I a WASM expert which is why I turned to golang/go compiler team about this.  Where are the golang/go wasm examples that work with this golang/go merged js/wasm compiler if this example does not work?

@omac777 I found your bug report https://github.com/neelance/go/issues/29
It wasn't neelance that told you to make a report here, it was johanbrandhorst and he was giving you a blanket statement without paying too much attention to your report.
The function has since been changed, you can see the process here https://go-review.googlesource.com/c/go/+/114197/1
WASM support has not been released so anything and everything can and will be subject to change until the release.

Where are the golang/go wasm examples that work with this golang/go merged js/wasm compiler if this example does not work?

You'll have to wait for the release if you want proper examples. Any examples written before the release will have a chance of breaking.

Also, the error in question was not code that I wrote.

I get that. I meant the code that you have posted as part of the issue.

I thought it would be polite to alert you that code was was compiling with neelance wasm-wip as experienced by lazyhacker and blogged last week no longer compiles here. I am not a js expert nor am I a WASM expert which is why I turned to golang/go compiler team about this.

Sure, but there is no issue here. lazyhacker's code was using neelance's branch. That code has changed during review. There is no guarantee at all that it will compile.
This is all the official documentation we have - https://tip.golang.org/pkg/syscall/js/?GOOS=js&GOARCH=wasm. Keep in mind, this is all in master, so things are expected to change and break. If you work with tip, it is assumed that you will have a rough experience.
I would request you to wait until Go 1.11 release to get

easy to build(with latest version) examples demonstrating the core web_to_go and go_to_web concepts


Footnotes not retained in article.summary

The #default_summary_generator for the Middleman::Blog::BlogArticle module improperly handles footnotes in the article body text. If a footnote link exists in the summary text, the current implementation will retain the link in the summary, but without bringing the accompanying footnote content (found at the bottom of the article body). This leaves a dead link in the summary.
This seems the worst of 3 possible implementations:

strip footnotes from summaries
retain footnote content along with footnote links in summary
retain footnote links without content (current implementation)

I'm not certain which ought to be the default behavior, but I think the latter is the least helpful. Dead footnote links are gross. If you feel the second option is worth considering, I include below my custom summary generator, which grabs the entire footnote section from an article if any footnotes are in the summary. Would likely be overkill for a default implementation, but I include it just in case it helps:
def setup_summary_generator(separator = /(READMORE)/i)
  return Proc.new  do |resource, rendered, length, ellipsis|
    require 'middleman-blog/truncate_html'
    # determine which type of summary to use
    if resource.data.summary?
      summary = resource.data.summary
    elsif rendered =~ separator
      # The separator is found in the text
      summary = rendered.split(separator).first
    elsif length
      summary = TruncateHTML.truncate_html(rendered, length, ellipsis)
    else
      summary = rendered
    end
    # does the summary text include any footnotes?
    if summary.include?('')
      # find the footnotes div in HTML
      footnote_section = /
(.*?)<\/div>/m.match(rendered)
      # if no footnotes, emptry string
      footnotes = if footnote_section.nil? then '' else footnote_section end
      summary = summary + footnotes.to_s
    end
    summary  # return
  end
end

Bump, this bug in combination with gjtorikian/html-proofer means that any footnotes you include have to come after your separator or else your build fails (which is a frustrating and fairly arbitrary restriction).
Separately, @smargh, how did you integrate this function into your existing middleman install? Did you just have to edit the gem?

Hiya
Looking through the Features there is a the following :
  activate :blog do |blog|
    blog.summary_generator = Proc.new { "This is my summary, and I like it" }
  end

Creating your own handler for this is whats required. We can look at a way of smartly integrating footnotes later.
@xavdid Would be great to see a repo with what you mean regarding the crash when footnotes are within the summary.
Closing for now - please -reopen a new issue with the crash.


Write an Anki plugin to simplify importing cards

There's a good chance that I could reuse some code from https://github.com/kiddsoftware/srscollector/tree/master/extras/anki

We now handle this using export anki and AnkiConnect.


Fix alignment of Save Delete buttons on boundary CRUD pages

It is kind of squished together right now OR it is on two separate lines. Needs to be fixed across all boundary pages if not done already.

Save button on the left should have "btn btn-primary" and delete button "btn btn-primary padded-btn" - for classNames this takes care of spacing and colour.


Problem with finding suitable target after running ./wacker.py

Hello, I am having a problem with the wacker tool giving me a message regarding the following:
Starting wpa_supplicant...
Successfully initialized wpa_supplicant
Start time: 29 May 2024 17:41:47
No suitable target found for freq=2437, bssid=54:47:CC:.., ssid=A******..
Stop time: 29 May 2024 17:41:48
Stopped at password attempt: !@#$%
As above I am getting a No suitable target found for freq=2437 and so on, and ive also tried the same using another freq=5500 and the script stopping at the beginning of my wordlist. Any help is thanked greatly, have tried using the nmcli command to confirm the freq I am on is the same as the ap being targeted.
command ran is: ./wacker.py --wordlist cain-and-abel.txt --ssid A****** --bssid 54:47:CC:--interface wlan0 --freq 2437
I am only trying to hide the mac and ssid as to not be so open unsure if it is an issue to you being able to help o/

Can you rerun your command using the --debug flag and send over the logs under /tmp/wacker/.
Also, what network card are you using? Vendor and model would be useful

The --debug option might contain the MAC and SSID. If that's the case, we'll work on adding another option to scrub them from the logs to make this process easier.


MongoDB support --archive option for backup/restore

Currently the MongoDB backup and restore jobs do not support the use of the --archive option to put the backup into a single archive file.   It would be really nice to have this option since it makes the resulting backup much easier to manage/move/download.
BTW -- if you try to add this option via your own args you just get an error since the resulting mongodump command line is illegal.

I can verify that I was able to reproduce the error where --archive is provided as user configuration part and ended up getting error:
Failed: bad option: --out not allowed when --archive is specified

As we are deprecating snapshot, we are not gonna fix it in snapshot-tool.
--archive support is added and default setup in stashed/mongodb backup system. xref: https://github.com/stashed/mongodb/blob/master/pkg/backup.go#L200


XFF table not displaying correctly when XFF list contains same address twice.

See request https://toolserver.org/~acc/sand/acc.php?action=zoom&id=117 on the sandbox.

This appears to work fine in newinternal:


Vertical title overflows on shorter screen heights

The vertical title doesn't get truncated when its vertical, like it does when horizontal on mobile screens. It ends up covering up the menu close button.

How does something like this look @jazzdrive3 ?
https://github.com/user-attachments/assets/6188fcf8-d96e-4cc7-a142-16ac2a42b11a

That could work. Though I'm channeling the strategists when they say, "Truncation isn't a strategy."
Another option could be that we add a "short title" field to the metadata and have a hard character limit for it.

how's this look?
https://github.com/user-attachments/assets/888f4bdf-35db-41d1-859c-92d2d104a94d


How to use emojis

Hello. I've been enjoying learning your cool app! How do you type emojis into your schedule?
Thanks!

You simply copy and paste emojis (from this website for instance: https://apps.timwhitlock.info/emoji/tables/unicode), that your terminal font supports.

Thank you! I appreciate it


[Custom] Implement simple application  @open sesame 04/06 08:14

Dependency of the PR
Commits to be reviewed in this PR
[custom] expose optimizer example
This patch exposes optimizer example. This patch is just copy & paste
for now. The upcoming patch will update this to the updated format
Self evaluation:

Build test: [ ]Passed [ ]Failed [X]Skipped
Run test: [ ]Passed [ ]Failed [X]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>
[Custom] Update api of momentum optimizer
This patch update api of momentum optimizer.
Self evaluation:

Build test: [ ]Passed [ ]Failed [x]Skipped
Run test: [ ]Passed [ ]Failed [x]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>
[Custom] Add example skeleton for the custom opt
This patch add example skeleton for the custom optimizer.
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>
[Custom] Implement simple application
Add simple application which uses custom optimizer
resolves #1772
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1781. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

:octocat: cibot: @zhoonit, Applications/Custom/momentum.h does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1781-202112101437540.31018304824829-9736d9a917b3ad12b0bfecb9810a4e4ebae602b6/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1781-202112141048120.90174794197083-8df20a22771bc217049d457a629a2980a90c5fb9/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnstreamer.mooo.com/nntrainer/ci/repo-workers/pr-checker/1781-202204060814240.28775405883789-172de16f8c0b8a1537d51dd164474a2d797d3429/.


Debian package for sliding-sync ?

I installed matrix-synapse on my server using apt-get install. Installing the slinding-sync proxy as describe in the documentation might not be very suitable since it would have a cost in term of maintenance. What is the future of this project ? Will it be integrated into synapse ? Will a debian package be released ?

It is planned to be integrated into Synapse on a timescale of "months".

Is there an issue I could subscribed to ?


datalist plugin added

https://github.com/rrd108/cakephp-datalist

Instead of Plugin::load('Datalist');  the readme should suggest using the plugin shell to load the plugin so that apps using cake 3.6+ use the new method of plugin loading.

Even though
"cakephp/cakephp": "^3.5"

so technically this is the correct command to provide BC for 3.5.

This asserting doesn't seem right.
https://github.com/rrd108/cakephp-datalist/blob/0c0ca3c2e8e88c6ec60bb2f6001328b32f7ba28e/tests/TestCase/Model/Behavior/DatalistBehaviorTest.php#L74
Having 'issuer_id' in data implies a belongs to relation in which case the association property name would be company and a single entity not an array of entities?

It would be better if you wrote tests using models which use fixtures.

I have fixed the following

travis build image added to README
plugin load example uses console in the README
test cases refactored to use table objects
new test cases added
fixed a bug when there were more datalists and one of them got a selected an the other a new value

I think what I did not fixed is to add CO badge to the README suggested by @dereuromark as I would need some hint how to do that :)

Should I do anything else?


setup sbt plugin to allow publishing of signed jars to Apache Maven repository

As part of releasing Pekko, we will need to run an sbt command to publish signed jars to Apache Maven repository
sbt +publishSigned

sbt-pgp

Possibly other plugins could be used

@mdedetrich I'm fairly surprised that sbt publishSigned does not work. I would have thought that sbt-apache-sonatype would be loading sbt-pgp transitively. Anyway, adding sbt-pgp allows me at least to create signed jars locally.
I'm currently playing with sbt-sonatype commands to try to prepare a release and worrying that I might accidentally get it to publish a release all the way to Maven Central.

@mdedetrich I'm fairly surprised that sbt publishSigned does not work. I would have thought that sbt-apache-sonatype would be loading sbt-pgp transitively. Anyway, adding sbt-pgp allows me at least to create signed jars locally.

By not working I guess you mean we are missing some dependency? If so adding sbt-pgp to sbt-apache-sonatype should solve the issue

I'm currently playing with sbt-sonatype commands to try to prepare a release and worrying that I might accidentally get it to publish a release all the way to Maven Central.

One thing we need to take note of is sbt-sonatype by default does bundling, which means we may have to do something like https://github.com/sirthias/parboiled2/pull/452

@pjfanning Release of sbt-apache-sonatype v0.1.10 has been triggered which adds sbt-gpg as a dependency. Let me know if it solves your problem

@mdedetrich I don't mind adding sbt-pgp directly to each project but if you like we can do it indirectly via a new release of sbt-apache-sonatype.
I was able to generate a bundle in repository.apache.org using sbt +publishSigned and sbt sonatypePrepare sonatypeBundleUpload.
This bundle is not closed so it will not yet be in staging. I could use sbt sonatypeClose but I think I prefer the idea of using the UI to close the bundle. We absolutely don't want a release manager to use the wrong sbt-sonatype command a do a full release before a vote has happened (ie sbt sonatypeRelease or sbt sonatypeBundleRelease).

@mdedetrich I don't mind adding sbt-pgp directly to each project but if you like we can do it indirectly via a new release of sbt-apache-sonatype.

Already done, check above comment

@mdedetrich could you have a look at https://repository.apache.org/content/groups/staging/org/apache/pekko/ ?
The contents of this look ok to me. I can drop this later today to avoid confusion.

@mdedetrich could you have a look at https://repository.apache.org/content/groups/staging/org/apache/pekko/ ?

The contents of this look ok to me. I can drop this later today to avoid confusion.
Can you try with +publishSigned to see that it works with all Scala versions?

@mdedetrich unfortunately, I'm hitting recurring issues building Scala 3 artifacts. The scaladoc job keeps just crashing out.

Are you running scaladoc manually or this being run as part of publishSigned? I might have some idea of whats going on, hit similar issues with pekko-grpc Scala 3 migration.

scaladoc issues happen in publishSigned (needed for the javadoc jars)

Okay I will look into it tomorrow/day after

@mdedetrich It seems to be failing at:
(osgi / Compile / doc) Scaladoc generation failed
I'm using a Mac (Monterey OS).

@pjfanning
Is this same problem as https://github.com/apache/incubator-pekko-grpc/actions/runs/5100731826/jobs/9169230377?

@pjfanning
Is this same problem as https://github.com/apache/incubator-pekko-grpc/actions/runs/5100731826/jobs/9169230377?

Looks different to me

PR merged


add gallery level back to the equation

Type
🐛 Bugfix
Value
Allows us to do what we once could do.
Apologies @davidpmccormick

@davidpmccormick fancy letting me know that you knew it all along?


Formatted md renders different html than original md

Describe the bug
context
When I do mdformat .
expectation
I expected it to format all the md files.
bug
But instead, it stops with an error.
Here's an error message I ran into...
$ mdformat .
Error: Could not format "/app/docs/docker.md".

The formatted Markdown renders to different HTML than the input Markdown. This
is likely a bug in mdformat. Please create an issue report here, including the
input Markdown: https://github.com/executablebooks/mdformat/issues

problem
This is a problem for people wanting to reformat md files because there may be cases that are not reformatted in a good way.
Reproduce the bug

run mdformat . with the original file (docker.md) in the directory

I pasted my docker.md file here since I'm using the tool remotely via ssh and I'm too lazy to scp it over.
Details

# Docker

## How to remove extra project files from docker image

We use the `.dockerignore` file for this. It marks project files to skip when building the docker image.

1. Look into the image to find extra unneeded files

    1. Run a shell in the docker image

        ``` bash
        docker run -it image_name sh
        ```

    1. Look at the directory structure

        ``` bash
        ls
        ```

1. Add the extra files and paths in `.dockerignore`

1. Rebuild the image

## Cache mount

This helps speed up subsequent docker builds by caching intermediate files and reusing them across builds. It's available with docker buildkit. The key here is to disable anything that could delete the cache, because we want to preserve it. The cache mount is not going to end up in the docker image being built, so there's no concern about disk space usage.

Put this flag between `RUN` and the command

``` docker hl_lines="2"
RUN \
--mount=type=cache,target=/root/.cache
  pip install -r requirements.txt

For pip, the files are by default stored in /root/.cache/pip.  Pip caching docs
For apk, the cache directory is /var/cache/apk/. APK wiki on local cache
??? info "References"
- buildkit mount the cache
- proper usage of mount cache
- mount cache reference
Reducing the image size
There are methods to do this on many levels. All of these methods contribute to reduce the final image size, either by skipping generation of intermediate files or by removing them afterward. We list the commonly-recommended methods here although we opted to use cache mount instead, which speeds up image rebuilds. The methods discussed here may be more suitable for a CI environment.
Docker

Docker cache mount
We use this method instead of ones which disable caching. See cache mount above. There's no need to delete any files since they're in a cache mount that's not part of the docker image.

Python

Skip bytecode (.pyc) generation
Python docs on PYTHONDONTWRITEBYTECODE
=== "env variable"
 Set this environment variable

 ``` docker
 ENV PYTHONDONTWRITEBYTECODE 1
 ```

=== "command env"
 Set the `-B` flag for python

 ``` docker
 RUN python3 -B -m pip install -r requirements.txt
 ```

Pycache prefix and rm
Python docs on PYTHONPYCACHEPREFIX

Tell python to write .pyc files in a mirror directory
=== "env variable"
 Set this environment variable to make python store all pycache bytecode files under some directory

 ``` docker
 ENV PYTHONPYCACHEPREFIX=/root/.cache/pycache/
 ```

=== "flag"
 Use the commandline flag for python

 ``` docker
 RUN python3 -X pycache_prefix=/root/.cache/pycache/ -m pip install -r requirements.txt
 ```

Remove the files in the same RUN command by appending this to the end
&& rm -rf /root/.cache/pycache/

Pip

Don't compile python into byte code
Pass the flag into pip to skip generating pyc files during install
RUN pip install --no-compile -r requirements.txt

Disable caching
Pip docs on caching
=== "env variable"
 Set this environment variable

 ``` bash
 ENV PIP_NO_CACHE_DIR=1
 ```

=== "flag"
 Pass this flag into pip

 ``` bash
 RUN pip install --no-cache-dir -r requirements.txt
 ```

Clean build
Combineable flags can be passed into a docker or docker-compose build to force a clean build. See docker build options

Try to download the latest base image
docker-compose build --pull

Disable caching. Build everything
docker-compose build --no-cache

</p>
</details>

### List your environment

$ mdformat --version
mdformat 0.7.17 (mdformat_tables: 0.4.1, mdformat_mkdocs: 1.0.4, mdformat_gfm: 0.3.5)

Thanks for the issue!
Vanilla mdformat has no trouble formatting your text. The issue seems to only occur with the externally developed plugin you use, mdformat_mkdocs. You should file an issue here https://github.com/KyleKing/mdformat-mkdocs/issues

Hi! I'm the creator of mdformat-mkdocs (https://github.com/KyleKing/mdformat-mkdocs) and happened across this issue. Testing locally, the example file appears to format correctly and the bug(s) have been addressed:
uvx --with='mdformat-mkdocs==4.1.1' mdformat docker.md

I'm not sure if you are still interested in mdformat/mdformat-mkdocs, but if so, feel free to reach out if you run into any issues or have questions!


generator/linux: Use --ldpath linker flag for 5.9

Swift Package Manager's linker flag handling changed between 5.9 and 5.10.   The flags which work for 5.9 cause linking failures 5.10 and later, and vice versa:
https://github.com/swiftlang/swift-package-manager/issues/7222
This commit generates workaround flags for 5.9 and new-style flags for all other versions.
The EndToEnd tests currently cannot run in CI, so this change was tested locally. (Issue #145)

The basic 'hello world' example generated by swift package init built succesfully with 5.9.2, 5.10.1 and 6.0.2 SDKs on x86_64 and aarch64.
A more complex example using Vapor built succesfully with 5.9.2, 5.10.1.  6.0.2 failed because of the CShims problem reported in Issue #138.

@swift-ci test

@swift-ci test


cassandra/spanstore: speed up query by service name

The service_name_index table is orded on disk by start_time DESC so
reads by full partition key will return ordered by start_time. Removing
the order by in the query to list spans significantly improves span
listing performance, observed going from >20s per query to <500ms.

 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.

CREATE TABLE IF NOT EXISTS ${keyspace}.service_name_index (
    service_name      text,
    bucket            int,
    start_time        bigint,
    trace_id          blob,
    PRIMARY KEY ((service_name, bucket), start_time)
) WITH CLUSTERING ORDER BY (start_time DESC)

yeah, makes sense.

Coverage remained the same at 100.0% when pulling df8324e5167f9a6e877007303007856a3f20d612 on Zariel:improve-cassandra-listing-perf into 5d5a16b7039500274b5f63f3dbf895273278f671 on uber:master.

I did some experimentation to simulate whats going on and found that my assumption was incorrect and in fact the following is happening.
Where N is the query LIMIT and a partition is (key, bucket) and clustering key is time
When not using ORDER BY
Reads N results single partition, data is sorted by time as expected, result is a single partition
When using ORDER BY
Reads N results for EVERY partition, data is then sorted by time and top N results are returned, result is from every partition.
This surprises me somewhat, I think that when not using ORDER BY Cassandra is returning the first N results which are already sorted within a single partition but not across partitions. If the read goes across multiple partitions then the result is not sorted.
I think the reason why the read performance is so poor for this query is that the coordinator is having to read N * buckets results in memory to return N results which causes heap and gc pressure. Here it may be a better idea to do this sort and top N from the query node and we should see better read performance and better Cassandra heap usage at the expense of more complicated query code.
Tool to check read orders if anyone is interested, https://github.com/Zariel/cassandra-sorted-reads


Flaky Test test_cancel_cpu_intensive_tasks

https://github.com/quickwit-oss/tantivy/actions/runs/9127888173/job/25099130897?pr=2402
running 1 test
test core::executor::tests::test_cancel_cpu_intensive_tasks ... FAILED

failures:

failures:
    core::executor::tests::test_cancel_cpu_intensive_tasks

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 857 filtered out; finished in 0.03s

--- STDERR:              tantivy core::executor::tests::test_cancel_cpu_intensive_tasks ---
thread 'core::executor::tests::test_cancel_cpu_intensive_tasks' panicked at src/core/executor.rs:208:9:
assertion failed: counter.load(Ordering::SeqCst) > 0
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Still flaky
--- STDOUT:              tantivy core::executor::tests::test_cancel_cpu_intensive_tasks ---

running 1 test

--- STDERR:              tantivy core::executor::tests::test_cancel_cpu_intensive_tasks ---
thread 'search-test0' panicked at src/core/executor.rs:206:42:
called `Result::unwrap()` on an `Err` value: RecvError
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Rayon: detected unexpected panic; aborting

https://github.com/quickwit-oss/tantivy/actions/runs/9250798522/job/25445025346

#2409 fixes this.


Update docker image names in ci

It's unclear how this used to work, but a recent issue arose (see
Isse #74) where running ovn-scale-test using the CI scripts was
failing. This was tracked down to incorrect docker image names.
Closes Issue #74
Signed-off-by: Kyle Mestery<EMAIL_ADDRESS>

@huikang Your eyes here are needed.

@huikang I am going to merge this now to unblock CI, but I'd like you to still take a peek at this once you're back.


Switch to up_log

Starting from 1.14, Mathcomp now has up_log and enough lemmas to use for e.g. bintrees instead of rolling our own.

Closed in https://github.com/clayrat/fav-ssr/commit/8977922dd4d89333a811488423d6268da863680a


Fix a potential mismatch between test_id_list and gen_test_file_list

Hi, this is really a minor issue but it can be annoying when it happens. When using Keras, at the DNNGEN step, the function predict stores the label data in a dictionary text_x whose keys are the ids of the label files  in gen_test_file_list. Since the dict is unordered, it sorts the list of file ids to retrieve the order of the files in gen_test_file_list. However this assumes that gen_test_file_list is ordered alphabetically which is not always the case (it is sorted by date of modification, at least on my system). For instance, I'm trying to use magphase, which requires to modify the label files, and I'm doing this modification via parallel processing that breaks the natural oder of the label files. Then of course, things will not go very well when predicting the durations...
One fix could be to use an ordered dict but it's even simpler to just retrieve the file ids from the list of file names, that's the small modification proposed below.
Thanks.

Thanks, that's really annoying - worked for me.


Close Tabs with TabsRouter

Reproduction link
https://stackblitz.com/edit/angular-ilfpjx?file=src%2Fapp%2Fapp.html
Steps to reproduce
first: Click on the "x" icon to try to remove a tab.
What is expected?
Run the icon's click event and remove the tab.
What is actually happening?
Nothing

Environment
Info

ng-zorro-antd
9.3.0

Browser
Chrome

Another question of mine is how to set the default for a tab router. I tried to redirect to a route and hoped that the tab containing the same link would be active.

don't  use nz-tab-link, it's DIRECTIVE.

     {{ tab.name }}

use <nz-tabset nzLinkRouter>, and manually handle the fallback behavior on closing(like routing to the closest tab's routerUrl)


FK not shown

The foreign keys are missing in the index list.
SQL query to load the FKs:
SELECT
    *
FROM
    sys.foreign_keys AS fk

    INNER JOIN sys.tables AS t
    ON t.object_id = fk.parent_object_id
WHERE
    t.[name] = 'TABLENAME';

Feature was added in the latest release


Optimization: Dynamic y axis function

The Goal
Write a function to define the upper limit for the y-axis range based on the dataset. Deven already wrote code that accomplishes this; we want to break it out into a separate, reusable function.

Similar to the xbreaks function, something like this could work:
ydynam <- function(dataset, interval, col_number){
upper <- case_when(
interval == 1 ~ max(dataset[col_number]) + interval,
interval != 1 ~ ceiling(max(dataset[col_number])/interval)*interval)
}
All this does is define "upper" as a value that can then be plugged into other functions.   Upper then feeds into scale_y_continuous as it did before on the agency charts.  I tested it on some agency charts and it seemed to do the trick.

Awesome, this seems like a good game plan. Please follow the same steps as the xbreaks function:

move the function definition of xbreaks to just local_utils
import the function in the Rmd scripts using source
call the function as normal

For which charts should we implement this?  Worth discussing tomorrow?

Great, implemented in the agency charts here: https://github.com/regulatorystudies/Reg-Stats/commit/0b04c8a7ec5739da0bdf0a5bc7cdf486c48248f1


ExCL self-hosted github runner

Replicate the Human-in-loop CI using ideas from https://github.com/JuliaORNL/JACC.jl/blob/main/.github/workflows/ci-gpu-AMD.yaml
and implement for KORC

https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows

Implemented in the https://github.com/ORNL-Fusion/KORC/blob/main/.github/workflows/olivine.yml workflow


feat: remove paramiko and use openssh binary

- What I did
Removed paramiko which was used for reverse ssh in order to address this code scanning alert
- How I did it
Removed paramiko and used the binary.
- How to verify it
Use a sshnp command like the following
sshnp -f {atsign} -t {atsign} -h {host} -d {device} --legacy-daemon
- Description for the changelog
feat: remove paramiko and use openssh binary

@cpswan @XavierChanth I'm not sure what best practices for versioning and removing paramiko from poetry / requirements.txt are so some help there would be greatly appreciated.

I've set this to draft as I think we should have an arch discussion before pushing ahead with this. I'd like to better understand the pros and cons of removing python native capability in exchange for other dependencies.

After discussion in arch, decided to opt for python native solution.


Update mockito-scala, ... to 1.17.7

Updates

org.mockito:mockito-scala
org.mockito:mockito-scala-scalatest

from 1.17.5 to 1.17.7.
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!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.mockito" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.mockito" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #119.


Custom target: Raspberry Pi

An issue to hold an enhancment.
It is probable that the linux target is under way "somewhere" and it is hoped that the Windows 10 Core can also be targetted.
https://www.pxt.io/target-creation

https://github.com/Microsoft/pxt/issues/581#issuecomment-273983955

Wont fix for now. Feel free to provide a pull request.


Use conventional-changelog to generate changelog

Since you are already using the angular style commit message, it's very easy to use conventional-changelog to automate your releases. There are a lot of options, we recommend standard-version. But you are using github releases, there is also conventional-github-releaser.

Looks good, thanks


Adding a merge checklist to release PRs

This adds a pre-merge checklist to our Release PRs. I took this workflow and template from primer/react https://github.com/primer/react/pull/2365#issuecomment-1256377199
I tried my best to edit for things we'll be interested in, but please suggest changes if I missed anything

I don't really have a problem with it but wonder if we need it for every PR.

It should only run on the Release PRs like this one https://github.com/primer/view_components/pull/1433


Create a ragu-dom wrapper for VueJs

There are also a client for React: https://github.com/ragu-framework/ragu-client-react
The same need to be done for VueJs.

https://github.com/ragu-framework/ragu-client-vue


Clean up Spotify auth route

Make the Spotify auth route more robust by switching requests lib to axios. Also, may want to consider sending and using refresh token when hourly Spotify token expires.

The auth route is now using axios.


Standardize how we lint code locally

We need a solution for the linting problem. The goal is to standardize how we do linting locally so we never see the linting changes in PR in the future.

I think we should all use prettier. It is what is required by react open source.
Config
There are two config files needed:
Ignore file: https://github.com/facebook/react/blob/main/.prettierignore
Config file: https://github.com/facebook/react/blob/main/.prettierrc.js
Command
React supports two command: npm run prettier and npm run prittier-all. The first one only checks on your changes.
https://github.com/facebook/react/blob/main/package.json#L138
How it works
This file runs prittier with npm. https://github.com/facebook/react/blob/main/scripts/prettier/index.js
Packages Required
const prettier = require('prettier');
https://www.npmjs.com/package/prettier
Using with vs code or other editors
https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode

It looks like the ts-main branch does something very close to this already. We can stick with that :)


Edit and Help Menus do nothing

Original issue: BasicBrowser/#2
Edit:

[x] Undo
[x] Redo
[x] Cut
[x] Copy
[x] Paste
[x] Select All

Help:

[ ] Contents
[ ] Index
[ ] Search
[x] About

These are the default menus though, so if we can't get them to work just delete them.

Wow ok, just because it's a GeckoWebBrowser allows me to add the entire edit menu.


added svgs for walkthroughs

For https://github.com/microsoft/vscode-jupyter/issues/8782 & https://github.com/microsoft/vscode-jupyter/issues/8895

Codecov Report

Merging #9198 (66b293d) into main (fbc6dfb) will decrease coverage by 0%.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main   #9198   +/-   ##
=====================================
- Coverage     71%     71%   -1%
=====================================
  Files        382     382
  Lines      24852   24852
  Branches    4035    4035
=====================================
- Hits       17684   17679    -5
- Misses      5543    5552    +9
+ Partials    1625    1621    -4

Impacted Files
Coverage Δ

src/client/datascience/dataScienceSurveyBanner.ts
69% <0%> (-7%)
:arrow_down:

src/client/datascience/webviews/webviewHost.ts
81% <0%> (-2%)
:arrow_down:

...lient/datascience/jupyter/kernels/cellExecution.ts
74% <0%> (+<1%)
:arrow_up:

...lient/datascience/variablesView/notebookWatcher.ts
93% <0%> (+2%)
:arrow_up:


Which test database can be used to test bigger data sizes?

I'm talking about sizes described by control byte and next byte.
I haven't encountered any values that require $size >= 30 to decode.

Hmm, I am not sure we have one. That would be a good addition. In our own testing, we tend to test the decoder separately, e.g., this Python test.


chore(dagger): update module to dagger v0.12

Update engine version to v0.12.2
internal import "main/internal/dagger"
Update types: X -> dagger.X
Update Debug() signature since Terminal() now returns dagger.Container: https://github.com/dagger/dagger-go-sdk/commit/b15a9be1ce2844276f36f6d24f95070b38cdebd3

Hi @jpadams, it seems that the linter its failing because it loads a previous version of the engine that doesn't support go 1.22.
Could you please update this line https://github.com/chainloop-dev/chainloop/blob/103742fb98c26cc4ff9a9fb1cc2a900304c12e1a/.github/workflows/lint.yml#L63 to include DAGGER_VERSION=0.12.2 instead of 0.11.0
Thanks!


Simplified constructors in readable-stream

Will the simplified constructor feature land in readable-stream? I use it all the time, but can't use it in projects that need to support Node.js 0.12.
Tell me if I can help out cherry picking commits from iojs/io.js

Sorry, must have overseen #117. Closing


add test to confirm Viz.js can recover from an error

I noticed an issue with 1.2.0, and I'm trying to help in the ways I'm able :) :tada:
Viz.js 1.2.0 seems to stop working after it encounters an error. It may be related to lastError:
https://github.com/mdaines/viz.js/commit/60bc435028362576f540a6727cfc28b3688ed014#diff-012dd2b56a863a41776f3a519e6aaa56R19
This PR is me adding a test to demonstrate how to reproduce the issue. (Btw, by adding this test to the top of the input.js broke the rest of the tests in that file, because of this issue.)

Thanks for reporting this. I've prepared a shorter test case and pushed a fix which I'll release soon.


Wireguard doesn't reconnect, resilience issues

Context
My infrastructure is installed with OPNSense exclusively.
To connect between firewalls, I've installed Wireguard as LAN-to-LAN and everything works beautifully.
My issue is that when a router disconnects (unintended) or reboots (I have a key firewall reboot every night since it sometimes get stuck and access is complicated) not all Wireguard reconnect and I lose connection to a network.
Now I will mention one important aspect, one of my Wireguard VPNs is on a CARP interface, could that be an issue ?!
Setup
OPNSense A ======= OPNSense B ====== OPNSense C1
+== OPNSense C2 (Currently switched off during tests)
A is on a dynamic DNS setup and works great. WG on A has no endpoint IP, see further.
B has two (2) WG interfaces (different Eth, IP & ports), one to A and an other to C1/2. WG configs on C1 & C2 are identical.
B initiates connection to A as B is inside a private LAN, unreachable directly. Works mostly great.
B to C are both on separate private LANs (no WAN in between). Timeout on both B & C set to 15 seconds
C1 & C2 are using CARP interface as it's in HA mode, C2 is switched off as it seems to makes no difference and easier during debugging.
B endpoint points to Carp interface of C
Problem
When B is rebooted or goes offline, it will never recover B to C, and less often but sometimes B to A fails without recovering as well.  As soon as I press Save on B (reload WG) it connects fine.
Expected
When either side goes down and recovers, I assume it should re-initiate the connection or at least retry.
In the connection details, I see i.e 15 hours since last handshake.
OPNsense 20.7.4-amd64
Various hardware setups, old HP G7 & G8 servers.

Carp is unsupported as you cant control the outgoing IP and therefore no match. I already asked the author of WireGuard twice without a reply. It's only supported in Linux

@mimugmail Thanks for your feedback.
Any recommendation on best practice ?
Such as having dual WG connections to both OPNSense IP C1 & C2 bypassing the VIP, guess I would need to configure both as separate interfaces and add routing priorities to avoid gateway competition ?!


Grammatical Error

The section Log Data Anti-Pattern - Solution, paragraph 4 has the final sentence:

The API for blob storage enables you locate blobs in a container based on a name prefix: to locate all the blobs that contain queue log data for the hour starting at 18:00, you can use the prefix "queue/2014/07/31/1800."

This should be changed to:

The API for blob storage enables you to locate blobs in a container based on a name prefix: to locate all the blobs that contain queue log data for the hour starting at 18:00, you can use the prefix "queue/2014/07/31/1800."

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cbd87ab1-9a5b-4d23-05ce-d9d5f5bb74a0
Version Independent ID: 0bf2b20a-1830-02e5-67bd-a05074a7236b
Content: Azure storage table design patterns
Content Source: articles/storage/tables/table-storage-design-patterns.md
Service: storage
Sub-service: tables
GitHub Login: @tamram
Microsoft Alias: tamram

@royal -  Thanks again for bringing this to our attention and for updating the doc. The doc should be updated once it is merged. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Cannot access account every ten minutes or so

Lately I have been having problems with my connection to the car. After restarting the app, it can successfully connect to the car. However, 10/15 minutes later it starts complaining about the connection not working because “device is unavailable”. Restarting the app updates the details but the next refresh fails again and the connection is broken.
Any thoughts?

Addition;
It actually only works when I add the password again and restart the app. But only for a very brief period... like a minute or two.

Hi! What are your retry settings?

Every 1 minute (default)

Hi.
Just checked my app, and I have the same symptoms.
I can supply a new password and it validates it OK, but I get the 'No access to your Tesla account' error within seconds after restarting the app.
I have several other iOS apps polling the Tesla servers, so they are responding.
I'm at work now and do not have the ability to run the app on my lab Homey, but will do so as soon as i can to see it this provides more insight.

This only started recently I believe. I use the app quite extensively and didn’t notice it until a week or two ago.

Hmm.. Strange.
I ran the app in debug mode on my lab Homey, and set ut the connection to the car. Workes perfect..
Thinking this indicated a faulty install on the production Homey, I uninstalled the app, Reinstalled it and set ut the car from scratch. But ni sigar, On the production Homey is still failes moments after restarting the app.

So.. After checking my logs, I see the problem started after a power outage about 13 days ago..
So i figured that might have something to do with it. So å initiated a reastart of Homey, and after the restart, waited for all my apps to start. And the Tesla app now seems stable again.
So please initiate a controlled restart from the app and wait 10 minutes.
Settings->General->Restart Homey

Interesting finding! However; I have also done a graceful restart yesterday but without luck.. I’ll give it another shot

Okey.. Spoke too soon.
The app on both production and my Lab Homey stopped.
But now i got the debug from the Lab Homey.
Looks like its loosing the API key?
@irritanterik Can you get something from this:
2020-04-29 21:13:49 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>538,
distanceTraveled: 0 }
2020-04-29 21:15:50 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>212,
distanceTraveled: 0 }
2020-04-29 21:17:50 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>239,
distanceTraveled: 0 }
error in Tesla.prototype.login Error: no_password
at login (/lib/tesla.js:355:40)
at Tesla.login (/lib/tesla.js:28:10)
at checkTokenWithRequest.catch (/lib/tesla.js:62:76)
at
2020-04-29 21:20:47 [log] [ManagerDrivers] [ev] [0] invalid_user_pasword event triggered
2020-04-29 21:20:47 [log] [ManagerDrivers] [ev] [0] Device unavailable due to invalid account / username / password
2020-04-29 21:20:47 [log] [ManagerDrivers] [ev] [0] error from Api, counting 1 to max 5
2020-04-29 21:20:47 [log] [ManagerDrivers] [ev] [0] trackLocation Api error
2020-04-29 21:20:47 [log] [ManagerDrivers] [ev] [0] trackController 1

A bit more info.
It seems the token is not invalid. After restarting the app it connects using the same token as before.

Looks like the app thanks the token is no longer valid (could be timing issue with the expiration validation check) and tries to pull a new token (which fails since the app does not store the password - this change started all the losing connection issues).

So would be nice if you both could confirm the stored token is not expired nor invalidated and accepted by Tesla after an app restart

Let me know how to gather the logs and I’m happy to verify.
To add info on how to make it work;
-Re-enter the password for the car
-wake up the car through the official Tesla app
-restart the Tesla homey app
It then is able to connect but only briefly.

I can confirm the token is not expired or invalid. The app connects successfully using the same token after restarting but quickly runs into this issue of trying to log in.

here is a complete log from start until failing then restarting and then failing again:
(I think i’ve anonymized everything, but if you see any sensitive data, please just delete this post)
`─────────────── Logging stdout & stderr ───────────────
2020-04-29 20:41:33 [log] [ManagerDrivers] [ev] Succesvol got grant in pairing
found a car: { id: 710344,
vehicle_id: 624,
vin: '',
display_name: 'Wikene',
option_codes: 'AD15,MDL3,PBSB,RENA,BT37,ID3W,RF3G,S3PB,DRLH,DV2W,W39B,APF0,COUS,BC3B,CH07,PC30,FC3P,FG31,GLFR,HL31,HM31,IL31,LTPB,MR31,FM3B,RS3H,SA3P,STCP,SC04,SU3C,T3CA,TW00,TM00,UT3P,WR00,AU3P,APH3,AF00,ZCST,MI00,CDM0',
color: null,
tokens: [ '9b1802', '4cb2e9' ],
state: 'online',
in_service: false,
id_s: '710343',
calendar_enabled: true,
api_version: 7,
backseat_token: null,
backseat_token_updated_at: null }
2020-04-29 20:41:38 [log] [ManagerDrivers] [ev] pairing: vehicle added { data: { id: '' },
name: 'Wikene',
icon: 'icon_x.svg',
store:
{ grant:
{ access_token: '11aed4ac',
token_type: 'bearer',
expires_in: 3888000,
refresh_token: '7aae3695',
created_at:<PHONE_NUMBER> },
username<EMAIL_ADDRESS>},
settings: { password: '' } }
2020-04-29 20:41:38 [log] [ManagerDrivers] [ev] [0] ##### TESLA onInit ##### { Homey: '4.1.0', App: '2.1.2', Device: '*******' }
2020-04-29 20:41:38 [log] [ManagerDrivers] [ev] [0] settings { password: '',
locationPolling: true,
tripTracking: true,
locationIntervalDriving: 30,
locationIntervalParked: 120,
batteryPolling: true,
batteryInterval: 20,
retriggerRestrictTime: 10,
retriggerRestrictDistance: 1,
tokenRetry: true,
tokenRetryInterval: 1,
apiAccess: false }
{ access_token: '11aed4ac',
token_type: 'bearer',
expires_in: 3888000,
refresh_token: '7aae3695',
created_at:<PHONE_NUMBER> }
2020-04-29 20:41:40 [log] [ManagerDrivers] [ev] [0] trackController 1
2020-04-29 20:41:42 [log] [ManagerDrivers] [ev] [0] battery 57
2020-04-29 20:41:46 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>166,
distanceTraveled: 0 }
2020-04-29 20:41:46 [log] [ManagerDrivers] [ev] [0] trackController setting { location: 120, battery: 1200 }
2020-04-29 20:43:47 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>909,
distanceTraveled: 0 }
2020-04-29 20:45:48 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>438,
distanceTraveled: 0 }
2020-04-29 20:48:47 [log] [ManagerDrivers] [ev] [0] error from Api, counting 1 to max 5
2020-04-29 20:48:47 [log] [ManagerDrivers] [ev] [0] trackLocation Api error
2020-04-29 20:49:48 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>149,
distanceTraveled: 0 }
2020-04-29 20:51:48 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>583,
distanceTraveled: 0 }
2020-04-29 20:53:47 [log] [TeslaApp] 20:53:47 Flow action set charge mode ***********
2020-04-29 20:53:49 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>206,
distanceTraveled: 0 }
2020-04-29 20:53:49 [log] [TeslaApp] 20:53:49 Flow action set charge limit ***********
2020-04-29 20:55:49 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>208,
distanceTraveled: 0 }
2020-04-29 20:57:49 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>175,
distanceTraveled: 0 }
2020-04-29 20:59:49 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>349,
distanceTraveled: 0 }
2020-04-29 21:01:48 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>326,
distanceTraveled: 0 }
2020-04-29 21:01:48 [log] [ManagerDrivers] [ev] [0] battery 57
2020-04-29 21:03:49 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>219,
distanceTraveled: 0 }
2020-04-29 21:05:50 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>204,
distanceTraveled: 0 }
2020-04-29 21:07:49 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>227,
distanceTraveled: 0 }
2020-04-29 21:09:49 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>397,
distanceTraveled: 0 }
2020-04-29 21:11:59 [log] [ManagerDrivers] [ev] [0] error from Api, counting 1 to max 5
2020-04-29 21:11:59 [log] [ManagerDrivers] [ev] [0] trackLocation Api error
2020-04-29 21:13:49 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>538,
distanceTraveled: 0 }
2020-04-29 21:15:50 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>212,
distanceTraveled: 0 }
2020-04-29 21:17:50 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 32342971.3,
timeSinceTrigger:<PHONE_NUMBER>239,
distanceTraveled: 0 }
error in Tesla.prototype.login Error: no_password
at login (/lib/tesla.js:355:40)
at Tesla.login (/lib/tesla.js:28:10)
at checkTokenWithRequest.catch (/lib/tesla.js:62:76)
at
2020-04-29 21:20:47 [log] [ManagerDrivers] [ev] [0] invalid_user_pasword event triggered
2020-04-29 21:20:47 [log] [ManagerDrivers] [ev] [0] Device unavailable due to invalid account / username / password
2020-04-29 21:20:47 [log] [ManagerDrivers] [ev] [0] error from Api, counting 1 to max 5
2020-04-29 21:20:47 [log] [ManagerDrivers] [ev] [0] trackLocation Api error
2020-04-29 21:20:47 [log] [ManagerDrivers] [ev] [0] trackController 1
--- INFO: com.tesla has been killed ---
2020-04-29 22:51:44 [log] [ManagerDrivers] [ev] [0] ##### TESLA onInit ##### { Homey: '4.1.0', App: '2.1.2', Device: '' }
2020-04-29 22:51:44 [log] [ManagerDrivers] [ev] [0] settings { password: '',
locationPolling: true,
tripTracking: true,
locationIntervalDriving: 30,
locationIntervalParked: 120,
batteryPolling: true,
batteryInterval: 20,
retriggerRestrictTime: 10,
retriggerRestrictDistance: 1,
tokenRetry: true,
tokenRetryInterval: 1,
apiAccess: false }
{ access_token: '11aed4ac',
token_type: 'bearer',
expires_in: 3888000,
refresh_token: '7aae**********3695',
created_at:<PHONE_NUMBER> }
2020-04-29 22:51:46 [log] [ManagerDrivers] [ev] [0] trackController 1
2020-04-29 22:51:48 [log] [ManagerDrivers] [ev] [0] battery 57
2020-04-29 22:52:51 [log] [ManagerDrivers] [ev] [0] error from Api, counting 1 to max 5
2020-04-29 22:52:51 [log] [ManagerDrivers] [ev] [0] trackLocation { isMoving: false,
distanceMovedSinceTrigger: 0,
timeSinceTrigger:<PHONE_NUMBER>597,
distanceTraveled: 0 }
2020-04-29 22:52:51 [log] [ManagerDrivers] [ev] [0] trackController setting { location: 120, battery: 1200 }
error in Tesla.prototype.login Error: no_password
at login (/lib/tesla.js:355:40)
at Tesla.login (/lib/tesla.js:28:10)
at checkTokenWithRequest.catch (/lib/tesla.js:62:76)
at
2020-04-29 22:55:51 [log] [ManagerDrivers] [ev] [0] invalid_user_pasword event triggered
2020-04-29 22:55:51 [log] [ManagerDrivers] [ev] [0] Device unavailable due to invalid account / username / password
2020-04-29 22:55:51 [log] [ManagerDrivers] [ev] [0] error from Api, counting 1 to max 5
2020-04-29 22:55:51 [log] [ManagerDrivers] [ev] [0] trackLocation Api error
2020-04-29 22:55:51 [log] [ManagerDrivers] [ev] [0] trackController 1`

Now it works for 3 hours straight. I genuinely do not know what triggers this behavior..

I also have the problem with homey telling me to log in again. My tesla is in the garage and the 4g/lte is not that great down there. But the Tesla app manages to wake up the car and read everything, but homey fails. Not sure why. The trick to wake the car with the Tesla app and then restart the Homey app works and I will get a reading of battery etc

This must be something triggered from a response from Tesla servers. Mine too has worked perfectly for two days now.

I guess we can call this one resolved. Haven’t received any disconnect messages ever since so I take it this was a problem on the Tesla site. Gonna close this one for now.
Thanks everyone involved!


[firebase_auth] android release build failing

Describe the bug
I am trying to build an and android release version running the following command.
flutter build apk --no-shrink  --split-per-abi
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':shared_preferences:verifyReleaseResources'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > Android resource linking failed
     /Users/mattfleshman/.gradle/caches/transforms-2/files-2.1/77a5d7c3f5c22bab0d3c60446f5dad5f/core-1.0.0/res/values/values.xml:57:5-88:25: AAPT: error: resource android:attr/fontVariationSettings not found.

     /Users/mattfleshman/.gradle/caches/transforms-2/files-2.1/77a5d7c3f5c22bab0d3c60446f5dad5f/core-1.0.0/res/values/values.xml:57:5-88:25: AAPT: error: resource android:attr/ttcIndex not found.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 6s
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done                       7.6s
The built failed likely due to AndroidX incompatibilities in a plugin. The tool is about to try using Jetfier to solve the incompatibility.
Building plugin firebase_auth...
Running Gradle task 'assembleAarRelease'...
Running Gradle task 'assembleAarRelease'... Done                    0.9s
✓ Built build/app/outputs/repo.
Building plugin firebase_auth_web...
Running Gradle task 'assembleAarRelease'...
Running Gradle task 'assembleAarRelease'... Done                    0.7s

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/mattfleshman/development/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth_web-0.1.2/android/build.gradle' line: 22

* What went wrong:
A problem occurred evaluating root project 'firebaseauth_web'.
> Failed to apply plugin [id 'com.android.library']
   > Minimum supported Gradle version is 5.4.1. Current version is 4.10.2. If using the gradle wrapper, try editing the distributionUrl in /Users/mattfleshman/development/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth_web-0.1.2/android/gradle/wrapper/gradle-wrapper.properties to gradle-5.4.1-all.zip

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 0s

The plugin firebase_auth_web could not be built due to the issue above.

pubspec.yaml snippet
environment:
  sdk: ">=2.6.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  firebase_core: ^0.4.4+3
  firebase_crashlytics: ^0.1.3+3
  #firebase_analytics: ^5.0.11
  firebase_messaging: ^6.0.13
  firebase_auth: 0.16.0
  bloc: ^3.0.0
  flutter_bloc: ^3.2.0
  meta: ^1.1.6
  equatable: ^1.0.0
  shared_preferences: ^0.4.2
  flutter_native_timezone: ^1.0.4
  sprintf: "^4.0.0"
  get_it: ^4.0.1
  email_validator: '^1.0.0'
  geolocator: ^5.3.1
  google_maps_flutter: ^0.5.25+3
  dio: ^3.0.9
  flutter_localizations:
    sdk: flutter
  google_sign_in: ^4.4.0
  font_awesome_flutter: ^8.8.1

Flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.12.13+hotfix.9, on Mac OS X 10.15.2 19C57, locale en-US)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
[✓] Android Studio (version 3.5)
[!] IntelliJ IDEA Ultimate Edition (version 2019.3.3)
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] Connected device (1 available)

! Doctor found issues in 1 category.

Hi @mflesh1
Can you please try possible solution
Thank you

@TahaTesser my gradle properties already has a higher version.
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-5.6.2-all.zip

Hi @mflesh1
Can you please provide flutter build apk --no-shrink --split-per-abi --verbose?
Thank you

@TahaTesser I ended up removing the dependency from the project as I did no need it. I am closing but not sure if the issue would still persist.


invisible armours

seems these become invisible on player death

Can't reproduce. Can you send a game log and tell me how to reproduce the issue?

seems to be a compatibility issue with Origins.
running:
fabric-api-0.25.4+1.16
Origins-1.16.4-0.4.4
wolves-with-armor-1.5.2-1.16.2
maybe i'm hoping for too much from a mod not made for 1.16.4 :/

Can confirm problem with Origins. Can reproduce running:
fabric-api-0.31.0+1.16
immersive-portals-0.80-mc1.16.5-fabric
Origins-1.16.5-0.5.1
Origins-Classes-1.16.5-1.1.1
PetOwner-1.7.1-1.16.2+
respawnablepets-1.16.5-1
wolves-with-armor-1.5.2-1.16.2
Armors play nicely with other mods (PetOwner, respawnablepets), but not Origins. Horse armors show no issue with Origins though, normal visibility/respawn.
Side note for respawnablepets: the armor also becomes invisible when the wolf (not player) respawns with Origins. Without Origins and with respawnablepets, armor is respawned as well.

Update: The armor becomes visible once I de-equip it, and the re-equip it. Maybe this will help if you get the same glitch.

I'll look into this in a bit, might be a CCA issue (my deps are pretty outdated), thanks for the info 👍


Get-PnPList returns SecurableObject instead of List

Reporting an Issue or Missing Feature
Issue
Expected behavior
Getting a Microsoft.SharePoint.Client.List as per the docs https://github.com/OfficeDev/PnP-PowerShell/blob/master/Documentation/GetPnPList.md
Actual behavior
Gets a Microsoft.SharePoint.Client.SecurableObject
Steps to reproduce behavior
Connect-PnPOnline -Url "https://contoso.sharepoint.com"
$list = Get-PnPList "Shared Documents"
$list.GetType()

Which version of the PnP-PowerShell Cmdlets are you using?

[x] PnP PowerShell for SharePoint 2013
[ ] PnP PowerShell for SharePoint 2016
[ ] PnP PowerShell for SharePoint Online

What is the version of the Cmdlet module you are running?
2.9.1611.0
How did you install the PnP-PowerShell Cmdlets?

[ ] MSI Installed downloaded from GitHub
[x] Installed through the PowerShell Gallery with Install-Module
[ ] Other means

I think you may be confusing the actual type (shown in the Name column) with the base type. You can
see below that the full name of the type returned from Get-PnPList is Microsoft.SharePoint.Client.List as expected.
Is there something that's not working when you use the object returned from Get-PnPList directly?
PS H:\> $l = Get-PnPList -Identity Documents
PS H:\> $l.GetType()

IsPublic IsSerial Name                 BaseType
-------- -------- ----                 --------
True     False    List                 Microsoft.SharePoint.Client.SecurableObject

PS H:\> $l.GetType().FullName
Microsoft.SharePoint.Client.List

@casselc you are totally right. The reason for me positing this issue was that I couldn't access any members of that list object such as Title.


Inconsistent font size in a comment with inline code blocks

Extension version: 0.38.1
VSCode Version: 1.65.2
OS: macOS 12.3

Steps to Reproduce:

Create a comment with some inline code blocks and a regular text, e.g. "`noexcept` for these 3 `register` functions?"

As you see, the code blocks are way larger than the regular text.

BTW. Why isn't there the background color change for the code blocks in the comments? Would be nice to have, although it's a totally different issue, I'd say.

@alexr00 I believe markdown renderer only generates html and does not provide default styling. Try looking into the css for the comment widget

It looks like this was done intentionally. Here's what I think the reasoning is:

Comments are shown in the editor, where by default the font size is 14px
Non-code text in VS Code is 13px
So, non code text in a comment is 13px
But, since code in a comment is still within an editor, it might look small, so make it 14px to match the editor.

Some original discussion: https://github.com/microsoft/vscode-pull-request-github/issues/168
I will get some more feedback and see what a majority of people think.

Feedback is that all codeblocks int he comment widget should be 13px (same size as non-codeblock text).

@alexr00 at least like that. Today I tried to set the font size for the rest of the UI, but it seems that I'm only in control of the code block font size. Hence my experience is always bad because the UI font is always hardcoded, but the code block font size can be configured.

The intended new behavior will be that the size of the codeblock font will match the size of the surrounding non-codeblock font. You will be able to change the size of all workbench font, including codeblocks, by zooming.

The intended new behavior will be that the size of the codeblock font will match the size of the surrounding non-codeblock font. You will be able to change the size of all workbench font, including codeblocks, by zooming.

It is already nice to have the fonts matching. But one question is having them match, another to have them customizable (even when they have to be the same). Look. If I set the font size of my code, say, 20px and I want my comments to have a size of 24px. This means that I will have to zoom in enough, to make the default font size (13px) look like 24px. When I zoom in, the rest will also increase the size of the text, and no longer be something I wanted with 20px. I hope I communicate my thoughts clean and understandable enough 🙂

@arsdever makes sense, thank you for clarifying.
The comment widget inherits it's font size from the workbench font size. This is true for almost all of the workbench (which is basically everything that isn't the editor part), so we would not have a separate setting for just the font size of the comment widget.
There is a feature request to have a setting for the workbench font size: https://github.com/microsoft/vscode/issues/519.

not sure if there's anything we can do about the extra space between normal text and code here, but that would look nice now that they're the same font size
![Screen Shot 2022-04-28 at 10 54 34 AM](https://user-images.githubusercontent.com/29464607/165816648-babdde55-
0831-402c-a686-675e71799c05.png)


WIP: Emptydir and security context

WIP for #7925
Very rough, mostly to track the downstream work I'm doing in openshift

I also expect this to fail until the mounttest-user image is pushed to gcr.io

@thockin This is the next one I'm going to bug you about -- I'm going to refactor this code but I'm carrying a patch for this in OpenShift and so it makes sense for me to begin refactoring from this state.

@pmorie - this one could use a little love too... likely goes with the other work?

@mrry550 This PR is likely not going in.  #12944 supercedes it.

Thx @pmorie - I'll watch over there instead. ;)

Superceded by #14192, closing out.


Responses with error status codes are still stored

Need some sort of error checking here https://github.com/timonus/TJImageCache/blob/master/TJImageCache/TJImageCache.m#L146. Probably should check if the resulting data results to a valid image instead of the status code, since any status code could still return image data.

For example, this URL returns a 403 and invalid image data.

Done in https://github.com/timonus/TJImageCache/commit/6917e1ac99abb8e2cae8653276abc19b433b5d84


fix: treat thrown responses as mocked responses

Related to https://github.com/mswjs/msw/pull/2135

Throwing a Response instance in a request listener is now equivalent to calling request.respondWith(thrownResponse).
interceptor.on('request', () => {
  throw new Response('hello world')
})

Released: v0.28.2 🎉
This has been released in v0.28.2!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i @mswjs/interceptors@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.


make: *** [Makefile:322：tf_encrypted/operations/secure_random/secure_random_module_tf_2.13.0.so]; make build error

description
I try to install tf-encryption with the following steps.
git clone https://github.com/tf-encrypted/tf-encrypted.git
cd tf-encrypted
pip install -e .
make build

However, I got this ERROR feedback when  execute make build, and i don't know the reason.
(tfe) $ pip install -e .
......
Successfully installed MarkupSafe-2.1.3 astunparse-1.6.3 flatbuffers-23.5.26 gast-0.4.0 google-auth-2.22.0 google-auth-oauthlib-1.0.0 google-pasta-0.2.0 h5py-3.9.0 keras-2.13.1 libclang-16.0.6 numpy-1.24.3 oauthlib-3.2.2 onnx-1.14.1 opt-einsum-3.3.0 protobuf-3.20.3 pyyaml-6.0.1 tensorboard-2.13.0 tensorboard-data-server-0.7.1 tensorflow-2.13.0 tensorflow-estimator-2.13.0 tensorflow-io-gcs-filesystem-0.33.0 termcolor-2.3.0 tf-encrypted tf2onnx-1.15.1 wrapt-1.15.0
(tfe) $ make build
mkdir -p tf_encrypted/operations/secure_random
g++ -shared operations/secure_random/secure_random.cc -o tf_encrypted/operations/secure_random/secure_random_module_tf_2.13.0.so \
        -fPIC -I/home/hjw/lcy/anaconda3/envs/tfe/lib/python3.8/site-packages/tensorflow/include -D_GLIBCXX_USE_CXX11_ABI=1 --std=c++17 -DEIGEN_MAX_ALIGN_BYTES=64 -L/home/hjw/lcy/anaconda3/envs/tfe/lib/python3.8/site-packages/tensorflow -l:libtensorflow_framework.so.2 -std=gnu++17 -O2 -I/home/hjw/lcy/tf-encrypted/build/include -L/home/hjw/lcy/tf-encrypted/build/lib -lsodium
operations/secure_random/secure_random.cc: In function ‘tsl::Status RandomUniformShapeCommon(tensorflow::shape_inference::InferenceContext*)’:
operations/secure_random/secure_random.cc:19:18: error: ‘OK’ is not a member of ‘tsl::Status {aka absl::lts_20230125::Status}’
   return Status::OK();
                  ^~
operations/secure_random/secure_random.cc: In function ‘tsl::Status I128RandomUniformShapeCommon(tensorflow::shape_inference::InferenceContext*)’:
operations/secure_random/secure_random.cc:47:18: error: ‘OK’ is not a member of ‘tsl::Status {aka absl::lts_20230125::Status}’
   return Status::OK();
                  ^~
operations/secure_random/secure_random.cc: In lambda function:
operations/secure_random/secure_random.cc:106:24: error: ‘OK’ is not a member of ‘tsl::Status {aka absl::lts_20230125::Status}’
         return Status::OK();
                        ^~
make: *** [Makefile:322：tf_encrypted/operations/secure_random/secure_random_module_tf_2.13.0.so] error 1

Hi,
what's the version of tensorflow you are using? I also encountered this problem when my tensorflow is 2.13.1. Then I tried tensorflow 2.9.1 (suggested in requirements.txt) and it works.


Improve README content rendering and styles

For some gems on gem.sh the show page renders very weird and broken looking READMEs, we should look into what's causing it and see if there might be a more relaxed Markdown parser which can also better recover from a malformed markdown file.
It might also be that some of our styles are leaking into the rendered markdown content, maybe we need to better scope the selectors.
Example: https://gem.sh/gems/activerecord/v7.0.6

One such issue seems to be related to code blocks with a language specified. I was reviewing a simple gem I wrote and found the readme was looking in disarray.
For example, when the following codeblocks specifying ruby are encountered:

it renders as

and

Link to my example:

https://gem.sh/gems/output_attributes/v1.0.1
https://github.com/ttilberg/output_attributes/

I believe the ActiveRecord is currently suffering the same issue. Fixing the language detection for code blocks might go a long way to resolving the output.

@ttilberg improved this a bit in #44, but I think there are still some thing we can improve, like:

the character escaping mentioned in #44
code highlighting in code blocks
styles of the stylesheet itself

Also some more advanced features could be cool:

the ability to copy code from code blocks and the
Auto-reference constants to the docs page when they are mentioned in the README


[Question] Can groupby agg scale in HPAT?

Hi,
I am trying to use HPAT to accelerate data science workloads, especially the ETL process.
The data frame I am using contains 21,721,922 rows and 45 columns. All the data entries use float64 dtype. There is no missing data after cleaning.
I was putting the following code into an HPAT decorated function. It simply groups the data frame by ``year" and calculates the average number for each year. I am tracking the execution time of the groupby-agg operator.
    t0 = time.time()
    tmp1 = df.groupby('YEAR')['INCTOT'].mean()
    tt = time.time() - t0

I am using a server with 2 x Intel(R) Xeon(R) CPU E5-2699 v4 CPU, where it has 44 cores in total.
The results look like this:
Baseline is to use Pandas only without HPAT.

Num of cores
groupby-agg time (sec.)

baseline
0.227021694

1
1.437

2
1.39

3
1.398

4
1.427

11
1.51

22
1.794

44
2.838

We observe that when the number of processes used increases, the time spent on groupby-agg also increases. Since GroupBy-agg is a simple map-reduce parallel pattern which should be able to parallelize, the observation is a bit weird to me as far as I understood.
Second, even we only use one thread, applying HPAT gives slowdown compared to pandas.
The groupby-count results of my dataset. Note that in each year, plenty of data entries exist--- there should have sufficient parallelism.

YEAR
count

1970
1486744

1980
8746006

1990
1906165

2000
2199860

2010
2494822

Am I missing something? Could you give some suggestions on how should I do to accelerate the groupby-agg operation using HPAT?
Thank you so much.
Best regards,
Hongyuan Liu

Thank you @bigwater! We're currently working on groupby


Pastanaga Editor: DraftJS toolbar shows up in multiple lines when text is selected at the edges

Steps to reproduce:

Go to https://plone-react.kitconcept.io/front-page/edit
login as admin
Select "this" (last term on the first paragraph)

-> Expected behavior: toolbar should always show in one line.

Related to #170

Discussion at Ploneconf 2018 in Tokyo with @albertcasado @sneridagh @tisto @robgietema:
The toolbar should stay in one line and move to the left / right so that it is always displayed in full.
Albert's design does not contain the arrow at the bottom that could make this more complicated, so we should get rid of it.

The current situation

Narrow to the left side is bad also

volto-slate partially solves this problem by detecting the left edge and also zindexing above the sidebar.
Though I think we need better UI for such big toolbars.


Use TCA dependency macro

The 1.5 version of TCA has a dependency macro available by default. This can be handly and clean up a lot of code.
Steps:

all dependencies must be struct
all closures defined as public var
unimplemented testKey comes for free so it must be deleted
public initializer comes for free so it must be deleted
default values must be provided

All dependencies have been updated


Add AST generation

[x] Add AST generation, fixes #33
[x] Run tests/fuzzing on Python 3.10 as well
[ ] More tests are required!

Still some tests to add as well

Coverage right now:
All files:

Functions in AST:

Tests for eval_literal.py are good enough - these are the only uncovered lines:

Lines
Reason

This code path will only happen if there's a bug in NumberParser

None of the code uses this part of this internal method (it's just there for consistency/future use for now)

This code path will only happen if there's a bug in NumberParser

This should probably be pragma: no covered

This code path will only happen if there's a bug in NumberParser

This should probably be pragma: no covered

^^ Done in 19b66a2791171a480df7da6f23ec3942008d4c6d

The remaining uncovered functions are all internal or one-liners

Finally done, branch deleted!