[Browser Tabs] Optimize function

Description

Reverse the order of the tabs and the most recently opened tab will be at the top.
Add a new action to disable/enable browser.
Add a new action to open tab in other browsers.

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi!
Thank you for your contribution! My name is Milena and I will be reviewing it today.
Love the "open tab in another browser" action. I believe it is very useful. However, don't you think that enabling and disabling browsers would be better on the extension's settings? Right now, it is very hidden on the Action Command. Tab sorting would also be a great candidate for the preferences.
What do you think?

Hi @mil3na Thanks for the review and suggestion.
If I put it in the package.json preferences, I can't get all the user's browser apps dynamically, the data in the package.json is fixed.This Setup Browser Action is also made with reference to Browser Bookmarks.

Tab sorting as a setting item is a good choice, I will add this feature

Hi @mil3na I have submitted a new commit: New setting: Recent Tabs on Top, please keep it under review!

@mil3na It's ready to merge.


Account setting "Delete from Server" lost after SSLError

Hi,
ever and anon I get an SSLCertificate error with my provider gmx.net.
When this happens the account settings changes and mails will be no longer
deleted from the mail server after they are deleted localy. I have to change the settings by hand back.
regards
dieter

I can't reproduce this.
What K-9 Mail version are you using?
What protocol are you using (IMAP, POP3, WebDAV)?
Maybe unrelated but still interesting: why do you get SSL errors?

1.) I use version 5.004 with a Galaxy S5
2.) Protocol Pop3
3.) I haven't seen any details. In the last days it didn't happen. I guess a Mail-Server within the cluster with an invalid certificate. But I don't know for shure.

Is this still an issue?

Yes. It still happens from time to time. But it appears only a small message tls error without a code or so. I have a dialog where I can change my settings. There I prest next. I get a connection to my mail provider.  But I still need to change the delete option after this. Is it possible to extend the  ssl error message? Or having a last error log without turning on debug log?

Nice. Thx. I think this will fix it :+1:


WIP: add labs script for using pyradiomics with DICOM

Re #434

@JoostJM I am confused about flak8 errors - local checks pass. Do you know why it behaves differently on CI?
@zhenweishi the updated script is here. Once this PR is merged, it will be ready for your use.

TODO:

[ ] include pyradiomics version
[ ] fix flake8 issues

I am confused about flake8 errors - local checks pass. Do you know why it behaves differently on CI?

I think I understand - I did not take into account the project specific settings in https://github.com/Radiomics/pyradiomics/blob/2b98e8b15a2a8a3574869cb82dc32473591a2e09/.flake8

I think I understand - I did not take into account the project specific settings in

Should not matter if you run flake8 from the root directory.

Hi, Andrey and Joost
Thanks both. I will continue to work on that.
Best,
Zhenwei
On Mon, 8 Oct 2018 at 20:18, Andrey Fedorov<EMAIL_ADDRESS>wrote:

@JoostJM https://github.com/JoostJM I am confused about flak8 errors -
local checks pass. Do you know why it behaves differently on CI?
@zhenweishi https://github.com/zhenweishi the updated script is here.
Once this PR is merged, it will be ready for your use.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Radiomics/pyradiomics/pull/437#issuecomment-427931760,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQOCxYQoasf1OU6u2Koy_EhnFXvr5qvwks5ui5b_gaJpZM4XNYuB
.

btw @fedorov, I did a forced-push to remove an unnecessary merge from the history.

I may need to do few adjustments. I found a meaningful place to put pyradiomics processing parameters, but I will need to add things to dcmqi first to allow encoding of those attributes.

@zhenweishi can you tell me when you are planning to do the conversion? There is this one issue about encoding algorithm identification that I would like to fix, and it would help me prioritize things if I know your plans a bit better.


Error when repo.add with 2 arguments : options/callback

When using the "add" feature of repo, if you call it with two arguments : options and callback, there is an error because command line executed is "git add [Object object]".
I was trying with repo.add({"A":true}, function(){...}), that is not working.
When replacing "files" first argument with null, using repo.add(null, {"A": true}, function(){...}), it is working and runs "git add -A"
Maybe just confusing documentation because options is not specified ?

options should be documented


fix: array of items not supported by getNearestDependencies

Description
This PR fixes an issue with an array of items not supported and then renames the function getImmediateDependencies to getNearestDependencies.
Related issue(s)
fixes https://github.com/asyncapi/generator-model-sdk/issues/122
fixes https://github.com/asyncapi/generator-model-sdk/issues/186

Coverage increased (+0.008%) to 95.152% when pulling d25014dca2035758beec3ff8f04b00a6367b23c6 on jonaslagoni:hotfix/getImmediateDependencies into 1ac4ae28263102a109d54c79c0c9f62e1beb461f on asyncapi:master.

If we will support patternProperties etc we should also support them in getNearestDependencies function, so this PR should be fixed/merged after refactor.

Good point. However, I think we can adapt it already since it does not affect the refactor.


[WIP] Adding AnnotatedServiceBuilder to add service level settings to annotated service

Motivation:
It is good to provide an ability to user to configure per service level settings for annotated service.
Closes: https://github.com/line/armeria/issues/2023
Modifications:

Pulled all methods that AbstractServiceBindingBuilder(minus AbstractBindingBuilder)  has into an interface called ServiceBuilder
AbstractServiceBindingBuilder implements this(ServiceBuilder) interface and also extends AbstractBindingBuilder
AbstractServiceBuilder provides default implementation of ServiceBuilder

But there is still a code duplication in AbstractServiceBindingBuilder and AbstractServiceBuilder.
Result:
AnnotatedService can now be configured to have service specific properties.
This PR is not a final . This is just to get an initial review before making test and documentation changes.

Probably have to fix commit history. Will be fixing it in mean while.

But there is still a code duplication in AbstractServiceBindingBuilder and AbstractServiceBuilder.

In that case, I think we can use delegation:
public abstract class AbstractServiceBindingBuilder extends AbstractBindingBuilder implements ServiceBuilder {
    private final DefaultServiceBuilder serviceBuilder = new DefaultServiceBuilder();
    ...
    public AbstractServiceBindingBuilder requestTimeout(Duration requestTimeout) {
        serviceBuilder.requestTimeout(requestTimeout);
        return this;
    }
    ...
}

WDYT?

Sure.

Will be reopening with clean commit history and implementing all suggestions.

Hello @sivaalli! How's everything going? Just let us know if there's any trouble while you implementing this.
Meanwhile, I found out that @heowc's work on #1752 has a high chance of a large conflict with this PR. Because #1752 and this PR have to move the annotations parsing logic into ServerBuilder.build() I'm a little bit worried. 😉

Hi @minwoox , Everything is going good. I have made some progress. Currently adding tests. Expecting to be done by tomorrow.

Glad to hear that. 😄 Then, I think @heowc needs to wait and get work after your PR is merged.


🪺 argocd v2.3.6 🪺

What is this PR About?
argocd 2.3.6
How do we test this?
helm install
cc: @redhat-cop/day-in-the-life

/lgtm
/approve


docs: add Layer0 deployment guide

Description
This guides adds deployment guide of Shopify Hydrogen on the platform, Layer0.
Before submitting the PR, please make sure you do the following:

[x] Read the Contributing Guidelines
[x] Update docs in this repository for your change, if needed

Hi! Thanks for the contribution. We're not accepting updates to our list of deployment or hosting providers at the moment, but we'll keep Layer0 in mind when we update it again!

@jplhomer How about now?

@jplhomer https://shopify.dev/custom-storefronts/hydrogen/deployment would you be open to one now? I see many providers being added.

@rishi-raj-jain Hydrogen is pivoting to be simply Remix: https://hydrogen.shopify.dev/roadmap
All new Hydrogen apps will use Remix instead of this framework, so as long as Layer0 supports Remix, we should be good.


cirq.H with EigenGate implementation Fixes #872

Addressing: https://github.com/quantumlib/Cirq/issues/872

Closing because too many tests fail. Need to rewrite.

Testing the matrix for a few different values of half_turns should do it.

cirq/testing/random_circuit.py:67: error: Incompatible types in assignment (expression has type "Dict[EigenGate, int]", variable has type "Optional[Dict[Gate, int]]") for gate_domain = DEFAULT_GATE_DOMAIN. I've tried tracking it down with no success so far.

Ready for the second round.

👍

@Strilanc Oh man. I had a feeling there had to be something. Modifying the test to do
assert np.allclose(c_opt.to_unitary_matrix(), c_expected.to_unitary_matrix())

Fixes everything without calling round. Should I send a new pull request with the reversion and this change to test_optimize()?

But isn't the failure in the circuit comparison, not in the matrix comparison?
if you can cut the round call, go ahead and make a PR for that.

Yes. Thankfully this test can be implemented without circuit comparison.


python 3.5 locale of running container is still "POSIX"

It seems that #13 doesn't fix this problem.
I use the latest images (python 3.5.1).

When I run the image with docker run --rm -it python /bin/bash, and then I execute "locale" in the container, I found the locale is "C.UTF-8".

But when I run the image with docker run -d python  python -m http.server, and then enter into the container and execute "locale", I found it's "POSIX".

I don't think it's expected, right?

I am not able to reproduce. :confused:  Here is what I tried:
$ docker run -d --name py python:3.5.1 python -m http.server
43b6dc6dd12a1e621b79eace4dc86b0bb28b3c9ea0098917da1add93a44abe07
$ docker exec -it py bash
root@43b6dc6dd12a:/# locale
LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_PAPER="C.UTF-8"
LC_NAME="C.UTF-8"
LC_ADDRESS="C.UTF-8"
LC_TELEPHONE="C.UTF-8"
LC_MEASUREMENT="C.UTF-8"
LC_IDENTIFICATION="C.UTF-8"
LC_ALL=
root@43b6dc6dd12a:/#

For method2, I used nsenter to enter into the container. And the locale is "POSIX".
I also tried with docker exec -it py bash, locale is "C.UTF-8".
I found that if you ran bash first, the locale will be "C.UTF-8" but if you ran "python script.py" directly the locale will be "POSIX".
Then I will still get the problem UnicodeEncodeError: 'ascii' codec can't encode character.
I mean it seems adding ENV LANG C.UTF-8 in the Dockerfile doesn't fix the problem.
Now I have to run the container via docker run -e PYTHONIOENCODING=utf-8 to avoid the UnicodeEncodeError problem in #13

Maybe I should drop nsenter and switch to the docker exec -it bash way to enter into the container.

Yeah docker exec replaced nsenter. I still don't know why docker exec to python instead of bash would loose the locale.

I would like to add to this, how to set a foreign locale with the python image?
I am trying this in my Dockerfile
ENV LANG de_DE.UTF-8
ENV LANGUAGE de_DE.UTF-8
ENV LANG_ALL de_DE.UTF-8
ENV LC_ALL de_DE.UTF-8

but get an error message during building
`bash: warning: setlocale: LC_ALL: cannot change locale (de_DE.UTF-8)```
And then the app crashes
UnicodeEncodeError: 'ascii' codec can't encode character '\xe4' in position 5: ordinal not in range(128)
How is it possible to set a different locale via Dockerfile?

This is how I solved it for now in my  Dockerfile
# Install locales dependencies
RUN apt-get update && apt-get install -y --no-install-recommends \
        locales \
        apt-utils \
    && rm -rf /var/lib/apt/lists/*

# Configure timezone and locale
RUN echo "Europe/Berlin" > /etc/timezone && \
    dpkg-reconfigure -f noninteractive tzdata && \
    sed -i -e 's/# en_US.UTF-8 UTF-8/en_US.UTF-8 UTF-8/' /etc/locale.gen && \
    sed -i -e 's/# de_DE.UTF-8 UTF-8/de_DE.UTF-8 UTF-8/' /etc/locale.gen && \
    echo 'LANG="de_DE.UTF-8"'>/etc/default/locale && \
    locale-gen de de_DE de_DE.UTF-8 && \
    dpkg-reconfigure --frontend=noninteractive locales && \
    update-locale LANG=de_DE.UTF-8


added github issue template.

This is just one sugestion, what do you think about guthub templates?
https://github.com/blog/2111-issue-and-pull-request-templates

:+1: thanks!

:+1:


Caching issue with getSchema function

Issue workflow progress

Progress of the issue based on the Contributor Workflow

[ ] 1. The issue provides a reproduction available on GitHub, Stackblitz or CodeSandbox

Please make sure the graphql-eslint version under package.json matches yours.

[ ] 2. A failing test has been provided
[ ] 3. A local solution has been provided
[ ] 4. A pull request is pending review

Describe the bug
Hi 👋
I've had some issues with tests using eslint's nodejs API and I realized it is because the parser uses a cached schema. This also seems to be the reason why the eslint service needs to be restarted in IDEs when there is a schema change and some rules, e.g no-unreachable-types, don't pick up the change.
I appreciate that caching the schema has performance implications, but without being able to reset the cache it can lead to unexpected behavior.
To Reproduce
Steps to reproduce the behavior:
Valid schema:
type Foo {
  bar: String!
}

type Query {
  foo: Foo!
}

Invalid schema:
type Foo {
  bar: String!
}

type Query {
  hello: String!
}

const pathToValidSchema = '...'
const pathToInvalidSchema = '...'

let eslint = new ESLint({
    useEslintrc: false,
    baseConfig: {
        parser: "@graphql-eslint/eslint-plugin",
        plugins: ["@graphql-eslint"],
        parserOptions: {
            schema: pathToValidSchema,
        },
        rules: {
           "@graphql-eslint/no-unreachable-types": "error"
        }
    },
})

let results = await eslint.lintFiles(pathToValidSchema)

expect(results[0].messages).toHaveLength(0) // ✅

eslint = new ESLint({
    useEslintrc: false,
    baseConfig: {
        parser: "@graphql-eslint/eslint-plugin",
        plugins: ["@graphql-eslint"],
        parserOptions: {
            schema: pathToInvalidSchema,
        },
        rules: {
           "@graphql-eslint/no-unreachable-types": "error"
        }
    },
})

results = await eslint.lintFiles(pathToInvalidSchema).

expect(results[0].messages).toHaveLength(1) // 🟥  <--- This will return 0 errors because it is still using the previous schema

Expected behavior
It should use the new paserOptions.schema and therefore return the correct number of errors.
Environment:

OS: MacOS
@graphql-eslint/eslint-plugin: 3.12.0
Node.js: 16.16

Resolution

As many of the rules have a test guard for caching, getSchema function could have one too.

if (process.env.NODE_ENV !== 'test' && schemaCache.has(schemaKey)) {
    return schemaCache.get(schemaKey);
  }

Caching could be based on content and not filename(s)

While option 1) is quicker to do, option 2) would also make sure that this plugin is working to its fullest in IDEs.

Hi ! Future release with cache invalidation could be tested in the following alpha version 3.13.0-alpha-20221024000319-1089aa0

released in<EMAIL_ADDRESS>


Issue with failure redirection

I am running into an issue where when I use this library to add recaptcha support it breaks the permitted access redirect to login?queryParam and this causes the captcha/error flagged actions to not properly work.  It ends up doing two redirects on a failed login /login -> /login?error -> /login only when I am using this to enhance the login form.
My config looks like
            enhancer.addRecaptchaSupport(http
                    .authorizeRequests()
                    .antMatchers("/static/**", "/csp-report-endpoint").permitAll()
                    .anyRequest().authenticated()
                    .and()
                    .formLogin())
                    .loginPage("/login")
                    .permitAll()
                    .and()
                    .logout()
                    .permitAll();

I am not sure why specifically adding this library causes this issue as I am still debugging.

I resolved this issue by adding "/login" to the antMatchers but I am still at a loss exactly why adding this broke things.

I think this is due to my config and not fully understanding how configuring security works under the covers.


A simple question on negative labels

It is mentioned in the analysis of the paper that the semantic space of the image is limited, so whether more negative labels will "just" cover the OOD data in the test set, resulting in the improvement of zero-shot performance?

You can refer to our rebuttals in ICLR 2024 and a reviewer asked a similar question.


Improvement for k8s.io/docs/reference/kubernetes-api/service-resources/service-v1/

Kindly add an example that will help

used incorrect account, closing this ticket


Authorization policy not enforced

Describe the bug
When RbacConfig is turned on, I can still access my service.
Expected behavior
When RbacConfig object is created, I should get access denied error.
Steps to reproduce the bug

Create a gke cluster
Install istio addon
gcloud beta container clusters update cluster1
--update-addons=Istio=ENABLED --istio-config=auth=MTLS_PERMISSIVE
Enable envoy injection for default namespace
kubectl label namespace default istio-injection=enabled --overwrite
Create a RbacConfig object.
Deploy my service.
User should get access denied.

Version
kubectl version v1.14.0
istio version --remote:
version.BuildInfo{Version:"1.1.1", GitRevision:"2b1331886076df103179e3da5dc9077fed59c989", User:"root", Host:"7077232d-4c6c-11e9-813c-0a580a2c0506", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Clean", GitTag:"1.1.0-17-g2b13318"}
Error: error execing into istio-citadel-7c4864c9d5-kplg6 citadel container: command terminated with exit code 255
Installation
gcloud beta container clusters update cluster1
--update-addons=Istio=ENABLED --istio-config=auth=MTLS_PERMISSIVE

The pilot discovery container doesn't have much logs for "rbac". The pilot istio-proxy container had errors "shutting down due to child request".
I don't see any log "built filter config for" for pilot.

Talked with @akyyy offline and logged into the user's cluster for debugging, the reason is you applied the wrong service which Istio doesn't support,
you need to name your service port following the Istio spec: https://istio.io/docs/setup/kubernetes/prepare/requirements/
I deleted one service and renamed the other one to start with http-.
Also please be noted, The RBAC in Istio 1.0 only supports HTTP, the RBAC in1.1 will also support TCP

/cc @liminw @wattli

Note, debugged with the customer offline for using Istio 1.1 in the customer's GKE cluster and it turns out the GKE cluster is started with some special arguments and it seems some firewall rules are preventing the connection to docker.io, which breaks the installation of Istio. Closing as this is not related to Istio.


Actor sheet does not work...

I installed the system manually into my foundry data/worlds folder, but the actor sheet does not function properly:

The sheet is missing the Attributes section,
Values will not be retained when you enter them on any other section of the sheet,
Equipment or other items cannot be dragged/dropped into the sheet (nothing happens when you try to do so).

Thanks.

Hello. There is now a version of WOIN that runs on foundry 0.8.8, which should have fixed all your issues.


where is my output in docker??

Where is the output after installing in docker?

The output is supposed to be stored in the same folder as that of Grawler.
On Sat, Feb 6, 2021 at 3:09 PM shahriarr_sec<EMAIL_ADDRESS>wrote:

Where is the output after installing in docker?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/A3h1nt/Grawler/issues/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANPWXZPRR64567OQ4TXFLRDS5UE6VANCNFSM4XGDGTPQ
.

Let me know if you've found the output so that I can close the issue.

Well, I installed with XAMPP. Thanks for this tool.


Support pip 8 hashes

pip 8 introduces a new feature that allows people to bake hashes into their requirements.txt, unfortunately this breaks pip-diff. An example would be https://github.com/pypa/warehouse/blob/master/requirements/main.txt
Output looks like:
Traceback (most recent call last):
  File "/app/tmp/buildpacks/python/vendor/pip-pop/pip-grep", line 81, in <module>
    main()
  File "/app/tmp/buildpacks/python/vendor/pip-pop/pip-grep", line 76, in main
    grep(**kwargs)
  File "/app/tmp/buildpacks/python/vendor/pip-pop/pip-grep", line 45, in grep
    r = Requirements(reqfile)
  File "/app/tmp/buildpacks/python/vendor/pip-pop/pip-grep", line 25, in __init__
    self.load(reqfile)
  File "/app/tmp/buildpacks/python/vendor/pip-pop/pip-grep", line 36, in load
    for requirement in parse_requirements(reqfile, finder=finder, session=requests):
  File "/app/tmp/buildpacks/python/vendor/pip-pop/pip/req/req_file.py", line 89, in parse_requirements
    for req in req_iter:
  File "/app/tmp/buildpacks/python/vendor/pip-pop/pip/req/req_file.py", line 172, in process_line
    for req in parser:
  File "/app/tmp/buildpacks/python/vendor/pip-pop/pip/req/req_file.py", line 89, in parse_requirements
    for req in req_iter:
  File "/app/tmp/buildpacks/python/vendor/pip-pop/pip/req/req_file.py", line 119, in process_line
    opts, _ = parser.parse_args(shlex.split(options_str), defaults)
  File "/app/.heroku/python/lib/python3.5/optparse.py", line 1388, in parse_args
    self.error(str(err))
  File "/app/.heroku/python/lib/python3.5/optparse.py", line 1568, in error
    self.exit(2, "%s: error: %s\n" % (self.get_prog_name(), msg))
  File "/app/tmp/buildpacks/python/vendor/pip-pop/pip/req/req_file.py", line 238, in parser_exit
    raise RequirementsFileParseError(msg)
pip.exceptions.RequirementsFileParseError: pip-grep: error: no such option: --hash

Thanks for the report — I find it interesting that no Heroku users have reported this yet. I suspect that while many people are excited that `--hash`` is available, almost none are actually using it.

I am a Heroku user ;)

@dstufft so what exactly is happening here? is parse_requirements bailing when it encounters a --hash?

Yes.

Is there another function available that doesn't fail in this situation, or perhaps a pre-processing step? What does pip do?

Pip added support for that flag, though actually looking at the code here maybe the real issue is just that buildpacks/python/vendor/pip-pop/pip needs updated to the lastest pip?

Ah, I see. Forgot about that.
That vendored pip was added to work around another issue. :)

Thanks for the report — I find it interesting that no Heroku users have reported this yet. I suspect that while many people are excited that --hash is available, almost none are actually using it.

The compile actually succeeds even with these exceptions, which is probably why people haven't reported it (https://github.com/heroku/heroku-buildpack-python/issues/302#issuecomment-219692444).

That vendored pip was added to work around another issue. :)

I've filed #10 for that issue (presuming there wasn't something else as well).

The master branch of this buildpack has this functionality restored.

This was fixed in heroku/heroku-buildpack-python#308 (which is currently the upstream for development) and then synced back to this repo in 4f5ebcd - so this issue can now be closed :-)


Remove version: Jackett.Jackett version 0.21.756

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.21.756/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


Installation of Angular-cli gives me warning error

I am trying to install Angular-cli in my terminal but when i run following command:
Yogesh:_logs yogi$ npm install @angular/cli -g
it gives me an error like this:
npm WARN checkPermissions Missing write access to /Users/yogi/.npm-global/lib/node_modules/@angular/cli/node_modules/@angular-devkit/schematics
npm WARN checkPermissions Missing write access to /Users/yogi/.npm-global/lib/node_modules/@angular/cli/node_modules/@angular-devkit/core
npm WARN checkPermissions Missing write access to /Users/yogi/.npm-global/lib/node_modules/@angular/cli/node_modules/@angular-devkit/architect
npm WARN checkPermissions Missing write access to /Users/yogi/.npm-global/lib/node_modules/@angular/cli/node_modules/@schematics/angular
npm WARN checkPermissions Missing write access to /Users/yogi/.npm-global/lib/node_modules/@angular/cli/node_modules/@schematics/update
npm WARN checkPermissions Missing write access to /Users/yogi/.npm-global/lib/node_modules/@angular/cli
npm WARN checkPermissions Missing write access to /Users/yogi/.npm-global/lib/node_modules/@angular/cli/node_modules/@angular-devkit
npm WARN checkPermissions Missing write access to /Users/yogi/.npm-global/lib/node_modules/@angular/cli/node_modules/@schematics
npm WARN checkPermissions Missing write access to /Users/yogi/.npm-global/lib/node_modules/@angular
npm ERR! path /Users/yogi/.npm-global/lib/node_modules/@angular/cli/node_modules/@angular-devkit/schematics
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/Users/yogi/.npm-global/lib/node_modules/@angular/cli/node_modules/@angular-devkit/schematics'
npm ERR!  { Error: EACCES: permission denied, access '/Users/yogi/.npm-global/lib/node_modules/@angular/cli/node_modules/@angular-devkit/schematics'
npm ERR!   stack: 'Error: EACCES: permission denied, access '/Users/yogi/.npm-global/lib/node_modules/@angular/cli/node_modules/@angular-devkit/schematics'',
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'access',
npm ERR!   path: '/Users/yogi/.npm-global/lib/node_modules/@angular/cli/node_modules/@angular-devkit/schematics' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).
npm ERR!      /Users/yogi/.npm/_logs/2018-10-19T23_26_46_228Z-debug.log.
Yogesh:~ yogi$ npm -v
6.4.1
Yogesh:~ yogi$ node -v
v8.12.0
Yogesh:~ yogi$ ng -v
-bash: ng: command not found
anyone know where's the problem?

Your project is open with editor.... and folder exists?

This seems like a problem with your node/npm and not with Angular CLI.
Please have a look at the fixing npm permissions page, common errors page, npm issue tracker, or open a new issue in that issue tracker if the problem you are experiencing isn't known.


Support for OpenAPI Specification - 'format' property for 'password' and 'email'

Description
While using an OpenAPI Specification YAML file, the 'format' field is not supported for types such as 'password' and 'email'.
According to the OpenAPI Specification (OAS), the 'format' field is open and can be used to validate input or map values to specific types in a programming language. However, it appears that Specmatic does not support specific formats like 'email' and 'password', ignoring the 'format'.
Steps to reproduce
Scenario 1: With Format field have value as 'email' and 'password'

Example Specification: With format field as 'email' and 'password'
servers:
  - url: http://localhost:3000
paths:
  /api/createuser:
    post:
      tags:
        - User Creation
      summary: Create a new user.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: "#/components/schemas/User"
      responses:
        "201":
          description: User account successfully created.
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    example: "User created successfully."
                  userId:
                    type: number
                    example: 123

components:
  schemas:
    User:
      type: object
      required:
        - username
        - password
        - email
      properties:
        username:
          type: string
          description: Desired username for the account.
          minLength: 5
          maxLength: 25
          example: joewilson
          pattern: "^[a-z]*$"
        password:
          type: string
          format: password
          description: Password for the account.
          minLength: 8
          maxLength: 25
          example: Password01
        email:
          type: string
          format: email
          description: Email address for account verification and communication.
          maxLength: 255
          example<EMAIL_ADDRESS>          pattern<EMAIL_ADDRESS>

Command to run the test: npx specmatic test createUser.yml --testBaseURL= http://localhost:3000

 Response
Request to http://localhost:3000 at 2024-1-31 1:12:32.507
    POST /api/createuser
    Accept-Charset: UTF-8
    Accept: */*
    Content-Type: application/json

    {
        "email": {
        },
        "password": {
        },
        "username": "RYOOF"
    }

  Response at 2024-1-31 1:12:32.561
    500 Internal Server Error
    X-Powered-By: Express
    Content-Security-Policy: default-src 'none'
    X-Content-Type-Options: nosniff
    Content-Type: text/html; charset=utf-8
    Content-Length: 1725
    Set-Cookie: connect.sid=s%3ACKQyQz_BtM2FUonhlygtjEsTHY_a_Zmm.0tQ3vrJtdFwWE7AFK6Z3UpMNP6HgH6s2bAvZW%2BxyMAE; Path=/; HttpOnly
    Date: Wed, 31 Jan 2024 02:12:32 GMT
    Connection: keep-alive
    Keep-Alive: timeout=5

Scenario 2: With Format field as string

Example Specification: With format field as string

servers:
  - url: http://localhost:3000
paths:
  /api/createuser:
    post:
      tags:
        - User Creation
      summary: Create a new user.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: "#/components/schemas/User"
      responses:
        "201":
          description: User account successfully created.
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    example: "User created successfully."
                  userId:
                    type: number
                    example: 123

components:
  schemas:
    User:
      type: object
      required:
        - username
        - password
        - email
      properties:
        username:
          type: string
          description: Desired username for the account.
          minLength: 5
          maxLength: 25
          example: joewilson
          pattern: "^[a-z]*$"
        password:
          type: string
          format: string
          description: Password for the account.
          minLength: 8
          maxLength: 25
          example: Password01
        email:
          type: string
          format: string
          description: Email address for account verification and communication.
          maxLength: 255
          example<EMAIL_ADDRESS>          pattern<EMAIL_ADDRESS>

Command to run the test: npx specmatic test createUser.yml --testBaseURL= http://localhost:3000

 Response
Request to http://localhost:3000 at 2024-1-31 1:14:3.610
    POST /api/createuser
    Accept-Charset: UTF-8
    Accept: */*
    Content-Type: application/json

    {
        "email": "OQXIV",
        "password": "HCYKWMPT",
        "username": "UQTQU"
    }

  Response at 2024-1-31 1:14:3.619
    201 Created
    X-Powered-By: Express
    Content-Type: application/json; charset=utf-8
    Content-Length: 56
    ETag: W/"38-GU8Q9mNu2zG5mhH8YsREsY1kHM4"
    Set-Cookie: connect.sid=s%3Al9XTqv9GjXp0KofMJrOGlIdwtkgZ9VSK.rm%2BIACiSOafPXDGGAvp3QE2vJuCck8S8LVQq58OPMx0; Path=/; HttpOnly
    Date: Wed, 31 Jan 2024 02:14:03 GMT
    Connection: keep-alive
    Keep-Alive: timeout=5

    {
        "message": "User UQTQU added successfully!",
        "userId": 42
    }

Expected behavior
Specmatic should support format of type 'email' , 'password'
Screenshots
Scenario 1 Example screeenshot

Scenario 2 Example screenshot

System Information:

OS & version: MacOS
Browser & version: [e.g. chrome, safari]
Specmatic version: 1.2.12
JDK version:  17

Additional context
Add any other context about the problem here.

hello @DeepikaHadadi, thanks a lot for all the details shared in the bug. We will certainly prioritise this.

@DeepikaHadadi The fix is now available as part of release 1.2.15.


[P4_Symbolic] Add golden test for packet synthesis for conditional.p4 and conditional_sequence.p4

Keyword Check:
~/sonic-buildimage/src/sonic-p4rt/sonic-pins$ ~/tools/keyword_checks.sh .
Keyword check Passed.
Build Result:
/sonic/src/sonic-p4rt/sonic-pins$ bazel build $BAZEL_BUILD_OPTS ...
INFO: Analyzed 542 targets (1 packages loaded, 117 targets configured).
INFO: Found 542 targets...
INFO: Elapsed time: 1.479s, Critical Path: 0.02s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
Test Result:
sonic/src/sonic-p4rt/sonic-pins$ bazel test $BAZEL_BUILD_OPTS --cache_test_results=no ...
INFO: Analyzed 542 targets (0 packages loaded, 16 targets configured).
INFO: Found 364 targets and 178 test targets...
INFO: Elapsed time: 221.840s, Critical Path: 119.21s
INFO: 232 processes: 269 linux-sandbox, 18 local.
INFO: Build completed successfully, 232 total actions
//gutil:collections_test                                                 PASSED in 0.5s
//gutil:io_test                                                          PASSED in 0.5s
//gutil:proto_matchers_test                                              PASSED in 0.6s
//gutil:proto_ordering_test                                              PASSED in 0.5s
//gutil:proto_test                                                       PASSED in 2.6s
//gutil:status_matchers_test                                             PASSED in 0.5s
//gutil:test_artifact_writer_test                                        PASSED in 0.6s
//gutil:testing_test                                                     PASSED in 0.5s
//gutil:timer_test                                                       PASSED in 5.1s
//gutil:version_test                                                     PASSED in 12.9s
//lib:basic_switch_test                                                  PASSED in 0.9s
//sai_p4/instantiations/google:tor_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google:union_p4info_up_to_date_test              PASSED in 0.1s
//sai_p4/instantiations/google:wbb_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google/test_tools:table_entry_generator_helper_test PASSED in 13.0s
//sai_p4/instantiations/google/test_tools:test_entries_test              PASSED in 0.9s
//sai_p4/tools:p4info_tools_test                                         PASSED in 0.6s
//sai_p4/tools:packetio_tools_test                                       PASSED in 1.0s
//thinkit:bazel_test_environment_test                                    PASSED in 0.7s
//thinkit:generic_testbed_test                                           PASSED in 0.9s
//thinkit:mock_control_device_test                                       PASSED in 0.6s
//thinkit:mock_generic_testbed_test                                      PASSED in 0.8s
//thinkit:mock_mirror_testbed_test                                       PASSED in 1.8s
//thinkit:mock_ssh_client_test                                           PASSED in 0.1s
//thinkit:mock_switch_test                                               PASSED in 0.7s
//thinkit:mock_test_environment_test                                     PASSED in 0.1s
//thinkit:switch_test                                                    PASSED in 0.8s
//sai_p4/instantiations/google/tests:p4_constraints_integration_test     PASSED in 1.9s
Stats over 5 runs: max = 1.9s, min = 0.7s, avg = 1.1s, dev = 0.5s
//sai_p4/instantiations/google/test_tools:table_entry_generator_test     PASSED in 43.7s
Stats over 50 runs: max = 43.7s, min = 0.8s, avg = 3.9s, dev = 10.1s
Executed 178 out of 178 tests: 178 tests pass.
INFO: Build completed successfully, 232 total actions

Co-authored-by: kheradmandG<EMAIL_ADDRESS>


I am not able to login

Not able to login with "admin" and "123" credentials

Are you trying to login to the project via my website or did you install it on your computer?

I tried in both ways but unable to logged in

Can you please help me out ?

There is problem with my login system & hashing password. I will check it and solve problems soon.

How do i access admin without login temporarily

Please help me out

I'm working on another project. I will take a look when i'm available as i said. Is there an urgent situation?

Yes bro, Urgent , I think it is small issue but i can't figure it out some how.

I am able to restore database files and able to login

can you explain the steps @PrathamBumb


supporting tool to be ready to handle new tx data structs

As a OmiseGO developer and integrator, I would like to use my dev tools that support the new tx data. So that I can keep up with the changes introduced in abstract layer
Risk

breaking changes that are non-backward compatible with older client libs

Value

integrators can easily integrate with abstract layer design feature

@Pongch What dev tools are we looking for here? In terms of interacting with the protocol transaction format and sending it to the contracts, we have https://github.com/omisego/ex_plasma which is client library to the plasma contracts.

oh, this issue is probably solved way back from the looks of it 👍 this is referring omg-js and the likes. I will close it


Alter SandboxRemote to use separate CAS store

See original issue on GitLab
In GitLab by [Gitlab user @jmacarthur] on Nov 5, 2018, 16:41
Background
Remote Execution currently uses the Artifact Cache to store and transmit filesystems and commands. Since !922, the Artifact Cache and Content-addressable storage cache are separate entities and we can just use a CASCache object for remote execution. Currently the configuration option for the artifact cache is used to select the cache for remote execution, so we'll need to add more configuration options.
Related to #659.
Task description

[ ] Add a configuration option which allows us to specify the endpoint for a CASCache separate to the artifact cache.
[ ] Rewrite SandboxRemote so it uses only CASCache, rather than ArtifactCache.
[ ] Remove the parts of ArtifactCache that are currently only used by SandboxRemote.

Acceptance Criteria
Equivalent remote execution functionality with the additional option to use a separate endpoint for remote execution storage.

In GitLab by [Gitlab user @jmacarthur] on Nov 9, 2018, 17:28
mentioned in merge request !946

In GitLab by [Gitlab user @jmacarthur] on Nov 27, 2018, 18:17
closed via merge request !946

In GitLab by [Gitlab user @jmacarthur] on Nov 27, 2018, 18:17
mentioned in commit 2a8a3b19966a25eff30391e9f50dbe9610d20c33


Fix app crashing error

UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
This error will cause nodejs to crash when the connection times out. Firewalls will cause timeout.
Error could be gracefully handled.

Thank you fro bringing this up. I think it is better to handle promise resolve and reject of client.connected in the place where this is called. Are you using SocketWrapper directly? Or through some higher level client in CosmJS?


Question: Does it support autoplay of youtube video?

Not sure about youtube video stream… I would rather recommend https://github.com/inProgress-team/react-native-youtube if you're not owning the mp4 file


A container with an IPv6 address occupies that address forever, therefore the container can't even be restarted.

Not related to the issue; happens on DigitalOcean just as locally and on my physical server. So, it was also tested with kernel 3.16.0-4-amd64 and Debian 8 - a completely different system than the one the docker info command is coming from - and the issue still persists.
Steps to reproduce the issue:

Create an IPv6 docker network: docker network create --ipv6 --subnet fe80:d000::/32 testnetwork
Run a container: docker run --net testnetwork --ip6 fe80:d000::10 --name testcontainer hello-world
Stop the container - hello-world does this by itself.
Start the container again: docker start testcontainer

Describe the results you received:
The container won't start because its IPv6 address is already in use, or at least Docker thinks it is.
Error response from daemon: Address already in use
Error: failed to start containers: testcontainer

Describe the results you expected:
The container starts on the same IPv6 address as I chose when running it.
Additional information you deem important (e.g. issue happens only occasionally):
This only happens if the container has an IPv6 address. Not with IPv4, and I assume the reason it seems to work without an IP specified in the run command is because it just gets another one the next time it's getting started - in fact, any IPv6 a container once had (also if you don't specify one) can not be used again (even for the same container) until the whole network is recreated. The IP cannot be used by any docker container from that point until the network is recreated - not even restarting the docker container or even rebooting the system fixes the issue.
Update: it seems like also the IPv4 address is blocked, but this seems to be only the case if an --ip6 is specified: after creating a container with docker run --net testnetwork --ip6 fe80:d000::10 --ip <IP_ADDRESS> --name testcontainer hello-world, the IP <IP_ADDRESS> is blocked for new containers even after this container is removed. When the same container is created without the --ip6 option, the IPv4 can still be used after the container is removed.
This looks like a pretty major bug for everyone who is using advanced container networking (or even just needs static IP containers) in combination with IPv6!

Known issue when user tries to reserve link-local addresses.
Reference https://github.com/docker/libnetwork/issues/988

@aboch is this being looked into?

There is specific link local address support in 1.12 I think, to address
this.
On 16 Jul 2016 10:43 p.m., "Sebastiaan van Stijn"<EMAIL_ADDRESS>wrote:

@aboch https://github.com/aboch is this being looked into?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/24269#issuecomment-233152569,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdcPAUuxPxd5KNqd71jKIGBi9WYa-ZAks5qWVCYgaJpZM4JDs5A
.

@moqmar @thaJeztah The issue is there only for link-local IPv6 addresses, not any IPv6 address.
Before moving forward, I would like to understand the use-case of using IPAM for link-local addresses.
By the nature of link-local addresses, we do not think they should be managed by the IPAM driver, and, as @justincormack pointed out, in docker 1.12 user will be able to specify a (IPv4 or IPv6) link-local address for the container's interface, without IPAM driver knowing about it (--link-local-ip).
Also, please note today user already has control over the default link-local IPv6 address assigned to the container's interface, by controlling the container's mac-address via the docker run option --mac-address.

@moqmar can you pls confirm @aboch's suggestion above and does that satisfy your requirement ?

Sorry, totally forgot about this issue - yep, --link-local-ip is pretty much exactly what I needed.


Update ACCP

Motivation:
Test with the latest Amazon Corretto Crypto Provider release.
Modification:
Update corretto version to 2.4.1, and pull the classifier from the OS maven extension.
Result:
We now test with the latest ACCP, and we can run those tests on aarch_64 platforms, because ACCP support those now.

The maven changes need more work since we get compilation failures on some platforms


stringRep ends with '\r'

With some scl files, I assume those with Windows/DOS line endings, stringRep contains a string ending with \r
wilson5.scl.txt

for now at least you can run dos2unix on that file and it should load fine. Presume you know that but in case you don't!

Sure, also easy to fix in our project using the library, just thought I'd report here in case you were not aware of it.

I was not! Appreciate the flag and will definitely think about how to fix. I guess just strop \r if they show up is the standard approach. Thank you!

Basically I need to replace std::getline with something more like this https://gist.github.com/josephwb/df09e3a71679461fc104
And then add your file to our test suite (presume you are OK if I do that but want to check!)

The file was taken from the zip file of scales from the Scala website.

Great. Turns out we already had a test dos le in our test set; I just only checked the parsing not the stripping.
PR and change coming shortly. I'll update surge also so it uses it before the 19 release.

OK fix in place along with expanding the test some. Thanks!

Oooh one more tweak coming. All our tests in tuning-lib pass with this change but one surge test is failing. Stay tuned!

Sneaky extra line at end of file check failed and we test that in surge tests but not tuning lib tests. All good to go now. Updating surge also.


Use a proxy ?

Describe the feature you would like to see
Hello,
Could you add the possibility yo use a proxy ?
Maybe add a http client config in the bundle configuration ?
Do you already have a solution ?
Ty

If you are agree with https://github.com/kreait/firebase-bundle/pull/60 , I could use my own ProjectFactory class to define the proxy.
class ProjectFactory extends \Kreait\Firebase\Symfony\Bundle\DependencyInjection\Factory\ProjectFactory
{
    public function createFactory(array $config = []): Factory
    {
        $factory = parent::createFactory($config);

        $httpClientOptions = HttpClientOptions::default();
        $httpClientOptions = $httpClientOptions->withGuzzleConfigOptions([
            'proxy' => 'http://proxy',
        ]);

        return $factory->withHttpClientOptions($httpClientOptions);
    }
}

I decided not to use the bundle. There are some issues and I can't override configurations.
So I used the php sdk only.
I share my config for a messaging usage with an unique client :
    ####
    # Kreait Firebase
    ####
    kreait_firebase.http_config_options:
        class: Kreait\Firebase\Http\HttpClientOptions
        factory: ['Kreait\Firebase\Http\HttpClientOptions', 'default']
        calls:
            - withProxy: !returns_clone ['%env(HDS_HTTP_PROXY)%']

    Kreait\Firebase\Factory:
        calls:
            - withHttpClientOptions: !returns_clone<EMAIL_ADDRESS>            - withServiceAccount: !returns_clone ['%env(resolve:FIREBASE_CREDENTIALS_PATH)%']
            - withHttpLogger: !returns_clone<EMAIL_ADDRESS>
    Kreait\Firebase\Contract\Messaging:
        factory: ['@Kreait\Firebase\Factory', 'createMessaging']

Good call, that's how I would recommend it anyway - perhaps I should update the README at some point...
Anyway, thanks for sharing, it will certainly be useful to others. I'll keep this and/or the other issue open for the time being, perhaps I can find some time somewhen.

Since you've given an example how to use the SDK without this bundle (again: 👏), and I've merged #60, I'll close this issue now, but feel free to add further comments if you'd like.


[QUESTION] Show result of curl request to TXT

Question
There is some pages (internet) that return simple raw TXT content. (for ie http://ipecho.net/plain )
There is a way to display that kind of  result ?
Category
Setup and Deployment
Please tick the boxes

[X] You are using a supported version of Dashy (check the first two digits of the version number)
[X] You've checked that this question hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

curl https://ipecho.net/plain returns the ip for me just fine.
Here I did it with js html and css, I think it would be best to create a jsfiddle account create a little widget with some html css as you like and just iframe it into dashy.
https://jsfiddle.net/CrazyWolf/qduzh524/4/
https://dashy.to/docs/widgets/#iframe-widget
Have fun :)

Ok will try it as soon as i can.


Using websockets to pass data?

I understand that I can use command passthrough but that is reliant on a transactional system.  If i have a websocket open and i am sending data to a room, and listening for data on a room I am not sure how to push the data I am listening for to the terminal.
I need some way to bind a listener to a prop within Terminal that will, when receives data, push more lines to the terminal, this may be completely independent of any command, and may happen without user input.
As of right now I cannot figure out a way to do this, any help?

I would suggest reading up on the plugin api https://github.com/nitin42/terminal-in-react/wiki/Plugins

Please close this if that satisfies your question

I am not the most clever man but I cannot seem to make it do what I want it to do.  I have created a plugin:
`import { PluginBase } from 'terminal-in-react';
export default class TerminalPlugin extends PluginBase {
static displayName() {
return 'Plugin';
}
static version() {
return '1.0.0';
}
constructor(api, config = {}) {
super(api, config);
this.api = api;
this.config = config;
}
response(res) {
    this.api.printLine(res);
}

}`
And I am then loading this plugin:
<Terminal               color="white"               prompt="white"               backgroundColor='black'               barColor='black'               style={{ fontWeight: "bold", fontSize: "1em" }}               hideTopBar               allowTabs={false}               plugins={[                   TerminalPlugin               ]}               watchConsoleLogging={false}   />
and in my component where I am rendering this I am doing this:
componentDidMount() {         setInterval(() => {             TerminalPlugin.response('WOAH A TEST THING!');         }, 2000); }
But instead of that data being pushed to the terminal I am getting this error:
Terminal.jsx:41 Uncaught TypeError: _TerminalPlugin2.default.response is not a function
I am relatively new with classes but I thought I would just be able to access that function.

A few things. displayName and version have to be strings not functions.
Each tab instantiates the plugin. Which means it takes the class and calls new on it. Class methods are not available in that manner unless they are static but plugins are only able to access the api methods in non-static methods. My suggestion is to pass in the socket as a config. This assumes socketio.
import { PluginBase } from 'terminal-in-react';
export default class TerminalPlugin extends PluginBase {
    static displayName = 'Plugin';
    static version = '1.0.0';

    constructor(api, config = {}) {
        super(api, config);
        config.socket.on('someEvent', this.response);
    }

    response = (res) => {
        this.api.printLine(res);
    }
}

Used in a component that connects to the socket and has it available
<Terminal
  color="white"
  prompt="white"
  backgroundColor='black'
  barColor='black'
  style={{ fontWeight: "bold", fontSize: "1em" }}
  hideTopBar
  allowTabs={false}
  plugins={[{
    class: TerminalPlugin,
    config: {
      socket: this.socket
    }
  }]}
  watchConsoleLogging={false}
/>

You sir are a genius, I believe this should do it!  Real quick, and I completely understand that this is not really the place for this question, so feel free to disregard and close, but I am not using the stage-0 babel presets so I cannot do class property transforms, so writing static displayName = "Plugin"; throws an error during webpack.  I thought the way to get around this was writing it as I did above, but clearly that is wrong, is there a way to write it appropriately without using the transform?

Yes if you are not using stage-0 or stage-1 i believe, then you can add static attributes like so.
import { PluginBase } from 'terminal-in-react';
class TerminalPlugin extends PluginBase {
   constructor(api, config = {}) {
       super(api, config);
       config.socket.on('someEvent', this.response);
   }

   response = (res) => {
       this.api.printLine(res);
   }
}

TerminalPlugin.displayName = 'Plugin';
TerminalPlugin.version = '1.0.0';

export default TerminalPlugin;

If this is working for you now please close this issue :)

Yes, sorry for the delayed response!  Thank you for helping clarify my noob misunderstandings, thank you!


Optimization: put pieces in CSS sprites and/or convert to SVG

Issue #113 uses a data-uri and is probably the best solution here.


Issue 1167:  Replace application.properties by yaml equivalent

Fixes #1167.

Replaced application.properties with application.yaml.

Acceptance Test

[ ] Building the code with mvn clean install -Dintegration.tests still works.
[ ] Running mvn spring-boot:run in the strongbox-web-core still starts up the application correctly.
[ ] Building the code and running the strongbox-distribution from a zip or tar.gz still works.
[ ] The tests in the strongbox-web-integration-tests still run properly.

Hi, @sudhs22!
Thank you for your contribution!
Would you mind signing the ICLA, as described in the Contributing page?
I have updated your PR's decription to also include the acceptance tests for this task. Could you please confirm, if all these tests pass as well? Thanks!
Also, please, feel free to join our chat channel, if you'd like to learn more about the project and/or like to find out what else you could help with.
Kind regards,
Martin

Hey Martin,
I will sign the ICLA and send the scan copy on this email in 2 days time.
I have run the command "mvn clean install", which ran all the tests and it
passed. Let me know if anything other tests needs to be run.
Thanks a lot.
Regards,
Sudeep
On Sun, Apr 21, 2019 at 6:49 PM Martin Todorov<EMAIL_ADDRESS>wrote:

Hi, @sudhs22 https://github.com/sudhs22!
Thank you for your contribution!
Would you mind signing the ICLA, as described in the Contributing
https://github.com/strongbox/strongbox/blob/master/CONTRIBUTING.md page?
I have updated your PR's decription to also include the acceptance tests
for this task. Could you please confirm, if all these tests pass as well?
Thanks!
Also, please, feel free to join our chat channel
https://chat.carlspring.org/, if you'd like to learn more about the
project and/or like to find out what else you could help with.
Kind regards,
Martin
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/strongbox/strongbox/pull/1242#issuecomment-485251213,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC7ODPQHS3TBFB6EVR7SQK3PRRSUTANCNFSM4HHLR52A
.

Hi,
We'll need to have your ICLA before being able to merge this PR.
In your comment above, I have listed the things you will need to run in order to check, if your changes work properly across all the affected projects and modules. Could you please look into this?

Heey @sudhs22 ,
Have you had a chance to sign the ICLA?

Hey @sudhs22 ,
Have you had a chance to sign the ICLA? We'll need you to sign this in order to be able to accept and merge your pull requests.

Hi @carlspring, in case @sudhs22 doesn't answer, I can take it (Wold I have to create another PR?

@ptirador : Please, proceed! ;)

Thanks for your efforts, @sudhs22, but we can only merge pull requests from contributors who have signed the ICLA.
Closed in favour of #1283.


Subgraph removing error : Removing subgraphs is not supported at this time.

I tried to remove a subgraph and the command shows an error explaining the operation is not supported
graph -v
0.19.0
graph remove / --node https://api.thegraph.com/deploy/
✖ Error removing the subgraph: Removing subgraphs is not supported at this time.

@ssilvajb please ask in our Discord and we will be able to remove the subgraph for you.


Corrects the Felix usage reporting options

Description
Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit 2e8914383e2fb5a8a13ab2a5cc3a99d82331af01
https://deploy-preview-2348--calico.netlify.com

I think the doc is already correct.  Yes, all env vars are strings, but the syntax is is telling you how to format that string so that Felix can parse it.  YAML is a typed format so things are a little different there.


ImportError: No module named glade

I was following the instructions to install xflux-gui on my Ubuntu 14.04 (x64) machine and at the end, when it seems the installation finishes, I run the command fluxgui (as the guide says) and it appears this error:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/fluxgui/fluxapp.py", line 6, in <module>
    import gtk.glade
ImportError: No module named glade

I tried to reinstall it but didn't worked. The first command sudo apt-get install git python-appindicator python-xdg python-pexpect python-gconf python-gtk2 python-glade2 libxxf86vm1 -y (where I think it have the problem, show this log:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libxxf86vm1 is already the newest version.
libxxf86vm1 set to manually installed.
python-gconf is already the newest version.
python-gconf set to manually installed.
python-gtk2 is already the newest version.
python-gtk2 set to manually installed.
python-xdg is already the newest version.
python-xdg set to manually installed.
git is already the newest version.
python-pexpect is already the newest version.
python-pexpect set to manually installed.
The following packages were automatically installed and are no longer required:
  linux-headers-4.2.0-38 linux-headers-4.2.0-38-generic
  linux-image-4.2.0-38-generic linux-image-extra-4.2.0-38-generic
  linux-signed-image-4.2.0-38-generic
Use 'apt-get autoremove' to remove them.
The following extra packages will be installed:
  libglade2-0
Suggested packages:
  python-gtk2-doc
The following NEW packages will be installed:
  libglade2-0 python-appindicator python-glade2
0 upgraded, 3 newly installed, 0 to remove and 9 not upgraded.
Need to get 61,1 kB of archives.
After this operation, 398 kB of additional disk space will be used.
WARNING: The following packages cannot be authenticated!
  python-appindicator
E: There are problems and -y was used without --force-yes

It had a Warning, but is not an error.
Anyone have the same issue as me and found a solution?

Looking at the apt-get install output above it looks like it failed because you used -y and there was a warning about not being able to authenticate the python-appindicator package. Please try
sudo apt-get install git python-appindicator python-xdg python-pexpect python-gconf python-gtk2 python-glade2 libxxf86vm1

(i.e. without the -y) instead.


Convert class components to functional components in the API docs examples

name: :book: New/Updated Documentation Content
about: Adding a new docs page, or updating content in an existing docs page
PR Type
Does this PR add a new page, or update an existing page?
Checklist

[x] Is there an existing issue for this PR?

https://github.com/reduxjs/redux/issues/4253

[x] Have the files been linted and formatted?

What docs page is being added or updated?

Section:

API Reference

Pages:

applyMiddleware
bindActionCreators

For Updating Existing Content
What updates should be made to the page?
The class-based react components should be converted to functional components.
Do these updates change any of the assumptions or target audience? If so, how do they change?
Converting the components to functional components assumes the audience understands the basics of functional react components and hooks. In contrast, the existing examples assume the audience understands the lifecycle methods of class components. Both of these concepts are foundational to modern React development. Still, functions and hooks seem to be the preferred method of defining a component (e.g., the React docs have mainly been rewritten to use functional components: https://reactjs.org/docs/lists-and-keys.html).

Sweet, thank you!
Yeah, there's a lot of the docs pages that need to be rewritten to show "modern Redux" and "modern React", but those have been low priority.
If you'd like to try updating some of the other docs pages, that would be wonderful!

My pleasure! I'll give it a whirl!


iOS capitalizes first letter despite KeyboardCapitalization.None

Here's my field
OutlinedTextField(
                value = email,
                onValueChange = { email = it },
                label = { Text("Email") },
                keyboardOptions = KeyboardOptions(
                    keyboardType = KeyboardType.Email,
                    imeAction = ImeAction.Next,
                    capitalization = KeyboardCapitalization.None
                ),
                modifier = Modifier.fillMaxWidth()
            )

Affected platforms
Select one of the platforms below:

iOS

Versions

Kotlin version*: 1.8.2
Compose Multiplatform version*: 1.4
OS version(s)* (required for Desktop and iOS issues): 12.6.1
OS architecture (x86 or arm64): x86
JDK (for desktop issues): 11

To Reproduce
Steps and/or the code snippet to reproduce the behavior:

in a multiplatform app, create a text field, like this

OutlinedTextField(
                value = email,
                onValueChange = { email = it },
                label = { Text("Email") },
                keyboardOptions = KeyboardOptions(
                    keyboardType = KeyboardType.Email,
                    imeAction = ImeAction.Next,
                    capitalization = KeyboardCapitalization.None
                ),
                modifier = Modifier.fillMaxWidth()
            )

Run the iosApp, and see that the first letter is capitalized, when typing into the input.

Expected behavior
I'd expect this option to apply in iOS: KeyboardCapitalization.None
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

keyboardOptions and keyboardActions are not implemented for iOS

OK, thanks for the quick response.

Duplicate of #2735

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Add case UUIDs to tests

CI doesn't seem to like this change

There's a problem with the latest Rakudo Star missing dependencies for the prove6 testing harness. I've resolved the issue upstream but there hasn't been a release with the fix yet.


switch clients for pkg/service tests

(don't merge, will try to put more commits here)

@mfojtik remove WIP, when it's ready for merge :)


Serve stale content from child if parent returns invalid/marked down

For hierarchical caching, when a child proxy needs to revalidate its stale content with the parent proxy but the parent returns an invalid response or is marked "unavailable", the child proxy should still return the stale content with a warning header. This is the same behavior without hierarchical caching, when the origin server is down and a server tries to revalidate its stale content and when it fails to, it returns back a 200 OK response with a warning header.
These changes still respect the max_stale_age configurations and do not serve stale content pass the expiration date.
Changes made:

when child receives invalid response from parent, it first checks if the stale cache response is returnable. if not, then it calls handle_parent_died to build the error response message
when the parent is marked down or unavailable (without making a request), it first checks if the stale cache response is returnable before building the error response message

the parent can be marked unavailable when the number of retries to the parent exceeds proxy.config.http.parent_proxy.fail_threshold within proxy.config.http.parent_proxy.retry_time
the is_server_negative_cached is removed as the conditional checks with configs only applicable to origin server. parent server status and selection (whether its marking a parent down or deciding the next available parent) are already decided in ParentSelectionStrategy

Autest checks the following using a PUSH workaround to mock parent going down:

Child returns stale content with warning header when object's age is less than max_stale_age and parent fail count is below parent_proxy.fail_threshold
Child returns stale content with warning header when object's age is less than max_stale_age and parent fail count is passed parent_proxy.fail_threshold and parent is marked unavailable
Child does not return stale content when object's age exceeds max_stale_age

Note: this is an updated PR from #8248

Cherry-picked to v9.2.x


Bump node-exporter to a stable version

When bootstraping node-exporter with the kube-prometheus helm chart I got an error
time="2017-08-14T13:05:51Z" level=error msg="ERROR: hwmon collector failed after 0.000024s: open /host/sys/class/hwmon: no such file or directory" source="node_exporter.go:91"

Node-exporter already fixed this issue on v0.14

lgtm


⚠ Bofrost.lu has degraded performance

In c1613fd, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1780 ms

Resolved: Bofrost.lu performance has improved in 6a0d52c after 38 minutes.


OkCoin: Fix futures typo

Typo in extracting margin field when querying for cross margin funds.

Will have to add another commit here


feat: version tracker

Closes https://github.com/cdklabs/construct-hub-webapp/issues/538
Closes https://github.com/cdklabs/construct-hub-webapp/issues/539
Closes https://github.com/cdklabs/construct-hub-webapp/issues/540
This adds a backend component that generates all-versions.json, a file in the backend that tracks all of the versions available of all packages, so that available version information can be displayed on the front end (to be added in a follow-up PR).
The file looks a bit like this:
{"packages": {"@aws-amplify/cdk-exported-backend": ["0.0.1","0.0.2","0.0.3","0.0.4","0.0.5"], "@aws-c2a/cdk-pipelines-step": ["0.7.1"], "@aws-cdk/assertions-alpha": ["2.0.0-alpha.1","2.0.0-alpha.2","2.0.0-alpha.3","2.0.0-alpha.4","2.0.0-rc.23","2.0.0-rc.24"], ....

To generate it, every minute a lambda makes ~1,000 S3 ListObjects calls in parallel over the course of 3-5 seconds*, and saves the results to the S3 bucket where package data is stored. The resulting JSON file is around 500kb on my development Construct Hub instance, or around half of the size of the catalog.
There are several other ways we could go about storing and updating this version data (e.g. storing a separate file per package, only updating the list of versions every time a new package is ingested, etc.) but these tend to add additional complexity since either more files need to be managed, or more failure modes are introduced as the component would have to integrate with the deny-list and ingestion systems.
Lambda invocations and S3 API calls aren't free, but my back-of-the-envelope calculation looked a bit like this:
S3 API calls: $7.2 / day = $0.000005 (per S3 requests) * 1000 (S3 requests per Lambda invoke) * (60 invokes / hr) * 24 (hrs / day)
Lambda cost:  $1.2 / day = $0.0000001667 (price per ms) * 5000 (ms per invoke) * 60 (invokes / hr) * 24 (hrs / day)
Total cost:   $8.4 / day

*These numbers are based on the ~800 packages we currently have in the public Construct Hub, and would be lower for private construct hub instances.
TODO:

[ ] Add unit tests
[ ] Add dashboard graphs

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Updated per feedback and added dashboard widgets and a unit test. I had to rebase my PR since it was originally written on top of the dev branch and accumulated a bunch of unrelated cruft.

I only have one (minor) concern that this might collect package versions based solely on the key prefix, while there is no viable data under that key (i.e: incomplete ingestion). This might be an acceptable trade-off though.

Yeah I think this trade-off is acceptable. I'm curious to see how often this happens - in most situations I've seen, if a package is determined to be invalid (e.g. it's missing a .jsii file) then the package data doesn't get stored in the bucket.
If a package ingested successfully but we weren't able to generate docs for it, then that package version will be included, but I think this is reasonable behavior (trying to view its docs will just show the page is unavailable).


How to use ITKIOOMEZarrNGFF in C++?

Can you please elaborate a little bit more on how to use ITKIOOMEZarrNGFF in C++? I see, https://github.com/InsightSoftwareConsortium/ITKIOOMEZarrNGFF/blob/fe5bc3caecfe774e64acabfd75e9d74e22eacfb5/README.md says:

Usage from C++ should not require any special action. In special situations, you might need to invoke:

itk::OMEZarrNGFFImageIOFactory::RegisterOneFactory();

Looks fine, but then, what steps are there to take to get it compiled? Is the idea for the client application to use something like ExternalProject_Add(ITKIOOMEZarrNGFF ...) in their CMakeLists.txt?
Is the intention to (eventually?) allow ITKIOOMEZarrNGFF to be selected as an optional module when CMake-configuring ITK?

Is the intention to (eventually?) allow ITKIOOMEZarrNGFF to be selected as an optional module when CMake-configuring ITK?

Yes. But meanwhile, read on.
Depending on the build system, ExternalProject_Add is a possibility. Probably the easiest is to build ITK, then build ITKIOOMEZarrNGFF pointing to the ITK build directory, and then use that ITK build directory from then on.


Pylance issue

 Environment data

Language Server version: 2024.8.1
OS and version: darwin arm64
Python version (and distribution if applicable, e.g. Anaconda):
python.analysis.indexing: true
python.analysis.typeCheckingMode: off

 Code Snippet

XXX

 Repro Steps

XXX

 Expected behavior
XXX
 Actual behavior
XXX
 Logs

XXX

Thanks for the report. Unfortunately, this is not enough information for us to investigate this issue.
If this continues to be a problem, would you please reopen the issue and add the information described in the troubleshooting guide?


Update change request template

This Pull Request updates GitHub templating.  As a matter of GitHub interface programming, committee review is not required.

Although I'm fine with the text, wouldn't it be more efficient to turn around the proof of acceptance:

either include a checked checkmark placed before the text, or
simply include the text into the template
This implies that requesters should remove the acceptance as opposed to include it.

@plbt5 : Checkmarks have an odd effect on the GitHub interface - they're interpreted as tasks to complete, so somewhat enact a requirement on the user.  This was intended to be an opt-in request from the Ontology Committee to the posting user.
GitHub Markdown also doesn't appear to support radio buttons at the moment; I'd put a pair of those in if the technical option were available.


PBKDF2 SHA1 iterations

I saw that the V3 format is using SHA1 with 10,000 iterations for key derivation, which is rather far away from the current recommendation of 1,300,000 iterations. I read in your FAQs that the decision to hardcode the iterations is intentional to make the format interoperable, but since RNCryptor's pbkdf2 functionality is still used by apps in the app store, I'm wondering what the best approach would be to prevent these apps from relying on such a low iteration count.

There is no way to change the encryption used by existing apps. That would be true no matter the format. But in particular, the RNCryptor v3 format does not encode an iteration count, so it absolutely cannot be changed for existing programs. And no system can change the parameters for existing encrypted data without modifying the file, even systems that do encode their parameters.
RNCryptor v4 supports encoding the iteration count up to 10M iterations. That format has never been implemented to my knowledge. I wouldn't implement the v4 spec today; it's not worth the trouble. Widely available crypto libraries have improved a lot since I designed it, and so some of the trade-offs are no longer necessary.
Any app that uses RNCryptor v3 today can definitely alter the number of iterations for its own ecosystem by modifying the code. It's a simple change for every RNCryptor implementation. This will break compatibility of course, both with other implementations and with any existing encrypted data, but most uses of RNCryptor are within a single ecosystem; it's not generally treated as a general-purpose storage format like ZIP. Modifying the iteration count has been commonly done for JavaScript implementations, which were (at the time) unable to handle 10k iterations in reasonable time and often were forced to use only 1000 to keep the system usable.


[SPARK-41971][SQL][PYTHON] Add a config for pandas conversion how to handle struct types

What changes were proposed in this pull request?
Adds a config for pandas conversion how to handle struct types.

spark.sql.execution.pandas.structHandlingMode (default: "legacy")

The conversion mode of struct type when creating pandas DataFrame.
When "legacy", the behavior is the same as before, except that with Arrow and Spark Connect will raise a more readable exception when there are duplicated nested field names.
>>> spark.sql("values (1, struct(1 as a, 2 as a)) as t(x, y)").toPandas()
Traceback (most recent call last):
...
pyspark.errors.exceptions.connect.UnsupportedOperationException: [DUPLICATED_FIELD_NAME_IN_ARROW_STRUCT] Duplicated field names in Arrow Struct are not allowed, got [a, a].

When "row", convert to Row object regardless of Arrow optimization.
>>> spark.conf.set('spark.sql.execution.pandas.structHandlingMode', 'row')
>>> spark.conf.set('spark.sql.execution.arrow.pyspark.enabled', False)
>>> spark.sql("values (1, struct(1 as a, 2 as b)) as t(x, y)").toPandas()
   x       y
0  1  (1, 2)
>>> spark.sql("values (1, struct(1 as a, 2 as a)) as t(x, y)").toPandas()
   x       y
0  1  (1, 2)
>>> spark.conf.set('spark.sql.execution.arrow.pyspark.enabled', True)
>>> spark.sql("values (1, struct(1 as a, 2 as b)) as t(x, y)").toPandas()
   x       y
0  1  (1, 2)
>>> spark.sql("values (1, struct(1 as a, 2 as a)) as t(x, y)").toPandas()
   x       y
0  1  (1, 2)

When "dict", convert to dict and use suffixed key names, e.g., a_0, a_1, if there are duplicated nested field names, regardless of Arrow optimization.
>>> spark.conf.set('spark.sql.execution.pandas.structHandlingMode', 'dict')
>>> spark.conf.set('spark.sql.execution.arrow.pyspark.enabled', False)
>>> spark.sql("values (1, struct(1 as a, 2 as b)) as t(x, y)").toPandas()
   x                 y
0  1  {'a': 1, 'b': 2}
>>> spark.sql("values (1, struct(1 as a, 2 as a)) as t(x, y)").toPandas()
   x                     y
0  1  {'a_0': 1, 'a_1': 2}
>>> spark.conf.set('spark.sql.execution.arrow.pyspark.enabled', True)
>>> spark.sql("values (1, struct(1 as a, 2 as b)) as t(x, y)").toPandas()
   x                 y
0  1  {'a': 1, 'b': 2}
>>> spark.sql("values (1, struct(1 as a, 2 as a)) as t(x, y)").toPandas()
   x                     y
0  1  {'a_0': 1, 'a_1': 2}

Why are the changes needed?
Currently there are three behaviors when df.toPandas() with nested struct types:

vanilla PySpark with Arrow optimization disabled

>>> spark.conf.set('spark.sql.execution.arrow.pyspark.enabled', False)
>>> spark.sql("values (1, struct(1 as a, 2 as b)) as t(x, y)").toPandas()
   x       y
0  1  (1, 2)

using Row object for struct types.
It can use duplicated field names.
>>> spark.sql("values (1, struct(1 as a, 2 as a)) as t(x, y)").toPandas()
   x       y
0  1  (1, 2)

vanilla PySpark with Arrow optimization enabled

>>> spark.conf.set('spark.sql.execution.arrow.pyspark.enabled', True)
>>> spark.sql("values (1, struct(1 as a, 2 as b)) as t(x, y)").toPandas()
   x                 y
0  1  {'a': 1, 'b': 2}

using dict for struct types.
It raises an Exception when there are duplicated nested field names:
>>> spark.sql("values (1, struct(1 as a, 2 as a)) as t(x, y)").toPandas()
Traceback (most recent call last):
...
pyarrow.lib.ArrowInvalid: Ran out of field metadata, likely malformed

Spark Connect

>>> spark.sql("values (1, struct(1 as a, 2 as b)) as t(x, y)").toPandas()
   x                 y
0  1  {'a': 1, 'b': 2}

using dict for struct types.
If there are duplicated nested field names, the duplicated keys are suffixed:
>>> spark.sql("values (1, struct(1 as a, 2 as a)) as t(x, y)").toPandas()
   x                     y
0  1  {'a_0': 1, 'a_1': 2}

Does this PR introduce any user-facing change?
Users will be able to configure the behavior.
How was this patch tested?
Modified the related tests.

I'll move the conversion function to pyspark/sql/pandas/types.py.

Shall we add .. versionchanged:: to toPandas?

Merged to master, thank you!


Responsive Card Decks alternative

Alternative implementation of https://github.com/twbs/bootstrap/pull/29073. In draft to show difference.
The .row-cols-* modifier now targets all children, and the .col- classes can still be used to override this behaviour if needed. This implementation has cards of 100%, which makes them have equal heights by default.

The height: 100% will be a breaking change for v4, so maybe I should change that in a configurable null variable.

https://github.com/twbs/bootstrap/pull/29317 makes more sense, closing this


Not in npm

npm install cata-base returns error: Registry returned 404 for GET on https://registry.npmjs.org/cata-base

Sorry @juanbrujo but this repos es WIP, maybe I will change the name...


Added multi-select support to LxmlDriver

As initially described in #428, we need multi-select support for Flask (i.e. <select multiple>). In this PR:

Added test for serializing a form for a select with multiple values
Added serialize method for testing serialization exclusively
Added fix for fill_form to support accepting multiple values

Missing:

Test for fill_form with list coercion. I am not sure why my past self never wrote a test for that

@twolfson thank you!