Update context.json to allow for typing.

What?
Make context.json a templated function, allowing for better Typing support on route responses, if the .json function is used.
Why?
To be able to have strongly typed responses with a single function call.
interface ResponseInterface {
    hello: string;
}

interface ErrorInterface {
    success: boolean;
    error: string;
}

const get = async (ctx: Context): Promise<ResponseInterface | ErrorInterface> => {
    if (1 !== 0) {
            return ctx.json({success: false, error: 'Not Found'}, Status.NotFound);
    }
    return ctx.json({hello: 'World'});
};

Considering this code block, and the void return of context.json now, this would result in a linting error when considering the promise return type.
Implementation Example
interface ResponseInterface {
    hello: string;
}

interface ErrorInterface {
    success: boolean;
    error: string;
}

const get = async (ctx: Context): Promise<ResponseInterface | ErrorInterface> => {
    if (1 !== 0) {
            return ctx.json<ErrorInterface>({success: false, error: 'Not Found'}, Status.NotFound);
    }
    return ctx.json<ResponseInterface>({hello: 'World'});
};

How does the proposal fix the why?
Making context.json a templated function will allow us to return from that function, our intended output data ('v'), withe the type (T) that we expect, this allows us to return context.json to 'early exit' from various code where required, and have strongly typed responses expectations from controllers.
Yes, we can set the code, and return a JSON object from an async function already, however using the function handles this all in one go, and is more intuitive/meaningful (as a function)
Alternatives
Currently to get this functionality into your ABC application, you will need a wrapper. Or a helper function that mimics this flow, through a CustomContext or middleware or other means that embeds a context reference, exposing context.json
function  json<T>(v: T, code: Status = Status.OK): T {
    // context.json(v,code);
    return  v;
}

Thank you for your proposal, but I will not adopt it in the end.
Here is a quick explanation: Abc only uses TypeScript as a type annotation tool instead of a language. We encourage users to use the "as" keyword according to their needs. I will explain the purpose and benefits of this in a future document.


Triggering errors on form submit?!

Hello,
first of all thanks a lot for this library, it has been a lot of help .. but i'm having this issue where i want to trigger input errors on submit and prevent submitting?
I tried calling bootstrapValidate inside  $('#myForm').submit(function (event){} but it seemed that it's not triggering the errors only making the function start the validations!
Anything that I'm missing ?
best regards !

Hey,
thanks for reaching out! For this functionality I advise you to use https://github.com/jquery-validation/jquery-validation, since I'm not working on bootstrap-validate in the near future (or, ever, but who knows)

@MetalNose  If you are still looking for a solution for this, you can do the following:

Give your form an ID so that you can refer to it in Javascript.
Then write event.preventDefault() so that the form won't be submitted when the user clicks submit.
Write a new function called validateForm() that is supposed to submit the form once it's valid.
Include jQuery in your HTML. You will need it to find "form errors".

Let's put this all together:
Here is an example of your form tag:
<form method="POST" id="formSignup" onsubmit="event.preventDefault(); validateForm();">
</form>

Add this code before your </body> tag:
<script src="https://code.jquery.com/jquery-3.5.1.min.js" crossorigin="anonymous"></script>
<script>
	function validateForm()
	{
		//Find the number of form errors shown
		var numInvalid = $( "#formSignup" ).find( ".invalid-feedback:not(:hidden)" ).length;

		if (numInvalid == 0) {
			//No errors, submit form
			document.getElementById("formSignup").submit();	//All is good. Submit form.
		}
		else {
			//Errors found, do not submit
		}
	}
</script>

I hope this helps anyone who still wants to use this wonderful library, without waiting for the new version.


Dev Portals Blog Post

Description
Checklist:

[ ] I have reviewed the style guide.
[ ] If blogging, I have reviewed the blogging guide.
[ ] I have manually confirmed that all new links work.
[ ] I added aliases (i.e., redirects) for all filename changes.
[ ] If making css changes, I rebuilt the bundle.

@meagancojocar Dropping a reminder not to publish until someone has gotten that GIF uploaded for you! :-)


WE-542 Use menuItemText

Fixes
This pull request fixes WE-542
Description
Use menuItemText in applicable context menus. Also implement ObjectsSidebarContextMenu to replace existing menus that include only a paste item.
Type of change

Enhancement of existing functionality

Impacted Areas in Application

Frontend

Checklist:
Communication

[x] PR is related to an issue
[ ] I have made corresponding changes to the documentation

Code quality

[x] Code follows the style guidelines
[x] I have self-reviewed my code
[x] No new warnings are generated

Test coverage

[x] Existing tests pass
[ ] New code is covered by passing tests

Merged with #1540


chore: add custom eslint plugin to prevent translation variables

SUMMARY

Since flask-babel is a static translation translation service, it can’t handle strings that include variables.(refer to https://github.com/apache/superset/pull/19641). This PR adds a custom eslint plugin to catch these.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

before

after

TESTING INSTRUCTIONS

Test Rule
cd superset-frontend
npm run test ./tools/eslint-plugin-translation-vars

Lint
npm run _lint

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

cc @villebro @zhaoyongjie @geido

Nice work @stephenLYZ ! ❤


Get rid of absolute versions for Dockerfiles

The Dockerfiles break regularly because of distros releasing patches for ZSH and it seems to be impossible to install a fuzzy version of ZSH (like 5.6.2-*) with apt-get. This PR switches to apt that has that ability.
//cc @Syphdias

Looks good to me. Though I cannot speak for 4.3.11 since the centos image thows a segvault on running yum, bash or sh (dash works). I think that's a local problem with my machine.

Currently the centos:6 image seems to be broken (also for a colleague). The centos:7 image works.

Hmm. What exactly do you mean by saying the image is "broken"? Is it not possible to start the docker container? Or is just P9K broken inside the container? Thinking about it, that is only there because of historical reasons. Our new minimum system requirement is ZSH 5.1..

As I said, I (and my colleague) get segfaults for starting various programs inside the container. We both use Debian (different version I think).
And since I can run the version with the label 7 from dockerhub. I assume the latest image from dockerub is faulty. Could be my system though.
 ❱ docker run --rm -it centos:7 /bin/bash
[root@3c19cabe14ad /]# ^C
[root@3c19cabe14ad /]# exit
^[[A%                                                                                chkugler@biscuittin:~% docker run --rm -it centos:6 /bin/bash
chkugler@biscuittin:~% echo $?
139
 ❱ docker run --rm -it centos:6 /bin/dash
# yum
Segmentation fault (core dumped)
# echo $?
139
# /bin/bash
Segmentation fault (core dumped)
# echo $?
139
# %

Ok apparently this is a know bug

Alright. I merged it. Thanks for the review @Syphdias .


Super-linter failed to get the root commit

Is there an existing issue for this?

[X] I have searched the existing issues

Are you using the latest Super-linter version available?

[X] I am using the latest Super-linter version.

[X] I can reproduce the issue running Super-linter using complete version identifier (example: vX.Y.Z), and not just with a partial one (example: vX)

[X] I am using the super-linter/super-linter action or container image, and not the deprecated github/super-linter action or container image.

Are you resonably sure that it's a Super-linter issue, and not an issue related to a tool that Super-linter runs?

[X] I think that this is a Super-linter issue.

Current Behavior
When we upgrade Super-linter with a version > 6.4 with goreleaser the action failed
We have test to disable Goreleaser with env var
VALIDATE_GO_RELEASER: false
Expected Behavior
Pipeline failed whit goreleaser.
Super-Linter version
v6.4.x
v7

Super-linter configuration
- name: Checkout code
        uses: actions/checkout@v4
        with:
          ref: ${{ github.event.pull_request.head.ref }}
          # Full git history is needed to get a proper list of changed files within `super-linter`
          fetch-depth: 0

      - name: Lint Code Base
        uses: super-linter/super-linter@v7
        env:
          VALIDATE_ALL_CODEBASE: false
          VALIDATE_CHECKOV: false
          VALIDATE_TERRAFORM_TERRASCAN: false
          VALIDATE_GO_RELEASER: false
          DEFAULT_BRANCH: ${{ inputs.default_branch }}
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          KUBERNETES_KUBECONFORM_OPTIONS: "-schema-location default -schema-location 'https://raw.githubusercontent.com/datreeio/CRDs-catalog/main/{{.Group}}/{{.ResourceKind}}_{{.ResourceAPIVersion}}.json' -ignore-filename-pattern '.*/helm/.*.yaml' -ignore-filename-pattern 'charts/.*.yaml'"

Relevant log output
Super-Linter initialization
  2024-09-03 08:19:09 [INFO]   --------------------------------------------------------------------------------
                                /@@#///////@@/(@//@%/(@.@(       @@
                            @@//////////////////////////////#*  @@@
                          @////@//(///////////@@@@@///@//@/@**//@@(
                        @///////@///////////////@@@@    (           @,
                       @/(&/@////////////////////                     @
                      @////////////////////////@@                      @
                    @%////////(//////////%/////&@            @@       *,@           ______________
               @@@@@/@/#/////(&//////////////////                       .@         /              \
          *@@@@@.    .%///(//@//////////////////&.   .@@,                 @%      / Don't mind me  \
        @@%           .&@&&/@.@//&/////(//////////    @@@@@@@@@         .. &@    / I'm just looking \
      @@%               @@@@@   @&/////////////////#   @/       V  @@/ ,@@@ @   <  for some trash... |
  @@@%                   @@@@        .%@@@@//////#@ @   @@         @     .,.     \__________________/
                                            @@@/@(  (@@@@% @/\      %
                                             @@@@(    .     .@@/\   #
                                               @                  %@%
  --------------------------------------------------------------------------------
  2024-09-03 08:19:09 [INFO]   ---------------------------------------------
  2024-09-03 08:19:09 [INFO]   --- GitHub Actions Multi Language Linter ----
  2024-09-03 08:19:09 [INFO]    - Image Creation Date: 2024-08-28T09:30:09Z
  2024-09-03 08:19:09 [INFO]    - Image Revision: b92721f792f381cedc002ecdbb9847a15ece5bb8
  2024-09-03 08:19:09 [INFO]    - Image Version: 7.1.0
  2024-09-03 08:19:09 [INFO]   ---------------------------------------------
  2024-09-03 08:19:09 [INFO]   ---------------------------------------------
  2024-09-03 08:19:09 [INFO]   The Super-Linter source code can be found at:
  2024-09-03 08:19:09 [INFO]    - https://github.com/super-linter/super-linter
  2024-09-03 08:19:09 [INFO]   ---------------------------------------------
  2024-09-03 08:19:09 [INFO]   - Validating changed files in code base...
  2024-09-03 08:19:09 [INFO]   dotnet: 8.0.401
  chktex: chktex: WARNING -- Could not find global resource file.
  ChkTeX v1.7.9 - Copyright 1995-96 Jens T. Berger Thielemann.
  Compiled with POSIX extended regex support.
  rubocop: 1.65.1
  perl:
  This is perl 5, version 38, subversion 2 (v5.38.2) built for x86_64-linux-thread-multi
  Copyright 1987-2023, Larry Wall
  Perl may be copied only under the terms of either the Artistic License or the
  GNU General Public License, which may be found in the Perl 5 source kit.
  Complete documentation for Perl, including FAQ lists, should be found on
  this system using "man perl" or "perldoc perl".  If you have access to the
  Internet, point your browser at https://www.perl.org/, the Perl Home Page.
  xmllint: xmllint: using libxml version 21207
     compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 HTTP DTDValid HTML C14N Catalog XPath XPointer XInclude Iconv ISO8859X Unicode Regexps Automata Schemas Schematron Modules Debug Zlib Lzma
  ansible-lint: ansible-lint 24.7.0 using ansible-core:2.17.3 ansible-compat:24.8.0 ruamel-yaml:0.18.6 ruamel-yaml-clib:0.2.8
  eslint: v8.57.0
  markdownlint: 0.41.0
  snakefmt: snakefmt, version 0.10.2
  cpplint: Cpplint fork (https://github.com/cpplint/cpplint)
  cpplint 1.6.1
  Python 3.12.5 (main, Aug  7 2024, 19:15:55) [GCC 13.2.1 20240309]
  editorconfig-checker: v3.0.3
  gitleaks: v8.18.4
  phpstan: PHPStan - PHP Static Analysis Tool 1.11.2
  dotenv-linter: dotenv-linter 3.3.0
  asl-validator: 3.8.3
  actionlint: 1.7.1
  installed by building from source
  built with go1.22.3 compiler for linux/amd64
  tekton-lint: 1.1.0
  terrascan: version: v1.19.1
  terraform: Terraform v1.9.5
  on linux_amd64
  2024/08/27 16:15:42 traces export: Post "http:///dev/otel-grpc.sock": http: no Host in request URL
  2024/08/27 16:15:42 traces export: Post "http:///dev/otel-grpc.sock": http: no Host in request URL
  clippy: clippy 0.1.78
  R: R version 4.4.0 (2024-04-24) -- "Puppy Cup"
  Copyright (C) 2024 The R Foundation for Statistical Computing
  Platform: x86_64-pc-linux-musl
  R is free software and comes with ABSOLUTELY NO WARRANTY.
  You are welcome to redistribute it under the terms of the
  GNU General Public License versions 2 or 3.
  For more information about these matters see
  https://www.gnu.org/licenses/.
  rustfmt: rustfmt 1.7.0-stable ( )
  shellcheck: ShellCheck - shell script analysis tool
  version: 0.10.0
  license: GNU General Public License, version 3
  website: https://www.shellcheck.net
  jscpd: 4.0.5
  black: black, 24.8.0 (compiled: no)
  Python (CPython) 3.12.5
  prettier: 3.3.3
  php: PHP 8.3.10 (cli) (built: Aug  1 2024 20:18:40) (NTS)
  Copyright (c) The PHP Group
  Zend Engine v4.3.10, Copyright (c) Zend Technologies
  textlint: v14.2.0
  npm-groovy-lint: GroovyLint: Successfully processed CodeNarc:
  CodeNarc version 3.3.0
  npm-groovy-lint version 14.6.0
  Embeds:
  CodeNarc version 3.3.0
  - Groovy version 3.0.9 (superlite)
  renovate-config-validator: (node:226) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
  (Use `node --trace-deprecation ...` to show where the warning was created)
  38.55.1
  golangci-lint: golangci-lint has version 1.60.3 built with go1.23.0 from c2e095c0 on 2024-08-22T21:51:56Z
  ruff: ruff 0.6.2
  kubeconform: v0.6.7
  golangci-lint: golangci-lint has version 1.60.3 built with go1.23.0 from c2e095c0 on 2024-08-22T21:51:56Z
  gherkin-lint: Version command not supported
  eslint: v8.57.0
  scalafmt: scalafmt 3.8.3
  stylelint: 15.11.0
  sqlfluff: sqlfluff, version 3.1.1
  bash-exec: Version command not supported
  google-java-format: google-java-format: Version 1.23.0
  phpcs: PHP_CodeSniffer version 3.10.1 (stable) by Squiz and PHPCSStandards
  terragrunt: terragrunt version v0.66.9
  psalm: Psalm 5.24.0@462c80e31c34e58cc4f750c656be3927e80e550e
  pylint: pylint 3.2.6
  astroid 3.2.4
  Python 3.12.5 (main, Aug  7 2024, 19:15:55) [GCC 13.2.1 20240309]
  shfmt: v3.9.0
  snakemake: 8.18.2
  arm-ttk: ModuleVersion = 0.25
  pwsh: PowerShell 7.4.2
  mypy: mypy 1.11.2 (compiled: yes)
  eslint: v8.57.0
  coffeelint: 5.2.11
  tflint: TFLint version 0.53.0
  + ruleset.terraform (0.9.1-bundled)
  cfn-lint: cfn-lint 1.10.3
  flake8: 7.1.1 (mccabe: 0.7.0, pycodestyle: 2.12.1, pyflakes: 3.2.0) CPython 3.12.5 on
  Linux
  spectral: 6.11.1
  clj-kondo: clj-kondo v2024.08.01
  eslint: v8.57.0
  ts-standard: 12.0.2
  eslint: v8.57.0
  protolint: protolint version 0.50.5(6cc254e)
  pyink: pyink, 24.3.0 (compiled: no)
  Python (CPython) 3.12.5
  raku: Welcome to Rakudo™ v2024.04.
  Implementing the Raku® Programming Language v6.d.
  Built on MoarVM version 2024.04.
  prettier: 3.3.3
  hadolint: Haskell Dockerfile Linter 2.12.0
  checkstyle: Checkstyle version: 10.18.0
  clang-format: clang-format version 17.0.6 (https://github.com/llvm/llvm-project.git 6009708b4367171ccdbf4b5905cb6a803753fe18)
  ktlint: ktlint version 1.3.1
  yamllint: yamllint 1.35.1
  dart: Dart SDK version: 3.5.1 (stable) (Tue Aug 13 21:02:17 2024 +0000) on "linux_x64"
  isort:
                   _                 _
                  (_) ___  ___  _ __| |_
                  | |/ _/ / _ \/ '__  _/
                  | |\__ \/\_\/| |  | |_
                  |_|\___/\___/\_/   \_/
        isort your imports, so you don't have to.

No response

Hi! This is not about Goreleaser. It just happens to be the last linters that emits its version information, but has nothing to do with the issue you're facing.
The issue is that Git is not able to trace back the root (initial) commit starting from the 2592f4c4edfcfe1e1f9010b82cc0316bbb6f8081 commit in your repository. This command failed on your repository:
https://github.com/super-linter/super-linter/blob/94920ffcc743ebba42205db26cc4bad16f309498/lib/linter.sh#L274-L278

I think what's likely happening here depends on how you're checking out the repository in the Checkout code step.
This is probably a configuration issue, rather than a Super-linter issue.

I think the change that is impacting you is #5534, which landed in v6.4.1, so it matches with your statement about versions < v6.4 working fine.
@jplanckeel-ep In order to understand what's happening here, we need to reproduce the issue first. Can you please provide a link to a workflow with debug logging enabled if this is a public repository? If it's a private repository, we need more help from your side to try to reproduce the issue, so we probably need that that you collect the logs yourself, taking care of redacting private information. We probably need both the actions/checkout log, and the super-linter debug log.

No replies. Closing this. We can reopen later if we get more data points. Thanks for taking the time to file this issue in the first place!

I've also run into the issue described here by @jplanckeel-ep.
I'm currently on v6.4.0 and have had multiple dependabot PRs trying to upgrade super-linter from that version fail with the same output given above.

I definitely might be missing an obvious issue with what I'm doing but I'm not very well versed in this side of things so nothing is sticking out to me.
This is my workflow step for checking out the code:
- name: Checkout code
        uses: actions/checkout@v4
        with:
          # Full git history is needed to get a proper list of changed files within `super-linter`
          fetch-depth: 0

          # Checkout the code from the pull request instead of the merge commit
          ref: ${{ github.event.pull_request.head.sha }}

This is my configuration for super-linter:
- name: Run super-linter
        uses<EMAIL_ADDRESS>        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

          # Only run on changed files
          VALIDATE_ALL_CODEBASE: false
          LINTER_RULES_PATH: .

          LOG_LEVEL: INFO

          JAVASCRIPT_DEFAULT_STYLE: prettier
          JAVASCRIPT_ES_CONFIG_FILE: .eslintrc.json

          TYPESCRIPT_DEFAULT_STYLE: prettier
          TYPESCRIPT_ES_CONFIG_FILE: .eslintrc.json

          # Explicitly state filetypes to validate (those not included will not be linted)
          VALIDATE_BASH: true
          VALIDATE_DOCKERFILE_HADOLINT: true
          VALIDATE_GITHUB_ACTIONS: true
          VALIDATE_GITLEAKS: true
          VALIDATE_HTML: true
          VALIDATE_JAVASCRIPT_ES: true
          VALIDATE_JSX: true
          VALIDATE_TSX: true
          VALIDATE_TYPESCRIPT_ES: true
          VALIDATE_YAML: true

I'll also try to provide the debug log if I can't figure it out.

Hello, i want open this issue, sorry for the delay.
Is private repo, we use dependabot like @nartb, i will check debug log


Init Resources Page

Ref https://github.com/babel/babel.github.io/issues/27
From @thejameskyle (looks awesome?)

:o Looks awesome!

I know! - was looking at an old branch (2yrs ago)
I think we should definetely do it - maybe update the links

Yeah, this is still a good idea I think. Just going to take a lot of maintenance


Add dynamic vagrant hosts file

Hallo Bert,
BTW your project is a great idea.
I add the possibility to used custom vagrant-hosts files, so i must not clone that project and delete the .git directory. I can hold the structure of the project.
I'm add the sample script custom-vagrant-host.yaml and add a description in the README.md  file.
I fix same github markdown issue follow these rules https://github.com/DavidAnson/markdownlint/blob/v0.6.4/doc/Rules.md
Mathias

@MathiasStadler Where @bertvv has $ git, he is correct. Most unix users understand that $ is a non-privliged user whereas # git would indicate a privileged user such as root in this instance.
It's a nuance and shouldn't really matter. Just an FYI.

Thanks, I like this PR! However, you forgot to add your name to the contributors... :-) If you do, I'll do the merge.
I always use $ or # as prompt just like @reavon mentions, but I don't really have an Opinion about this, so your proposed change is fine by me.
Thank you very much for your contribution!

@bertvv Just found your blog post which led me here. I must say fantastic work, thank you. I currently have a lot of vagrant files that I was using environment variables to select the correct one when I did vagrant up.
This also means I have a lot of different environments I am creating and this PR was the first thing that came to mind so thank you @MathiasStadler.

Hey @MathiasStadler, sorry it took so long to merge your PR! Thank you @garfieldcoked for the comment, that reminded me...


Port Change Needed after Vizio Firmware Update

Vizio released software update <IP_ADDRESS> recently, and changed the port used to communicate with the TV from port 9000 to port 7345.
Using Port 9000 would result in errors similar to this pairing error: ERROR:pyvizio.vizio:Failed to execute command: HTTPSConnectionPool(host='[TV IP Address', port=9000): Max retries exceeded with url: /pairing/start (Caused by SSLError(SSLError(1, '[SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:777)'),))
Changing to Port 7345 in protocol.py resolved the error.

Where is protocol.py? I tried searching around but am having no luck to edit it.

I found the path by running pip show pyvizio (or pip3 ...) - see the Location property and it should be in the pyvizio folder (see line 112, of invoke_api, in protocol.py).

@trowhite I didn't figure it out, but found the solution here: https://github.com/exiva/Vizio_SmartCast_API/issues/15#issuecomment-377067804


[opt_ctrl,dv] Fix types in otp_ctrl_scoreboard.sv

This fixes a silly typo in the definition of a "check_timout" variable. In particular, simulators like Xcelium don't allow a variable to be declared like "bit [123] foo". The correct syntax would be packed dimensions like "bit [123:0] foo".
However, there's a reasonably obvious simpler fix, so I switched things to just using an integer. In the original code, a value of 0 was overridden with '1 (which was 2**32 with this type). Leaving it as zero (which already means "no timeout" for set_exp_alert) seems to work perfectly well.
As a minor nit, I also changed the variable name. Timeout now contains an "e"!

Ha, it turns out that @msfschaffner has done this in the time it took to get this merged. This is fixed in #20906 (and my other little tweaks don't really matter).
That'll teach me to put a bit more effort into getting things merged :-D


Stop duplicating the postal code prefix in the format

If the postal code prefix is already declared ("postprefix"), there is no need to also have it in the format string ("fmt").
Postal code prefixes are usually appended only for international mail, so not having the prefix in the format string would allow a formatter to choose when to add the prefix (for international, but not domestic sending, etc).

When you say "formatter", what are you using to format?   Are you using getFullEnvelopeAddress within the Android widget?


Allow to call npm install --ignore-scripts instead of npm install

By the installation the ioBroker.vis calls special post-install script to generate the HTML files.
For that the ioBroker.js-controller is required.
By preparation with the "release-script" of course no js-controller is present.
My suggestion is to extend .releaseconfig.json with attribute: "ignore-scripts": true and in this case the call here will be modified: https://github.com/AlCalzone/release-script/blob/master/src/release.ts#L520
Or to use attribute "install-args": ["--ignore-scripts"] so it will be more flexible.

That step is mainly meant to bring package-lock.json and package.json in sync. I could also add an option to skip this step entirely - what do you prefer?

ioBroker.vis doesn't have a lockfile, so the lockfile sync step isn't needed. You should be able to do this in v3.0.0 using this option: https://github.com/AlCalzone/release-script#dont-synchronize-the-lockfile---no-update-lockfile

Thank you!


Add test for "ghost" file

Minimal test to demonstrate "ghost" file issue.

Addressed in https://github.com/awslabs/mountpoint-s3/pull/216


ADD:SSV-Prysm

Please approve https://github.com/stereum-dev/ethereum-node/pull/63 first to get the existing ssv tests successful again. Then we review this one and adapt it if needed.


BetterDiscord Server

I'm not sure whats going on, (maybe it has too many members??) but when I try to join the BetterDiscord server for themes and such it doesn't join and just loads for 20sec before displaying no channels and no selected server? is the server bugged, or something I did wrong along the steps of installing?

The server is just full, you'll have to wait for a spot to open up. If you want to browse plugins and themes get the PluginRepo and ThemeRepo plugins from here https://github.com/mwittrien/BetterDiscordAddons/tree/master/Plugins
It will add buttons to the plugin and theme pages (at the top) so you can browse them without being in the server.


Add support for custom conditions on task groups

Currently, individual tasks can be assigned a custom condition. Task groups don't have that capability though.

Yeah, it's in the works.  It's not a task issue but a service side issue.  task group support is coming soon (the main issue is the task group UI is still using the old editor)

👍 on this.. any news @bryanmacfarlane ?

@rmarinho I just came to the conclusion that I need this and I need it now. After observing @bryanmacfarlane's comment I realized that if we set the condition to a task and then create a task group from that task, the condition will still be set, just not visible until they deploy the new UI. I just tried it and it works. 🥇

Yep, indeed. I found this out by coincidence.

Any ETA for this release?

If someone else is looking for a workaround: using the dev chrome tools, search for .prototype.beginUpdateTaskGroup in MS's code. In there, the variable t contains the JSON object sent to the REST endpoint. You can set a breakpoint beforehand and modify it as required.

@jstawski - see the comment that went along with closing it.

@bryanmacfarlane Is there a publicly tracked issue for migrating Task Groups to the new UI?

I'm not sure if this merits a new bug or not, but here some feedback. As of today, it seems the only way to add a variable into a task group is to reference one in one of the tasks. That is problematic if the variable is only used on the custom condition as it is not being checked. I had to resolve by using a dummy task and reference the variable there, but it truly shouldn't be like that. Either add support to check for new variables on the custom condition or the ability to manually add a variable.
For others that might run into this problem:
My dummy condition is a Command Line task:
Tool: echo
Arguments: "$(VariableName)"

Yes, not usable if the variable is only used on the custom condition.

@bryanmacfarlane This still does not seem to be implemented

@bansalaseem for task group question.

Since this is a service side issue, developer community would be a better channel.  That's the only publicly tracking mechanism for the service.

Thanks @jstawski for the feedback. Right now the workaround which you have done looks reasonable and we have a story in our backlog to manually specify a task group variable. I dont have a specific timeline when we will get to it though.

Yeah, it's in the works. It's not a task issue but a service side issue. task group support is coming soon (the main issue is the task group UI is still using the old editor)

We are using TFS 2018 Update 2. There is still no option to add a condition to the Task Group!
I want to NOT RUN the entire task group, based on a single condition. Seems overkill to introduce a variable in one of the underlying tasks and then add a custom run condition on each of the tasks with the group. That's just really silly!
So why is this issue closed? There is a valid use case for having a custom run condition on the task group itself.

Is there an update on this? I have the same requirement as AroglDarthu. I am using Azure DevOps and see no option to control execution of task group apart from hacky solution!

Are you planning to enable Custom Conditions on task groups any time soon?
The initial request was from Aug 2017.

Came here looking for this, almost 2 years later. Any updates?

Following on from my message above; the way that I ended up solving this was using separate Agent Phases and putting the task group into an Agent Phase that I've set up with execution conditions. If you do use this path, make sure you set the Dependencies on each phase so that it only runs if previous phases have been completed.

Due to few other priority items like pipelines YAML, we couldn't find bandwidth to work on this feature. As of now the backlog for the next 2 months is full. We will try to pick up task group conditions feature after that. Will keep you posted.

Please add this. I need this to be able to run Task Groups in parallel using "multi-configuration".
For the impatient ones: I've found a sick workaround:

take your Task Group and add a dummy task to print two vars (this is just to make the vars appear on Task Group variable list).  Eg:
Inline Powershell: Write-Host("$(selector) $(staticselector)")

specify Custom Condition on ALL tasks in the Task Group to:
and(succeeded(), eq(variables['selector'], variables['staticselector']))

Add $selector variable to your release, set to a multi-configuration CSV string, eg:  "thread_one,thread_two,thread_three"

add your Task Group three times to a Multi-Configuration Agent Job. For each one, set:
$selector to $(selector)
$staticselector to one of the CSV values, eg "thread_one" for the first instance, "thread_two" for the second and "thread_three" for the third

Profit!  Each multi-configuration job runs a separate thread of your Task Group with thread-specific parameters

Another vote for this.

+1 !

+1

Attached link to related Developer community issue - since it would be better place to get last updates about it's status.

@anatolybolshakov: Are you or anybody else from the team able to get some more information about this issue? It is 5 years since this issue was posted and two years since the last comment. In the related Developer community issue you link to there has been no official answer/activity for years 😞

typical microsoft product tbh. introduce a new feature that's somewhat useful. spend the extra sprint or two to make it really useful? no sorry...

+1 on this please, it has been almost 6 years now since we asked for this simple feature.

Adding another request for this. I'm not getting my hopes up but man it would be nice to have this, we have to do some janky workarounds until this exists.

+1

+1


Demo of a single image

Thanks for you fantastic work!
Could you please provide the code for generating the mask for a single image?

hi did you solve the problem?


[Feature] Sparse_ init

Request to add Sparse_ initialization similar to https://pytorch.org/docs/stable/nn.init.html#torch.nn.init.dirac_. I have gone through the official documentation of MLX but couldn't find the above initialization method. I think it would be a good addition to MLX.

@awni May I know if the above has an update?

We could put that initialization in our init package. I'll mark this as a feature request. Just curious, what do you intend to use it for?

@awni We were experimenting with different initialization techniques and figured out that sparse init is not implemented. I think it  can be a good enhancement feature.

The PR is merged and hence closing the issue.


In VMware win10 virtual machine, there are white line on the top

And examples running in VMware without display UI, the process running in the background


Enforcement of the coding conventions

The coding conventions are described here: https://kb.zubax.com/x/84Ah
The existing codebase has certain deviations which should be fixed in the rewrite; the two things that come to mind are the capitalization rules (CANFrame is correct, CanFrame is not) and reliance on the native types (std::uint32_t is safe to use, unsigned is not). Also, a lot of useless stuff can be safely thrown out now since we have agreed to abandon support for C++03.
We need some tool for enforcement of MISRA C++ rules. I Googled around a bit and found nothing except SciTools Understand, which I have a bit of experience with: https://scitools.com/features. Back in 2014 they offered a free license for open source projects, not sure if they still do. While the tool generally worked for me, it was rather unreliable and tended to produce nonsensical reports, especially when dealing with heavily templated code which libuavcan has much of. Seeing as we have no other options so far, we should probably give it a try.
Besides MISRA, we could well use more static analysis in general. We currently have Coverity Scan; perhaps we should also consider using the Clang Static Analyzer, which I heard good things of but never used myself.

@thirtytwobits SciTools bestowed one free license upon us. It is valid for one year, can be freely renewed afterward.
I asked them whether it is possible to set up their tool in a headless mode in a CI environment, but they ignored this question twice, so I take it as a "no".

This task has become a bit too non-specific for v1. We now have enforcement of style and Issue #226 covers integrating clang-tidy but we do lack MISRA and/or HIC++ enforcement. Can I change this to read "Choose and enforce a C++ standard for safety critical software"?

I think I might have found just what we need. SonarQube has a cloud-based static analysis service named SonarCloud which is free for open source projects, and it supports a reasonable subset of MISRA (https://rules.sonarsource.com/cpp/tag/misra, https://rules.sonarsource.com/cpp/tag/misra-c++2008) among other rules. I have set it up for the new PyUAVCAN rewrite which is my first ever encounter with this service; currently I can't vouch for its C++ side so we need to try it. The list of rules at least looks very promising.
There is also Coverity Scan, which AFAIK does not offer MISRA checks in its free version but its in-depth control flow analysis has proven to be generally useful in the past (we're using it for one project internally). I am not sure, however, how does it compare against clang-tidy; experimentation might show that once we've set up the latter Coverity might become redundant.
I believe you have already taken care of the coding style enforcement with clang-format so that is a non-issue anymore.
Per the MISRA usage guide we need to set up a dedicated requirement document containing a list of rules from all applicable coding standards (such as MISRA or HIC++) with an explicit list of tools per rule that enforce it (which would be (so far) SonarQube, Coverity, clang-tidy, clang-format). Would you consider adding that to the libuavcan docs?

Integration examples for clang-tidy, clang-format, and SonarQube with MISRA enforcement are available in https://github.com/pavel-kirienko/o1heap. The coverage measurement is quite flaky but it's a different beast and I think it's solved here properly already.

Seeing as SonarQube is set up, I suggest we split this issue into two new ones:
1. Enable MISRA checks in SonarQube
A large subset is supported and can be enforced using SonarQube:

2. Set up Clang-Tidy


stream audio and video from RTSP source

Hi
I am using amazon-kinesis-video-streams-producer-sdk-cpp, tying to play audio+video data directly from RTSP source.
While playing RTSP URL in VLC, able to get audio+video.
Using same RTSPsrc, what changes are required to get audio data over Kinesis server. can anyone please check.
Note : I have added below changes
Replaced DEFAULT_CONTENT_TYPE "video/h264" macro with "video/h264,audio/aac"
Added separate Track and pipeline for audio.
Getting below messages contentiously while playing the stream.
[WARN ] [03-02-2022 14:34:21:371.218 GMT] putKinesisVideoFrame(): Failed to submit frame to Kinesis Video client. status: 0x52000085 decoding timestamp: 32778115 presentation timestamp:<PHONE_NUMBER>5499550
0:00:03.307935980 1900668 0x7f788001c360 WARN            rtpmp4gdepay gstrtpmp4gdepay.c:684:gst_rtp_mp4g_depay_process:<depay_audio> Detected ADTS header of 7 bytes, skipping
[WARN ] [03-02-2022 14:34:21:387.127 GMT] putKinesisVideoFrame(): Failed to submit frame to Kinesis Video client. status: 0x52000085 decoding timestamp: 32933862 presentation timestamp:<PHONE_NUMBER>5385407
[WARN ] [03-02-2022 14:34:21:441.332 GMT] putKinesisVideoFrame(): Failed to submit frame to Kinesis Video client. status: 0x52000085 decoding timestamp: 33480239 presentation timestamp:<PHONE_NUMBER>5692921
0:00:03.375690568 1900668 0x7f788001c360 WARN            rtpmp4gdepay gstrtpmp4gdepay.c:684:gst_rtp_mp4g_depay_process:<depay_audio> Detected ADTS header of 7 bytes, skipping

Hi @Heena2411, there seems to be an issue with your decoding and presentation timestamps. The error code 0x52000085 indicates STATUS_MAX_FRAME_TIMESTAMP_DELTA_BETWEEN_TRACKS_EXCEEDED. Please refer to how the timestamps are set in the samples to fix this.
Closing assuming answered, feel free to reopen in case of further questions/issues


Full review / update required for Data Classification page

This article is 3 years old and naturally drifted away from service behaviour.
Some items that require an update:

Screenshots to match new workspace experience and other changes to Power BI service UI
Elements documented that do not work the same way in service. Example: https://github.com/MicrosoftDocs/powerbi-docs/issues/2443

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

ID: 460b9768-213a-bd8b-5ad8-ed5071848a98
Version Independent ID: 24bdc0f5-a172-0d0b-02b2-ff798ccd96cf
Content: Dashboard data classification - Power BI
Content Source: powerbi-docs/create-reports/service-data-classification.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thanks, @VitalyMCT - I've assigned this issue to the author to review for accuracy and make an update. I appreciate you flagging this for us.

Hi @VitalyMCT, this type of data classification was discontinued some time ago and this article was removed, redirecting users to the sensitivity label documentation. Closing this issue now. Sorry for the long overdue notice...


Cound you please support ClipOval() and Timer.

please support ClipOval() and Timer . Thank you very much

Support for Timer added in dart_eval v0.7.9


Violations in generated region are not ignored

Hello,
Few years ago, with StyleCop classic, we used the trick #3 described there : https://sethflowers.com/blog/force-stylecop-to-ignore-a-file/
We put many regions like this in our code :
#region Component Designer generated code
StyleCop classic was ignoring all violations inside those regions.
We just tried to upgrade to StyleCop.Analyzer and see that violations in those regions are raised instead of being ignored.
Is there a way to match previous behavior by some options somewhere ? Is this a bug ?
Thanks

StyleCop Analyzers uses Roslyn for all warning suppressions, and the analyzer driver don't consider those region directives. You should be able to use option 2 instead.

I moved the concerned code to the designer file to solve this issue. Thanks


Inaccurate drivable area in dynamic_obstacle_avoidance

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
When the dynamic_obstacle_avoidance module is enabled and the EGO vehicle attempts to avoid an oncoming dynamic object, the process of cutting the drivable area is not performed correctly. As a result, the drivable area appears as shown below.
https://github.com/autowarefoundation/autoware.universe/assets/32412808/09e4785e-ef10-4946-984f-2993a63d92ea
Expected behavior
The dynamic object needs to be correctly cut from the drivable area, and the drivable area should appear as shown below.

Actual behavior
The dynamic object is not being correctly cut from the drivable area, and the drivable area appears as shown below.

Steps to reproduce

run plan_sim
map: LEO-VM-00038.zip
add a dynamic object

Versions
Possible causes
The algorithm for cutting the object from the drivable area needs to be improved.
Additional context

The issue here is not the incorrect creation of the input path, but rather that the drivable area bounds are not being generated properly in the tier4_planning_plugin:

Drivable bounds from behavior_path_planner:

https://github.com/autowarefoundation/autoware.universe/assets/32412808/d0c7f3bf-3831-41c9-8a54-70fa969a75d1

Drivable bounds from behavior_velocity_planner:

https://github.com/autowarefoundation/autoware.universe/assets/32412808/87d408e8-f251-43ed-a6c9-31bf25acb24a

Drivable bounds from tier4_planning_plugin:

https://github.com/autowarefoundation/autoware.universe/assets/32412808/6e351e51-8cdd-4309-ab84-baf3195ed74b
When I publish the drivable area bounds myself using a publisher, everything looks correct. However, when the same topic is visualized with the tier4_planning_plugin, the strange situation described above occurs.


Test simulator

Use data from other teams and see how their flights went, compare to what this sim predicts

https://github.com/ISSUIUC/flight-data/tree/master

https://github.com/catsystems/euroc21-team-data

Use Cds from here and sim that, compare to both the RocketPy and their experimental (both very similar):
https://github.com/RocketPy-Team/RocketPy/blob/master/docs/examples/ndrt_2020_flight_sim.ipynb
https://github.com/RocketPy-Team/RocketPy/blob/master/docs/examples/valetudo_flight_sim.ipynb
https://github.com/RocketPy-Team/RocketPy/tree/master/tests/fixtures/acceptance/PJ_Valetudo
https://github.com/RocketPy-Team/RocketPy/blob/master/docs/examples/juno3_flight_sim.ipynb
https://github.com/RocketPy-Team/RocketPy/tree/master/data/juno3
https://github.com/RocketPy-Team/RocketPy/blob/master/docs/examples/bella_lui_flight_sim.ipynb

It would be good to do more later, but it looks fantastic so far


Nest neighborhoods under boros in table

Basically copying oldportal design. Makes the table more usable, I think.

Is this mostly done via the datatables spec?


Rename MsgPruneAcknowledgements

Ideally something along the lines of MsgPruneStalePacketState? Can be done in #5444 if people prefer or afterwards with a quick PR.

@DimitrisJim can I work on this issue?

Thank you for offering to work on this issue, @chandiniv1. We are a bit on a hurry to get the prune acknowledgement functionality in, so I am just going to do this my self now.

Done here.


feat: allow configuring the hostNetwork variable (#1577)

Reason for Change:

1577, allow configuration of the hostNetwork option.

Requirements

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

Issue Fixed:

Fixes #1577
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:

@aramase @nilekhc ping


NoClassDefFoundError sometimes

Issue from https://github.com/orfjackal/retrolambda/issues/37

Here is a assumption why this fails (still the reproduction is random here). The compileFlavorBuildJava happens before the compileRetrolambdaFlavorBuild.
:mobile:compileDevelopDebugJava
:mobile:_compileDevelopDebugJava
:mobile:compileRetrolambdaDevelopDebug

If I turn proguard "on" then assuming the build is affected by this bug the :mobile:compileDevelopDebugJava will fail without this plugin had the chance to build the lambdas and make the conversions.
PS: gradle:1.1.3

For workaround after it happens, rm -rf ./app/build/intermediates/classes and assembleFlavorBuild will fix the error.

It does not happen when incremental false.

I'm still seeing this after bumping plugin version to 3.2.3 and cleaning my project. Tried manually deleting build/ folder. What can be the case?

I get good results for months by adding
classpath 'me.tatarka.retrolambda.projectlombok:lombok.ast:0.2.3.a2'
but still see the lint issue without this.
Is there a reason that fix isn't yet merged back into the canonical branch?

The fix for this bug was merged directly to the master branch and was released in 3.2.2.
I upgraded to that version of the plugin and removed the incremental false workaround mentioned above — I haven't experienced this bug since then.
Nobody else has mentioned Lint here — are you talking about a different issue to this one, which relates to NoClassDefFoundErrors?


[GoogleSearchBridge] Use search result timestamps as item timestamps

Updates bridge to use each search result's timestamp as item timestamp when available. Closes #1865

@VerifiedJoseph looks like you missed my statement:

Could you please tell me, on which cases those timestamps appear?

Also I miss-typed other statement. By telling this

Note timestamps found here:

I actually meant "None timestamps found here".
Anyway, maybe @kmizeta knows those cases?

According to the docs for strtotime() the function only works with "English textual datetime", which would explain why its not working for you, @em92.

@VerifiedJoseph looks like you missed my statement:

Could you please tell me, on which cases those timestamps appear?

Also I miss-typed other statement. By telling this

Note timestamps found here:

I actually meant "None timestamps found here".
Anyway, maybe @kmizeta knows those cases?

hi!
it's no so simple because Google "datetime" response for any item depends from where (your geoip I think) you are making the request. So, for my purposes I'm making requests from a country that speaks spanish, and the dates are in this format:
dd month yyyy (with month in spanish).
I've already modified the original code to adapt to spanish responses:
public function collectData(){
$html = '';
            $html = getSimpleHTMLDOM($this->getURI())
                    or returnServerError('No results for this query.');

            $emIsRes = $html->find('div[id=res]', 0);

            if(!is_null($emIsRes)) {
                    foreach($emIsRes->find('div[class=g]') as $element) {
                            if($element->find('span[class=f]',0)->plaintext=="") break;

                            $item = array();

                            $t = $element->find('a[href]', 0)->href;
                            $z = $this->getGooglets($element->find('span[class=f]',0)->plaintext);
                            $item['uri'] = htmlspecialchars_decode($t);
                            $item['title'] = $element->find('h3', 0)->plaintext;
                            $item['content'] = $element->find('span[class=aCOpRe]', 0)->plaintext;
                            #$item['timestamp'] = strtotime('2020-11-29 00:00:00');
                            $item['timestamp'] = $z;
                            $this->items[] = $item;
                    }
            }
    }

public function getGooglets($s){
$mes = array(1=>'ene.',2=>'feb.',3=>'mar.',4=>'abr.',5=>'may.',
6=>'jun.',7=>'jul.',8=>'ago.',9=>'sep.',10=>'oct.',11=>'nov.',12=>'dic.');
$x = explode(" ",$s);
if($x[0]=='hace'){
$tipo = substr($x[2],0,1);
switch($tipo) {
case "h":
$t = mktime(date("H")-$x[1],date("i"),0,date("m"),date("d"),date("Y"));
break;
case "m":
$t = mktime(date("H"),date("i")-$x[1],0,date("m"),date("d"),date("Y"));
break;
case "d":
$t = mktime(12,0,0,date("m"),date("d")-$x[1],date("Y"));
break;
default:
$t = mktime(date("H"),date("i"),0,date("m"),date("d"),date("Y"));
}
            }
            else {
                    $m = array_search($x[1],$mes);
                    $t = mktime(12,0,0,$m,$x[0],$x[2]);
            }

            return $t;

    }

Doesn't work. Unable to find the <span>.

Things that work well now:

It grabs all the results
It grabs all the text from the results

Things that are janky:

The timestamp needs more analysis. Some results contain "x days ago", some do "x hours ago". Sometimes it correctly assumes the timestamp from that, sometimes it doesnt. Maybe the extra code isnt nescessary.
Prevent debug notices, setup some isset statements maybe. The google results also show things like PDF files etc so its not 100% clear.

I think it's good enough for now. It un-breaks the current bridge and can be improved on later.


added first DBConnector as well as an example

The package DBConnector has been added in it's first "complete" state, as well as an example
documentation still needed.

Did you intend to open this as a PR?

as I understood the:
https://github.com/ponylang/ponyc/blob/master/CONTRIBUTING.md#how-to-contribute
this was what I had to do to publish the package to pony
is there anything wrong with this?

just found out, I should probably had placed src/DBConnector and the package file in packages/DBConnector instead
also made a version with documentation comments.

I don’t think this is ready to be accepted. I’d suggest this going through the RFC process. There’s no tests. It’s named DBConnector but uses Postgres specific code. I’m not sure a database specific adapter is appropriate for the standard library.

That said, I appreciate the enthusiasm and desire to contribute.

@GameEngine1 Thanks for this contribution!
As @SeanTAllen pointed out, it is somewhat misplaced. Please open an issue for an RFC here: https://github.com/ponylang/rfcs or maybe even create your first RFC. We are glad to help you out on this, discussing your ideas in an issue in the https://github.com/ponylang/rfcs repository.
I will close this one and hope, we continue this as an RFC as a database connectivity layer is much appreciated.


Fix wasm example

Close #133 by adding compiler flags

Thank you! There are also the zigbee and wgpu examples, which are actually better examples. I'll try to overhaul this example as well, getting rid of the node dependency and Makefile.

Thank you, I will check these out, as well.
Is there any workaround for the missing throttle block on wasm? My impression is that the wasm examples either terminate after N samples or use an actual SDR with a limited data rate.
(Opened a discussion topic to gather some ideas for porting it here, for reference: https://github.com/FutureSDR/FutureSDR/discussions/134)


Add Owners to Site

Step 5:  Add a link to Explore the Site in the Share message, and then click Share. - the link in Explore the Site https://docs.microsoft.com/en-us/Office365/CustomLearning/custom_explore gives a 404 not found.

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

ID: c1c36be4-dad8-cd58-8f1c-b4fa9150b79f
Version Independent ID: 509c4fe6-99fe-906c-bf6a-a3544c807fc9
Content: Provision the Custom Learning site
Content Source: CustomLearning/custom_provision.md
GitHub Login: @pkrebs
Microsoft Alias: pkrebs

Fixed
https://github.com/MicrosoftDocs/OfficeDocs-CustomLearning/blob/public/CustomLearning/custom_provision.md


Should automatically memoize getters.

There is no reason why getters shouldn't automatically be memoized (with allowing opt-out if necessary)
As they tend to be providing some logic to the returned value, like a filter or a map/reduce.

There are many reasons for using getters.  While one of them is to compute derived values and another is simply to expose properties that are private.  In my experience a very few number of getters (even those providing derived values) actually benefit from memoization.  There is some overhead in setting up an observer mechanism for getters and I would prefer not to impose that by default.


Update winapi

Updates winapi to version 0.3.
Removes user32-sys, kernel32-sys and gdi32-sys, they are no longer needed, because they are provided by winapi-rs.
Also removed star glob imports, some of the imported symbols are quite generic and this way it is also more consistent with the rest of the code.
Closes #53

Looks good! Thanks.


Binary caching with AWS fails with message: Could not fetch aws

Describe the bug
I am trying to set up binary caching with AWS S3. The vcpkg install step fails with:
Attempting to fetch 1 package(s) from AWS
[DEBUG] Found path: /usr/bin/aws
[DEBUG] 1004: popen( /usr/bin/aws --version 2>&1)
[DEBUG] 1004: cmd_execute_and_stream_data() returned 0 after   238149 us
error: Could not fetch aws. You may be able to install this tool via your system package manager.
note: updating vcpkg by rerunning bootstrap-vcpkg may resolve this failure.

(an entire debug log attached below)
However, I do have aws CLI installed in my system at /usr/bin/aws. When looking into the debug log, I can see that vcpkg tries to popen the correct /usr/bin/aws and returns code 0.
Running /usr/bin/aws --version 2>&1 manually does run successfully and returns exit code 0:
~$ /usr/bin/aws --version 2>&1
aws-cli/1.27.89 Python/3.10.10 Linux/6.1.25-1-MANJARO botocore/1.29.84

I do have the correct AWS credentials (with AmazonS3FullAccess) and I am able to list bucket, get objects, etc, with the bucket when running /usr/bin/aws from the command line.
The binary caching is configured as:
export VCPKG_BINARY_SOURCES=x-aws,s3://mnovak-vcpkg-test-bucket/vcpkg-cache/,readwrite

The /usr/bin/aws appears as a Python script (this is to be expected):
~$ file /usr/bin/aws
/usr/bin/aws: Python script, ASCII text executable

Environment

vcpkg: 2023-04-07-bedcba5172f5e4b91caac660ab7afe92c27a9895
OS: Linux 6.1.25-1-MANJARO
AWS CLI: aws-cli/1.27.89 Python/3.10.10 Linux/6.1.25-1-MANJARO botocore/1.29.84

The exact same setup was also tried on the ubuntu:22.04 Docker image and it produced the exact same error.
To Reproduce
Steps to reproduce the behavior:

Install the latest vcpkg from the master branch.
Install the latest AWS CLI.

Configure credentials on your system.
Do export VCPKG_BINARY_SOURCES=x-aws,s3://some-s3-bucket-name/vcpkg-cache/,readwrite
Run vcpkg install --triplet x64-linux stb --debug
The command will fail with the message: error: Could not fetch aws.

Expected behavior
Vcpkg will upload the binary cache to the AWS S3 bucket.
Failure logs
failure-vcpkg-aws-s3.log
Additional context
None.

The minimum version you must provide is 2.4.4

Oh! I understand now. Thank you very much.
The error message was a bit confusing. Fixed by installing AWS CLI v2 via sudo pacman -S aws-cli-v2 on Manjaro.


Formatting: Simple multi-error format

The tree output format should be opt-in, and we should default to just empty-line-separated leaf errors.
For leaf errors, multi-error parent just provides an additional piece of the error trace, so there will be some repetition of frames between those errors.
This also ties into #71: we can expose a simple iterator func(error, []frame) with the understanding that parent/child relationships don't need to be exposed.

+1 on formatting customization options.
I'd also like to experiment with an option to deduplicate the error messages in the tree for common uses of errors.Join.

So here's my thinking:
Tree representation is not actually useful.
Nobody wants an ASCII error representation in their error output.
They either want structured information (which is now possible with #102),
or they want simple readable output.
I propose that we change Format and FormatString to do empty-line-separated errors for multi-errors.
So the trace for a single error chain is:
error message

path/to/package.Func
        path/to/file.go:42
path/to/package.Func
        path/to/file.go:42
...

And the trace for a multi-error is:
error message 1

path/to/package.Func
        path/to/file.go:42
path/to/package.Func
        path/to/file.go:42
...

error message 2

path/to/package.Func
        path/to/file.go:42
path/to/package.Func
        path/to/file.go:42
...

...

This matches the simplicity of errors.Join, which does newline-separated messages.
Anything more customizable can be done with UnwrapFrame directly.
If anyone actually finds the tree functionality useful, we can put it in a FormatTree function.
Thoughts?

Example from playing around:
Flat:
std err 1
std err 2
std err 3
std err 4

braces.dev/errtrace_test.Example_tree
        /path/to/errtrace/example_tree_test.go:2

std err 1

std err 2

braces.dev/errtrace_test.wrapNormalErr
        /path/to/errtrace/example_tree_test.go:1

std err 3

std err 4

braces.dev/errtrace_test.wrapNormalErr
        /path/to/errtrace/example_tree_test.go:1

Tree:
+- std err 1
|
+- std err 2
|
|  braces.dev/errtrace_test.wrapNormalErr
|       /path/to/errtrace/example_tree_test.go:1
|
|  +- std err 3
|  |
|  +- std err 4
|  |
|  |  braces.dev/errtrace_test.wrapNormalErr
|  |    /path/to/errtrace/example_tree_test.go:1
|  |
+- std err 3
|  std err 4
|
std err 1
std err 2
std err 3
std err 4

braces.dev/errtrace_test.Example_tree
        /path/to/errtrace/example_tree_test.go:2


[Bug]: Supabase template broken in 4.0.0b302

Description
fresh install of Coolify, trying to spin up a Supabase instance from the template. default settings on everything:
Saved configuration files to /data/coolify/services/zcg0okw. Creating Docker network. Starting service. Pulling images. Non-string key in services.imgproxy.environment: 0
Might add that seems like Supabase hasn't worked correctly for a bit now in general (including port problems as indicated in other issue reports)
Minimal Reproduction (if possible, example repository)
New resource -> Supabase -> Deploy
Exception or Error
No response
Version
4.0.0-beta.302

I am getting a similar error while trying to deploy a minio resource.
Saved configuration files to /data/coolify/services/f8ssgc8.
Creating Docker network.
Starting service.
Pulling images.
Non-string key in services.minio.environment: 0


no function clause matching in Joken.Signer.rs/2

In a  Phoenix App. trying to use Joken.Plug in the router gives me an error at runtime
Request: POST /graphiql
** (exit) an exception was raised:
    ** (FunctionClauseError) no function clause matching in Joken.Signer.rs/2
        lib/joken/signer.ex:78: Joken.Signer.rs("RS256", "my_secret_key")
        (blog_phoenix) web/router.ex:20: BlogPhoenix.Router.verify_function/0
        lib/joken/plug.ex:174: Joken.Plug.parse_auth/2
        (blog_phoenix) web/router.ex:5: BlogPhoenix.Router.graphql/2
        (blog_phoenix) web/router.ex:1: BlogPhoenix.Router.match_route/4
        (blog_phoenix) web/router.ex:1: BlogPhoenix.Router.do_call/2
        (blog_phoenix) lib/blog_phoenix/endpoint.ex:1: BlogPhoenix.Endpoint.phoenix_pipeline/1
        (blog_phoenix) lib/plug/debugger.ex:123: BlogPhoenix.Endpoint."call (overridable 3)"/2
        (blog_phoenix) lib/blog_phoenix/endpoint.ex:1: BlogPhoenix.Endpoint.call/2
        (plug) lib/plug/adapters/cowboy/handler.ex:15: Plug.Adapters.Cowboy.Handler.upgrade/4
        :cowboy_protocol.execute/4

This is the router code:
defmodule BlogPhoenix.Router do
  use Phoenix.Router
  import Joken

  pipeline :graphql do
    plug Joken.Plug, verify: &BlogPhoenix.Router.verify_function/0, on_error: &BlogPhoenix.Router.error_logging/2
    plug BlogPhoenix.Context
  end

  scope "/" do
    pipe_through :graphql

    get "/graphiql", Absinthe.Plug.GraphiQL, schema: BlogPhoenix.Schema
    post "/graphiql", Absinthe.Plug.GraphiQL, schema: BlogPhoenix.Schema
    forward "/graphql", Absinthe.Plug, schema: BlogPhoenix.Schema
  end

  def verify_function() do
    %Joken.Token{}
    |> Joken.with_signer(rs256("my_secret_key"))
  end

  def error_logging(conn, message) do
    IO.puts("got an error")
    {conn, message}
  end
end

I am currently using joken 1.5.0
I cannot seem to see what is wrong as the Joken.Signer.rs convenience function does indeed take 2 parameters

Update. My issue was trying to use a RS256 token which doesnt just work with a string secret. I have changed to use hs256 token
however i still get a "Could not verify token" response even though i have the hs256 secret correct (tested with jwt.io)

Hi @ItsRaWithTheH!
Well, your second issue seems a bit strange... we will need more info to understand why it is failing.
Can you provide us with more info? This message might indicate a claim is not valid.

Yes, I’m sure it would help to provide the JWT, both encoded and unencoded so that people can attept to reproduce your issue.

I think it is because joken assumes the secret is not base64 encoded and jwt.io's demo has the secret as encoded. There is a comment on a closed issue here about it

I am using an auth0 generated token for an example application
eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJuYW1lIjoiUmFodWwgTWFoaWRhIiwibmlja25hbWUiOiJJdHNSYVdpdGhUaGVIIiwiaXNzIjoiaHR0cHM6Ly9pdHNyYXdpdGh0aGVoLmF1dGgwLmNvbS8iLCJzdWIiOiJnaXRodWJ8NTM5MzU2MSIsImF1ZCI6Im1BTzA5dUE5ejViOUJjTEVtczJ2YWNLRFowNlpmSkhOIiwiZXhwIjoxNDk5ODU0MTc1LCJpYXQiOjE0OTk4MTgxNzV9.ha24ogf-3oQhrh-laLIpbMc2-bB-UMjK2MccKK_dy4s
according to Auth0 settings, my client secret is not base64 encoded (its an option that i have left unchecked for now), and using my secret in jwt.io correctly decodes it (see screenshot) https://drive.google.com/open?id=0B7PTiKI7FL3vRnVLQ29VZlZQSzQ

@ItsRaWithTheH I tried to decode your token with hs256 using both "secret" (jwt.io default) and "my_secret_key". Obvisouly you've edited it for posting here and that is perfectly ok.
Not sure how you are generating your token but I can see that you have iat and exp claims. Be sure they are being properly validated. Try adding some validations to your verify function (here is an example validating a subject claim).

Since we've just released 2.0.0-rc0 that was a complete rewrite and since this did not have any activity, I'll close this.
If the issue persists, please re-open. Thanks!


Chiral support

@caseykneale what do you think about it? Let's put the references here to deal with it.

I talked about this with @timholy once upon a time. Its kind of an "open" problem, as in there are several ways to deal with it. So, parsing chiral SMILES is not problematic, but the requirements on how to store chiral chemical data in a graph in a meaningful way are tricky. This could be a good stretch goal for the package, but, I don't know if I have the time to invest in solving it at this point in time. I'll try to dig up the references he and I were looking at, if I can remember them.

I think you can lik here your refs. I'm working on the dependencies tree in my forked version and I will submit the PR here soon to publish the new version of the package today.

I think you can lik here your refs. I'm working on the dependencies tree in my forked version and I will submit the PR here soon to publish the new version of the package today. Obviously, the new release will not contain the chiral support yet. I'm just looking for ideas to implement in new releases

For the record, the way we handle this now is just getting the spatial coordinates into MolecularGraph (using PubChemCrawler), and once you have spatial coordinates it's trivial to do whatever you want. I'm not saying there isn't reason to want a coordinate-free solution, of course.


[Bug] Unselect checkbox when apply filters

Bug report
When i want to apply a bulk operation and selecting some entries, if then i apply some filter, the previous selected items are still selected.
What I did
In list view i have a bulk operation. I select 3 entries

Then i realised that i have to apply some filter that those 3 items previously selected where not a result from appling that filter. I select 3 other entries:

Finally i execute the bulk operation. In the alert appears that 6 entires where selected. The first 3 previous of being applied filter and the later.

I think that when applying some filters, the selected entries should be cleared.

Hello @aberaldo
Sorry it took me so much time to get here, it seems this issue missed any project board and I missed it too 😞
Your report is amazing, it was very easy for me to replicate the issue. Thanks for that 🙏
I've submitted https://github.com/Laravel-Backpack/CRUD/pull/4556 that should fix this.
If you test the PR let me know there if it's working for you.
Thanks again, cheers!

Thanks @aberaldo  & @pxpm . Let's move the conversation to #4556 please 🙏


Filtering on widgets when having "ñ" fails

@saleiva commented on Mon Oct 03 2016
underscore:172 Uncaught TypeError: Cannot read property 'toString' of null

@xavijam commented on Mon Oct 03 2016
Potentially a deep-insights bug, taking a look.

Where should be the character ñ? In the column name to be filtered?
In that case, how can I get a ñ in there?
Thank you!

Create a table with 2 columns, the_geom, type
Add 2 points in 0,0 for example
set type to "ESPAÑA" in one of them, and "FRANCE" in the other one
Add a widget to filter by the type column
Click on ESPAÑA.

I can't reproduce it.
This is my table:

This is the widget:

And if I click on ESPAÑA it works ok.

Did you try both, within the builder and the public view of the map?

Yes! Builder and embed, autostyling and filtering. I've just tried it again.

well, close it then. Will report it again if it happens!

Ok! Maybe it has been fixed with other changes :)


maybe add older versions of atlassian apps

maybe add older versions of atlassian apps

nope.
we will stay in support only of latest versions and lts. other older versions will not be rebuilding and supported.
i am sorry.

find  old openjdk6 and openjdk7, then test them. very old images may be broken with non-oracle java.

working on this issue


remove to* methods from ScratchSession as they don't do much

they don't do much and hide functionality

Ok


Cannot convert a MPS Tensor to float64 dtype as the MPS framework doesn't support float64. Please use float32 instead.

I am trying to run a code on MPS apple silicon. it is giving the following error
"Cannot convert a MPS Tensor to float64 dtype as the MPS framework doesn't support float64. Please use float32 instead."
However, the code is running fine on colab with device = 'cuda'. What could be the possible reason.
Untitled-1.txt

Ran into the same issue. Apple M1  has its own GPU that is not 'cuda'. And it does not support float64.

You can use this PR https://github.com/facebookresearch/segment-anything/pull/122

Hello
we’re you able to make it work on m1?


It seems that these settings above do not work to copy from a terminal window in tmux. I've added one line that does work but obviously not all the functionality is there. If it does not make sense to change your this project, can you at least tell me what other bindings I would need to get full functionality working? Thanks again as always.
On the linux branch of my dotfiles, here are the lines https://github.com/kleinjm/dotfiles/blob/linux/tmux/.tmux.conf#L132-L144

@gpakosz Thanks a lot!!!
After I lost almost a day to figure out it, finally I got it, thanks to you!!!


ACQ/ERM - LDP1 version of finance_funds derived table

Closes #728
This is a version for LDP1 of the already existing version for Metadb.
Note: The community discussed in the meeting that this PR can be uploaded without testing. This does not conform to the rules of CONTRIBUTING.md. It was determined that the reviewers would test the PR themselves using real data.
All queries:
- [ ] Pull request is based on a new branch (not main)
- [ ] Pull request scope is not overly broad
- [ ] Release notes have been added or updated in CHANGES.md
- [ ] Query runs without errors
- [ ] Query output is correct
- [ ] Query logic is clear and well documented
- [ ] Query is readable and properly indented with spaces (not tabs)
- [ ] Table and column names are in all-lowercase
- [ ] Quotation marks are used only where necessary

Report queries:
- [ ] Query has complete user documentation
    - [ ] Purpose of report
    - [ ] Sample output
    - [ ] Query instructions

Derived tables:
- [ ] Query begins with user documentation in comment lines
- [ ] File name is listed in `runlist.txt` after dependencies
- [ ] All columns have indexes
- [ ] Table is vacuumed and analyzed

I always set the line VACUUM ANALYZE at the end in this repository. There is no exact rule as to where that should be or I can't find it. However, it makes sense to do it at the end.

The community decided that the table should be called "finance_fund_ext". I create the change this week.

I changed the name of the derived table because there was a naming conflict with the table in the schema public. In the meeting, the community agreed on the name finance_funds_ext.


"Unreachable code" after JS IIFE

Issue Type: Bug
After today's update Code is reporting all code after an IIFE that returns within try and catch blocks as unreachable.
Demonstration:
const asdf = (() => {
	try {
		// do stuff
		return 1;
	} catch (e) {
		return 0;
	}
})(); // everything after this line is "unreachable"

let a = 1;
let b = 2;

VS Code version: Code 1.43.0 (78a4c91400152c0f27ba4d363eb56d2835f9903a, 2020-03-09T19:44:52.965Z)
OS version: Linux x64 5.3.0-40-generic

/duplicate of https://github.com/microsoft/TypeScript/issues/36828

In meantime you can use nightly builds of TS where this problem was resolved.
Easiest way - JavaScript and TypeScript Nightly extension


Can't see the default text for rich text box field.

Version information

Laravel: v5.6.33
Voyager: v1.1
PHP: 7.2.6
Database: MySql

Description
I have a Bread with a rich text box field and some default text for this field, When I add a new record, I can't see the default text for this rich text box field.
This field in the database is type text.
Steps To Reproduce
Steps to reproduce the behavior:

In a Bread put a field rich text box type
Put default text for this in details of the field
{
"default": "something"
}

Im new in Laravel and Voyager but,
How can I do for display a default text for rich text box field. ?
thx.

The richtextbox does not support the default value (Maybe they forget)
look at  vendor\tcg\voyager\resources\views\formfields\rich_text-box.blade.php
<textarea @if($row->required == 1) required @endif class="form-control richTextBox" name="{{ $row->field }}" id="richtext{{ $row->field }}">     @if(isset($dataTypeContent->{$row->field}))         {{ old($row->field, $dataTypeContent->{$row->field}) }}     @else         {{old($row->field)}}     @endif </textarea>
now compare with another form field for example text_area.blade.php
<textarea @if($row->required == 1) required @endif class="form-control" name="{{ $row->field }}" rows="{{ $options->display->rows or 5 }}">     @if(isset($dataTypeContent->{$row->field}))         {{ old($row->field, $dataTypeContent->{$row->field}) }}     @elseif(isset($options->default))         {{ old($row->field, $options->default) }}     @else         {{ old($row->field) }}     @endif </textarea>
has you can see, the rich textbox don't support default value,
Personally in some case I use to Override the view but I never tried with formfields

Hmm ok, ok, thanks so much. So I will override the view.
I was confused because in voyager docs  understanded that rich text box could have default.


Bland and little color variation for R syntax (.r files)

The gruvbox colorscheme displays bland colored syntax highlighting for the R language, .r files, compared to other colorschemes like the default colorscheme.
I have Treesitter set up and working as can be seen in the images, using Treesitter playground.
With default colorscheme syntax highlighting looks proper:

With gruvbox colorscheme the syntax highlighting looks bland, e.g. operators not colored and functions bold but not colored:

The gruvbox colorscheme is applied and works it seems, I just find it lacking compared to the syntax highlighting of other languages with gruvbox. Minimal init.vim file used for images: https://pastebin.com/AZQmRnmz
Is this how gruvbox is designed for R or is there something wrong with my setup? If this is just the way it is, can I specify a different gruvbox colorscheme only for .r files and if that's possible could someone point me in the right direction in doing so?

hey @joiharalds not sure if this is an issue with the proper R treesitter support. Unfortunately i am not much of a help for this particular one since i don't use R. Have you checked if https://github.com/arnau/vim-rlang maybe can help improve some of the groups?

Thanks for the answer!
I'm already using Nvim-R which supersedes vim-R-Plugin which vim-rlang is extracted from.
My lazy solution is to just use a different colorscheme for .R files. I could probably amend the colors of gruvbox for .R files but haven't gotten around to it. I'll report here if I do something of that sort.


enchancement(docs|ci): android beta promotion docs and ci

The type of this PR is: Enhancement

This PR resolves CX-976
Description
Added some docs about google play store releases, (one line pending to check after we do the first actual production release), and added the fastlane lanes and scripts for it.

PR Checklist (tick all before merging)

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

I'll merge, and @mounir, about the link and the last steps, let's do a final verification when we do the first official prod release? I feel kinda blind changing these without trying. I'd be more comfortable doing this with the first release, and document it while we do it.

#squashongreen


Logo of the Programming Club

The textual logo "KamandPrompt" on the navigation baar looks good, but we need the Programming Club logo like the one attached for the the website. Also check if it can match with the colour scheme, else we need to change that too.

Where do you plan to add the logo?

Top left, for a start. I don't think the text KamandPrompt looks very appealing. What do you think?

Yes, it can go a bit smaller.  I think we'd need to invert the logo?

Don't worry @abhigyank , this is why you have graphic designer in the team. :sunglasses: :stuck_out_tongue:

Issue solved!


Allowing complete control of the axios instance at the request level (so we can use any axios feature)

A few updates, no breaking changes:

Addingaxios and axiosOverride config arguments that allow complete control of the axios instance at the request level so we can use any axios feature (including the timeouts in #49 )
(cleanup) Standardizing instance function arguments to function(b2, args) while retaining backwards compatibility - necessary for addingaxios and axiosOverride args.
(cleanup) Moving API endpoint generation into one file - endpoints.js
Improved documentation (#1 )

To be honest I'd rather just release a major version with the breaking change than have all this cruft in the code to deal with backwards compatibility. But I'll defer to the others opinions on that.

@odensc I agree that it'll look cleaner without the backwards compatibility, but I'd wait on a few other potentially breaking changes before releasing the next major update: rewriting b2.js with an ES6 class and (if possible) removing of the .authorize() call and managing that automatically/internally as requested in #56


Investigate Visitor Pattern in ANTLR for Modifying Parsing Behavior

Description
To ensure that our parsers can yield the desired output structure, it's pivotal to understand how the visitor pattern in ANTLR can be utilized to modify parsing behavior. This task requires setting up experiments to test and validate our understanding, focusing on extracting the type of information outlined in our desired parser output structure.
Completion Criteria

[ ] Research how the visitor pattern is used in ANTLR for modifying parsing behavior.
[ ] Design and implement experiments aiming to extract the specified information from parsers utilizing the listener pattern.
[ ] Analyze the experiment results to ascertain the correctness of our understanding and the feasibility of obtaining the desired parser output.
[ ] Document the findings and share the results with the team for review and discussion.

Not for us. Using listener pattern.


consistent naming for better readability

this change is as per the discussion in the link below
https://github.com/kubeflow/training-operator/pull/1418#issuecomment-925084880

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 8.161%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
311

Relevant Lines:
3811

💛  - Coveralls

ping @pramodrj07 Hi do you still work on it?

Hi Yes. I am working on it. I will push the update in a few hours.

Thanks!


Added contact us & fixed footer text in light mode

@DhanushNehru
Change is only required in footer of "index.html" and "choose.html".
Please don't change other elements.
Contact form is already present as "form.html".
You just need to add button of "contact us".


[All hosts](community call) Add June blog link

Adding the link for the June 9 2021 community call.

Docs Build status updates of commit 2f226ed:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/overview/office-add-ins-community-call.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a0a6e02:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/overview/office-add-ins-community-call.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


The schema parser should be able to import external schema files

The schema parser should be able to import external schema files.
The problem of this issue is knowing the path of the parsed raml file. The parser plugin should provide the path of the raml or the path of the schema file.
The easiest part of this issue is to load external schemas with uri like:
http://mydomain.com/subSchema

+1.

Referencing PR with fix.

So now raml-parser provides the current folder of the file ?
Could you please do a PR with the needed changes @alvassin ?

@repocho Raml does not provide current folder of the file, i've just added option dereferenceSchemas=true, which enforces dereferencing of all schemas. If this solution suits you, you need to pull latest version from raml-js-parser & use dereferenceSchemas=true option when loading raml file.

So !!
If I understand well, if we use { dereferenceSchemas: true } loading a raml file, it will retrieve all $refs correctly from the schemas inside the raml files and also will retrieve all the $refs inside the json schema files.
So the result will be a json without $ref attributes at all, right ?
If I'm right I can remove from raml-mocker all the related code of "$ref" attribute.

@repocho right, it should work so.

Great !!! I'm testing it and works like a charm !!
Thanks for your help and your PR to raml-parser @alvassin !!

@alvassin I have detected that circular dependencies are not allowed but could be valid. If array elements children is 0 it will stop.
For example:
{
    "$schema": "http://json-schema.org/schema",
    "definitions": {
        "node": {
            "type": "object",
            "properties": {
                "id": {
                    "type": "string",
                    "format": "id"
                },
                "label": {
                    "type": "string"
                },
                "children": {
                    "type": "array",
                    "items": {
                        "$ref_circular": "#/definitions/node"
                    }
                }
            },
            "required": ["id", "label", "children"]
        }
    },
    "items": {
        "$ref": "#/definitions/node"
    },
    "type": "array"
}

What do you think it's the best way to solve this??

I've opened another issue for that: #20


Fail equals method doesn't compare exceptions properly

This assertion should succeed:
@Test
fun test() {
    val fail = Fail<String>(TestException())
    val fail2 = Fail<String>(TestException())

    assertEquals(fail, fail2) // fails
}

class TestException : Exception("Testing error")

@Lamorak Why? The stack traces are different.

Well first it's very contra intuitive because if the exceptions are equal, you'd expect the Fail wrappers to also be equal. Second, this essentially prohibits any testing with failed state because no two Fails will ever be equal (unless they somehow hold the same instance of exception).
I suggest to just use the exception's equals method bucause it should know best which two exceptions are equal after all.

@Lamorak The exceptions are not equal though. They were thrown on different lines therefore they have different stack traces and represent different exceptions.
For testing, the recommended approach is to create your exception once and check for it both times.

@gpeal Why doesn't the provided sample work? The exceptions weren;t even thrown yet and should have no stack traces.
I do create one exception and check for it in the test, but as you know exceptions are not immutable therefore the check fails.

@Lamorak Your test fails because the two exceptions have different stack traces because they were created on different lines of code.

I'm going to close this because I don't think it is an issue for the reasons above. Feel free to reopen it if you feel otherwise.

I'm going to close this because I don't think it is an issue for the reasons above. Feel free to reopen it if you feel otherwise.


argo installation fails for user provided cluster with some existing namespaces

tested this on minikube where if i have a namespace that is not an argo namespace, install fails...
axopsbootstrap: [{'reason': u'SuccessfulMountVolume', 'message': u'MountVolume.SetUp succeeded for volume "default-token-j30rt" ', 'name': u'axops-bootstrap-pod'}]
==============================
2017-10-12T17:18:25 INFO ax.platform.platform MainThread: Updating application managers
2017-10-12T17:18:25 INFO ax.platform.platform MainThread: --- updating argos3
2017-10-12T17:18:25 ERROR ax.cluster_management.app.cluster_installer MainThread: 'NoneType' object has no attribute 'getitem'
Traceback (most recent call last):
File "/ax/python/ax/cluster_management/app/cluster_installer.py", line 271, in install_and_run_platform
platform.start()
File "/ax/python/ax/platform/platform.py", line 335, in start
a = Application(app, client=self.kubectl)
File "/ax/python/ax/platform/application.py", line 52, in init
elb_status = elb.status(with_loadbalancer_info=True)["loadbalancer"][0]
TypeError: 'NoneType' object has no attribute 'getitem'
2017-10-12T17:18:25 ERROR ax.cluster_management.argo_cluster_manager MainThread: 'NoneType' object has no attribute 'getitem'
Please manually check the cluster status and retry installation with same command if the error is transient.
Traceback (most recent call last):
File "/ax/python/ax/cluster_management/argo_cluster_manager.py", line 77, in parse_args_and_run
getattr(self, cmd)(args)
File "/ax/python/ax/cluster_management/argo_cluster_manager.py", line 246, in install_platform_only
PlatformOnlyInstaller(platform_install_config).run()
File "/ax/python/ax/cluster_management/app/cluster_installer.py", line 527, in run
cluster_dns, username, password = self._ci_installer.install_and_run_platform()
File "/ax/python/ax/cluster_management/app/cluster_installer.py", line 279, in install_and_run_platform
raise RuntimeError(install_platform_failure_message)
RuntimeError: 'NoneType' object has no attribute 'getitem'
Please manually check the cluster status and retry installation with same command if the error is transient.
!!! Operation failed due to runtime error: 'NoneType' object has no attribute 'getitem'
Please manually check the cluster status and retry installation with same command if the error is transient.

Fixed with 7a3ca2a08a05a77616d4511441670dff0e300c3d.


[WIP] Configurable server results pipe

This pull-request adds the ability to configure the Sensu Transport pipe used for consuming check results. A super power user tool, only intended to be used when deploying an active-active site setup (e.g. using the RabbitMQ shovel plugin).
Example RabbitMQ configuration:
[
    {rabbitmq_shovel,
       [{shovels,
         [{site_a_results,
           [{sources,      [{broker, "amqp://sensu:secret@site-a:5672/%2Fsensu"},
                            {declarations,
                               [{'exchange.declare',
                                       [{exchange, <<"results">>},
                                        {type, <<"direct">>}]},
                                {'exchange.declare',
                                       [{exchange, <<"site-a-results">>},
                                        {type, <<"direct">>}]},
                                {'exchange.bind',
                                       [{source, <<"results">>},
                                        {destination, <<"site-a-results">>}]},
                                {'queue.declare',
                                       [{queue, <<"shovel-site-a-results">>}]},
                                {'queue.bind',
                                       [{exchange, <<"results">>},
                                        {queue, <<"shovel-site-a-results">>}]}
                               ]}]},
            {destinations, [{broker, "amqp://sensu:secret@site-b:5672/%2Fsensu"},
                            {declarations,
                               [{'exchange.declare',
                                       [{exchange, <<"site-b-results">>},
                                        {type, <<"direct">>}]},
                                {'exchange.bind',
                                       [{source, <<"results">>},
                                        {destination, <<"site-b-results">>}]}
                               ]}]},
            {queue, <<"shovel-site-a-results">>},
            {ack_mode, on_confirm},
            {publish_properties, [{delivery_mode, 2}]},
            {publish_fields, [{exchange, <<"site-b-results">>}]},
            {reconnect_delay, 5}
           ]}
          ]
        }]
     }
].

[
    {rabbitmq_shovel,
       [{shovels,
         [{site_b_results,
           [{sources,      [{broker, "amqp://sensu:secret@site-b:5672/%2Fsensu"},
                            {declarations,
                               [{'exchange.declare',
                                       [{exchange, <<"results">>},
                                        {type, <<"direct">>}]},
                                {'exchange.declare',
                                       [{exchange, <<"site-b-results">>},
                                        {type, <<"direct">>}]},
                                {'exchange.bind',
                                       [{source, <<"results">>},
                                        {destination, <<"site-b-results">>}]},
                                {'queue.declare',
                                       [{queue, <<"shovel-site-b-results">>}]},
                                {'queue.bind',
                                       [{exchange, <<"results">>},
                                        {queue, <<"shovel-site-b-results">>}]}
                               ]}]},
            {destinations, [{broker, "amqp://sensu:secret@site-a:5672/%2Fsensu"},
                            {declarations,
                               [{'exchange.declare',
                                       [{exchange, <<"site-a-results">>},
                                        {type, <<"direct">>}]},
                                {'exchange.bind',
                                       [{source, <<"results">>},
                                        {destination, <<"site-a-results">>}]}
                               ]}]},
            {queue, <<"shovel-site-b-results">>},
            {ack_mode, on_confirm},
            {publish_properties, [{delivery_mode, 2}]},
            {publish_fields, [{exchange, <<"site-a-results">>}]},
            {reconnect_delay, 5}
           ]}
          ]
        }]
     }
].

Example Sensu configurations:
{
    "sensu": {
        "server": {
            "results_pipe": "site-a-results"
        }
    }
}

{
    "sensu": {
        "server": {
            "results_pipe": "site-b-results"
        }
    }
}

TODO: Sensu settings validation rules.

Just waiting on https://github.com/sensu/sensu-settings/pull/92

A more complete configuration example for check results and keepalives:
[
    {rabbitmq_shovel,
       [{shovels,
         [{site_a_results,
           [{sources,      [{broker, ["amqp://sensu:secret@site-a-1:5672/%2Fsensu"
                                     , "amqp://sensu:secret@site-a-2:5672/%2Fsensu"
                                     , "amqp://sensu:secret@site-a-3:5672/%2Fsensu"
                                     ]},
                            {declarations,
                               [{'exchange.declare',
                                       [{exchange, <<"results">>},
                                        {type, <<"direct">>}]},
                                {'exchange.declare',
                                       [{exchange, <<"site-a-results">>},
                                        {type, <<"direct">>}]},
                                {'exchange.bind',
                                       [{source, <<"results">>},
                                        {destination, <<"site-a-results">>}]},
                                {'queue.declare',
                                       [{queue, <<"shovel-site-a-results">>}]},
                                {'queue.bind',
                                       [{exchange, <<"results">>},
                                        {queue, <<"shovel-site-a-results">>}]}
                               ]}]},
            {destinations, [{broker, ["amqp://sensu:secret@site-b-1:5672/%2Fsensu"
                                     , "amqp://sensu:secret@site-b-2:5672/%2Fsensu"
                                     , "amqp://sensu:secret@site-b-3:5672/%2Fsensu"
                                     ]},
                            {declarations,
                               [{'exchange.declare',
                                       [{exchange, <<"results">>},
                                        {type, <<"direct">>}]},
                                {'exchange.declare',
                                       [{exchange, <<"site-b-results">>},
                                        {type, <<"direct">>}]},
                                {'exchange.bind',
                                       [{source, <<"results">>},
                                        {destination, <<"site-b-results">>}]}
                               ]}]},
            {queue, <<"shovel-site-a-results">>},
            {ack_mode, on_confirm},
            {publish_properties, [{delivery_mode, 2}]},
            {publish_fields, [{exchange, <<"site-b-results">>}]},
            {reconnect_delay, 5}
           ]},
          {site_a_keepalives,
           [{sources,      [{broker, ["amqp://sensu:secret@site-a-1:5672/%2Fsensu"
                                     , "amqp://sensu:secret@site-a-2:5672/%2Fsensu"
                                     , "amqp://sensu:secret@site-a-3:5672/%2Fsensu"
                                     ]},
                            {declarations,
                               [{'exchange.declare',
                                       [{exchange, <<"keepalives">>},
                                        {type, <<"direct">>}]},
                                {'exchange.declare',
                                       [{exchange, <<"site-a-keepalives">>},
                                        {type, <<"direct">>}]},
                                {'exchange.bind',
                                       [{source, <<"keepalives">>},
                                        {destination, <<"site-a-keepalives">>}]},
                                {'queue.declare',
                                       [{queue, <<"shovel-site-a-keepalives">>}]},
                                {'queue.bind',
                                       [{exchange, <<"keepalives">>},
                                        {queue, <<"shovel-site-a-keepalives">>}]}
                               ]}]},
            {destinations, [{broker, ["amqp://sensu:secret@site-b-1:5672/%2Fsensu"
                                     , "amqp://sensu:secret@site-b-2:5672/%2Fsensu"
                                     , "amqp://sensu:secret@site-b-3:5672/%2Fsensu"
                                     ]},
                            {declarations,
                               [{'exchange.declare',
                                       [{exchange, <<"keepalives">>},
                                        {type, <<"direct">>}]},
                                {'exchange.declare',
                                       [{exchange, <<"site-b-keepalives">>},
                                        {type, <<"direct">>}]},
                                {'exchange.bind',
                                       [{source, <<"keepalives">>},
                                        {destination, <<"site-b-keepalives">>}]}
                               ]}]},
            {queue, <<"shovel-site-a-keepalives">>},
            {ack_mode, on_confirm},
            {publish_properties, [{delivery_mode, 2}]},
            {publish_fields, [{exchange, <<"site-b-keepalives">>}]},
            {reconnect_delay, 5}
           ]}
         ]
        }]
     }
].


PyConf Hyd 2020

Can you kindly add the details for Pyconf Hyderabad 2020 to the page? Details are as below
Name and link : PyConf Hyderabad 2020 (https://pyconf.hydpy.org/2020/)
Date : 5th - 6th December 2020
Venue : Virtual
Description : PyConf Hyderabad is the regional gathering for the community that uses and develops the open-source Python Programming Language. And this year, it is Virtual!
Scholarship Provided : No

Raised PR #187 for the same.

Done in #187! Thanks for creating the PR real quick, @inovizz! :raised_hands: :tada:


Licensing

Hi, I was hoping to use pygame-text-input for a program I am developing for an A-Level project, but there is no licensing info which I could find. Github projects with no license are All Rights Reserved by default, so it would be illegal for me to use the file without explicit permission. Is it possible to add a license to the library to clear up when and how it can be used?

Yeah sure. I'll put it under the MIT license. Tell me if that's not compatible with your project.

That would be fantastic, thank you very much.


NLog.config file not added to project when installing NuGet Package using PackageReference

NLog version: (4.5.6)
Platform: .NET 4.6.1
Referencing previous issue https://github.com/NLog/NLog/issues/2461#issuecomment-394013813
Steps to reproduce...

File > New > Project > WPF App
Right-click References > Manage NuGet Packages...
Select Browse tab > type NLog.Config > Install

NLog.config file should be added to project, but don't see like I did before starting to use the new PackageReference for NuGet.
I can see the file in the Debug folder.

What's the NLog version?

NLog and NLog.Config version: 4.5.6

what's your visual studio version?

VS 2017 15.7 RTM

Same here with NLog.Config 4.5.7.
I am not sure what is accomplished by the package is actually supported in nuget package reference mode...

it should work on both modes. This has been fixed in the past, not sure if it's the same problem

In my case I don't have any file coming from content in the packages (nlog.config, nlog.xsd).
Also I noticed nlog.config is using an Install.ps1 script, which is no longer supported in package reference mode (https://docs.microsoft.com/en-us/nuget/reference/migrate-packages-config-to-package-reference#package-compatibility-issues)

Thanks for reporting.
Closing this in favor of https://github.com/NLog/NLog/issues/2823


feat(align-deps): allow version range subsets

Description
Allow exact and version range subsets with --diff-mode allow-subset.
Resolves #2983
Resolves #2984
Test plan
n/a

Looks like a good change. One question is whether this will lead to more duplicate packages within the repo and whether we need to do something to counteract that.

It's more likely that dupes will be introduced. I've added a warning label in the docs.