docs: Extend simple example to handle failed request

Hey there,
I recently stumpled across a misunderstanding of the library and the referenced simple example.
Since the example contains an error handling with respect to the UI, it should also correctly recognize occurring errors. As mentioned in the docs, fetch and other clients do not throw by default an error - so I added the error handling to the example within the result handler.

I would want to keep the simple example as simple as possible (minimal lines of code). fetch has this unfortunate spec that 4xx and 5xx are not treated as failed promises. Maybe it would be better to just use axios or ky for this example?

Fair point. I changed the PR to use Axios instead

interesting that we had axios in the dependencies already 😅

:tada: This PR is included in version 4.0.0-alpha.20 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


docs: fix admission control sample usage

Commit Message: docs: fix admission control sample usage
Docs Changes: Please see discussion in Issue here

should we also backport this?

@daixiang0  makes sense altho probably not very high priority atm - i would be happy to review backport PRs once this one has landed

do you have any pointers for where I would make this change?

yep if you:
# git grep literalinclude docs/

you should see where existing configs are included - the config file will need to be a full "bootstrap" config and will be automatically validated and tested

@phlax , I've moved the config out to another file and fixed a few things in the docs.
I tried adding some garbled text to the config to see whether the CI would reject the config as invalid, but it still passed. I tried that with this newly added yaml (_include/admission-control-filter.yaml), and also with an existing config (_include/bandwidth-limit-filter.yaml), both passed.
Does the validation step exist? Am happy to set that up if not, or maybe I'm missing something? Lmk. Thanks

Does the validation step exist?

should be automatic - it is tested in 2 ways - how did you try to test it ?

how did you try to test it ?

./ci/run_envoy_docker.sh './ci/do_ci.sh docs

the first test (validation) is run with:
# bazel run "${BAZEL_BUILD_OPTIONS[@]}" //configs:example_configs_validation

the second - im not sure off hand how it is triggered, but it requires a built binary and is run later in CI - this one starts a server with each of the configs

Thanks @phlax. Happy to help with any other pipeline/build/CI issues as they arise; or any larger pieces of work too.


expose kubeconfig as terraform output

This makes the output of terraform output a bit more verbose,
but allows to use kubeconfig when including kube-hetzner into
other terraform projects without having the path depend on the
modules source. It's local in this example but could just as well
be a remote github repository.
Example terraform code:
module "kube-hetzner" {
  source = "./kube-hetzner"

hcloud_token = "hahaha-not-really"
public_key   = "/home/me/.ssh/my-first-key.pub"
private_key  = null
location                  = "fsn1"
agent_server_type         = "cpx21"
control_plane_server_type = "cpx11"
lb_server_type            = "lb11"
servers_num               = 2
agents_num                = 2
hetzner_ccm_containers_latest = true
hetzner_csi_containers_latest = true
}

resource "local_file" "kubeconfig" {
    content  = module.kube-hetzner.kubeconfig
    filename = "kubeconfig.yaml"
}

output "controlplanes_public_ip" {
  value       = module.kube-hetzner.controlplanes_public_ip
}

Ah, that didn't work as expected. terraform validate ran successfully locally because kubeconfig.yaml already existed locally. Going to look at it again later on

Seems interesting! Curious to see where this leads.

@mysticaltech This got a bit bigger than expected:

It would be great to have kubeconfig be a part of terraforms dependency graph & state. This would enable multi-user setups (because it does not depend on local disk files anymore) and to use kubeconfig to authenticate hashicorp/kubernetes while still passing terraform validate - I think thats not possible with the current solution.
A drawback is that we can't deploy CCM, CSI & Traefik from our local host, because we don't have kubeconfig.yaml locally while provisioning the control plane, only afterwards.
so we just run kubectl apply on the control plane itself, after k3s is ready
but to do so, we need to deploy all manifests.  I've merged the patches into a single kustomization.yaml file, because that makes the deployment of those files to the control-plane server easier.
we could also put the traefik config into the same kustomization file, which would save us one of the file provisioner blocks.

What do you think? Is this a feasible approach?
This is still a draft atm, because it does not work with SSH agents yet, because the remote provider used does not support it yet,  waiting for https://github.com/tenstad/terraform-provider-remote/pull/31 :D

Definitely could work! It also seems like a cleaner way of doing things, not dispersed between local and remote.

https://github.com/tenstad/terraform-provider-remote/pull/31 has been merged :-)

Well done @phaer! So that makes the data 'remote_file'  workable in all use cases correct? :) This PR is huge but seems awesome.
About the new OS, hopefully very soon! I will keep you posted on the corresponding issue.

@mysticaltech Hi, I think we should wait untill terraform-provider-remote cuts a new release, because I don't think binaries are available before that, so users would need to build the provider themselves.
Regarding the new OS: I did some experiments with Ranchers cOS-toolkit as well as Fedora CoreOS, but nothing to release yet. OpenSuSE MicroOS looks interesting as well, but I wont have time too look into it properly for at least a week

Good to hear, thanks @phaer!

A new release has been published: https://github.com/tenstad/terraform-provider-remote/releases/tag/v0.0.23
Should we merge that as is? I am going to try to rebase this onto the staging branch this week.

superseeded by  #46


Introduce http listeners

public interface HttpListener {
    default void beforeFirstHttpCall() {
    }

    default void beforeHttpCall(String requestMethod,
                                String passedUrl,
                                String fullUrl,
                                HttpHeader requestHeader,
                                HttpRequestBody requestBody) {
    }

    default void afterHttpCall(String requestMethod,
                               String passedUrl,
                               String fullUrl,
                               HttpHeader requestHeader,
                               HttpRequestBody requestBody,
                               HttpResponse response) {
    }
}

beforeFirstHttpCall can be used to automatically bootstrap an embedded server

@MykolaGolubyev what's the usecase you have in mind for the beforeFirst and for the before/after methods?  Shouldn't we also include a afterLast so that anything you setup in beforeFirst can be torn down?

@tsiq-karold the intention is to let people to bootstrap an embedded server.  Additionally is to trace calls.
I thought about afterTheLastCall. Not sure how to reliably implement it except using onshutdwon kind of handler (similar to reports gen). On the other hand I assume that an embedded server will shutdown itself on exit anyway.

@tsiq-karold the intention is to let people to bootstrap an embedded server. Additionally is to trace calls.

I get the need for the a BeforeFirst, I'm not sure I see what you would do in the beforeHttpCall though, what did you mean by trace?

I thought about afterTheLastCall. Not sure how to reliably implement it except using onshutdwon kind of handler (similar to reports gen).

Similar to report gen could work.  Alternatively, we presumably know once we've executed all the scenarios so can't we just call it then?

On the other hand I assume that an embedded server will shutdown itself on exit anyway.

In-process embedded server, yes.  However, it's possible that people would use the BeforeFirst to start an out of process server for example or populate a real deployment with some test data.  Such usecases would require a clean up step.

@tsiq-karold will expand on BeforeFirst a bit first. This is mainly for JUnit like runners. On a pure groovy side we tend to have more scripting around and it is more DevOps like. So it is less of an issue there to bootstrap.
By tracing I meant simple user/framework additional logging. In a way similar to StepReporter but more focused on http and flat.
Let me add afterLast with a bold comment that it could be way after the real last call. I will have to use TestListener.afterAllTests (which relies on shutdown handler for junit like runners)

Hmm, TestListener.afterAllTests will only work when @Webtau is present on a test. Which is not good for his sort of listeners. @Webtau is optional in a sense, that if you don't have it, test class won't be part of a report. I don't have any good idea right now how to make it work for both Groovy and JUnit.

OK, let's park the after last thing for now.  When someone asks for it, we can revisit.

@tsiq-karold good to go?

@tsiq-karold good to go?

Let's do it.


Create changelog automatically

Description
It's a common practice to have a changelog, even though nobody reads it. But well ...
####Acceptance Criteria
Using goreleaser:

[ ] Sort all the commits since the last release
[ ] Exclude commits that start in the title with docs or test or Merge pull request or Merge branch or go mod tidy.

** or alternatively** try this:
Acceptance Criteria

[ ] Install https://github.com/marketplace/actions/changelog-ci
[ ] Test it

@cerebrux I think you have something already made. Hm?

Depends on #69

@cerebrux I think you have something already made. Hm?

I was thinking to implement something like this, but I don't remember actually doing it :P.
So let me check it :)

I have no Idea how my fork closed this issue ! LOL

I have no Idea how my fork closed this issue ! LOL

😅

I was wondering why the:
Acceptance Criteria
 Install https://github.com/marketplace/actions/changelog-ci

was not working in my tests.... then I read again it documentation:
[..]changelog is prepended to CHANGELOG.md file and committed and/or commented to the release Pull request.
So... this one probably goes to "κουβά" as we don't need every pull request to be populated with changelog... or do we ?

@cerebrux
You didn't use the https://github.com/marketplace/actions/changelog-ci, I see here that you created goreleaser. You need to read the documentation and create the CHANGELOG/md file initially (I think, it might not be necessary but for safety I would say let's) then create /edit the .github/workflows/workflow.yml file and add the step:
name: Changelog CI

# Controls when the action will run. Triggers the workflow on a pull request
on:
  pull_request:
    types: [opened, reopened]

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      # Checks-out your repository
      - uses: actions/checkout@v2

      - name: Run Changelog CI
        uses<EMAIL_ADDRESS>        with:
          changelog_filename: CHANGELOG.md
          config_file: changelog-ci-config.json
        # Add this if you are using it on a private repository
        # Or if you have turned on commenting through the config file.
        env:
          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}

if you want to use the default conf options then skip the config_file declaration.

Goreleaser automatically attaches the commit messages from the commits in between tags. I have a feeling the only thing we need to do is to clean-up commits that should not be referenced in the release notes (like ci:). So probably we can let goreleaser handle everything.


Create a<EMAIL_ADDRESS>email address

So that people can get in touch with us more easily who want to do an interview. We can have it forward to a few members of the team instead of landing in the inbox that we never check.

Okay it exists now as an email. Just need to add it to the Contact page next.


infinite loop

If you don't want to specify a different target bucket, this script ends up in an infinite loop. I found a solution where a DynamoDB was used to avoid this case. But I thought that maybe adding a meta information like "x-amz-meta-optimized" with value 1 or something might be a solution. The Script then skips files with this meta tag.
The downside of this:

Script runs twice (Is also happening when using a DB)
Images do have an additional Meta-Tag

What do you think about this?

That seems to be good solution. But, I think these downside cases too.

Script runs twice (Is also happening when using a DB)

If JPEG image, resize image twice, quality is down. (but it may be better than infinite loop...)

Images do have an additional Meta-Tag

I think that has no problem. Or something would be likely to be a problem?
I using this package to avoid infinite loop, Put the directory prefix of Lambda's event source settings (e.g. lambda/*) , and put different directory (same bucket) on this package's setting.
The But may, if there is other good workaround...
thanks.

If JPEG image, resize image twice, quality is down. (but it may be better than infinite loop...)
Ah no, I just meant the script runs twice. On the beginning of the script should be a check if the Meta-Tag is already set. If it is, the resizing and optimizing are skipped.
I think that has no problem. Or something would be likely to be a problem?
I don't think so either, no.

I using this package to avoid infinite loop, Put the directory prefix of Lambda's event source settings (e.g. lambda/*) , and put different directory (same bucket) on this package's setting.
Unfortunately we do have a web-application which uses 3rdparty libraries. These libraries are not likely to configure to write and read in two separate directories (or Buckets).

So I might try to create a PR for that. It shouldn't be hard to read and write the Meta-Tag.

Ah no, I just meant the script runs twice. On the beginning of the script should be a check if the Meta-Tag is already set. If it is, the resizing and optimizing are skipped.

Oh yes, I was mistaken. I agree with you.

So I might try to create a PR for that. It shouldn't be hard to read and write the Meta-Tag.

I'm looking forward to your PR!

Close with PR #11 thanks!


Fixes to avoid multiple definitions for thread pools and suppress compiler warnings.

When using the ips4o parallel sort via normal Makefiles, I ran into multiple definition errors when compiling associated with the various *ThreadPool Impl structs. I inlined all the associated functions where the definition was separated from the declaration, which resolved the errors. This is the first commit in the PR.
In addition, I attempted to suppress most of the (presumably spurious) compiler warnings when including the ips4o headers. (I did this for -Wall -Wextra -Wpedantic, but I typically don't use pedantic so I don't actually care about the warnings associated with __int128.) The remaining warning, as far as I get them at least, is associated with classifier.h:131:
./lib/ips4o/include/ips4o/classifier.hpp:131:28: warning: suggest parentheses around ‘&&’ within ‘||’ [-Wparentheses]

I attempted to add parentheses and such to make this warning go away, but the compiler seems to be hung up on something here. I don't fully understand the control flow of this function, but if you can explain it to me or have some ideas regarding the warning, I would be happy to take another look at the warning and try and suppress it.
Thanks for your time and feedback!

I went through and adopted the suggestions:

The static cast to avoid signed-unsiged comparison is now to int instead of std::int64_t.
Unused parameters have been removed and the function calls have been adjusted. Similarly, unused values have been completely removed. (This should be tested by somebody that knows the code well because I do not know whether getting the shared pointer on line 480 of parallel.hpp had any important side effects.
In my testing, the sort still works correctly in serial and parallel contexts, but I'm not sure if there is a more comprehensive test suite that could be run.


add metrics to eval overall usage and value created

lines of coverage rendered
files with coverage rendered
have these displayed in the statusbar on hover?
sendEvent captured

cleanup loadCoverageAndRender event instead (no vanity number)


Adding support of multi directives

Hello,
We really enjoyed the lib but multi directives support was missing and we so the "TODO", so here it is :)
We also added test for this use case.
Hope this will be ok for you and make it available to everyone

The changes looks good.

@vkolgi
Thanks to you !
Any idea on when you'll release the new version ?

@MorganDbs I will bump the minor version and release today.

@vkolgi that's quick ! Thanks a lot


[Feature Fix] Removed password character maximum limit

Purpose
Regarding Issue #2856, removes the 35 character limit on passwords.
Changes
Removed maxLength for the knockout observable for the password as well as the validator in auth/forms.py. Also removed/updated the related warnings/messages during sign up/registration and password reset.
Side Effects
Shouldn't really affect anything else, I removed one of the rules in knockout (knockout.validation.js) originally, but added it back when I realized it's not specific to the password max length, but rather just a generic rule for max length.

I think we should still have a length limit (to prevent arbitrarily long user inputs), though it should be larger than 35. 256 should be fine.

@sloria  That makes sense, I'll make the changes now.

@sloria I changed it, the password can now be between 6 and 256 characters.


Fix a regression in authenticating HTTP proxies.

We were using the regular authenticator, not the proxy authenticator.
Closes: https://github.com/square/okhttp/issues/2414

LGTM. Test failures?

We had a broken test! Fixed that too.


When the code will be released?

Unfortunately, the work is currently under review process, which is why we are prohibited from uploading the code on "social" websites of any form. But, if you could drop me an E-Mail (in pre-print), we could discuss "alternative" ways.


Add Golem (small project from 2014-2016)

May have actually started before 2014

Thanks, looks interesting!


added cli option to preserve VPC settings on update; fixes #78

This adds a command line option called --preserve-vpc which allows you to omit the VPC settings (i.e. subnets and security groups) so that it will preserve whatever settings are already present on updates. This is useful when deploying the same function to multiple accounts where the security groups and subnets will necessarily change.

Alright I've made that change to call it using kwargs. Anything else?

@nficano is this repo still maintained? Do you have a procedure for merging PRs and getting new releases built?


Cannot install firefox in Ubuntu running on virtual machine  (MAC M1)

Hi,
After installing ubuntu using virtual machine UTM (on a M1 mac with arm64), I tried to install firefox using the following command:
sudo snap install firefox
I get the following error:
error: cannot install "firefox": Post        https://api.snapcraft.io/v2/snaps/refresh: x509: certificate signed by        unknown authority
To cope with this issue, I ran the following command:
openssl s_client -connect api.snapcraft.io:443
It prints correctly the CA.
Any help please?

same here, flatpak and linux mint packages seem to install fine though


Is it possible to serve tiles at {z}/{x}/{y}.{extension}?

Tilestrata is great!  Just wondering if hosting tiles at {z}/{x}/{y}.{extension} is possible, or if the /filename.png at the end is always necessary.  Just trying to keep consistent URLs for map services I am setting up.

@brianreavis - would you be open to a pull request that optionally allows this URL format?

Now out in 2.1.0!


Dependabot/bundler/library/homebrew/simplecov 0.20.0

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?
[ ] Have you successfully run brew man locally and committed any changes?

I'm not sure what this PR does. If you'd like to make a genuine contribution please make sure to follow the PR template and explain the proposed changes.


fix: Korean input trigger keydown event twice

[!NOTE]
The solution needs to be tested by a proper Korean language user. Being a non-Korean lang user, I can change the keyboard and type input and test, but I will not be able to say whether what I tested is proper according to the Korean language,

Issue
Korean and Japanese languages characters are formed using the compositions of keys.
From GPT:
Composition-based Input:
Korean, like many East Asian languages, often uses an Input Method Editor (IME) for text entry. This involves a composition process where multiple keystrokes may be required to form a single character.
Challenges:

The value of the input field may not be final until the composition is complete.
Key events may fire multiple times for a single Korean character.
The keyCode or which properties may not accurately represent the Korean character being input.

The issue we were facing is that the keys were still composing when we were handling onKeyDown  event. By the time the composition is done, it is used to trigger one more time enter and last character.
can read more here
Fix
Add a composing check-in on the KeyDown event to handle the next stages. Though Key events might fire multiple times, this makes sure, that until all composing is done enter is not triggered .
Why the handling is added in onKeyDown event not on onChange?

we are concentrating on enter key which is the terminating key. It's not considered as value in the input tag.

This fixes https://github.com/react-tags/react-tags/issues/988
SCREEN RECORDINGS
English lang
https://github.com/user-attachments/assets/fe4060cf-d51f-4fa5-9efd-7f99a20f575f
Korean lang
https://github.com/user-attachments/assets/80ba9760-6184-4faa-8a76-4189ebc8901b

Hey @ad1992 , here is the fix for https://github.com/react-tags/react-tags/issues/988. How to ask the bug reporter to try this out and check whether this works ?

@shrilakshmishastry looks like this has fuzzy PR changes as well, can you only push the changes related to the fix?

@shrilakshmishastry please leave a comment about why this PR is closed

The PR is closed as the branch is cut out from non master branch


prepare next release, update CHANGES

/cc @hannesm @dinosaure do you agree the CHANGES messages?

sounds good to me, thanks!


oasis.app Browser ethereum provider and URL network param do not match!

Good day to all,
I got an issue with oasis.app site. Check the screenshot below. How I can fix this issue? Thank you all and have a great day ahead.

We need to get a feedback from Oasis.app developers themselves since we need to know what specifically they are asking to successfully integrate with a wallet.


SCHTASKS documentation missing the 'OnEvent' schedule type

SCHTASKS /Create /?
SCHTASKS /Create /SC ONEVENT is an option not listed in this documentation.

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

ID: 0feda591-bda7-75e4-3eee-f38ec06f6f17
Version Independent ID: f9f5b2ca-d26f-dd8a-70d1-0c07b94a4dd6
Content: schtasks create
Content Source: WindowsServerDocs/administration/windows-commands/schtasks-create.md
Product: windows-server
Technology: windows-commands
GitHub Login: @JasonGerend
Microsoft Alias: alalve

Hey whoisrich,
Thanks again for contacting Microsoft, we value your feedback.
A documentation change has been made adding the ONEVENT schedule type and will be live after the next business day. We will now be closing this thread.
Thank you and have a most pleasant day.
#please-close


Version number interpretation

I was trying to delete a package and it could not find it because of the version number: the package had a version 4.0.01 and i was trying to delete version 4.0.1... Touchy :)

Ee should consider normalizing version numbers on the gallery at some point, at least for lookups.


TeachingTip Title takes space even when there is no content.

When the tips Title content is set to null the remaining content still lays out as if there were text in the title.

I looked into this, and I found no way to solve this with retemplating. A possible solution would be to check if the Title is empty and update the height using code behind. But that, in my opinion, is not the best solution.

@StephenLPeters do you have a recommendation for the fix?

I think that title = null is a pretty strong indication that we should collapse the text block which displays that title.  We could make a string to visibility converter to declare this in markup, I don't think making this check from code behind is outlandish though.

@StephenLPeters Can I look into this issue or are you currently looking into this?

I'm not, please take it :)


chore: merge develop into mainsail-develop

Summary
https://app.clickup.com/t/86duzn9wt

Checklist

[ ] I checked my UI changes against the design and there are no notable differences
[ ] I checked my UI changes for any responsiveness issues
[ ] I checked my UI changes in light AND dark mode
[ ] I checked my (code) changes for obvious issues, debug statements and commented code
[ ] I opened a corresponding card on Clickup for any remaining TODOs in my code
[ ] I added a short description on how to test this PR (if necessary)
[ ] Documentation (if necessary)
[ ] Tests (if necessary)
[ ] Ready to be merged

Only a few Validators are showing up so I need to look into that


repro - Verify installed packages (pacman -Q) versus BUILDINFO packages

Currently the tool sets up a build env but does not verify if it's 100% correct, this can be done by verifying the installed packages against the BUILDINFO required installed packages.

Fixed with #40

Wops, wrong closed issue :o


Pluggin not working

Hi. I like what this plugin is trying to accomplish. Could really improve my workflow.
However, whenever I run UpdateRemotePlugins I encounter the following error:
Encountered TypeError loading plugin at $HOME/.local/share/nvim/plugged/vim-database/rplugin/python3/database: 'type' object is not subscriptable
Traceback (most recent call last):
File "$HOME/.local/lib/python3.8/site-packages/pynvim/plugin/host.py", line 165, in _load
module = imp.load_module(name, file, pathname, descr)
File "/usr/lib/python3.8/imp.py", line 244, in load_module
return load_package(name, filename)
File "/usr/lib/python3.8/imp.py", line 216, in load_package
return _load(spec)
File "", line 702, in _load
File "", line 671, in _load_unlocked
TypeError: 'type' object is not subscriptable
Tried the error fixes in the README, it's still not working. Please help.

Hi, Sorry for my late response...
For your error, I can not reproduce it on my local machine. Could you try to upgrade your python 3 version to python 3.9 to see whether the error still occurs?
Or you can update your pynvim plugin on your machine.

Seeing this months later... Thanks, upgrading the neovim python provider ( g:python3_host_prog ) to 3.9 resolved the issue. However, I suggest reflecting this requirement in the README. There it cites python 3.7 as a dependency, which clearly isn't the case.


Moved hw directory to its own repository

New link: https://github.com/PiSCSI/piscsi-hw

Note that the new repository retains all of the history from the original rascsi git repo

@akuker do you have ideas around making the hw repo easily discoverable from the software repo? Perhaps a link in the readme?


example: add buttons for LND RPC sub-servers

Adds buttons to the example html page to test calling the RPCs of lnd sub-servers. At the moment. these buttons will always be disabled due to the sub-server permissions not being added to the session macaroon created by litd. Once https://github.com/lightninglabs/lnc-web/issues/60 is resolved, these buttons should become enabled to properly test all of the sub-servers.

Since this PR only edits the example client, I am going to merge it without requesting a second reviewer. Thanks again for adding this @jamaljsr!


make RESPONSE_LIMIT settable by the caller

For data analysis, it'd be convenient to export the full data set in a JSON blob per data type.  I propose:
/bulk/cases, /bulk/methods, /bulk/organizations which each return a single JSON blob with all of the data of each type in one response.
@dethe thoughts?

Actually, I think all we need to do is to be able to disable pagination on /search.
/search?query=&selectedCategory=Methods&page=2&sortingMethod=alphabetical seems to work OK, and indeed returns more data than the default search, which confuses me a bit.

Updated the title to say what I mean.

We have pagination and bulk export now, closing.


Result of Robust Linear Model

Hi Professor Di and Emi,
I have built a robust linear model (using rlm function from MASS) by ID for all of the IDs in the dataset, and it is way faster and computable than using the robust linear mix model.
Further, if the observation’s weight is <1, I imputed that observation and change its value with the prediction value of the model.
I found the result as seen in this picture:

I  also plotted some of the IDs and compare them by the cleaning method:

In addition, the summary of the current clean data is:
Min. 1st Qu.  Median    Mean 3rd Qu.    Max.
0.01    4.50    7.13    9.26   11.53  268.33
And the cleaned data using robust linear model is
Min. 1st Qu.  Median    Mean 3rd Qu.    Max.
0.020   4.629   7.195   9.165  11.441 192.300
Based on this result, should the data from the robust linear model cleaning used in the final data?
Or is there anything I should explore further?
Thank you,
Dewi

Hi Dewi, Yes 😺
Sent from my iPhone

On 19 Feb 2021, at 7:32 pm, Dewi Amaliah<EMAIL_ADDRESS>wrote:

Hi Professor Di and Emi,
I have built a robust linear model (using rlm function from MASS) by ID for all of the IDs in the dataset, and it is way faster and computable than using the robust linear mix model.
Further, if the observation’s weight is <1, I imputed that observation and change its value with the prediction value of the model.
I found the result as seen in this picture:
I also plotted some of the IDs and compare them by the cleaning method:
In addition, the summary of the current clean data is:
Min. 1st Qu. Median Mean 3rd Qu. Max.
0.01 4.50 7.13 9.26 11.53 268.33
And the cleaned data using robust linear model is
Min. 1st Qu. Median Mean 3rd Qu. Max.
0.020 4.629 7.195 9.165 11.441 192.300
Based on this result, should the data from the robust linear model cleaning used in the final data?
Or is there anything I should explore further?
Thank you,
Dewi
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


allow single file exclusions

In order to use deptrac in a mature project with multiple layer violations, we want to be able to exclude a list of files (instead of regexs) generated by our pre-commit hooks, so we can force our devs to fix the violations of the files they modified instead of explicitly work on a huge one-time refactor.
I found that the exclusion system of the FileResolver is always expecting a regex and breaks if you try to exclude a file path. With this change we resolve the iteration of the array_filter earlier if the config line has a file path format.
Since you don't have tests for this file, you can manually test this fix creating a depfile to analyze the tool itself:
paths:
  - ./src
exclude_files:
  - ./src/OutputFormatter/JUnitOutputFormatter.php
  - .*OutputFormatterInterface.*
layers:
  - name: Dependency
    collectors:
      - type: className
        regex: .*Dependency.*
  - name: OutputFormatter
    collectors:
      - type: className
        regex: .*OutputFormatter.*
ruleset:
  Dependency:
    - OutputFormatter

@carlosas Thank you for contribution!
Since this class is not really testable it might be a good idea introduce / evaluate https://github.com/bovigo/vfsStream. I will figure this out after my vacation.
For now we could rework and test the exclusion strategy. The Finder uses internally the FilterIterator and has already a PathFilterIterator. But it relies on a relative pathname which does not work very well with multiple paths. We could add our own implementation which reuse/extends PathFilterIterator, override PathFilterIterator::accept()-method and use SplFileInfo::getPathname(). So we would configure a finder instance, get its iterator and wrap it with our own FilterIterator. Plus a test could be added for this new class (https://github.com/symfony/finder/blob/master/Tests/Iterator/PathFilterIteratorTest.php might be reusable).
@carlosas Would you like to try this out?
Btw. instead of another if-statement preg_quote($pathname, '/') could have been used :-)

I'll give a look this weekend to the approach you are suggesting


Remindabot🤖

Feature ✅
Description
Write a script to remind user every 20 minutes to get up and walk or stretch a little. As you might be working on PC, you might not notice the warning on terminal. So the script must interact via notifications or Text to speech.
Example

If user enters
the program must

-1
Terminate

0
Pause

1
Resume

Contributors are supposed to mention their coding language while asking for assignment

Hey!I'd like to work on this! Can you assign it to me? (Language: Python)

Hey! Let me know if any additional features are needed! I'd appreciate any suggestions @pratik-choudhari

@GoluffyxD Great work👏


Added a function to change baseUrl.

To change the tile set, call updateBaseUrl on the osm layer.  This moves all existing tiles to the zoom level of 'old' so that they will not be used, then updates the layer.

This is great.  I'll add a quick test as part of the osmLayer selenium test already in place.  Thanks @manthey.

Nice. Quick question . Why keep the old tiles? Just wanted to get your thoughts.

Because I wasn't certain if removing them would have a negative effect: tiles that are not fully loaded will still call tileOnLoad.  At that point, if they aren't present, we would need logic in that routine to handle it.  By keeping the, the existing garbage collection will handle this.

Right. I think this is probably the path of least resistance here.

If it is not too much work: I prefer we remove them. You can set the flag on the old ones because if on load gets called it may interfere with the current tiles. But j I havenot reviwed the branch very carefully

I'll look into it a bit later.

I'll refactor to remove the tiles later today or tomorrow.

Sounds good, thanks. If it looks good then please merge and create new issue for it. I agree it's least resistance for now

thanks @manthey. I am reviewing it now

Looks good @manthey. I will just wait for the travis and then will merge it.

@aashish24 looks like Travis is stuck -- it passed, but isn't sending the results back to github.

Well, that's a new one.  I say merge it.

yeah seems like it.. merging it fornow.

Absolutely. When in doubt, merge! :smile:

@manthey one thought I had. Currently we list only one baseurl: m_baseUrl = "http://tile.openstreetmap.org/". Would it be possible for you to add list of good URL's (with one being the default). In that case, user can query list of possible URL's and use them appropriately. It will be helpful to provide this list for new users of GeoJS. The number of lines of code will be few. Thoughts?

I was planning to add an example with a widget for switching between tile servers.  I would probably do #279 and #281 along with this.

@jbeezley that would be great.


Improve robustness of API key tests

I don't think we have an issue for this, but took a stab at adding some retry logic to our API key tests.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.5%) to 87.998%

Totals

Change from base Build<PHONE_NUMBER>:
-0.5%

Covered Lines:
2097

Relevant Lines:
2383

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.5%) to 87.998%

Totals

Change from base Build<PHONE_NUMBER>:
-0.5%

Covered Lines:
2097

Relevant Lines:
2383

💛  - Coveralls


[stable/node-problem-detector]: Bump to 0.8.1 NPD

What this PR does / why we need it:
The new version brings the following fixes

Fixed several potential busy loops
Added a k8s-exporter-heartbeat-period flag to make the heart beat period of K8s exporter configurable.
Fixed a potential NPD panic caused by close of closed channel
Added Stackdriver exporter for NPD
Collect a lot more useful CPU/disk/memory metrics
Fix a few metric units for disk metrics and the calculation for disk_avg_queue_len
Fix the first 0 value metrics reported for disk_avg_queue_len
Improve network_problem.sh to support nf_conntrack and report error when conntrack table is 90% full.
Support host_uptime metrics for CentOS

Signed-off-by: Markos Chandras<EMAIL_ADDRESS>Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

/assign
/lgtm


Supporting X-Watson-Learning-Opt-Out

This came from an awesome helpful Twitter thread: https://twitter.com/dalelane/status/1106565327457054720, thanks @dalelane! 👍
Would it make sense to allow teachers and young people to opt-out of data collection, as in https://cloud.ibm.com/apidocs/assistant#data-collection?  Especially for folks using this with young children, this seems like it should maybe even be the default for all services.
What do you think?

Also, the help awesomely describes the site's use of things like the analytics and error reporting services.

Teachers or parents may read this copy and have the expectation that this is the exhaustive list of where the data that they submit is stored.  But it doesn't mention anything about sending data to IBM services, and that data storage, so it seems like maybe this should be updated to include that as well.
What do you think makes sense?

@dalelane 👍 ❤ 💻


devops-apiserver无法运行,Error: unable to retrieve the complete list of server APIs

What is version of KubeSphere DevOps has the issue?
kubesphere/devops-apiserver:ks-v3.4.1
How did you install the Kubernetes? Or what is the Kubernetes distribution?
Kubernetes v1.23.10
What happened?

Relevant log output
W0521 00:56:50.352880       1 client_config.go:617] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.

 W0521 00:56:50.353565       1 options.go:143] ks-apiserver starts without redis provided, it will use in memory cache. This may cause inconsistencies when running ks-apiserver with multiple replicas.

 I0521 00:56:50.392736       1 sonarqube.go:55] Sonarqube integration is disabled

 I0521 00:56:50.393446       1 sonarqube.go:55] Sonarqube integration is disabled

 [restful] 2024/05/21 00:56:50 log.go:33: [restful/swagger] listing is available at /apidocs.json

 [restful] 2024/05/21 00:56:50 log.go:33: [restful/swagger] /apidocs/ is mapped to folder bin/swagger-ui/dist

 I0521 00:56:50.398432       1 apiserver.go:234] Start cache objects

 Error: unable to retrieve the complete list of server APIs: api.scenetech.cc/v1alpha1: the server is currently unable to handle the request

 2024/05/21 00:56:50 unable to retrieve the complete list of server APIs: api.scenetech.cc/v1alpha1: the server is currently unable to handle the request

Additional information
No response

kubectl delete apiservices/v1alpha1.xxx.xxx.xxx

there is no CRD named api.scenetech.cc/v1alpha1 in ks-devops, so please check if ImageID of devops-apiserver is d192e090f152 or pull it again, then restart deployment devops-apiserver ?


generate comments on private fields

Is it possible to configure plugin in such a way that it will generate comments on private fields, methods, etc.?

It's a great and very useful Plugin, thanks a lot!
It looks like the only issue is the missing Doc for JavaDoc2:
I guess that JavaDoc2 is configured here in IntelliJ: Settings » Other Settings » JavaDoc
It this is true, then it should be mentioned in the Introduction Page.
There, we can configure templates and enable the generator for private class items.
It looks like the Plugin generates Comments if the Visibiliy Private is enabled.

Fixed in 4.0.1 version

Thank you very much!


Can't use 2.1.0.pre without getting corrupt file

Attempting to use the following to test xlsx generation (from the docs). Every time I open the subsequently created xlsx files, I get
"Excel could not open example.xlsx because some content in unreadable. Do you want to open and repair this workbook?" and then "The workbook cannot be opened or repaired by Microsoft Excel because it is corrupt."
p = Axlsx::Package.new do |package|
  package.workbook.add_worksheet do |sheet|
    sheet.add_row([1, 2, 3])
    sheet.add_row(['a', 'b', 'c'])
  end
end

p.serialize('example.xlsx')
s = p.to_stream
File.open('example_streamed.xlsx', 'w') { |f| f.write(s.read) }

(Ruby 2.1.2, Rails 4.2.1, rubyzip 1.1.7, Mac OSX 10.10.2)

Your worksheet is missing a name.
p p.validate
=> [#<Nokogiri::XML::SyntaxError: Element '{http://schemas.openxmlformats.org/spreadsheetml/2006/main}sheet': The attribute 'name' is required but missing.>]

Thanks! That fixed it. Maybe that should be required with add_worksheet?

@kddeisz It's actually a bug. The serialisation code ignores some defaults we've set. Will fix it when I have time.


Added filter with raw properties

Issue: https://github.com/Portable-Network-Archive/liblzma-rs/issues/126

@ChanTsune it's ok. I removed marcos and added delta filter. Could you review?

@ChanTsune if everything is ok can you publish release?

@ikrivosheev
Thank you for your work!
It seems that manual.rs also needs to include pub const LZMA_FILTER_DELTA: lzma_vli = 0x03;.
I will release it as soon as possible once all the tests pass.

@ChanTsune ups, thank you. Fixed.

@ikrivosheev
Thank you for your contribution!
I’d love to include your name in the THANKS file. Do you have a preferred name you'd like us to use?

@ikrivosheev Thank you for your contribution!
I’d love to include your name in the THANKS file. Do you have a preferred name you'd like us to use?

Thank you. My full name is Ivan Krivosheev.


Adjust for directus 10.10

Requires some adjustment to readme + maybe something to build module files with github runners or something, not tested yet

Thanks for the PR, it seems good just one comment and a change.
The install guide is for the "deprecated" way of using extensions. We'll need to move the config to the database somehow. Could you move the files up to the src/ folder instead of having them in the sub modules folder.

Hi, great to hear that we can try to do something together with that project. I found a bug that makes this module on directus 10.10 bugged, it's not generating configs because of some crashing code. I'll try to fix that, also I'll try to check if moving files to src/ won't cause problems, I think I did it for purpose. Maybe it will be possible to not make this module a bundle.

did you have any luck with making it work for v10.10+

did you have any luck with making it work for v10.10+

Hi, I haven't had the time yet, but I'll still be handling this issue later on.


imported font-awesome

Thankyou for the amazing new fonts Tanmayi, Appreciate the help :)

Thankyou for the amazing new Fonts Tanmayi, Appreciate the support like that :)


Add a terminology section to the docs?

I often hear something like "the Dask docs are great, but can be a bit overwhelming when first getting started". One reason is that Dask has some terminology that new users may be unfamiliar with (e.g. "chunks", "task graph", "graph optimization", etc.)
Xarray has a nice documentation page where they define common terms that are used throughout their project (https://xarray.pydata.org/en/stable/user-guide/terminology.html).
Would adding a similar terminology page to Dask's documentation be useful? We could define terms like "chunks", "task graph", ... in a central location and then link back to the terminology page when we use a term like "task graph" in other documentation pages. This might help new users get up to speed on Dask's vocabulary more quickly.

I'm interested in helping with this! Has anyone started working on this yet? One way I thought about breaking up the work is:

Start by iterating on list of terms to define
Create definitions for each term
Add links to usage of these terms from various pages (could be one PR or multiple)

Another thing that would be useful to have in the docs - mapping between similar concepts in different domains. Eg: array chunks are similar to dataframe partitions, etc.

Thanks @rikturr! Feel free to open up a PR with an initial draft of a terminology page. Don't worry about making the initial list of terms comprehensive, this is definitely something we can (and will) add to over time

I just came across this page for the first time and found it useful https://docs.dask.org/en/latest/spec.html

Another terminology thing that took me a while to figure out is that blockdims is the same as chunks (i.e. fully specified chunks, like you'd see if you queried the .chunks attribute of an array).
This might be more useful for dask developers rather than for dask users, though. You see blockdims written in lots of places through the code, but I don't think it's a thing dask users need.

Made a start in #7881 and we can go from there!


A Different error on install

Here's the error I get when running ember install ember-plupload:
Installing browser packages via Bower...
  not-cached git://github.com/moxiecode/plupload.git#2.1.3=plupload#2.1.3#
Tag/branch 2.1.3=plupload#2.1.3# does not exist
Error: Tag/branch 2.1.3=plupload#2.1.3# does not exist

https://github.com/paddle8/ember-plupload/blob/master/blueprints/ember-plupload/index.js#L6
This needs to be changed to  addBowerPackageToProject('plupload', '2.1.3');
Because of this: https://github.com/ember-cli/ember-cli/pull/4643

Thanks for this! I just bumped plupload's dependency as well. I'll merge this in and note that it needs support for newer versions of ember-cli


Update cfcr.yml

v0.24.0 note found at https://github.com/cloudfoundry-incubator/kubo-release, so pointing to

name: "kubo"
version: "0.24.0"
url: "https://bosh.io/d/github.com/cloudfoundry-incubator/kubo-release?v=0.24.0"
sha1: "96dcd74c99d2a092c7d9d7f21476fb8aa607f54d"

What this PR does / why we need it:

How can this PR be verified?
deploy fro https://github.com/cloudfoundry-incubator/kubo-deployment.git will fail
Is there any change in kubo-release?
Is there any change in kubo-ci?
Does this affect upgrade, or is there any migration required?
Which issue(s) this PR fixes:
https://github.com/cloudfoundry-incubator/kubo-deployment/issues/359
Release note:

I have published the release. It should work now.


⚠ Bofrost.es has degraded performance

In 589f0f1, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1543 ms

Resolved: Bofrost.es performance has improved in 6831f41 after 6 minutes.


implement coin market cap api and get a full list of coins / symbols

https://github.com/MikeJohnManiatis/reddivestor/pull/25


Fohlen/testing

Updated the nightly-builds & notifications to fit our own notifico!

Looks great!
Please just squash/fixup a507bd6 onto 9085f35. This way the diffs from both commits are merged and we don't need a fix commit. You can use git rebase -i HEAD~5 to do this.
Otherwise this is fine. Please merge with git rebase master; git checkout master; git merge fohlen/testing :)


Change TTA homepage link to our TTA page

Don't merge this, it's for UR only

@peteryates Is this still needed or can this PR be closed now?

Ah, forgot about this one! We can close it but I think @KeishaDfE's research will show this is generally an improvement (hedging my bets!)


[FEATURE] / [BUG] The external scoreboard no longer covers the entire ingame scoreboard

Since the addion of Objective Bounties (I think), the external scoreboard no longer fully covers the ingame one and also doesnt provide as much information as the ingame one.
A few Ideas:

Make it easier for the user to customize things (maybe it's already possible, but I couldn't find anything)
Simply extend the external Scoreboard background image to cover the ingame one (at the loss of Objective Bounty information)
Extend the scoreboard and put the Objective Bounty information onto it (don't know if that's possible / easy to implement)
If the user has the toggles for Team Names, Team Scores and/or Team icons on, but the one for the Scoreboard is toggled off, show the Team Names/Scores/Icons next to the ingame scoreboard (needs an additional check and might not look perfect, but provides all the data)

Attached is a screenshot of the problem

To customize, change the scoreboard yourself, all positions, backgrounds, etc are customizable. Try changing the ingame.json file and images in the ingame overlay.
Also its not meant to cover it, you should hide the scoreboard in the beginning of the game. There is a config option to do that automatically for you


Move demo app

Moved web demo app from asset-tracking-js

Closing this because it's no longer needed.


Drag and Drop the items between flatlists

Is your feature request related to a problem? Please describe.
Currently, the functionality allows for dragging and dropping an item within the same list. However, it would be highly beneficial if the feature could be extended to support dragging an item from one list to another. This enhancement would improve the flexibility and usability of the drag-and-drop interaction by enabling users to move items across different lists.
Additionally, it would be great if we could extend the drag-and-drop functionality to allow entire lists (e.g., List1, List2, List3) to be dragged as a whole for reordering purposes. This would allow for more dynamic interaction, where not only the items but also the lists themselves can be repositioned, providing a more seamless and intuitive user experience.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@aliraza943 please check this if this solves ur issue
https://www.npmjs.com/package/react-native-draggable-groups


Cherrypick child key derivation

The original implementation is in
https://github.com/SwingbyProtocol/tss-lib/pull/6/files#diff-e663957d1112b8c89bb7a782fe1cebe0d5e4d84a17861ae5af5cc0b59d1dbf56
Some changes made according to audit report

Hey, @FitzLu. Is there any change key derivation will be merged into main branch any time soon?..


Attempt at a fix for #475

Attempt at a fix for #475. Apologies for my coding style.

I don't think that is the right approach as the User.Id should NEVER be empty if you are authorized.
My guess is that due to the background service in AD that fills in the users it has not been added yet.
@larshg Maybe we need to revert https://github.com/jakubgarfield/Bonobo-Git-Server/commit/2af315756ebec6bfcf05f43b09d3fd073c186186?

But aren't we talking about 2 different contexts? The browser context and the git context. Yes the User.Id should never be null from a browser but git does not have access to that cookie/session. Git has to re-authenticate somehow.

Git does a full http authentication (cookie or windows auth) before it reaches the GetSecureInfoRefs part.
Set a breakpoint at the authentication code and you will see it.

@chrismdev you can try debug through the OnAuthorization in GitAuthorizeAttribute - this should authenticate you when using a git client.
And the git client should prompt for username and password if you use the general url - also if you use credential store you might have to clear it, if you have old values saved etc.

@larshg the problem is that we never get to see the passwords unless internal auth is used. IIRC This means the pipeline will auth the user against the AD and let it proceed. The next step will then try to fetch this user again and becaus it has not been added to the backend by the background worker it will still have an GUID of 0.

@RedX2501  what do mean that we never get to see the passwords? Your git client has to be authenticated somehow by providing a username and password?

You are right on the git side. I was thinking about the Browser side when using Windows Auth.

So if you run your site as a intranet and you should automatically be authenticated, bonobo is not presented with username and password?
Because I still have to supply user and password (atleast first time when running chrome) - microsoft edge browser ask for it each time its started - but maybe the url of the remote and local bonobo server I have, is not correctly added as a trusted site :)

Yes, the first time you set username and password (or not if internet explorer does the ntlm handshake) and then a cookie is set on your system. Based on that cookie the user is then retrieved from the DB.

Have created a new pull request for this


[Request] Docker Deployment of the Latest Version of Crawl4ai and a Guide to Using the REST API

Hi, there , Is there a Docker deployment version of Crawl4ai and a usage method for the REST API?

Hello, yes, there have been some changes and we have moved from the synchronous version to an asynchronous version. That's why we need to rewrite the Docker. Hopefully, by next week, we will be able to upload the Docker as well, and you will also have access to the REST API server, which is currently in our plan.


MAINT: Select magnitude images in collect_data for BIDS 1.5.0

Closes #591.
In BIDS 1.5.0, the part entity will be released. part can have a value of mag, phase, real, or imag, of which only mag is used for most preprocessing pipelines. When part is not provided, the data are assumed to be magnitude.
Changes proposed:

Add part == mag or None to filters in collect_data() for T1w, T2w, FLAIR, and BOLD data.
Add new entities (part, inv, flip, and mt) to config file.

@tsalo can you merge/rebase master? The CI failure may have already been fixed.

@tsalo can you merge/rebase master? The CI failure may have already been fixed.

Done!

Done!

BTW would it be reasonable to select T1w and T1map instead of just T1w? Same for T2w.

BTW would it be reasonable to select T1w and T1map instead of just T1w? Same for T2w.

Because we haven't tested fMRIPrep on T1map data, I would be inclined instead to encourage users to create a BIDS filter file to find the T1maps, until we gain some confidence that we can work with them automatically.
I'm currently imagining a new section to the docs with "Advanced and experimental use cases" where we explain how to do things that are possible but not (yet) supported. Open to other ideas.

Because we haven't tested fMRIPrep on T1map data, I would be inclined instead to encourage users to create a BIDS filter file to find the T1maps, until we gain some confidence that we can work with them automatically.
I'm currently imagining a new section to the docs with "Advanced and experimental use cases" where we explain how to do things that are possible but not (yet) supported. Open to other ideas.

RE the current failure, I think we need to update https://github.com/nipreps/niworkflows/blob/master/niworkflows/data/nipreps.json to include part.

RE the current failure, I think we need to update https://github.com/nipreps/niworkflows/blob/master/niworkflows/data/nipreps.json to include part.

Because we haven't tested fMRIPrep on T1map data, I would be inclined instead to encourage users to create a BIDS filter file to find the T1maps, until we gain some confidence that we can work with them automatically.

That makes sense. Thanks for the clarification.

I'm currently imagining a new section to the docs with "Advanced and experimental use cases" where we explain how to do things that are possible but not (yet) supported. Open to other ideas.

That sounds awesome!

RE the current failure, I think we need to update https://github.com/nipreps/niworkflows/blob/master/niworkflows/data/nipreps.json to include part.

Done! I also added the rest of the new entities.

Because we haven't tested fMRIPrep on T1map data, I would be inclined instead to encourage users to create a BIDS filter file to find the T1maps, until we gain some confidence that we can work with them automatically.

That makes sense. Thanks for the clarification.

I'm currently imagining a new section to the docs with "Advanced and experimental use cases" where we explain how to do things that are possible but not (yet) supported. Open to other ideas.

That sounds awesome!

RE the current failure, I think we need to update https://github.com/nipreps/niworkflows/blob/master/niworkflows/data/nipreps.json to include part.

Done! I also added the rest of the new entities.

I think this may require a new pybids release. I could pin to a commit in the setup.cfg though?

I think this may require a new pybids release. I could pin to a commit in the setup.cfg though?

Ah, you're right. We're using a vanilla BIDSLayout, not passing our own. I think it's fine to leave the new entities in our JSON.
@tyarkoni Any objections to a PyBIDS release with entities that precede the BIDS spec release that makes them official? They're already merged into master, just pending a release.

Ah, you're right. We're using a vanilla BIDSLayout, not passing our own. I think it's fine to leave the new entities in our JSON.
@tyarkoni Any objections to a PyBIDS release with entities that precede the BIDS spec release that makes them official? They're already merged into master, just pending a release.

None objection!

None objection!

@oesteban that's a good point. I know where part comes in, but I'm less sure about how to handle the other entities. They all apply specifically to anatomical data, but incorporating them might require basically supporting qMRI (i.e., considering which suffixes accept each entity rather than bundling all anatomical suffixes together).

@oesteban that's a good point. I know where part comes in, but I'm less sure about how to handle the other entities. They all apply specifically to anatomical data, but incorporating them might require basically supporting qMRI (i.e., considering which suffixes accept each entity rather than bundling all anatomical suffixes together).

I know I'd use part-mag for preprocessed fieldmaps. Although the raw spec does not allow it for the moment, we can push at least that to the BIDS-Derivatives.

I know I'd use part-mag for preprocessed fieldmaps. Although the raw spec does not allow it for the moment, we can push at least that to the BIDS-Derivatives.

I've updated the default path patterns to include part. I don't think the other ones are necessary just yet, and I'm reticent to try incorporating all of qMRI in this PR.

This will depend on bids-standard/pybids#826.


Consider supporting additional mysql variants (mysql 5.7, 8, mariadb 10.3+) and Postgres?

Is your feature request related to a problem? Please describe.
People generally like to have the dbserver be the same software they're using on the server. Since mariadb isn't really a drop-in replacement for anything any more, the differentiation continues.
Unfortunately, we hitched our wagon to mariadb some time ago, when it was in fact pretty much a drop-in replacement and could meet people's needs. So we use the terminology "mariadb_version" in config instead of something more general. So this would be something that would have to change.
Maybe Postgres too?
Describe the solution you'd like
I'm pretty sure we'd need a separate container for each, but can do a far better job building from the same base than we're currently doing, which is all copy/paste and not well maintainable.
We'd have to change the configuration mechanism and naming of the image.

This is important;

Non-mariadb variants may not have ddev snapshot and ddev restore-snapshot though
The current dual-copy Dockerfile and such needs to be replaced with a consolidated build.

We are starting to move our Apps from MySQL/MariaDB to PostgreSQL as the features and performance are simply better.
At the moment, we just add a custom service the our ddev configuration and it more or less works. We would welcome the official support of PostgreSQL.

Yeah, we will certainly consider official support. In the meantime, would you document your strategy with a PR in https://github.com/drud/ddev-contrib @dacostafilipe ? The pending PR https://github.com/drud/ddev-contrib/pull/6 does that for mysql versions, would love your review on it, and would love your postgresql approach.

Example created : https://github.com/drud/ddev-contrib/pull/7

For those who might hit this issue looking for PostgreSQL, see https://github.com/drud/ddev-contrib/tree/master/docker-compose-services/postgres
Multiple MariaDB and MySQL versions will be available in v1.12


Recalculate order line price after change

Resolves #82
Also widened a bit input field - quantities > 99 were trimmed.
Pull Request Checklist

[x] All visible strings are translated with proper context.
[x] All data-formatting is locale-aware (dates, numbers, and so on).
[x] Translated strings are extracted to .pot file.
[x] Number of API calls is optimized.
[x] The changes are tested.
[x] Type definitions are up to date.
[x] Changes are mentioned in the changelog.

It's almost finished, we need to get back to this PR and merge it @dominik-zeglen.


Downloads from the app not downloading

Hi, as discussed with Mark, the feature to download source code from the Mac app doesn't work.
Hopefully this will be fixed soon as it shouldn't take too long.
Many thanks

Thank you. Please use https://pap.quicktype.io in the meantime.


Is there Protocol Buffer (protobuf) support? Or will it be supported in future?

I'd like to try this SDK, but my app uses protocol buffers to talk with server.
It would be great, if I could bundle my app with .desc files and see requests with field names =)

Not at the time. PRs are welcome.
I'm also considering adding a way to extend Pulse with plugins. For example, provide custom response viewers.


should not hardcode the test key in spdm_device_secret_lib_sample

Currently, we support RAW private key mode and hardcode key in https://github.com/DMTF/libspdm/blob/main/os_stub/spdm_device_secret_lib_sample/lib.c.
It is not a good design, because if the test key at https://github.com/DMTF/libspdm/tree/main/unit_test/sample_key is updated, it will cause mismatch.
See issue https://github.com/DMTF/spdm-emu/issues/257
I think we need a better way to keep them in sync.

to keep RAW keys in sync with sample_key/*, maybe we can auto-generate those raw keys from sample_key/ and include in lib.c


upgrade-angular-v4: Property 'additionalProperties' does not exist on type 'FunctionKeys'

In monaco-editor.directive.ts there is a references to schema.additionalProperties = false;.  This property does not exist on the type FunctionKeys
ERROR in /_git/AzureFunctionsPortal/AzureFunctions.AngularClient/src/app/shared/directives/monaco-editor.directive.ts (194,24): Property 'additionalProperties' does not exist on type 'FunctionKeys'.

I'm not seeing this reference in monaco-editor.directive.ts.  I also don't see this error when building, even if I do "ng b --prod".  How are you reproducing this error?

Oh wait now I see it after pulling the latest code.

I ended up casting the getJson response object to , which is what @ahmelsayed appears to have done in the dev branch:
https://github.com/projectkudu/AzureFunctionsPortal/commit/f20e36f34dd9a627f48e940454a25ba99e562517


No Docker build configuration for Scala Shopping cart example

Needs Docker configured in the build.sbt to create a docker image for the shopping cart sample so users can easily build and run it. Instructions to run it should be documented.

I'll do this

@justinhj The Scala support is a work-in-progress, so supporting a docker build for it seems like it would be most valuable once the Scala support is done?

Ah, I see, will come back to it then


bluefy disconnect writable locked (dfu)

https://github.com/capacitor-community/bluetooth-le

https://github.com/es-git/es-git/blob/master/packages/http-transport/ts/utils/streamToAsyncIterator.ts

Fixed in e96fb28 (v0.3.22)


Combine update combined_metadata and data-raw actions

This PR combines the actions to update combined_metadata and data-raw to make update-curation.yml. Note that .github/workflows/data-raw.yml is removed and that the curation file is still called sampleMetadata.rda, although it may be changed back to combined_metadata.rda via #196. The action uses cMDC's checkCuration, which is currently failing because it expects column "dataset_name" but has "studyName".
Closes #200.

curatedMetagenomicDataCuration provides a vignette and badge to help curators fix errors, but it provides no guarantees of validity of metadata - curators can and do commit preliminary work then fix it sometime later. There is the additional issue that by the time the PR is reviewed here, the curation repo may have been changed further, but still manual review of the PR is desirable because there are limitations of the automatic checks that we sometimes over-ride by either accepting language that fails, or rejecting language that passes (for example see https://github.com/waldronlab/curatedMetagenomicDataCuration/issues/2).  To have an assurance of valid metadata in curatedMetagenomicData, tests have to be done in its own workflow.

If and after this is approved, I'd also like to merge this myself so I can rebase it on master when it has the changes for #212 and #211 so I can handle the merge conflicts. This will make for a cleaner history.

we should probably encapsulate the checking logic in a script rather than the action itself in the future.

Which part of the logic? The check itself already relies on the function curatedMetagenomicDataCuration::checkCuration(), this action is about running the check weekly and creating a badge and automatic pull request.


Fixes minor spelling and formatting issues

I'm not sure about the duplicated assertion in test/CliIntegration.js, but tests ran fine without that line.

@bartveneman: Nicely found, thank you :-)


Replace uvindex on gltf pattern nodes with texcoord

Fix
Fixes #1486
Changes the exposed input interface from uvindex which is an integer to texcoord which is a vector2. This allows for either

A texcoord to be attached for integer based uv set workflows (e.g. glTF).
A geompropvalue  to be attached for name based workflows (e.g. USD).

Example
This is the boombox example using a mix of integer and named streams
<?xml version="1.0"?>
<materialx version="1.38" colorspace="lin_rec709" fileprefix="boombox/">
  <gltf_colorimage name="image_basecolor" type="multioutput" xpos="9.246377" ypos="-2.534483">
    <input name="file" type="filename" value="BoomBox_baseColor.png" colorspace="srgb_texture" />
    <input name="texcoord" type="vector2" nodename="texcoord_vector2" />
  </gltf_colorimage>
  <gltf_image name="image_orm" type="vector3" xpos="10.144928" ypos="-0.431034">
    <input name="file" type="filename" value="BoomBox_occlusionRoughnessMetallic.png" />
  </gltf_image>
  <gltf_normalmap name="image_normal" type="vector3" xpos="9.681159" ypos="0.956897">
    <input name="file" type="filename" value="BoomBox_normal.png" />
    <input name="texcoord" type="vector2" nodename="geompropvalue_vector2" />
  </gltf_normalmap>
  <gltf_image name="image_emission" type="color3" xpos="9.913043" ypos="2.784483">
    <input name="file" type="filename" value="BoomBox_emissive.png" colorspace="srgb_texture" />
  </gltf_image>
  <gltf_pbr name="SR_boombox" type="surfaceshader" xpos="13.565217" ypos="-0.931035">
    <input name="base_color" type="color3" nodename="image_basecolor" output="outcolor" />
    <input name="alpha" type="float" nodename="image_basecolor" output="outa" />
    <input name="metallic" type="float" nodename="image_orm" channels="z" />
    <input name="roughness" type="float" nodename="image_orm" channels="y" />
    <input name="occlusion" type="float" nodename="image_orm" channels="x" />
    <input name="normal" type="vector3" nodename="image_normal" />
    <input name="emissive" type="color3" nodename="image_emission" />
  </gltf_pbr>
  <surfacematerial name="Material_boombox" type="material" xpos="17.391304" ypos="0.000000">
    <input name="surfaceshader" type="surfaceshader" nodename="SR_boombox" />
  </surfacematerial>
  <texcoord name="texcoord_vector2" type="vector2" xpos="6.695652" ypos="-1.362069" />
  <geompropvalue name="geompropvalue_vector2" type="vector2" xpos="6.644928" ypos="0.422414">
    <input name="geomprop" type="string" value="UV0" />
  </geompropvalue>
</materialx>

@JGamache-autodesk please review to ensure this will solve the issue properly. Thanks.

@kwokcb @JGamache-autodesk Usually we would wait until the next specification version to make a non-backwards-compatible change to a node interface, but let me know your thoughts on whether the uvindex input might have been so limited in its usage that we can safely drop it within MaterialX 1.38.

I believe that its probably uncommon to use multiple uv sets at least in the glTf context.  In which case uvindex is proably rarely set so won't cause a issue.
Due to the difficulty for Maya integration and it not showing up in Houdini, my hunch is that there is limited DCC adoption.
These were introduced last September and this issue is being raised now.

Sounds good to me, and I certainly like the new interface proposed here, which aligns strongly with existing nodes such as image.


Ingest settings formatting

List of boostrap servers is incorrectly formatted in https://github.com/lsst-uk/lasair-deploy/blob/main/roles/ingest/templates/settings.py.j2

Fixed.


Add cni folder to kubelet service

Create cni folder at start

Didn't we do that on the minions too @jonathanschwarze?

Thanks.


Add Foxglove schemas and generate ros/proto/jsonschema definitions

Public-Facing Changes

Description
TODO:

[ ] generate FileDescriptorSet for easy use with mcap/websocket
[x] generate TypeScript definitions for Node Playground
[ ] export TypeScript definitions from index.d.ts?
[x] generate .msg for ROS 2
[x] array lengths for matrices?
[x] add other types

Closes https://github.com/foxglove/studio/issues/3043

Curious why proto has a foxglove subdirectory and the others do not?

Curious why proto has a foxglove subdirectory and the others do not?

protoc --proto_path works like -I for compiling C/C++ code. If you want the imports to look like import "foxglove/X.proto"; then it needs to have a foxglove subdirectory.


fixed compile-error for 4.20

fixes #106

should be fixed with https://github.com/Koderz/RuntimeMeshComponent/commit/6bee6c39694fd69d6195614b9dc739edcbc4aa87 - closing.


Mark InOrderConsumerFactory as deprecated

This is not a great way to interact with Kafka - committing the offset after every message puts load on the cluster, especially with many high volume consumers. Additionally, kafka itself doesn't guarantee ordering across partitions. Kafka will deliver messages at least once, but achieving at-most-once should be done at the application layer since publishing to the cluster in many cases does not guarantee exactly-once.
In the future, we can revisit consumer best practices and potentially create multiple new consumer types for different use cases. But for now, we should at least discourage people from using this one.

Chatted with Syd (thanks for raising!), DevX is currently focused on Snoodev Code Yellow so we're paused on other things. We'll come back to this when we have bandwidth to support!

Closing this for now, it's very old - we can come back when ready


Param default fixes to v0

A number of issues here with the param default parsing:

Showing null for optional fields with initializers
Not showing defaults for when the "eg" field is used. Looks like this issue was fixed in master but never cherry-picked to v0.
When the parsed value is a string, not adding quotes.

Only part of this change needs to be cherry-picked to master. "Adding quotes around string literals"

master change: https://github.com/Microsoft/pxt/pull/2780


Add config to check if Media Service connector is installed.

Description:
Media Service API is implemented in the connector mode and therefore it will not be shipped with the default product. When the connector is manually installed in the product, there should be a configuration to check if the media service is actually installed before performing operations such as deciding whether to enable/disable profile image uploading in user portal.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Create nnnn-variadics-as-attribute.md

Reviewed pull-request for Variadics as Attribute.

In the discussion on the list, several people on the main mailing list are strongly against this, and I see little support.  I also see little chance that this would be accepted by the core team.  If you're serious about pursuing this, please continue on-list discussion and try to obtain more consensus.


Ask about user's opinion about the speed with which Rust evolves

The previous question was just... bad. This variation is hopefully more clear. I also think that it makes sense to ask this as the first question in this segment about Rust features.
Fixes: https://github.com/rust-lang/surveys/issues/248

I fear that this question might be a bit too broad to be useful. E.g. I'd wish Rust would evolve faster in some directions, but slower in others... (Though given the question as is, I'd likely answer that I'm happy with the current pace).
What are we measuring here and what actionable learning do we expect from this?

Good point, but I'm not sure if we can design a question that would enable us to find out the "pace opinion" for multiple areas (which areas?). Probably people will always want performance improvements, bug fixes etc., but might not want new features.
Regarding the motivation of this question, it's a bit complicated. It originally started with a question that follows this one, about features that people would like to see stabilized. This question was a bit controversial last year (see discussion in https://github.com/rust-lang/surveys/pull/243 if you're interested). What we would really like to find out are areas that Rust users struggle with, but it's not easy to figure that out with a closed answer set, and analyzing thousands of very liberally written open answers is also not something that we are good at. So we decided (as a compromise) to just include some basic list of most commonly requested features in the following question (and then we also have a question about problematic areas).
Then, out of this question, came up the idea about figuring out if people want any Rust features to be added at all. So what we are essentially measuring is the vibe about how fast Rust changes, if people want us to add new features or not, and how much has our complexity budget has already been spent. I think that this can be used to judge whether some new language features (which might be good ideas on its own) might perhaps be just too big of a change (like the recent is pattern matching discussion, or also the effect system comes to mind).
I think that the current set of questions about features/problems/pace of development is not great, but so far I have been struggling to figure out a better way to combine them together and derive what we actually want to ask our users.

Rebased and modified the perex + the first answer.


Add koa-bodyparser flow types, fix error [fusion-plugin-rpc]

I'm working in a fusion app that has koa-bodyparser flow types, and I'm getting an error when registering the plugin from fusion-plugin-rpc:
Error ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ node_modules/fusion-plugin-rpc/src/server.js:122:36

Cannot call bodyparser with bodyParserOptions bound to opts because inexact mixed [1] is incompatible with exact
Options [2].

     node_modules/fusion-plugin-rpc/src/server.js
     119│         throw new Error('Missing handlers registered to RPCHandlersToken');
     120│       if (!emitter)
     121│         throw new Error('Missing emitter registered to UniversalEventsToken');
     122│       const parseBody = bodyparser(bodyParserOptions);
     123│
     124│       return async (ctx, next) => {
     125│         await next();

     flow-typed/npm/koa-bodyparser_v4.x.x.js
 [2]  27│   declare module.exports: (opts?: Options) => Middleware;

     node_modules/fusion-plugin-rpc/src/tokens.js
 [1]  18│ export const BodyParserOptionsToken: Token<mixed> = createToken(

This PR adds the koa-bodyparser flow types using flow-typed, and fixes the flow error that results from using mixed instead of Options in the type used for the BodyParserOptionsToken.
I got around this in my application by removing the flow-typed file, but wanted to open a PR to report the issue I had as well as suggest an option to fix it.

!merge


Support other date delimiters in new date control

Select one ...  (check one with "x")
[ ] bug
[ ] feature request
[x ] enhancement

Expected behavior
Would be nice to support other date delimiters than "/". Sweden for example use "-" and Germany ".'
Actual behavior
Right now only "/" is supported.
Reproduction of behavior
Environment details

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web

@rbirkgit: Thanks for filing the issue!
I see that the date format which is retrieved from Angular for locale sv is y-MM-dd (https://github.com/angular/angular/blob/master/packages/common/locales/sv.ts#L40)
and for de is dd.MM.yy
(https://github.com/angular/angular/blob/master/packages/common/locales/de.ts).
I want to verify if we can use the delimiter in this format to display dates in the date picker input. I think we can but I just need to verify it once.
I would also have to consult with out UX team and our internationalization team to check what they think about this. I will add more updates to this tickets when I have more info.

in russian date format dd.MM.y
ru.ts

Hi, @adityarb88 i am set Locale to my app like { provide: LOCALE_ID, useValue: 'en-IN' } in app module, but it still showing the MMDDYYYY format only, actually it need to change into DDMMYYY format right?.How i get this format.
and i have a one more doubt, now if i change the actual date in datePicker i will get any onChnage event  now (change detection)?
Thank you.


Stop archiving the local Maven repository in CI builds

This fortunately has no benefit anymore as of [1], and not archiving the
local Maven repository should speed up CI builds.
[1] https://github.com/oss-review-toolkit/ort/pull/3445
Signed-off-by: Sebastian Schuberth<EMAIL_ADDRESS>

@mnonnenmacher I couldn't find any such code in the Azure builds, so I guess there never was any.


Specialize BufList::copy_to_bytes

Some implementations of the Buf trait have an optimized version (for
example Bytes) of copy_to_bytes, opportunistically use that one.
For some background, I was implementing a similar type and had a look there and noticed it is not implemented. Or is there some reason why it shouldn't be implemented?

Good idea! The implementation looks right to me (though trickier than I assumed before looking). What do you think of adding a few tests since it's tricky?

If only containing a single Bytes, the pointer should be the same before and after.

That it popped the buf if the length is the same.

That it handles a single buf that's longer.
That it handles multiple bufs.

OK, that makes sense. And yes, these things usually come with more corner cases than expected (this whole implementation doesn't even assume empty buffers are possible somewhere in the middle).
During the tests I've noticed this implementation doesn't panic if the request is longer than all the buffers put together. That is probably allowed, because the advance allows for non-panicking and copy_to_bytes doesn't have any note about panicking. But I think it would be better if it panicked. There are few possibilities:

Leave it as it is (+ add test for that it doesn't panic and takes the whole rest)
Add a trivial test at the top of the relevant block. But that one will call .remaining() which iterates through all the buffers one more time, which could be a bit slower.
Do the check after the copying is done, as the Bytes::remaining() is likely something much faster. The downside is, the data has already been consumed so we could either put it back (push_front), at the cost of added code complexity, or say that after a panic, the structure is in some unknown state anyway.
Port keeping pre-computed remaining length from the version I've written. The downside is added code complexity.
Use that :arrow_up: as a dependency. But it's a 0.1 crate (though I don't expect breaking the API of this particular type), it's additional dependency, and  your code has some actual benchmarks around this type.

So I'd like to know which option you'd prefer.

The default implementation does panic: https://docs.rs/bytes/1.0.1/src/bytes/buf/buf_impl.rs.html#816
It seems like we can just add the check to the _ => branch, since the other 2 would be delegating to another implementation that can do that same check.

The default implementation does panic

I know. I was just saying that an implementation is probably not required to panic in that situation.
As for the check, I was probably stressing too much over the fact that remaining iterates over all the inner buffers while IMO remaining should be cheap… but then, the default implementation did it too.


Is there any way to have the panel open in the middle and not only on top or bottom?

I want the panel to initialize in the middle but ater scrolling to the bottom to stay on the botttom and not be anchored to the middle

use umanoInitialPanelState.


Updated logo and updated favicon image to logo

Updated logo on all pages except resources , login and terms and conditions ( Since these pages do not have a logo)
Favicon of all the pages have been updated to the logo itself

Resolve Conflicts.

@SauravMukherjee44 conflicts have been removed


RegisterContentPresenter should always return true

Is your feature request related to a problem? Please describe.
I noticed an issue where a custom ContentControl (specifically my Frame control) was significantly slowing down runtime swapping of resources (like 300-350% slower) because Frame isn't currently registering it's ContentPresenter. This is in part because I don't use the PART_ naming prefix for template items, which is the only condition the base RegisterContentPresenter method will return true:
https://github.com/AvaloniaUI/Avalonia/blob/6cfa75aaf3cf8c2be841fa9433f5ff71d33e4f7c/src/Avalonia.Controls/ContentControl.cs#L108-L117
I still don't understand why this was the issue, as the logical tree (from devtools) still looked like it was set up correctly & styling applied normally, but it leads me to this:
From what I can tell, this method only serves the purpose of registering the parent ContentControl to the ContentPresenter. (From the code above, it also sets the presenter property on ContentControl, but only if you use that specific name). So is this method really even needed? Is there any case where you'd put a ContentPresenter in a ContentControl and wouldn't want it registered to the parent ContentControl?
There's also the issue of only registering if you name it PART_ContentPresenter, which is dangerous. Regardless of the PART_ prefix preference, it's possible the name may be desired to be something different to be more specific. Or there could be multiple ContentPresenter for multiple "content-like" properties.
So IMO, the base method in ContentControl should always return true to ensure a ContentPresenter is registered properly. And, the Presenter property on ContentControl should be protected set so derived controls can set this accordingly.

ContentControl only supports one presenter and there are places in the code base that assume that it can only have one presenter (like automation support)
ContentControl, like every other templated control, expects its single expected template child to have a certain name

So it seems that ContentControl is just not a suitable base class for your needs. You can have your own IContentPresenterHost  implementation that would always return true.

We should probably add a protected setter to Presenter property though, since otherwise the virtual flag on the RegisterContentPresenter doesn't really make sense.

ContentControl only supports one presenter and there are places in the code base that assume that it can only have one presenter (like automation support)

Yes, ContentControl can only have one presenter for its main content, but certain ContentControl derived controls can have more than one "content-like" property and therefore more than one ContentPresenter in its template. An example is SplitView, which registers the main ContentPresenter, and the one used in the pane:
https://github.com/AvaloniaUI/Avalonia/blob/d7414d39d83e213e3845853877e7ac9ea90b5c8b/src/Avalonia.Controls/SplitView.cs#L318-L328
Obviously the Presenter property can only be set to one, but based on my understanding of what RegisterContentPresenter does, that's not the main job and setting that property here is more convenience - it's more on hooking the ContentPresenter up to the ContentControl for something that I can't figure out (logical tree related?) and so always returning true here I don't think has a downside - and there's obviously has an impact if you don't register the presenter.

ContentControl, like every other templated control, expects its single expected template child to have a certain name

IMO, ContentControl should be treated more like a primitive control (not in the namespace sense) and therefore should NOT enforce template naming at this level. It's more a building block for derived controls like Button or List items and generally not used on its own. Derived controls should be where the template naming is enforced - as there may be more specific names desired at that level rather than something generic like "[PART_]ContentPresenter"

An example is SplitView

Looking at the code, it seems that automation support for SplitView might be broken, since it doesn't have its own automation peer and PART_PanePresenter isn't handled by ContentControlAutomationPeer


Switch to new design for Plugins and Middlewares handling

There are some useless work across the commits, like doing one thing then the reverse, I learned a few things here.

Thanks :+1: Merged to push the new implementation, will check later all the changes.


testing macros defined using CTEs

as I work on #59, I've had to disable ~17 tests in integration_tests/dbt_utils/dbt_project.yml for the same reason. The reason why is because of the pivot to the test block where code to be tested gets injected as a subquery into the result of get_test_sql(). For the ~17 or so macros being tested, they all use CTEs, which aren't allowed as subqueries in TSQL. previously this was only an issue for bespoke tests, where the solution was to tell users that CTEs in bespoke tests were not supported.
However, this issue is a bigger blocker, because now:

we don't have the ability to test dbt-utils macros in tsql, without first rewriting them to not use CTEs, and
even existing sqlserver__ ports of dbt-utils macros that were working would now need to be refactored to not use CTEs in order to be tested

the above two points are possible, but not ideal. Here's a commit of me doing it once, but I'm not looking forward to how this will look for a macro like get_date_spine.
your input is much appreciated as always @jtcohen6! It's a bummer that I didn't consider this scenario when testing dbt-sqlserver with dbt-core==0.20.0 initially.

@swanderz I recall discussing (somewhere) that T-SQL adapters might need to override the built-in test materialization, in addition to the get_test_sql macro, to do the following:

Create a temp table (instead of a subquery) that contains result of the test query
Select from that temp table to get fail_calc, should_warn, should_error`
If store_failures is enabled, make it a permanent table instead!

That feels a bit hacky, but it's the best workaround I can think of for the lack of nested-CTE support in T-SQL. I think all parts should be doable with existing dbt-core constructs.


How to compile?

How are you supposed to compile?
npm install
npm install --dev <-- a ton of errors
bower install
what am I missing?
grunt

The library is prebuilt and available for use, it can be found at dist/aws-sdk-mobile-analytics.min.js
To build it yourself simply run npm install and it will compile and minify to the dist location.


Reflection: Traffic in RemoteRefs.

Instead of passing around raw local pointers and references, and spreading
tricky offset arithmetic around with the Local/RemoteAddress fields in
ReflectionInfo, have the TypeRefBuilder code use RemoteRefs everywhere,
which keep the remote/local mapping together in one unit and provide
centralized API for this logic.
This doesn't yet change how code uses the RemoteRef address data to
follow pointers across objects, for things like reading type refs, but
that should be much easier to do after this lands.

@swift-ci Please test

@swift-ci Please test Windows

Build failed
Swift Test OS X Platform
Git Sha - 036a8e3972734a229664a08cfbc0d886dbfd2d6c

Build failed
Swift Test Linux Platform
Git Sha - 036a8e3972734a229664a08cfbc0d886dbfd2d6c

@swift-ci Please test

@swift-ci Please test Windows

Build failed
Swift Test Linux Platform
Git Sha - 036a8e3972734a229664a08cfbc0d886dbfd2d6c

Build failed
Swift Test OS X Platform
Git Sha - 036a8e3972734a229664a08cfbc0d886dbfd2d6c

@swift-ci Please test

@swift-ci Please test Windows

@swift-ci Please test Windows

Build failed
Swift Test OS X Platform
Git Sha - 20f3badcc63d3ad82fffdb6a905c6d97bbfd7b66

Build failed
Swift Test Linux Platform
Git Sha - 20f3badcc63d3ad82fffdb6a905c6d97bbfd7b66

@swift-ci Please test Windows

@compnerd The "Please test Windows" bot seemed to be ignoring my requests after the first one yesterday up until I tried again this morning. Known problem?

These Windows test failures look unrelated:
    Swift(windows-x86_64) :: Driver/sourceinfo_file.swift
    Swift(windows-x86_64) :: Driver/merge-module.swift
    Swift(windows-x86_64) :: Driver/advanced_output_file_map.swift

https://ci-external.swift.org/job/swift-PR-windows/87/


Add filter function for land overpasses.

Adds _filter_land() to radiometer level1 processing to filter out data taken over land.

This branch is now in conflict with changes in the restructuring of the post-processing. Are the changes here still relevant or already included in there?


firefox enable content sandbox

Issue description
Firefox's common.nix includes this.
Can we enable the sandbox now?
  configureFlags = [
    ...
    #"--enable-content-sandbox" # TODO: probably enable after 54
    ...
  ]

That comment can be removed. From some investigating into old-configure.in that configure flag is seemingly gone. Also Content Process Sandboxing reports true in about:support which makes me believe that it has been folded into the default enabled sandbox.


Implement formatter / indentation

I have the BashSupport plugin installed in IntelliJ IDEA (version 12.1.2) and
am using an Emacs-based keymap, so my tab key executes the 'Emacs Tab' action.
When I edit bash files, the tab key does not indent at all (the cursor remains
at its current location). If I switch to the Default keymap, the tab key
inserts the expected 4 space characters (I've configured "Use tab character" ==
false, and "Tab size" == 4), but it is inserting 4 characters on every Tab
keypress. Ideally, I'd like the tab character to auto-indent based on the
surrounding code context, for example, if I'm indenting a line inside an "if"
block that is already indented by 4 characters, I expect a single tab keystroke
to take me to column 8. Currently, when using the Default keymap I have to
press tab twice to move from the cursor from column 0 to column 8. I seem to
remember that this was working in a previous version but appears to be broken
now.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 30 Apr 2013 at 4:11

I'm affected by this. I am also using the emacs keymap and in bash files "Tab" does nothing.
Ideally pressing tab with the cursor being anywhere on the line would cycle through all reasonable indentations. Alternatively it would already be great if a tab press would increase the indentation by one block (e.g. 4 spaces, depending on indentation settings), again with the cursor being anywhere on that line, i.e. this  would be the inverse of Shift-Tab, which correctly undents already now.
Does any one have any clue where to start with fixing this. I'm willing to investigate, but I have very little knowledge of Intellij plugin development.


Is it possible to use SPFx extensions to customize command bar in modern page in communication site?

Currently we can use SPFx extensions to customize command bar in List view, Site content page or Library. Is it possible to customize command bar of home/article page in communication site?

Unfortunately, that's not supported currently. Technically you can have list view command set in pages library, but that's not yet visible in page view side.


请问如何设置网页版协议登陆

puppet例子里面默认的是wechaty-puppet-hostie，我试了下设置成
os.environ['WECHATY_PUPPET'] = 'wechaty-puppet-puppeteer'，
这样不行，请问应该如果正确设置

You can create hostie token from web protocol, refer to: How to create your own Wechaty Hostie Token with the Web Protocol . But we don't recommand you to use this protocol, which is not stable wechat account.
you can apply padplus token from https://github.com/wechaty/wechaty/issues/1941 . Hope it can help you !

Have you made bot working good to you? If it does, we will close this issue later.


Implementation of WeakDampingODE class that represents exemplary ODE

The goal is to upload weak linear damping simulations into SolverDescription paper.

Code to copy:
from dynpy.models.odes.nonlinear import WeakNonLinearOscillatorMSM
WeakNonLinearOscillatorMSM.from_reference_data()