No licence?

Your MIT licence on README.md badge link leads nowhere, please update it.
https://github.com/anseki/leader-line/blob/master/LICENSE-MIT

Created PR https://github.com/anseki/leader-line/pull/351

Hi @Nurech, thank you for the report. :smile:


Simplify callback activityId regex

After some testing, I am afraid that we will need another release after all.
The Hub returns a string like this:
errorCode=200:errorString=OK:activityId=18635065
and it turns out that different firmware versions do not use the same
order of those fields. This commit simplifies the matching to just the
minimum that is needed, hopefully making it resilient to future changes.

Thanks for the update, this PR and your previous PR is included in 1.0.18

That was fast, thank you!


tree-wide: add missing parent icon themes

Motivation for this change
Icon themes may inherit from other icon themes. The inheritance is specified using the Inherits key in the index.theme file.
According to the icon theme specification that means that icons not provided by the theme are looked for in its parents. The idea is that missing icons are looked for in the parent icon themes, in the order specified.
Therefore the parent themes should be installed as dependencies for a more complete experience regarding the icon sets used.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] 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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I have tested with propagatedBuildInputs and with propagatedUserEnvPkgs in a VM configured with the startx display manager and the fluxbox window manager. I have listed the files in /run/current-system/sw/share/icons. I have also looked at the themes with the application lxappearance. The only theme explicitly installed was papirus-maia-icon-theme (using environment.systemPackages).
Only with propagatedUserEnvPkgs the parent themes were made available automatically.
The following screenshots illustrates the results.
With propagatedBuildInputs:

With propagatedUserEnvPkgs:

I think this is conclusive.

I think it might be preferable (even though ugly) to symlink the inherited themes into the output. Relying on propagatedUserEnvPkgs is just too big of a violation of encapsulation and purity for my taste.

If symlink works, than this should be the preferred solution.
In future a setup-hook that scans index.theme performs the symlink on its own might be the way to go.

I think it might be preferable (even though ugly) to symlink the inherited themes into the output.

Won't this result in collisions if the parent theme is installed separately? (That might be fine, they're the same content after all).

Testing with symbolic links in papirus-maia-icon-theme with both papirus-maia-icon-theme and breeze-icons in environment.systemPackages:

Collisions are reported at build time:
$ nixos-rebuild build-vm --show-trace --option sandbox true -I nixpkgs=/alt/nixpkgs -I nixos-config=/alt/nixos/configuration.fluxbox.nix 2>&1 | tee /var/tmp/nixos-rebuild-vm.log
building Nix...
building the system configuration...
these derivations will be built:
  /nix/store/1cspvw79b958fsw7073d2cxw55ylj6bc-system-path.drv
[...]
building '/nix/store/1cspvw79b958fsw7073d2cxw55ylj6bc-system-path.drv'...
collision between<EMAIL_ADDRESS>and<EMAIL_ADDRESS>collision between<EMAIL_ADDRESS>and<EMAIL_ADDRESS>collision between<EMAIL_ADDRESS>and<EMAIL_ADDRESS>collision between<EMAIL_ADDRESS>and<EMAIL_ADDRESS>collision between<EMAIL_ADDRESS>and<EMAIL_ADDRESS>[...]
collision between `/nix/store/bq8hnk8n1xyy18nmwd7mf78kirs2s0d9-breeze-icons-5.68.0/share/icons/breeze/places/64/folder-downloads.svg' and `/nix/store/89bsafcnz0a6r1wfaiifvmsnbh6ccnxz-papirus-maia-icon-theme-2019-07-26/share/icons/breeze/places/64/folder-downloads.svg'
created 39920 symlinks in user environment
gtk-update-icon-cache: Cache file created successfully.
gtk-update-icon-cache: Cache file created successfully.
gtk-update-icon-cache: Cache file created successfully.
building '/nix/store/ylzwcnfziq0sh9h2cdcxdxq89s5i4app-dbus-1.drv'...
building '/nix/store/0ggf9zbx6ackvk98fqkyr4ccyy1lx747-unit-polkit.service.drv'...
building '/nix/store/q6n9wsd55dvpqnr3d3xh7fj1jprf8pzm-unit-systemd-fsck-.service.drv'...
building '/nix/store/93i3jmhp60v3xxavm22fn8d571ljy4dz-unit-dbus.service.drv'...
building '/nix/store/scjf25hizm5c8lyl9fdbsjnaaxclgxyx-unit-dbus.service.drv'...
building '/nix/store/f73af23ffjps3iw9l7m48k39fqm8dqir-system-units.drv'...
building '/nix/store/kwnp8n3jczl3wmim25mixbl178478xa8-user-units.drv'...
building '/nix/store/44rvwlz38pjra1bryds6qr0dy0svmlk0-etc.drv'...
building '/nix/store/1crsvb182anj0b9was6bqgdjxqs1yv9v-nixos-system-nixos-20.09pre-git.drv'...
building '/nix/store/rg3qf72c3xcvzygc16050jf68q7rrfsw-closure-info.drv'...
building '/nix/store/zxzpd7zcpmskib7yjcg3xi1h0havalkw-run-nixos-vm.drv'...
building '/nix/store/afqj6dvskdb2hf0962yiz76qv6mkm0mq-nixos-vm.drv'...

Done.  The virtual machine can be started by running /nix/store/088zz2r26xw8vj61kmrrcfcp3h173vzn-nixos-vm/bin/run-nixos-vm

Should I go on and implement this solution for all icon themes?

Using symlinks has one complexity: indirect inheritance. It would be needed to symlink also the parent themes from the parents, and so on, up to the inheritance root. This is not implemented yet in this PR.
Also I am not liking the number of collisions.

cc @worldofpeace

Now there is a setup hook in hicolor-icon-themes that, for each installed icon theme, finds its parent themes by looking at theme.index. Then each parent theme is searched among the dependencies. If found the theme directory is linked at $out/share/icons.
The dependencies providing parent icon themes should be propagated.
It works for indirect inheritance.

I like the approach @jtojnar has suggested here, I also really don't favor using propagatedUserEnv. But I'm honestly not sure, what was the margin of encapsulation and purity we even wanted out of icon themes in nixpkgs?

The dependencies providing parent icon themes should be propagated.
It works for indirect inheritance.
I have also tried to fix all packages providing icon themes in nixpkgs in order to indicate the dependencies needed to find the parent themes.

I think this is something we should document in the gnome section in the nixpkgs manual.
@jtojnar do you think backporting https://github.com/NixOS/nixpkgs/pull/85229/commits/682734d8526d9cbb273c0c4d0e12aaa6ebb7897f would be a good idea for 20.03?

Also I am not liking the number of collisions.

These collision warnings have always been annoying, :smile: even if this introduced some.
I don't think there is a way to avoid that, unless we just make it be quiet in general.

Fixed merge conflicts.

This is approved @romildo but we need to target staging since this appears to be a mass rebuild.

This is approved @romildo but we need to target staging since this appears to be a mass rebuild.

@worldofpeace Targeting staging introduces some file conflicts. I suppose I have to fix them. Any direction on how to do it?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/proliferation-of-symbolic-links-in-run-current-system-sw-share-icons/7587/1


[Gh 1570] feature flag for table metrics

Feature or Bugfix

Feature

Detail
Using existing functions like is_feature_enabled to enabled / disable use of metrics and associated profiling jobs.
Relates

https://github.com/data-dot-all/dataall/issues/1570

Security
Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

Does this PR introduce or modify any input fields or queries - this includes
fetching data from storage outside the application (e.g. a database, an S3 bucket)? N/A

Is the input sanitized?
What precautions are you taking before deserializing the data you consume?
Is injection prevented by parametrizing queries?
Have you ensured no eval or similar functions are used?

Does this PR introduce any functionality or component that requires authorization? N/A

How have you ensured it respects the existing AuthN/AuthZ mechanisms?
Are you logging failed auth attempts?

Are you using or adding any cryptographic features? No

Do you use a standard proven implementations?
Are the used keys controlled by the customer? Where are they stored?

Are you introducing any new policies/roles/users? No

Have you used the least-privilege principle? How?

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

@dlpzx , @noah-paige , can you please take look at this PR. It is to disable/enable the metrics for dataset tables - https://github.com/data-dot-all/dataall/issues/1570

@TejasRGitHub there are some conflicts to resolve, but overall the feature looks good

@dlpzx , updated branch to resolve merge conflicts in config.json. Thanks for reviewing and approving


The Reported Contents Filter is duplicating/showing old values

Describe the issue/bug:
The old value of both reported user and reported by input is appearing after changing the search
To Reproduce:

Go to brainly.com.br/question/add?reported-contents
Search for a Nick on reported by or reported user input
Replace the nick with a rank

Also, sometimes the content length (RegExp) and Special rank filter is duplicated and breaks the page layout, like this

https://brainly.com.br/perfil/Alphka-14558160

Hey @Alphka
Can you confirm this issue still persist after the version 7.21.0? Let me know please

Hey @Alphka
Can you confirm this issue still persist after the version 7.21.0? Let me know please

Hi Sahin!
Yes, this issue is still happening here.

Hi Sahin!
Yes, this issue is still happening here.


scalajsc fails on windows upon first invocation

The first invocation after scalajsc has been added to the path, it seems to not find the Scala.js library (log follows). The next invocation works as expected.
How to reproduce (use foo.scala from test cases):
> set PATH=%PATH%;<...>
> scalajsc foo.scala

After over three years, I think we can safely say no one cares :)


support for uint64_t values for fields

Hi
I am getting errors for supporting uint64_t values insertions into influxDB
What is your suggestion to fix this?
test.cpp:122:114: error: cannot convert ‘long long unsigned int’ to ‘const std::variant<int, long long int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, double>&’
  122 |  db->write(influxdb::Point{"pooya"}.addTag("guid","2032489038270972513").addTag("port","5").addField("rcv_data", (unsigned long long int)18446744073709551615).addField("unicast_xmit_pkts",2072512).addField("unicast_rcv_pkts", 2512).addField("multicast_xmit_pkts",55805).addField("multicast_rcv_pkts",29));
      |                                                                                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                                                                                |
      |                                                                                long long unsigned int
In file included from /usr/local/include/InfluxDB.h:38,
                 from /usr/local/include/InfluxDBFactory.h:31,
                 from test.cpp:32:
/usr/local/include/Point.h:55:106: note:   initializing argument 2 of ‘influxdb::Point&& influxdb::Point::addField(std::string_view, const std::variant<int, long long int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, double>&)’
   55 |     Point&& addField(std::string_view name, const std::variant<int, long long int, std::string, double>& value);
      |                                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~

addField() doesn't support unsigned types yet. If your values fit into a int64_t you can cast them.

Following up on this. Have you implemented the support for unsigned types?

Not that easy as both overloads become ambiguous.


Documentation Update Centos Python Dependencies

Describe the bug
If you try and install using the recommended "pip3 install locust" on Centos 7 (and 8 as far as I can tell) the install fails. You need to make sure you have "gcc" and "python3-devel" installed first and then do "pip3 install locust --user"
Environment

OS: Centos 7/8
Python version: 3.6
Locust version: (please dont file issues for anything but the most recent release or prerelease builds)
Locust command line that you ran:
Locust file contents (anonymized if necessary):

Actually, this should work (because there should be a prebuilt version published to pypi, but there isnt!)
Investigating...

(there is an entry in the installation wiki about this specific problem, and that is linked from the installation instructions, but it should not be required for normal cases)

Ah, I found the issue: geventhttpclient has no wheels for python 3.6

Fair enough. Shall I put in a pull request to update the documentation?

Nah, I think it is not worth mentioning, as it shouldnt be a problem for 99% of users. If you want you can expand the explanation in the wiki-entry though.


Checking a possible git problem

Just checking: there seems to be some problem with my signature.

Fixed now.


Add reports for students with enrichment options out of availability

It's possible to update the enrichment options for slots after students have been assigned. As such, we need to report to check on this scenario

Commit c8e3df18b7a1f55ef497d91fe4c49d879a969ff1 adds a very preliminary version of this on the weekly report. It should be probably be added to an email as well.


Things displayed state

things, gui state information will be stored in the individual pico with a cash in the manifold pico.
manifold web app will update thing picos directly. the thing pico will then send events to the manifold pico to update a cash of information. While most information will be stored in the thing pico, specific app data will only persist in manifold pico, for example, tile position.

Duplicate of #10


Feature: file.copy should support downloads

It's pretty common to want to download software (or maybe config) from http, even ftp.
wget can be run from command.run, but you have to dump it in /tmp etc etc.
It feels nice to model this by supporting http etc URL schemes in file.copy (file:// can be the default in the case of no scheme)

@mt-inside I added a HttpDownload atom recently that would provide the basis for this. I'll work on adding a user facing action for it this week 👍🏻

@mt-inside file.download action will be available shortly 👍🏻


Não estou conseguindo fazer modificações nas configurações, tudo que eu troco aparece essa frase "Não é possível gravar nas configurações do usuário. Abra as configurações do usuário para corrigir erros/avisos e tente novamente." e não salva.

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

I'm not able to make changes to the settings, everything I change appears this sentence "Unable to record in user settings. Open user settings to correct errors / warnings and try again." and does not save.

Your settings.json file seems to have been corrupted. Remove the large block of code and return it to being valid JSON.

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


ISPN-1556 Do not rollback tx if it fails and marked as FAIL_SILENTLY

https://issues.jboss.org/browse/ISPN-1556
Fix a potential NPE too.

Thx Mircea. I saw your dev email reply after I had commented here.


KAFKA-15602: revert KAFKA-4852

This PR reverts

https://github.com/apache/kafka/commit/51dbd175b08e78aeca03d6752847aa5f23c98659
https://github.com/apache/kafka/commit/496ae054c2d43c0905167745bfb2f4a0725e9fc2

Also added some JavaDocs to ByteBufferSerializer to explain the contract.

I would focusing on reverting -- if we want to update tests, we can do it in a separate PR?

@showuon Considering this for 3.5.2 bug-fix release. (Given that we wait for RocksDB testing to complete -- we are on it -- we could squeeze this one in, too?).
Also \cc @guozhangwang who merge the original PR.

Hi @mjsax - I think so too.

Thanks @mjsax I read the JIRA description and all discussions and I agree we can revert the changes asap before we have a thorough KIP discussion on what should be the right semantics (and for that semantics I agree with your comment that is the only one that makes sense in the JIRA as well, btw).

Merged to trunk and cherry-picked to 3.6, 3.5, and 3.4 branches.


Add print stats pass

[flow] add options to print out operation statistics
Use --iree-flow-dump-stats-after-outlining. It dumps the operation
statistics after outlining dispatch regions.
The default file name is stats-after-outlining.json, but it can be
changed by --iree-flow-dump-stats-after-outlining-output-file.
Here is an example output for miniLM.
{
  "arith.addf" : 476,
  "arith.constant" : 667,
  "arith.divf" : 74,
  "arith.index_cast" : 3,
  "arith.maxf" : 24,
  "arith.minf" : 12,
  "arith.mulf" : 402,
  "arith.sitofp" : 1,
  "arith.subf" : 63,
  "builtin.module" : 272,
  "flow.dispatch" : 271,
  "flow.dispatch.tensor.load" : 611,
  "flow.dispatch.tensor.store" : 271,
  "flow.executable" : 271,
  "flow.executable.export" : 271,
  "flow.executable_end" : 271,
  "flow.tensor.reshape" : 52,
  "flow.tensor.slice" : 1,
  "func.func" : 272,
  "func.return" : 272,
  "hal.tensor.export" : 2,
  "hal.tensor.import" : 3,
  "linalg.batch_matmul" : 24,
  "linalg.fill" : 171,
  "linalg.generic" : 248,
  "linalg.index" : 1,
  "linalg.init_tensor" : 271,
  "linalg.matmul" : 73,
  "linalg.yield" : 516,
  "math.exp" : 12,
  "math.rsqrt" : 25,
  "math.tanh" : 1,
  "tensor.extract" : 3
}

--iree-flow-dump-dispatch-graph is renamed by --iree-flow-dump-graph-after-outlining to match the naming style.
The PR also adds --iree-flow-dump-graph-after-deduplication and --iree-flow-dump-stats-after-deduplication.

https://github.com/google/iree/issues/9423

Ben added a mechanism to collect statistics from compilation. It would be useful to integrate into that than having separate paths (or use the existing MLIR support for pass statistics if that is possible).
Also not sure about collecting such counts across dispatches after outlining. I am not sure what information this will give....

flow.dispatch represents the number of callers.
flow.executable represents the number of callees.
After deduplications, the number of callers stays the same, while the number of callees will be reduced further.

The script that uses this information would filter based on its need.

+1 to trying to use the existing pass infra if possible - every pass and flag is additional burden (and extra docs/etc).
I think what you're really looking for here is pass instrumentation: https://mlir.llvm.org/docs/PassManagement/#pass-instrumentation. @ScottTodd posted an example he had using it to gather statistics just like this (counting total number of ops of all types after every pass and printing a pretty chart).
All these flags could then be reduced to a single string flag that took a list of pass names would let you get these statistics at every single point in the compilation process without changing code - we really can't add dozens of flags :)
There's also the existing statistics pass Mahesh mentions, which if you're looking for user-serviceable program information (vs debugging flags, like these) is the route to go.
The existing pass prints out global, per-dispatch, and per-dispatchable info like this in both pretty textual and csv/json/etc but happens at the stream level instead of flow. https://github.com/google/iree/pull/8167 has more info on it and an example of its modes: https://gist.github.com/benvanik/b690efc4f4320b9d3ea96dd72f633127. It has some stuff in it for gathering things like executable functions -> all dispatches to them in a way that handles deduplication (https://github.com/google/iree/blob/main/compiler/src/iree/compiler/Dialect/Stream/Transforms/DumpStatistics.cpp#L46). The important thing about doing it in the stream dialect is that at the point this runs we will have performed allocation, interface refinement, and device placement such that the information is representative of what actually ends up running. How flow treats ops is an implementation detail to end users, and the best tool that's indicative of performance is the stream level (as we know what devices and what dispatches/transfers are performed).
Specifically of interest in there is that you can add another CSV table/JSON dict/etc that contains cumulative op stats in each dispatch, and for humans in the bottom pretty printed example it has the TODOs were per-dispatch information can live (summaries/etc). For example, this TODO could contain the list of linalg ops or whatnot: https://github.com/google/iree/blob/719856b9f45a5e3685a37bd87db62081a53cb4f9/compiler/src/iree/compiler/Dialect/Stream/Transforms/DumpStatistics.cpp#L327-L328 that would show up here: https://gist.github.com/benvanik/b690efc4f4320b9d3ea96dd72f633127#file-2-mobilenet_stats-mlir-L505
The JSON output is what we'll wire up to tracking/dashboards, so if there's information you want surfaced/automated that's the place to do it (when possible).

Thanks for the review.
The main goal of the change is to help @pzread easily get the number of dispatches with a compiler option. The JSON format is what he preferred, so I have added the feature to the upstream LLVM. (See OpStats.cpp.)
The pass instrument didn't seem to be a good way for me because it runs the pass after every pass. Another way is that we dump IR of interest and run the OpStats pass separately using iree-opt. It is not as convenient as the compiler option I propose, but it should serve the purpose well.
If we restrict the requirement only to the number of dispatches, we can use the stream dump statistics pass. This sounds like a good option for me, but @pzread, you would need to parse the information in your script or change the pass to print in JSON.
Another way would be adding a feature like --mlir-print-ir-after=<pass> to the MLIR framework. Then, we can use an option like --mlir-print-stats-after=<pass>. But, when there are multiple points, the offline script needs to parse the stderr content. We may extend the option to --mlir-print-stats-after={pass=mypass,file=mypass.json}.
Anyway, I will abandon this PR. It is up to you @pzread to choose which way to go.

Thanks @okkwon , I'll take a look to see which way to go.

The pass instrument didn't seem to be a good way for me because it runs the pass after every pass. Another way is that we dump IR of interest and run the OpStats pass separately using iree-opt. It is not as convenient as the compiler option I propose, but it should serve the purpose well.
Another way would be adding a feature like --mlir-print-ir-after=<pass> to the MLIR framework. Then, we can use an option like --mlir-print-stats-after=<pass>. But, when there are multiple points, the offline script needs to parse the stderr content. We may extend the option to --mlir-print-stats-after={pass=mypass,file=mypass.json}.

Take a look at how --mlir-print-ir-after= is implemented - it uses pass instrumentation in the way Ben described.

All these flags could then be reduced to a single string flag that took a list of pass names and would let you get these statistics at every single point in the compilation process without changing code - we really can't add dozens of flags :)

https://github.com/llvm/llvm-project/blob/fc7f7260a609b2092260b6a5e867a20cf364808c/mlir/lib/Pass/PassManagerOptions.cpp#L86-L126
https://github.com/llvm/llvm-project/blob/fc7f7260a609b2092260b6a5e867a20cf364808c/mlir/lib/Pass/IRPrinting.cpp#L135-L163
You pass a list of pass names via flags, which then get checked at runtime. The instrumentation runs after every pass, but it doesn't need to take action after every pass - it can choose to only run if the pass matches what was specified. You can add any aggregation, file I/O, etc. as needed in your pass instrumentation implementation.

(we'll need to redo this as scott mentions in any PR that tries to add more flags like this - it's tech debt as-is and not urgent but we don't want to use its current implementation as justification to extend it :)


my IoT open Tech webhook template

Summary

my IoT open Tech integration. my IoT open Tech is an IoT platform developed upon ThingsBoard Community Edition.
...
Changes

This is a new template

Notes for Reviewers

https://www.doc.my.iotopentech.io/integrations/the-things-network.html
...
Checklist

[x] Scope: The referenced issue is addressed, there are no unrelated changes.
[x] Compatibility: The changes are backwards compatible, they don't break existing deployments.
[x] Testing: The changes are tested.
[x] Documentation: Relevant documentation is added or updated.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


chore: upgrade to eslint@6

Summary
Seems to have some weird lint errors, so a separate PR seems like a good idea.

file is definetely used, not sure what's up
https://github.com/babel/babel-eslint/issues/791
https://github.com/eslint/eslint/issues/12117
I've lock it at 6.1 which works fine

Test plan
Green CI

Codecov Report

Merging #8855 into next will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            next   #8855   +/-   ##
=====================================
  Coverage   63.8%   63.8%
=====================================
  Files        274     274
  Lines      11576   11576
  Branches    2841    2842    +1
=====================================
  Hits        7386    7386
  Misses      3560    3560
  Partials     630     630

Impacted Files
Coverage Δ

packages/jest-environment-node/src/index.ts
48.48% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9336e74...7475ea1. Read the comment docs.

@SimenB seems like babel-eslint issue is resolved? https://twitter.com/left_pad/status/1165738603755925504


Profile_Integration_TC5

Title
should delete user profile if Owner
Description
Implement test to delete user profile at the endpoint /api/profiles/:Id for the profile owner.

Method : DELETE
Endpoint : /api/profiles/:Id

Expected Result

Status code: 200
Data: should reflect updated or removed profile fields

Acceptance Criteria

[x] Implement test case

LGTM!!!!!!!!!!!!!!!!


Hostname + default metadata when no overrides

This should not affect instances where overrides are provided.

Lint check function won't allow pass without version bump


BluFi w/ Nimble Example in Panic  (IDFGH-5720)

Problem Description
Using IDF from master where the blufi nimble implementation and example are available.  Example runs fine with bluedroid though when switched to nimble, enabling CONFIG_BT_NIMBLE_BLUFI_ENABLE and flashing to devboard (ESP32-C3-DevKitM-1) things go into a panic.
source: https://github.com/espressif/esp-idf/tree/master/examples/bluetooth/blufi
sdkconfig and stack dump are attached.
sdkconfig.txt
blufi_nimble_stack_dump.txt

Hi @jolu1977 ,
Can you please confirm if the issue is resolved with attached changes ?
fix_init_crash_c3.txt
Thanks,
Rahul

Confirmed, example code now works.
Thanks!


Rename 'deployed' version to 'published' version

Description

UI change only for this PR (to change in the entire codebase will can in another PR if we decide we want to move in that direction)
Note: also change "make" to "set" to also have it be clearer
User Impact

clearer naming

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:white_check_mark: All tests successful. No failed tests found.
Additional details and impacted files

:loudspeaker: Thoughts on this report? Let us know!


[Feature proposal] Add multiple floor support

It would be very nice to have support for multiple floor.
There could also be a floor selector.

hey @pierreduchemin ,
It' nice! Actually you can replace map data to support for multiple floor. And you can try to it.

Thank you @onlylemi, I will give it a try !


reordering sidebar and adding homepage to apis

Checklist

[X] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[X] Tests for the changes have been added/updated (if applicable)
[X] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.

Creating API Home and Tools section in nav/docs


Image transformations require SciPy. Install SciPy.

I am running tensorflow with the help of miniforge3 on MacBook Pro M1.
I have followed the steps to install tensorflow on M1 from here: https://github.com/jeffheaton/t81_558_deep_learning/blob/master/install/tensorflow-install-mac-metal-jul-2021.ipynb

TensorFlow version (use command below): tensorflow-mac 2.5.0
Python version: 3.9
Bazel version (if compiling from source):
GPU model and memory: M1 8gb

ImportError                               Traceback (most recent call last)
/var/folders/k9/t0sd91511s16j207y0y2wps40000gn/T/ipykernel_91808/2572958566.py in
9 import scipy
10
---> 11 history = model.fit(
12     train_generator,
13     steps_per_epoch = 15,
/opt/homebrew/Caskroom/miniforge/base/envs/tensorflow/lib/python3.9/site-packages/tensorflow/python/keras/engine/training.py in fit(self, x, y, batch_size, epochs, verbose, callbacks, validation_split, validation_data, shuffle, class_weight, sample_weight, initial_epoch, steps_per_epoch, validation_steps, validation_batch_size, validation_freq, max_queue_size, workers, use_multiprocessing)
1131          training_utils.RespectCompiledTrainableState(self):
1132       # Creates a tf.data.Dataset and handles batch and epoch iteration.
-> 1133       data_handler = data_adapter.get_data_handler(
1134           x=x,
1135           y=y,
/opt/homebrew/Caskroom/miniforge/base/envs/tensorflow/lib/python3.9/site-packages/tensorflow/python/keras/engine/data_adapter.py in get_data_handler(*args, **kwargs)
1362   if getattr(kwargs["model"], "_cluster_coordinator", None):
1363     return _ClusterCoordinatorDataHandler(*args, **kwargs)
-> 1364   return DataHandler(*args, **kwargs)
1365
1366
/opt/homebrew/Caskroom/miniforge/base/envs/tensorflow/lib/python3.9/site-packages/tensorflow/python/keras/engine/data_adapter.py in init(self, x, y, sample_weight, batch_size, steps_per_epoch, initial_epoch, epochs, shuffle, class_weight, max_queue_size, workers, use_multiprocessing, model, steps_per_execution, distribute)
1152     adapter_cls = select_data_adapter(x, y)
1153     self._verify_data_adapter_compatibility(adapter_cls)
-> 1154     self._adapter = adapter_cls(
1155         x,
1156         y,
/opt/homebrew/Caskroom/miniforge/base/envs/tensorflow/lib/python3.9/site-packages/tensorflow/python/keras/engine/data_adapter.py in init(self, x, y, sample_weights, shuffle, workers, use_multiprocessing, max_queue_size, model, **kwargs)
930     self._keras_sequence = x
931     self._enqueuer = None
--> 932     super(KerasSequenceAdapter, self).init(
933         x,
934         shuffle=False,  # Shuffle is handed in the _make_callable override.
/opt/homebrew/Caskroom/miniforge/base/envs/tensorflow/lib/python3.9/site-packages/tensorflow/python/keras/engine/data_adapter.py in init(self, x, y, sample_weights, workers, use_multiprocessing, max_queue_size, model, **kwargs)
807     # Since we have to know the dtype of the python generator when we build the
808     # dataset, we have to look at a batch to infer the structure.
--> 809     peek, x = self._peek_and_restore(x)
810     peek = self._standardize_batch(peek)
811     peek = _process_tensorlike(peek)
/opt/homebrew/Caskroom/miniforge/base/envs/tensorflow/lib/python3.9/site-packages/tensorflow/python/keras/engine/data_adapter.py in _peek_and_restore(x)
941   @staticmethod
942   def _peek_and_restore(x):
--> 943     return x[0], x
944
945   def _handle_multiprocessing(self, x, workers, use_multiprocessing,
/opt/homebrew/Caskroom/miniforge/base/envs/tensorflow/lib/python3.9/site-packages/keras_preprocessing/image/iterator.py in getitem(self, idx)
63         index_array = self.index_array[self.batch_size * idx:
64                                        self.batch_size * (idx + 1)]
---> 65         return self._get_batches_of_transformed_samples(index_array)
66
67     def len(self):
/opt/homebrew/Caskroom/miniforge/base/envs/tensorflow/lib/python3.9/site-packages/keras_preprocessing/image/iterator.py in _get_batches_of_transformed_samples(self, index_array)
236             if self.image_data_generator:
237                 params = self.image_data_generator.get_random_transform(x.shape)
--> 238                 x = self.image_data_generator.apply_transform(x, params)
239                 x = self.image_data_generator.standardize(x)
240             batch_x[i] = x
/opt/homebrew/Caskroom/miniforge/base/envs/tensorflow/lib/python3.9/site-packages/keras_preprocessing/image/image_data_generator.py in apply_transform(self, x, transform_parameters)
861         img_channel_axis = self.channel_axis - 1
862
--> 863         x = apply_affine_transform(x, transform_parameters.get('theta', 0),
864                                    transform_parameters.get('tx', 0),
865                                    transform_parameters.get('ty', 0),
/opt/homebrew/Caskroom/miniforge/base/envs/tensorflow/lib/python3.9/site-packages/keras_preprocessing/image/affine_transformations.py in apply_affine_transform(x, theta, tx, ty, shear, zx, zy, row_axis, col_axis, channel_axis, fill_mode, cval, order)
279     """
280     if scipy is None:
--> 281         raise ImportError('Image transformations require SciPy. '
282                           'Install SciPy.')
283     transform_matrix = None
ImportError: Image transformations require SciPy. Install SciPy.

Hi ! @jackfrost1411 , That is issue related to installation of Scipy.  Please uninstall and install Scipy and check the issue again. Thank you.

This kind of error on m1 macbooks usually are only solved by reinstalling the tensorflow. Just remove the tensorflow that you have installed and follow the instruction on the apple site ->
https://developer.apple.com/metal/tensorflow-plugin/
After doing all the steps, you also need to install tensorboard also using pip in the same environment.

Thanks  @jackfrost1411 ! Could you close  the issue then!

This link helped me

reinstall scipy
shutdown and reopen jupyter server.

It worked for me. Thank you


Doesn't work with v47

couldn't import ,could you renew the plugin

the problem is not the sketch 47, but the macOS High Sierra. My co-worker has the 47 but still on macOS Sierra 10.12 and it is working

and it's only to import. export works fine

@olafchou same as me and I can't import.

Thanks for letting me know all, I'll be working on a fix.

Thanks for the pateience all! I just pushed an update which should fix the import issues. For now I'm closing this issue.
https://github.com/nilshoenson/shared-text-styles/releases/tag/1.4


Fix: casparCG template transitions bug

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix.

CasparCG Templates doesn't actually support transitions, but we have code paths that support it (but apparently they are buggy).

What is the current behavior? (You can also link to an open issue here)
When playing a template object, and (accidentally) has set a transition for it, the template isn't played properly.
(when stopped, a PLAY "empty" is sent, not a CG STOP)

What is the new behavior (if this is a feature change)?
CG PLAY and CG STOP are sent, as they should

Other information:

TODO

[ ] Verify that this is actually the right thing to do, and that templates actually does not and should not support transitions

There is an edge case here when your template doesn't have an out transition and you want to do a fade out using the casparcg transitions


Hide SerializedDependency

This hides SerializedDependency from general public, as requested here. It also hides SerializedManifest which was (wrongly?) exposed.
This is required for #2196. I want to move in small steps this time, hence the separate PR.
Technically this break backwards compatibility, because SerializedDependency and SerializedManifest were public (SerializedPackage was private however). Are such changes allowed in cargo?

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @wycats (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Ok, quick GitHub search says that Serialized(Dependency|Manifest) are used only by cargo.

@bors: r+ a42422dfd5e75bd7d9edd06660f878270e4d69cb
Thanks!

:hourglass: Testing commit a42422d with merge fcff230...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64


Upgrade argument parser

Codecov Report

Merging #58 (d2027f0) into main (df7b378) will increase coverage by 0.34%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #58      +/-   ##
==========================================
+ Coverage   98.29%   98.64%   +0.34%
==========================================
  Files          28       28
  Lines        1701     1693       -8
==========================================
- Hits         1672     1670       -2
+ Misses         29       23       -6

Impacted Files
Coverage Δ

Tests/ShuskyTests/ShuskyTests.swift
98.90% <0.00%> (+4.39%)
:arrow_up:

Sources/ShuskyCore/Models/Command.swift
100.00% <0.00%> (+10.00%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update df7b378...d2027f0. Read the comment docs.


[APIM-4.0.0] Invalid username reference for TopicConnectionFactory url in jndi-cp.properties.j2

Description:
Currently,  jndi-cp.properties.j2 file is referring only the apim.event_hub.username as the username to construct the TopicConnectionFactory when some conditions are true. This will break the configuration if email user is enabled in the deployment.toml and also when event_hub configurations are applied(TM seperation use case)
It will result constructing the endpoint setting the username as admin<EMAIL_ADDRESS>Ideally this value should be admin!wso2.com!carbon.super to be success with the configurations.
Hence we need to refer apim.throttling.jms.username instead.
Steps to reproduce:

Configure APIM-4.0.0 with email-user enabled configs
Apply event_hub configurations.
Start the server and check  jndi-cp.properties file.

Affected Product Version:
APIM-4.0.0
Environment details (with versions):
N/A

duplicate


Add API to set arbitrary context in Transaction.

Oh, did not know that, but makes sense. Changed it.


Replace ng::helpers with ov::test::utils for enums

https://jira.devtools.intel.com/browse/CVS-123998

Merged in scope of https://github.com/openvinotoolkit/openvino_contrib/pull/760


Issue with chapter09/concurrency/once/main.go

Hello,
I had an issue with the execution of this example. With the default code I got the following output (nearly always, once or two I got two "Hello, friend!" messages...
https://github.com/PacktPublishing/Test-Driven-Development-in-Go/blob/main/chapter09/concurrency/once/main.go

~/git/Test-Driven-Development-in-Go/chapter09/concurrency/once$ go run main.go
Hello, friend!
Channel closed.
Goodbye, friend!

Fixed it with wait  groups but perhaps there's a simpler way...
package main

import (
	"fmt"
	"sync"
)

var wg sync.WaitGroup

func safelyClose(once *sync.Once, ch chan struct{}) {
	defer wg.Done()
	fmt.Println("Hello, friend!")
	once.Do(func() {
		fmt.Println("Channel closed.")
		close(ch)
	})
}

func main() {
	var once sync.Once

	ch := make(chan struct{})
	for i := 0; i < 3; i++ {
		wg.Add(1)
		go safelyClose(&once, ch)
	}
	<-ch
	wg.Wait()
	fmt.Println("Goodbye, friend!")
}

~/git/Test-Driven-Development-in-Go/chapter09/concurrency/once$ go run main.go
Hello, friend!
Channel closed.
Hello, friend!
Hello, friend!
Goodbye, friend!

Hello,
Also had similar issues with other bit of this chapter, for example concurrency/data.races and concurrency/buffered-channels. I'm using go version 1.21.3


project config and mux interfaces

adding base mux interfaces and gradle files

BTW – gonna try to adopt the Kotlin DSL for Gradle, if you guys agree. I personally have a pet peeve with Groovy 😛


experimental: reorg code to move server as gnatsd base package + cmd/gnatsd main

I took a pass on #106 for some feedback/thought. This PR encourages the gnatsd server to be embedded in application services utilizing nats - turning nodes into brokers as well, with the goal for nats to be a layer for building distributed services baked right into the service layer.
I also wrote a basic example using this PR - https://gist.github.com/pkieltyka/049266c307bc8f14ea65. It's not that interesting yet.
This PR includes:

Moved /gnatsd/server package to /gnatsd and moved the main() in server to /cmd/gnatsd
A new Makefile to build the server: make build to run tests: make test
All tests pass

Thanks, will have @krobertson and @olegshaldybin take a quick look.

cool. btw, seems to be some minor configuration issue with coveralls in this branch, but I am sure its easily solvable I just never used coveralls.

@pkieltyka overall it looks good... will review it a bit further. We have a few outside parts to update. Namely, I'll take a look at the Dockerfile since I think it needs updating to build the right file, and our outside system which builds the binaries on the releases tab.
Don't worry about the Coveralls bit... it looks like with the move, some some code that counted as covered is not in a package that has no tests. Looking it over, there are no functional changes, and it is only 0.3%.

@krobertson nice, glad to hear it! go get github.com/nats-io/gnatsd/cmd/gnatsd would work as well.

@krobertson any chance for further review / consideration? lmk for suggestions and I can tweak

@pkieltyka Did you get a chance to tweak to pass tests?

More recent changes in gnatsd render this PR obsolete. Let's reopen/discuss via a new Issue if you feel parts of this PR are still relevant.


Documentation facelift (docs.bacalhau.org & more...)

Core repo
README

highlight “What is Bacalhau”
highlight Getting Started
add references to the community on Slack
more..

Docs repo

https://github.com/bacalhau-project/docs.bacalhau.org/issues/26
https://github.com/bacalhau-project/docs.bacalhau.org/issues/24
... more generally all issues at 👇
https://github.com/bacalhau-project/docs.bacalhau.org/issues

First round of facelifting completed ✅

new core repo README https://github.com/filecoin-project/bacalhau#readme
revised docs https://docs.bacalhau.org/

new getting started
updated image processing example
new structure
new examples...


Command line arguments for configuration files

Description

Is it configfile or configfiles ?
pattern --config of Markdown seems to be --config in RST (I will double check that with my previous commit)
API referencesconfigfiles, but does not describe CLI parameter

QC
it's only about the docs

Related: https://github.com/snakemake/snakemake/pull/527


Issue with vite_ssr_import#_ code replacement

Given code like the following (extracted from luxon library):
import { formatOffset, parseZoneInfo, hasIntl } from "../impl/util.js";
export default class LocalZone extends Zone {
  formatOffset(ts, format) {
    return formatOffset(this.offset(ts), format);
  }
}

it looks like vite replaces incorrect tokens causing a syntax error:
const __vite_ssr_import_0__ = __vite_ssr_import__("/node_modules/luxon/src/impl/util.js")
__vite_ssr_exports__.default = class LocalZone extends __vite_ssr_import_1__.default {
  __vite_ssr_import_0__.formatOffset(ts, format) {
    return __vite_ssr_import_0__.formatOffset(this.offset(ts), format);
  }
}

(The problem being at the method definition.)
The error looks like this when running vite:
(node:57520) UnhandledPromiseRejectionWarning: SyntaxError: Unexpected token '.'
    at new Function (<anonymous>)
    at instantiateModule (/Users/tj/src/github.com/vitejs/vite/packages/vite/dist/node/chunks/dep-50c31524.js:67960:9)

~Looking into whether a patch is non-trivial now...~ See https://github.com/vitejs/vite/pull/2223.

#2223 seems to be fixing a different issue (class methods) since here the error is caused by the Identifier being a super class of a class declaration.


chore: update dep

Update dev and peer dependency requirement on vite-plugin-package-config.

@antfu with the release of<EMAIL_ADDRESS>the peer dependency requirement for this package is out of date. Hopefully this PR resolves that in a suitable way.
Something else to consider, creating a v1.0.0 release for both packages would allow patch and minor releases to be accurately matched with ^x.x.x notation.


Remove github workflows DEVOPS-494

Notification service has moved to Platta

Notification service branch is deployed to platta: https://kuva-notification-service-pr33.api.dev.hel.ninja :rocket::rocket::rocket:


last_login can no longer be null in test data

I'm hoping this makes the functional tests pass rather than failing when trying to import the fixture data.

Works for me on Django 1.7.7 and 1.8.


Upgrade few transitive dependencies

Upgrade few transitive dependencies
Some of the transitive dependencies referred are not latest. Hence updated to the latest version.

Thanks but this is already in #29447


T379710 npm audit fix and dependencies update

Phabricator: https://phabricator.wikimedia.org/T379710
Update:
audit report after the latest version update
up to date, audited 2205 packages in 2s

327 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

Full audit report
# npm audit report

body-parser  <1.20.3
Severity: high
body-parser vulnerable to denial of service when url encoding is enabled - https://github.com/advisories/GHSA-qwcr-r2fm-qrc7
fix available via `npm audit fix`
node_modules/body-parser
  express  <=4.21.0 || 5.0.0-alpha.1 - 5.0.0
  Depends on vulnerable versions of body-parser
  Depends on vulnerable versions of cookie
  Depends on vulnerable versions of path-to-regexp
  Depends on vulnerable versions of send
  Depends on vulnerable versions of serve-static
  node_modules/express

braces  <3.0.3
Severity: high
Uncontrolled resource consumption in braces - https://github.com/advisories/GHSA-grv7-fg5c-xmjg
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/braces
node_modules/sane/node_modules/braces
  micromatch  <=4.0.7
  Depends on vulnerable versions of braces
  node_modules/micromatch
  node_modules/sane/node_modules/micromatch
    anymatch  1.2.0 - 2.0.0
    Depends on vulnerable versions of micromatch
    node_modules/sane/node_modules/anymatch
      sane  1.5.0 - 4.1.0
      Depends on vulnerable versions of anymatch
      Depends on vulnerable versions of micromatch
      node_modules/sane
        jest-haste-map  24.0.0-alpha.0 - 26.6.2
        Depends on vulnerable versions of sane
        node_modules/@wordpress/jest-preset-default/node_modules/jest-haste-map
        node_modules/@wordpress/scripts/node_modules/jest-haste-map
        node_modules/jest-jasmine2/node_modules/jest-haste-map
          @jest/core  <=26.6.3
          Depends on vulnerable versions of @jest/reporters
          Depends on vulnerable versions of @jest/transform
          Depends on vulnerable versions of jest-config
          Depends on vulnerable versions of jest-haste-map
          Depends on vulnerable versions of jest-resolve-dependencies
          Depends on vulnerable versions of jest-runner
          Depends on vulnerable versions of jest-runtime
          Depends on vulnerable versions of jest-snapshot
          node_modules/@wordpress/scripts/node_modules/@jest/core
            jest  24.2.0-alpha.0 - 26.6.3
            Depends on vulnerable versions of @jest/core
            Depends on vulnerable versions of jest-cli
            node_modules/@wordpress/scripts/node_modules/jest
              @wordpress/scripts  >=1.0.1-0
              Depends on vulnerable versions of @svgr/webpack
              Depends on vulnerable versions of @wordpress/jest-preset-default
              Depends on vulnerable versions of @wordpress/stylelint-config
              Depends on vulnerable versions of babel-jest
              Depends on vulnerable versions of cross-spawn
              Depends on vulnerable versions of jest
              Depends on vulnerable versions of jest-circus
              Depends on vulnerable versions of jest-dev-server
              Depends on vulnerable versions of markdownlint
              Depends on vulnerable versions of markdownlint-cli
              Depends on vulnerable versions of puppeteer-core
              Depends on vulnerable versions of stylelint
              node_modules/@wordpress/scripts
            jest-cli  24.2.0-alpha.0 - 26.6.3
            Depends on vulnerable versions of @jest/core
            Depends on vulnerable versions of jest-config
            node_modules/@wordpress/scripts/node_modules/jest-cli
          @jest/reporters  <=26.6.2
          Depends on vulnerable versions of @jest/transform
          Depends on vulnerable versions of jest-haste-map
          node_modules/@wordpress/scripts/node_modules/@jest/reporters
          @jest/test-sequencer  <=26.6.3
          Depends on vulnerable versions of jest-haste-map
          Depends on vulnerable versions of jest-runner
          Depends on vulnerable versions of jest-runtime
          node_modules/@wordpress/scripts/node_modules/@jest/test-sequencer
          node_modules/jest-jasmine2/node_modules/@jest/test-sequencer
            jest-config  24.2.0-alpha.0 - 26.6.3
            Depends on vulnerable versions of @jest/test-sequencer
            Depends on vulnerable versions of babel-jest
            Depends on vulnerable versions of jest-jasmine2
            node_modules/@wordpress/scripts/node_modules/@jest/core/node_modules/jest-config
            node_modules/@wordpress/scripts/node_modules/jest-cli/node_modules/jest-config
            node_modules/@wordpress/scripts/node_modules/jest-runner/node_modules/jest-config
            node_modules/@wordpress/scripts/node_modules/jest-runtime/node_modules/jest-config
            node_modules/jest-jasmine2/node_modules/jest-config
              jest-runner  24.0.0-alpha.0 - 26.6.3
              Depends on vulnerable versions of jest-config
              Depends on vulnerable versions of jest-haste-map
              Depends on vulnerable versions of jest-runtime
              node_modules/@wordpress/scripts/node_modules/jest-runner
              node_modules/jest-jasmine2/node_modules/jest-runner
                jest-circus  25.2.4 - 26.6.3
                Depends on vulnerable versions of jest-runner
                Depends on vulnerable versions of jest-runtime
                Depends on vulnerable versions of jest-snapshot
                node_modules/@wordpress/scripts/node_modules/jest-circus
              jest-runtime  24.0.0-alpha.0 - 26.6.3
              Depends on vulnerable versions of @jest/transform
              Depends on vulnerable versions of jest-config
              Depends on vulnerable versions of jest-haste-map
              Depends on vulnerable versions of jest-snapshot
              node_modules/@wordpress/scripts/node_modules/jest-runtime
              node_modules/jest-jasmine2/node_modules/jest-runtime
                jest-jasmine2  24.2.0-alpha.0 - 26.6.3
                Depends on vulnerable versions of jest-runtime
                Depends on vulnerable versions of jest-snapshot
                node_modules/jest-jasmine2
          @jest/transform  <=26.6.2
          Depends on vulnerable versions of jest-haste-map
          node_modules/@wordpress/jest-preset-default/node_modules/@jest/transform
          node_modules/@wordpress/scripts/node_modules/@jest/transform
          node_modules/jest-jasmine2/node_modules/@jest/transform
            babel-jest  24.2.0-alpha.0 - 26.6.3
            Depends on vulnerable versions of @jest/transform
            node_modules/@wordpress/jest-preset-default/node_modules/babel-jest
            node_modules/@wordpress/scripts/node_modules/babel-jest
            node_modules/jest-jasmine2/node_modules/babel-jest
              @wordpress/jest-preset-default  4.1.0 - 7.1.5-next.33ec3857e2.0
              Depends on vulnerable versions of babel-jest
              node_modules/@wordpress/jest-preset-default
          jest-snapshot  24.2.0-alpha.0 - 24.5.0 || 26.1.0 - 26.6.2
          Depends on vulnerable versions of jest-haste-map
          node_modules/@wordpress/scripts/node_modules/jest-snapshot
          node_modules/jest-jasmine2/node_modules/jest-snapshot
            jest-resolve-dependencies  26.1.0 - 26.6.3
            Depends on vulnerable versions of jest-snapshot
            node_modules/@wordpress/scripts/node_modules/jest-resolve-dependencies

cookie  <0.7.0
cookie accepts cookie name, path, and domain with out of bounds characters - https://github.com/advisories/GHSA-pxg6-pf52-xh8x
fix available via `npm audit fix`
node_modules/cookie

cross-spawn  <6.0.6 || >=7.0.0 <7.0.5
Severity: high
Regular Expression Denial of Service (ReDoS) in cross-spawn - https://github.com/advisories/GHSA-3xgq-45jj-v275
Regular Expression Denial of Service (ReDoS) in cross-spawn - https://github.com/advisories/GHSA-3xgq-45jj-v275
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/@pkgr/utils/node_modules/cross-spawn
node_modules/@storybook/cli/node_modules/cross-spawn
node_modules/@storybook/codemod/node_modules/cross-spawn
node_modules/@wordpress/scripts/node_modules/eslint/node_modules/cross-spawn
node_modules/@wordpress/scripts/node_modules/execa/node_modules/cross-spawn
node_modules/cross-spawn
node_modules/default-browser/node_modules/cross-spawn
node_modules/eslint/node_modules/cross-spawn
node_modules/execa/node_modules/cross-spawn
node_modules/foreground-child/node_modules/cross-spawn
node_modules/sane/node_modules/cross-spawn
node_modules/webpack-cli/node_modules/cross-spawn

dompurify  3.0.0 - 3.1.2
Severity: high
DOMPurify allows tampering by prototype pollution - https://github.com/advisories/GHSA-mmhx-hmjr-r674
DOMpurify has a nesting-based mXSS - https://github.com/advisories/GHSA-gx9m-whjm-85jf
fix available via `npm audit fix`
node_modules/dompurify

ejs  <3.1.10
Severity: moderate
ejs lacks certain pollution protection - https://github.com/advisories/GHSA-ghr5-ch3p-vcr6
fix available via `npm audit fix`
node_modules/ejs

ip  *
Severity: high
NPM IP package incorrectly identifies some private IP addresses as public - https://github.com/advisories/GHSA-78xj-cgh5-2h22
ip SSRF improper categorization in isPublic - https://github.com/advisories/GHSA-2p57-rm9w-gvfp
fix available via `npm audit fix`
node_modules/ip

markdown-it  <12.3.2
Severity: moderate
Uncontrolled Resource Consumption in markdown-it - https://github.com/advisories/GHSA-6vfc-qv3f-vr6c
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/markdown-it
  markdownlint  <=0.25.0
  Depends on vulnerable versions of markdown-it
  node_modules/markdownlint
    markdownlint-cli  <=0.30.0
    Depends on vulnerable versions of markdownlint
    node_modules/markdownlint-cli

node-fetch  <2.6.7
Severity: high
node-fetch forwards secure headers to untrusted sites - https://github.com/advisories/GHSA-r683-j2x4-v87g
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/node-fetch
  puppeteer-core  10.0.0 - 13.1.1
  Depends on vulnerable versions of node-fetch
  Depends on vulnerable versions of ws
  node_modules/puppeteer-core

nth-check  <2.0.1
Severity: high
Inefficient Regular Expression Complexity in nth-check - https://github.com/advisories/GHSA-rp65-9cf3-cjxr
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/svgo/node_modules/nth-check
  css-select  <=3.1.0
  Depends on vulnerable versions of nth-check
  node_modules/svgo/node_modules/css-select
    svgo  1.0.0 - 1.3.2
    Depends on vulnerable versions of css-select
    node_modules/svgo
      @svgr/plugin-svgo  <=5.5.0
      Depends on vulnerable versions of svgo
      node_modules/@svgr/plugin-svgo
        @svgr/webpack  4.0.0 - 5.5.0
        Depends on vulnerable versions of @svgr/plugin-svgo
        node_modules/@svgr/webpack

path-to-regexp  <=0.1.9 || 4.0.0 - 6.2.2
Severity: high
path-to-regexp outputs backtracking regular expressions - https://github.com/advisories/GHSA-9wv6-86v2-598j
path-to-regexp outputs backtracking regular expressions - https://github.com/advisories/GHSA-9wv6-86v2-598j
fix available via `npm audit fix`
node_modules/express/node_modules/path-to-regexp
node_modules/path-to-regexp

postcss  <8.4.31
Severity: moderate
PostCSS line return parsing error - https://github.com/advisories/GHSA-7fh5-64p2-3v2j
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/postcss-less/node_modules/postcss
node_modules/postcss-safe-parser/node_modules/postcss
node_modules/postcss-sass/node_modules/postcss
node_modules/postcss-scss/node_modules/postcss
node_modules/stylelint/node_modules/postcss
node_modules/sugarss/node_modules/postcss
  autoprefixer  1.0.20131222 - 9.8.8
  Depends on vulnerable versions of postcss
  node_modules/stylelint/node_modules/autoprefixer
    stylelint  0.1.0 - 13.13.1
    Depends on vulnerable versions of autoprefixer
    Depends on vulnerable versions of postcss
    Depends on vulnerable versions of postcss-less
    Depends on vulnerable versions of postcss-safe-parser
    Depends on vulnerable versions of postcss-sass
    Depends on vulnerable versions of postcss-scss
    Depends on vulnerable versions of sugarss
    node_modules/stylelint
      @wordpress/stylelint-config  <=19.1.1-next.5df0cd52b7.0
      Depends on vulnerable versions of stylelint
      Depends on vulnerable versions of stylelint-config-recommended-scss
      Depends on vulnerable versions of stylelint-scss
      node_modules/@wordpress/stylelint-config
      stylelint-config-recommended  <=2.2.0 || 4.0.0 - 5.0.0
      Depends on vulnerable versions of stylelint
      node_modules/stylelint-config-recommended-scss/node_modules/stylelint-config-recommended
        stylelint-config-recommended-scss  <=4.3.0
        Depends on vulnerable versions of stylelint
        Depends on vulnerable versions of stylelint-config-recommended
        Depends on vulnerable versions of stylelint-scss
        node_modules/stylelint-config-recommended-scss
      stylelint-scss  0.0.0-alpha.1 || 1.0.0 - 3.21.0
      Depends on vulnerable versions of stylelint
      node_modules/stylelint-scss
  postcss-less  <=3.1.4
  Depends on vulnerable versions of postcss
  node_modules/postcss-less
  postcss-safe-parser  <=4.0.2
  Depends on vulnerable versions of postcss
  node_modules/postcss-safe-parser
  postcss-sass  <=0.4.4
  Depends on vulnerable versions of postcss
  node_modules/postcss-sass
  postcss-scss  <=2.1.1
  Depends on vulnerable versions of postcss
  node_modules/postcss-scss
  sugarss  <=2.0.0
  Depends on vulnerable versions of postcss
  node_modules/sugarss

request  *
Severity: moderate
Server-Side Request Forgery in Request - https://github.com/advisories/GHSA-p8p7-x288-28g6
Depends on vulnerable versions of tough-cookie
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/request
  wait-on  <=4.0.2
  Depends on vulnerable versions of request
  node_modules/wait-on
    jest-dev-server  4.1.1 - 4.4.0
    Depends on vulnerable versions of wait-on
    node_modules/jest-dev-server

send  <0.19.0
send vulnerable to template injection that can lead to XSS - https://github.com/advisories/GHSA-m6fv-jmcg-4jfg
fix available via `npm audit fix`
node_modules/send
  serve-static  <=1.16.0
  Depends on vulnerable versions of send
  node_modules/serve-static

tar  <6.2.1
Severity: moderate
Denial of service while parsing a tar file due to lack of folders count validation - https://github.com/advisories/GHSA-f5x3-32g6-xq36
fix available via `npm audit fix`
node_modules/tar

tough-cookie  <4.1.3
Severity: moderate
tough-cookie Prototype Pollution vulnerability - https://github.com/advisories/GHSA-72xf-g2v4-qvf3
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/tough-cookie

webpack  5.0.0-alpha.0 - 5.93.0
Severity: moderate
Webpack's AutoPublicPathRuntimeModule has a DOM Clobbering Gadget that leads to XSS - https://github.com/advisories/GHSA-4vvj-4cpr-p986
fix available via `npm audit fix`
node_modules/webpack

ws  6.0.0 - 6.2.2 || 7.0.0 - 7.5.9 || 8.0.0 - 8.17.0
Severity: high
ws affected by a DoS when handling a request with many HTTP headers - https://github.com/advisories/GHSA-3h5v-q93c-6h6q
ws affected by a DoS when handling a request with many HTTP headers - https://github.com/advisories/GHSA-3h5v-q93c-6h6q
ws affected by a DoS when handling a request with many HTTP headers - https://github.com/advisories/GHSA-3h5v-q93c-6h6q
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/@storybook/cli/node_modules/ws
node_modules/jsdom/node_modules/ws
node_modules/puppeteer-core/node_modules/ws
node_modules/webpack-bundle-analyzer/node_modules/ws
node_modules/ws

60 vulnerabilities (3 low, 40 moderate, 17 high)

There is an issue when doing the npm audit fix --force, reported here https://github.com/WordPress/gutenberg/issues/63771#issuecomment-2503533739 --- add the fix commit https://github.com/wikimedia/wikipediapreview-wordpress/pull/138/commits/634a5f2894ceaf3c05cdee743229b8f2680d8cf7 until the wordpress/script not get reverted back to 1.0.0

Good news, wordpress team has fixed the issue and we no longer need the overrides.


Unable to update a little change in the current design

Describe the bug
My prompt:
That looks good. Now I think it would be better that we show a little description of what's the current screen is about in the left side in the same line where we have the filtering options like dd-mm-yyyy, same for Engagement view and Activity view.

Don't change rest of the design view.

It rewrites the code rather than modifying/adding some lines in the existing code. And then add comments like these:
{/* Rest of the component remains the same */}
// ... existing activityLogs and helper functions ...

Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-agnkey
Steps to reproduce
My prompt:
That looks good. Now I think it would be better that we show a little description of what's the current screen is about in the left side in the same line where we have the filtering options like dd-mm-yyyy, same for Engagement view and Activity view.

Don't change rest of the design view.

It rewrites the code rather than modifying/adding some lines in the existing code. And then add comments like these:
{/* Rest of the component remains the same */}
// ... existing activityLogs and helper functions ...

Expected behavior
It should update/add new lines of code rather than deleting the existing one and then trying to create the same thing again which will obviously fail.
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 130
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 75832933,
  "usedJSHeapSize": 61352201,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = Nishantbhagat57
Chat ID = fc732ff38efe

Additional context
No response

// rest of the code remains the same...
// leave original code here
// Rest of the component's logic remains unchanged...
@kc0tlh


Add more integration tests

Codecov Report

Merging #54 (1fef860) into main (dabf87e) will increase coverage by 3.81%.
The diff coverage is 87.50%.

@@            Coverage Diff             @@
##             main      #54      +/-   ##
==========================================
+ Coverage   86.32%   90.14%   +3.81%
==========================================
  Files          51       51
  Lines        5463     5477      +14
==========================================
+ Hits         4716     4937     +221
+ Misses        747      540     -207

Impacted Files
Coverage Δ

src/steps/misc_steps/init_boards_step.rs
15.78% <78.57%> (+15.78%)
:arrow_up:

src/generic_steps/generic_filter.rs
100.00% <100.00%> (ø)

src/step_param_utils.rs
100.00% <100.00%> (ø)

src/steps/io_steps/export_games.rs
88.46% <0.00%> (+0.96%)
:arrow_up:

src/workflow_step.rs
70.00% <0.00%> (+1.00%)
:arrow_up:

src/steps/parsers/parse_bin_game_step.rs
94.28% <0.00%> (+1.42%)
:arrow_up:

src/steps/maps/perfect_checkmate_map.rs
93.44% <0.00%> (+93.44%)
:arrow_up:

src/steps/reducers/avg_reduce.rs
95.30% <0.00%> (+95.30%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dabf87e...1fef860. Read the comment docs.


Update from version 3 to 4, error 500 and missing payment methods

Upgrading from version 3 to 4, give the payment 500 error + the current payment methods are not available anymore after upgrade, you need to setup everything again.
Multistore. Version <IP_ADDRESS>.

Same for us. I can't get the new module to work.

Same for me, on Prestashop <IP_ADDRESS>

Hello guys,
Sorry to hear about this, the issue is known and is handled at the development team.
We will update you when we will eliminate this issue.
Best Regards,
Invertus Support Team

Same here, from 3 to 4. On prestashop <IP_ADDRESS>

Hello guys,
Please check the latest release regarding those mentioned bugs
https://github.com/mollie/Prestashop/releases
Have a great day,
Invertus Support Team

Hi
also with the new release, the problem with the error 500 page is not solved. In the backoffice of prestashop I see the following log: "PaymentModule::validateOrder - Order Status cannot be loaded"
Hope it can be solved asap. There is no problem when using version 3 of this module

Hey @Kevertje68 sorry about this, assuring that the team got your message.
We are moving on to this issue.
Have a great day,
Invertus Support Team

I'm having the same issue.

Problem are old / wrong methods in hook displaypaymentEU

Change: $apiMethod['id'] to $apiMethod['id_method']
Change: $apiMethod['name'] to $apiMethod['method_name']

Logo images:
+Add:  $images = json_decode($method['images_json'],true);
+Change: $method['image']['size1x'] TO $images['size1x']
+Change $method['image']['size2x'] TO $images['size2x']

This problem happened to me too. Prestashop <IP_ADDRESS> and Mollie module 4.0.2.
I solved it by changing the config status in:
/modules/mollie/controllers/front/payment.php:380
The search was for a status "STATUS_MOLLIE_AWAITING" but Mollie only has the status
"MOLLIE_STATUS_OPEN" created in the config table of Prestashop.
Change:
(int) Configuration :: get (Mollie \ Config \ Config :: STATUS_MOLLIE_AWAITING),
To
(int) Configuration :: get (Mollie \ Config \ Config :: MOLLIE_STATUS_OPEN),

@LMG-Jeffy  you can find Config :: STATUS_MOLLIE_AWAITING in Configuration table with name mollie_awaiting.
It should exist in your table, if not there something is wrong and you should try to reset your module. Thanks to your comment we were able to found the different issues and fix it in the upcoming 4.0.4 release.
If you use Config :: MOLLIE_STATUS_OPEN it should have status 0 in your database.

I updated to 4.04 and now the issue is that during the checkout procdure, when I click on "Go to Payment" (on the page where you can select the carrier during the check out procedure), it directly goes to an error 500 page en there is no error log data in the back office of Prestashop.
The URL looks like this _shopname.nl/_index.php?controller=order
Hope it can be solved.

Hello @LMG-Jeffy have you managed to upgrade the module to v4.0.4? https://github.com/mollie/PrestaShop/releases/download/4.0.4/mollie.zip
Please let us know the outcome, if you are still experiencing the status problems.
Best Regards.

Hello @Toyboy125 and @Kevertje68 ,
Thank you for raising this issue. Our development team will act to this matter and investigate your issue. We are expecting to share the update with you tomorrow.
Thank you for using Mollie

I am experiencing the same issue. Really in need of a fix!

Hi everyone,
Please try to reset the module. It should help.
We will also upload the latest release today.

Same here on prestashop 1.6.8.
Module is not usable at all.
Good thing to start the weekend with. Thank you mollie.

Stange
locally it works now (xampp)
Version 4.0.5
but live site same fault.
log status
PaymentModule::validateOrder - Order Status cannot be loaded	Cart	206

Hi Everyone,
We really appreciate your input in this community. We have added this issue to our backlog and planned the resources accordingly. In the meantime if you have similar issue, please try to reset the module or upgrade it to v 4.0.5.
We are expecting to make the next release with this fix next week.

Version 4.0.6
Now testing on live site.
it seems good.
Thanks for the support.

Issue was resolved in 4.0.6 release.


removed unnecessary logos

Removed Unnecessary logos from the footer

now its look like this

Good work @parthksingh1!


Parameterize regression test suite with DDL sharding key

parameterization is coming to luatest [1], it would be nice to parameterize the whole test suite with an option that enables/disables custom sharding key to make sure that everything is fine.

https://github.com/tarantool/luatest/pull/163

The sharding keys support comes with tests (PR #181), so I guess here you propose to coalesce the similar tests cases. My thoughts on the topic are below.

It is hard to verify that we don't miss some cases if we'll do a massive tests rewritting.
Those new tests will be more abstract and less straighforward.
It is considerable amount of thorough work.
However if we'll define a set of simple tests that can be written in an abstract way and run against different schemas, we can easily add a new case to verify against all those schemas.

I found the idea of using parametrization in new tests, where it is appropriate, nice. But I doubt about rewriting of existing tests. However I'm not the author of tests, so my judgement may be a bit too abstract.
@ligurio, what do you think here?

I agree. Feel free to close the issue.

Closing then. // CC @DifferentialOrange


fix: check if jump key is pressed to prevent unintended jump animation

close #2
Added logic to check if the jump key was actually pressed in jump animation condition.

@wildcatco That's a critical issue we need to address. Thank you for pointing it out.
However, I think the fundamental problem is that velocity.y sometimes becomes greater than 0.
Logically, velocity.y should never increase above 0 in the first place.
Even when climbing uphill, the position should be adjusted, but the velocity itself shouldn't increase.
That's why the jump doesn't play even when climbing stairs.
I think the issue might be in the following part, and I'd like us to think about it together.
// PhysicsControls.ts

/**
 * Checks for collisions between the player's collider and the world octree.
 * Updates the player's grounded state and adjusts velocity and position accordingly.
 */
private checkCollisions() {
  this._isGrounded = false;

  const collisionResult = this._worldOctree.capsuleIntersect(this._capsuleCollider);

  if (!collisionResult) return;

  this.dispatchEvent(_collideEvent);

  if (collisionResult.normal.y > 0) {
    // Player is grounded.
    this._isGrounded = true;
    this.dispatchEvent(_groundedEvent);
  } else {
    // Player is colliding but not grounded.
+  this.velocity.addScaledVector(collisionResult.normal, -collisionResult.normal.dot(this.velocity));
+  this.dispatchEvent(_fallEvent);
  }

  // Adjust the collider position to resolve penetration.
  if (collisionResult.depth >= 1e-10) {
    this._capsuleCollider.translate(collisionResult.normal.multiplyScalar(collisionResult.depth));
  }
}

Ah, I see now. The issue occurs when the colliding object is positioned above the character.
Then, I think the solution you suggested is a good one.
https://github.com/user-attachments/assets/f3d948ff-b100-42c4-a617-cbb3ac5c74c5

@Byongho96 Maybe we can fix the fundamental problem later.
I moved checking logic into if statement to avoid unnecessary calculation. 19a840310ceabbc327785cf6dbfd6300159030ec
If it's ok, merge please.


Example not running on OSX with 0.9+

I have been having issues with getting the example code to run. I’ve tried the latest release as well as previous versions. When I use the project generator I add in ofxIpVideoGrabber and ofxXmlSettings. I then copy the example code in to the respective src files and put the xml file in the data folder. When I run the code I get quite a few errors, mostly regarding Threading.
Suggestions on resolving this would be appreciated.
Thanks!

Thanks @bakercp for the speedy response!
Yes, so I am on OSX and I just pulled your changes and generated a new project with the project generator and included the addons and I got similar threading issues.
The error was "No matching constructor for initialization of std::unique_lock<std::mutex>"
Was this correct or do I need to do something in the addon directory?
Thanks

Hmm that is odd. What version of openFrameworks are you using?  If it's pre 0.9.0, then this addon probably won't work without getting an earlier release (from the releases tab).

I'm running openFrameworks 0.9.1 with the latest release.

Hm.. Very strange.  Can you post an image of your error output?
Also, can you try it with the latest release (0.9.3)?  Also, what version of xcode / osx are you using?

Latest releaces - OSX 10.11.3. Xcode 7.2.1.
I'll try cloning 0.9.3 and try.
Attached is the error output.

I am using a different project generator - "projectGeneratorSimple".

I don't seem to have the one your using. Is this why?

Most probably definitely. :)
If you download the release package http://openframeworks.cc/versions/v0.9.3/of_v0.9.3_osx_release.zip
Unzip it and look here:

Hmm. I'm not sure it's in a different repo and gets packaged during the release script process.  Closing this for now. Let me know if you run into any other problems. :)


Adds Test TestLoadAASXWithBooleanProp

Loads aasx file with SubmodelElement with boolean property
Checks if boolean value of SubmodelElement property is of class Boolean
moves test resources in related directory

Co-authored-by: Jannik Fried<EMAIL_ADDRESS>Co-Authored-By: Rene Fischer<EMAIL_ADDRESS>Signed-off-by: Jannis Jung<EMAIL_ADDRESS>

Replaced with https://github.com/eclipse-basyx/basyx-java-sdk/pull/44


list index out of range

OS: Windows
QGIS version: 3.14.10.-Prizren
I can't load any layer. I can establish connexion but I'm getting an error for every single table I'm trying to load
2 types of error:

SFConvertColumnToLayerTask run failed: list index out of range. Same error if I execute as a SQL query. I add a where clause and I select the geopgraphy type
Running snowflake convert column to layer task failed. SQL Compilation error: error line x at position XX, invlaid indetifier 'SHAPEFILE/CENTROID/SHAPE_AREA/STOPTIME/METERS" The invalid identifier is not related to the geopgragy column. I'm not able to identify why it fails on those specific fields.

Hey @philehot, please try out the latest version and let mw know if it's still reproducible.

I thought initially we had some tables in our WH already converted to GEOGRAPHY but turns out this was not the case. Once I updated a geo column to TO_GEOGRAPHY, the table showed up in QGIS. Closing this as it was not an issue.


Update next.config.js

We require all PRs to follow Conventional Commits specification.
More details 👇🏼
 No release type found in pull request title "Update next.config.js". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit


HTTP Authorization?

I'm looking into accessing an (Image)WMS service protected with HTTP credentials.
I saw #4213 and did some googling, which usually resulted in suggestions similar to this as ImageLoadFunction:
function customLoader(tile, src) {
  var client = new XMLHttpRequest();
  client.responseType = 'blob';
  client.open('GET', src);
  client.setRequestHeader("Authorization", "Basic " + window.btoa('xxxxxxx' + ":" + 'xxxxxxxxx'));
  client.onload = function() {
    tile.getImage().src = URL.createObjectURL(client.response);
  };
  client.send();
}

The call is made from a (http) development to an external https environment.
However, FireFox seems to block the OPTIONS request (CORS preflight).
Upon reading futher, I read that this is typical for most WMS servers.
It would just be kind of nice if there was something about this (whether it's possible or a workaround) in the OpenLayers documentation.
Or is this only possible with TileWMS?

This seems to be an unfortunate browser limitation.
Instead of a GET, FireFox performs an OPTIONS due to the use of a custom header (Authorization). This gets blocked, but I don't have control over the third party's Nginx server (proxy for a GIS server).
https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS#preflighted_requests
However, if the request is one that triggers a preflight due to the presence of the Authorization header in the request, you won’t be able to work around the limitation using the steps above. And you won’t be able to work around it at all unless you have control over the server the request is being made to."


Docs: search not working / outdated Sphinx

Problem: The search within the github.io docs is not working. The reason is probably an outdated/mismatched jquery package within the deployment. A rebuild with the latest sphinx version should fix the issue; this will be done as part of the next release process where the Jenkins build jobs will run.

See PR #127

Search Functionality is working properly now. Documentation and theme  updated.
Here is the latest one https://eudat-b2safe.github.io/B2HANDLE/


Playing around with example highlighter

This builds off of @KatherineCox 's work in #170

For me it is kinda tricky to visualize where the borrowed text starts and stops in the bookdown. Added a div to "highlight" this
Third chunk is missing the module settings
If you define AnVIL_module_settings in one chunk, they persist to the next chunk used. This could be a problem if someone sets variables on chunk 1 but doesn't want them on chunk 2. Added a comment to make that clear and added rm() at the end of the chunks

Awesome, thanks!
Re: persisting settings

Yeah, I've been trying to figure out the best way to handle them.
The reason I moved the individual settings inside a list (AnVIL_module_settings) was so that they at least aren't cluttering up the R environment with multiple, miscellaneous names.
This does still mean that individual modules in the same doc can bump into each other.  I've been wondering if we should automatically clear out AnVIL_module_settings at the end of a module (i.e. stick the rm() inside the child doc)?

re: the example divs

Love this!!  I totally agree that we need something to distinguish the instructions from the module content.
Do you think it's confusing for users looking at the .Rmd file that there's extra stuff around the module code block?   I've been hesitant about adding AnVIL_Template-specific things in/around the code blocks because I imagine people will want to copy paste them.
Although, looking at your divs, they look really good!  I might actually want to keep the surrounding div when I drop the module into a book, because it gives students a visual boundary around the instructions for a particular task.  So perhaps it's not actually a concern if people copy the whole thing, div and all.
In that case, maybe rename the class something like "module" or "instructions" or something, and treat it as part of the AnVIL style?  It might be nice to have a highlighting box that doesn't come with an image.  Might also want to set it so that it doesn't have padding-left: 100px;, since there's no picture.
Maybe still worth putting some instructions about keeping/removing the div box somewhere

Although, looking at your divs, they look really good! I might actually want to keep the surrounding div when I drop the module into a book, because it gives students a visual boundary around the instructions for a particular task. So perhaps it's not actually a concern if people copy the whole thing, div and all.
That's what I was thinking. If they are left in, no harm no foul.

In that case, maybe rename the class something like "module" or "instructions" or something, and treat it as part of the AnVIL style (i.e. expect that people will use it in their own books)? It might be nice to have a highlighting box that doesn't come with an image. Might also want to set it so that it doesn't have padding-left: 100px;, since there's no picture.
Maybe still worth putting some instructions about keeping/removing the div box somewhere
Noted! I can add that. Do you care if I merge my PR and we work on the same one?

Do you care if I merge my PR and we work on the same one?
@avahoffman Go for it!  The only thing I was working on was moving the variables inside the AnVIL_module_settings list, and I think you've finished that for me in this PR by updating chapter 8 :)

@KatherineCox great! Thanks for the quick review! :)

I've been wondering if we should automatically clear out AnVIL_module_settings at the end of a module (i.e. stick the rm() inside the child doc)?

This was my original thought. It doesn't work and anvil_module_settings still persists. Maybe because the child environment is separate?

Ah, too bad.  I wonder if we could reach up from inside the child environment to the parent with <<-, and set AnVIL_module_settings to NULL?
I considered trying to mess around with withr, but I think the withr code would need to be outside the child doc, which would make things more confusing for users.  If we need to handle clearing the settings in the main document, I think your rm() solution is best - people are familiar with rm().

we can always change it later if we want to get fancy :)


How to test on rosbag file ?

I'm sorry, but can SuMa run on some rosbag format dataset ?

We currently only support the KITTI format.


chore: Alternative Refactor

Description
As per https://github.com/noir-lang/noir-bignum/pull/27
This version passes MOD_BITS around as a generic, instead of as a constant, which is needed for the latest noir release.

The tests fail because this PR is only compatible with the latest version of aztec-packages nargo.

In my defense, I just ran nargo fmt and it made 3000 extra line changes.

Can you update the CI to run on the new minimum noir version?

just change the version in test.yml to 0.36.0 and the noir tests should pass


Devstopwatch app 0.04 - fixes #1157

bugfix stopwatch broken with v0.03 setUI - fixes #1157
realigned quick n dirty screen positions
help adjusted to fit bangle1 & bangle2 screen-size with top/lower widgets
fixed bangle2  foreground color for header: chrono and last lap highlight 3bit color (blue)
added screenshot for bangle2 and a small README for both

looks great - thanks!


if /auto-request-control, only request control once upon connect

if auto-request-control setting is enabled then only request control once upon connect, otherwise it will auto request control again every time server turns off control which is a bit annoying.

@freerdp-bot test


FileNotFoundError: [Errno 2] No such file or directory: '/home/rvl224/OnePose_Plus_Plus-main/data/demo/demo_cam/demo_cam-annotate/color'

I put demo data under repo root, ran:
REPO_ROOT=/home/rvl224/OnePose_Plus_Plus-main

ln -s /home/rvl224/OnePose_Plus_Plus-main/demo_cam $REPO_ROOT/data/demo

OBJ_NAME=demo_cam

cd $REPO_ROOT

bash scripts/demo_pipeline.sh $OBJ_NAME

But it showed
Error executing job with overrides: ['+preprocess=sfm_demo', 'dataset.data_dir=[/home/rvl224/OnePose_Plus_Plus-main/data/demo/demo_cam demo_cam-annotate]', 'dataset.outputs_dir=/home/rvl224/OnePose_Plus_Plus-main/data/demo/sfm_model']
Traceback (most recent call last):
  File "/home/rvl224/OnePose_Plus_Plus-main/run.py", line 400, in main
    globals()[cfg.type](cfg)
  File "/home/rvl224/OnePose_Plus_Plus-main/run.py", line 65, in sfm
    sfm_worker(data_dirs, cfg)
  File "/home/rvl224/OnePose_Plus_Plus-main/run.py", line 105, in sfm_worker
    img_name_lists = os.listdir(osp.join(seq_dir, img_dir_name))
FileNotFoundError: [Errno 2] No such file or directory: '/home/rvl224/OnePose_Plus_Plus-main/data/demo/demo_cam/demo_cam-annotate/color'

Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.

what did I do wrong? There isn't color in /demo_cam/demo_cam-annotate when I download from onedrive.

oops, you have to pull the demo_cam out after you extracted it. Since there's a "__MACOSX" folder beside it I thought the whole extracted file belongs in the dataset.

oops, you have to pull the demo_cam out after you extracted it. Since there's a "__MACOSX" folder beside it I thought the whole extracted file belongs in the dataset.

hey pal, I met the same problem but I haven't finish it yet.
what do you mean by pulling the demo_cam out? it's still no folder called color in the diretory, right?
appreciate it if you can help me out.


Invalid scroll size: scroll=10 in Neovim(PHP Xdebug)

Kubuntu 20.04
Neovim: 0.4.3
Debugger: Php Xdebug
I got this error: Invalid scroll size: scroll=10 when using F2, or F3to step over/step into a function in a php project. spent a day to find the solution but didn't have any result.(see my screenshot for more information)

Here is my full log file: https://pastebin.com/BJJKV34Q

Found the issue, there is a line in my nvim config:
" autocmd BufEnter * :set scroll=10
removed that line and it works well.


Build is failing

Describe the bug
Build is failing on "Build the Network Firewall Solution CodeBuild source code" step with the error:
tests/network-firewall-manager.spec.ts:281:16 - error TS2571: Object is of type 'unknown'.
281         expect(error["message"]).toBe("Subnet IDs must be in the environment variables")
~~~~~
tests/network-firewall-manager.spec.ts:301:20 - error TS2571: Object is of type 'unknown'.
301             expect(error["message"]).toBe("VPC ID must be in the environment variables")
~~~~~
lib/common/firewall-config-validation.ts:14:33 - error TS2307: Cannot find module 'aws-sdk' or its corresponding type declarations.
14 import { NetworkFirewall } from "aws-sdk";
~~~~~~~~~
lib/common/firewall-config-validation.ts:156:39 - error TS2571: Object is of type 'unknown'.
156             const errorCode: string = error["code"]
~~~~~
lib/common/firewall-config-validation.ts:161:28 - error TS2571: Object is of type 'unknown'.
161                     error: error["message"]
~~~~~
lib/common/firewall-config-validation.ts:194:39 - error TS2571: Object is of type 'unknown'.
194             const errorCode: string = error["code"]
~~~~~
lib/common/firewall-config-validation.ts:198:28 - error TS2571: Object is of type 'unknown'.
198                     error: error["message"]
~~~~~
lib/common/send-metrics.ts:13:30 - error TS7016: Could not find a declaration file for module 'uuid'. '/home/ec2-user/environment/test/aws-network-firewall-deployment-automations-for-aws-transit-gateway/source/node_modules/uuid/dist/index.js' implicitly has an 'any' type.
Try npm i --save-dev @types/uuid if it exists or add a new declaration (.d.ts) file containing declare module 'uuid';
13 import { v4 as uuidv4 } from "uuid"
~~~~~~
lib/common/send-metrics.ts:14:21 - error TS2307: Cannot find module 'aws-sdk' or its corresponding type declarations.
14 import { SSM } from "aws-sdk"
~~~~~~~~~
lib/common/send-metrics.ts:15:19 - error TS2307: Cannot find module 'axios' or its corresponding type declarations.
15 import axios from "axios"
~~~~~~~
lib/common/send-metrics.ts:48:25 - error TS2571: Object is of type 'unknown'.
48                     if (error["code"] = "ParameterNotFound") {
~~~~~
lib/ec2-manager.ts:14:38 - error TS2307: Cannot find module 'aws-sdk' or its corresponding type declarations.
14 import { EC2, NetworkFirewall } from "aws-sdk"
~~~~~~~~~
lib/ec2-manager.ts:86:23 - error TS2571: Object is of type 'unknown'.
86       throw new Error(error["message"])
~~~~~
lib/network-firewall-manager.ts:15:33 - error TS2307: Cannot find module 'aws-sdk' or its corresponding type declarations.
15 import { NetworkFirewall } from "aws-sdk"
~~~~~~~~~
lib/network-firewall-manager.ts:146:23 - error TS2345: Argument of type 'unknown' is not assignable to parameter of type 'string | undefined'.
Type 'unknown' is not assignable to type 'string'.
146       throw new Error(error)
~~~~~
lib/network-firewall-manager.ts:228:23 - error TS2345: Argument of type 'unknown' is not assignable to parameter of type 'string | undefined'.
Type 'unknown' is not assignable to type 'string'.
228       throw new Error(error)
~~~~~
lib/network-firewall-manager.ts:327:19 - error TS2345: Argument of type 'unknown' is not assignable to parameter of type 'string | undefined'.
Type 'unknown' is not assignable to type 'string'.
327       throw Error(error)
~~~~~
lib/service/awsClientConfig.ts:13:36 - error TS2307: Cannot find module 'aws-sdk' or its corresponding type declarations.
13 import {ConfigurationOptions} from 'aws-sdk'
~~~~~~~~~
lib/service/ec2-service.ts:14:43 - error TS2307: Cannot find module 'aws-sdk' or its corresponding type declarations.
14 import { ConfigurationOptions, EC2 } from 'aws-sdk'
~~~~~~~~~
lib/service/network-firewall-service.ts:14:55 - error TS2307: Cannot find module 'aws-sdk' or its corresponding type declarations.
14 import { ConfigurationOptions, NetworkFirewall } from 'aws-sdk'
~~~~~~~~~
lib/service/network-firewall-service.ts:41:11 - error TS2571: Object is of type 'unknown'.
41       if (e.code === "ResourceNotFoundException") {
~
lib/service/network-firewall-service.ts:77:11 - error TS2571: Object is of type 'unknown'.
77       if (error.code === "ResourceNotFoundException") {
~~~~~
lib/service/network-firewall-service.ts:94:11 - error TS2571: Object is of type 'unknown'.
94       if (error.code === "ResourceNotFoundException") {
~~~~~
lib/service/network-firewall-service.ts:117:13 - error TS2571: Object is of type 'unknown'.
117         if (error.message === "ThrottlingException") {
~~~~~
lib/service/network-firewall-service.ts:121:13 - error TS2571: Object is of type 'unknown'.
121         if (error.code === "ResourceNotFoundException") {
~~~~~
lib/service/network-firewall-service.ts:159:13 - error TS2571: Object is of type 'unknown'.
159         if (error['message'] === 'Update token is invalid.') {
~~~~~
lib/service/network-firewall-service.ts:180:13 - error TS2571: Object is of type 'unknown'.
180         if (error['message'] == 'Update token is invalid.') {
~~~~~
lib/service/network-firewall-service.ts:282:72 - error TS7006: Parameter 'ruleGroup' implicitly has an 'any' type.
282         response.FirewallPolicy?.StatefulRuleGroupReferences?.forEach((ruleGroup) => {
~~~~~~~~~
lib/service/network-firewall-service.ts:285:73 - error TS7006: Parameter 'ruleGroup' implicitly has an 'any' type.
285         response.FirewallPolicy?.StatelessRuleGroupReferences?.forEach((ruleGroup) => {
~~~~~~~~~
Found 29 errors.
If I use Node version 15 , I face this error during "Build the CDK code" step:

<EMAIL_ADDRESS>build
tsc

test/network-firewall-automation-solution.test.ts:37:40 - error TS2345: Argument of type 'import("C:/Users/TABSBE/OneDrive - RWWA/github/aws-network-firewall-deployment-automations-for-aws-transit-gateway/source/node_modules/@aws-cdk/core/lib/stack").Stack' is not assignable to parameter of type 'import("C:/Users/TABSBE/OneDrive - RWWA/github/aws-network-firewall-deployment-automations-for-aws-transit-gateway/source/node_modules/@aws-cdk/assert/node_modules/@aws-cdk/core/lib/stack").Stack'.
Type 'Stack' is missing the following properties from type 'Stack': reportMissingContextKey, splitArn, exportValue, maxResources
37     expect(SynthUtils.toCloudFormation(getTestStack())).toMatchSnapshot();
To Reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Please complete the following information about the solution:
Versions:
CDK: 1.77.0
NODE: v14.1.0
NPM: 6.14.4
Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context
Add any other context about the problem here.

Hi @rahuldeverani
Can you try running the following commands to build the module,
cd source/networkfirewallAutomations
npm install
npm run build

Sorry for replying late , it worked!


feat: add supported node versions for all packages

Which problem is this PR solving?
In accordance with https://github.com/open-telemetry/opentelemetry-js/issues/2834 we've changed the support range to >=8.12.
https://github.com/open-telemetry/opentelemetry-js/commit/da22673d102d3ecb6364a39be968cd8d666cc136 changed that in Core.
Short description of the changes
Updated every package.json according to the issue above and out CI configuration, which skips tests for some of the packaged that have dropped the support for older node versions.

strictly speaking only modules using the performance times require 8.12 others work fine with lower versions. But not sure if there is any benefit of having e.g. a resource detector working with 8.0 but there is no SDK to use it with.

strictly speaking only modules using the performance times require 8.12 others work fine with lower versions. But not sure if there is any benefit of having e.g. a resource detector working with 8.0 but there is no SDK to use it with.

That's right. In that sense we don't absolutely need to narrow down propagators and detectors. I think I'd approached it differently if we had SDK compatible with 8.5 and took it from module<>plugin direction making the version minimum of what either can support. Would you prefer it solved differently?

I think it's fine. I doubt that it has much impact at all as people using that old node versions are most likely used to ignore warnings anyway :o).