Fix quick install

see https://github.com/apache/skywalking-cli/pull/106#discussion_r684621030
The additional tree path results in 404.

This change alone doesn't seem to fix the quick install, btw. The files that get downloaded (from https://apache.website-solution.net) with this install do not match https://downloads.apache.org/skywalking/cli/0.9.0/skywalking-cli-0.9.0-bin.tgz.sha512.

https://apache.website-solution.net/ seems not an official ASF site. Is it a mirror?

This change alone doesn't seem to fix the quick install, btw.

What do you mean doesn't seem to fix? Is there any issue of the document?

It should be failing the signature check https://github.com/apache/skywalking-cli/blob/39dce3dea9f5fdd26e03163a47214d4c0c4fee9d/scripts/install.sh#L64
Whenever I run it, it just hangs:
$ /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/apache/skywalking-cli/master/scripts/install.sh)"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 21681  100 21681    0     0   109k      0 --:--:-- --:--:-- --:--:--  109k
The latest version of swctl is 0.9.0

I downloaded binary and sha512 from the official site, https://dist.apache.org/repos/dist/release/skywalking/cli/0.9.0/
And sha512 check passed through this
> shasum -c skywalking-cli-0.9.0-bin.tgz.sha512
skywalking-cli-0.9.0-bin.tgz: OK

@fgksgf @kezhenxu94 Could you check this?

The install script installs the un-official https://apache.website-solution.net/skywalking/cli/0.9.0/skywalking-cli-0.9.0-bin.tgz

This should be fixed. all release should be from official https://archive.apache.org/dist/skywalking/cli/

The hashes match now... I'm not sure why the install script hangs then.

Password required popup.

I am feeling this is Chinese mirror.

@BFergerson Have you tried to changed https://apache.website-solution.net to https://archive.apache.org/dist/skywalking/cli/, and try again?


bug: Couldn't update state on render

When I register listener on render of component, sometimes it occurs Couldn't update  react state ...
Need investigation redux-listener occurs an error.

I'm working on it

I've found out it's because of  functions in listeners
It keeps function when component is mounted into listener, but never changes its functions even component is unmounted.
  middleware.addListener = (type, listener) => {
    for (let i = 0; i < listeners.length; i += 1) {
      if (listeners[i].type === type) {
        return;
      }
    }
    listeners.push(createListener(type, listener));
  };

We should change this library to be able to use in component.


DEVTOOLING-924 pt2 - Refactor/exporter resource types

Here is the second PR for DEVTOOLING-924 where we refactor inconsistent usages:

resourceName to ResourceType when referring to the type of resource.

This also allows us to reference the ResourceType for importing in test initialization

resourceName to resourcePath when referring to the combined path of type + label
There are a few other variable name fixes along the way.

Hi @bbbco , No issues were seen in bbbco:refactor/exporter_resource_types
Integration tests & acceptance tests looks good.


Time series in Unix vs. ISO

The docs for Time series point to https://github.com/d3/d3-scale/blob/master/README.md#time-scales, which uses Date objects.
But the time-chart example uses unix timestamps, which are numbers vs. objects.
ISO date objects work in Area and LineSeries components (so far), but I get 'invalid propType warnings, expected Number but received Date' for LabelSeries, Crosshair, DecorativeAxis, etc.

thanks for raising this. You are right, there's an inconsistency in what can be passed as x or y properties across the board, some series accept anything, while other elements require a number or a number or a string. Will fix in next release

See #586. Closing as well

Date objects as x do work with LabelSeries, for example. But the Invalid propType warning still persists, as x is typed as number/string. I reckon this is just a propTyping issue or is this expected behaviour?


add dakshow dao custom domain

Hi! What is your PR about?

[ ] Add or edit a skin
[x] Add a custom domain for your space
[ ] Add an alias to migrate your space
I have fixed conflict, please check & merge my PR, thank you.

There is a conflict in your PR since domains.json file has been updated, can you resolve it?
To prevent conflicts, it is recommended to add your subdomain between two existing domains rather than at the end or beginning of the list.

I have add my subdomain between two existing domains rather than at the end or beginning of the list but why it conflict,sir?


feat!: Vite 4 support

SvelteKit has Vite ^4.0.0  as peer dependency.
This PR also inlcudes:

remove rollup assets file names
bump versions to major
sveltekit ^1.0.0 as peer dependency
deprecated kit base option

The PWA plugin will support both layouts, there is no need to include here the Rollup assets file names:
https://github.com/vite-pwa/vite-plugin-pwa/pull/413
Don't merge until previous PR merged and released: this PR will need also update the PWA plugin version
/cc @benmccann

@benmccann Can you also release a new version on npm please

@hmajid2301 0.1.0 version released


test: Use concurrent accesses instead of multiple databases under xdist

@jarulraj These are currently the only stable changes that we have for this milestone. On my system, makes all tests pass when run with xdist.
To run the tests, I use:
pytest --cov-report term-missing:skip-covered  --cov-config=.coveragerc --cov-context=test --cov=eva/ -s -v --log-level=WARNING -m "not benchmark" --dist loadscope -n auto

Thanks for the changes. We will borrow ideas from this PR.


Fixed typos in network.raml.

Please retest.

Retest please.

retest this please

Retest this please


feat(#1): add project skeleton with maven and some eo objects

I've added project skeleton with maven and some eo objects.
Closes: #1

@Graur Please, check

@Graur Please, check again.

@yegor256 reminder

@rultor merge

@yegor256 Unfortunately, either you or me don't have 'write' permissions to the repository, I can't do what you're asking. Try to add me as a collaborator with 'write' access.

@yegor256 probably you have to give write permissions to rultor

@yegor256 reminder

@yegor256 reminder

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@volodya-lombrozo @yegor256 Oops, I failed. You can see the full log here (spent 12s)
+ set -e
+ set -o pipefail
++ dirname ./run.sh
+ cd .
+ echo 2394852
+ echo '2.0-SNAPSHOT BUILD'
2.0-SNAPSHOT BUILD
+ date
Mon 05 Dec 2022 07:29:41 AM CET
+ uptime
 07:29:41 up 11 days, 13:07,  0 users,  load average: 6.08, 6.08, 5.93
+ cat
.rultor.yml in yegor256/objectionary-secrets doesn't allow objectionary/eo-http to use its assets (there are 22 friends), see http://doc.rultor.com/reference.html#assets
+ exit -1
'cid' file is absent, most probably the Docker container wasn't started correctly

@yegor256 reminder

@rultor merge


[ROCM] Register GPU AssertionCustomCall for ROCM

While trying to upstream register calls, the reviewers wanted us to use a runtime mechanism to determine if the platform is CUDA or ROCM. This PR addresses that.

May I ask why we can't use PlatformUtil::GetDefaultPlatform().value() ? it returns an upper case platform name (either ROCM or CUDA) so you don't need absl::AsciiStrToUpper()

good question, the problem with this is is that the Platform object is not initialized yet and causes a runtime failure when Assert OP is registered.

May I ask why we can't use PlatformUtil::GetDefaultPlatform().value() ? it returns an upper case platform name (either ROCM or CUDA) so you don't need absl::AsciiStrToUpper()

good question, the problem with this is is that the Platform object is not initialized yet and causes a runtime failure when Assert OP is registered.

Platform object? I am sorry maybe I missed something. PlatformUtil::GetDefaultPlatform() is a static function, isn't? It's also from PlatformUtil that is same as PlatformUtil::CanonicalPlatformName()

May I ask why we can't use PlatformUtil::GetDefaultPlatform().value() ? it returns an upper case platform name (either ROCM or CUDA) so you don't need absl::AsciiStrToUpper()

good question, the problem with this is is that the Platform object is not initialized yet and causes a runtime failure when Assert OP is registered.

Platform object? I am sorry maybe I missed something. PlatformUtil::GetDefaultPlatform() is a static function, isn't? It's also from PlatformUtil that is same as PlatformUtil::CanonicalPlatformName()

It returns a StatusOr object which wraps a pointer to Platform object. As I understand the platform objects are initialized by multi_platform_manager, but when the register function is called the initialization of platforms haven't happened yet. I tried what you suggested, but that results in runtime error.
static StatusOrse::Platform* GetDefaultPlatform();
By the way, I pushed this PR upstream and Cheshire approved it.

May I ask why we can't use PlatformUtil::GetDefaultPlatform().value() ? it returns an upper case platform name (either ROCM or CUDA) so you don't need absl::AsciiStrToUpper()

good question, the problem with this is is that the Platform object is not initialized yet and causes a runtime failure when Assert OP is registered.

Platform object? I am sorry maybe I missed something. PlatformUtil::GetDefaultPlatform() is a static function, isn't? It's also from PlatformUtil that is same as PlatformUtil::CanonicalPlatformName()

It returns a StatusOr object which wraps a pointer to Platform object. As I understand the platform objects are initialized by multi_platform_manager, but when the register function is called the initialization of platforms haven't happened yet. I tried what you suggested, but that results in runtime error. static StatusOrse::Platform* GetDefaultPlatform();
By the way, I pushed this PR upstream and Cheshire approved it.

Thanks a lot for your explanation! This is really helpful to understand how it works!


Telemetry: please consider making it optional

As much as I adore every of your efforts, I will not have even more telemetry installed. It would be kind to remove it, or give the user an option to permanently disable all current or all future usage of it. Yes, it's not a bug, it's a privacy / trust thing.

@jammet
for sure, we have already the work item scheduled https://github.com/microsoft/PowerToys/issues/964

Our telem uses the Windows telem system so everything we get is sampled.
For context why this is important, It helps us make some critical decisions on what to fix.  Looking at the data, we prioritized a bunch of FancyZone virtual desktop work.
We're also working toward a transparency report so everyone can clearly see what / why we need each bit.


sshd: disable trigger limit for systemd socket

Motivation for this change
When startWhenNeeded is enabled, a brute force attack on sshd will cause systemd to shut down the socket, locking out all SSH access to the machine. Setting TriggerLimitIntervalSec to 0 disables this behavior.
This has been observed on other distros as well, for example: https://bugs.archlinux.org/task/62248
cc @edolstra @Infinisil @FRidh
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)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@ofborg eval

I still use this patch and would like it to be merged.

@ofborg eval

@lopsided98 can you rebase on master to fix the github actions?

@ofborg test openssh


[LIB-552] Now SCPlease include objectsCount property to store estimat…

…ed objects count if needed

Looks good!


Upgrade cql-exec-vsac to 1.1.1

This version of cql-exec-vsac adds support for downloading version-specific value sets.

Merging this as a simple library upgrade for a library that has already been fully reviewed and approved.


Migrate to gotest.tools :)

Related to https://github.com/docker/libnetwork/pull/2213

Also cleans some vendor.conf unused lines

Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

Looks like some of the empty dependencies were added in https://github.com/docker/libnetwork/pull/2183
/cc @euanh

@thaJeztah I bumped all dependencies which libnetwork and moby had in common to the version used in moby.   I didn't look for dependencies which could be removed from libnetwork.    The new dependencies at the bottom of the file were added because one of the new versions of an existing dependency needed them.
It seems some of the original dependencies can be removed, taking the new ones with them.   Great!

rebased and fixed the conflict


🎮 Game Request
TownRise is an immersive city-building and resource management game where players take on the role of a city planner tasked with developing a small town into a thriving metropolis. The game combines strategic planning, resource management, and creative design to create a rich and engaging gameplay experience.
Point down the features
Game points:
City Building
Resource Management
Dynamic Challenges
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

assign\

Hey @Maheshwari-Love !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign


Adding conversion function converting NMEA date/time to POSIX timestamp

This fixes #20. @generationmake can you take a look that this is what you want?

Codecov Report

Merging #24 into master will decrease coverage by 1.52%.
The diff coverage is 84.61%.

@@            Coverage Diff             @@
##           master      #24      +/-   ##
==========================================
- Coverage   94.02%   92.50%   -1.53%
==========================================
  Files           5        7       +2
  Lines         201      240      +39
==========================================
+ Hits          189      222      +33
- Misses         12       18       +6

Impacted Files
Coverage Δ

src/ArduinoNmeaParser.h
100.00% <ø> (ø)

src/nmea/util/timegm.c
79.31% <79.31%> (ø)

src/nmea/util/convert.cpp
100.00% <100.00%> (ø)

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 5c42dbb...77b8d00. Read the comment docs.

Good morning @generationmake :wave: :coffee: I've rebased this PR after the merge of #22. Can you please have a look if this fulfils requirements stated in #20?

Hi @aentinger
I don't know if I am using this function correctly. Maybe I need an additional example.
I added the lines:
  time_t posix_timestamp = nmea::util::toPosixTimestamp(rmc.date, rmc.time_utc);   Serial.println((unsigned int)posix_timestamp);
to the function
void onRmcUpdate(nmea::RmcData const rmc)
of the example.
But it seems like it doesn't because it always prints
4294967295
and the number doesn't change.
What am I doing wrong?

Good morning @generationmake :wave: :coffee:
I believe this is the result because one of either your date or time entries still contains the value -1. In this case the function rk_timegm.c returns -1 which is<PHONE_NUMBER> when casted to unsigned int.
To resolve this I'm providing an additional function isValid(date,time) to determine whether or not both date and time value are valid. Only if they are valid they should be fed into toPosixTimestamp(...), e.g.
if (nmea::isValid(rmc.date, rmc.time))
{
  time_t posix_timestamp = nmea::util::toPosixTimestamp(rmc.date, rmc.time_utc);
  Serial.println((unsigned int)posix_timestamp);
}

Please let me know if this solves your problem.

Hi @aentinger
This could be. I made the test yesterday when pull request #25 was still open and I think I didn't have a full fix.
I will test again.

I made some tests and added it to my GPX logger and it seems to work.

Thank you for the review :+1: I've indeed forgotten to update keywords.txt in a while, should be up to date now.


[FLINK-8014] [FLINK-8016] Add Kafka010JsonTableSink and documentation

What is the purpose of the change

Adds a TableSink to write JSON-encoded rows to Kafka 0.10 topics
Adds documentation for KafkaJsonTableSinks

Brief change log

Add Kafka010JsonTableSink
Enable flush on checkpoint to ensure at-least-once guarantees
Refactor tests for KafkaJsonTableSInks
Add documentation for KafkaJsonTableSinks

Verifying this change

Tests have been added.
The sink uses a regular Kafka 0.10 producer
The SerializationSchema is separately tested

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? YES
If yes, how is the feature documented? Documentation has been added to website

Thanks for the review @twalthr.
Will fix the remaining issue and merge this PR.


Fixes key expiration of both cache implementations for CHMs and sharded immutable maps

Added a PurgableMapRef class to allow creating a mapref together with a function that purges keys according to schedule in the cases where it makes sense.  (A vanilla mapref lacks any way to access keys for this, so, in particular, we keep track of the underlying implementation in the chm and the sharded cases).  Note this means we can't directly use the mapref construction in the sharded case that's in the actual mapref package.  Unified logic between the DispatchOneCache and MemoryCache implementations to minimize copying.  Note this involved a type class downgrade Async => Concurrent in the DispatchOneCache.ofConcurrentHashMap to match the MemoryCache implementation (seems like they should be the same). Tests to check key expiration were added and this required in the relaxing of the privacy level of the isExpired method.
Fixed #380

Ok, this one has fought me. I finally just switched the whole build and I think we need a new version since the 2.12 artifacts refuse to participate. I think since this is basically source compatible the way forward is to release 0.6 and let the chips fall where they will.


[IO] support external data in dictdump ">" links

Currently we only support internal and external links:
https://github.com/silx-kit/silx/blob/d8a666dcfab4f071f38615ac495937cf85e97f95/src/silx/io/dictdump.py#L445
A use case has come up (Bliss NeXus writer) where an EDF should be linked.

https://docs.h5py.org/en/stable/high/group.html#h5py.Group.create_dataset

Do you mean supporting external datasets?
h5py.Group.create_dataset:

external – Store the dataset in one or more external, non-HDF5 files. This should be an iterable (such as a list) of tuples of (name, offset, size) to store data from offset to offset + size in the named file. Each name must be a str, bytes, or os.PathLike; each offset and size, an integer. The last file in the sequence may have size h5py.h5f.UNLIMITED to let it grow as needed. If only a name is given instead of an iterable of tuples, it is equivalent to [(name, 0, h5py.h5f.UNLIMITED)].

I don't know by if it can be of any help please be aware that we did some proto for tomography:

in edfconvert -  see around lines ~1135
for tiff: https://gitlab.esrf.fr/tomotools/scripts/-/blob/master/create_vds_from_tiff.py?ref_type=heads

Do you mean supporting external datasets?

Yes


APP-1140 fix

Can one of the admins verify this patch?

Codecov Report

Merging #52 into dev will decrease coverage by 0.1%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev      #52      +/-   ##
==========================================
- Coverage   89.35%   89.24%   -0.11%
==========================================
  Files          36       36
  Lines         911      911
  Branches       49       49
==========================================
- Hits          814      813       -1
  Misses         83       83
- Partials       14       15       +1

Impacted Files
Coverage Δ

...ion/webhook/github/parser/v1/BaseGithubParser.java
87.27% <0%> (-1.82%)
:arrow_down:

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 e21b47b...99e783d. Read the comment docs.


account for changing column types in incremental tables

Incremental tables are a powerful dbt feature, but there's at least one edge case which makes working with them difficult. During the first run of an incremental model, Redshift will infer a type for every column in the table. Subsequent runs can insert new data which does not conform to the expected type. One example is a varchar(16) field which is inserted into a varchar(8) field.
In practice, this error looks like:
Value too long for character type
DETAIL:
  -----------------------------------------------
  error:  Value too long for character type
  code:      8001
  context:   Value too long for type character varying(8)
  query:     3743263
  location:  funcs_string.hpp:392
  process:   query4_35 [pid=18194]
  -----------------------------------------------

The recommended solution, currently, is to change the model materialization to table, re-run dbt, then change it back to incremental.
One possible solution is to the use temp table generated by dbt during incremental model updates. The types of every temp table column can be compared to the types of every existing table column. If the types differ, then dbt can alter the offending column to the type of temp table column.
This is kind of tricky in practice, because it could be that the existing column is varchar(8) while the new column is varchar(1)... Some logic is required to ensure that columns are not altered to more-restrictive data types.
Additionally, all incremental model operations currently occur within a single transaction. If we were to implement this proposed solution, we'd need to run Python code in between the temp table phase and the delete/insert phase of the incremental model update, thus splitting up the transaction.
CC @jthandy

I don't believe that running python in the middle of a transaction means we need to "split" it... I agree that there is complexity involved in the running of this, and that it's similar to what we've spoken about before where a single operation can be split across multiple nodes in the graph. I think the important thing to do there is to make it such that multiple nodes can participate in a single transaction.

(otherwise, I'm 👍  on everything you outlined)

0.5.1 release


ZAP Scan import: xml parse error

Bug description
It happens only when I use ictu/zap2docker-weekly image for scanning DVWA (https://github.com/ICTU/zap-baseline).  It helps me with authenticated packaged scan.
docker run --rm -v $(pwd):/zap/wrk/:rw -t ictu/zap2docker-weekly zap-full-scan.py -I -j  -t http://<IP_ADDRESS>/ -x dvwa_baseline_dojo.xml --hook=/zap/auth_hook.py -z "auth.loginurl=http://<IP_ADDRESS>/login.php auth.username='admin' auth.password='password'  auth.auto=1"
If I use official image - scan importing works properly
docker run --rm -v $(pwd):/zap/wrk/:rw -u zap -p 8080:8080 -p 8090:8080 -i owasp/zap2docker-stable zap.sh -cmd -quickurl http://<IP_ADDRESS>/login.php -quickprogress -quickout wrk/zap_report.xml
Deployment method (select with an X)

[X] Kubernetes
[ ] Docker
[ ] setup.bash / legacy-setup.bash

ERRORS
I tried to import report into Defectdojo and got errors (file attached below):
ERROR:django.request:Internal Server Error: /api/v2/import-scan/
Traceback (most recent call last):
  File "./dojo/api_v2/serializers.py", line 1097, in save
    parser_findings = parser.get_findings(data.get('file', None), test)
  File "./dojo/tools/zap/parser.py", line 40, in get_findings
    return self.get_items(tree, test)
  File "./dojo/tools/zap/parser.py", line 67, in get_items
    site = Site(node)
  File "./dojo/tools/zap/parser.py", line 145, in __init__
    self.items.append(Item(alert))
  File "./dojo/tools/zap/parser.py", line 222, in __init__
    n2 = item_node.findall('instances/instance/param')[i]
IndexError: list index out of range

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/django/core/handlers/exception.py", line 34, in inner
    response = get_response(request)
  File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line 115, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "/usr/local/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/usr/local/lib/python3.6/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view
    return view_func(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/rest_framework/viewsets.py", line 125, in view
    return self.dispatch(request, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/rest_framework/views.py", line 509, in dispatch
    response = self.handle_exception(exc)
  File "/usr/local/lib/python3.6/site-packages/rest_framework/views.py", line 469, in handle_exception
    self.raise_uncaught_exception(exc)
  File "/usr/local/lib/python3.6/site-packages/rest_framework/views.py", line 480, in raise_uncaught_exception
    raise exc
  File "/usr/local/lib/python3.6/site-packages/rest_framework/views.py", line 506, in dispatch
    response = handler(request, *args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/rest_framework/mixins.py", line 19, in create
    self.perform_create(serializer)
  File "./dojo/api_v2/views.py", line 1325, in perform_create
    serializer.save(push_to_jira=push_to_jira)
  File "./dojo/api_v2/serializers.py", line 1101, in save
    raise Exception('Error while parsing the report, did you specify the correct scan type ?')
 Ensure it's set on all web pages returned by your site (if you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's "frame-ancestors" directive.

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options

16
15
3

10038
10038
Content Security Policy (CSP) Header Not Set
Content Security Policy (CSP) Header Not Set
2
3
Medium (High)

Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.

http://<IP_ADDRESS>/vulnerabilities/fi/?page=include.php
GET

http://<IP_ADDRESS>/instructions.php
GET

http://<IP_ADDRESS>/vulnerabilities/sqli/
GET

http://<IP_ADDRESS>/vulnerabilities/exec/
GET

http://<IP_ADDRESS>/sitemap.xml
GET

http://<IP_ADDRESS>/setup.php
GET

http://<IP_ADDRESS>/
GET

http://<IP_ADDRESS>/vulnerabilities/captcha/
GET

http://<IP_ADDRESS>/vulnerabilities/upload/
GET

http://<IP_ADDRESS>/vulnerabilities/brute/
GET

http://<IP_ADDRESS>/vulnerabilities/csrf/
GET

11

Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header, to achieve optimal browser support: "Content-Security-Policy" for Chrome 25+, Firefox 23+ and Safari 7+, "X-Content-Security-Policy" for Firefox 4.0+ and Internet Explorer 10+, and "X-WebKit-CSP" for Chrome 14+ and Safari 6+.

https://developer.mozilla.org/en-US/docs/Web/Security/CSP/Introducing_Content_Security_Policy

https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html

http://www.w3.org/TR/CSP/

http://w3c.github.io/webappsec/specs/content-security-policy/csp-specification.dev.html

http://www.html5rocks.com/en/tutorials/security/content-security-policy/

http://caniuse.com/#feat=contentsecuritypolicy

http://content-security-policy.com/

16
15
3

10108
10108
Reverse Tabnabbing
Reverse Tabnabbing
2
2
Medium (Medium)

At least one link on this page is vulnerable to Reverse tabnabbing as it uses a target attribute without using both of the "noopener" and "noreferrer" keywords in the "rel" attribute, which allows the target page to take control of this page.

http://<IP_ADDRESS>/vulnerabilities/brute/
GET
https://www.owasp.org/index.php/Testing_for_Brute_Force_(OWASP-AT-004)

http://<IP_ADDRESS>/
GET
VirtualBox

http://<IP_ADDRESS>/vulnerabilities/sqli/
GET
http://www.securiteam.com/securityreviews/5DP0N1P76E.html

http://<IP_ADDRESS>/vulnerabilities/sqli_blind/
GET
http://www.securiteam.com/securityreviews/5DP0N1P76E.html

http://<IP_ADDRESS>/vulnerabilities/xss_d/
GET
https://www.owasp.org/index.php/Cross-site_Scripting_(XSS)

http://<IP_ADDRESS>/instructions.php
GET
https://www.virtualbox.org/

http://<IP_ADDRESS>/vulnerabilities/csrf/
GET
https://www.owasp.org/index.php/Cross-Site_Request_Forgery

http://<IP_ADDRESS>/vulnerabilities/upload/
GET
https://www.owasp.org/index.php/Unrestricted_File_Upload

http://<IP_ADDRESS>/vulnerabilities/fi/?page=include.php
GET
https://en.wikipedia.org/wiki/Remote_File_Inclusion

http://<IP_ADDRESS>/vulnerabilities/captcha/
GET
https://www.google.com/recaptcha/admin/create

http://<IP_ADDRESS>/vulnerabilities/exec/
GET
http://www.scribd.com/doc/2530476/Php-Endangers-Remote-Code-Execution

11

Do not use a target attribute, or if you have to then also add the attribute: rel="noopener noreferrer".

https://owasp.org/www-community/attacks/Reverse_Tabnabbing

https://dev.to/ben/the-targetblank-vulnerability-by-example

https://mathiasbynens.github.io/rel-noopener/

https://medium.com/@jitbit/target-blank-the-most-underestimated-vulnerability-ever-96e328301f4c

3

10096
10096
Timestamp Disclosure - Unix
Timestamp Disclosure - Unix
0
1
Informational (Low)

A timestamp was disclosed by the application/web server - Unix

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
1019803690

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
1839030562

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
909522486

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
722521979

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
40341101

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
1309151649

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
1732584194

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
405537848

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
1894986606

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
1473231341

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
155497632

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
1990404162

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
1700485571

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
1069501632

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
38016083

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
2022574463

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
373897302

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
1163531501

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
643717713

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
1444681467

67

Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.

1019803690, which evaluates to: 2002-04-26 06:48:10

http://projects.webappsec.org/w/page/13246936/Information%20Leakage

200
13
3

10036
10036
Server Leaks Version Information via "Server" HTTP Response Header Field
Server Leaks Version Information via "Server" HTTP Response Header Field
1
3
Low (High)

The web/application server is leaking version information via the "Server" HTTP response header.  The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.

CSRF attacks are effective in a number of situations, including:

    * The victim has an active session on the target site.

    * The victim is authenticated via HTTP auth on the target site.

    * The victim is on the same local network as the target site.

CSRF has primarily been used to perform an action against a target site using the victim's privileges, but recent techniques have been discovered to disclose information by gaining access to the response. The risk of information disclosure is dramatically increased when the target site is vulnerable to XSS, because XSS can be used as a platform for CSRF, allowing the attack to operate within the bounds of the same-origin policy.

http://<IP_ADDRESS>/vulnerabilities/xss_d/
GET
<form name="XSS" method="GET">

http://<IP_ADDRESS>/vulnerabilities/captcha/
GET
<form action="#" method="POST" style="display:none;">

http://<IP_ADDRESS>/vulnerabilities/xss_s/
GET
<form method="post" name="guestform" ">

http://<IP_ADDRESS>/vulnerabilities/csrf/
GET
<form action="#" method="GET">

http://<IP_ADDRESS>/setup.php
GET
<form action="#" method="post">

http://<IP_ADDRESS>/vulnerabilities/brute/
GET
<form action="#" method="GET">

http://<IP_ADDRESS>/vulnerabilities/sqli/
GET
<form action="#" method="GET">

http://<IP_ADDRESS>/vulnerabilities/weak_id/
GET
<form method="post">

http://<IP_ADDRESS>/vulnerabilities/exec/
GET
<form name="ping" action="#" method="post">

http://<IP_ADDRESS>/vulnerabilities/sqli_blind/
GET
<form action="#" method="GET">

http://<IP_ADDRESS>/vulnerabilities/xss_r/
GET
<form name="XSS" action="#" method="GET">

http://<IP_ADDRESS>/vulnerabilities/upload/
GET
<form enctype="multipart/form-data" action="#" method="POST">

12

Phase: Architecture and Design

Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

For example, use anti-CSRF packages such as the OWASP CSRFGuard.

Phase: Implementation

Ensure that your application is free of cross-site scripting issues, because most CSRF defenses can be bypassed using attacker-controlled script.

Phase: Architecture and Design

Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).

Note that this can be bypassed using XSS.

Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.

Note that this can be bypassed using XSS.

Use the ESAPI Session Management control.

This control includes a component for CSRF.

Do not use the GET method for any request that triggers a state change.

Phase: Implementation

Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.

No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF] was found in the following HTML form: [Form 1: "" ].

http://projects.webappsec.org/Cross-Site-Request-Forgery

http://cwe.mitre.org/data/definitions/352.html

352
9
3

10031
10031
User Controllable HTML Element Attribute (Potential XSS)
User Controllable HTML Element Attribute (Potential XSS)
0
1
Informational (Low)

This check looks at user-supplied input in query string parameters and POST data to identify where certain HTML attribute values might be controlled. This provides hot-spot detection for XSS (cross-site scripting) that will require further review by a security analyst to determine exploitability.

http://<IP_ADDRESS>/vulnerabilities/captcha/
POST
Change

http://<IP_ADDRESS>/vulnerabilities/exec/
POST
Submit

http://<IP_ADDRESS>/vulnerabilities/csrf/?Change=Change&password_conf=ZAP&password_new=ZAP
GET
Change

http://<IP_ADDRESS>/vulnerabilities/captcha/
POST
Change

http://<IP_ADDRESS>/vulnerabilities/exec/
POST
Submit

http://<IP_ADDRESS>/vulnerabilities/brute/?Login=Login&password=ZAP&username=ZAP
GET
Login

http://<IP_ADDRESS>/vulnerabilities/upload/
POST
MAX_FILE_SIZE

http://<IP_ADDRESS>/vulnerabilities/upload/
POST
Upload

http://<IP_ADDRESS>/vulnerabilities/upload/
POST
Upload

http://<IP_ADDRESS>/vulnerabilities/upload/
POST
Upload

http://<IP_ADDRESS>/vulnerabilities/brute/?Login=Login&password=ZAP&username=ZAP
GET
Login

http://<IP_ADDRESS>/vulnerabilities/csrf/?Change=Change&password_conf=ZAP&password_new=ZAP
GET
Change

http://<IP_ADDRESS>/vulnerabilities/exec/
POST
Submit

13

Validate all input and sanitize output it before writing to any HTML attributes.

User-controlled HTML attribute values were found. Try injecting special characters to see if XSS might be possible. The page at the following URL:

http://<IP_ADDRESS>/vulnerabilities/captcha/

appears to include user input in:

a(n) [input] tag [name] attribute

The user input found was:

Change=Change

The user-controlled value was:

change

http://websecuritytool.codeplex.com/wikipage?title=Checks#user-controlled-html-attribute

20
20
3

10024
10024
Information Disclosure - Sensitive Information in URL
Information Disclosure - Sensitive Information in URL
0
2
Informational (Medium)

The request appeared to contain sensitive information leaked in the URL. This can violate PCI and most organizational compliance policies. You can configure the list of strings for this check to add or remove values specific to your environment.

http://<IP_ADDRESS>/vulnerabilities/brute/?Login=Login&password=ZAP&username=ZAP
GET
username
  username

http://<IP_ADDRESS>/vulnerabilities/csrf/?Change=Change&password_conf=ZAP&password_new=ZAP
GET
password_conf
  password_conf

http://<IP_ADDRESS>/vulnerabilities/brute/?Login=Login&password=ZAP&username=ZAP
GET
password
  password

http://<IP_ADDRESS>/vulnerabilities/csrf/?Change=Change&password_conf=ZAP&password_new=ZAP
GET
password_new
  password_new

4

Do not pass sensitive information in URIs.

The URL contains potentially sensitive information. The following string was found via the pattern: user

username

200
13
3

10054
10054
Cookie Without SameSite Attribute
Cookie Without SameSite Attribute
1
2
Low (Medium)

A cookie has been set without the SameSite attribute, which means that the cookie can be sent as a result of a 'cross-site' request. The SameSite attribute is an effective counter measure to cross-site request forgery, cross-site script inclusion, and timing attacks.

http://<IP_ADDRESS>/security.php
POST

http://<IP_ADDRESS>/security.php
POST
PHPSESSID
  Set-Cookie: PHPSESSID

http://<IP_ADDRESS>/vulnerabilities/weak_id/
POST

3

Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.

https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site

16
13
3

10029
10029
Cookie Poisoning
Cookie Poisoning
0
1
Informational (Low)

This check looks at user-supplied input in query string parameters and POST data to identify where cookie parameters might be controlled. This is called a cookie poisoning attack, and becomes exploitable when an attacker can manipulate the cookie in various ways. In some cases this will not be exploitable, however, allowing URL parameters to set cookie values is generally considered a bug.

http://<IP_ADDRESS>/security.php
POST
security

1

Do not allow user input to control cookie names and values. If some query string parameters must be set in cookie values, be sure to filter out semicolon's that can serve as name/value pair delimiters.

An attacker may be able to poison cookie values through POST parameters. To test if this is a more serious issue, you should try resending that request as a GET, with the POST parameter included as a query string parameter. For example:  http://nottrusted.com/page?value=maliciousInput.

This was identified at:

http://<IP_ADDRESS>/security.php

User-input was found in the following cookie:

security=low

The user input was:

security=low

http://websecuritytool.codeplex.com/wikipage?title=Checks#user-controlled-cookie

20
20
3

10021
10021
X-Content-Type-Options Header Missing
X-Content-Type-Options Header Missing
1
2
Low (Medium)

The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.

http://<IP_ADDRESS>/vulnerabilities/upload/
GET
X-Content-Type-Options

http://<IP_ADDRESS>/
GET
X-Content-Type-Options

http://<IP_ADDRESS>/robots.txt
GET
X-Content-Type-Options

http://<IP_ADDRESS>/instructions.php
GET
X-Content-Type-Options

http://<IP_ADDRESS>/vulnerabilities/fi/?page=include.php
GET
X-Content-Type-Options

http://<IP_ADDRESS>/vulnerabilities/sqli/
GET
X-Content-Type-Options

http://<IP_ADDRESS>/vulnerabilities/captcha/
GET
X-Content-Type-Options

http://<IP_ADDRESS>/vulnerabilities/csrf/
GET
X-Content-Type-Options

http://<IP_ADDRESS>/vulnerabilities/brute/
GET
X-Content-Type-Options

http://<IP_ADDRESS>/vulnerabilities/exec/
GET
X-Content-Type-Options

http://<IP_ADDRESS>/setup.php
GET
X-Content-Type-Options

11

Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.

If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.

This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type.

At "High" threshold this scan rule will not alert on client or server error responses.

http://msdn.microsoft.com/en-us/library/ie/gg622941%28v=vs.85%29.aspx

https://owasp.org/www-community/Security_Headers

16
15
3

10017
10017
Cross-Domain JavaScript Source File Inclusion
Cross-Domain JavaScript Source File Inclusion
1
2
Low (Medium)

The page includes one or more script files from a third-party domain.

http://<IP_ADDRESS>/vulnerabilities/captcha/
POST
https://www.google.com/recaptcha/api.js

http://<IP_ADDRESS>/vulnerabilities/captcha/
GET
https://www.google.com/recaptcha/api.js

2

Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.

829
15
3

10109
10109
Modern Web Application
Modern Web Application
0
2
Informational (Medium)

The application appears to be a modern web application. If you need to explore it automatically then the Ajax Spider may well be more effective than the standard one.

http://<IP_ADDRESS>/phpinfo.php
GET
apache2handler

1

This is an informational alert and so no changes are required.

Links have been found that do not have traditional href attributes, which is an indication that this is a modern web application.

3

10010
10010
Cookie No HttpOnly Flag
Cookie No HttpOnly Flag
1
2
Low (Medium)

A cookie has been set without the HttpOnly flag, which means that the cookie can be accessed by JavaScript. If a malicious script can be run on this page then the cookie will be accessible and can be transmitted to another site. If this is a session cookie then session hijacking may be possible.

http://<IP_ADDRESS>/security.php
POST
PHPSESSID
  Set-Cookie: PHPSESSID

http://<IP_ADDRESS>/security.php
POST

http://<IP_ADDRESS>/vulnerabilities/weak_id/
POST

3

Ensure that the HttpOnly flag is set for all cookies.

https://owasp.org/www-community/HttpOnly

16
13
3

10027
10027
Information Disclosure - Suspicious Comments
Information Disclosure - Suspicious Comments
0
2
Informational (Medium)

The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.

http://<IP_ADDRESS>/setup.php
GET
db

1

Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.

The following pattern was used: \bDB\b and was detected in the element starting with: "", see evidence field for the suspicious comment/snippet.

200
13
3

10023
10023
Information Disclosure - Debug Error Messages
Information Disclosure - Debug Error Messages
1
2
Low (Medium)

The response appeared to contain common error messages returned by platforms such as ASP.NET, and Web-servers such as IIS and Apache. You can configure the list of common debug messages.

http://<IP_ADDRESS>/instructions.php
GET
PHP warning

http://<IP_ADDRESS>/instructions.php?doc=readme
GET
PHP warning

2

Disable debugging messages before pushing to production.

200
13
3

10027
10027
Information Disclosure - Suspicious Comments
Information Disclosure - Suspicious Comments
0
1
Informational (Low)

The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.

http://<IP_ADDRESS>/vulnerabilities/javascript/
POST
from

http://<IP_ADDRESS>/vulnerabilities/javascript/
GET
from

2

Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.

The following pattern was used: \bFROM\b and was detected in the element starting with: "


A few cleanups on tile hashing

Rename global_hash to agg_tiles_hash

This is still a big sticking point: what should be the name for the metadata key for this value? The value represents the hash of all z,x,y,tile over all rows of the tiles table (or view).  Should it include md5 in its name, or should the hash be auto-detected by its length? (details in #856)

Generate it based on tiles table/view
validate or generate, but not both (it will always fail otherwise)
break up logic for per-tile, total, and integrity checks
delete unused sqlx prep file

If it's true each hash digest has a unique byte length, I prefer the auto-guessing as it's simple and allow algorithms not MD5.
If we choose auto-guessing, should we allow user to choose algorithms when generating hash?

eventually we could let users pick algorithms - not very difficult, but not worth our time at the moment i think - md5 has worked pretty well for this usecase, despite being ... cryptographically poor.  I agree about autoguessing.  I think agg_tiles_hash sounds best, as it is both short, and implies aggregation

feature
drawback

algorithm in name
explain its algorithm explicitly
different name across mbtile files like tiles_md5_hash in file1, tiles_sha1_hash in file2

guessing
explain its algorithm implicitly; consistent metadata name across mbtile files

Did a quick overview, all looks good to me.

I walked @GeoKarim (my coworker) through the code to make sure there are no obvious oopsies


Allow arguments for backend commands

I love that the django backend is (being) implemented!
So it looks like the commands (migrate, makemigrations and showmigrations) are hardcoded in the backend component via django.core.management.call_command.
As a result it's currently not possible to add parameters or options to the commands like eg. apistar makemigrations --dry-run.
Those possible arguments should probably be supported in a generic way for all commands of various backends, shouldn't it?

Those possible arguments should probably be supported in a generic way for all commands of various backends, shouldn't it?

Absolutely, yup!

Let's close this off at the moment, as it's not currently relevant given the 0.4 re-write.


Add 1.10.1 and 1.9.5

Go 1.10.1 and Go 1.9.5 are released
https://groups.google.com/forum/#!topic/golang-announce/IkPkOF8JqLs

Thank you @ttakezawa .
https://github.com/syndbg/goenv/releases/tag/1.12.0 released! :raised_hands:


better ncbi errors

Codecov Report
Attention: Patch coverage is 18.18182% with 9 lines in your changes missing coverage. Please review.

Project coverage is 85.51%. Comparing base (352a0e3) to head (79eb034).

Files with missing lines
Patch %
Lines

src/components/sources/SourceGenomeRegion.jsx
0.00%
8 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #328      +/-   ##
==========================================
- Coverage   85.67%   85.51%   -0.16%
==========================================
  Files         121      121
  Lines        3699     3708       +9
  Branches      793      796       +3
==========================================
+ Hits         3169     3171       +2
- Misses        491      497       +6
- Partials       39       40       +1

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


use not_planned close reason

closes #379
https://github.blog/changelog/2022-05-19-the-new-github-issues-may-19th-update/ says

We have added a new state_reason attribute to our REST API, GraphQL API and webhooks. These are currently in preview and will be fully shipped in the upcoming week.

but it looks the docs aren't updated given https://github.com/actions/stale/issues/744 has been done I'm assuming it works.
Not sure if you also want an option for this or happy just switching to it?

Anyone? Please merge. Thanks!

Waiting for this feature. Is there any estimate for its release?

It would be great if this got released

I am starting to think that this repo really lives up to its name.

Ran into this issue confusing community members on our repo, please can we consider merging it.

@gr2m ?

The app is defacto unmaintained and we recommend to use the action instead.

we made it official: both the app and this repository are now deprecated.


Remove old RSA CRT names.

Fixes #19488
The constants OSSL_PKEY_PARAM_RSA_FACTOR, OSSL_PKEY_PARAM_RSA_EXPONENT, and OSSL_PKEY_PARAM_RSA_COEFFICIENT are not valid OSSL_PARAMS keys. Using them results in the parameters being ignored if they are passed to fromdata. The result of this is that it would use just n, e and d when performing operations, instead of CRT related operations (such as rsa_mod_exp)
The correct values include an index such as OSSL_PKEY_PARAM_RSA_FACTOR1, OSSL_PKEY_PARAM_RSA_EXPONENT1 and OSSL_PKEY_PARAM_RSA_COEFFICIENT1.
The data driven self tests have been updated to use the correct values.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

OTC: This is a breaking change. But using the removed values as supplied is not doing what the user intended. This may force the user to update their code.
Note: setting CRT parameters using fromdata is not likely to be a common operation.

It is very common to use fromdata to import when coming from other protocols.
That things "worked" but were just slower (and hence missed) makes this one a bit of a nasty bug.

Note that this is correctly documented in the RSA related pod file..

Note also that https://github.com/openssl/openssl/pull/19443 fixes the demo that used this..

As per @t-j-h suggestion, I have left the values in and pointed them to existing values. This will break during runtime as opposed to not compile. Tests added to prove this happens.

Depends on https://github.com/openssl/openssl/pull/19501


Add more info

https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/conceptual-resilient-sdk-applications#connectivity-modes
It says "Direct mode uses the TCP protocol". This is only true for v2 if you set ConnectionPolicy.ConnectionProtocol to Tcp, otherwise it'll use HTTPS. I think this should be included here for clarity since Direct/HTTPS is a valid mode in v2.
See this answer:
https://stackoverflow.com/a/74405199/2063755

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

ID: 3204e7a7-fc38-9fa6-232a-f946fb481c8e
Version Independent ID: 4ba997aa-7d75-cd5e-4cbc-2ec1b1249458
Content: Designing resilient applications with Azure Cosmos DB SDKs
Content Source: articles/cosmos-db/nosql/conceptual-resilient-sdk-applications.md
Service: cosmos-db
Sub-service: nosql
GitHub Login: @ealsur
Microsoft Alias: maquaran

Hi @DavidKlempfner,
Thanks for the feedback. We will look into this and update as appropriate.

Hi @ealsur,
Could you please look into this request. Thanks

V2 is on deprecation path in the next couple of months, the documentation used to have Direct/HTTPs but it was removed in favor of more recent content. Adding it back when it's about to be deprecated would add little value.

Hello @DavidKlempfner,
We have softened the language to say that Direct mode typically use TCP. Since using HTTP mode with TCP is no longer a recommendation or possibility, we don't want to promote that in the docs.
The change should be live later today.


Move gem group setting to separate, cacheable file

Previously we stored installed gem groups in the Homebrew settings file (gitconfig). This made sense, but this PR changes that to use a separate file instead.
The benefit of doing so is so that the file can be cached in GitHub Actions, so the same cache can be used across multiple CI workflows even if the groups used in each are different. Otherwise, the previous behaviour would be to just uninstall all the groups not requested in that workflow.

Thanks again @Bo98!


Targeted Assets section bug

When the 'Equities' field in the target section is updated, the 'Gold' field is set to the same value. The same problem exists for the 'Bonds' and 'Cash' field.

Targeted Assets, for purposes of "glide path" allocations, are not currently functional.  I'm going to relabel this as an enhancement, since it is just part of the core functionality that needs to be finished.


Installation issue with python setup.py install

WARNING: '' not a valid package name; please use only .-separated package names in setup.py

Now you can install the package using pip install . without any warnings.


Use six.add_metaclass to support py37

six.with_metaclass fails under python 3.7. Six has another
metaclass-constructor that does not suffer the same failure.
https://bitbucket.org/gutworth/six/pull-requests/12/add-patch_with_metaclass-which-provides-a/diff

Somebody please merge this

@todofixthis, any updates? Can you reach someone who has permissions to merge this? It would be great to get this done and have it Python 3.7 compatible.

Hello, Could someone merge this, please?

+1

Hey @Panos512 @infothrill I apologise that there's been radio silence on this one.  I no longer work at EFL Global (now LenddoEFL); I'll see if I can get in touch with someone though.

Hi @Panos512 @infothrill I'm really sorry that this is taking so long.  I have gotten in touch with someone at LenddoEFL, and they are working on it.
If we don't have resolution within the next couple of days, I will fork this project and release it under a different name.

Hey @Panos512 @infothrill I apologise that it has taken so long to address this.
I have forked the project, removed support for Python 2, added support for Python 3.7 and 3.8 as well as pypy3.
The new project is called phx-class-registry, and I will be maintaining this project personally from now on.

awesome. thank you

Perfect! Thanks a lot!


Unable to load Tapo integration

Getting the following error in logs since upgrading HA last two updates....
Logger: homeassistant.setup
Source: setup.py:162
First occurred: 18:57:09 (1 occurrences)
Last logged: 18:57:09
Setup failed for custom integration tapo: Requirements for tapo not found: ['plugp100==2.1.14'].
Have been unable to remove integration although I have reloaded it.

I have a feeling this maybe the change to the python version that HA Core now ships with, they have updated it to 3.10 so I think the dev will have to update the python maybe? I'm theorising

The author is working on it:
https://github.com/petretiandrea/home-assistant-tapo-p100/issues/199#issuecomment-1177879540

Refers to #199


Bumped dependencies

All tests pass and I verified it manually using ember-cli and the tape fixtures
@airportyh r?

Sorry for the late response, was tied up for a couple of days. You are good to merge and publish on npm yourself now that I've added you as a contributor. Try it and let me know if you run into any issues.


Please how to solve this problem？

my enviroment is windows,cu117,cp38,on python virtual enviroment.

Do you konw how to solve it? I had the same problem.

I solved this problem by installing Microsoft Visual Studio. Because I found that the place the error happening(backend.py) was looking for cl.exe
But I'm not sure this is a reasonable approach.

Hi, have you guys tried the below code block from ReadMe page?
Mine is Ubuntu, but i solved the same problem by the below build block
Hope it works!
+)refers to @Visytudz, installing VS code  can auto build raymarching folders, too.
`# install all extension modules
bash scripts/install_ext.sh
if you want to install manually, here is an example:
cd raymarching
python setup.py build_ext --inplace # build ext only, do not install (only can be used in the parent directory)
pip install . # install to python path (you still need the raymarching/ folder, since this only install the built extension.)`

my enviroment is windows,cu117,cp38,on python virtual enviroment.

解决了吗


Adding missing fields to User

I needed these two fields for a personal project (though I know they're pretty easy to come up with... nonetheless, feel free to reject this should you think it's not required.
Note: I had to explicitly define circe's en/decoders on User's companion object and use semiauto instead of auto in Users. Not sure why I had to but I kept having weird DerivedDecoder issues without this change.

@mfirry Thank you for this contribution. At first, it looks good.
Did you try to run the tests? I'm not sure if you may need to update the tests too. I cannot try them now, but I could do it later.

I had to explicitly define circe's en/decoders on User's companion object and use semiauto instead of auto in Users. Not sure why I had to but I kept having weird DerivedDecoder issues without this change.

Weird, what kind of issue were you getting?

So at first I figured I could "just" add the two fields (both as Option[String]). I did that and published it locally and tried it (as a dep of my project) and I had the following:
(it's a Play app)
play.api.http.HttpErrorHandlerExceptions$$anon$1: Execution exception[[RuntimeException: java.lang.NoSuchMethodError: github4s.free.domain.User.<init>(ILjava/lang/String;Ljava/lang/String;Ljava/lang/String;Lscala/Option;Lscala/Option;Lscala/Option;Lscala/Option;Lscala/Option;Lscala/Option;)V]]
  at play.api.http.HttpErrorHandlerExceptions$.throwableToUsefulException(HttpErrorHandler.scala:323)
  at play.api.http.DefaultHttpErrorHandler.onServerError(HttpErrorHandler.scala:243)
  at play.core.server.AkkaHttpServer$$anonfun$1.applyOrElse(AkkaHttpServer.scala:382)
  at play.core.server.AkkaHttpServer$$anonfun$1.applyOrElse(AkkaHttpServer.scala:380)
  at scala.concurrent.Future.$anonfun$recoverWith$1(Future.scala:417)
  at scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:41)
  at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:64)
  at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:55)
  at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:91)
  at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
Caused by: java.lang.RuntimeException: java.lang.NoSuchMethodError: github4s.free.domain.User.<init>(ILjava/lang/String;Ljava/lang/String;Ljava/lang/String;Lscala/Option;Lscala/Option;Lscala/Option;Lscala/Option;Lscala/Option;Lscala/Option;)V
  at play.api.mvc.ActionBuilder$$anon$10.apply(Action.scala:425)
  at play.api.mvc.Action.$anonfun$apply$2(Action.scala:97)
  at play.api.libs.streams.StrictAccumulator.$anonfun$mapFuture$4(Accumulator.scala:175)
  at scala.util.Try$.apply(Try.scala:213)
  at play.api.libs.streams.StrictAccumulator.$anonfun$mapFuture$3(Accumulator.scala:175)
  at scala.Function1.$anonfun$andThen$1(Function1.scala:57)
  at scala.Function1.$anonfun$andThen$1(Function1.scala:57)
  at scala.Function1.$anonfun$andThen$1(Function1.scala:57)
  at play.api.libs.streams.StrictAccumulator.run(Accumulator.scala:208)
  at play.core.server.AkkaHttpServer.$anonfun$runAction$4(AkkaHttpServer.scala:376)
Caused by: java.lang.NoSuchMethodError: github4s.free.domain.User.<init>(ILjava/lang/String;Ljava/lang/String;Ljava/lang/String;Lscala/Option;Lscala/Option;Lscala/Option;Lscala/Option;Lscala/Option;Lscala/Option;)V
  at github4s.api.Users$anon$importedDecoder$macro$25$1$anon$macro$23$1.from(Users.scala:45)
  at github4s.api.Users$anon$importedDecoder$macro$25$1$anon$macro$23$1.from(Users.scala:45)
  at shapeless.LabelledGeneric$$anon$1.from(generic.scala:229)
  at shapeless.LabelledGeneric$$anon$1.from(generic.scala:226)
  at io.circe.generic.decoding.DerivedDecoder$$anon$1.apply(DerivedDecoder.scala:15)
  at io.circe.Decoder.decodeJson(Decoder.scala:64)
  at io.circe.Decoder.decodeJson$(Decoder.scala:64)
  at io.circe.generic.decoding.DerivedDecoder.decodeJson(DerivedDecoder.scala:6)
  at io.circe.Parser.finishDecode(Parser.scala:13)
  at io.circe.Parser.finishDecode$(Parser.scala:9)
[info] p.c.s.AkkaHttpServer - Stopping server...

Hi @mfirry.
I believe you're having a binary compatibility issue between the library that's currently published (0.20.0), and the one you've published locally.
The error you're receiving says that the current github4s artifact in your classpath doesn't have all those fields.
Can you share your libraryDependencies value to see if there's any issue there?
you could try doing a sbt clean, followed by bumping github4s version & releasing locally, followed by depending on the new locally published dependency in your play app.  That should work?

Hi @pepegar,
"com.47deg"     %% "github4s"     % "0.20.1-SNAPSHOT" is on my deps list.
I'll try what you suggest and update this PR if it works.
Thanks a lot.

Looks like you were right @pepegar. I'll update this in a minute.

I might need to add more fields (like bio, email and so on...).
Should I do this in one big PR (this one) or smaller ones?

@mfirry regarding adding more fields, I don't have a strong opinion. If you want to keep adding commits to this PR is fine from my side. Just mark this PR as WIP and ping us when you're done.

I think I'm done here.

I'm re-thinking about the following and followers part... I might add getFollowing and getFollowers to the User algebra. I'll make a quick try and let you guys know.
Having a url as a String field of the User does not seem very useful.

Ok it does work but the User object in the /following call is slightly different than the one in the /users/_username_ (for example it misses the public_repos field).
How to go about it?

having lots of optional fields
define another User case class (think LightUser) with less fields

I'll spend the weekend thinking about.
What's your take?

Hi @mfirry,
hum... that's tricky :)
How many different fields are there? My gut feeling is that, if there's no a lot of different fields I prefer to keep a single entity User.
If the fields change a lot though, it may make sense to have different entities.
Sorry to give you such a vague answer :)
I think we could discuss it much better if you can push your WIP to see how many optional fields we end up with.

To answer your question, here's the list of fields you get from the users api and you don't get from the following one:
<   "name": "Tom Preston-Werner",
<   "company": null,
<   "blog": "http://tom.preston-werner.com",
<   "location": "San Francisco",
<   "email": null,
<   "hireable": null,
<   "bio": null,
<   "public_repos": 61,
<   "public_gists": 62,
<   "followers": 21344,
<   "following": 11,
<   "created_at": "2007-10-20T05:24:19Z",
<   "updated_at": "2018-12-18T19:52:12Z"

Of all of these, in this PR, I've added hirebale, bio and public_repos...
Here's what I figured I could do: I'm gonna set public_repos as Option[Int] and end this one here.
I'll open a separate PR in order to be able to add the GetFollowing to the Users ops ADT.
Deal? :)

Hey @mfirry, sorry I forgot about this. I'll review it ASAP, thank you!

Hi @mfirry, thanks for your contribution! I think your changes are good! However you have to fix also the test so we can have a green in travis and merge your PR 🙂
Fix the tests so we can fully review you PR!!
Thanks! 😄

Uh sorry. My bad. Don't know how that happened. Fixing it as we speak.

So some integration tests fail... but it's not clear to me whether I can do anything about it. Can somebody else have a look and point me to the right direction?
Thanks


lsm9ds0 driver: FIX + dts support

lsm9ds0 driver: FIX + dts support (Address issue #9962)

Codecov Report

Merging #12136 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #12136   +/-   ##
=======================================
  Coverage   48.05%   48.05%
=======================================
  Files         284      284
  Lines       43368    43368
  Branches    10397    10397
=======================================
  Hits        20840    20840
  Misses      18388    18388
  Partials     4140     4140

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 e841d42...e806bd0. Read the comment docs.


The position of activity view is not right

when I run app from xcode, it is all good. But when I click on the icon from my phone,[self.view makeToastActivity:CSToastPositionCenter];  shows on the top left.


[RESOLVED] High ICMP ping response time

Problem started at 08:14:29 on 2023.04.13
Problem name: High ICMP ping response time
Host: HP_iLO
Severity: Warning
Operational data: Value: 5ms
Original problem ID: 16138
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23268&eventid=16138

Problem has been resolved in 3m 0s at 08:17:29 on 2023.04.13
Problem name: High ICMP ping response time
Host: HP_iLO
Severity: Warning
Original problem ID: 16138


Less Sourcemap only references files inside 'styles' config

Bug Report or Feature Request
- [x] bug report
- [ ] feature request

Versions.

@angular/cli: 1.0.0-rc.2
macOS El Capitan
Repro steps.

My angular-cli.json:
 "styles": [
        "styles.less"
      ],

My styles.less
@import "less/vars";
@import "less/base";
@import "less/layout";
// ...etc.

When I run ng serve -ec -sm I can see the sourcemap file generated, but Chrome's devtools lists styles.less as the sole source file instead of base.less or layout.less, etc.
The log given by the failure.

Here's what I skimmed out of the generated sourcemap file. You can see there's no mention of the imported files whatsoever.
{"version":3,"sources":["webpack:///./src/styles.less"], ... \n\n\n\n// WEBPACK FOOTER //\n// ./src/styles.less"],"sourceRoot":""}

Desired functionality.

I should see the individual imported files in the Chrome devtools and not just the main file.
Mention any other details that might be useful.

Wonder if this is solved by today's release of less-loader v4.0.0?

I was able to verify that this is still an issue on new 1.0.0 projects using Less as the preprocessor.

@cvharris would you check the latest Angular CLI release?

Closing the issue due to inactivity. If the problem still exists in the latest version of the CLI, please open a new issue following the template and providing a minimal demo where we can reproduce it. Thanks! :-)


30 - US: As an author, I want to comment on posts that I can access

[ ] Documentation
[ ] Tests

#52


CQ-4349511 Fixed name field in dialog not checking for invalid characters

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes and the overall coverage did not decrease.
[ ] All unit tests pass on CircleCi.
[ ] I ran all tests locally and they pass.

As discussed in the scrum logged a ticket for aligning element name with AF2 spec
https://jira.corp.adobe.com/browse/CQ-4349643
cc: @nit23uec


custom data management (for multiple tenant Kafka)

Codecov Report

Merging #456 (d6999bb) into main (3fd2287) will decrease coverage by 0.23%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #456      +/-   ##
==========================================
- Coverage   80.59%   80.36%   -0.24%
==========================================
  Files          70       70
  Lines        8154     8198      +44
==========================================
+ Hits         6572     6588      +16
- Misses       1225     1253      +28
  Partials      357      357

Impacted Files
Coverage Δ

pkg/cluster/layout.go
89.47% <0.00%> (-10.53%)
:arrow_down:

pkg/object/mqttproxy/session.go
74.23% <0.00%> (-7.98%)
:arrow_down:

pkg/cluster/cluster.go
49.65% <0.00%> (-2.05%)
:arrow_down:

pkg/object/mqttproxy/client.go
77.16% <0.00%> (-0.51%)
:arrow_down:

pkg/filter/proxy/request.go
95.45% <0.00%> (+0.14%)
:arrow_up:

pkg/cluster/config.go
89.07% <0.00%> (+0.18%)
:arrow_up:

pkg/filter/proxy/server.go
73.54% <0.00%> (+2.95%)
:arrow_up:

pkg/object/pipeline/mock.go
86.95% <0.00%> (+5.94%)
: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 3fd2287...d6999bb. Read the comment docs.

@localvar please add some documents for this feature.

This feature is ready for the requirement of multiple tenant Kafka now, but the idea of this feature is the same as the CustomResource feature in EaseMesh. So I will do a refactor to avoid code duplication, but this may introduce some changes, so I plan to write the document after the refactor, is this fine?

fine. you can include the documents in the refactor.


Allow to follow symlink / open original from explorer

Since #11539, explorer indicates symlinks like this:

It would be nice to be able to navigate to the actual location quickly, either by a command in a context menu or something like Cmd+click on the arrow.

Good question. I only had this specific node_modules/.bin use case in mind in which case the explorer sidebar would just "scroll" me to the right location but you're right that the file might live outside of the workspace. In that case, probably the best behavior would be to open Finder / Windows Explorer on that file.

The same as if I opened the symlinked file and invoked "Reveal Active File in Sidebar".
For example, <workspace>/node_modules/.bin/tsc is a symlink to <workspace>/node_modules/typescript/bin/tsc. When I invoke this hypothetical Show Original command, it scrolls me from .bin/tsc to typescript/bin/tsc in VSCode's explorer.

@borekb in most cases the symlinked file is probably not in the explorer tree but somewhere outside, what should hapen then?

I think it would be best then to open the file in Finder / Windows Explorer as suggested above.

For those coming across this issue, I've tried the Symlink Follow extension by zaucy and it works well for this.


Envisalink Fixes + Enhancements

Description:

Contains fixes that allow the envisalink component to play nicely with the asyncio changes being made in HASS.
Added the ability to trigger the alarm from HASS using the DSC/Honeywell 'panic' feature.
Bump to pyenvisalink 1.6 which contains a bunch of new handled events + fixes.

Related issue (if applicable): fixes #3438
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#
Example entry for configuration.yaml (if applicable):

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If code communicates with devices, web services, or a:

[X] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[X] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[X] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Thanks- yeah I originally had ensure_future in there, but at the time I had to support all versions of Python 3.4. The goal of this library is really to be used with home-assistant, so if you're using ensure_future, I can follow suit.
I'll try your suggestion on passing the loop in too, but I am calling asyncio.set_event_loop in my constructor, and I thought that would cover it, essentially making the default loop = hass.loop.

You don't want to use set_event_loop because it means that you set the global event loop. It's better to specify the loop each time.

OK! I did a ton of research on this, and I'm pretty sure I know what's going on here.
First, let me say that I did make your recommended changes in the pyenvisalink library (I'm just now seeing your latest comment on set_event_loop- i'll just take that out entirely then).  I "borrowed" your trick from util/async.py to handle the legacy 3.4 async vs. ensure_future discrepency, plus I'm also explicitly naming the loop that I'm using in all my yields, ensure_futures,etc.  this will hopefully prevent some other issue down the line- as you mentioned.
So the issue I was experiencing yesterday was- I was attempting to be more asynchronous in my component's setup() method- I was trying to use "yield from" to allow the other components to setup while waiting on my login success callback from the device that i get asynchronously.
However- I've found that since my component's setup is being called from run_in_executor (bootstrap.py, line 302), I'm not really within a coroutine, and thus I cannot really do that, and must resort to synchronous/threading methods to wait for my callback.  I'm going to push a new change through shortly that I believe will be the simplest method of doing this.
So would it make sense to eventually make bootstrap/component_setup more async friendly? Now that i'm starting to understand this more, i would envision putting a task on the loop for each _setup_component method we need to call- does that make sense?

The plan is to eventually move as many things over to async as possible. Since it is a big undertaking, we decided to go as small as possible and make sure that is stable. After that we'll try to spread the async love.
I would however never consider making setup async, instead I would consider adding support for a new async_setup to keep backwards compatibility.

🐬  !


Bug: publishing a metric with 9 dimensions doesn't work

Expected Behaviour
Publishing a CW metric with 9 dimensions should work without problems.
Current Behaviour
When trying to publish a CW metric with 9 dimensions of my own, it seems the metrics never reach CloudWatch, although I can't see errors anywhere.
Code snippet
with single_metric(
    name="MyMetricName",
    unit=MetricUnit.Percent,
    value=percentage,
    namespace=os.environ["POWERTOOLS_METRICS_NAMESPACE"],
) as metric:
    metric.add_dimension(name="pool_id", value=metrics.uuid)
    metric.add_dimension(name="pool_name", value=metrics.name)
    metric.add_dimension(name="pool_min_size", value=metrics.min_size)
    metric.add_dimension(name="pool_curr_size", value=metrics.curr_size)
    metric.add_dimension(name="pool_real_size", value=metrics.real_curr_size)
    metric.add_dimension(name="pool_decommissioning_counter", value=metrics.decommissioning_counter)
    metric.add_dimension(name="pool_ready_counter", value=metrics.ready_counter)
    metric.add_dimension(name="pool_creating_counter", value=metrics.creating_counter)

    return metric

Possible Solution
No response
Steps to Reproduce

Try to publish a CW metric with 9 dimensions
let powertools add the service dimension on its own
no metrics are published

AWS Lambda Powertools for Python version
1.20.2
AWS Lambda function runtime
3.8
Packaging format used
PyPi
Debugging logs
####################### LAMBDA LOG ENTRY WITH LESS THAN 9 DIMENSIONS ####################
{
    "_aws": {
        "Timestamp":<PHONE_NUMBER>980,
        "CloudWatchMetrics": [
            {
                "Namespace": "phoenix-orchestration",
                "Dimensions": [
                    [
                        "service_name",
                        "pool_id",
                        "pool_name",
                        "pool_curr_size",
                        "pool_min_size",
                        "pool_real_size",
                        "service"
                    ]
                ],
                "Metrics": [
                    {
                        "Name": "SlotAvailability",
                        "Unit": "Percent"
                    }
                ]
            }
        ]
    },
    "service_name": "tenant-pool",
    "pool_id": "c481bab7-ac0c-45d2-bbcc-e5cab7f61156",
    "pool_name": "Test Pool",
    "pool_curr_size": "11",
    "pool_min_size": "11",
    "pool_real_size": "11",
    "service": "tenant-pool",
    "SlotAvailability": [
        100
    ]
}

####################### LAMBDA LOG ENTRY WITH 9 DIMENSIONS ####################
{
    "_aws": {
        "Timestamp":<PHONE_NUMBER>124,
        "CloudWatchMetrics": [
            {
                "Namespace": "phoenix-orchestration",
                "Dimensions": [
                    [
                        "pool_id",
                        "pool_name",
                        "pool_min_size",
                        "pool_curr_size",
                        "pool_real_size",
                        "pool_decommissioning_counter",
                        "pool_ready_counter",
                        "pool_creating_counter",
                        "service"
                    ]
                ],
                "Metrics": [
                    {
                        "Name": "SlotAvailability",
                        "Unit": "Percent"
                    }
                ]
            }
        ]
    },
    "pool_id": "f1316488-6aa6-464f-be78-13902b20ec33",
    "pool_name": "Prospects (Ireland) v2",
    "pool_min_size": "0",
    "pool_curr_size": "0",
    "pool_real_size": "0",
    "pool_decommissioning_counter": "0",
    "pool_ready_counter": "0",
    "pool_creating_counter": "0",
    "service": "tenant-pool",
    "SlotAvailability": [
        100
    ]
}

Hey @dnlopes thanks a lot for raising this with us.
I've got two questions before I try reproducing it tomorrow morning:

Does this only happen with 9 dimensions?
Does this happen with the latest version? We're in 1.26 now

At a first glance we're serialising correctly and CloudWatch EMF should pick it up - CloudWatch has a limit of 10 dimensions, we add "service", hence 9+service should be fine.
Thank you!

Does this only happen with 9 dimensions?

Yes. After facing this issue I simply removed one of the dimensions and everything went back to normal.

Does this happen with the latest version? We're in 1.26 now

I will bump my dependency and try again layer.
Btw, the last log record I pasted is from a wrong execution, but I think you already have everything you need to try to replicate it. I will try again with the latest version of powertools later and report back.

Great, thank you @dnlopes; this helps a lot. I gave the CloudWatch team a heads up, and will try to reproduce it tomorrow with and without powertools to rule out an issue with EMF async processor in CloudWatch Logs Engine.

Hey @dnlopes I wasn't able to reproduce it with 9 dimensions: https://github.com/heitorlessa/pt-1239
I initially suspected it was the value length of one of those dimensions but nope. I've used the exact same values as dimensions you shared.
I wonder if it's one of those common issues: console cache, wrong region, viewing wrong namespace (doubt it), etc.
Let me know if what I tried to reproduce is invalid, or if there's any other data you want us to try reproduce. There are only two small differences in the code:

No explicit namespace as Metrics utility can pick up POWERTOOLS_METRICS_NAMESPACE env variable value if set
No explicit return within the context manager (there's no need)

I noticed now that the sample code in the OP also has 8 dimensions, maybe that's the confusion here.
Rephrasing for clarity: publishing a CW metric with a total of 10 dimensions doesn't seem to work (9 custom dimensions + 1 from powertools)

Ah! Sorry I understood that 9 dimensions in total doesn't work. Let me add a dummy one, make some load, and come back with the results

Great, everything makes sense now then 😅
Thanks.

New layer for version powertools 1.26.1 released. As Heitor mentioned current layer version is 20:
arn:aws:lambda:{region}:017000801446:layer:AWSLambdaPowertoolsPython:20
The PR for the docs in on the way.


responsiveness is not apply on Bottom Sheet

Thanks for great plugin
responsiveness is not apply on Bottom Sheet

Dialogs create a different context. Therefore, you'll need to wrap your dialog contents in a ResponsiveBreakpoint for the Breakpoints to apply in a dialog.


In bind_port, there is no check for segments

In bind_port, there is no check for segments, before accessing the segments we can check whether its a valid segment based on the below method
def check_segment(self, segment):
"""Check whether segment is valid"""
return segment[api.NETWORK_TYPE] in [constants.TYPE_LOCAL,
                                     constants.TYPE_GRE,
                                     constants.TYPE_VXLAN,
                                     constants.TYPE_VLAN]

and access it like below
for segment in context.segments_to_bind:
   ** if self.check_segment(segment):**
        context.set_binding(segment[api.ID],
                            self.vif_type,
                            self.vif_details,
                            status=n_const.PORT_STATUS_ACTIVE)

line details : https://github.com/libuparayil/networking-huawei/blob/master/networking_huawei/plugins/ml2/ac/driver.py#L551

I think this check is not required for  us. Will cross check

ok


Missing the information in "About" field.

Missing the Link to "Github Pages"

not loclization issue

add it.


Identify as HTML version 5

I think it is good to have this line at (or near, after opening comments) the top of every HTML file you write. For one thing, it will validate better. For another that gets you up-to-date with where the world is now. Even though it says just html this is the tag for HTML version 5. The tags for earlier versions are a lot more complicated and you just don't need them anymore anyway.

To make the HTML validator totally happy, you could also address the warning, as my last change above does:
Warning: Consider adding a lang attribute to the html start tag to declare the language of this document.

CORRECTIONS ADDED TO MY CODE FROM PULL REQUESTS


Auto-suggest mechanism for dependencies seems to sometimes break an existing ID (likely when sync is enabled)

Please check that this issue hasn't been reported before.

[X] I searched previous Bug Reports didn't find any similar reports.

Expected Behavior
Using (unreleased) auto-suggest to add a dependency to a task with an existing ID should not change that ID.
Current behaviour
Using auto-suggest to add a dependency to a task with an existing ID has appended a few characters to the existing ID for me, several times, in my own vault.
Steps to reproduce

Paste these tasks in to a note:

- [ ] Car tax DD - from joint account #project 🆔 RFL
- [ ] Car 2024 anniversary #project

Place cursor at end of 2nd task
Type dep and accept the depends on option
Start typing car
Accept suggestion of the Car tax DD task

Expected result:
- [ ] Car tax DD - from joint account #project 🆔 RFL
- [ ] Car 2024 anniversary #project  ⛔ RFL

Actual result - note the extra L  at end of first task
- [ ] Car tax DD - from joint account #project 🆔 RFLL
- [ ] Car 2024 anniversary #project  ⛔ RFL

Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[ ] Linux
[X] macOS
[ ] Windows

Obsidian Version
1.6.0
Tasks Plugin Version
pre-7.2.0 development version
Checks

[ ] I have tried it with all other plugins disabled and the error still occurs

Possible solution
No response

I wonder if this is an Obsidian sync issue?

Probably caused by #2825...
Perhaps if the ID as added, then whilst Obsidian Sync is running, the second line is changed, sync got confused.
This is exactly the kind of situation where I tend to see sync conflicts and corrupted lines in my main vault.

I believe that I have fixed this, via the fixes to the two issues mentioned in  comment https://github.com/obsidian-tasks-group/obsidian-tasks/issues/2823#issuecomment-2134051543 above...
I'll leave it open for now, as I'm going to merge the changes to my fork, so I can test them in my main vault for a few days...

I believe that I have fixed this, via the fixes to the two issues mentioned in comment #2823 (comment) above...
I'll leave it open for now, as I'm going to merge the changes to my fork, so I can test them in my main vault for a few days...

This hasn’t happened again since I fixed those issues. Closing.


test: Add TPC-H test results

Which issue does this PR close?

Closes #.
Rationale for this change

We have already added back TPC-DS query results in #77. This adds back TPC-H query results.
What changes are included in this PR?

Adds back TPC-H query results golden files to the repo. These files were generated using CometTPCHQuerySuite with Comet turned off, to make sure it is the same as Spark's results.
How are these changes tested?

cc @sunchao @snmvaughan

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 33.32%. Comparing base (171e54c) to head (8538baf).

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #218   +/-   ##
=========================================
  Coverage     33.32%   33.32%
  Complexity      768      768
=========================================
  Files           107      107
  Lines         37037    37037
  Branches       8106     8106
=========================================
  Hits          12341    12341
  Misses        22099    22099
  Partials       2597     2597

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

Ah, yeah, they are disabled because the outputs are different to Spark. But for these output files, we should generate them. Let me add them.

Merged. Thanks.


Switch Nextcloud Redis from kubedb to bitnami

Description
This pull request removes the kubedb dependency from Nextcloud by installing Redis by replacing it with the Helm deployable version provided by Bitnami.

/merge


Unable to load  responses for a few network calls , although they log perfectly in Postman

For certain GET , POST calls  in my chrome dev tools show size content as" 0" and status  as "pending", although in my response header i can see 200 ok and content length of  few KB,
raise on SO while  back http://stackoverflow.com/questions/38867355/stetho-unable-to-show-response-for-few-call-in-chrome-dev-tools .
I also  upgraded  to okhttp 3   and stetho 1.4.2  but still plagued by same  issues.
Attaching  screenshot of one such network call selected

Hmm, it's possible that something is throwing an exception or otherwise aborting the interceptor flow during another OkHttp interceptor (or perhaps even inside okhttp itself due to something you've hooked or an upstream bug?) and that's causing us to only see the initial request going out but not the reply.  Since you can repro you're in the best possible position to get a little bit of extra debug info for us.  Could you try just attaching a debugger into StethoInterceptor#intercept and step through to see what it's doing or if it gets interrupted.
Note that the way Stetho intercepts your network traffic is not at a low level such as sockets, instead it relies on okhttp in this case to report the information and state via okhttp's own Interceptor API.  So basically whatever StethoInterceptor sees is what chrome://inspect will show.


Have "pretty" hostname info

http://man7.org/linux/man-pages/man5/machine-info.5.html#https%3A%2F%2Fwww.freedesktop.org%2Fsoftware%2Fsystemd%2Fman%2Fmachine-info.html
This might be interesting, but surely not important atm ^^.

I think setting metadata may be useful to distinguish e.g. between desktop and server configs


Idling Performance

I wanted to share some results relating to the performance of this thread pool when all member threads are idle. These results are caused by the waiting loop in threads that are idle.

Though its probably not a great idea to run 500 threads on a machine with 8 logical cores, a large number of threads can be needed for blocking i/o operations, and the idle CPU usage overhead can burden and drain the battery life of client applications.

Pool is not like to be idle, yes. Job stealing works ever when idle. I guess sleep implementation will be a bit complex and gives some addition latency when will require to wake up pool.
I've noticed this effect. But in my own case it is low, and seems bad idea to create 500 threads per pool for only 8 hardware cores ;).

@yvoinov I agree that 500 threads is excessive on a machine with 8 cores. The reason I pushed it that far was to test the limits on my machine in the context of this thread pool, and to extrapolate the results of the idling performance.
The point of this issue is that this thread pool consumes CPU even when idle. Whether or not this is a problem is completely dependent on your use case.
In my particular use case, I want extra threads lying around in my thread pool. This drives up the number of threads that may be idling at the same time. Reasons to keep some extra threads around are:

If my use cases requires blocking at higher levels, I need enough threads in my thread pool to ensure that I don't end up in a deadlock situation.
If my use case requires multiple concurrent i/o operations on the thread pool, this is another situation where I need to keep extra threads around in my pool.

Let's say we take the lowest data point on the Linux VM with 4 cores (which is 50 threads). Is 3% CPU usage an acceptable level of consumption? Some cases where this might not be ideal:

A system with other processes that contend for CPU resources.
A system that runs on battery. The CPU usage when idle will drain this.
Non-batch applications, where in general idle background tasks should minimize resource consumption.

In my case, I've started 64k threads on server (bare metal SPARC) with 8 cores and 32 Gb RAM :) All memory + swap was eaten in minutes, just with idle threads and proportional queue.
I still think it is bad idea to run more threads than physical/logical cores.
Yes, I see ~3% idle cpu usage with empty thread pool. Yes, I think this is acceptable.
No, I don't care about laptop battery because of using thread pool only on servers.
This idle consumption is continue pool benefits - I see no way to implement job stealing with sleeping workers.
If battery/laptop applications is critical for you - may be better to consider yet another thread pool implementation, without job stealing/load balancing.

@SeverTopan I think you misuse thread pool pattern. It is not supposed to handle real-time-like I/O, there exist non-blocking async API at the OS level for this. There is NO point of having more threads in thread pool then logical cores number.

@yvoinov, @inkooboo, I think you are making a lot of assumptions about what someone might want to use a thread pool for when you say there is no point in having more threads than logical cores. If all the code you are executing in the thread pool is pure computation, and never sleeps/waits/blocks (synchronization, signals, I/O, etc), then I agree with you.
Purely from the perspective of maximizing CPU utilization, there is no harm or observable overhead in having the number of threads be 2-3x the number of cores, and it can help boost utilization when the work being done is not pure computation.