Add Button icon height property (max or fixed)

Sets the Button icon height regardless of the button height, so you don't have to carefully tune the button height to get the icon size desired.
For HiDPI multi-display window dragging, it makes it easy to configure button icons that look identical but at a higher resolution when transitioning from 1X to 2X displays. This is done by importing an SVG icon and setting the scale to 2X, then using the new icon_height property, set the height to the original size, i.e. 16, which will look correct on the 1X display. If the window is dragged onto a HiDPI display, the button will then use the 32-pixel resolution.
If the button's expand_icon property is enabled, icon_height sets the maximum height of the icon if not set to 0. If expand_icon is not enabled, icon_height sets the fixed height for the icon.

This functionality is now provided by #75472


feat(healthcheck) adding visibility to target health status

Note: This is a work-in-progress.
This adds /upstreams/:upstream_id/health, an endpoint to report health of the targets of an upstream.
It returns the same contents of /upstreams/:upstream_id/targets, with the addition of a "health" field, which may return one of four values:

"healthy" - healthchecks are enabled, target is considered healthy by healthchecks, target is in use by the load balancer
"unhealthy" - healthchecks are enabled, target is considered unhealthy by healthchecks, target is in not in use by the load balancer
"not in balancer" - healthchecks are enabled, target failed to be inserted into the
load balancer (usually because of DNS resolution error), target is therefore not in use
null - healthchecks are disabled.

WIP note: Note that in the current code, if healthchecks are disabled and the target is not in the balancer, it will display as null and not as "not in balancer", which it probably should.

@Tieske I think you'll be interested in discussing this as well, especially the "not in balancer" state. Perhaps it would be desirable for us to be able to report here why exactly the (non-zero-weight) target is not in the balancer? I'm not sure if DNS errors the only possible cause for this state.

Does this response distinguish between targets that have been manually "marked healthy" or "marked unhealthy" vs. those that have been ascertained to be healthy or unhealthy by health checks? (Not suggesting that it should, at least not yet, need to think about it more - just wondering)

@coopr no, it doesn't -- as listed above, there is a single "healthy" and a single "unhealthy" state. The backend this API is exposing does not store this distinction.

If possible, I would rather have a string (i.e. "healthchecks disabled") instead of null. I think that would make it a bit easier to deal with - if a client wants to use this api it saves one conditional, and there's less risk of getting a "Null is not an object" javascript error.

Does anything special need to be in the response to indicate that it is specific to the Kong node that is reporting it? I ask because all other parts of the Admin API will respond with cluster-wide details, while in this case, the details are node-specific. Perhaps healthcheck visibility should be added to https://getkong.org/docs/0.12.x/admin-api/#information-routes instead (or in addition)?

I think @coopr's point is particularly interesting - this is one case of node-specific data endpoint (but others already exist, like / and /status for example). This could be a case of documentation, or stronger rules about how we name our endpoints (/cluster/... vs. /node/...).

@coopr @thibaultcha I thought about that as well. Now that #3234 is merged and we have a node id available, I added added the node id as a wrapping key to the response as a whole, indicating that the response pertains to that node:
{
    "a2ad0188-c249-4f3d-b62b-f3605324031c": {
        "data": [
            {
                "created_at":<PHONE_NUMBER>938,
                "health": "healthy",
                "id": "37135a85-9752-4fbb-86ac-513ea8f8335c",
                "target": "<IP_ADDRESS>:2112",
                "upstream_id": "5136b1f1-1f06-4c6f-860c-cdc629044fbb",
                "weight": 100
            }
        ],
        "total": 1
    }
}

I'm a bit torn between that (which makes it explicit that the data is "scoped" by the node) or just adding a "node_id" key alongside "data" (which would make the meaning of the UUID more evident). Opinions?

I'm still leaning towards incorporating this information into the existing node-specific endpoints that @thibaultcha mentioned https://github.com/Kong/kong/pull/3232#issuecomment-366388554

I'm still leaning towards incorporating this information into the existing node-specific endpoints that @thibaultcha mentioned #3232 (comment)

I like it better too but I am not sure if now is the time to make such paradigm shifts in the Admin API yet... I think it makes sense eventually, but that such a change is beyond the scope of this PR (or current items at work)?
My favorite (for now) would be:
{
        "node_id": "a2ad0188-c249-4f3d-b62b-f3605324031c",
        "data": [
            {
                "created_at":<PHONE_NUMBER>938,
                "health": "healthy",
                "id": "37135a85-9752-4fbb-86ac-513ea8f8335c",
                "target": "<IP_ADDRESS>:2112",
                "upstream_id": "5136b1f1-1f06-4c6f-860c-cdc629044fbb",
                "weight": 100
            }
        ],
        "total": 1
}

The logic of having the node_id as a key would be that it would be easy to consolidate data from multiple nodes, since it is all namespaced by node_id. But in hindsight that might not make sense, since if you want to integrate you would want status per target, hence a structure of target/node_id/data would make more sense, but by then the "easy integration" argument is already lost.
As an alternative to @thibaultcha's proposal we could index the data entries by target-field instead of making it an array. But that would be more lua-ish than json-ish. So I'm with @thibaultcha on this one, my 2cts.
as for endpoint;

I'm still leaning towards incorporating this information into the existing node-specific endpoints that @thibaultcha mentioned #3232 (comment)

I like it better too but I am not sure if now is the time to make such paradigm shifts in the Admin API yet... I think it makes sense eventually, but that such a change is beyond the scope of this PR (or current items at work)?

As long as we have an idea what the design looks like, now is as good a time to start as any...

Implemented the second option listed here (the one in @thibaultcha's example), with "node_id". Reshuffling the data around isn't hard if one needs to consolidate responses later.
Also, changed the nil state to "healthchecks disabled" for now, but my "WIP" comment in the PR description still stands as a to-do item.

Update: changed the behavior so that failure to resolve DNS (which causes the target to not be included in the balancer) returns "not in balancer", whether healthchecks for the upstream are on or off.

I'd like to have some opinions on how we should call the four states. Things to consider:

currenly, the "not in balancer" state is always caused by DNS failing to resolve

"unresolved"? "DNS error"?
would it be useful to include "DNS" explicitly? (however, what if other situations appear in the future that cause targets not to be added?)

these strings are going to be string-matched by other tools

should we prefer single-word results, like "unresolved", "unavailable", "unknown"?
should we do it "enum-style", like "HEALTHCHECKS_OFF" and "DNS_UNRESOLVED"? (is there any precedent for this anywhere else in the Admin API?)

when healthchecks are disabled, the balancer works as if assuming them to be always healthy. Still, I think having separate states for "healthchecker presumes healthy" and "healthchecks disabled" is important for diagnostics.

reducing the "healthchecks disabled" state to one word is complicated, because "health": "disabled" may sound like the healthchecker determined the target to be unhealthy and disabled it (likewise for "unavailable", etc.) -- the only single-word that seems unequivocal to me would be "health": "unchecked"

tl;dr:

how to call the "not in balancer" state?
how to call the "healthchecks disabled" state?

As long as we have an idea what the design looks like, now is as good a time to start as any...

@Tieske Not really - we are designing this on the go which we want to avoid for such a massive change, but more importantly we have our work and priorities already set for the next few weeks, with 2 releases that need to be completed, documented, tested and shipped - there probably isn't time to start changing this now if we want to stick to our target dates.

currenly, the "not in balancer" state is always caused by DNS failing to resolve

@hishamhm My thinking reading this: not in balancer (DNS ERROR)

should we do it "enum-style"

It does indeed look more appropriate for parsing... Maybe "not in balancer" isn't a state, but other states (such as DNS_ERROR) are documented as resulting in the Target not being included in the balancer?

HEALTHY
UNHEALTHY
HEALTHCHECKS_OFF
DNS_ERROR
... (other states which result in "not in balancer")

It'd be nice to also keep track of the error that triggerred the DNS_ERROR state, like: "error": "dns server error: 3 name error" - but if not doable without non-trivial efforts, no biggie.

but if not doable without non-trivial efforts, no biggie.

Yeah, an extra description field crossed my mind as well, but that error happens inside lua-resty-dns-client and the end-result is that it just doesn't launch the callback, which means kong.core.balancer and healthchecks don't get notified about the target at all. I extrapolate the DNS error out of the fact that the target is missing from the balancer table (that's why I was reluctant in calling it "DNS error" at first). FWIW, lua-resty-dns-client does retry by itself, meaning that if DNS is down and it  eventually resumes working, the library will issue the callback and the target will change state.
If we were to add a detailed diagnostics argument, it would be nice to also display the reason why the healthchecker switched state as well (HTTP status, timeout, etc.) but the library doesn't store that at this point, so file this under non-trivial too. :)

@hishamhm ditto: can we avoid splitting a feat's test into a separate commit? I think it is also more trouble for you to maintain this way when tweaking the patch...


system.device vs device.id vs hw.id

See https://github.com/open-telemetry/semantic-conventions/pull/1408#discussion_r1770627540 for the context

device.id is an id of a mobile device (or another device on which instrumented process is running)
hw.id is an id of a hardware component
system.device is an id of a virtual or physical component such as disk, network interface, etc

The proposal is to

merge hw.id and system.device into a new attribute that would represent physical or virtual component and can be reused in HW and system metrics
if for some reason it's not possible, the system.device should be elaborated and should include the property being described (e.g. system.device.id or system.device.name)

In here https://github.com/open-telemetry/semantic-conventions/pull/1413/files#diff-abc3e1468589797073cc2e0fcb7620efd3e94bf4c37ac3e669c7793f0ed226acR18 there's also dc.device.type, so another "duplication"

What would be the difference between system.device.id and system.device.name?

I guess it's just so we have a way to represent a "real" id and a read-friendly version of the device.

system.device is an id of a virtual or physical component such as disk, network interface, etc

regarding network interfaces there is a related discussion: https://github.com/open-telemetry/semantic-conventions/issues/308#issuecomment-2417207425


authorization requires an authentication mechanism

@dave-hillier  please review.
Fixes #5870

@dave-hillier do you think it needs to be a reminder on all the other pages as well, in case people don't even read the introduction?

I assume people can land anywhere. Not sure which other pages you mean so
I’ll take a look later.
I think a big part of my issue was that the examples on the page looked
complete, so perhaps they can be made to look more like code snippets
On Mon, 9 Apr 2018 at 20:25, Barry Dorrans<EMAIL_ADDRESS>wrote:

@dave-hillier https://github.com/dave-hillier do you think it needs to
be a reminder on all the other pages as well, in case people don't even
read the introduction?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/Docs/pull/5901#issuecomment-379865350, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB82hJJolu6c_3JpIqbGVnvileAsFYyiks5tm7W7gaJpZM4TK3d0
.

@dave-hillier  I'll monitor these doc's and see if I should an an include file to each doc saying authentication is required. thanks for pointing this out. I've never tried authz without auth.


2767: Fix cut off texts in category list

Short description

Fix cut off texts in category list. Both #2769 and #2771 did not work for me/broke some other styling. This PR should resolve all those problems with minimal changes.
Proposed changes

Remove unused thumbnail for SubCategoryListItem
Set flex-shrink: 1 on CategoryListTitle to fix wrapping

Side effects

None.
Resolved issues

Fixes: #2767.

Arg! Sorry


URL Matchers alignment issue on View API Backend page

When viewing an individual API Backend with multiple URL Matcher entries, the URL Matchers appear in a staggered row:

Task

[ ] Add markup necessary for URL Matchers to appear in a row or column.

Fixed with PR #760 (issue #472)


DateTime UTC/local issue

https://api.dart.dev/stable/3.2.3/dart-core/DateTime/toIso8601String.html
DateTime.toIso8601String output is

UTC: 2023-12-19T23:03:49.582308Z
Local time / no UTC: 2023-12-20T11:43:26.708

https://api.dart.dev/stable/3.2.3/dart-core/DateTime/parse.html
DateTime.parse doc says:

The result is always in either local time or UTC. If a time zone offset other than UTC is specified, the time is converted to the equivalent UTC time.

So my question is how it will parse a local time if no offset is specified?
* No Z indicates it's not UTC, but no offset comes with it
Thanks

Dart DateTime, like JavaScript Date, supports precisely two time zones: UTC and "local time", which is whatever the operating system says it is.
You can't specify a specific time zone other than UTC. The only way to get local time is to not specify a time zone at all, in which case it's the local time zone, whatever that is.
So if you specify no time zone at all, you get local time. The actual time zone is then supplied by the OS or browser.

I understand, but this is confusing:

An optional time-zone offset part, possibly separated from the previous by a space. The time zone is either 'z' or 'Z', or it is a signed two digit hour part and an optional two digit minute part. The sign must be either "+" or "-", and cannot be omitted. The minutes may be separated from the hours by a ':'. Examples: "Z", "-10", "+01:30", "+1130".

If DateTime.parse allows to parse any TZ datetime, why DateTime.toIso8601String does not include the current TZ offset?
An example of use case would be to have serveral servers with different TZ which store a log. If anything goes wrong and I'm not able to know what TZ uses some server, that log info would be dead.
I try to use always UTC but I see here a problem. Also local time is the default for DateTime. Isn't it?

@lrhn

Thinking of local time as having a time zone is probably not the best explanation.
Instead think of a DateTime as either being an "absolute time", a universally usable time stamp, or as a time zone unaware "calendar date plus wall clock time".
Any input with a time zone is an absolute time stamp. It's converted to UTC, instead of remembering the original time zone, but that only matters if you want to show it again. For comparisons, it's the same point in time either way.
An input without a time stamp is not a point in time. It's a calendar date and a clock time, which may mean different things when interpreted in different locations. It's a relative time.
When you convert such a relative local time to string, it doesn't add a time zone, just because that happens to be the current time zone, because that would change the meaning when it's parsed back.
Similarly, parsing an input with a time zone didn't convert that absolute time to local time, even if the time zone happens to be the same as the current local time.
They are fundamentally different ways to represent a point in time, and covering to string and praying back preserves the difference.
The time zone aware value is always represented as the UTC time

Okay, anyway I will save logs using UTC to bypass any problem.
I still think that would make sense to have the TZ inside the DateTime object, and to be possible to have/convert to any TZ. Also to print out the TZ offset. Would make it much more flexible


Undeploy jars properly after test suite termination

We should add the same undeploy logic for *CustomMarshaller*IT

@anistor couldn't Arquillian delete the jars?

I initially started cleaning up stuff that was NOT deployed using Arquillian. These obviously needed explicit cleaning. Then I continued with some Arquillian managed stuff. Seems it is not cleaned up, and not sure if it should be expected to be cleaned up by design.

Closing this. These commits are now included in https://github.com/infinispan/infinispan/pull/5604 ,  https://github.com/infinispan/infinispan/pull/5605 and https://github.com/infinispan/infinispan/pull/5623


chore(treefmt): Replace root file

.git/config won't be present when using a VCS such as jujutsu, however there will always be exactly 1 flake.nix 2 at the root of the repository so we can use it instead
(an example of this being used is also in the treefmt README in the flakes section: https://github.com/numtide/treefmt-nix?tab=readme-ov-file#flakes)

@mergify queue


FlashAttention3 support for forward pass with kv cache

After inspection, I realized that contrary to FlashAttention2 (which includes a mha_fwd_kvcache method), the current FlashAttention3 does not include forward pass with KV cache support.
I suppose that adding this would be mostly following the already existing mha_fwd_kvcache implementation from FlashAttention2. Is there any interest to add support for KV cache forward pass on FlashAttention3 ?

We have a PR for initial kv cache support and inference improvements with FA3: https://github.com/Dao-AILab/flash-attention/pull/1236


[ci/appveyor] use conda-recipe for bld/test

Changes

moved environment.yml to devtools (if still desired). I remember Rene asked to keep it.
use conda-recipe for building/testing in Appveyor.

Related Issues
Closes # (add issue numbers)
Checks

[ ] updated CHANGELOG.md
[ ] updated tests
[ ] updated doc/
[ ] update example/tutorial notebooks

Should I add an changelog entry for this?

Should I add an changelog entry for this?

Don't think so since it has no effect on the package.

It puzzles me, that the build_env.yaml is being looked up in the root directory. I thought it should always lie next to meta.yaml
Error: ENOENT: no such file or directory, open '/home/runner/work/weldx/weldx/conda.recipe/build_env.yml'

Eventually this is cached somehow?

update the recipe for new dir layout with devtools, somehow conftest.py is not beeing found..?

maybe we should remove the appveyor CI, what do you think @vhirtham ?

Thanks. Now what about Appveyor? Should it stay or should it go? :)

Thanks. Now what about Appveyor? Should it stay or should it go? :)

Not sure. In contrast to Travis it is not utterly useless to us since it doesn't have the same build time limits. As long as there is no further maintenance overhead I am fine with both (stay or go).

I guess the overhead will be low, now that we can steer everything from the conda recipe

yes should be minimal overhead now :)


Improve the Node.js install doc

Added the high-level steps for configuring ICSF. It's a prereq for node.js.
Removed out-of-date download link.
Refactored the whole topic to better organize the information.

Signed-off-by: nannanli<EMAIL_ADDRESS>
Is there a related issue for this PR?
Issue number: #1073
Developer's Certificate of Origin (DCO)

@NayerNajafi @Joe-Winchester Hi Nayer, Joe,
This PR addresses issue #1073 about adding more details about configuring ICSF which is a prereq for node.js.
I added the high-level steps in our doc and also points users to the ICSF doc for more details. Although ICSF itself is a prereq for Node, but what we do now is to pull most node related information in the Zowe doc to reduce the redirection between Zowe doc and node doc and also confusion between what node prereqs versus what Zowe actually requires (like Python, make is not required). Hope this would help clarify a lot of confusion around node install.
Would you please review this PR and let me know if any comments or suggestions? Thanks!

Looks great - thank you @nannanli and @NayerNajafi


git clone: add an optional --quiet option

This can be turned on by setting (in the .travis.yml)
git:
quiet: true
This change allows to avoid many useless lines in the logs:
remote:...
[...]
Receiving objects:...
[...]
Resolving deltas:...
[...]

This PR follow the closed travis-ci/travis-build/pull/364. the --quiet is now optional, off by default to keep existing behavior.
Any way to test this change ?

OK, a new a PR is coming. Closing.


chore: bump MIN_PEER_PROTO_VERSION to 70216

Additional Information
Extracted from dash#6272
Breaking Changes
None expected.
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas (note: N/A)
[x] I have added or updated relevant unit/integration/functional/e2e tests (note: N/A)
[x] I have made corresponding changes to the documentation (note: N/A)
[x] I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

generally LGTM, but let's add some release notes for it


add support to take backups from PostgreSQL databases

Description:
Created an ansible playbook to take backup of PostgreSQL databases and pull them to the local server
Usage:

Review and update the list of databases to backup in vars.yml
Update hosts field in pgsql_bkp.yml file to point to the ansible section that points to the PostgreSQL database host
If you want to pull the backupsto your local server, set fetch_local to true in vars.yml
ansible-playbook -u root -k ./pgsql_bkup.yml -i <ansible hosts file generated using utilities/nodes.py>

@Chaffelson : I have made the changes you have requested.

@pmereddy can you please rebase this and I'll merge it.


fix: patch for include and exclude parameters #172

emoji-search.service.ts: Pool variable was getting set with incorrect id (emojiId) ... needed to grab emoji object first to obtain the correct id, and then set the correct key (emoji.id) on pool object.
picker.component.ts: Was getting console error (undefined object) with small number of categories. This fixes it.
Closes #172

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Depreciation warnings

Oct 24 09:42:52 bhr13 python[1020799]: /opt/sram-scim-monitor/scim-server/server.py:9: DeprecationWarning: `example` has been deprecated, please use `examples` instead
Oct 24 09:42:52 bhr13 python[1020799]:   from routers import BASE_PATH, config, resource, schema, users, groups

Oct 24 09:42:52 bhr13 python[1020799]: /opt/sram-scim-monitor/scim-server/server.py:41: DeprecationWarning:
Oct 24 09:42:52 bhr13 python[1020799]:         on_event is deprecated, use lifespan event handlers instead.
Oct 24 09:42:52 bhr13 python[1020799]:         Read more about it in the
Oct 24 09:42:52 bhr13 python[1020799]:         [FastAPI docs for Lifespan Events](https://fastapi.tiangolo.com/advanced/events/).
Oct 24 09:42:52 bhr13 python[1020799]:
Oct 24 09:42:52 bhr13 python[1020799]:   @app.on_event("startup")

Oct 24 09:42:52 bhr13 python[1020799]: /opt/sram-scim-monitor/scim-server/server.py:46: DeprecationWarning:
Oct 24 09:42:52 bhr13 python[1020799]:         on_event is deprecated, use lifespan event handlers instead.
Oct 24 09:42:52 bhr13 python[1020799]:         Read more about it in the
Oct 24 09:42:52 bhr13 python[1020799]:         [FastAPI docs for Lifespan Events](https://fastapi.tiangolo.com/advanced/events/).
Oct 24 09:42:52 bhr13 python[1020799]:
Oct 24 09:42:52 bhr13 python[1020799]:   @app.on_event("shutdown")

Fixed in https://github.com/SURFscz/SCIM-server/commit/7a17e0a498002d45ccc4765cff780b8b90eb272c

confirmed


Remove unnecessary backslashes in regex to satisfy flake8.

Summary of Changes
Another small PR. Backslashes are not required within [] because most characters are interpreted as literals. Removing these backslashes satisfies more stringent flake8 style checks.
Tests
None needed, small text change.
Documentation
None needed, small text change.
CheckList
Make sure you have checked all steps below to ensure a timely review.

[X] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[X] PR includes a summary of changes.
[X] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[X] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[X] PR passes make test
[X] I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message"

Another tiny change from doing merge conflict resolution from upstream.

Codecov Report

Merging #37 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #37   +/-   ##
=======================================
  Coverage   77.66%   77.66%
=======================================
  Files          13       13
  Lines         394      394
  Branches       38       38
=======================================
  Hits          306      306
  Misses         74       74
  Partials       14       14

Impacted Files
Coverage Δ

search_service/proxy/elasticsearch.py
78.31% <100%> (ø)
: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 b14e37c...0974c79. Read the comment docs.

@worldwise001 thanks. Could you bump the minor version of the change as well?

also curious given we have flake8 running for this repo, is your local / private repo having a different or stringent flake8 rule?

I believe we have more stringent flake8 rules. I can bump the minor version of the change too.

@worldwise001 , please do. Thanks:)

I try it out which the wildcard search still works with the change. So I think it should be fine. Thanks @worldwise001 :)


Automatically check for security vulnerabilities in Gradle's dependencies

Follow-up to #2944, so we notice these problems right away.

For anyone who's looking into it:
You can try this plugin.
https://jeremylong.github.io/DependencyCheck/dependency-check-gradle/index.html

The plugin looks really helpful. Just gave a quick shot and sent a PR https://github.com/gradle/gradle/pull/3436. After merging we can probably just set up a new CI job. I believe at the moment the plugin does not have an option to automatically fail the build if at least one issue was found. Either way I think that it would be even helpful if we'd look at the report occasionally.
One or more dependencies were identified with known vulnerabilities:

native-platform-freebsd-amd64-libcpp-0.14.jar (net.rubygrapefruit:native-platform-freebsd-amd64-libcpp:0.14, cpe:/a:freebsd:freebsd:0.14) : CVE-2014-3956, CVE-2012-2143, CVE-2012-0217, CVE-2001-1029, CVE-2001-0402
native-platform-freebsd-amd64-libstdcpp-0.14.jar (cpe:/a:freebsd:freebsd:0.14, net.rubygrapefruit:native-platform-freebsd-amd64-libstdcpp:0.14) : CVE-2014-3956, CVE-2012-2143, CVE-2012-0217, CVE-2001-1029, CVE-2001-0402
native-platform-freebsd-i386-libcpp-0.14.jar (cpe:/a:freebsd:freebsd:0.14, net.rubygrapefruit:native-platform-freebsd-i386-libcpp:0.14) : CVE-2014-3956, CVE-2012-2143, CVE-2012-0217, CVE-2001-1029, CVE-2001-0402
native-platform-freebsd-i386-libstdcpp-0.14.jar (cpe:/a:freebsd:freebsd:0.14, net.rubygrapefruit:native-platform-freebsd-i386-libstdcpp:0.14) : CVE-2014-3956, CVE-2012-2143, CVE-2012-0217, CVE-2001-1029, CVE-2001-0402
maven-core-3.0.4.jar (org.apache.maven:maven-core:3.0.4, cpe:/a:apache:maven:3.0.4) : CVE-2013-0253
bcpg-jdk15on-1.58.jar (cpe:/a:openpgp:openpgp:1.58, cpe:/a:pgp:pgp:1.58, org.bouncycastle:bcpg-jdk15on:1.58, cpe:/a:pgp:openpgp:1.58) : CVE-2005-0366, CVE-2001-0381, CVE-2001-0265
groovy-all-2.4.12.jar (org.codehaus.groovy:groovy-all:2.4.12, cpe:/a:apache:groovy:2.4.12) : CVE-2016-6497

@bmuschko Would this fail the build? If so, we might need some exclusions because it looks impossible for us to get rid of groovy-all-2.4.12.jar...

@blindpirate At the moment the build does not fail for these vulnerabilities. I believe they are not considered critical enough. The plugin does have an option to failOnError or not.

impossible for us to get rid of groovy-all-2.4.12.jar

Can you bring me up to speed on why that is? Couldn't we upgrade a new patch version that potentially fixes the issue (if it is released)?

Oh, AFAIK, Groovy team are working on 3.0.0 and they don't have a plan to release 2.4.13 (perhaps).

On a different note this announcement from GitHub is going to be interesting. If vulnerabilities in our project become more visible through the UI then I am sure we'll get more pressure to fix them from the community.


Update detect GitHub username function

ghq create is very good subcommand!
When I creating a new repository with ghq create, $USER was used for GitHub username.
because of ghq.user was not set.
Currently, the user name is obtained in the following order.
1.ghq.user
2. GitHub username
3. $USER or $USERNAME
However, if one or two are not found, it seems natural to use the name set in git config user.name ${GIT_USERNAME}.
How about that?

Thanks for the suggestion.
Actually, I have thought that it might be good. However, I rejected this idea.
Because, git config user.name is generally a full name and often contains spaces and user names in ghq are like unix login names, full names are not appropriate.

Ok. I understood why use $USER, not git config user.name.
thank for reviewing.


fix: remove absolute path from http vector sink

Changes

#851  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MasterPtato and the rest of your teammates on  Graphite


Non-latin seed concept fails

Choose non-latin concept as seed concept ion settings
Reload
Tab hangs indefinitely

DOn't know if it's related but Entity Browser was the only active application.

Hi @eduard93 , can you reproduce this using the EntityAPI:GetSimilar() or EntityAPI:GetRelated() queries underneath or would this be on the result-assembly side specific to this repo (not part of the kit)? If the former, please file a prodlog if you don't mind.
Not sure how this could start consuming as many cores, as it was implemented as a single-process thing.

The error lies somewhere else. I call the methods fine from a terminal - they work.
The problem arises if I open several EntintyBrowser tabs.

I can't seem to reproduce that behaviour with the latin domains I have here. Is this in a domain that is full of non-latin concept? And were you using the UTF8 fix I suggested in the alternate branch or is this straight out of the master branch?
I'd be surprised if @ZitRos wouldn't have used this with non-latin text :-)

@bdeboe, I didn’t :)
On Thu, May 31, 2018 at 3:03 PM Benjamin De Boe<EMAIL_ADDRESS>wrote:

I can't seem to reproduce that behaviour with the latin domains I have
here. Is this in a domain that is full of non-latin concept? And were you
using the UTF8 fix I suggested in the alternate branch or is this straight
out of the master branch?
I'd be surprised if @ZitRos https://github.com/ZitRos wouldn't have
used this with non-latin text :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/intersystems-ru/iknow-entity-browser/issues/8#issuecomment-393508184,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEwhSCNHAVnGZkvLN94xyGvbFfyY5Okaks5t39v1gaJpZM4USDHJ
.

@bdeboe I have tried both with and without UTF8 fix. It fixes the problem with question marks #5  and creates the problem with icons #7. It does not affect current issue.

Found the problem.
Turns out terminal and browser go by somewhat separate roots, so browser tries to build graph of a 70 000 concepts, and terminal a hundred.
Setting pagesize to 1000 fixed my problem.


Adding workflow to automatically publish releases after a tag is pushed

Signed-off-by: Sarat Vemulapalli<EMAIL_ADDRESS>Description
Release tags are automatically published by https://github.com/opensearch-project/opensearch-build.
Github releases [1] are not published and are manually published after every release.
This workflow automates publishing github releases.
It automatically includes the release notes.
I've tested this manually on my fork:
Release: https://github.com/saratvemulapalli/OpenSearch/releases/tag/5.4.6
Workflow: https://github.com/saratvemulapalli/OpenSearch/actions/runs/2632146820
[1] https://github.com/opensearch-project/OpenSearch/releases
Check List

[x] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

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

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/277/
CommitID: 281aef1

Flaky test
Tests with failures:
 - org.opensearch.cluster.routing.allocation.decider.DiskThresholdDeciderIT.testHighWatermarkNotExceeded

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@eaab798). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #3813   +/-   ##
=======================================
  Coverage        ?   70.37%
  Complexity      ?    56558
=======================================
  Files           ?     4557
  Lines           ?   272681
  Branches        ?    40038
=======================================
  Hits            ?   191900
  Misses          ?    64555
  Partials        ?    16226

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 eaab798...281aef1. Read the comment docs.


Update tdr-metadata-validation to 0.0.33 in scala-steward-dependencies

About this PR
📦 Updates uk.gov.nationalarchives:tdr-metadata-validation from 0.0.27 to 0.0.33
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "uk.gov.nationalarchives", artifactId = "tdr-metadata-validation" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "uk.gov.nationalarchives", artifactId = "tdr-metadata-validation" }
}]

labels: library-update, early-semver-major, semver-spec-patch, commit-count:1

Superseded by #123.


Add crew endpoint

Endpoint: https://api.spacexdata.com/v3/crew
Things to decide on:

[ ] Crew schema
[x] Integration with launches

Any update on this? :slightly_smiling_face:
Proposition:
[
  {
    person: "Bob Behnken",
    organization: "NASA",
    flights: [{
      flight_number: 83,
      launch_date: "2020-01-01"/null,
      return_date: "2020-06-01"/null,
      destination: "ISS",
    }],
  }
]

It's a payload property I would think.
The specificity in terms of the stage is likely to be important here.
For Demo-2 it's likely that the NASA astronauts will arrive on Crew Dragon and then leave on the same Demo-2 Crew Dragon. But it's also likely (indeed it's the normal behaviour I think for ISS) that you leave on a different rocket.
There's not much on return-to-Earth data in a payload right now - it's just
"mass_returned_kg":905,
"mass_returned_lbs":1995

For Crew Dragon you also have both unpressurized and pressurized mass (if we get the breakdown). You need crew_sent, crew_returned. Not sure if flight_time is:

Earth -> Earth
Earth -> ISS
Stage Sep -> ISS
Stage Sep -> Earth

If it's just Stage Sep -> ISS you want to have ISS -> Earth somewhere.
Also there's no way currently to get ISS arrival date-time, ISS departure date-time, Earth arrival date-time as far as I can tell. That's also relevant for CRS missions.

Planning on getting this in place this weekend, at least an initial version.
@philipwhiuk

Planning on adding a top level crew array with the names of crew at launch. In addition, I can add a crew_returned array to the crew dragon payload, along with other crew dragon applicable info.

flight_time currently is time from liftoff to splashdown

@AlbericTrancart
Will likely use a missions array to keep track of flights like the existing setup for cores/capsules
[
  {
    "person": "Bob Behnken",
    "organization": "NASA",
    "missions": [
      {
        "name": "CRS-12",
        "flight": 45
      },
      {
        "name": "CRS-17",
        "flight": 78
      }
    ],
  }
]

Can I work on this issue?

@mighty-phoenix sure, endpoint is in place, data just needs to be collected and added to the database.

@jakewmeyer I am new to this project. Can you please tell me how I can proceed with collecting and adding the data to the database?


Change docker image names to latest

Purpose
Change docker image names to latest

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

Project coverage is 80.21%. Comparing base (839dd54) to head (8950cfa).
Report is 20 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #2225       +/-   ##
===========================================
+ Coverage   28.42%   80.21%   +51.79%
===========================================
  Files         124        9      -115
  Lines       14546      551    -13995
  Branches     2681      246     -2435
===========================================
- Hits         4135      442     -3693
+ Misses      10274      109    -10165
+ Partials      137        0      -137

Flag
Coverage Δ

adapter
?

common-controller
?

config-deployer-service
?

idp-domain-service
80.21% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


The pip version is not consistent with the documentation.

The second example in the README, in ThingsResource.on_get() (line 135), tries to set a item in the request.context dict, but running it raises the following exception:
Traceback (most recent call last):
    File "/usr/lib64/python2.7/wsgiref/handlers.py", line 85, in run
        self.result = application(self.environ, self.start_response)
    File "api.py", line 111, in falcon.api.API.__call__ (falcon/api.c:1829)
    File "api.py", line 96, in falcon.api.API.__call__ (falcon/api.c:1635)
    File "api_helpers.py", line 262, in falcon.api_helpers._wrap_with_before.do_before (falcon/api_helpers.c:3405)
    File "api_helpers.py", line 262, in falcon.api_helpers._wrap_with_before.do_before (falcon/api_helpers.c:3405)
    File "/home/ysag/Virtualenvs/glyfix/lib/python2.7/site-packages/falcon/hooks.py", line 142, in do_after_one
        responder(self, req, resp, **kwargs)
    File "things2.py", line 135, in on_get
       req.context['doc'] = result
AttributeError: 'Request' object has no attribute 'context'

I checked the source code for the Request class in falcon/request.py, and indeed, it doesn't even contain the token context.
[EDIT] Pasting the problematic code snippet:
class ThingsResource:

    def __init__(self, db):
        self.db = db
        self.logger = logging.getLogger('thingsapp.' + __name__)

    @falcon.after(serialize)
    def on_get(self, req, resp, user_id):
        marker = req.get_param('marker') or ''
        limit = req.get_param_as_int('limit') or 50

        try:
            result = self.db.get_things(marker, limit)
        except Exception as ex:
            self.logger.error(ex)

            description = ('Aliens have attacked our base! We will '
                           'be back as soon as we fight them off. '
                           'We appreciate your patience.')

            raise falcon.HTTPServiceUnavailable(
                'Service Outage',
                description,
                30)

        # An alternative way of doing DRY serialization would be to
        # create a custom class that inherits from falcon.Request. This
        # class could, for example, have an additional 'doc' property
        # that would serialize to JSON under the covers.
        req.context['doc'] = result

        resp.set_header('X-Powered-By', 'Small Furry Creatures')
        resp.status = falcon.HTTP_200

    @falcon.before(deserialize)
    def on_post(self, req, resp, user_id, doc):
        proper_thing = self.db.add_thing(doc)

        resp.status = falcon.HTTP_201
        resp.location = '/%s/things/%s' % (user_id, proper_thing['id'])

This gave me a hard time, req.context is only avaliable from version 0.2.0b1, the problem is that via pip I only get version 0.1.10

Right, sorry folks for the confusion. The docs didn't even exist until 0.2 and it isn't clear from readthedocs this is the case. I'll get this cleaned up ASAP.


[Do Not Merge] Fix #741 - Silver Prediction SQL

Fixes #741
It is a draft yet, the description will be added asap

Reviewed it, right now this code is janky and prone to errors.

Please stop using polars/sql mix, it should only be SQL
Please do not split logic into several sections, loops, etc... it should only be SQL
When in doubt, use CTE queries such that we can test and verify the logic into chunks

I propose we stop working on this and dependencies (like the streamlit work/dashboards) that rely on this, and let's get a leaner DuckDB PR merged. I'm going to update the epic so we can narrow our focus and effort further.

This code is still WIP and we'll be going back to this once we complete the duckdb integration. Closing for now.


Add TED-LIUM 3 dataset

🚀 Feature
Hi! I saw torchaudio is missing the TED-LIUM dataset from https://arxiv.org/abs/1805.04699, https://www.openslr.org/51/ which is commonly used in ASR benchmarks and I would like to propose the addition of it to the list of avaliable datasets (And propose myself to code and contribute for it! :) )
Motivation
TED-LIUM is a very common dataset in ASR benchmarking tasks and we should include it on the library.
Pitch
Add TED-LIUM 3 dataset to the list of datasets
I would like to work in a PR to introduce it if it sounds good to the main contributors :)

Sounds good to me, and you can open a PR for this! Please make sure to follow the current dataset code organization when doing so :)

Sounds good to me, and you can open a PR for this! Please make sure to follow the current dataset code organization when doing so :)

Nice! Will do :)

Closed by #882 -- please feel free to re-open if this is not the case :)


"Invalid CSS property declaration" .flip-clock-wrapper.clearfix { *zoom: 1; }

Safari and https://jigsaw.w3.org/css-validator/#validate_by_input report that
.flip-clock-wrapper.clearfix { *zoom: 1; }
is an invalid declaration.
Chrome doesn't seem to mind, however.

This has been removed in the newer versions. Closing this old thread.


Object.assign	IE Not compatible

Object.assign	IE Not compatible

Quill official statement does not support IE11 the following browser.
https://github.com/quilljs/quill/issues/936

Edge

I will hotfix this right now.

I fixed this in v2.0.2, just update your dependency and it should work :) !


More than one GX device not supportet

Hello.
I do have a configuration with more than one GX devices which I want to have in Home Assistant.
It would be great if the Integration would support multiple  instances.
Actually I need to create all modbus sensors  needed by hand.
I also have 2 Systems, a 48V and a 24V System.

+1 also have more than 1 system

any work around on this?

Hi, just my workaround:
I did create the modbus entries for the relevant values of each GX device, so I do not have such an amount of unnecessary values and I solved my problem with more devices.

I have 5 sites here at the main office and want some values at the main screen here at the ofiice

Further tracking of this feature request will be done in #162.
Please let your voice be heard over there.


Set up GitHub Actions for Test

Kindly assign me to this task

Kindly assign me to this task

Okay done!


WIndows PowerToys will not show .pdf files in Windows 11

Microsoft PowerToys version
v0.84.1
Installation method
Microsoft Store
Running as admin
None
Area(s) with issue?
File Explorer: Preview Pane
Steps to reproduce
Firstly, a while back I installed PowerToys on my Windows 10 laptop because my basic (non-Adobe extortionist program) PDFGear was not showing me previews in my preview pane. This has been working well for the most part with occational restarts.
Now on my fresh Windows 11 desktop, to duplicate, I downloaded PowerTows, selected "File Explorer add-ons", changed the Portable Document Format (.pdf) from off to on witrh no joy. A little new to Win 11, but changed folder to show the "Details pane". That was cool and does show a very small pdf file (I have no idea if it would without PowerToys because I've never seen it before). The thumbnail is too small to be useful for quickly getting info off the file without opening it and I found no way to expand to image. I have read all the online help. I found how to change from "Details" to "Preview" and the same file does not show. Just the normal statement "This file can't be previewed".
I restarted the computer. No change.
I closed PowerToys and reopened as Administrator, deselected .pdf and reselected it. No change.
I restarted the computer, opened as administrator, deselectged and reselected .pdf. No change.
Everytime changing .pdf on and off (even before opening as Admin.) all the desktop icons reset.
I noted that the PowerToys app was listed as "PowerToys (preview)", so I thought "Shit, this isn't the real program, just a preview" so I uninstalled it.
I then went to the Microsoft store at apps.microsoft.com and downloaded PowerToys from the "Install" link at the top (no mention of any preview)
When installed (now) it still says "(preview)" after the title. WTF?
I tried everything again but it will NOT preview my .pdf files!
✔ Expected Behavior
That I could preview .pdf files in my folder's preview pane so I don't have to open the application just for a quick view (like works on my Windows 10 laptop). My simple pdf program obviously not supported by windows without this fix. Why wouldn't Windows automatically preview ALL .pdf extensions?
❌ Actual Behavior
Nothing happened. PowerToys File explorer add-ons had no effect on being able to preview .pdf files.

LAST MINUTE While writing, to get the version prior to sending, I noticed an option to ALWAYS run as administrator.
I selected that and tried pdf off and on again. I noticed a pdf preview showing but selected another and no preview.
I turned the pdf option (all this from beginning in "File explorer add-ons") OFF and low & behold I now see .pdf previews!
I can only conclude that when running as admin., I never checked with the .pdf off to see the previews.
I am beginning to think that the File explorer add-ons is NOT the preview solution that PowerToys was giving me and in fact was interfering with it. OMG what a waste of time! I would like to get feedback anyway to understand what module is allowing me to view the .pdfs in the preview pane
Other Software
To handle my .pdf files, I use a free but very effective (and responsive to problems) PDFGear, v. 2.1.8

@Aaron-Junker

/dup https://github.com/microsoft/PowerToys/issues/34952

Thank you cinnamon-msft for saying I had a duplicate.
I'm looking for someone to help me.
Best,
GardenMum


6.1.5	Campaign Progress Dashboard

Placeholder for requirement around displaying campaign progress (details & sub requirements being filled asap)

@tonysurma - Has anything been fleshed out for the requirements of this one. Perhaps a wireframe and main data it would need to show?

We've got a bit but we are focusing on the P1 items in terms of requirements etc.  So.... more to come

No problem. Thanks.

@tonysurma - Another which we might be able to start tackling next week. Are there any wireframes or sketches as to the planned content?

@schuback @OhMcGoo can you take a look at how we want to document the requirements for this? cc @EmilyLuijbregts


[WIP] Add Travis CI testing.

The PR adds Travis CI testing for Dnaplotlib.
This will help in understanding the features that can break the package.

Closing the PR.


Social coding link update

Thanks @bast for reminder!
Now links to the lesson material instead of slides.
Should be merged before exercise leader onboarding tomorrow, so that EL can see the new exercise.

Sorry I did not see this PR! I really messed up and create another PR! So I guess we can close that one.

Oh. I am sorry. I was actually asking myself whether I haven't already merged a similar PR. Deja-vu. But I doubted my memory rather than double-checking.

My fault. I did not check. Next time I'll be more careful.


Logo for AGallery

Hello,
Good Day, i make a logo icon for your project.Because there is no logo in your project. If you want to use this icon in your project, then comment below, I will give you the source file. And if you want a change, then tell me I will change.

Thank you @hafizahmmed
This is my current logo. App theme is based on these colours .So if you can make a logo of this colour it will be nice.

please check this

This would be nice. Doing in photoshop? I need them in diff resolutions.

give me the size requirement for the icon.
i provided you all source file.

plzz check here https://drive.google.com/open?id=1AlUDZMtk9FiJntZvcxO5cdQiJistWlyW
anything change comment blow.

Everything looks good. If you can change the feature image

Which type you need feature image?
Like promo?

Yes thank you. this will work

when you add this in your project?

This week.
On Wed 23 May, 2018, 3:51 PM hafiz ahmmed<EMAIL_ADDRESS>wrote:

when you add this in your project?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/aakashswain001/AGallery/issues/4#issuecomment-391297706,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWXBM9wcRqR67evcJJgtx9-C7SPGYC_Cks5t1TgWgaJpZM4UAw57
.

thankyou for add my icon. Why do not you add a license to the project? I think it's necessary for your project.


Applying bundle failed

Hi!
Unfortunately, I could not apply the first bundle. I copied the csv to /etc/graylog but the error message says "Applying bundle failed". Only the third bundle is working for me.
Thanks for any help

Hi knidla,
i could reproduce you issue, it should be solved with #25 .Please remove every component and start fresh with importing content pack files. If there are any further issues feel free to reopen this issue.
Enjoy using this content pack.
Also feel free to contribute, there are still some extractors to build:-)

Hi ThoZed,
thank you very much for editing the content pack. Unfortunately, this Isssue is still the same for me, I cannot apply the content of the first pack. The second, third and fourth, I can apply. I removed all packs and even removed Dashboards and Streams, but no difference. Well, I could do a restart of the graylog-server and try again.
Best wishes, Knilda

Hi knilda,
actually i couldn't reproduce the problem. But i ran in similar problems if some parts of a content pack aren't removed before applying the content pack again.
fist remove all content packs under System/Content Packs/Firewall
Please check all components and remove them manually if they are still there...

grok_patterns:
DHCPMESSAGE

lookup_data_adapters:
Fireware msg ID to Area Lookup
Fireware msg ID to Name Lookup
Fireware msg ID to Description Lookup
Fireware msg ID to Level Lookup
countrycode 3dig to latlong

lookup_caches:
Fireware msg_ID Cache
Country Code Table

lookup_tables
Lookup Table Fireware msg ID to Description
Lookup Table Fireware msg ID to Level
Lookup Table Fireware msg ID to Area
Lookup Table Fireware msg ID to Name
Countrycode3_to_latlong

inputs
watchguard-syslog-udp

streams
Watchguard WARNING
Watchguard Mobile Security
Watchguard Proxy
Watchguard Networking
Watchguard Security Services
Watchguard DEBUG
Watchguard Cluster
Watchguard Management
Watchguard VPN
Watchguard all messages
Watchguard ERROR"
Watchguard Firewall"
Watchguard INFO

dashboards
Watchguard - presentation
Watchguard - incident
Watchguard - integrator

have fun, looking forward to hear if you could solve the issue

Hi ThoZed,
it worked! I had to delete lookup_tables first, then I could delete lookup_caches and lookup_data_adapters. I am happy for the content pack because I need it to test my R shiny App (https://github.com/knilda/shrlog) with watchguard firewall data. Your extractors are perfect to make it run. I am very happy about that! (demo is here: https://knilda.shinyapps.io/shrlog_example
Let me see if I can contribute with more extractors, when I get more into that.
Best wishes and thank you very much for your help,
knilda

Hello Knilda,
I'am glad to hear, that you could finally use the content pack. I just checked your App. It's a good approach to provide filtered data, really nice! . I look forward to see the progress on you Repo.
Maybe i could provide a howto, in which way a new extractor is added to this content pack. There are a plenty of them to build.
If you have a specific Message ID which isn't processed yet, feel free to open a new issue.
Have a nice day
ThoZed

Hello ThoZed,
thank you for your review! Nice to hear you like my App.
A howto would be nice, as I am new to building extractors.
Best wishes, Martina


Feature: Check if a Binary Tree satisfies the BST property in C++

Hey, @akgmage assign this to me.


Update all dependencies

Is there any way you could cut a new release including these changes?

Can do! I'm on vacation right now, but I'll do a new release by the end of next week.

Oh, that's awesome!  The old version of request had a ton of
vulnerabilities, so much appreciated.  Enjoy the vacation!
On Wed, Sep 26, 2018, 19:12 Tyler James Leonhardt<EMAIL_ADDRESS>wrote:

Can do! I'm on vacation right now, but I'll do a new release by the end of
next week.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tylerl0706/wgetjs/pull/1#issuecomment-424933463, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABURT0D3528mcsR9YDjbWN2V6SfyJPDpks5ufDQEgaJpZM4Sm6VN
.

This should be published now! Let me know if you have any trouble.


Add max to BatchedTensor

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (7b258f9) 100.00% compared to head (e63cfbd) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #231   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          917       919    +2
  Branches        80        80
=========================================
+ Hits           917       919    +2

Impacted Files
Coverage Δ

src/redcat/tensor.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[DOCU-2187] Add config.canary_by_header_name to canary plugin

Summary
Add documentation for new config.canary_by_header_name for canary plugin
Reason
Addresses DOCU-2187
Testing

Hey @brentos ! Can you please retarget this PR to the release/gateway-2.8 branch?


Reload all if configuration file is newer than

If an xml file is older than conf.json or its previous version, upload as part of import.

Implemented in 3.0.6


Floated button is vertically misaligned with .input-group in form if we use 14 px as default font size

I recompile bootstrap css with default font size - 14 pixels

It's changed only html styles

So I've emulated it in jsBin with overwritten html font size.
The problem that the button now has 1pix space at top. So it looks ugly and misaligned with left inputs and .input-group-addon.

jsBin https://jsbin.com/behimohuga/edit?html,css,output

Hi @jack-fdrv!
You appear to have posted a live example (https://jsbin.com/behimohuga/edit), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

W002: <head> is missing X-UA-Compatible <meta> tag that disables old IE compatibility modes

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

@jack-fdrv which browser give you this issue? Because of i can NOT confirm your issue for both FF and Chrome. For the form elements and the button the box model will look like that shown below:

The above box-model seems right for me.

Chrome (last) 47.0.2526.106 (64-bit)

Hello?

There are 300 issues and 120 PRs currently on this project...so you may not immediately get an answer/resolution to your particular problem. No need to "ping" your issue...we'll get to it ;)

Sry, ok, I've thought you need any more help =)

This is due to the computed padding changes. That button has a computed height of 33.5px and is sitting down 1px due to the rounding error.

Fix coming with improved math in #19121.

Merged #19121, so closing. Please be aware, however, that similar things can happen when you change the root font size. There's no guaranteed fix for this kind of stuff, especially across all browsers.


Does not work for NA

Hey North America Isnt working for some reason
https://gyazo.com/a2856306682919b05dc00e8542aba7bb
when i print it i get these times
[{"fajir":"17:43","duhur":"17:43","asr":"06:38","magrib":"10:05","isha":"11:48"}]]
these times are way way off

Hi @Dontmindmes, sorry for late response.
I've test it and it works properly. It seems you forgot to change the timezone and the calculation method.
Since you didn't mention in which North America you are, I will use Los Angeles as example :

Latitude: 34.0522300°
Longitude: -118.2436800°
Elevation: 96 m
Timezone: Since right now is DST, the timezone is PDT (UTC -7) instead of PST (UTC -8)
Calculation method: North America uses ISNA (Islamic Society of North America) calculation method

Now, the code should look like this (playground):
package main

import (
	"fmt"
	"time"

	"github.com/RadhiFadlillah/go-prayer"
)

func main() {
	cfg := prayer.Config{
		Latitude:             34.0522300,
		Longitude:            -118.2436800,
		Elevation:            96,
		CalculationMethod:    prayer.ISNA,
		AsrCalculationMethod: prayer.Shafii,
		PreciseToSeconds:     false,
	}

	location := time.FixedZone("PDT", -7*3600)
	date := time.Date(2019, 5, 24, 0, 0, 0, 0, location)
	times := prayer.Calculate(date, cfg)

	fmt.Println(date.Format("2006-01-02"))
	fmt.Println("Fajr    =", times.Fajr.Format("15:04"))
	fmt.Println("Sunrise =", times.Sunrise.Format("15:04"))
	fmt.Println("Zuhr    =", times.Zuhr.Format("15:04"))
	fmt.Println("Asr     =", times.Asr.Format("15:04"))
	fmt.Println("Maghrib =", times.Maghrib.Format("15:04"))
	fmt.Println("Isha    =", times.Isha.Format("15:04"))
}

Which will print this output :
2019-05-24
Fajr    = 04:25
Sunrise = 05:44
Zuhr    = 12:52
Asr     = 16:35
Maghrib = 19:56
Isha    = 21:15

Which is quite accurate if compared with MuslimPro :

The Zuhr time has two minutes difference, because AFAIK there are some difference of opinions on when azan for Zuhr should be commenced.
As we know, Zuhr time begins at the noon. However, there is hadith that forbade us to pray at the exactly middle of the day when sun is right above our head. Instead, we should wait until the sun has descended a bit to the west.
From this hadith, there are two different opinion on when azan should be announced :

The azan should be announced after the sun has descended a bit (noon + 1-2 minute).
The azan is announced right on noon when the sun is in the middle of the sky, since the prayer will be done later anyway (after iqamah).

Since my country uses the first option, I set it as default in this package. If you prefer the second options, you can easily correct the time using TimeCorrections.
For more details about Zuhr, you can check this out.

Since it seems there are no problem anymore, I will close this issue. Feels free to reopen it if needed.


Support using kubectl available on PATH

What would you like to be added:
Add support for using kubectl available on the path
Why is this needed:
It seems that the application tries to extract (not clear where from?) version of kubectl to match the cluster.
The group policy/anti-malware software installed by the company seem to prevent that, and results in a 0 byte executable.
I know for a fact that the kubectl available on the path works with all the clusters in question.
Furthermore, this machine is not able to reach out to the internet.
Environment you are Lens application on:

Kubernetes distribution: Local
Desktop OS: W10

I think we need to add an option for using bundled (local) kubectl. Now by default Lens tries to download matching kubectl version from the official download servers.

Fixed by #800


fix typo

Learn Build status updates of commit b723f6b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

landing/arm-docs/overview.md
:white_check_mark:Succeeded

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


SEM data model

Adds SEM data model, as well as more specific data models for the instruments. This PR also includes DLite plugins to parse ThermoFischer and Hitachi type images.

As a comment - the intention of this repository was to be (more or less) implementation-agnostic, i.e., all the Python files here should be moved to another, dedicated MatCHMaker DLite plugins repository.

I have discussed this with @jesper-friis. We will refactor the folders a bit to move the python scripts away from the entities, but we will keep the plugins in a folder under SEM for now. If the complexity of the repo grows, it can be split into two repos later.


Support using an alternative name for 'DocumentNode' in generated code

Is your feature request related to a problem? Please describe.
We happen to have a type in our GraphQL schema named DocumentNode. This presents a problem for us, because the generated code is invalid. It contains a duplicate definitions of this name.
The generated code is as follows:
import { TypedDocumentNode as DocumentNode } from '@graphql-typed-document-node/core';

Describe the solution you'd like
Ideally, the code generator should detect the problem, and generate a unique name.
Alternatively, provide a config option to override the name of the alias.
Describe alternatives you've considered
I've tried to patch the generator code (using something like pnpm patch). It turns out there are multiple packages involved that needs to be patched:

@graphql-codegen/typed-document-node
@graphql-codegen/visitor-plugin-common

I think this solution will work, but it's inconvenient.
Is your feature request related to a problem? Please describe.
No response

Same issue on our end in our article-cms…
Renaming the GQL-Types just to prevent the codegen-output from running into this problem, seems pretty unreasonable.
I'd argue that this is not a feature request, but rather a oversight in the codegen implementation.
@saihaj Would you agree?


Failed to import rules when 'npm_config_cache' env var is set

Version
1.0.3
YAML file where the error occurs
N/A
Command used to run
I have my project folder on my W: drive, but I also tried moving the project to my C: drive. I tried with the npx version and the locally installed version. Every variation has the same end result, described below.
npx dclint .
npx dclint .\docker-compose.outline.yaml
.\node_modules\.bin\dclint.cmd .
Optional configuration (if different from the default)
N/A
Additional context
Windows 11, Node 18.20.4
I created a Dev Drive with the drive letter W, and moved the npm cache folder to there using the following user environment variable:
npm_config_cache=W:\System\npm_cache
I suspect this configuration is causing the issue because even if I run the command from my C: drive, the error message contains the W: drive (Received protocol 'w:').
Current behavior (console output)
PS W:\Projects\proj1\docker-configuration> npx dclint .
[ERROR] Error importing rule from file: no-build-and-image-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: no-duplicate-container-names-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: no-duplicate-exported-ports-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: no-quotes-in-volumes-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: no-version-field-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: require-project-name-field-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: require-quotes-in-ports-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: service-container-name-regex-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: service-dependencies-alphabetical-order-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: service-image-require-explicit-tag-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: service-keys-order-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: service-ports-alphabetical-order-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: services-alphabetical-order-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[ERROR] Error importing rule from file: top-level-properties-order-rule.js Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}

Expected behavior
The command should lint my files.

@brnbs Hi! Could you please try latest 1.0.6 version and let me know?

Same error messages using 1.0.6:
[ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'

@brnbs I see.
Could you help me to test this situation a bit more?
Create two files (test-rule.js and dynamic-esm-import.mjs):
// test-rule.js
export default class TestRule {
    constructor() {
        console.log("Test rule loaded!");
    }
}

and
// dynamic-esm-import.mjs
import path from 'path';
import { fileURLToPath, pathToFileURL } from 'url';

const __dirname = fileURLToPath(new URL('.', import.meta.url));

async function dynamicImport(modulePath) {
    try {
        console.log(`[dynamicImport] Attempting to import from path: ${modulePath}`);
        const importedModule = await import(modulePath);
        console.log("[dynamicImport] Imported module:", importedModule);
        const instance = new importedModule.default();
    } catch (error) {
        console.error("[dynamicImport] Error in dynamic import:", error);
    }
}

async function dynamicImportAlternative(modulePath) {
    try {
        console.log(`[dynamicImportAlternative] Attempting to import from path: ${modulePath}`);
        const importedModule = await import(modulePath);
        console.log("[dynamicImportAlternative] Imported module:", importedModule);
        const instance = new importedModule.default();
    } catch (error) {
        console.error("[dynamicImportAlternative] Error in dynamic import:", error);
    }
}

dynamicImport(path.join(__dirname, './test-rule.js'));
dynamicImportAlternative(pathToFileURL(path.join(__dirname, './test-rule.js')).href);

and run them:
node dynamic-esm-import.mjs

Do you see same errors?

@brnbs Also do experience the same error if using docker image?

I got the same error:
PS W:\Projects\test> node dynamic-esm-import.mjs
[dynamicImport] Attempting to import from path: W:\Projects\test\test-rule.js
[dynamicImportAlternative] Attempting to import from path: file:///W:/Projects/test/test-rule.js
[dynamicImport] Error in dynamic import: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
(node:11208) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
[dynamicImportAlternative] Error in dynamic import: W:\Projects\test\test-rule.js:2
export default class TestRule {
^^^^^^

SyntaxError: Unexpected token 'export'
    at internalCompileFunction (node:internal/vm:76:18)
    at wrapSafe (node:internal/modules/cjs/loader:1283:20)
    at Module._compile (node:internal/modules/cjs/loader:1328:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
    at Module.load (node:internal/modules/cjs/loader:1203:32)
    at Module._load (node:internal/modules/cjs/loader:1019:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:203:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:337:24)
    at async dynamicImportAlternative (file:///W:/Projects/test/dynamic-esm-import.mjs:21:32)

I also did a test with an extra package.json file with the "type": "module" line:
PS W:\Projects\test> node dynamic-esm-import.mjs
[dynamicImport] Attempting to import from path: W:\Projects\test\test-rule.js
[dynamicImportAlternative] Attempting to import from path: file:///W:/Projects/test/test-rule.js
[dynamicImport] Error in dynamic import: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'w:'
    at new NodeError (node:internal/errors:405:5)
    at throwIfUnsupportedURLScheme (node:internal/modules/esm/load:149:11)
    at defaultLoad (node:internal/modules/esm/load:99:3)
    at ModuleLoader.load (node:internal/modules/esm/loader:417:13)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:288:22)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at #createModuleJob (node:internal/modules/esm/loader:312:17)
    at ModuleLoader.getJobFromResolveResult (node:internal/modules/esm/loader:265:34)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:251:17)
    at async ModuleLoader.import (node:internal/modules/esm/loader:336:23) {
  code: 'ERR_UNSUPPORTED_ESM_URL_SCHEME'
}
[dynamicImportAlternative] Imported module: [Module: null prototype] { default: [class TestRule] }
Test rule loaded!

The docker run -t --rm -v ${PWD}:/app zavoloklom/dclint . command works fine in the same W:/Projects/test directory on 2 yml files.

@brnbs Hi! I still could not reproduce it my local machine, so could you please try this version before I publish it?https://www.npmjs.com/package/dclint/v/1.0.8-beta.1

@brnbs Hi! I have completely changed building process and files handling, so I think v2 would not have this bug.
Let me know if something wrong anyway.


Extension issue

Issue Type: Bug
Extension Name: LiveServer
Extension Version: 5.6.1
OS Version: Windows_NT x64 6.1.7601
VS Code version: 1.56.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Nothing


Unignore test on code import from notebooks

ignored in https://github.com/neuromation/cookiecutter-neuro-project/pull/195

already fixed


remove unused packages/files

Signed-off-by: Rachel Kurchin<EMAIL_ADDRESS>

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@41aecae). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 40c1164 differs from pull request most recent head deb7f1f. Consider uploading reports for the commit deb7f1f to get more accurate results

@@            Coverage Diff            @@
##             master      #32   +/-   ##
=========================================
  Coverage          ?   43.07%
=========================================
  Files             ?        7
  Lines             ?      260
  Branches          ?        0
=========================================
  Hits              ?      112
  Misses            ?      148
  Partials          ?        0

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 41aecae...deb7f1f. Read the comment docs.

Should also remove PackageCompiler from the deps, but this should help make the package lighter for sure!


Zoom coefficient option

With $().cropper('zoom', num) the user can choose the zoom ratio that want, but when scrolling the zoom ratio is 0.1.
Required in #251
I added:

a option zoomRatio to specific the zoom ratio (default is 0.1);
a method to set zoomRatio and another to get it (setZoomRatio and getZoomRatio);

examples
$().cropper({
    zoomRatio: 0.03 //default is 0.1
});
$().cropper('setZoomRatio', 0.15);
$().cropper('getZoomRatio'); //return zoomRatio value
$().cropper('zoom', +1 * $().cropper('getZoomRatio')); //zoom in
$().cropper('zoom', -1 * $().cropper('getZoomRatio')); //zoom out

I think setZoomRatio and setZoomRatio are unnecessary features. and I have added wheelZoomRatio option in v0.11.0. Thank you!


Could you clarify on the licensing of models and code

Hi @xk-huang excellent work and can't thank enough , what is the stance of licensing of models and code here , need clarity here

Hi @papasanimohansrinivas, Thanks for pointing out the missing license!
The code and our trainable weights (i.e., the text query mixer), are udner The model is licensed under the Apache 2.0 license. I would add the license ASAP.
Free free to reach out if you have any more questions.


Investigate slow running unit test packages

I see the following packages taking more than seconds to run. Unit tests should take less than a second, a couple of seconds at most.
✓  cli/azd/pkg/exec (5.867s)
✓  cli/azd/pkg/graphsdk (11.307s)
✓  cli/azd/pkg/azsdk (23.481s)

Investigate why these packages are slow (likely due to retry policy), and fix.

Slowest:
$ gotestsum tool slowest --jsonfile json.log         github.com/azure/azure-dev/cli/azd/pkg/azsdk TestZipDeploy 24.81s
github.com/azure/azure-dev/cli/azd/pkg/azsdk TestZipDeploy/WithPollingError 24.56s
github.com/azure/azure-dev/cli/azd/test/functional Test_CLI_RestoreAll_UsingFlags 16.1s
github.com/azure/azure-dev/cli/azd/test/functional Test_CLI_RestoreAll_InProjectDir 16.059s
github.com/azure/azure-dev/cli/azd/pkg/graphsdk Test_GraphClientRequest_With_Preflight_Error 10.34s
github.com/azure/azure-dev/cli/azd/pkg/exec TestKillCommand 5.01s

After changes in #2276:
gotestsum tool slowest --jsonfile json.log
github.com/azure/azure-dev/cli/azd/test/functional Test_CLI_RestoreAll_UsingFlags 14.37s
github.com/azure/azure-dev/cli/azd/test/functional Test_CLI_RestoreAll_InProjectDir 14.36s
github.com/azure/azure-dev/cli/azd/test/functional Test_CLI_ProjectIsNeeded 5.48s
github.com/azure/azure-dev/cli/azd/test/functional Test_CLI_Init_CanUseTemplate 1.49s
github.com/azure/azure-dev/cli/azd/test/functional Test_CLI_Restore_UsingServiceName 1.35s


Update SpecVersion to stop returning InternalError for nil errors

add check for nil error in function SpecVersion, instead of returning a wrapped error every time.

Would you mind updating the test to use 0.7.0, so that it passes on testnet? Thanks

Would you mind updating the test to use 0.7.0, so that it passes on testnet? Thanks

Done, sorry I missed this 😬

Nice!


[MongoDB] Error: Authentication failed

I do have problems with the vscode extension connecting to a locally running mongodb server.
The connection-string is of the type:
mongodb://myrootuser:mypassword@<IP_ADDRESS>:27017
Everything works with the 0.8.0 release and prior, but beginning with 0.9.0 and later I was not able to use the extension with my mongodb instance.
Working state (i.e. with 0.8.0):

Non-working state (i.e. with 0.10.0):

The "OUTPUT" tab of the Mongo Language Server says:
Debugger listening on ws://<IP_ADDRESS>:6005/92e3661d-9f2b-49b9-bb16-36257074eca9
For help, see: https://nodejs.org/en/docs/inspector
[Error - 1:59:45 PM] (node:16492) UnhandledPromiseRejectionWarning: MongoError: Authentication failed.
    at Function.MongoError.create (/home/mlanger/.vscode/extensions/ms-azuretools.vscode-cosmosdb-0.10.0/dist/node_modules/mongodb-core/lib/error.js:31:11)
    at /home/mlanger/.vscode/extensions/ms-azuretools.vscode-cosmosdb-0.10.0/dist/node_modules/mongodb-core/lib/connection/pool.js:497:72
    at authenticateStragglers (/home/mlanger/.vscode/extensions/ms-azuretools.vscode-cosmosdb-0.10.0/dist/node_modules/mongodb-core/lib/connection/pool.js:443:16)
    at Connection.Pool.socketCount [as messageHandler] (/home/mlanger/.vscode/extensions/ms-azuretools.vscode-cosmosdb-0.10.0/dist/node_modules/mongodb-core/lib/connection/pool.js:477:5)
    at Socket.dataHandler (/home/mlanger/.vscode/extensions/ms-azuretools.vscode-cosmosdb-0.10.0/dist/node_modules/mongodb-core/lib/connection/connection.js:333:22)
    at Socket.emit (events.js:182:13)
    at addChunk (_stream_readable.js:279:12)
    at readableAddChunk (_stream_readable.js:264:11)
    at Socket.Readable.push (_stream_readable.js:219:10)
    at TCP.onread (net.js:636:20)
[Error - 1:59:45 PM] (node:16492) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
[Error - 1:59:45 PM] (node:16492) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Please let me know If you need any further information!

Hi @mmlanger ,
I tried repro'ing the issue - it looks like the issue reproduces even in 0.8.0. Stepping through the code, the auth failure is coming from Mongo itself. Looking around, it looks like this could be a root cause:
https://jira.mongodb.org/browse/SERVER-17459

getting the same error with 0.10.1. Any update?

I figure it could be down to the version of the mongodb package shipped. 0.8.0 has an older version of mongodb (2.2.25) where this works, while the newer version (2.2.36) is throwing me an authentication failed error. We have made changes to how we handle connection strings, but my repro (with debugging) didn't show me any difference for this case. I'll look at it again, and let you know of any workaround.

Our MongoDB version is 3.2.13

Mine is MongoDB server version: 4.0.6.

Hi, I've tried reproducing this again, but to no avail.
Mongo v3.4, Os Windows 10, extension at commit 351180b1e8016853e82306d1b7d3083fe333e123
Here's what I did:

Create an admin user, with a password.
Stop and restart mongod for the above change to take effect
Run mongo then connect("mongodb://admin:password@<IP_ADDRESS>:27017") . I can see collections in the shell
Detach local <IP_ADDRESS>:27017 from the extension, and attach mongodb://admin:password@<IP_ADDRESS>:27017 . I can see the database and accounts.

Is there something w.r.t role based or collection based access I need to be aware of?


Arrow functions break scope context in mocha testing

For example:
describe('my webdriverio tests', () =>  {
  this.timeout(99999999);

Breaks.

Yep, arrow functions "inherit" the this and arguments of their containing function. This is documented on the Babel docs and even includes a mention in the FAQ. Just use a normal function.


Change reset value of SPI follower miso to 1

From Julie:
Re-run the basic spi test (The longer test that includes all the SPI function). It passed.
Look at the wave:

Before rst_n release, miso is 1.
After rst_n, miso is drive by the buffer data.
Whence ss_n go low, the real value of miso will be sent to master.


Wrong shm default size

shm is configured to have a default size of 256Mi.
The setup will fail saying:
/dev/shm must be at least 2GB in size

Hello @mvtab!
I completely missed this check, probably because I use host shm. I'll raise the default to 2Gi right away!

Thank you!


TypeError: Cannot read properties of undefined (reading 'playlistSidebarRenderer')

I'm seeing an increase of errors on one of my websites, JWA.
When the program starts, it automatically tries to fetch around 30 YouTube playlists for the artists displayed on the site. Ever since the new YouTube redesign, 50% of the requests began to fail with the following error:
TypeError: Cannot read properties of undefined (reading 'playlistSidebarRenderer')
    at parsePlaylist (/home/runner/Jam-with-all/node_modules/@fabricio-191/youtube/lib/methods/playlist.js:44:19)
    at getPlaylist (/home/runner/Jam-with-all/node_modules/@fabricio-191/youtube/lib/methods/playlist.js:35:9)
    at runMicrotasks (<anonymous>)

Any help here?

Yeah, the data changed since the update, solved it on version 0.0.4, update and tell me if it reapears


Blocked from moving onto the next exercise. (Matrix to Linked List)

Hi, I got done with Matrix a bit ago and I seem unable to move onto Linked List. I'm not sure why it will not unlock for me. I'm guessing this may have to deal with the move from Ecmascript to Javascript, but I don't know.

Let me know if there any more details I can share to help with this issue.
Thanks!

I guess you are right in that this may be a migration issue. Because the config says linked list is core exercise and is not unlocked by something else. Let me check with the core members and get back to you. Sorry for the inconvenience.

I've had the same issue: https://github.com/exercism/exercism/issues/4289.

@amscotti Is this fixed for you now?

@iHiD Yup! Thanks for the help, I can now work on Linked List. :) 🎉

Enjoy! :)