GitOps set config command

As a user, I want an easy way to configure settings for my CLI.  This will make it easy for me to update settings.
Acceptance Criteria

When they execute the command gitops set config analytics=true or gitops set config analytics=false then the value is set and we know not to ask them again.
When the user executes the command gitops set config analytics=false they should receive a warning that this will only turn off analytics for the CLI and that they should go to the documentation to turn off the analytics in the GitOps Dashboard.
It is expected that this command will work on the Enterprise CLI as well.
It is expect that the config blob is a JSON object.
Leverage https://pkg.go.dev/os#UserConfigDir

{
    "analytics": true,
    "userId": 12345
}

As discussed with @ozamosi, positional arguments will be used instead of the analytics flag (similar to kubectl config and git config): gitops set config analytics true


VSCode crash

[Info  - 5:10:07 PM] Connection to server got closed. Server will restart.
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/libcore/option.rs:378:21
stack backtrace:
   0: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
   1: core::fmt::write
   2: std::io::Write::write_fmt
   3: std::panicking::default_hook::{{closure}}
   4: std::panicking::default_hook
   5: std::panicking::rust_panic_with_hook
   6: std::panicking::continue_panic_fmt
   7: rust_begin_unwind
   8: core::panicking::panic_fmt
   9: core::panicking::panic
  10: ra_syntax::ast::make::ast_from_text
  11: ra_syntax::ast::make::name_ref
  12: ra_hir_expand::diagnostics::DiagnosticSink::on::{{closure}}
  13: ra_hir_expand::diagnostics::DiagnosticSink::_push
  14: ra_hir_expand::diagnostics::DiagnosticSink::push
  15: ra_hir_ty::expr::ExprValidator::validate_body
  16: ra_hir::code_model::Function::diagnostics
  17: ra_hir::code_model::Module::diagnostics
  18: ra_ide::diagnostics::diagnostics
  19: std::panicking::try::do_call
  20: __rust_maybe_catch_panic
  21: ra_db::CheckCanceled::catch_canceled
  22: ra_ide::Analysis::diagnostics
  23: ra_lsp_server::main_loop::handlers::publish_diagnostics
  24: ra_lsp_server::main_loop::loop_turn
  25: ra_lsp_server::main_loop::main_loop
  26: ra_lsp_server::main
  27: std::rt::lang_start::{{closure}}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Using https://github.com/rust-analyzer/rust-analyzer/commit/9df1663c12f48df7f4921e68c928016877390565
And on code: https://github.com/leo-lb/hyper-async-std/commit/7943d76a46a441df197c57bd71c07dfa6ec370ae

A Minimal case :
struct NewCompat(usize);

impl<T> From<usize> for usize {
    fn from(v: usize) -> Self {
        NewCompat { v }
    }
}

@edwin0cheng Thanks.

@leo-lb  #2762 should fix it,  would you mind to test it again in master ?

Does not crash anymore! Thanks!


centralize functionality that is reused across many tests

Specifically DummyType, dummy workflows, etc. This is important for testing the basic functionality, as the actual types and workflows live in other repositories.

@jairideout, this one is done, right?

Almost -- qiime.core.testing needs the dummy methods factored out of the unit tests. I may just take care of that during the method refactoring I'm working on.


Removes tiny.amazon.com links

Description
Removes tiny.amazon.com links that are internal.
Category
Maintenance
Testing
N/A
Check List

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

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

Codecov Report

Merging #1420 (925d568) into main (8714e2a) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main    #1420   +/-   ##
=======================================
  Coverage   65.51%   65.51%
=======================================
  Files          93       93
  Lines        2294     2294
  Branches      312      307    -5
=======================================
  Hits         1503     1503
  Misses        723      723
  Partials       68       68


triggerUncaughtException

getting this error and have no clue how to fix it , I used the nvm use 8 and nvm use 16 trick to get past the first error but now getting this, I get it on the test network.
node offers.js --config=config.json --file=list.txt --verbose

Init config...

Init config...
Init OpenSea SDK...
Using network: rinkeby...
Using Infura...
Init event handlers...

Starting...
Instance ID: 7484-169
Auto price enabled.
Default floor: 0.001, roof: 100, epsilon: 0.001.
Delay per line: 1000--2000 ms.

   1 Acquiring asset...
     Address: 0x08a62684d8d609dcc7cfb0664cf9aabec86504e5
     Id:      100

   1 Processing...
     Address: 0x08a62684d8d609dcc7cfb0664cf9aabec86504e5
     Id:      100
     Price:   0.007

 % Order created
{
  code: -32603,
  message: 'Unknown Error: internal service failure\n',
  data: { originalError: {} },
  stack: 'Error: Unknown Error: internal service failure\n' +
    '\n' +
    '    at Request._callback (/Users/toro/opensea/sea-offers-bot-js/node_modules/@trufflesuite/web3-provider-engine/subproviders/rpc.js:57:23)\n' +
    '    at Request.self.callback (/Users/toro/opensea/sea-offers-bot-js/node_modules/request/request.js:185:22)\n' +
    '    at Request.emit (node:events:390:28)\n' +
    '    at Request.<anonymous> (/Users/toro/opensea/sea-offers-bot-js/node_modules/request/request.js:1154:10)\n' +
    '    at Request.emit (node:events:390:28)\n' +
    '    at IncomingMessage.<anonymous> (/Users/toro/opensea/sea-offers-bot-js/node_modules/request/request.js:1076:12)\n' +
    '    at Object.onceWrapper (node:events:509:28)\n' +
    '    at IncomingMessage.emit (node:events:402:35)\n' +
    '    at endReadableNT (node:internal/streams/readable:1343:12)\n' +
    '    at processTicksAndRejections (node:internal/process/task_queues:83:21)'
}

 * 1 Offer succeed with errors.
     Address: 0x08a62684d8d609dcc7cfb0664cf9aabec86504e5
     Id:      100
     Price:   0.007

   1 Internal error due processing.

On mainnet it seems to be working but I get it blocked by cloudflare, btw I'm not using an opensea api key, could that be the problem ?
`node offers.js --config=config.json --file=list.txt --proxy=proxy.txt --verbose
Init config...
Init config...
Init OpenSea SDK...
Using network: mainnet...
Using Infura...
Init proxies...
Switch proxy 1 - http://<IP_ADDRESS>:44555
Init event handlers...
Starting...
Instance ID: 6928-463
Auto price enabled.
Default floor: 0.001, roof: 100, epsilon: 0.001.
Delay per line: 1000--2000 ms.
1 Acquiring asset...
Address: 0x1eff5ed809c994ee2f500f076cef22ef3fd9c25d
Id:      8
1 Processing...
Address: 0x1eff5ed809c994ee2f500f076cef22ef3fd9c25d
Id:      8
Price:   0.008
% Order created

1 Offer succeed with errors.
Address: 0x1eff5ed809c994ee2f500f076cef22ef3fd9c25d
Id:      8
Price:   0.008
1 Request was blocked by Cloudflare.

Done.
`

Can you set in config "log_full": true
And then show your log?

On mainnet, your proxy probably blacklisted by Cloudflare. Can you make it work without proxy?

To pass Cloudflare, add in config user_agent and cookie. You can pass captcha manually in browser and then use cookie cf_clearance=...

If your proxy blacklisted by Cloudflare, you will probably need different proxy, ideally setup your own private proxy.


Add a --context flag to dispatch

Feature Request
Add a --context flag to dispatch CLI.
Detailed Description

You can have multiple contexts in the dispatch config file (~/.dispatch/config.json). Each context stores the location of a dispatch endpoint. Currently, to switch context you need to do dispatch manage context --set <context_name>. This is helpful as long as you intend to work in that context for some time.
But it's not possible to temporarily switch to a context and run a single command e.g. I just need to see if the functions are getting invoked in my production dispatch but I don't want to switch context and accidentally delete the resources in it. Hence, it will be nice to add a --context global flag to the CLI and switch the context only for that CLI command.
e.g. dispatch get functions (retrieves functions from my default dispatch context)
dispatch --context prod-dispatch get functions (retrieves functions from my prod dispatch context)
dispatch delete function process-credit-payment (Phew! that was just my dev-cluster)
Context

Possible Implementation

Complexity

[x] Low - Simple enhancement or bug fix, no architectural changes or refactoring
[ ] Medium - Change requires some thought, but is relatively isolated
[ ] High - Significant architectural change or large refactor

Zhiming can you take this?

Ok I will try this.


WebHook Content

Hi,
I read Wix Restaurant Api for Sending WebHooks  and i noticed that every time an order submits to system WebHook receives Menu Object and Order Object.
What's the need for Menu Object? If we want to submit orders to our POS System?
Thanks In advance

The Order object lists the IDs of ordered items, and the Menu object has the full information for each item (title, description, etc).
You can ignore the menu data if you don't need it :)

thanks a lot


Identify better path for Snowflake Account ID

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/892
Originally created by @bencodezen on 2019-08-16 15:51:19

Pasting in the URL pulls out the ID so quickly it make the user question whether or not they did the right thing.

View 6 previous comments from the original issue on GitLab


Add files via upload

Lányi Ferenc Technikum és Szakképző Iskola
lanyiferenc.hu

@nagypal-rob First stage of verification passed, official domain for Lányi Ferenc Technikum és Szakképző Iskola is lanyiferenc.hu as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@nagypal-rob Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


[DOC] Simple Schema for Observability

What do you want to do?

[ ] Request a change to existing documentation
[x] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
With OpenSearch 2.6, we intend to release a standardization for conforming to a common & unified Observability schema which will be named Simple Schema for Observability (SSO).
This schema is compatible with OTEL schema & includes traces, logs & metrics. We also intend for supporting Alerts entity.
Simple Schema for Observability will also accept ECS logs when such structured log are present.
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.

https://github.com/opensearch-project/observability/issues/1399
https://github.com/opensearch-project/observability/issues/1398
https://github.com/opensearch-project/observability/issues/1388
https://github.com/opensearch-project/observability/issues/1389
OTEL
ECS

Hi Aria, can you please take a look at this and let me know the scope? Thanks.

Hey @YANG-DB , I was wondering if we can get some clarification on this one. For documentation are we looking to explain our integration of SSO and OTel, like how it works under the hood, or are we looking to explain that basically "We support these things, here's how to configure it in Observability" ?

Hi
I think that for sso scheme we need to describe the high level purpose and use case without drilling into the actual implementation details...

Hey @YANG-DB, thanks for clarifying. One further question. Can you tell me if SSO is still scheduled for release with 2.6?

Yes we are planning on releasing that on 2.6

In progress and on track.

@YANG-DB can you review this PR for technical accuracy? - https://github.com/opensearch-project/documentation-website/pull/2940

on it ...


ARTEMIS-2578 clarify storage capacity messages

This is a surprisingly large change just to fix some log messages, but
the changes were necessary in order to get the relevant data to where it
was being logged. The fact that the data wasn't readily available is
probably why it wasn't logged in the first place.

nice one...
I didn't include it because it was a simple version.
nice enhancement

I can't merge it myself now.. but I aprove the changes. if no one merges it before me, I will do it later today.


Vue-cli parallelism error at building when CPU limitations

Version
3.0.0
Node and OS info
Yarn 1.9.4 / CircleCI docker img: circleci/node:10.8-stretch-browsers
Steps to reproduce

Use the free version of CircleCI.
Build with CircleCI.

What is expected?
Normal build
What is actually happening?
events.js:183
throw er; // Unhandled 'error' event
^
Error: This socket has been ended by the other party
at Socket.writeAfterFIN (...)

Deactivating the parallelism is a workaround. More info here: https://forum.vuejs.org/t/solution-to-building-error-in-circleci-or-any-other-machine-with-cpu-limitations/40862
I think this should be in the docs.

Not sure if that's the real cause as our own tests run on free Circle CI.

Are you able to reproduce it?

As quoted here:

The issue with this on Dockerized services such as CircleCI is that the container thinks it has access to all of the hosts cores, although its being limited down to 4 by another process.

I've encountered this issue before, with jest.

@JFGHT Vue CLI's own tests runs on Circle CI free tier all the time, and it is passing right now. The only thing I can think of is that we are open source so we get 4 containers by default. Are you building from a private repo? In addition, can you share your Circle CI config.yaml?
One obvious option is disabling parallel by default in CI environments, although I'd like to avoid that if possible, as that would lead to non-optimal performance in CI systems that do support multiple cores.

Yes, I'm building in a private repo.
# Javascript Node CircleCI 2.0 configuration file
#
# @see https://circleci.com/docs/2.0/language-javascript/
#
version: 2

defaults: &defaults
  working_directory: ~/bloqify/generic
  docker:
  - image: circleci/node:10.8-stretch-browsers
    environment:
      JEST_SUITE_NAME: jest
      JEST_JUNIT_OUTPUT: artefacts/tests/jest/js-test-results.xml

upgrade_os: &upgrade_os
  run:
    name: Update OS
    command: sudo apt-get update && sudo apt-get install

upgrade_yarn: &upgrade_yarn
  run:
    name: Update Yarn
    command: sudo npm i -g yarn

yarn_install: &yarn_install
  run:
    name: Yarn install
    command: yarn install --frozen-lockfile --non-interactive

inspect_webpack_config: &inspect_webpack_config
  run:
    name: Inspect Webpack config
    command: yarn inspect

yarn_build: &yarn_build
  run:
    name: Yarn build
    command: yarn build

yarn_test: &yarn_test
  run:
    name: Run tests
    command: yarn test:unit --ci --runInBand --reporters="default" --reporters="jest-junit"

eslint_junit: &eslint_junit
  run:
    name: ESlint
    command: ./node_modules/.bin/eslint ./src/**/*.{js,ts}  --format junit --output-file ./artefacts/eslint/js-lint-results.xml

cloud_functions_yarn_install: &cloud_functions_yarn_install
  run:
    name: Install Cloud Functions dependencies
    command: cd functions && yarn install

deploy_firebase: &deploy_firebase
  run:
    name: Deploy Master to Firebase && deploy functions
    command: ./node_modules/.bin/firebase deploy --non-interactive --token=$FIREBASE_DEPLOY_TOKEN

restore_yarn_cache: &restore_yarn_cache
  restore_cache:
    keys:
    - node_modules-{{ checksum "yarn.lock" }}
    - node_modules

save_yarn_cache: &save_yarn_cache
  save_cache:
    key: node_modules-{{ checksum "yarn.lock" }}
    paths:
    - node_modules

restore_git_cache: &restore_git_cache
  restore_cache:
    keys:
    - generic-{{ .Branch }}-{{ .Revision }}
    - generic-{{ .Branch }}-
    - generic-

save_git_cache: &save_git_cache
  save_cache:
    key: generic-{{ .Branch }}-{{ .Revision }}
    paths:
    - ".git"

generic_build-procedure: &generic_build-procedure
  <<: *defaults
  steps:
  - <<: *upgrade_os
  - <<: *upgrade_yarn
  - <<: *restore_git_cache
  - checkout
  - <<: *save_git_cache
  - <<: *restore_yarn_cache
  - <<: *yarn_install
  - <<: *inspect_webpack_config
  - <<: *yarn_build
  - <<: *save_yarn_cache
  - persist_to_workspace:
      root: ~/bloqify
      paths:
      - generic

build_web1-procedure: &build_web1-procedure
  working_directory: ~/bloqify/web1
  docker:
  - image: circleci/node:10.7-stretch-browsers
  steps:
  - <<: *restore_git_cache
  - checkout
  - <<: *restore_yarn_cache
  - <<: *yarn_install
  - <<: *inspect_webpack_config
  - <<: *yarn_build
  - persist_to_workspace:
      root: ~/bloqify
      paths:
      - web1

lint-js-procedure: &lint-js-procedure
  <<: *defaults
  steps:
  - <<: *upgrade_os
  - <<: *upgrade_yarn
  - attach_workspace:
      at: ~/bloqify
  - <<: *eslint_junit
  - store_test_results:
      path: artefacts/eslint
  - store_artifacts:
      path: artefacts/eslint
      destination: eslint

test-jest-procedure: &test-jest-procedure
  <<: *defaults
  steps:
  - <<: *upgrade_os
  - <<: *upgrade_yarn
  - attach_workspace:
      at: ~/bloqify
  - <<: *yarn_test
  - store_test_results:
      path: artefacts/tests/jest
  - store_artifacts:
      path: artefacts/tests/jest
      destination: jest

deploy_web1-procedure: &deploy_web1-procedure
  working_directory: ~/bloqify/web1
  docker:
  - image: circleci/node:10.8-stretch-browsers
  steps:
    - attach_workspace:
        at: ~/bloqify
    - run:
        name: Create .firebaserc file
        command: 'echo ''{ "projects": { "default": "web1" } }'' > .firebaserc'
    - <<: *cloud_functions_yarn_install
    - <<: *deploy_firebase

jobs:
  generic_build:
    <<: *generic_build-procedure
  lint-js:
    <<: *lint-js-procedure
  test-jest:
    <<: *test-jest-procedure
  build_web1:
    <<: *build_web1-procedure
  deploy_web1:
    <<: *deploy_web1-procedure

workflows:
  version: 2
  build-test-deploy:
    jobs:
    - generic_build
    - lint-js:
        requires:
          - generic_build
    - test-jest:
        requires:
          - generic_build
    - build_web1:
        context: web1
        requires:
          - test-jest
          - lint-js
        filters:
          branches:
            only: master
    - deploy_web1:
        requires:
          - build_web1

Fixed https://github.com/vuejs/vue-cli/issues/3850.


consistent command line options (cbuild, csolution)

I general all tools of the CMSIS-Toolbox should have consistent messages and options.
For cbuild I suggest the following changes:
Usage:
  cbuild [<command>] <project.cprj | csolution.yml> [<options>]

Commands:
  list contexts       Print list of contexts in a csolution.yml
  list toolchains     Print list of installed toolchains
  build                   Generate output (default when no command specified)

Options:
  -C, --clean                  Remove intermediate and output directories
  -c,  --context string        Input context name [<cproject>][.<build-type>][+<target-type>]
  -d, --debug                  Enable debug messages
  -g, --generator string       Select build system generator (default "Ninja")
  -h, --help                   Print usage
  -i, --intdir string          Set directory for intermediate files
  -j, --jobs int               Number of job slots for parallel execution
  -l, --load string            Set policy for packs loading [latest|all|required]
  -L, --log string             Save output messages in a log file
  -o, --outdir string          Set directory for output binary files
  -O, --output string          Set directory for all output files
  -p, --packs                  Download missing software packs with cpackget
  -q, --quiet                  Suppress output messages except build invocations
  -R, --rebuild                Remove intermediate and output directories and rebuild
  -S, --schema                 Validate project input file(s) against schema
  -t, --target string          Optional CMake target name
  -u, --update string          Generate *.cprj file for reproducing current build
  -U, --update-rte             Update the RTE directory and files
  -v, --verbose                Enable verbose messages from toolchain builds
  -V, --version                Print version

Note: Some option letters are capitalize to harmonize it with csolution.

I suggest also to review the number of options that are currently available.  Maybe several options should be not exposed to the user, i.e. -intdir (which really refers to the ./tmp directory).

Should we consider discontinuing the support for *.cprj files in cbuild 2.0 considering that this format will be replaced by *.cbuild.yml in the future?

Yes, we should discontinue .cprj and replace it with cbuild.yml

We cannot remove .cprj as input for cbuild until we support the building from *.cbuild.yml files since cprj is currently the only option to rebuild from fixed versions (reproducible build use case).

I suggest to consider
-u, --update string          Generate *.cprj file for reproducing current build

for cprj input files, because csolution convert will always generate a cprj with fixed pack and component versions.
Therefore move under cprj: specific flags
Also we need to make sure people understand the --context / -c can occur multiple times to construct a context set.
We still need to decide on the exact command line option for replacing a context rather than adding a context.
--context-replacement

see: cmsis-toolbox 2.0.0-dev2


Add "bash" to tools/postinstall

When running yarn with git bash on windows, it errors with tools\postinstall' is not recognized.
Adding 'bash' before tools/postinstall resolve this.
Fixes: zulip#4427

Seems like we wanted to do a PR with this before, but didn't get around to it :sweat_smile:

I think we can just make this change in our package.json, so it'll be better for everyone, do you want to just make that PR?

I thought of that, but i don't know if these changes in package.json will have a diffrent behave on macOS or not. I think it's not since you asks.
On it.

Seems like we wanted to do a PR with this before, but didn't get around to it 😅

Yes,  i mentioned the issue to that 😃

@AlaaElden98 BTW when you're revising a PR after review, it's generally best to update the existing PR rather than close it and make a new one. See our docs here:
https://zulip.readthedocs.io/en/latest/git/pull-requests.html#update-a-pull-request

Thanks! I adjusted the commit message to match our style — you should take a look at it and try to match that style in the future. Specifically:

Add the area that you changed in front of the first line — package.json in this case (it's not always the name of a file, that's just what makes the most sense in this case, i think)
You don't need to describe what you did in a commit like this, since git show will show people that. Focus on describing why you made the changes you did, rather than what you did.

Thanks for finding this and fixing it, I'm sure future contributors will appreciate the smoother experience :)


Remove DHCP addresses from devices that change to static

working towards fixing #1705
needs testing on:

[x] Packet.net
[ ] Packet.net iPXE
[x] Digital Ocean - IPv4 looks good, IPv6 seems to have one right and one wrong - I presume its not removing (does the dhcp --remove only do the ipv4 stack?)
[x] AWS
[ ] GCE
[x] bare metal PXE
[x] bare metal installed
[ ] bare metal ISO
[x] vmware workstation
[ ]  virtualbox

Notes:
I've just used caddy to serve the vmlinuz and initrd from my cloud-dev build box, and then used a modified version of https://github.com/rancher/os/blob/master/scripts/hosting/digitalocean/cloud-config.yml  - I'm thinking of making make release spit out a version of that file (and a pxeconf file) so its easy to test.

Testing ~
look into the /var/lib/rancher/conf/metadata file and make sure that only the listed ips and gateways are actually the ones on the interfaces
if there are others, use dmesg (with rancher.debug=true) to work out what part of the ApplyNetwork code it comes from...

back to getting a test timeout :(

ok, this looks like its not making things worse, and it is removing the DHCP address from my baremetal.


[Bug]: Shipping description missing and payment description wrong.

Expected Behavior
Shippings method description to be available.
Payment's and shipping's methods to be correct.
Actual Behavior
Shipping method's description is missing.
Vendure passes us shipping's and payment method's descriptions as raw html and we render it as text which causes the description to be wrong - for example it starts with  and ends with . You can style you descriptions as well.
Possible Solution
Get the correct field for shipping description
Ue v-html instead of moustache
Steps to reproduce
No response
What version of vendure integration are you using?
1.1.0
What version of Node.js are you using?
14
What browser (and version) are you using?
safari
What operating system (and version) are you using?
macos
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Ah yes, we'd have to use whatever mechanism Vue provides to safely set innerHTML of a div so this gets rendered correctly.


[BUG][Functional] Failure to add static routes to TGW (unless TGW peered)

Required Basic Info

Accelerator Version:  v1.3.3
Install Type: Any

Describe the bug

When the TGW is not peered with another TGW
When 'static' routes are defined directly on the TGW, under routes
the routes are not created
the same routes are created on peered TGW's

** SECONDARY FIX IMPACTS **

the TGW peering ID is currently part of the logical ID
this fix removes this, as removing a TGW peer will cause a change of logical ID (when it should have no impact)
in this case, the route is re-created and causes a SM failure due to duplicate routes
upgrades to this PR, for customers with peered TGW's, requires first removing TGW blackhole STATIC routes from any peered TGW's before upgrade (this does not include blackhole attachments)

merged w/main, will ship in v1.3.4


Cap compat entries for all versions of a package EXCEPT the latest version

How to generate these changes
Step 1: Install the RetroCap.jl package:
] add https://github.com/bcbi/RetroCap.jl#master

Step 2: Clone the General registry and make a new branch:
git clone https://github.com/JuliaRegistries/General.git
cd General
git checkout -b yourinitials/retrocap-addcaps

Step 3: Run RetroCap with the NoUpperBound strategy:
julia> using RetroCap
julia> add_caps(NoUpperBound(), pwd())

I feel this need to a pretty detailed description of why this change is made. Changing the registry should be as rarely as possble so what's up with this wholesale upper bounding?

This is mainly a proof of concept implementation of @StefanKarpinski‘s suggestion on Slack from last week.
https://julialang.slack.com/archives/CBF3Z1D7V/p1573141684258100

here’s a stray thought: don’t require upper bounds on new versions, but whenever someone registers a new version, automatically generate upper bounds for all older versions based on the current claimed compatibility and what versions actually exist
so it’s fine to register<EMAIL_ADDRESS>with B = "≥ 2.3"
but then when you register<EMAIL_ADDRESS>regardless of whether it has an upper bound or not, you automatically generate a cap for<EMAIL_ADDRESS>based on what the current highest version of B is; for example, if B has a 3.4.1 version, then you would cap<EMAIL_ADDRESS>with B = "2.3 - 3" since that’s the next breaking release
the invariant that you want to maintain is that only the newest version of any package has no upper bounds
since that’s the situation that makes the resolver do bad things
that way people who are adamant about having upper bounds on their packages being literally the worst burden that anyone has ever been asked to bear in the history of the world, don’t have to


Invalid project.podspec file: no implicit conversion of Array into String.

How were you trying to build the app?
The problem arises when doing pod install.
It shouldn't be nothing hard to fix, i simply noticed that the ruby file generated by nitrogen contains the following
spec.source_files = current_source_files + [
    # Generated cross-platform specs
    "nitrogen/generated/shared/**/*.{h,hpp,c,cpp,swift}",
    # Generated bridges for the cross-platform specs
    "nitrogen/generated/ios/**/*.{h,hpp,c,cpp,mm,swift}",
  ]

Which cause the error if in my .podspec i have this
s.source_files = "ios/**/*.{h,m,mm,cpp}"

So i can easily fix the error by wrapping the sources in my .podspec with braces
s.source_files = ["ios/**/*.{h,m,mm,cpp}"]

Not a big deal but probably a case that was not considered
Full build logs
[!] Invalid `Podfile` file:
[!] Invalid `project.podspec` file: no implicit conversion of Array into String.

Project dependencies
"devDepdencies": {
 "react-native": "0.75.4",
 "react-native-nitro-modules": "^0.11.0",
}

Nitro Modules Version
0.11.0
Nitrogen Version
0.11.0
Target platforms
iOS
Operating system
MacOS
Can you build the Nitro Modules Example app?
I didn't try (⚠ your issue might get ignored & closed if you don't try this)
Additional information

[ ] I am using Expo
[X] I am using Nitrogen (nitro-codegen)
[X] I have read and followed the Troubleshooting Guide.
[X] I searched for similar issues in this repository and found none.

Fixed in https://github.com/mrousavy/nitro/pull/234 - can you check if that works for you?


requirement: "knplabs/knp-components"

I don't like the requirement "knplabs/knp-components".

i'll take a look if its solveable by a own interface

https://github.com/saxulum/saxulum-crud/blob/master/src/Pagination/PaginatorInterface.php


Update MTPDF.m

fixed bug: crash when date field is not standard
using NSDateFormatter rather than parsing date string manually

Hey, thank you very much for contributing. I'd very much appreciate some tests to show that this works and also consistent style/formatting with the rest of the project. Thanks!

I think I did it the way it was because after looking at a bunch of pdfs, the date format could vary wildly, so I tried to make it as flexible as possible, pulling whatever time/date info was there without baulking.

that's true but your solution doesn't provide additional format compatibility whereas with NSDateFormatter class there is more flexibility to add various formats. Indeed I've forced to use this way because your implementation did't recognise some of them.


Emit empty properties on each resource when not specified

Some resource types require a properties object to be specified, even if it's empty. For example, two I have recently come across with this behaviour are:

Function apps (Microsoft.Web/sites where kind=functionapp)
API Management product-API mappings (Microsoft.ApiManagement/service/products/apis)

I have had several customers run into issues with this, and the error messages aren't always very helpful.
Perhaps Bicep could emit a properties property on every resource, regardless of whether it's been specified?

I'm not sure we can do that. Just like there are resource types that require empty properties, there can very well exist resource types that fail PUTs with empty properties because they expect it to be omitted.
I think the options we have here are:

Pass through what the user specified in the .bicep file. (we're doing that today)
Generate or omit based on the swagger declaration for that resource type. If swagger is unavailable, fall back to 1.

@johndowns  - I don't think we can do this for the reasons Marcin outlined. I'm going to close, but let us know if we missed something.


HDDS-8659. Ozone admin SCM CLI command for block tokens

What changes were proposed in this pull request?
Introduce an Ozone admin SCM CLI command to force generate new secret keys (rotate).
Format: ozone admin scm rotate --scm hostPort
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-8659
How was this patch tested?
Added integration test cases.

@duongkame, @kerneltime, @sadanand48, @siddhantsangwan could you please take a look? Thanks

Format: ozone admin scm rotate --scm hostPort

I think the CLI should not rely on the admin to find the destination SCM, instead itself find the leader using the failover proxy, and only the leader SCM should accept this call, and process this call.
Also, the CLI can be divided into 2 usages.
ozone admin scm rotate
# this command only trigger a rotation if the the latest secret key timestamp already pass the rotate duration
# otherwise, it prints out a message to explain why rotation doesn't happen, e.g. `The lastest key was created at {lastest key timestamp} which doesn't pass the rotate duration of 1 day yet`.

ozone admin scm rotate --force
# force key rotation to happen now.

I think the CLI should not rely on the admin to find the destination SCM, instead itself find the leader using the failover proxy, and only the leader SCM should accept this call, and process this call.

The command should work even by skipping the --scm flag.

Also, the CLI can be divided into 2 usages.

Sure, will be making the changes for adding an explicit --force flag to the SCM CLI.

@tanvipenumudy CI runs in forks for each push.  There is some limit on the concurrent Github Actions jobs/workflows for each repo (although I don't know the details).  If you push in multiple batches, you might want to cancel runs for outdated versions of your code, otherwise the latest commits will be queued for a long time.

Thank you @adoroszlai, noted. Will be cancelling all the previous runs to enable quicker Git CI/CD checks over the latest commits.

Thank you for the reviews, I have addressed the comments on the PR.
The Git CI: integration (ozone) seems to fail at org.apache.hadoop.ozone.TestSecretKeysApi - but the test cases have been passing locally.

Thank you @duongkame, made the required changes to avoid exposing TimeoutException.


Metrics Explorer: Make human readable dates for line charts.

Needs design

Chatted with Dhiraj about this. The application design figma project has rough mockup on how we're going to handle this for 0.6.0.


Organization logos drag down page performance

As we originally tested YAWIK without a lot of logos, this problem did not show up earlier:
The loading of organization logos from MongoDB for use in the jobboard significantly drags down page performance. Not only is it terribly slow to start with (in our case load times of sometimes 2+ seconds per image), the problem is exacerbated by overwriting our usual caching header for image files (we usually send Cache-Control: max-age=31536000). Instead, YAWIK serves the logos with these headers:
Cache-Control: max-age=31536000, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Pragma: no-cache

The effect of this is all too visible in webpagetest.org under repeat view, e.g. http://www.webpagetest.org/result/160405_VB_PZA/
Without using a caching server such as Varnish, I see three options to improve YAWIK's jobboard performance:

storing the logo in the file system instead of in MongoDB
including some kind of caching mechanism in the file system for these logos
as a work-around: lazy-loading the logos using e.g. this very small JavaScript https://varvy.com/pagespeed/defer-images.html (thanks to @technopagan who made me aware of this - we currently use it on pages such as http://www.greenjobs.de/angebote/neueste.html)

I would like to use assetic for these issues
https://github.com/kriswallsmith/assetic

sorry, not closed

Thanks @cbleek
I had never heard of assetic. But it looks pretty good and should be able to solve our problem. Do you have experience with it? Would it be difficult to integrate it in YAWIK?
Btw: We switched on HTTP/2 server push, today. Now, all static assets are pushed to HTTP/2 capable browsers even before the HTML arrives. But this shows even more, how long it takes to serve the organization logos - here a video of the page loading in slow motion: http://www.webpagetest.org/video/view.php?id=160407_44c0efbdbd2ec9034f0c0ce697d7cb4af9f0c7fc
(Fortunately it also shows that the problem is not too big: The page is usable and looks good after 1.7s. And the reflow of the text in the rows - when the logos come in - is not too bad.)

This will be addressed with #298


Stats display a bit glitchy

Install method (Flatpak/Binary/Other)

Flatpak
BoxBuddy: 2.2.1

Distrobox Version
distrobox version: <IP_ADDRESS>
Your Host OS
openSUSE Aeon
Describe your Issue
There is a little long line below the stats of a container:

I just noticed it and did not made any further investigations as of now. Probably just some config missing on my end I assume?
After some investigation I found that the message appears also using podman stats but disappears after a short while. Hitting refresh in the UI however does still give the message shown.

I dont ever get this on Fedora :thinking:
Do you see this if you do:
podman stats box_name --no-stream --format '{{.CPUPerc}};{{.MemPerc}};{{.MemUsage}}' 2> /dev/null

Pushing something in 2.2.2 which will hopefully sort this.
I was able to recreate it on a Tumbleweed VM, but only with the flatpak

Pushing something in 2.2.2 which will hopefully sort this. I was able to recreate it on a Tumbleweed VM, but only with the flatpak

Ay I see. Yeah was about to answer that the command you posted does output no such messages. Many thanks for looking into it :heart:


Simplify parameter bindings

This update builds on #2343 and dramatically simplifies input parameter bindings, somethings that's always been rather complicated as we've attempted to model convertibility in Rust. Rather than depend on thousands of From and TryFrom implementations, types now implement the marker traits called CanInto and CanTryInto that do nothing but indicate to the windows crate that such types are convertible. The various Windows APIs can then rely on these traits to transform input arguments in the most efficient way possible, either casting directly to a parent interface (in a COM hierarchy) or calling QueryInterface when a conversion is expected (in a WinRT hierarchy).
The end result is a simpler abstraction with far less code. Specifically, it avoids generating around 7,000 From and TryFrom implementations. That amounts to a lot of functions that the Rust compiler doesn't have to parse, saving on build time.

Forgot to merge - I'll be back!


hi ur codebase is finecet d

You forgot .gitignore

I am...... Going to look up how to make prs into seperate branches instead of the one they're pring to. Lack of Git knowledge my beloved

I PEAKED

Yk now that I think about it. I definitely fucked up something while merging this PR the way I did because cy does not show up in contributors, assuming that pr author gets added to contrib list when pr is merged

So that's something I guess

lol what did you do to the commit history? This PR is naked!

pog merge

Yk now that I think about it. I definitely fucked up something while merging this PR the way I did because cy does not show up in contributors, assuming that pr author gets added to contrib list when pr is merged

I think you need to merge 2 prs


Replace module dependence 'tempfile' by 'tmp' #8

Fix #8

No thanks. You should generally not depend on environment variables being settable at runtime.


Fix indexes and add some other stuff

Changes:

optimize indexes and queries
chat posts when someone is added/removed from the chat
chat 'last_active' field that sorts the user's chats by the time it was last active

Manual DB changes:

drop all indexes from every collection
db.chats.updateMany({}, {$set: {last_active: 0}})

Commit was applied and only the last_active attribute was applied to the database since indexes yielded no results from Tnix's testing


Dependency package of display-notification version 2.0.0 having vulnerability (Versions of the package semver before 7.5.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range)

Describe the bug
Node.js version: 18.16.1
OS version:  Windows 10
Description: Dependency package of display-notification version 2.0.0 having vulnerability. Latest version of display-notification having fix.  Link https://security.snyk.io/vuln/SNYK-JS-SEMVER-3247795
Actual behavior
Expected behavior

Code to reproduce

Checklist

[ *]  I have searched through GitHub issues for similar issues.

[ *] I have completely read through the README and documentation.

[ *] I have tested my code with the latest version of Node.js and this package and confirmed it is still not working.

Is there any update on this issue. Can you please update the "display-notification" to the package >2.0.0.  We have facing the vulnerability issue in the nested dependency package (semver-5.7.1) of the<EMAIL_ADDRESS>Upgrading the "display-notification" package will resolve the issue.
Please help us resolve this.

Hi @titanism,
I have also security vulnerabilities due to display-notification at version  2.0.0, please upate to a newest version, the 2.0.0 has been released 8 years ago https://www.npmjs.com/package/display-notification?activeTab=versions

https://gitlab.com/gitlab-org/security-products/gemnasium-db/-/blob/master/npm/execa/GMS-2020-2.yml


How the heck do I turn preview content off in the editor?

Basically, ghost is becoming super slow on my browser when editing posts that are long(1000 words or more). I can't even type anymore because the preview part of the post is making my browser slow, I don't understand how a simple feature such as turn on/off the preview content can't be inside ghost.
How am I supposed to write long posts when my browser can't handle it. Did I miss the setting of how to turn it off, because I looked everywhere and I can't turn the preview off on the editor.

@IAlwaysBeCoding sorry to hear you're having trouble! Ghost version 0.8.0 (which will be released in a couple of days) contains a number of bugfixes related to the editor preview performance, which should help a decent amount with your issue 😄
If it's still a problem after that, this can be re-opened or re-formatted to be a proper issue.

@acburdine  Perfect then, I will wait for Ghost version 0.8.0 . Really great news, and thanks for the quick reply.Keep up the good work guys!


"Find a room" translation

The "find a room" placeholder cannot be translated because it's hardcoded.

Crap. Just noticed that the nl.json file was reformatted. Sorry. My bad.


Transaction list after edit lost group by date

When I edit a transaction, after saving, the transactions list will be reloaded.
Sometimes, not every time, the transactions list lost all group by date...
This is how should be:

This is how is bugged:

Same list, but all dates are disappear 😄

🤣🤣
after the reload...
after saving edit, reload is done every time, but the result changes sometimes 😅

I have an update... the grouping by is lost for the latest transactions, if I scroll down the other transactions are grouped... it seems that (more or less) only the last 10 transactions, or the last week's transactions lose groups it by...

ok, in case I investigate more and I open an issue on firefly repo 👍🏻

Sorry, I explained myself badly.. I meant that if there is a problem with the sorting and group by performed by the firefly API, I will open an issue there...
If the group by is performed by the firefly API, and is occasionally lost, there is probably a problem there..
Somewhere the group by is executed, and if you say that it is not your app that executes it, but it is the firefly API, it means that the firefly API requires investigation 😄
I'll turn on debugging and try to figure out what causes group by to be lost in some cases


Is it possible to use Vtk9.0.0

Is it possible to use Vtk9.0.0, since I know Vtk9.0.0 fixed many issues.

vtk9.0.0 should work, but vtk 9.0.1 not work.
I just compiled it with vtk from master, after fixing some small issues there is one left I don't know how to do at quickVtkFboOffscreenWindow.cpp:
auto FboOffscreenWindow::SetFramebufferObject(QOpenGLFramebufferObject *fbo) -> void {
    this->BackLeftBuffer = this->FrontLeftBuffer = this->BackBuffer = this->FrontBuffer = static_cast<unsigned int>(GL_COLOR_ATTACHMENT0);

    auto size                    = fbo->size();

    this->Size[0]                   = size.width();
    this->Size[1]                   = size.height();
    this->NumberOfFrameBuffers      = 1;
    this->FrameBufferObject         = static_cast<unsigned int>(fbo->handle());
    this->DepthRenderBufferObject   = 0;
    this->TextureObjects[0]         = static_cast<unsigned int>(fbo->texture());
    this->OffScreenRendering        = 1;
    this->OffScreenUseFrameBuffer   = 1;
    this->Modified();
}

So, from this commit some real changes must be made to compile with the latest vtk.

According to this issue on gitlab vtk it seems still possible to to this.But I don't know how.

Any solution yet? I'm facing the same problem.

Hey @danielbuhrig, I'm working on refactoring the project and set things up for VTK 9.0 but that will take some time. I'll keep this issue updated as development goes on

Cool, thank you!
On Thu, Sep 24, 2020 at 1:21 PM A. E. Szalo<EMAIL_ADDRESS>wrote:

Hey @danielbuhrig https://github.com/danielbuhrig, I'm working on
refactoring the project and set things up for VTK 9.0 but that will take
some time. I'll keep this issue updated as development goes on
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/qCring/QuickVtk/issues/56#issuecomment-698282000, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4IVZU2G2FCEIUXDWE4IW3SHMTVNANCNFSM4N7FRO2A
.

@qCring Did you make any progress here? I'm also at looking integrating using the QQuickFrameBuffer interface.  From your code, I believe the SetFrameBufferObject function needs to become something like the following:
    auto FboOffscreenWindow::SetFramebufferObject(QOpenGLFramebufferObject* fbo) -> void
    {
        vtkTextureObject* tex = vtkTextureObject::New();
        tex->AssignToExistingTexture(fbo->handle(), fbo->texture());
        this->GetDisplayFramebuffer()->AddColorAttachment(0, tex);
        this->Modified();
    }

After making this change, I'm having some problems with initializing the OpenGL state.
In OpenGLInitState the application is getting an Access Violation in vtkOpenGLState::Initialize() on the following function ::glBlendFuncSeparate(cs.BlendFunc[0], cs.BlendFunc[1], cs.BlendFunc[2], cs.BlendFunc[3]);.
Let me know if you've seen this, maybe we can help each other out.

Hi Jhuels
The initialization you get is most likely due to Qt initializing the
context using the message loop.
I had similar issues with this before and polled the application - process
events until the window is valid. If not all glXXX calls will segfault.
We are still stuck with 8.2 for other reasons, but I will soon move to 9.0
/Jens
On Tue, 10 Nov 2020, 22:12 jhuels<EMAIL_ADDRESS>wrote:

@qCring https://github.com/qCring Did you make any progress here? I'm
also at looking integrating using the QQuickFrameBuffer interface. From
your code, I believe the SetFrameBufferObject function needs to become
something like the following:
auto FboOffscreenWindow::SetFramebufferObject(QOpenGLFramebufferObject* fbo) -> void
{
    vtkTextureObject* tex = vtkTextureObject::New();
    tex->AssignToExistingTexture(fbo->handle(), fbo->texture());
    this->GetDisplayFramebuffer()->AddColorAttachment(0, tex);
    this->Modified();
}

After making this change, I'm having some problems with initializing the
OpenGL state.
In OpenGLInitState the application is getting an Access Violation in
vtkOpenGLState::Initialize() on the following function ::glBlendFuncSeparate(cs.BlendFunc[0],
cs.BlendFunc[1], cs.BlendFunc[2], cs.BlendFunc[3]);.
Let me know if you've seen this, maybe we can help each other out.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/qCring/QuickVtk/issues/56#issuecomment-724969089, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQJKYXPDVEY6NCAZ5S45I3SPGUCJANCNFSM4N7FRO2A
.

Thanks for the hint Jens!
I found out it was due to GLEW not being initialized before setting up the context state.  This can be solved by calling vtkOpenGLRenderWindow::OpenGLInitContext() before initializing the vtkOpenGLState.

@jhuels Did you means that you success to migrate to VTK 9.0?

No, I just used 8.2 cause it worked.  I had the same issue on both versions, so presumably you could get 9.0 working as well.


Feature request: Edit/delete reminder

As of the current version, I'm not able to edit, view, or easily delete a reminder. It would be a nice feature.

Thanks for filing a feature request! As of now you can delete a reminder simply by swiping the card to the left or right.
I initially didn't implement editing features because I assumed most people would just recreate a reminder and delete the old one. But since I now know there's demand for it I'll start working on it as soon as I have more time on my hands 👍

Any progress on that, or maybe pull request suggestions ???

Haven't had the chance to get into this one yet, but if you want to look into this go right ahead! Another feature that I haven't figured out is an archived task list or the ability to rearrange tasks by holding and dragging them across the screen instead of using one of the sorting options. Could be something interesting to look into!


Alert CI mailing list on nightly failures

Edd was kind enough to set us up a google group for recieving alerts on failing nightlies. The past couple of days we've had failures though so I'm not sure that the email address is linked to the CI server.
@karmel @av8ramit  Is it possible to alert<EMAIL_ADDRESS>on fails?

You are correct-- we had not set the email up yet. Sent out a fix; will update when it goes through. Thanks for noticing.

Currently our Travis CI alerts us of failures. Closing this for now unless we see a need in the future.


hyprpicker: 0.2.0 -> 0.3.0

Description of changes
Update hyprpicker to version 0.3.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 319229 run on x86_64-linux 1

3 packages failed to build:

grimblast
hyprpicker
xdg-desktop-portal-hyprland

See changelog https://github.com/hyprwm/hyprpicker/compare/v0.2.0...v0.3.0
Due to https://github.com/hyprwm/hyprpicker/commit/0e416939a172f1ea5f367cdba1490479dd6d4aec
Move to CMake based, so the package no longer builds.

Thanks, I did not check the source initially, I've fixed that up, now it doesn't use make and should build properly now


Open Images tag metadata is loaded in the wrong encoding

Not sure exactly where this is falling down, but the tag metadata needs to be more carefully ingested to get the encoding right:

Was hoping this would magically be fixed when loading the AWS database, but nope:
http://openledger-dev.creativecommons.org/ledger/detail/rdSaskZEfs7VhW6v4jBp0Q%3D%3D
Might be broken in the data too.


Improving usability of subscription

[x] Change the default behavior of DECLARE cursor_name SUBSCRIPTION CURSOR FOR subscription_name to SINCE now() without backfilling historical data.
[x] Change op column type from int16 to varchar to make it more understandable: 1 -> insert, 2 -> update_insert, 3 -> delete, 4 -> update_delete
[ ] When waiting for new subscription data to come, change the FETCH behavior from returning empty result to blocking (with an optional timeout) until new data arrives. This makes user easier to develop their application in event-driven manner. #18107
[ ] When user session is active (i.e. client-FE connection is alive), automatically retry querying log store on retryable errors, including cluster recovery, query stream timeout, transient network error between FE and CN.
[ ] more msg with show cursors https://github.com/risingwavelabs/risingwave/pull/18217#discussion_r1730629473

Feel free to post more ideas under this issue.

When user session is active (i.e. client-FE connection is alive), automatically retry querying log store on retryable errors, including cluster recovery, query stream timeout, transient network error between FE and CN.

Recently we found that if user declare a cursor but doesn't fetch it frequently, it may cause the query stream remain valid but unpolled for a long time. We may extend the above idea to actively shutdown idle query stream and re-create one from the previous pos in log store when the cursor is fetched again.


migrated to gradle 2.2.1

builds on openjdk-1.8
updated dependencies as far as possible (exceptions: guava, jetty)
broke 'ghpages' stuff - tried to fix but didnt manage.. commented out for now

We have a new netflixoss plugin that also switches to gradle 2.2.1 will take a look in the next week or so.

any news :question:

I'll make this second on my list to upgrade to the new build plugin today.
On Thu, Jan 29, 2015 at 6:55 AM, Tom Hensel<EMAIL_ADDRESS>wrote:

any news [image: :question:]
—
Reply to this email directly or view it on GitHub
https://github.com/Netflix/exhibitor/pull/207#issuecomment-72037644.

looking forward..


How to resolve "Unable to find version 0.13.3-build02496 of package Microsoft.ApplicationInsights.WindowsStore" Error

Dear,
I Open WindowsIoTCorePi2 on Windows 10 Build 10074 with Visual Studio 2015 RC Enterprise, and VS can't build the solution because of the following reason. Would you please help me to fix this? Thanks!

I have W10 Build 10122 and experiencing the same issue.

Closed due to back of activity. Please re-open if needed.


Key switch state & maintain power functionality

As defined in ISO11783-7 and here, it is possible to make requests to the tractor ECU to maintain (ECU) power for another 2 seconds. This could be helpful when your application needs time to shutdown.
Do we want to implement this on the stack side? E.g. where you can register an (async) listener for when the key switch is turned off, and the stack makes sure the power stays on for as long as the listener(s) are busy? Probably with a (configurable) timeout of like 30 secs, incase the listener(s) accidently come into an unrecoverable state.

Or, we keep requesting to maintain (ECU) power until the CANHardwareInterface is stopped. And then you'd keep running your application loop for as long the key-switch is turned on. After which you do the shutdown logic and finally stop the CANHardwareInterface. Though I image this should be optional behavior that is by default disabled. Since otherwise you might unintentionally and unknowingly keep the power up... Just thinking out-loud here.

It might as well be one layer down, where the logic is in the CANManager instead of in the CANHardwareInterface. The same logic applies I think. Since it then would be in the core of the stack, the functionally also is available to applications not using the CANHardwareInterface 😄


fix: registry add insecure options

What type of PR is this?

/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #705
Special notes for reviewers:
None

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

None

/lgtm

/cherry-pick release-1.4


Fix TransformMany

Fixes #173
Added Transform interface with transformOnRefresh to cache extensions (similar to list)
Changed TransformMany in SourceCache:

enable transformOnRefresh if without childChanges
added ToList() to force calculate Select, else Previous items and Current items will be equal
in case when there is childChanges there was strange applying of lock - Select was iterated outside locked area

Do I need to make transformOnRefresh optional for TransformMany and add it to interface?
Probably similar stuff must be done for SourceList.
I think, that I have messed up with lock

Added fix for list's TransformMany
For SourceList:
Does list's ManyContainer need the same logic by wrapping destination in Func is needed?
For now iterating IEnumerable is done without lock.

Super awesome effort. Much appreciated. I will be back from vacation soon and will take a very detailed look at this.


allow consecutive newlines in jsdoc tag comments

Fixes #35511
The parser for JSDoc tag comments currently skips successive NewLineTrivia tokens.
In files using CRLF line endings, this leads to only \r being retained in the node, which can cause issues for tooling.
This PR removes that restriction, such that all NewLineTrivia tokens are persisted in the node.

This has been merged with master after your changes.

@typescript-bot pack this


Modernize examples

Description
Chipping away at some of the C++17 items mentioned here. I also found an easy way to simplify the CMake code for all the examples that should help improve readability and maintainability.
I ran the Tennis, Island, and Shader examples on macOS and could not observe any different behavior.
Tasks

[x] Tested on Linux
[x] Tested on Windows
[x] Tested on macOS
[x] Tested on iOS
[x] Tested on Android

I found a new solution to the most vexing parse that was forcing me to initial variables with =. Instead I just make a new local variable for the random device. This means we can continue to match SFML's style of not using auto.

This means we can continue to match SFML's style of not using auto.

Is that our official stance? Certainly not my personal preference... :)
@eXpl0it3r

For the record I'd also prefer we start using auto where there is technical merit and potentially go so far as dictating that all future patches use auto for all variable declarations. I haven't already used it because I wanted to make sure my patches blended into SFML as well as possible.

For the record I'd also prefer we start using auto more often and potentially go so far as dictating that all future patches use auto for all variable declarations.

Direct question: why? 🙂

Direct question: why? 🙂

For starters, it's not a big deal and I'm fine sticking with the current style since there's so much inertia behind it. There are many other things I'd rather the team focus on than my preference to use auto.
That being said, here's why I like auto for variable declarations:

Requires that you initialize the variable
Easier to visually scan for variable declarations (somewhat subjective, but true for me personally)
I just think it's prettier (this is absolutely subjective lol)
Impossible to encounter the most vexing parse
Reduces the likelihood of accidentally making implicit conversions
Lets the compiler automatically propagate type changes throughout the codebase with less effort on our part

SFMLBuildMaster: Build this please.

Addressed a comment and added a missing header that was breaking one of the extended CI jobs. This PR is good to go now.

SFMLBuildMaster: Build this please.

Looks like I fixed the last failing CI job 👍

🥳

Is that our official stance? Certainly not my personal preference... :)

I'm an AAA (Almost Always Auto) kind of person, but I'm aware that it's controversial.


Prepare manual reviews for programming exercises

Only allow manual reviews for passed due dates and SEMI_AUTOMATIC assessments
Add grading instructions to programming exercise update component

Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[x] Server: I added multiple integration tests (Spring) related to the features
[x] Server: I implemented the changes with a good performance and prevented too many database calls
[x] Client: I documented the TypeScript code using JSDoc style.

Motivation and Context

In preparation of manual review for programming exercises, we need the possibility to add grading instructions when creating a programming exercise.
It is also important that the button for adding a new result (i.e. a manual review) is only enabled for programming exercises, if the assessment type is SEMI_AUTOMATIC and the due date  (or after due date) has passed. The same goes for the result endpoints. Those should return forbidden in case the above mentioned requirements are not met.
Description

I added a markdown component for adding grading instructions when creating/editing programming exercises, that only is enabled once the instructor clicks on "Manual Review" in the exercise timeline.
The button for creating a new result is also only displayed if the above mentioned conditions have been fulfilled.
Steps for Testing

Log in to Artemis
Navigate to Course Administration
Create a new programming exercise and enable the manual review
You should be able to add grading instructions
Set a due date
The new result button on the participations overview should only be visible once the due date is in the past

@ungaralex in case you received a notification, please ignore my last comments. I was looking at outdated code


Init: Variant Ant gtk themes 1.3.0

Motivation for this change
The Ant GTK theme is already packaged but there are 3 variants which can be packaged identically.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I have probably massively overengineered this so sorry in advance

I'm going to redo this in a way that isn't silly


The mongo driver is required in order to build GridFs.

CMake Error at CMakeLists.txt:51 (MESSAGE):
The mongo driver is required in order to build GridFs.

for centos ned to install dependancy using below command
yum install mongo-c*

@dipenpatel235 I still get this message, even though I've installed "sudo yum install mongo-c*"


cargo update and fmt examples

formatting consistency using nightly features

Running rustfmt and clippy  make sense. I wonder if a rustfmt config file is really necessary. I'd prefer to keep the default configuration (avoiding the rustfmt config file). The most important config option is probably edition. This one is, however, set automatically when using cargo fmt
Could your re-run rustfmt with the config file removed and commit again?

Fair enough, I will update with a commit

done, thanks

thanks a lot for this contribution


docs: fix lib.io link

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

v7.2.3
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Question]: how should I optimize it in the production environment to ensure stability?

Describe your problem
./entrypoint.sh: line 25: 18337 Killed                  $PY api/ragflow_server.py
[WARNING] [2024-06-24 07:59:24,499] [synonym.init] [line:24]: Realtime synonym is disabled, since no redis connection.
SUM: [WARNING] Load term.freq FAIL!
____                 ______ __

/ __ \ ____ _ ____ _ / // /  _      __
/ // // __ // __ // /   / // __ | | /| / /
/ , // // // // // /  / // // /| |/ |/ /
// || _,/ _, ///    // _/ |/|_/
/____/
[INFO] [2024-06-24 07:59:36,021] [_internal._log] [line:96]: WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.

Running on all addresses (<IP_ADDRESS>)
Running on http://<IP_ADDRESS>:9380
Running on http://<IP_ADDRESS>:9380

The process was killed, how should I optimize it in the production environment to ensure stability?

No less than 64G RAM, more than 16G GPU mem, multiple nodes of ES cluster.
That will work.

My resources meet the requirements, but the system is still being killed with 5 concurrent requests, and the response time exceeds 40 seconds. At this point, the system resource usage is not high.


feat(datepicker): Datepicker prototype

Note, its nessecary to run yarn packages:build for tailwind to build in the packages, and for the build.css file to become available
Adds a new datepicker component, that supports both dates and times. Its possible to configure to use minutes or not for the times, and if the time should be dropped altogether.
Still a few minor things to iron out, but I'd like some feedback on this, both on the usability, and if there are some things that can be optimized code-wise.
Note: This PR relies on the #744 PR for styling, hence the file additions.

Did not figure out how to get back to date select after changing year


support for windows paths when retrieving wnid from path

Looks good, thanks!
Would you like this package to be registered?

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Please upload report for BASE (main@e6c3adb). Learn more about missing BASE report.

Files
Patch %
Lines

src/utils.jl
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #13   +/-   ##
=======================================
  Coverage        ?   42.06%
=======================================
  Files           ?        5
  Lines           ?      126
  Branches        ?        0
=======================================
  Hits            ?       53
  Misses          ?       73
  Partials        ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update vendored vault-unsealer to latest released version

We are hard coding a commit for vault-unsealer. We should upgrade that to the latest released version.
https://github.com/jetstack/tarmak/blob/master/Gopkg.toml#L48
Also check if we are using the latest version in the terraform
Run a full cluster apply to verify the changes (no automated E2E yet)

This is where you can find it in terraform: https://github.com/jetstack/tarmak/blob/master/terraform/amazon/vault/templates/vault_user_data.yaml#L304

This has been fixed


change feed directly invokes sproc?

Dp you mean the Change Feed (running with a slight delay after the original insert/update, and not in the same trx) can directly invoke a sproc, without the need for an azure function?

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

ID: 669528a7-38dc-a6a9-f98f-4cbb91fd44e0
Version Independent ID: 5e5fcb52-86e8-7e08-6209-79f9ce5e2a91
Content: How to model and partition data on Azure Cosmos DB using a real-world example
Content Source: articles/cosmos-db/how-to-model-partition-example.md
Service: cosmos-db
GitHub Login: @ThomasWeiss
Microsoft Alias: thweiss

@deyanp Thanks for reaching out to us. We are looking into this and will get back to you shortly.

@deyanp No, there is no such capability. In this example, the change feed would indeed trigger an Azure Function that calls the stored procedure.
#please-close


Removing the stable repository

The stable repository provides a quick on-boarding with a set of
community curated charts. Two problems with the community stable
repository has lead to its need to be removed.

The URL is hard coded to a Google Cloud bucket under Google's
control. This was setup when Helm was part of Kubernetes and
Kubernetes was a Google project. The bucket cannot be
transferred to another non-Google controlled project. And,
the bucket is not accessible in some parts of the world
(e.g., China).
The number of charts in the stable repository has grown
generally unmaintainable. The repository maintainers cannot
manage the number of PRs coming it cauing delays in response
or no response and PRs are automatically closed. This is
a poor experience.

The alternative is the Helm Hub that provides a central point of
search for many Helm repositories. Different people and organizations
can maintain their own charts. A central server is not needed as
Helm is setup to be distributed.
cc @helm/charts-maintainers

This looks good to me. Do we already have a deprecation plan for the charts repository? Is there a doc maybe?

The v3 docs may need an update as well since the stable repository is a commonly used example. Would you be willing to update helm-www as well, or would you mind filing a ticket for that?

@maorfr When helm v2 is deprecated at the earliest. That timeline is up for discussing in the next Helm Dev Call.
@bacongobbler I noticed that. I wanted one PR to land at a time. I have a few in flight. I'll get to that unless someone else wants to.

What happens with the existing charts that A LOT of users depends on? Will they be migrated to Helm Hub? Where is Helm Hub? ( https://hub.helm.sh/ I assume? )
Please make follow up issues for chart owners to migrate their charts before you remove anything please, to avoid chaos and angry helm users.
cc @helm/charts-maintainers

@norrs this just removes stable as a default repository, it can still be added manually with helm repo add stable https://kubernetes-charts.storage.googleapis.com


Refactor: make InjectedPluginSource.PluginFactory private.

@muga Just refactoring. It is unnecessarily public. PTAL?

Thanks!


Naming report files?

Hi! I'm curious, is it possible to set the name of the coverage report file being produced?
For example, I have the following .nycrc.cobertura.json configuration file (for one of my tests, the other test has one but has a different report-dir), this produces a file called cobertura-coverage.xml. I will be running two test frameworks and would like to name these reports differently. Is this possible? As stated, I currently need to have the report-dir different for both tests, which is a bit ugly:
{
    "extends": "./.nycrc.json",
    "all": false,
    "report-dir": "./coverage_production/server",
    "reporter": ["cobertura"],
    "include": [
        "build_production/server/**/*.js",
        "server/**/*.ts"
    ]
}

@basickarl :wave: hey; I understand it's potentially a bit messy, but I think that either using two different report directories, or as an alternative running the first set of tests, moving the reports into a final location, then running the second set of tests is your best bet.
There's already quite a bit of flexibility around managing where temporary files and reports are located, I don't think (as a project) we want to extend this to the files generated by specific reports. nyc supports many reporting formats, and I feel this would ultimately turn into a painful number of configuration options.
Hopefully you can figure out a reasonable work around?


No email address confirmation during sign up

When creating an account, no confirmation email is sent, and it is not needed to start log in and using the account.
We need to implement that before starting to have more users.

Should be fixed. PR is: https://github.com/codalab/codabench/pull/751


[Bug]: The Logic of the  Showing weekness is wrong please improve it.

Contribution guidelines

[X] I've read the contribution guidelines and wholeheartedly agree

Description
The logic which is written for weakness card to populate has to be modified
Expected behaviour
The logic which is written for weakness card to populate has to be modified .
Actual behaviour
Check the Code QL Snyk and Sonar Qube -> get all the vulnerability details -> Remove Duplicates -> Display
Steps to reproduce
See the BesLighthouse code
Relevant screenshots
See the BesLighthouse code
What browsers are you seeing the problem on?
No response
Relevant log output
No response

@sumodgeorge FYI


Fix portability for bash and sh

@Rpinski could you take a look?

I'm very sorry for ignoring your pull request for such a long time! Thank you for contributing!


npm audit reports issue for lodash dependency

Running npm audit on this project shows a moderate vulnerability for lodash < 4.17.11 (https://npmjs.com/advisories/782)

that PR solved the issue, but for some reason (outdated) it was closed
https://github.com/kimmobrunfeldt/chokidar-cli/pull/58

This is a newer vulnerability (than that related to the PR originally). Let me fix this today

And it's out as v1.2.2


Use CITATION.cff instead of Qiskit.bib

What is the expected behavior?
Recently, GitHub supports cff format for citation.
https://citation-file-format.github.io
How about using cff?

Yeah but then I need yet another package to get the bib file that I actually need.  I also do not think that a single one of these would be enough.  More like one for the core of Qiskit and then another for individual applications.
Also, it does not really solve the Authorship issues https://github.com/Qiskit/qiskit/issues/1273 that popup in our current solution.

There was some discussion of how to add support for this in https://github.com/Qiskit/qiskit/pull/1322 . (.bib files are also apparently supported.)

I'll close this as stale now, since there never seemed to be a huge amount of support for using this CFF format.  We can re-open this on the relevant component repos, if people are more in favour of it again in the future.


AtlasEngine: Harden against invalid soft fonts

This is a theoretical improvement for #15553 where Windows Terminal
crashed due to AtlasEngine accessing the soft font bitmap outside of
bounds. The problem is that the soft font cell size was non-zero.
This PR hardens against such situations by checking whether the
requested soft font index is inside the bounds of the bitmaps.
The improvement couldn't be tested as it couldn't be reproduced.

I just realized you're using GPT generated content. Not appreciated. 🙂


python3Packages.sfepy: 2021.4 -> 2022.1

Description of changes
Update Sfepy
ZHF: #172160
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@jonringer @FRidh, commenting to get this noticed. It fixes a current failure on master and, thus, will contribute to ZHF: #172160 after a backport.
Result of nixpkgs-review pr 167582 run on x86_64-linux 1

2 packages built:

python310Packages.sfepy
python39Packages.sfepy


Add tb_poll_fds() to obtain file descriptors for polling

This adds a function to obtain file descriptors from termbox that can be be polled for IO-readiness.
This can be used to integrate termbox into an event loop like asyncio or curio in python, or libuv in C, so the program can process other things (like network sockets) asynchronously with UI events.
The idea is to use tb_poll_fds() to get a set of descriptors, register them for polling (e.g. with EPOLLIN), and when any events arrive, the next tb_poll_event() can be expected to complete quickly.
(edit: markdown formatting and C usage example)

Any feedback/requests on this?

Sorry for not responding. As you can see this project is not exactly well maintained. I'm sure main loop issues are relevant for the C world as what is offered is not perfect. But yeah, I don't think I have time for any sensible project maintenance right now. Feel free to keep the changes in your own fork if you need them.
I should probably add a note to README that this project is no longer maintained.


English updates

Fixed and reworded the text. Not sure why the github diff shows such a large block of difference between lines 22 and 46 as there usually are only a few words changed every couple of lines (as in the rest of the doc).
Additional notes:

Please very that lines 64-65 retained the correct meaning. This section was not that clear.
Should the pros/cons be swapped in the 'Alternatives Considered' section? The Pro's read like cons and vice versa...
In the algorithm description is the mention of 'line 11' correct? Should that not be either line 12, or line 9?

Fix Irregular writing and expression issues.


Livewire 3

Bug description
Since I upgraded to Livewire 3 pages with livewire components keep reloading.
Livewire 3 removed "Livewire Endpoint Middleware Group"  from app/config/livewire.
So thinking the issue lies there. But I have no Idea how to fix it, any ideas?
Steps to reproduce
Install/upgrade Livewire 3.
Expected behavior
Components working correctly
Laravel version
10
stancl/tenancy version
3.7

Solved it by adding:
`
use Stancl\Tenancy\Middleware\InitializeTenancyByDomainOrSubdomain;
use Stancl\Tenancy\Middleware\PreventAccessFromCentralDomains;
use Livewire\Livewire;
Livewire::setUpdateRoute(function ($handle) {
return Route::post('/livewire/update', $handle)
->middleware(
'web',
InitializeTenancyByDomainOrSubdomain::class,
PreventAccessFromCentralDomains::class,
);
});`
to "TenancyServiceProvider.php" inside the protected function mapRoutes() method!


Hire a community manager

[x ] Write job description
[ ] Feedback from lib-personnel
[ ] Submit to Central HR
[ ] Put together a Recruiting Advisory Committee (RAC)
[ ] Post and recruit
[ ] Interview
[ ] Hire


Latest UPS w/ WildFly 12

Updating to UPS/WF12 combo
Reviewers,  can you test-run this ?
See README on how to run the combo !

Looking


Closes: #1

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Finally we accomplished it @google-admin