nvm installation fails on fedora 19 with "Unable to access nvm.git" error

Operating system and version: Fedora 19 running on Virtual Box

nvm debug output:
nvm debug
bash: nvm: command not found...

nvm ls output:

How did you install nvm? (e.g. install script in readme, Homebrew):

What steps did you perform?
sudo wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash

What happened?
nvm isntallation failed with the following error:
=> Downloading nvm from git to '/home/sukumad1/.nvm'
=> Cloning into '/home/sukumad1/.nvm'...
fatal: unable to access 'https://github.com/creationix/nvm.git/': Peer reports incompatible or unsupported protocol version.
Failed to clone nvm repo. Please report this!

What did you expect to happen?
expected nvm to install correctly

Is there anything in any of your profile files (.bashrc, .bash_profile, .zshrc, etc) that modifies the PATH?

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?

About to connect() to nodejs.org port 443 (#0)

Trying <IP_ADDRESS>...
Connected to nodejs.org (<IP_ADDRESS>) port 443 (#0)
Initializing NSS with certpath: sql:/etc/pki/nssdb
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
SSL connection using TLS_RSA_WITH_AES_128_CBC_SHA
Server certificate:
subject: CN=*.nodejs.org,OU=PositiveSSL Wildcard,OU=Domain Control Validated
start date: Aug 14 00:00:00 2017 GMT
expire date: Nov 20 23:59:59 2019 GMT
common name: *.nodejs.org
issuer: CN=COMODO RSA Domain Validation Secure Server CA,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB

HEAD /dist/ HTTP/1.1
User-Agent: curl/7.29.0
Host: nodejs.org
Accept: /
Accept-Encoding: deflate, gzip

< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Thu, 13 Jun 2019 05:00:28 GMT
Date: Thu, 13 Jun 2019 05:00:28 GMT
< Content-Type: text/html
Content-Type: text/html
< Connection: keep-alive
Connection: keep-alive
< Set-Cookie: __cfduid=d2f9d2d2a458eb04fbb99b1eac5b0d56c1560402028; expires=Fri, 12-Jun-20 05:00:28 GMT; path=/; domain=.nodejs.org; HttpOnly
Set-Cookie: __cfduid=d2f9d2d2a458eb04fbb99b1eac5b0d56c1560402028; expires=Fri, 12-Jun-20 05:00:28 GMT; path=/; domain=.nodejs.org; HttpOnly
< CF-Cache-Status: HIT
CF-Cache-Status: HIT
< Expires: Thu, 13 Jun 2019 09:00:28 GMT
Expires: Thu, 13 Jun 2019 09:00:28 GMT
< Cache-Control: public, max-age=14400
Cache-Control: public, max-age=14400
< Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< Vary: Accept-Encoding
Vary: Accept-Encoding
< Server: cloudflare
Server: cloudflare
< CF-RAY: 4e618045dd7dd732-SYD
CF-RAY: 4e618045dd7dd732-SYD
< Content-Encoding: gzip
Content-Encoding: gzip
<

Connection #0 to host nodejs.org left intact

Note: I have already updated by GIT and also ran the following:
yum update -y nss curl libcurl
Still not working

You ran the install script with sudo - that won't do what you expect. One of the whole points of nvm is to not have to use sudo.
What happens if you rerun the installation script as it is in the readme verbatim?

Getting the same error even without sudo
wget -qO-
https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
=> Downloading nvm from git to '/home/sukumad1/.nvm'
=> Cloning into '/home/sukumad1/.nvm'...
fatal: unable to access 'https://github.com/creationix/nvm.git/': Peer
reports incompatible or unsupported protocol version.
Failed to clone nvm repo. Please report this!
On Thu, Jun 13, 2019 at 3:38 PM Jordan Harband<EMAIL_ADDRESS>wrote:

You ran the install script with sudo - that won't do what you expect. One
of the whole points of nvm is to not have to use sudo.
What happens if you rerun the installation script as it is in the readme
verbatim?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nvm-sh/nvm/issues/2064?email_source=notifications&email_token=AMK77UWWT4RIAZE4MAAQO4LP2HMNBA5CNFSM4HXV5CC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXSSEEQ#issuecomment-501555730,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMK77USULV6PTDGXNCQJJGLP2HMNBANCNFSM4HXV5CCQ
.

What version of git do you have? Per the readme, nvm requires v1.7.10 or later.

git version <IP_ADDRESS>
On Thu, Jun 13, 2019 at 4:56 PM Jordan Harband<EMAIL_ADDRESS>wrote:

What version of git do you have? Per the readme, nvm requires v1.7.10 or
later.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nvm-sh/nvm/issues/2064?email_source=notifications&email_token=AMK77UVOQJBWTU56WJ7PUEDP2HVR5A5CNFSM4HXV5CC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXSWW6Q#issuecomment-501574522,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMK77UROEEADVR3I5S37QE3P2HVR5ANCNFSM4HXV5CCQ
.

What happens if you try to git clone the repo directly? if https is unsupported, perhaps your OS is missing OpenSSL?

Can you please let me know how to git clone?

git clone https://github.com/nvm-sh/nvm.git ~/.nvm

Same error even with git clone:
[sukumad1@f19_vm_sukumad1 Downloads]$ git clone https://github.com/nvm-sh/nvm.git ~/.nvm
Cloning into '/home/sukumad1/.nvm'...
fatal: unable to access 'https://github.com/nvm-sh/nvm.git/': Peer reports incompatible or unsupported protocol version.

In that case, it’s not a problem with nvm - it’s that your machine is unable to connect to https with git.
Perhaps your ssl certs are out of date, or perhaps your machine is lacking OpenSSL? I’m not sure how to help you from here.


System.InvalidOperationException: 'The control already has a visual parent.' Menu

Describe the bug
Throw System.InvalidOperationException when click on menu
To Reproduce
Steps to reproduce the behavior:

Run ControlCatalog.NetCore
Go Menu
Click on First Menu
Change Theme to FluentDark
Click on First Menu
See error

Expected behavior
it do not Throw System.InvalidOperationException
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

Version: dc6df28e77671109e0b75e6b18b30022608c4f78

Additional context
Add any other context about the problem here.

It is probably the same problem as #4058.

Dup of https://github.com/AvaloniaUI/Avalonia/issues/4839
Caused by materialized controls used as items source, which can't be reused with another parent (after theme was switched, template with itemspresenter is replaced)


adding sphinx sidebars functionality

Apparently I had time to figure this out after all :-)
This PR makes this theme use the html_sidebars functionality of Sphinx. The default behavior is the same, but now if users modify html_sidebars, then the results will show up in their site.
closes #244 (and maybe addresses some of the other sidebar issues?)
I'm pretty sure the failing test is the same jupyter-sphinx bug @jorisvandenbossche mentioned elsewhere
and see here for a page where I added a custom sidebar! https://pydata-sphinx-theme--248.org.readthedocs.build/en/248/contributing.html

ping to @jorisvandenbossche - let me know if you want me to self-merge this kinda thing but I feel like it's good practice to have at least another pair of 👀 on things...

@choldgraf can you merge master or rebase, seems to be a conflict with theme.conf

done! let's see if tests pass


[WSL] EXDEV: cross-device link not permitted

I asked about this on gitter: [ ]
Link to my question on gitter:

Expected Behavior
ganache-cli should start.
Current Behavior
ganache-cli does not start.
It did work fine in version 6.5.1.
Possible Solution
Use a module like mv: https://github.com/andrewrk/node-mv as suggested in https://stackoverflow.com/a/43206506/1226799
Steps to Reproduce (for bugs)
In WSL:
$ npx ganache-cli --db blockchain_db
Ganache CLI v6.9.0 (ganache-core: 2.10.1)
Error: EXDEV: cross-device link not permitted, rename '/tmp/tmp-1580wcSrmVw2vfps' -> 'blockchain_db/!trie_db!0x41c488877f4bd7f076e7a46574f86eb2e58bb101aad9fd4da0dbf9b60ec8c949'

npx ganache-cli does work fine.
So does: mkdir --parents ~/blockchain_db && npx ganache-cli --db ~/blockchain_db/
Context
I'm trying to start a database and sometimes need to use it later with the same state.
Your Environment

Version used: Ganache CLI v6.9.0 (ganache-core: 2.10.1)
Version of Truffle/Remix/Other tools used:
NodeJS Version: v10.17.0
Operating System and version (include distro if Linux): WSL, Ubuntu 18.04.3 LTS
Link to your project or repro gist: https://github.com/microsoft/0xDeCA10B
Commit hash to use with above link for reproduction:
I intend to submit a pull request to fix this issue: [ ] I might.

Looks like this is already reported in https://github.com/trufflesuite/ganache/issues/1617
and should be corrected by https://github.com/trufflesuite/ganache-core/pull/548

Yup (closing since this is a duplicate)! We're smoketesting the release today and will release a new version soon.


Add filter specific contexts and root contexts.

Signed-off-by: John Plevyak<EMAIL_ADDRESS>For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

I am wondering what is the use case of root context sharing?

If I understand the lifecycle correctly, the use case is pre-computation of config and/or config-related caches. WASM module is instantiated per request, so it is too expensive to do any kind of parsing without a  shared context.

Yeah that is sharing a root context by all stream contexts in a module and the current state. But if I understand the proto change correctly, this PR introduces a mechanism to share root context across modules. And I am not clear on what's the use case of that. It seems minor to me to save initialization work when creating a new module.

This PR makes it possible to share root contexts within a VM (not between VMs).   This permits multiple filters to run in a single VM but with arbitrary sets sharing the same Context and RootContext subclass and the same RootContext.
One of the primary use case for this is the Null VM where it is not possible to use global or thread_local variable to share state because global's would be shared over all VMs and thread_local variables would be shared by a VM and the concurrently running new-configuration (filter-chain) VM during a reconfiguration event (xDS).
For portability between the Null VM and WASM, shared state should be stored in subclasses of RootContext.
I am looking for feedback on this API and this is based on my understanding of what you guys have asked for.

Is there a way to add bianpengyuan as a reviewer ?

I have added a RootContext* getRoot(string_view root_id) call which allows cross-root access for full sharing within a VM.  PTAL

@jplevyak Sorry to bug you but just want to double check, is my understanding correct about how to use these new config?


ci: add kuberentes version matrix for kind tests

Signed-off-by: Anish Ramasekar<EMAIL_ADDRESS>
Reason for Change:

Adds kubernetes version matrix with kind for e2e tests
Refactors the pipeline to run more jobs in parallel

Requirements

[x] squashed commits
[x] included documentation
[x] added unit tests and e2e tests (if applicable).

Issue Fixed:

Does this change contain code from or inspired by another project?

[ ] Yes
[x] No

If "Yes," did you notify that project's maintainers and provide attribution?
Special Notes for Reviewers:

/azp run e2e-pr


Some rst sections' content omitted from output

$ git clone https://github.com/pypa/setuptools
$ rich setuptools/docs/pkg_resources.rst

The last bunch of sections have headers but no content in the output, though content exists in the input.

@wasi_master Do you recognise this issue?

Those may just be footers? And footers are usually in the bottom. I'll have to test further. But I'll need a reproducible example

I've fixed the issue locally

@willmcgugan Fixed in 1.1.7, You can close this issue


Add documentation about KMP_AFFINITY

Description of the feature
Because https://github.com/pyansys/pymapdl/issues/1213 Some information should be added to the dev-guide.
Steps for implementing the feature
Create a PR in dev-guide.
Useful links and references
No response

Closing because it is proposed in: https://github.com/ansys/ansys-dev/pull/81


chore(job): migrate region step 1 update_company_with_field_mask to j…

Description
Fixes Internal: (b/347826075)[http://b/347826075]
Checklist

[x] I have followed Sample Format Guide
[ ] pom.xml parent set to latest shared-configuration
[ ] Appropriate changes to README are included in PR
[ ] These samples need a new API enabled in testing projects to pass (let us know which ones)
[ ] These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
[ ] Tests pass:   mvn clean verify required
[ ] Lint  passes: mvn -P lint checkstyle:check required
[ ] Static Analysis:  mvn -P lint clean compile pmd:cpd-check spotbugs:check advisory only
[ ] This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
[ ] This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
[x] Please merge this PR for me once it is approved

@code-review-assist review

@code-review-assist review


PreserveCompilationContext needs to be set only if a project has any …

…Razor files
Fixes #2077

🆙 📅


Check for existing webhook before creating it

When pushing an app, check if the webhook already exists before creating
it or it will crate a webhook for every push and consequently will trigger
the pipeline multiple times.

CI is breaking because forked PRs don't have access to GitHub secrets. I created a PR which will hopefully fix it: https://github.com/SUSE/carrier/pull/176/files
this one should be rebased when #176 is merged.

ok CI is good, you just have to put a fix: in-front of your commit message to make the conventional commit linter happy: https://github.com/SUSE/carrier/blob/main/docs/development.md

All good, merged! Thanks again.


Mapping configured by CRD are not being picked up by default when also configuring from the filesystem

Describe the bug
https://www.getambassador.io/docs/latest/topics/running/running/#configuration-from-the-filesystem says:

Note well that while the Ambassador Edge Stack will read its initial configuration from this directory, configuration loaded from Kubernetes annotations will replace this initial configuration. If this is not what you want, you will need to set the environment variable AMBASSADOR_NO_KUBEWATCH so that the Ambassador Edge Stack will not try to update its configuration from Kubernetes resources.

but when I do that, I only see the mapping configured from the filesystem.
To Reproduce
Steps to reproduce the behavior:

Deploying ambassador from the chart and pass a valid configuration to ambassadorConfig
Apply a simple mapping as described in https://www.getambassador.io/docs/latest/topics/using/mappings/#advanced-mapping-configuration
Open the diagnostics UI
The mappings defined throught the config will be there, but the ones done via CRD will not

Expected behavior
I expected both the mapping configured using the config and the CRDs to show up
Versions (please complete the following information):

Ambassador: 1.4.0
Kubernetes environment: N/A

Additional context
I see a log line in the ambassador pods that says:
AMBASSADOR INFO not watching for Kubernetes config

which I believe comes from:
https://github.com/datawire/ambassador/blob/081cb9b1a8743e3155b0ab21f4cbd141f848d2b2/python/entrypoint.sh#L159-L169
So, it seems that the docs are saying the contrary of what happens. Can we update the docs? (not sure if we can change the default or it will be considered a braking change).

We can definitely update those (very out-of-date 🙁) docs -- in fact, if you want to submit a PR there, that'd be awesome! Otherwise we'll tackle it as soon as we can.

The CRDs are available in our QuickStart guide.


rename opengpt by rungpt

@numb3r3 I think we can release 0.1 or even 1.0 after this pr is merged

@huangkaipeng4399 Does the example script works with run_gpt?


Support for Unit Testing of Transforms in Substation

Is your feature request related to a problem? Please describe.
When looking into adopting Substation as a potential solution, one of the pieces that made it difficult to commit fully was the absence of built-in unit testing to ensure that transforms function as expected prior to being deployed.
I was hoping to see unit tests that would allow me to write a transform for a given data source and on PR or as part of some sort of command line utility, execute that unit test to verify that my transform is in a working state. This test would ideally give a success or failure output right in the console and an exit code. This would help me to trust my changes as well as expedite the collaboration process with teammates.
Describe the solution you'd like
One of the components that I think could really enhance adoption and utility of Substation, is integrated support for unit testing transforms.
What I would hope to see is the ability to specify a unit test very close to the transform itself, whether in the same file or a neighboring file. where you could assert things like field foo matches string bar, field foo is number - or any of the other conditional statements that are baked into the substation transform library could be used as validation checks to guarantee the output field matches the assertion.
Some ideas for what this could look like might be from chatting about this on slack (100% @jshlbrd's cool idea here):
// Toy example of an embedded unit testing framework that reuses existing
// Substation packages. The `substation-test` app has this workflow:
// 1. Compile `transforms` (which modify data).
// 2. Compile `tests[].transforms` (which create input test data).
// 3. Compile `tests[].condition` (which checks the output test data).
// 4. Run the tests against the `transforms`.
local sub = import '../../../substation.libsonnet';

local utest = [
  sub.tf.obj.insert({ obj: { target_key: 'foo' }, value: 'bar' }),
  sub.tf.send.stdout(),  // Optional: print the input data to stdout for debugging.
];

{
  tests: [
    {
      name: "substation-pass",
      // Use transforms to create input data for the test.
      transforms: utest,
      // Apply a condition to the output data to check the test result.
      condition: sub.cnd.str.eq({obj: { source_key: 'baz'}, value: 'qux' }),
    },
    {
      name: "substation-fail",
      // Use transforms to create input data for the test.
      transforms: utest,
      // Apply a condition to the output data to check the test result.
      condition: sub.cnd.num.len.eq({value: 0 }),
    },
  ],
  // Each test is run against these transforms.
  transforms: [
    sub.tf.obj.insert({ obj: { target_key: 'baz' }, value: 'qux' }),
  ]
}

I like that the data, tests, and transforms are all baked into a singular file making the connection between tests and their business logic very transparent.
Where my idea might deviate from this is that I would hope to see this functionality built into a single substation binary. I would prefer to be able to write substation test *.jsonnet directly in my CLI and also be able to write substation build *.jsonnet to build a substation app or substation run *.json to run it (this could be opened as a separate issue, since I know this deviates from how substation works. But a central, vended, entrypoint for my substation workflow including unit testing mentally clicks a lot better in my head than a dedicated unit testing CLI .)
Describe alternatives you've considered
The alternatives I've considered are primarily built into other tools. A great example is Vector's built-in support for unit testing with their VRL language. In Vector, you can easily map an input source, a transform, and an output destination for your unit test. If the input data matches your output assertions, the unit test passes.
This feature allows you to create detailed, comprehensive unit tests that validate the presence and structure of each expected field. It is also run through the same executable that is used to run the pipelines, just a different CLI entrypoint - making the workflow super easy.
Additional context
https://vector.dev/docs/reference/configuration/unit-tests/
Example of a unit test in Vector that validates the existence of fields from the incoming data.
source: |
  assert!(exists(.message), "no message field provided")
  assert!(!is_nullish(.message), "message field is an empty string")
  assert!(is_string(.message), "message field has as unexpected type")
  assert_eq!(.message, "success", "message field had an unexpected value")
  assert!(exists(.timestamp), "no timestamp provided")
  assert!(is_timestamp(.timestamp), "timestamp is invalid")
  assert!(!exists(.other), "extraneous other field present")

Thanks @britton-from-notion for the detailed write-up! It shouldn't take much effort to get this working because the necessary parts already exist.

Where my idea might deviate from this is that I would hope to see this functionality built into a single substation binary. I would prefer to be able to write substation test *.jsonnet directly in my CLI and also be able to write substation build *.jsonnet to build a substation app or substation run *.json to run it (this could be opened as a separate issue, since I know this deviates from how substation works. But a central, vended, entrypoint for my substation workflow including unit testing mentally clicks a lot better in my head than a dedicated unit testing CLI .)

Agreed that this is a separate issue. I think what you're describing is a utility application for managing source code and configurations. Most of the apps under cmd/development could fit within that, with some changes. For example:

substation build -- builds config files (wraps jsonnet)
substation fmt -- formats config files (wraps jsonnetfmt)
substation test -- runs config unit tests
substation version -- pull local release version (from github metadata)

I'm not sure what the behavior of substation run would be, but it might encapsulate the existing file and Kinesis development apps. Since deployments are decentralized and managed by Terraform, it's unlikely that it would ever support a command like substation deploy.


git-sync container restarts

We have Airflow setup on Kubernetes.
Currently our git repo performs a maintenance once a day, which causes airflow git-sync container to fail with error 503 and restart itself and the whole worker/web/scheduler pod.
Error looks like the following:
"msg"="too many failures, aborting" "error"="Run(git ls-remote -q origin refs/heads/develop): exit status 128: { stdout: "", stderr: "Bitb ││ ucket is currently unavailable:\n- The system is unavailable while maintenance is being performed.\n- Bitbucket is unavailable while it is being backed up\nfatal: Could not read from ││  remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n" }"  "failCount"=0
Is there a way to prevent git-sync container restart on occasions when git repo is not reachable?

@DenysKunak you can set the dags.gitSync.maxFailures to a non 0 value, this will allow a certain number of failures before the git-sync container restarts.
dags:

  ## configs for the git-sync sidecar (https://github.com/kubernetes/git-sync)
  ##
  gitSync:

    ## the number of consecutive failures allowed before aborting
    ##  - the first sync must succeed
    ##  - a value of -1 will retry forever after the initial sync
    ##
    maxFailures: 0


Have a Table empty content

Describe the feature you'd like
Have a component that allows me to ship a consistent UX when a table is empty.
Describe alternatives you've considered
Each product has somehow its own way to display an "empty" table. It would be great if we can drop as much as possible the internal implementations of this scenario and fall back to a Wave solution.

This is duplicated by #130


the email body does not contain the name of the reciver when the reciver has set the language to german

Describe the bug
When a space is shared to a group and if a member of that group is using german language he gets a mail notification without his name.
Hallo <no value>,

Admin hat Sie eingeladen, dem Space "<space-name>" beizutreten.

Zum Ansehen hier klicken: <base-url>/f/<space-id>

Steps to reproduce
Steps to reproduce the behavior:

create a space as marie
create a group group1
add einstein to that group
change einstein's language to de
share that space with group1
einstein gets a mail notification

Expected behavior
einstein should receive mail notification with his name
Expected email body
Hallo <user-name>,

Admin hat Sie eingeladen, dem Space "<space-name>" beizutreten.

Zum Ansehen hier klicken: <base-url>/f/<space-id>

Actual behavior
einstein receives mail notification without his name
Setup
Ocis : latest master
Additional context
Add any other context about the problem here.

Do space-name and base-url get filled in correctly in the email?

I fixed the placeholder in transifex.
Needs a re-sync

Should be fixed now https://github.com/owncloud/ocis/commit/164b24cc41295587ef9baeb2dee9d8f06d0c7b87
Can you re test please?

Do space-name and base-url get filled in correctly in the email?

yes space-name gets filled with the spaces name and base-url with https://localhost:9200


Send to back

Hey, girls,
we created the fetch that collects the form data, sends it back and collects the url back. Also the collapsible create card button.
Can you please check it?

Thanks for checking. I deleted the console logs and imports that were not used.

Ok @rodriguezmontesinoseva. You can merge.


#180 only highlight first item of valid filtered results

Addresses #180

Clear fix and good tests, thanks a lot!


GoodTwitter

GoodTwitter extension appears to be broken today.. I am using Opera for MAC & took an Apple & an Opera update last night so not sure if all of that has anything to do with the GoodTwitter problems I am experiencing this morning.. I have tried the uninstall, install & everything else your site has suggested but GoodTwitter still appears to revert back to the new twitter format..

I did that one hour ago actually I did that several times... I uninstalled and installed again and still having problems IMO Twitter has turned this extension off..
from my MAC
-----Original Message-----
From: Gabriela<EMAIL_ADDRESS>To: ZusorCode/GoodTwitter<EMAIL_ADDRESS>Cc: casperandangel<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Sent: Wed, Oct 16, 2019 11:34 am
Subject: Re: [ZusorCode/GoodTwitter] GoodTwitter (#26)
Try clearing all the cookies from the site. It will require signing in again though.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

It's working for me in Windows though.

I complained to Opera & Google on my Twitter account and Opera just sent 3 different updates & now all looks good with GoodTwitter extension and the other extensions I use from Chrome store..
from my MAC
-----Original Message-----
From: Gabriela<EMAIL_ADDRESS>To: ZusorCode/GoodTwitter<EMAIL_ADDRESS>Cc: casperandangel<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Sent: Wed, Oct 16, 2019 12:24 pm
Subject: Re: [ZusorCode/GoodTwitter] GoodTwitter (#26)
It's working for me in Windows though.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


[Download-Artifacts] CDN Issues?

Describe the issue
since a few days we get problems with the download of artifacts over the CDN. The direct access to the blob works very well and fast.
unfortunately/ fortunately the problem does not always occur.
we could observe the problem in different infrastructures/networks.
Scripts used to create container and cause the issue
$ArtifactUrl = Get-BCArtifactUrl -select Weekly
Download-Artifacts -artifactUrl $ArtifactUrl

Full output of scripts
BcContainerHelper version 4.0.14
Setting defaultNewContainerParameters = @{shortcuts=CommonDesktopFolder}
BC.HelperFunctions emits usage statistics telemetry to Microsoft

Downloading application artifact /sandbox/21.5.53619.54140/at
https://bcartifacts.azureedge.net/sandbox/21.5.53619.54140/at
Downloading C:\Users\AzDevOps\AppData\Local\Temp\048ca889-0cd5-4800-a16a-d3a801741438.zip
Using WebClient
Unpacking application artifact to tmp folder using 7zip

ERRORS:
Unexpected end of archive

ERROR: Data Error : Applications.AT\Base Application.Source.zip
Error unpacking artifact downloaded from CDN, retrying download from direct download URL
https://bcartifacts.blob.core.windows.net/sandbox/21.5.53619.54140/at
Downloading C:\Users\AzDevOps\AppData\Local\Temp\89ce7fdd-6697-477c-8965-e9410036b38a.zip
Using WebClient
Unpacking application artifact to tmp folder using Expand-Archive

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context

does it happen all the time? No
did it use to work? Yes

@freddydk +1
We have seen this error message "Unexpected end of archive" or "Could not download" a lot in the last few days.
BcContainerHelper is version 4.0.14
BcContainerHelper is running as administrator
HyperV is Enabled
UsePsSession is True
Host is Microsoft Windows Server 2019 Standard - 10.0.17763.4010
Docker Client Version is 19.03.5
Docker Server Version is 19.03.5
Removing Desktop shortcuts
loading application artifact /sandbox/21.5.53619.54140/de
https://bcartifacts.azureedge.net/sandbox/21.5.53619.54140/de
Downloading C:\Windows\TEMP\44179ce0-9583-4a8c-8773-7be8e58ea830.zip
Using WebClient
Could not download from https://bcartifacts.azureedge.net/..., retrying from https://bcartifacts.blob.core.windows.net/ in 3 seconds...
Using WebClient
Download-Artifacts Telemetry Correlation Id: 05dad3f9-70c1-4074-b176-8084095f2522
New-NavContainer Telemetry Correlation Id: f6dafd4c-fbec-43c6-af56-0cdb55617b95

I'm having the same issue with US artifacts.  My error looks like this:

If you use:
Get-BcArtifactUrl -storageAccount 'bcartifacts.blob.core.windows.net' -select weekly -country us
Then it will never try the CDN, but will go directly for the storageaccount.
(same with bcinsider and other storageaccounts)

It would help if you would specify which artifacts you are trying to download (and how)

Sure, sorry forgot to write it.
I execute the folowing code
$artifactUrl = Get-BCArtifactUrl -type Sandbox -country de -select Latest -storageAccount BCPublicPreview
 $containerCreationParameter = @{
            artifactUrl               = $artifactURL
            containerName             = $Name
            licenseFile               = $LicenseFile
            auth                      = 'NavUserPassword'
            Credential                = $Credential
            shortcuts                 = 'CommonDesktop'
            additionalParameters      = $EnvironmentVariables
            restart                   = 'always'
            accept_eula               = $true
            accept_outdated           = $true
            alwaysPull                = $false
            assignPremiumPlan         = $true
            doNotUseRuntimePackages   = $true
            includePerformanceToolkit = $false
            includeTestToolKit        = $true
            includeTestLibrariesOnly  = $true
            useBestContainerOS        = $true
            useSSL                    = $true
            updateHosts               = $true
            useTraefik                = $useTraefik
            PublicDnsName             = $PublicDnsName
            multitenant               = $true
            isolation                    = 'process'
            myscripts                    = $Scripts
        }

        try {
            New-BcContainer @containerCreationParameter -ErrorAction Stop
        } catch {
            Write-Host "Couldn't create Container"
            Write-Host $_
            return $_
        }

My Ouput (This try downloaded the application artifacts directly)
BcContainerHelper version 4.0.14
BC.HelperFunctions emits usage statistics telemetry to Microsoft
BcContainerHelper is version 4.0.14
BcContainerHelper is running as administrator
HyperV is Disabled
UsePsSession is True
Host is Microsoft Windows Server 2022 Datacenter - 10.0.20348.1607
Docker Client Version is 23.0.1
Docker Server Version is 23.0.1
Removing Desktop shortcuts
Downloading application artifact /sandbox/22.0.54157.54529/de
https://bcpublicpreview.azureedge.net/sandbox/22.0.54157.54529/de
Downloading C:\Users\mje\AppData\Local\Temp\4183fa9b-846d-4fd5-9c03-ef4af0603cbe.zip
Using WebClient
Unpacking application artifact to tmp folder using 7zip
Downloading platform artifact /sandbox/22.0.54157.54529/platform
https://bcpublicpreview.azureedge.net/sandbox/22.0.54157.54529/platform
Downloading C:\Users\mje\AppData\Local\Temp\bfd4a7f6-cdd6-4ad0-bfe4-dbdb18de8533.zip
Using WebClient

Then it stucks here and i stopped it after an hour.

If you use:
Get-BcArtifactUrl -storageAccount 'bcartifacts.blob.core.windows.net' -select weekly -country us
Then it will never try the CDN, but will go directly for the storageaccount. (same with bcinsider and other storageaccounts)

Oh good to know, i'll try this. 😊
Thanks

I will add a setting to BcContainerHelper which you can set to avoid the use of CDN - meaning that it will always go for direct blob storage.
In most cases, this will be slower - but if there are issues with the CDN - it will use that.
When a machine has problems with CDN - then I will set this setting for the session to avoid future usages of CDN.
After a restart or a PS restart - it will retry (unless set in settings file)
Make sense?

Shipped in 5.0.2


.displayName missing in snapshot tests

We have a great number of buttons in our app and created some handy exports to make them easily usable:
import ActionButton, { PrimaryButton } from '../../ui/buttons/ActionButtons';

export const CancelButton = props => (
  <PrimaryButton
    icon="cancel"
    text={t('popups.actions.cancelAppointment')}
    {...props}
  />
);
// CancelButton.displayName = 'CancelButton';

export const BackAlternativeButton = props => (
  <ActionButton
    icon="arrow-left"
    text={t('popups.actions.alternativesBack')}
    {...props}
  />
);
// BackAlternativeButton.displayName = 'BackAlternativeButton';

// ActionButtons.js
import Button from './Button'; // pretty complicated Button that implements sizes, borders, loading etc.

const ActionButton = props => <Button size="l" {...props} />;
const PrimaryButton = props => <ActionButton buttonType="primary" {...props} />;

export default ActionButton;
export { PrimaryButton };

The buttons look and work as expected. But when creating snapshot tests (or using react-storybook), the displayName used is either Unknown or Component:
<Unknown
  disabled={false}
  isLoading={false}
  onClick={[Function]}
/>

// if one of the button is contained within React.Fragment, we receive this:
<Component
  disabled={true}
  key="decline"
  onClick={[MockFunction]}
/>

Only by manually adding a displayName (like above) we get the correct JSX output.
Is this by design? It's a pretty simple workaround (just add .displayName properties), but it's a bit annoying nonetheless :-)
Version
styled-components: 2.4.0
babel-plugin-styled-components: 1.4.0
Expected Behavior
The snapshot should contain the correct component name.
Actual Behavior
The snapshot contains Unknown or Component for the component name.

Shouldn't it be like that instead?
"babel": {
    "plugins": [
      "styled-components"
    ]
  }

I mean styled-components instead of babel-plugin-styled-components

@doque do you still get that behaviour?
I'm testing with:
"styled-components": "^3.3.3",
"babel-plugin-styled-components": "^1.5.1",

and I don't get this anymore.


RuntimeError when executing models/tutorials/image/cifar10/cifar10_train.py

Environment info
Operating System:
Ubuntu Server 16.04LTS
Installed version of CUDA and cuDNN:
CUDA 8.0 cuDNN 5.1
(please attach the output of ls -l /path/to/cuda/lib/libcud*):
ls -l /usr/local/cuda/lib64/libcud*
-rw-r--r-- 1 root root   560184 Mar  7 09:54 /usr/local/cuda/lib64/libcudadevrt.a
lrwxrwxrwx 1 root root       16 Mar  7 09:54 /usr/local/cuda/lib64/libcudart.so -> libcudart.so.8.0
lrwxrwxrwx 1 root root       19 Mar  7 09:54 /usr/local/cuda/lib64/libcudart.so.8.0 -> libcudart.so.8.0.27
-rwxr-xr-x 1 root root   394472 Mar  7 09:54 /usr/local/cuda/lib64/libcudart.so.8.0.27
-rw-r--r-- 1 root root   737516 Mar  7 09:54 /usr/local/cuda/lib64/libcudart_static.a
-rwxr-xr-x 1 root root 84163560 Mar  9 03:26 /usr/local/cuda/lib64/libcudnn.so
-rwxr-xr-x 1 root root 84163560 Mar  9 03:26 /usr/local/cuda/lib64/libcudnn.so.5
-rwxr-xr-x 1 root root 84163560 Mar  9 03:26 /usr/local/cuda/lib64/libcudnn.so.5.1.10
-rw-r--r-- 1 root root 70364814 Mar  9 03:26 /usr/local/cuda/lib64/libcudnn_static.a
If installed from binary pip package, provide:

A link to the pip package you installed:
https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-1.0.1-cp27-none-linux_x86_64.whl
The output from python -c "import tensorflow; print(tensorflow.__version__)".
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcublas.so.8.0 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcudnn.so.5 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcufft.so.8.0 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcurand.so.8.0 locally
1.0.1

If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
I followed this tutorial to launch the model:
python cifar10_train.py

Logs or other output that would be helpful
Traceback (most recent call last):
  File "cifar10_train.py", line 124, in <module>
    tf.app.run()
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 44, in run
    _sys.exit(main(_sys.argv[:1] + flags_passthrough))
  File "cifar10_train.py", line 120, in main
    train()
  File "cifar10_train.py", line 110, in train
    log_device_placement=FLAGS.log_device_placement)) as mon_sess:
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/monitored_session.py", line 315, in MonitoredTrainingSession
    return MonitoredSession(session_creator=session_creator, hooks=all_hooks)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/monitored_session.py", line 601, in __init__
    session_creator, hooks, should_recover=True)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/monitored_session.py", line 434, in __init__
    self._sess = _RecoverableSession(self._coordinated_creator)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/monitored_session.py", line 767, in __init__
    _WrappedSession.__init__(self, self._create_session())
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/monitored_session.py", line 772, in _create_session
    return self._sess_creator.create_session()
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/monitored_session.py", line 494, in create_session
    self.tf_sess = self._session_creator.create_session()
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/monitored_session.py", line 375, in create_session
    init_fn=self._scaffold.init_fn)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/session_manager.py", line 272, in prepare_session
    msg))
RuntimeError: Init operations did not make model ready for local_init.  Init op: group_deps, init fn: None, error: Variables not initialized: global_step, conv1/weights, conv1/biases, conv2/weights, conv2/biases, local3/weights, local3/biases, local4/weights, local4/biases, softmax_linear/weights, softmax_linear/biases, conv1/weight_loss/avg, conv2/weight_loss/avg, local3/weight_loss/avg, local4/weight_loss/avg, softmax_linear/weight_loss/avg, cross_entropy/avg, total_loss/avg, conv1/weights/ExponentialMovingAverage, conv1/biases/ExponentialMovingAverage, conv2/weights/ExponentialMovingAverage, conv2/biases/ExponentialMovingAverage, local3/weights/ExponentialMovingAverage, local3/biases/ExponentialMovingAverage, local4/weights/ExponentialMovingAverage, local4/biases/ExponentialMovingAverage, softmax_linear/weights/ExponentialMovingAverage, softmax_linear/biases/ExponentialMovingAverage

It looks like variables have not been initialized. Try adding this line right after you start the session
sess.run(tf.global_variables_initializer())

@Evan-Gao : Is it possible that you're not using the latest versions of the tutorial files (from https://github.com/tensorflow/models/tree/master/tutorials/image/cifar10)? Or perhaps there are some stale files in /tmp/cifar10_train (the default directory where the tutorial places it files).
I was unable to reproduce the error with release 1.0.1 and the latest contents of those files.
Could you try with a fresh snapshot (and after rm -rf /tmp/cifar10_train)?

@asimshankar I pull the latest version and everything is fine now. thx


File tab only becomes active if clicking over the file name

It should become active by clicking anyplace in the tab, other than the 'close' button.

Fixed by ef90027c4b3c576744fe83aab954f60bdb3c35db.


dgsh_tee cleanup issue

Executing pash with --dgsh_tee flag generates big files (0.5G-1.6G) on /tmp that are not removed after script completion.
The generated filename format is something like sg-g0FOvGgoyVkI.
Changing the width number affects the number of the generated files.

-w 8: 7 files
-w 4: 3 files
-w 2: 1 file

executing 1.sh from analytics-mts will trigger this 'bug'
$PASH_TOP/pa.sh  --dgsh_tee -w 2 1.sh
Commit: 6e149033484d00046869386538e6975176304873
Kernel: Linux livestar 4.9.0-14-amd64 #1 SMP Debian 4.9.246-2 (2020-12-17) x86_64 GNU/Linux
OS: Debian GNU/Linux 9 (stretch)
Machine: Livestar

CC @angelhof @tammam1998

(BTW congrats @dkarnikis, this is a great bug report, we should tag it and use it in the documentation as the model but report for newcomers)

Thanks for the report! Are the files removed when execution completes successfully? Or do they always stay there?
@tammam1998 do you know if there is a flag that ensures that dgsh-tee removes intermediate files?

Thanks for the report! Are the files removed when execution completes successfully? Or do they always stay there?

Yes!

Hi @dkarnikis @nvasilakis  @angelhof
I made a change to fix the problem in the dgsh fork we are using. Here is a direct link to the commit for quick reference.
I tested it briefly and it looked like the bug was fixed with no side effects. Let me know if the issue persists in other test cases/situations or if anything breaks.
P.S you need to delete the dgsh-tee binary and run make.

@angelhof I don't believe there is such flag. All flags are documented here

Thanks @tammam1998 ! If this is indeed a bug in dgst-tee then we need to contact the authors. I am also a little concerned because I see this comment in the file https://github.com/tammam1998/dgsh/blob/pash/core-tools/src/dgsh-tee.c#L280.
I think that it is OK for now to use your solution (if compiler/test_evaluation_scripts.sh --experimental passes), but I think that we need to contact the authors of dgst-tee using a PR, explaining this issue and the fix :)
Tammam, whenever you have time can you make a PR in the dgsh repo with your fix? You can point to this issue here to give them more context

@angelhof will do!

@tammam1998 I can verify that your fixes solve the issue. Thanks !


Update 2.230.0

Update 2.230.0

Codecov Report

Merging #1273 (7094909) into main (30d0b22) will decrease coverage by 71.47%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #1273       +/-   ##
==========================================
- Coverage   79.78%   8.32%   -71.47%
==========================================
  Files          47      28       -19
  Lines        8866     889     -7977
  Branches        0     114      +114
==========================================
- Hits         7074      74     -7000
+ Misses       1792     815      -977

Files Changed
Coverage Δ

scripts/cc-cli/src/api.ts
0.00% <ø> (ø)

scripts/cc-cli/src/commands/balance.ts
0.00% <ø> (ø)

scripts/cc-cli/src/commands/bond.ts
0.00% <ø> (ø)

scripts/cc-cli/src/commands/chill.ts
0.00% <ø> (ø)

scripts/cc-cli/src/commands/distributeRewards.ts
0.00% <ø> (ø)

scripts/cc-cli/src/commands/newSeed.ts
0.00% <ø> (ø)

scripts/cc-cli/src/commands/rotateKeys.ts
0.00% <ø> (ø)

scripts/cc-cli/src/commands/send.ts
0.00% <ø> (ø)

scripts/cc-cli/src/commands/setKeys.ts
0.00% <ø> (ø)

scripts/cc-cli/src/commands/showAddress.ts
0.00% <ø> (ø)

... and 18 more

... and 44 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[Dev] Clean up logfile for dev starts

Cleans up the log file introduced in https://github.com/opendatahub-io/odh-dashboard/pull/914
Every time we start our dev environment is a good time to clean up the logfile. If we don't, it grows indefinitely. I hit over 5mb recently... it likely will grow indefinitely as there is no cleanup mechanism.
This is by design for production, but for development it's unnecessary.

would you want the same cleaning to run on frontend as well. And even the root folder has some logs?

would you want the same cleaning to run on frontend as well. And even the root folder has some logs?

Logs are generated by the backend -- see the PR I mentioned in the description. https://github.com/opendatahub-io/odh-dashboard/pull/914/files#diff-489e4ec44d1b710d94129fd9004a2d41bbae615dbc8e9ea3e9b2c6513a3c0accR50
No sense in cleaning it from the frontend -- as it can't write to the file.


Create forest/domain with options don't work

Windows 2008
# Create Contoso.com forest with DNS, Win2008 R2 Operational Mode Windows Server 2008 R2
windows_ad_domain "contoso.com" do
  action :create
  type "forest"
  safe_mode_pass "Passw0rd"
  options ({ "domainlevel" => "4",
             "forestlevel" => "4",
             "InstallDNS" => "yes"
           })
end

The options aren't formatted correctly. In this case you wind up with "-forestlevel 4" on the shell command for dcpromo when it should be "-forestlevel:3".
I suspect this has something to do with the warning at the beginning of the run of
"ERROR: This version of Windows Server is currently unsupported beyond installing the required roles and features"

@geerzo Yep, just ran into this.
Sorta, we need to remove that message, we've been supporting Server 2008 for some time now, there are just some remaining bugs with integration.
Try this to work within the current framework:
windows_ad_domain "contoso.com" do
action :create
type "forest"
safe_mode_pass "Passw0rd"
options ({ "domainlevel" => "4",
"forestlevel" => "4",
"InstallDNS:yes" => nil
})
end


JWT Issued By External OAUTH Server is Not Accepted

Hello Daniel
I have a setup where Alfresco Content Repository is running in Docker and I have enabled following settings in docker compose file to allow for bearer JWT token to be method of authentication
-Dauthentication.chain=identity-service1:identity-service
-Didentity-service.register-node-at-startup=true
-Didentity-service.authentication.enabled=true
-Didentity-service.authentication.enable-username-password-authentication=false
-Didentity-service.bearer-only=true
-Didentity-service.realm-public-key=INTENTIONALLY BLANK
When attempting to reach admin console via above settings using Spring Cloud Gateway to generate token (all is ok).
When attempting to reach admin console via above settings, where token is issued by Authorisation Server (Apereo CAS), I get error saying Authorisation 'Bearer' not supported.  I do get that same error when I attempt REST API calls.
I have found it is the issuer (iss) in JWT token payload that is different in my case. If I update iss to http://localhost:8180/auth/realms/alfresco , all is ok.
I cannot locate any setting on repository side that is looking for this validation.
Any insights will be useful.
The version of Afresco Content Repository that I am using is 6.2.0-ga Community edition.
Thanks in advance.

hi, I am sorry but I cannot help you with that kind of issue. Please use the issues on this project only for questions and issues related to the project itself or ask on alfresco hub.


Shouldn't Int translate to an i32?

In the documentation it says, that an Int is an i32

Int: A signed 32‐bit integer.

but rust tells me, that an i64 is generated?
error[E0308]: mismatched types
  --> src/main.rs:30:22
   |
30 |             id: Some(id),
   |                      ^^ expected i64, found usize
help: you can convert an `usize` to `i64` and panic if the converted value wouldn't fit
   |
30 |             id: Some(id.try_into().unwrap()),
   |                      ^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
error: Could not compile `anilist_unofficial`.

To learn more, run the command again with --verbose.

Hmm good point, I don't remember the rationale. Maybe it's in the commit history. This should definitely be investigated, thanks for reporting it.

It seems that type Int = i64 has been there since the beginning (2024a4f486361cdb3c4399794e614dbd81e77746), so nothing in the commit history at least.
I also suspect that type ID = String; is wrong and that it should actually be struct ID(String); (deriving at least Eq I guess) since it is just serialized as a String, but is supposed to be distinct. I don't know how difficult that change would be.

@tomhoule Candidate for 1.0?

Definitely, thanks for the ping!

Is this issue open for contributions?

Sure, but it will need a release note to indicate the breaking change. Or changes if you also tackle the ID mismatch.

Looks like the problem is here: https://github.com/graphql-rust/graphql-parser/blob/8a759df14ff6a2d97b55bcbccad0a53ce0bee4a6/src/common.rs#L46. This needs to be fixed upstream.

Thanks. I've filed an issue: graphql-rust/graphql-parser#53


How to use pretraining weights for training?

How to use pretraining weights for training? After downloading the pretraining weight, which folder should I put it in? How to call the pretraining weight file?
Thanks！

Here is an example to use pre-trained weights.

OK, I just need to change the weight address of the config file. I haven't used cvpods library. It's not very clear. Thank you very much for your answer!
------------------ 原始邮件 ------------------
发件人:                                                                                "megvii-model/YOLOF"                                                                                @.>;
发送时间: 2021年5月12日(星期三) 下午3:35
@.>;
抄送: "Hide on<EMAIL_ADDRESS>主题: Re: [megvii-model/YOLOF] How to use pretraining weights for training?  (#27)
Here is an example to use pre-trained weights.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Question: Incorrect condition for cis_1.3..3

Question
tasks/section_1/cis_1.3.x.yml
at task:

name: "1.3.3 | Ensure cryptographic mechanisms are used to protect the integrity of audit tools"

has a condition "when"
when:
- rhel9cis_rule_1_3_2
Should it not be:
when:
- rhel9cis_rule_1_3_3
Environment (please complete the following information):

Ansible Version: 2.14.2
Host Python Version: Python 3.11.2
Ansible Server Python Version: Python 3.11.2

hi @p3ll1n0r3
Thank you for taking ths time to raise this issue, this is now in devel
https://github.com/ansible-lockdown/RHEL9-CIS/pull/151
We will be cutting a new release to main in the coming weeks.
many thanks
uk-bolly


[Feature Suggestion] Consider supporting new preferences window layout since macOS 13?

The layout has these features:

[Optional] Index-search box.
A navigation sidebar but is not foldable by dragging the splitter. (i.e. the splitter is not draggable).
Fixed overall window (view) width.
A toolbar showing the title of the current page.
Each preference section now have its visible round-shaped borders.
Section title can have descriptions.

This layout with a sidebar is only for the built-in Settings app. It's not meant to be used by third-party apps.

Each preference section now have its visible round-shaped borders.

This is just .formStyle() which you can set yourself in SwiftUI.

@sindresorhus Thanks for mentioning that.
Do you have any idea how to make the navigation pane not-hidable? i.e. making the splitter "not draggable".

It's not currently possible. I would have wanted that in an app of mine too.


owner(ticdc): do not stop backoff when encountering an error

What problem does this PR solve?

Issue Number: ref #5647
What is changed and how it works?
Do not stop backoff and switch the changefeed to a failed state. This PR cherry-pick some code from #6020
Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
No
Do you need to update user documentation, design documentation or monitoring documentation?
No
Release note
None

/run-all-tests


Asset import/export functionality, role and cross-filter are still ID-based, not uuid-based.

I have two Superset, one for the testing environment where I have two datasets (indicator-monthly [id:1] and indicator-daily [id:2]).
I do an asset export from the testing Superset and import on the second environment. But it seems that the id of my datasets has changed to indicator-daily [id:1] and indicator-monthly with [id:2]
If I do an export and import in the first environment, the identifier doesn't change.
I don't know the process but it seems that some content are based on uuid but not this one.
How to reproduce the bug

Create the dataset indicator-monthly and then the dataset indicator-daily on the first instance of Superset
Then export it with the api /api/v1/assets/export
Import the previous dataset on the new Superset with the api /api/v1/assets/import
Finally, go to Settings > List roles > edit a role > check permission with datasource access

Expected results
what you expected to happen.

Actual results
what actually happens.

Environment
(please complete the following information):

installation type: helm chart 0.6.5
browser type and version: Brave Version 1.52.130 Chromium: 114.0.5735.198 (Build officiel)  (64 bits)
superset version: 2.1.0
python version: 3.8.16
any feature flags active:

    dashboard_feature: |
     FEATURE_FLAGS = {
       "EMBEDDED_SUPERSET": True,
       "ENABLE_TEMPLATE_PROCESSING": True,
       "DRILL_TO_DETAIL": True,
       "HORIZONTAL_FILTER_BAR": True,
       "DASHBOARD_CROSS_FILTERS": True
     }

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Hi there... sorry this hasn't seen much activity. Can you confirm if this is still an issue in Superset 3.x?

I believe this relates to the UUID SIP here: https://github.com/apache/superset/issues/27194
Really, we should be using UUIDs everywhere. Closing this since it's not being perceived as a bug, but any contribution toward this improvement is more than welcome!


signer/authenticator

Add an authenticator service that allows enrollers to add members and members to get and verify signed credentials.

@Mergifyio refresh

Github seems to not want to run checks on this PR 🧐

Seems they are having a downtime https://www.githubstatus.com

@twittner do we have the API spec for this component?
Also from the code it seems like verification is done by the authority, and we need to move it out because we might not have access to the authority when verifying a credential.

@twittner do we have the API spec for this component?

schema.cddl contains the relevant parts. As for the credential itself, see https://github.com/build-trust/codebase/issues/375.

Also from the code it seems like verification is done by the authority, and we need to move it out because we might not have access to the authority when verifying a credential.

Every node can start its own authenticator and signer service locally. Access to a remote authority is not required. As I mentioned above I can make the verification part accessible via reference to identity and authenticated storage, but this is an implementation detail.

schema.cddl contains the relevant parts. As for the credential itself, see https://github.com/build-trust/codebase/issues/375.

Can we also have an API doc in addition to the schema?

Every node can start its own authenticator and signer service locally. Access to a remote authority is not required. As I mentioned https://github.com/build-trust/ockam/pull/2965#discussion_r942206527 I can make the verification part accessible via reference to identity and authenticated storage, but this is an implementation detail.

My point is we don't need a signer to verify credentials. My understanding is that signer has some storage, it's using authenticated identities table, it has a private key etc. None of this is needed for a verifier component.

My understanding is that signer has some storage, it's using authenticated identities table, it has a private key etc. None of this is needed for a verifier component.

As I already stated above, I can provide a verification function that is accessible via references to identity and storage, but it is not true that storage is not needed for the verification. Signatures contain the identity ID of the authority and storage is used to load the corresponding public key (which must have been added previously).
The current implementation more or less reflects https://github.com/build-trust/codebase/issues/296 and I am fully aware that this is not the end of the story.

Can we just provide the identity of authority in the verify request instead of adding it to the state and then referring to that?
Also I don't see verify API in the schema definition.

Can we just provide the identity of authority in the verify request instead of adding it to the state and then referring to that?

In case we want to support multiple signatures at some point it would become problematic as we would not know which identity to use for which signature. It would also be highly redundant to include it in every credential exchange between members. And finally we would still need to compare the provided identity with the one we are supposed to use (presumably stored locally), as otherwise the sender could present us a signature from an arbitrary authority.

Also I don't see verify API in the schema definition.

To verify, the credential is sent as request body.

In case we want to support multiple signatures at some point it would become problematic as we would not know which identity to use for which signature.

It's a valid argument, but we can always provide a list of accepted identities.

It would also be highly redundant to include it in every credential exchange between members.

Members have control over which authorities they accept the signatures from, so it's not a part of credential exchange in any case.

And finally we would still need to compare the provided identity with the one we are supposed to use

We already do that, no? That wouldn't change regardless of where you get the identity from.
My main concern is that member and verifier are different components and I would prefer if member component had control over which authorities it accepts credentials from. If we have that in the verifier component, then member would not be able to control that, other than adding new ones.
If we go the way when verifier stores authority identities then we need to give more control to the member to chose which ones it wants to verify. Such as not having the "own" identity for the verifier and allowing member to remove identities. In other words not allowing the verifier to verify anything other than what member explicitly tells it to verify.
Still I would prefer if that was per-call basis and without a storage on the verifier side.

Also verifier defninitely needs to be separate from the signer.

It makes sense that verifier can and should be separate. Also I think that at this point we can define different types of rust components, to further clarify what functionality should be available where. The types are:

Rust native code
FFI
Rust-served services living in a sidecar
Rust-served services exposed to nodes living outside of the internal network

Thoughts?

In case we want to support multiple signatures at some point it would become problematic as we would not know which identity to use for which signature.

It's a valid argument, but we can always provide a list of accepted identities.

What I meant was that signature verification would require us to try all combinations of signatures and public keys since we do not know which key to use.

It would also be highly redundant to include it in every credential exchange between members.

Members have control over which authorities they accept the signatures from, so it's not a part of credential exchange in any case.

Maybe we are talking past each other, but I understood your comment

Can we just provide the identity of authority in the verify request instead of adding it to the state and then referring to that?

to mean that the verification in signer::Server should accept the identity and this part was intended to be used on client-side for member credential verification as well.

And finally we would still need to compare the provided identity with the one we are supposed to use

We already do that, no? That wouldn't change regardless of where you get the identity from.

The current protocol works like this:
The credential contains the identity ID of the signer. The party that receives the credential loads the corresponding public key from storage where it had been added previously when the enroller provided the authority's identity to the member. If the key is not found signature validation fails.
If the public key is provided in the call to verify, would we not still need to consult local storage to see if we have that key?
The protocol was specified here: https://github.com/build-trust/codebase/issues/324

If the public key is provided in the call to verify, would we not still need to consult local storage to see if we have that key?

What I mean is that we still make a check that the signature key id is in the "accepted keys" and we have a check for that. Difference would only be that "accepted keys" may be controlled by the member via arguments somehow.

Also I think that at this point we can define different types of rust components, to further clarify what functionality should be available where.

Yes. We're currently running 3 and  4 in sidecars, but ideally would like to run them in different sidecars so maybe we can call them differently.
FFI (2) only exposes vault functions and only used in encrryption secure channel from Elixir perspective.
I'd like to run verifier component in the sidecar (3) for easier access and also because it's more simple RPC component
I'd like to run the signer (authority) component in more "proper" node, exposed via secure channel listener (4), while still running like a sidecar from k8s point of view.
This node secure channel needs to be authorizing enrollers and members.

My thoughts are:

2 should be replaced with 3 in the future
3 should avoid having persistent state. The only exception to this rule is Vault storage. Everything else should be stored on the caller side
3 should be managed by rust NodeManager and be started by ockam services [SERVICE_NAME] start. This way we at least will know what is the exect list of those services and what are their dependencies. After that we can review individual case
4 should be avoided in general. Every exception should be reviewed carefully in sense of why we can't have such service on elixir side

fwiw,  yesterday' evening tried to integrate with the Authority on rust,   but failed.   Looked at the credential'  issue/retrieval api  @twittner  implemented,   and just implemented that same thing as an Authority on elixir.. to have something to test.
I can show on today's meeting,  but yes the things about having admin creating projects, setting enrollers,  enrollers adding members, member retrieving credentials it's all working.   What to do with that credential once retrieved is a different story :shrug:


[Bug] BetterDiscord instability & crashes when viewing certain text formats

Describe the Bug
Certain text formats (such as the box embeds bots can post) will crash BD. Given Discord opens to those channels after a reload, this crash is permanent until Discord is either fully closed down, or BD is reinstalled; opening the friends list by default. Since the fix for the latest Discord update, this version of BD is rather unstable in general (lots of plugin errors as well)
To Reproduce
Attempt to view a channel containing the bot embed box (such as the #github-log channel in the BD Discord) or similar formatting options.
Expected Behavior
Channel loads and displays as normal
Screenshots

Discord Version
Stable
Additional Context

Does the crashing occur without any plugins installed? Plugins often need to make their own changes separate from BD when Discord updates.

Does the crashing occur without any plugins installed? Plugins often need to make their own changes separate from BD when Discord updates.

it worked without any plugins, I am testing each plugin to find out which plugin cause the crash

This crash just occured for me as well
Here's what the console prints out:
Prettified stacktraces, stack:
 Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined.
Component stack:
     at span
    at betterdiscord://plugins/0PluginLibrary.plugin.js:1650:73
    at span
    at h2
    at https://discord.com/assets/fb1f1576ed1d453163fe.js:1059:319
    at div
    at div
    at t.default (https://discord.com/assets/288bc8ed74323c900218.js:1953:172)
    at li
    at t.default (https://discord.com/assets/288bc8ed74323c900218.js:1953:172)
    at betterdiscord://plugins/0PluginLibrary.plugin.js:1650:73
    at ol
    at div
    at p (https://discord.com/assets/288bc8ed74323c900218.js:1962:545)
    at div
    at https://discord.com/assets/fb1f1576ed1d453163fe.js:1514:872
    at div
    at E (https://discord.com/assets/288bc8ed74323c900218.js:3550:180)
    at H (https://discord.com/assets/fb1f1576ed1d453163fe.js:1011:489)
    at https://discord.com/assets/fb1f1576ed1d453163fe.js:1014:611
    at main
    at Te (https://discord.com/assets/40013fde4987fc0228da.js:74:819)
    at https://discord.com/assets/fb1f1576ed1d453163fe.js:1524:878
    at t (https://discord.com/assets/288bc8ed74323c900218.js:3202:414)
    at ChatLayerProvider
    at t (https://discord.com/assets/f89a1b32de3f9305fc8f.js:23:104)
    at t (https://discord.com/assets/40013fde4987fc0228da.js:82:452)
    at https://discord.com/assets/40013fde4987fc0228da.js:87:623
    at div
    at div
    at t (https://discord.com/assets/40013fde4987fc0228da.js:53:923)
    at e (https://discord.com/assets/2e45b6b321248222f12a.js:44:760)
    at https://discord.com/assets/f89a1b32de3f9305fc8f.js:57:342
    at https://discord.com/assets/40013fde4987fc0228da.js:67:386
    at re (https://discord.com/assets/40013fde4987fc0228da.js:35:591)
    at t (https://discord.com/assets/288bc8ed74323c900218.js:5505:926)
    at c (https://discord.com/assets/288bc8ed74323c900218.js:1806:291)
    at t (https://discord.com/assets/288bc8ed74323c900218.js:5508:10)
    at div
    at div
    at div
    at Me (https://discord.com/assets/40013fde4987fc0228da.js:39:31)
    at div
    at l (https://discord.com/assets/288bc8ed74323c900218.js:4116:605)
    at t (https://discord.com/assets/40013fde4987fc0228da.js:135:344)
    at div
    at t (https://discord.com/assets/288bc8ed74323c900218.js:4025:281)
    at t (https://discord.com/assets/40013fde4987fc0228da.js:137:946)
    at K (https://discord.com/assets/40013fde4987fc0228da.js:139:509)
    at div
    at t (https://discord.com/assets/5c091cbf84346774e26c.js:5:674)
    at k (https://discord.com/assets/40013fde4987fc0228da.js:116:188)
    at t (https://discord.com/assets/288bc8ed74323c900218.js:5505:926)
    at t (https://discord.com/assets/288bc8ed74323c900218.js:5508:10)
    at t (https://discord.com/assets/40013fde4987fc0228da.js:214:85)
    at u (https://discord.com/assets/288bc8ed74323c900218.js:3710:833)
    at Suspense
    at d
    at t (https://discord.com/assets/288bc8ed74323c900218.js:5505:926)
    at t (https://discord.com/assets/288bc8ed74323c900218.js:5508:10)
    at div
    at y (https://discord.com/assets/288bc8ed74323c900218.js:3235:435)
    at t (https://discord.com/assets/288bc8ed74323c900218.js:3202:414)
    at VerificationLayerProvider
    at t (https://discord.com/assets/288bc8ed74323c900218.js:3202:414)
    at AppLayerProvider
    at p (https://discord.com/assets/288bc8ed74323c900218.js:1962:545)
    at t (https://discord.com/assets/288bc8ed74323c900218.js:705:521)
    at T (https://discord.com/assets/288bc8ed74323c900218.js:707:975)
    at t (https://discord.com/assets/288bc8ed74323c900218.js:708:442)
    at u (https://discord.com/assets/288bc8ed74323c900218.js:3710:833)
    at h (https://discord.com/assets/288bc8ed74323c900218.js:692:9)
    at te (https://discord.com/assets/288bc8ed74323c900218.js:695:605)
    at t (https://discord.com/assets/288bc8ed74323c900218.js:751:24)
    at u (https://discord.com/assets/288bc8ed74323c900218.js:3709:772)
    at https://discord.com/assets/288bc8ed74323c900218.js:4180:30
    at H (https://discord.com/assets/288bc8ed74323c900218.js:5319:700)
    at t (https://discord.com/assets/288bc8ed74323c900218.js:5502:570)
    at t (https://discord.com/assets/288bc8ed74323c900218.js:5458:817)
    at f (https://discord.com/assets/288bc8ed74323c900218.js:2227:987)

It looks like there's some problem with ZeresPluginLibrary

I'm getting this issue and from the process of elimination, it looks like "BetterBotTags.plugin.js" is causing a crash when viewing a channel with lots of bot posts.
Got this in console

delete BetterBotTags.plugin.js and BD worked well

I'm getting this issue and from the process of elimination, it looks like "BetterBotTags.plugin.js" is causing a crash when viewing a channel with lots of bot posts.
Got this in console

delete BetterBotTags.plugin.js and BD worked well

Can confirm by removing BetterBotTags, BD works fully as intended so far.


I can't login anymore

Same, it also kicked me out of the room i was talking

Happened to me as well, it seems like api.dogehouse.tv is down

App is down. Got kicked out of the room i was in and can't sign back in. Only the login screen seems to load. Related: #89

I also got kicked out and now i cant login anymore

same, Image for reference:

related: https://github.com/benawad/dogehouse/issues/90

it was such a nice talk 🙈

Do you have Discord? If yes, here is my Discord: SturmEnte#4367  Gesendet von Mail für Windows 10 Von: ChrisGesendet: Samstag, 13. Februar 2021 01:09An: benawad/dogehouseCc: SturmEnte; CommentBetreff: Re: [benawad/dogehouse] I can't login anymore (#88) it was such a nice talk 🙈—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.

We back
https://dogehouse.tv/room/06c53a8a-1af0-497a-846b-3ee1eb3586be


Service Worker Scope

if ('serviceWorker' in navigator) {
  navigator.serviceWorker.register('/sw-test/sw.js', { scope: '/sw-test/' }).then(function(reg) {
    // registration worked
    console.log('Registration succeeded. Scope is ' + reg.scope);
  }).catch(function(error) {
    // registration failed
    console.log('Registration failed with ' + error);
  });
};

We know the scope depends on the sw.js file's location, if the path of sw.js is '/sw-test/sw.js', then, the scope should be '/sw-test/'.    So why do we need to define a scope attribute seperately?
I found the the scope can't be the parent directory of the SW path.

I found my answer on

I found my answer on #595


Div mod cleanup

We may want to consider alignment always being expressed as a power of 2, which could avoid some of the checking that is necessary (e.g. 12 instead of 4096). This could be done at a later time and cleanup however. This will be closed, but merged as part of the rebased PR #95.


Process account funds using hex encoded BigInts

Code to fix wallet fund transfers. See issue #84
Hex encoding allows for transfers to be accepted and converting the underlying value datatype from Long to BigInteger allows for any amount (large amounts) of an account balance to be transferred in one transaction.

These changes were included in yourcodesucks's quorum-ui branch, which has been merged. #95


More robust shell scripts for building

[x] Contingency if (when) GitHub is down

NTS: spin out plugin build.sh to design patterns.

Done. There's a check for README.md, which won't exist if GH is down, so closing.


include JSON processor tool (like jq)

it would be handy to have a JSON processor in this image, I would vote for jq
I am happy to raise a PR if that's acceptable.

Can you please test cloudbees/java-build-tools:latest?
See https://github.com/cloudbees/java-build-tools-dockerfile/commit/593c533d274d5b31c8bf32b3314085b6af0c02f8

working fine. thanks!

You're welcome @cs-mahmoud-khateeb


don't validate params on delete, or a failed create won't be deleted

Thanks, I overlooked that. Will merge when I'm back


use explicit fstype in storageclass example

When using newer CSI components, no default fstype is set for PVs.
This leads to kubelet skipping the fsGroup step since it expects
the volume to be in block mode.
See https://github.com/piraeusdatastore/linstor-csi/issues/91

LGTM. we might have some examples in linbit-documentation that we should update as well.


Current ReadMe out of date (12/24/14)

https://github.com/ravenac95/sudolikeaboss/blob/master/README.rst
The readme says to install 0.1 (if by source) but the workaround didn't work until I uninstalled and re-installed via homebrew and noticed 0.2 was installed instead.

Sorry for the delay. I was actually out of commission for a while. I resolved the issue


update CRD

Describe what this PR does and why we need it:
Update CRD to include excludedServices field
Which issue this PR fixes (This will close that issue when PR gets merged)
fixes AEROGEAR-2151

verified locally

Merging with failed build as failure is due to a technical issue in the cluster being tested upon.


PUBLIC TESTNET: initialize compass on fee manager after compass 2.0.0 vote

Once the vote to deploy compass passes, you will need to call the fee manager MANUALLY and call the initialize_compass() function on it. I can show you once we get to that stage.
fee manager addresses:
https://docs.palomachain.com/guide/resources/networks.html#testnet
Compass proposal - vote 30

@taariq The initialize_compass function call must come from the address that deployed the contract. It was deployed from this address. Is this a Volume wallet? How can I use it?

@maharifu I asked Vera for a response on this question.

@taariq The initialize_compass function call must come from the address that deployed the contract. It was deployed from this address. Is this a Volume wallet? How can I use it?

@webelf101 from Vera;

this is Steven's account. He deployed the fee manager contract

Will you run the call please?

What are the compass addresses on Eth and Arb for public testnet? @taariq @maharifu

What are the compass addresses on Eth and Arb for public testnet? @taariq @maharifu

@webelf101 They are here: https://docs.palomachain.com/guide/resources/networks.html#testnet

Compass is now redeployed on the testnet. The new addresses are:
ETH: 0x061A44249c2050adcdEB8Ab09213b3E6510Cd43F
ARB: 0xC859BCf62DC2571e693422277cdb3453f84c14bf
And FeeManager addresses:
ETH: 0xf62d5ab8bb6378238c3e67e468809081ad8b77dd
ARB: 0xdc503ab31f8295cf87b09e151bf1f8fb6824d118

I initialized the fee manager contracts. @maharifu


Unsupported argument "hosted_zone_name" for module "bastion"

I am getting an odd issue where my terraform plan step is now failing due to the unsupported argument "hosted_zone_name" in the "bastion" module. The below plan previously worked. It seems that "hosted_zone_name" has been replaced with "hosted_zone_id". However, I have not found any documentation indicating this change. Moreover, the terraform registry page for this repo shows that "hosted_zone_name" is still a valid input. It seems like this repo though no longer lists "hosted_zone_name" as a variable. Is there answer that the "hosted_zone_name" variable should now be "hosted_zone_id"? Thank you!
Code:
module "bastion" {
  source = "git::https://github.com/Guimove/terraform-aws-bastion.git?ref=master"
  bucket_name = module.bastion_logs_s3.bucket_id
  region = var.region
  vpc_id = module.vpc.vpc_id
  is_lb_private = "false"
  bastion_host_key_pair = var.stage
  hosted_zone_name = var.hosted_zone_id
  bastion_record_name = local.bastion_hostname
  elb_subnets = module.subnets.public_subnet_ids
  auto_scaling_group_subnets = module.subnets.public_subnet_ids
  create_dns_record = "true"
  tags = var.tags
}

Error:

You are correct that the new variable name is hosted_zone_id, which is more accurate, but still has a poor description. The change happened in https://github.com/Guimove/terraform-aws-bastion/pull/65/commits/7f3e6c27426ed645df2b8c896f5eaf3d0c05b423, which was included in tag 1.20.1.
For people suprised by this new behavior, you can either pin yourself to an older version
source = "Guimove/bastion/aws"
version = "1.2.0"
hosted_zone_name = ...

or bump the required version and rename the variable
source = "Guimove/bastion/aws"
version = "~> 1.2.1"
hosted_zone_id = ...

@Guimove if at all possible when you're releasing breaking changes like this in the future, can you bump the major version? That way users like ourselves can benefit from non-breaking changes but hold off on any that will require revisions in our code.
(Thanks for putting together this module, it is very handy!)

Hello,
Sorry, I've created a new 2.0.0 version for all these new major changes.


The Shift+Alt+R Opens Terminal Menu Always

Issue Type: Bug
The Shift+Alt+R open the terminal menu instead of the show in explorer option all the time. Please fix it as soon as possible
VS Code version: Code 1.44.2 (ff915844119ce9485abfe8aa9076ec76b5300ddd, 2020-04-16T16:36:23.138Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz (4 x 2394)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.42GB (2.69GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (15)

Extension
Author (truncated)
Version

code-gnu-global
aus
0.2.2

bracket-pair-colorizer-2
Coe
0.0.29

githistory
don
0.6.5

vsc-material-theme
Equ
32.6.0

vsc-material-theme-icons
equ
1.1.4

cpptools
ms-
0.27.1

material-icon-theme
PKi
4.1.0

java
red
0.61.0

LiveServer
rit
5.6.1

vscodeintellicode
Vis
1.2.6

vscode-java-debug
vsc
0.25.1

vscode-java-dependency
vsc
0.9.0

vscode-java-pack
vsc
0.9.0

vscode-java-test
vsc
0.22.3

vscode-maven
vsc
0.21.2

(1 theme extensions excluded)

Default binding for shift+alt+r:

@sbatten maybe related to alt to open menu?

This is working properly for me. @Abir-Tx, where is focus when you run the command. It cannot be in the editor, otherwise the Run menu should be opened.

This is working properly for me. @Abir-Tx, where is focus when you run the command. It cannot be in the editor, otherwise the Run menu should be opened.

Not working for me on my two computers. The focus is on opened file in VS Code but still pressing Shift+Alt+R doesn't work as expected.

After pressing Shift+Alt+R -

I can repro in a multi-root workspace.

I cannot reproduce on Windows, here is what I do:

open a multi-root workspace
click on a file in one folder
hit Shift+Alt+R

The file is revealed.

@bpasero that's my repro:

It should work if you modify the keybinding to work even when the editor is not focused:

{
    "key": "shift+alt+r",
    "command": "revealFileInOS"
}

@bpasero wouldn't that open the explorer's focused item, not the active editor file?

It should work fine. We have code that returns the correct resource depending on focus.

@bpasero oh, how come it's !editorFocus by default then?

🤷

Yeah after modifying the keybinding it is working now.
Thanks :-)

It should work if you modify the keybinding to work even when the editor is not focused:

See also https://github.com/microsoft/vscode/issues/92893#issuecomment-600418796
Does the default keybinding deserve to be changed?


Use pyproject.toml instead of setup.py

Hi! What about to use pyproject.toml?

There where issues with which tools would read configs from setup.cfg, pyproject.toml or own config file. Also the authors name has UTF-8 characters, which cased issues.
I will have to revisit this


fix(migrateDev): prompt to reset schemas, not database, on pg

closes https://github.com/prisma/prisma/issues/10043

About the PR:

It's suspicious that not test failed, it probably means that this part is not tested, and it would be good to have this covered
The new message We need to reset the schema(s). will show for all users using PostgreSQL, it's not optimal 🤔

Might be confusing for users that do not use schemas explicitly
It would be better for confidence in what would be reset for users:

if we can tell if only 1 or multiple schemas
and their names for transparency

In general:
We should probably do something uniform over all the places too

migrate dev, the current PR
printDatasource.ts is used to print the following in the CLI
Datasource "my_db": PostgreSQL database "tests-migrate", schema "public" at "localhost:5432"
db push

if --force-reset is passed:

console.info(
      `The ${dbInfo.dbType} ${dbInfo.schemaWord} "${dbInfo.dbName}" from "${dbInfo.dbLocation}" was successfully reset.`,
    )

If a reset is necessary, we promt

`To apply this change we need to reset the database, do you want to continue? ${chalk.red(
      'All data will be lost',
    )}.`,

and logconsole.info(
      `The ${dbInfo.dbType} ${dbInfo.schemaWord} "${dbInfo.dbName}" from "${dbInfo.dbLocation}" was successfully reset.`,
    )

ensureDatabaseExists.ts

if the database does not exist, we create it and log

`${databaseProvider} ${schemaWord} ${chalk.bold(dbName)} created at ${chalk.bold(
      getDbLocation(credentials),
    )}`

Note: getConfig has schemas since https://github.com/prisma/prisma/pull/17052
From https://github.com/prisma/prisma-engines/pull/3550


Telemetry opt out notification has wrong text (says opt in)

RC1

Clear/delete settings (%APPDATA%/azuredatastudio)
Start up RC1
This notification prompt is shown

But that's incorrect - it should be saying "Opt Out" since telemetry is currently enabled.
This appears to be a regression from 1.47.1

@kisantia FYI, this is probably worth looking at so users aren't confused (assuming we aren't collecting telemetry when we actually are)

Nevermind, forgot that RC1 has telemetry disabled in product.json by default. I'm going to go change that since there isn't a reason we should have that disabled...

ohhh is that why I wasn't seeing "Telemetry" as an option in the Tasks pane in the RC build, but see it in Stable? I was about to ask you about that

yup meant output pane and yes I had set the log level to Trace


Use pip build occur ModuleNotFoundError: No module named 'mmdet'

When running pip install -v -e .,  will occur ModuleNotFoundError: No module named 'mmdet'.
The mistake in setup.py causes this error (this error doesn't cause the program exits.), I will make a pull request to fix this.

Thanks for your help.


fix wrong url in WMS GetCapabilities

 GetCapabilities hat falsche Url

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

28 of 33 (84.85%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.003%) to 85.331%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

services/src/handlers/wms.rs
28
33
84.85%

Totals

Change from base Build<PHONE_NUMBER>:
-0.003%

Covered Lines:
27468

Relevant Lines:
32190

💛  - Coveralls

bors merge


[Suggestion] add bookshelf feature to classify books/stories

I have categories for different purposes:

Component: display a UI element for reusability
Scene: display a whole UI page for a scene
App: display the whole app with full functionalities just like react-native start
and more... for testing specific functionalities with UI

My current stories are like this:

* [API] REST API
* [Scene] AdDialog
* [Comp] BannerButton
* [Comp] BannerView

I want to make stories to be classified in categories
* API
    * REST API
* App
    * new start
    * logged-in user
* Components
    * BannerButton
    * BannerView
    * ...
* Scenes
    * AdDialog
    * ....

using the following code
// original story: accept a string for the story name
storiesOf('[Scene] AdDialog', module)

// with category: accept an array for the category and story names
storiesOf(['Scene', 'AdDialog'], module)

Hi @xareelee -- you can use the new Story Heirarchy feature to achieve this I think? https://medium.com/storybookjs/announcing-storybook-3-2-e00918a1764c
Try storiesOf('Scene / AdDialog', module) etc

Thanks for the info. I did not notice this new feature. It works after upgrading to 3.2.


Removed unecessary line

Try to resolve issue #35.

These are critical breaking changes.
Please accept the PR ASAP

This also fixes #37
Please merge ASAP. Thank you.

Fixed in upstream, sorry guys


ok button target fix

Issue #9079

@anthonydresser was this fix fine for release/1.16?  I didn't see where the discussion landed for this fix?

as a release targeted fix, i dont have any issues with this.

/merge

The label Approved is required for using this command.

/merge

Merging PR based on approval from @kburtram


RFE: Showing issues' related github commits

I was wondering whether you'd be willing to include support for retrieving github commits that are related to a JIRA Issue.
Connecting JIRA to github is outlined here but unfortunately the REST API to retrieve commit details is private/undocumented -- but nevertheless works fine.
As far as I can see this would require introduction of a 'static' schema -- would that be acceptable?
Ideally, listing tickets would allow optional inclusion of commits, merge status, peer review...
I'd happily try to work on it and create a PR but wanted to hear your general thoughts on this first.
btw, thanks a lot for go-jira. It already rocks :)

Hey Jan, sorry I didnt have time to reply to this when I saw it, then I forgot to reply after.
I am generally okay adding features for undocumented apis, as long as they works.  I would want to make sure it works with the atlassian.net hosted jira service, which is what my regression tests work against.  I am not sure how we would test that, but in theory we could set up issues/PRs on a test branch tor this project to test it out.
The code is very messy and uses many bad practices (like casting interface{} all over).  I need to fix that, but am short on time.  I am concerned about keeping the command line interface simple, so we might need to discuss any changes to the CLI usage.  If you want to work towards a PR that would be great, I will unlikely have time to deal with this feature myself.
Thanks!
-Cory

Hi Cory,
thanks for your response and sorry for my late reply now.
I've made a first attempt to tweak code to make it work as outlined. We're using atlassian.net hosted jira service, so this shouldn't be a problem. Just to explain my goal: In the end, I'd like to produce changelog messages in MarkDown format -- that link to our JIRA issue and corresponding github PRs.
My (relatively small...) tweaks are referenced above.
I believe it's not really ready for a PR yet... please let me know how to improve... or just cherry-pick whatever looks usable to you. I must admit I have no clue how to make the github-integration
optional, so that the 2nd request only happens if people effectively use the JIRA github integration (prefs? cli-option?).
Having the changes applied, output currently looks like this:
...existing defaultViewTemplate stuff... then, new at bottom:

 PullRequest: id=#3048, status=MERGED, lastUpdate=2017-05-15T12:42:26.000+0200
 PullRequest: id=#3056, status=MERGED, lastUpdate=2017-05-12T11:43:30.000+0200

changelog:
[Story] [SPR-1537](https://myendpoint.atlassian.net/browse/SPR-1537) Implement logic to foobar  #3048 #3056

Please let me know how to proceed. Cheers!

Hey, sorry again, you have good timing as your last comment got to me as I was leaving the country for a 3 week vacation, then lost track :)  Anyway, the changes look interesting but agree we need to figure out a strategy to make them optional.  I wonder if there is some information in the issue metadata that indicates that github integration is enabled.
If you run jira view <ISSUE> -t debug that will print the full json output for what is available to the view template.  I wonder if there is any field in there that indicates there is some relation to github.

I have completely rewritten gojira, so it might be easier for you to hack on now if you want to send the PR my way.  I dont have a source of JIRA-Github integrations to work with so I cant provide much assistance on this one.


Live Demo / Documentation Down

Is this still active? Any chance you could restart the demo server?

@KarmicJohn Yes it is still active! However, the newer version of this starter template is located here - https://github.com/MileanCo/angular-meteor-es6-dashboard-seed/  It uses the latest ES6 and Meteor version.
The code is this repository uses Meteor <1.4 and ES5. As such, some of Meteor code is deprecated. Better to use the newer version above.

Either way, I've fixed the live demo! It's back online.
Thanks for the heads up.


Use the BasePackage from Asterism instead of a custom model

Is your feature request related to a problem? Please describe.
The Bag model serializer is causing invalid JSON to be created because of incorrect names in the Bag model. This would likely be mitigated if the BasePackage from Asterism was used instead of a custom model.
Describe the solution you'd like
Use the BasePackage from Asterism as the basis of the Bag model.

@helrond One minor issue I'm running into with this is that we're not currently using the "Process Status" field in Zorya; should I create some and update this field in each service, or try another approach?

@bonniegee If you're getting an error, you could try setting PROCESS_STATUS_CHOICES to an empty tuple and see if that works?

Noting here that we should be updating the services to update the process status field.


Extend bootstrap waiting loops 105->115

1050 seconds appears to be a little too close in Wi-SUN case. Test fails a bit too often. Propose increasing waiting period to 1150.

Looks like the third test(3/3) failed.
17:18:18 14:18:18.198 | TC     Dummy-1: Waiting for connection 105/105
17:18:18 14:18:18.198 | TC     Dummy-1: Waiting for 10 seconds

Looks like it didn't test with the new loop count.


Display Ingredients

App currently does not display ingredients for the chosen recipe. Find a way to store that information as an attribute in a button so that we are able to extract the data once the user clicks the recipeBtn.
It is finished when the user clicks the recipe button and the ingredients needed are listed in the display.

Implemented ingredients display. User can now click the recipe Button and ingredients needed are listed on the display.


URLs are not correctly escaped for file names with spaces.

When direct access is turned on, this adapter does not escape file names when generating the URL. As a result, it is possible for the server to return invalid URLs for files with characters in the name, such as spaces, that should be escaped. As a result, some Parse clients, such as the iOS client, are unable to download files whose names have spaces in them.
To reproduce, create a file with a space in the name and attempt to access it via the iOS client.

Having the same problem :(