Chore: Add Docker Support

Created Dockerfile using chainguard/wolfi-base as base image. This image is security focused and out of the box runs on non-root user and has fewer dependencies reducing the attack surface.
Improved also the docker-compose.yml by adding pgadmin a PostgreSQL web UI to help the database visualisation during development.

Any specific reason you're adding the binary from the local machine to the docker image? Don't you prefer running a multi-stage build, compiling the app and adding that to the later stage? We would need to install stuffbin in the docker container but perhaps that would make it more "contained".
I can do it. I'll pull this branch and make the necessary changes if you agree.

@Jalmeida1994 remember that the build of the artifact is handle by the gorelease plugin.
Or I'm seeing this wrong?

Ahh of course! Completely forgot about it! I need to check up on goreleaser more!

You can squash and merge if you want!


use imd-v3-integration as ref for LAMMPS fork

Fixes #39
Changes made in this Pull Request:

clone modified IMDv3 LAMMPS source from ljwoods2/lammps:imd-v3-integration

PR Checklist

[ ] Tests?
[ ] Docs?
[ ] CHANGELOG updated?
[x] Issue raised/referenced?

Fixed the LAMMPS integration workflow.

Will steal this change for the "docker" branch where I am rewriting the tests using docker instead of building in the CI


SIGUSR2 kills waybar

Sending SIGUSR2 instead of reloading it, kills it.
Waybar v0.9.3
ubuntu 20.04

I was also confused by this. I assumed I misunderstood the docs, so to "reload" the config I just kill it and manually start it again now.

Hey.
SIGUSR2 is not even in the latest release version 0.9.5. it just kills the program.
It does have SIGUSR1 too toggle the bar.
@Alexays has to release a new version.
If you compile from the master branch it works perfectly.

Ah, I see. Maybe the wiki docs should clarify what features aren't released yet, to avoid confusion with users.

Yeah that the issue with the Github wiki...
We can probably specify the version in which the functionality has been implemented.


Route53: creating a health check with type of CALCULATED fails

When trying to create a CALCULATED health check for aggregating health check alarms, the response from the moto library fails to parse. However when executing the same request to an AWS account it succeeds with the creation.
Versions:

Python @ 3.8
Moto @ 2.0.2
Botocore @ 1.20.30

Example test code:
@mock_route53
def test_create_calculated_health_check(self):
    client = boto3.client('route53')

    response = client.create_health_check(
        CallerReference='test-route53-health-HealthCheck-ZHV123',
        HealthCheckConfig={
            'Type':             'CALCULATED',
            'Inverted':         False,
            'Disabled':         False,
            'HealthThreshold':  1,
            'ChildHealthChecks': [
                '96f93979-70e9-4d55-b299-fab4db2931e6'
            ]
        },
    )

    self.assertIsNotNone(response)

Stacktrace:
======================================================================
ERROR: test_create_calculated_health_check (__main__.HealthChecksTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/moto/core/models.py", line 106, in wrapper
    result = func(*args, **kwargs)
  File "test_health_checks.py", line 43, in test_create_calculated_health_check
    response = client.create_health_check(
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/client.py", line 662, in _make_api_call
    http, parsed_response = self._make_request(
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/client.py", line 682, in _make_request
    return self._endpoint.make_request(operation_model, request_dict)
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/endpoint.py", line 102, in make_request
    return self._send_request(request_dict, operation_model)
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/endpoint.py", line 134, in _send_request
    success_response, exception = self._get_response(
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/endpoint.py", line 166, in _get_response
    success_response, exception = self._do_get_response(
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/endpoint.py", line 217, in _do_get_response
    parsed_response = parser.parse(
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 245, in parse
    parsed = self._do_parse(response, shape)
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 809, in _do_parse
    self._add_modeled_parse(response, shape, final_parsed)
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 818, in _add_modeled_parse
    self._parse_payload(response, shape, member_shapes, final_parsed)
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 859, in _parse_payload
    body_parsed = self._parse_shape(shape, original_parsed)
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 312, in _parse_shape
    return handler(shape, node)
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 388, in _handle_structure
    parsed[member_name] = self._parse_shape(
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 312, in _parse_shape
    return handler(shape, node)
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 388, in _handle_structure
    parsed[member_name] = self._parse_shape(
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 312, in _parse_shape
    return handler(shape, node)
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 388, in _handle_structure
    parsed[member_name] = self._parse_shape(
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 312, in _parse_shape
    return handler(shape, node)
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 174, in _get_text_content
    return func(self, shape, text)
  File "/Users/craignewton/insided/ops-10/insided/community-setup/venv/lib/python3.8/site-packages/botocore/parsers.py", line 486, in _handle_integer
    return int(text)
ValueError: invalid literal for int() with base 10: 'None'

Looks like there are two issues (at least..) with the calculated health-check:

It returns IPAddress and Port in the response, when it shouldn't
It has port as 'None', with throws the above error.

Are you able to share an example response for the test case you provided, @newtondev? Just want to make sure I haven't missed anything else

@bblommers thanks for picking this up. The only other issue I had was with the CallerReference as mentioned in this ticket: https://github.com/spulec/moto/issues/3786


How to make patches for more shaders？

The current version is great for seus renewed and many shaders, but it failed to compile kappa, seus ptgi, continuum shaders, how to personally make patches for them?

This mod now automatically patches the shaders. The version 0.2.0 already supports the shader you mentioned.


Enabling eval in param scope

Enabling eval usage in param scope by default. Removed the duplicate
symbols from body scope. Also removed the work around used for special
symbols like this, super etc.

@pleath Can you please take a look?


Add an API Proxy to a Product

Tutorials: https://developers.sap.com/tutorials/hcp-apim-create-product.html
Step 7: Click Publish
I'm using my trial account to follow this tutorial.
I have created Product and tried to publish it. Then I got the following message.

Is trial version not supported for publishing Products?

Hello,
You have not enabled API Business Hub Enterprise, please enable it and try again
Please check Step 4, Provision Capabilities

Hello @kulkarnir
Thanks for your reply.
I have enabled API Business Hub and now able to access it.


[WIP] Rs/claim tail violations

claim fixes from https://github.com/ramensen/riak_core (WIP more PR's in the works)

oops


ArgumentEntity suggestions bug

ArgumentEntity does not suggest selectors. This is because minecraft:entity parser only returns entities but not selectors.

Selectors are only visible starting a certain permission level, the demo server uses 4

Oh okay. My bad.


[SQL] Add az sql mi op list, az sql mi op get to display operation steps and operation parameters

Description

Add az sql mi op list, az sql mi op get to display operation steps and operation parameters
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

add to S174

Hi @toki95 , could you take a look at failed tests?

Hi @toki95 , could you take a look at failed tests?

These tests don't correlate to my change, I've informed the owning team of these failures.

@Juliehzl friendly ping :)

@toki95 I thought the failed tests are test_sql_managed_db_short_retention, test_sql_managed_deleted_db_restore, test_sql_managed_db_mgmt and test_sql_managed_db_long_term_retention  which are related with SQL.

Yes, but not with this change. I have informed the team. We can merge this.

@MyronFanQiu ping :)

/azp run

@toki95 Hi. Since you change the sdk's verison and the api-version is also changed. You have to re-run the failed tests lively. These four failed tests should be caused your change.

/azp run

@MyronFanQiu tests fixed, please merge.

Approved. @Juliehzl I'm not code owner. Please help merge this pr.

Hi @toki95, it seems you just replace the api version. Could we run all test in live mode for sql service to prevent there is breaking change for sql related command with new sdk version?

New PR https://github.com/Azure/azure-cli/pull/14728.
Old closed due to branch issues.


how to match the request.url with react-router on server side

how to match router on server side using react-router v4 #SSR

@xwillmadeit I'm doing for it, please wait. It will be released soon.


what distinguish between address,random (short) address and current (short) address in library file

in the library file,it defined many address arrays why should it has random address ?isn't  one determined address is enough for one DWM1000 device?
who can help me.
thanks  a lot.

Can you please write an example? I can't understand what you are referring
to.
On Fri, Jul 20, 2018, 5:40 AM xingshanxi<EMAIL_ADDRESS>wrote:

in the library file,it defined many address arrays why should it has
random address ?isn't one determined address is enough for one DWM1000
device?
who can help me.
thanks a lot.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/thotro/arduino-dw1000/issues/278, or mute the thread
https://github.com/notifications/unsubscribe-auth/AWi_NioMbJ-IRoFcPBw5vgAKIo5QEbi9ks5uIVEggaJpZM4VXaIf
.

thanks your reply.I am a  green hand ,some functions and parameters of the library puzzles me .


Rust, cargo: :cc does not work for errors.

:cc does not work after finding an error on file save with Rust projects
Expected behavior
:cc should jump to the line with an error
Steps to reproduce
Compile Rust project with error, :cc, cursor doesn't jump.
I'm using neomake on every save.
The problem was introduced recently during changes related to using cargo check. I reported it here: https://github.com/neomake/neomake/issues/843#issuecomment-292766946 , and after the feature got completed, it seems still there.
@jonhoo reported same problem. Can you please confirm if it's gone for you?

This is because neomake has now moved to using vim location-list instead of quickfix. Thus, you need to use the commands :lnext, :lprev, :lopen, and :lclose.

Oh, that's what it meant.
Seems like adding:
cnoreabbrev cn lnext
cnoreabbrev cp lprev
cnoreabbrev cc lopen<CR>

fixed my issue.

Well, quickfix and location lists are different, and you should not mask one by the other.
Check out https://github.com/tpope/vim-unimpaired/, which provides a set of useful mappings, also for navigating qf/location lists.


Update notification templates

Documentation is in the wiki
https://dsdmoj.atlassian.net/wiki/spaces/LIC/pages/1393918299/Notifications
and in the Notify service
https://www.notifications.service.gov.uk/services/04decd8b-eef3-40c5-8157-0459fd2ebf8e


Support collection Initializer with D2Shapes

Adding the support Collection Initializers to D2Shape so that it is more similar to the actual D2 format and is more convenient to write.
For example, instead of:
var company = new D2Shape("google", null, Shape.Rectangle);

company.Add(new D2Shape("gmail", "Gmail", Shape.Rectangle));
company.Add(new D2Shape("meet", "Meet", Shape.Rectangle));
company.Add(new D2Shape("deepmind", "DeepMind", Shape.Rectangle));

We can now do
var company = new D2Shape("google", "Google", Shape.Rectangle)
{
    new D2Shape("gmail", "Gmail", Shape.Rectangle),
    new D2Shape("meet", "Meet", Shape.Rectangle),
    new D2Shape("deepmind", "DeepMind", Shape.Rectangle),
};

Nice! Thanks for you contribution 👍


Use rotating log files

This resolves #598

 You should sign our Contributor License Agreement in order to get your pull request merged.

Thanks @jacobhands! Now I can feel confident recommending that people enable this in production environments over long periods of time :+1:


Add optional remediation field to changeset

Add optional metadata fields that can be populated by Codemodder when remediating findings from external tools.
This is currently unused by upstream tools but it may be useful to capture this metadata and could be useful going forward.

Will revisit as part of #17 .


Develop | Frontend | Index, Catalog and other pages with mocks

Added mocks server as next.js;
Added react-hook-form, qs and other libs & packages;
Added carousel, fake data generation and other features.

incorrect merge request


refactor: use write object interface name

What's changed and what's your intention?
use WriteObject instead of Create
Checklist

[x]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

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

Project coverage is 77.63%. Comparing base (2da0829) to head (805e289).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #24   +/-   ##
=======================================
  Coverage   77.63%   77.63%
=======================================
  Files           8        8
  Lines         456      456
=======================================
  Hits          354      354
  Misses         78       78
  Partials       24       24

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


Lock Cache before downloading Dart SDK on Windows

fixes #7921

This is some dark magic right there.


Update to version 2.0.0

Now uses a subclass of UIViewController to configure keyboard support options.

Any thoughts on the above @earlgaspardBottleRocket?

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c115e2e). Click here to learn what that means.
The diff coverage is 54.3%.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   54.54%
=========================================
  Files             ?        8
  Lines             ?      253
  Branches          ?        6
=========================================
  Hits              ?      138
  Misses            ?      115
  Partials          ?        0

Impacted Files
Coverage Δ

Example/KeyboardSupport/ViewControllerC.swift
0% <0%> (ø)

Example/KeyboardSupport/ViewControllerB.swift
0% <0%> (ø)

...ple/Tests/KeyboardSupportViewControllerTests.swift
100% <100%> (ø)

...mple/Tests/KeyboardSupportConfigurationTests.swift
100% <100%> (ø)

...upport/Classes/KeyboardSupportViewController.swift
34.74% <34.74%> (ø)

Example/KeyboardSupport/ViewControllerA.swift
69.23% <57.14%> (ø)

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 c115e2e...4d0ba3b. Read the comment docs.


Roman/pred 1395

Coverage decreased (-0.8%) to 82.472% when pulling 370df44f8ccf0fad3bfd945a1436795d92071d1e on roman/PRED-1395 into 013677f16bdcd43a67730bb981d746bf285029b1 on master.

Coverage increased (+0.2%) to 83.5% when pulling 5a5a374827f4da12b621d854420874a2a5c06155 on roman/PRED-1395 into 013677f16bdcd43a67730bb981d746bf285029b1 on master.

Coverage increased (+0.2%) to 83.5% when pulling 5a5a374827f4da12b621d854420874a2a5c06155 on roman/PRED-1395 into 013677f16bdcd43a67730bb981d746bf285029b1 on master.

Coverage increased (+0.2%) to 83.444% when pulling f6f88a223f890b741266163046b51e25d2aa0e62 on roman/PRED-1395 into 013677f16bdcd43a67730bb981d746bf285029b1 on master.

Coverage increased (+0.2%) to 83.444% when pulling f6f88a223f890b741266163046b51e25d2aa0e62 on roman/PRED-1395 into 013677f16bdcd43a67730bb981d746bf285029b1 on master.

Coverage increased (+0.2%) to 83.444% when pulling f6f88a223f890b741266163046b51e25d2aa0e62 on roman/PRED-1395 into 013677f16bdcd43a67730bb981d746bf285029b1 on master.

Coverage increased (+0.2%) to 83.5% when pulling 02400387dd52faabd72e992bdeff3d1177ff2cb7 on roman/PRED-1395 into 013677f16bdcd43a67730bb981d746bf285029b1 on master.

Coverage increased (+0.2%) to 83.491% when pulling e6812ad42255342deb31d23835934e6d536fa48c on roman/PRED-1395 into 013677f16bdcd43a67730bb981d746bf285029b1 on master.

Coverage increased (+0.2%) to 83.491% when pulling e6812ad42255342deb31d23835934e6d536fa48c on roman/PRED-1395 into 013677f16bdcd43a67730bb981d746bf285029b1 on master.

Coverage increased (+0.2%) to 83.491% when pulling e6812ad42255342deb31d23835934e6d536fa48c on roman/PRED-1395 into 013677f16bdcd43a67730bb981d746bf285029b1 on master.

Coverage increased (+0.2%) to 83.435% when pulling b237247f835e240c7b316d3f71da5be0b88c19e4 on roman/PRED-1395 into 013677f16bdcd43a67730bb981d746bf285029b1 on master.


Add support for build-tool-depends

http://cabal.readthedocs.io/en/latest/developing-packages.html?highlight=build-tool-depends#pkg-field-build-tool-depends
I found myself wanting this here, but because hpack doesn't support build-tool-depends, I have to add it to the generated .cabal file post facto.

@mitchellwrosen I'm sorry for that.  hpack-0.24.0 introduces verbatim as a Cabal escape hatch (check the relevant section in the README).  This can be used as a workaround for now like so:
tests:
  spec:
    main: Spec.hs
    verbatim:
      build-tool-depends:
        hspec-discover:hspec-discover == 2.*
    source-dirs: test
    dependencies:
      - hspec == 2.*

However, this will not guarantee that hspec-discover and hspec are of the same version + I'm not sure how you would guarantee that without requiring exact version on both hpack and hspec-discover:hspec-discover.

Or better yet:
tests:
  spec:
    defaults: sol/hpack-defaults@hspec-cabal-new

Or if you want reproducibility (which never hurts!):
tests:
  spec:
    defaults: sol/hpack-defaults@e2f7990163fdbcfa884a9e3202664122f9f6cd24

Sorry, no tag for now..

I'm a bit confused about the rational behind not adding build-tool-depends to hpack. Let's not have some sort of contentious hard-fork from Cabal-the-file-format if we can help it ;)

@mitchellwrosen I'm sorry if I gave the impression that we won't add support for build-tool-depends.  If adding build-tool-depends would solve the problem than I would be more than happy to do so.  But first I want to have the full picture!
Open questions:

How to guarantee consistent versions between a library and an associated build tool
What about compatibility with older versions of cabal? Should build-tool-depends imply cabal-version: >= 2?
Backward compatible .cabal fies require a careful combination of build-tool-depends and build-tools, do we want to solve this in Hpack or leave it to the user?

Blocked on https://github.com/haskell/cabal/issues/5105

https://github.com/sol/hpack/pull/316 is my proposal to address this.  I'm hoping for at least one thorough review before merging that change. Any help with that is much appreciated.


Add new select component for  scene - #210

Description of changes
Implements new select component for #210 using the react-select library.  On the Code School page 'Schools By State' section at the bottom, users can:

Display the state options by clicking the down caret in the Select component (like a traditional HTML select element)
Type in the state names in the Select component.  This filters the state options displayed, based on the search query

When state options are displayed:

Arrow keys + enter can be used to navigate the list and select a state
Mouse pointer clicks can also be used to select a state
Multiple states can be added to a selection
Individual states can be cleared from the selection
All states can be cleared at once from the selection

School cards are displayed on the screen below the Select component, based on which states are selected.  When multiple states are selected, the school cards are sorted alphabetically by state.
Issue Resolved
Closes #210
Notes
The Select component will now be available for use on other pages via import Select from 'react-select';
To import the global CSS styles for the Select component from the react-select dependency, I created src/shared/styles/react-select.global.css (similar to what we are already doing for react-table and normalize.css).  But, unlike with those files, I used the CSS @import syntax within react-select.global.css to import the CSS styles from the dependency's styles in the node_modules directory.  We may want to adopt a similar pattern for react-table or normalize, instead of hardcoding in those CSS styles into our app.

Everything looks really great, on all mobile browsers for iOS, the client zoomed in when the Select2 component was selected. Does this occur on Android as well? I'm willing to approve this PR anyways, but I believe that would be the only improvement I can think of.

@kylemh Good call to check how the mobile UI looks - I totally forgot about that. Checked it on Chrome for Android, didn't experience any zooming, worked pretty much same as desktop Chrome.  We can always open another mobile-only issue to fix that though, if we want to progress incrementally.

That SO thread is the exact user story I experienced for clear reference - definitely follow that.

Since you're going back in there, there are 2 minor style changes I would implement:

Separate the clear button a little farther from the down-arrow icon, and make it larger.
Make the entire component around 15% larger - text and all.

@kylemh Added some fixes in response to code review:

added fix to prevent zoom for iOS (tested on Safari, but not iOS Chrome)
added some overrides for to global react-select CSS to increase height/line-height/font-sizes where possible
set the width of the Select (within the StateSortedSchools component) to full-width of the section, but with a max-width

We can probably tweak these styles more later when we add some app-wide styles for Form Components.


CI/CD - Support DirectX test pipeline

Description
Support DirectX test pipeline.

can you fix the unit test first?

that's because the depency on #543 PR, if that PR merged, then this PR's UT will pass


stale read feature

What problem does this PR solve?
support stale read feature.
proposal: https://github.com/pingcap/tispark/issues/2317

/run-all-tests

/run-all-tests

/run-all-tests profile=spark3.2

/run-all-tests profile=spark-3.2.1

/merge


chore: release 0.17.2-SNAPSHOT

:robot: I have created a release *beep* *boop*
Updating meta-information for bleeding-edge SNAPSHOT release.

This PR was generated with Release Please.

Release is at https://github.com/googleapis/google-auth-library-java/releases/tag/v0.17.2

The release build has started, the log can be viewed here. :sunflower:


Could the provider adhere to the semantic versioning standards?

After renovate upgraded the xenorchestra provider from 0.24.2 -> 0.26.1 I noticed that there was a breaking change introduced on the xenorchestra_network resource by https://github.com/vatesfr/terraform-provider-xenorchestra/pull/260 (thanks for the fix btw, lost track of it, sorry for that).
While it's easy to fix it would be very nice if breaking changes would introduce a new major version so minor/patch level updates can be installed with relative safety.

Hi @hkraal, thanks for being active in providing feedback.
Unfortunately, I think there are some potentially large breaking changes that could come (#211 being one that will likely be disruptive, but worth addressing). This is why I've been sticking to a 0.x.y release number, which I'm indicating that a breaking change could come at any time. I have taken special care to keep backwards compatibility in mind (#267, #300), but there are still some rough edges in the current functionality that can only be solved by a breaking change.
Looking at the semver spec, it seems the area before 1.0 is a bit of a gray area. However, it does mention that 1.0.0 defines the public API and matches my hesitation for moving past a 0.x.y release.

Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes.
... later in the FAQ
How do I know when to release 1.0.0?
If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backward compatibility, you should probably already be 1.0.0.

Let me start with the fact that you do follow SemVer and I was jumping the gun here, sorry for causing noise wrongfully.
I do understand your reasoning to stick to a 0.x.y release state as a developer but from a user perspective it would be very nice to know when things are expected to break. It's there but the release notes weren't very clear about this either but I certainly could have been more wary about the provider version <1.0.0 and thus not being crystallised out yet ;)
With all buzz around VMware and Vates it's clear intentions towards harbouring those which have been ditched by the Broadcom takeover; shielding the new users from breaking changes in minor releases might be worth something as well despite being valid in the 0.x.y release cycle


Make start codons optional

If no start codon is found, this starts from the beginning instead. This can make code slightly shorter, but start codons are still recommended to avoid unexpected behaviour should the string TGA occur elsewhere in the code.

uwot


CypressError trigger in bitbucket pipeline

Hi all,
I'm using a custom bitbucket pipeline image to run cypress e2e test. But I'm getting bellow CypressError when it executes.

CHERRYPICK: TEST: fulle2e "before each" hook for "TEST: End 2 end test ******************":
CypressError: Timed out retrying: cy.its() errored because the property: 'app' does not exist on your subject.

Custom docker image is extended version of cypress/included:3.8.3.
FROM cypress/included:3.8.3

RUN apt-get update

RUN DEBIAN_FRONTEND=noninteractive apt-get -q -y install \
    curl \
    unzip \
    git

# Configure NodeJs
RUN curl -sL https://deb.nodesource.com/setup_12.x  | bash - && \
    apt-get -y install nodejs

# Configure AWS CLI-2
RUN curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip" && \
    unzip awscliv2.zip && \
    ./aws/install

Can anyone help me to figure out what's the reason for my issue is?
Thank you!

Closing old issue. The error seems un-related to the docker image.


[SPARK-42597][SQL][FOLLOW-UP] Exclude EqualNullSafe when unwrapping date type to timestamp type

What changes were proposed in this pull request?
This PR excludes EqualNullSafe when unwrapping date type to timestamp type. This is because the unwrapped expression contains a UDF, which cannot pushed down to the data source:
EqualNullSafe(Cast(ts, DateType), date) -> If(IsNull(ts), FalseLiteral, And(GreaterThanOrEqual(ts, Cast(date, TimestampType)), LessThan(ts, Cast(date + 1, TimestampType))))

Why are the changes needed?
Fix bug.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Update existing unit test.

qq:

because the unwrapped expression contains a UDF

Where is the UDF, and how it's related to UDF?

@HyukjinKwon The EqualNullSafe(Cast(ts, DateType), date) shoud rewrite to If(IsNull(ts), FalseLiteral, And(GreaterThanOrEqual(ts, Cast(date, TimestampType)), LessThan(ts, Cast(date + 1, TimestampType)))).  It contains If.  So there is no benefit if rewrite EqualNullSafe(Cast(ts, DateType), date).

@wangyum I think we should mention two things:

the current rewrite is incorrect for EqualNullSafe
even if we fix the rewrite, it will contain If and can't be pushed down to the data source.

Merged to master.


Question: possible to use next-international for fetched, dynamic content? i.e. without types

This is just a conceptual question that will help me figure out if we can rollout next-international in one project we're working on.
And by dynamic content I don't mean blog posts, I just mean a dynamic list of keys for an application which is continuing to evolve.
We are fetching translation data from our API, but next-international calls out type issues when invoking either getI18n or getScopedI18n

We could conceivably address this by adding >500 keys to the type definition, but aside from such a huge type seeming strange, it also creates a maintenance hurdle as we have to update the type any time we add a new key.
Is there a way to make next-international work with this model without needing to manually track the keys? Also, we're deploying to Vercel on the edge, so no fs to use to store an updated type definition when a new key is added.

Very interesting use case, does that mean you don't want to use at all the type-safety features that provides next-international?
What does your createI18nServer function look like? I'd assume it's using fetch() instead of a dynamic import(), but just to make sure.
That's something we could ad for the v2 of next-international (#359), just need to think a bit about how to implement it.

Had this exact same problem! Absolutely love the type-safety provided when using static string, but we have quite a bit of data stored in objects and we often map over this data to render JSX and typically build the translation key with that data which gets a TS error.
To overcome this, I've placed a thin wrapper around createI18nClient and will do the same with server that looks something like this:
"use client";
import { createI18nClient } from "next-international/client";

export const {
    useI18n,
    useScopedI18n,
    I18nProviderClient,
    useChangeLocale,
    useCurrentLocale,
} = createI18nClient({
    en: () => import("./en"),
    de: () => import("./de"),
});

// Hacks so scopedT can accept dynamic strings without TS errors
type Params = Record<string, string>;
export function useI18nUntyped() {
    const scopedT = useI18n();
    // @ts-expect-error Argument of type is not assignable
    return (key: string, params?: Params) => scopedT(key, params);
}

type ScopeParams = Parameters<typeof useScopedI18n>[0];
export function useScopedI18nUntyped<Scope extends ScopeParams>(scope: Scope) {
    const scopedT = useScopedI18n(scope);
    // @ts-expect-error Argument of type is not assignable
    return (key: string, params?: Params) => scopedT(key, params);
}

This then allows us to do stuff like this useless example

Can you share source code? I wanted to add translations with fetch API, but I don't know how to implement it.


[Request] On-Off Function, Mono-Stereo

Hello! I am always grateful to you.
I'd like to ask if you can add additional functions.
In my case, I input my voice. (No music, no backup vocals) And I want a conversion without reverb.
Could you please make it possible to turn on and off the music and backup vocal removal and reverb functions?
I also type in mono files, and the output is coming out in stereo. Could you add a function that can come out as a mono?
Thank you very much for your hard work.
(I'm a translator user, so I don't know what nuance my message is getting through, but only my thanks are genuine🥹)

It seems that in your case, you only need the voice conversion functionality. In that case, you can use the official RVC voice conversion GitHub which does just that. They also come with more advanced options since it's made specifically for voice conversion, while this repo integrates multiple steps into a pipeline. https://github.com/Mangio621/Mangio-RVC-Fork

You should be able to obtain only the AI vocals from the song output file directory tho. You can look through each audio file but I think it's the one with the extended filename with numbers

thank you
It's a bit more complex ui, but it seems to work for me. thank you for telling me!

No prob


Add pellet statistics

Adding new modbus values available since V23.010

Pellet usage since last storage fill (in kg)
pellet usage total (since upgrade to Version 21.050 or newer) (in kg)
generated heat energy (total) (in kWh)
reset pellet storage filled (flag)

Hi @lein1013
Thanks for your PR! I'll have a closer look tonight. Unfortunately, I don't have a Pelletsboiler to verify.
Do you have the latest specification at hand, so you could share it?
Would you also want to add the entities in https://github.com/LavermanJJ/home-assistant-solarfocus ?
-Jeroen

Hi @LavermanJJ,
I got the information directly from the solarfocus support. I'll ask if they have this information somewhere public available.
I've also added the entities in my fork (https://github.com/lein1013/home-assistant-solarfocus), but there I did not develop the code in a way, that I can do a pull request without breaking existing code. But maybe we shall consider some refactoring there.
Testing the HACs integration was easy, because I could use my fork. For the python package, I would need to investigate more how to do this.
Hence, I plan to test the sensor first with the modbus integration of Home Assistant:
modbus:
  - name: "solarfocus"
    type: tcp
    host: xxxxxx
    port: 502
    sensors:
      - name: Pelletsverbrauch
        unit_of_measurement: kg
        slave: 2
        address: 2814


Add optional init arg to sample-xeogl-gltf to test HTTP perf

Launch the app with -i http to download the model instead of using local resource.
This change also prints the total time taken to load the model to logcat.

Abandoning this one since it just adds clutter to the sample. I can keep these changes locally for my own testing.


Fix in bfi bug

Previous windowing for the rolling mean was st at 6 days when it should have been set at 7 days per the documentation
Windowing is now 7 days

Coverage remained the same at 96.09% when pulling cd51cf6f9d880f29a1869f8d6a8877f08c910046 on tmills-usgs:master into 10d91f035833f3eac7656ad622dc15f3d11e917c on USGS-R:master.

For the record, removing that partial= did nothing because partial= was not even implemented in RcppRoll.

Yeah that is why I removed it. It was left over from the switch from zoo

On May 19, 2017, at 7:48 AM, David Blodgett<EMAIL_ADDRESS>wrote:
For the record, removing that partial= did nothing because partial= was not even implemented in RcppRoll.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

👍  Just getting it in here for the record in case someone looks at the history.


Ash/Zofia/Buck counters Maestro

https://www.reddit.com/r/Rainbow6/comments/aam9o2/this_is_a_site_i_made_showing_how_different/ectclof/?context=3
https://www.reddit.com/r/Rainbow6/comments/aam9o2/this_is_a_site_i_made_showing_how_different/ectitpu/?context=3

Torn on whether to include Buck with his grenades or not.

Nah, leave the grenades out, in that case might as well add breach charges. maybe as a trivia category?. But his shotgun should drop/breaks the cam when shot around it/breaks the wall.


Create a mock API to serve information on files within a project

When users click on an individual project, we'd like them to be able to get more information on that project and download the files. For now we're focusing on the download portion, and like to mock an endpoint that provides information on the files of a project.
AC:

[x] Mock project endpoint. Returns details on an individual project, including list of individual files and their sizes, cell counts, species, organ, and assay type. More details on payload in #14
[ ] Mock file downloads if actual data is present.

The download file link be a link to an individual static file.

@Bento007 to discuss with @liaprins-czi most likely download paths.

The file endpoint has been mocked https://ye54tu6ueg.execute-api.us-east-1.amazonaws.com/dev/project/{id}/{file}


CI segfaults on FreeBSD

CI has started to segfault on FreeBSD since the latest nightly.
This build passed with  nightly-x86_64-unknown-freebsd 1.39.0 (760226733 2019-08-22)
This build failed with nightly-x86_64-unknown-freebsd 1.39.0 (9eae1fc0e 2019-08-23)
The segfault is triggered by the build.rs of rand_pcg v0.1.2  and rand_chacha v0.1.1 (cc @dhardy), which AFAICT only call autocfg (cc @cuviper ). There was an update of autocfg recently so initially I thought that might be it, but it seems that the builds were working correctly with that update, so AFAICT neither autocfg nor rand are at fault here (cc @mati865 @asomers ).  Looking at the recently merged PRs in rust-lang/rust, I don't see any suspicious one.

I'm mostly unavailable until Monday/Tuesday.
Without backtrace it'll be hard to find the reason. Maybe you could run GDB on that CI or even locally?

I have a minimal reproducer now: https://github.com/rust-lang/libc/pull/1490
# Cargo.toml
[package]
name = "test_failure"
version = "0.1.0"
authors = ["The Rust Project Developers"]
license = "MIT OR Apache-2.0"

[build-dependencies]
autocfg = "0.1"

and build.rs:
extern crate autocfg;

fn main() {
    println!("cargo:rerun-if-changed=build.rs");
    let ac = autocfg::new();
    ac.emit_rustc_version(1, 26);
}

This fails on FreeBSD12, but not on FreeBSD11. A backtrace of the segfault would be nice.

I'll take a look.

Something is calling fstatat, and it's calling the FreeBSD 12 version but probably expecting the FreeBSD 11 structure definitions.  It screws up the stack so the core file's stack trace is useless, but I think this is the culprit:
#0  0x00000008012df594 in stat () from /lib/libc.so.7
#1  0x0000000001065f60 in std::sys::unix::fs::stat ()
    at /checkout/src/libstd/sys/unix/fs.rs:736
#2  0x0000000001054d47 in std::fs::metadata (path=0x7fffffffe1a8)
    at /checkout/src/libstd/fs.rs:1398
#3  0x000000000104609d in autocfg::AutoCfg::with_dir (dir=...)
    at /usr/home/somers/.cargo/registry/src/github.com-1ecc6299db9ec823/autocfg-0.1.6/src/lib.rs:143
#4  0x0000000001045d8a in autocfg::AutoCfg::new ()
    at /usr/home/somers/.cargo/registry/src/github.com-1ecc6299db9ec823/autocfg-0.1.6/src/lib.rs:123
#5  0x0000000001045c92 in autocfg::new ()
    at /usr/home/somers/.cargo/registry/src/github.com-1ecc6299db9ec823/autocfg-0.1.6/src/lib.rs:109
#6  0x0000000001045696 in build_script_build::main () at build.rs:5

Why isn't libc using the right link_name?

@asomers

Why isn't libc using the right link_name?

Can you submit a PR fixing that ?

I'm still trying to figure out what's going on.  I verified that the 8-22 nightly compiler works and the 8-23 nightly doesn't, but I don't see any obviously relevant changes in that date range.  rust-lang/rust's liblibc does use the correct link_name.  The problem is something more subtle.  I'll keep investigating .

The only thing in https://github.com/rust-lang/rust/compare/760226733...9eae1fc0e that looks relevant is the libc upgrade, https://github.com/rust-lang/libc/compare/0.2.61...0.2.62, which includes the FreeBSD changes of #1467.
The new match which_freebsd() here is emitting cargo:rustc-cfg=freebsd11 even for the unknown case, but Rust CI is building for FreeBSD 10.3.
https://github.com/rust-lang/rust/blob/eeba189cfb2cfc5c5898513352d4ca8f1df06e05/src/ci/docker/scripts/freebsd-toolchain.sh#L8

Since fstatat was specifically mentioned earlier:
https://github.com/rust-lang/libc/blob/9af04cebf685a38e159937633aa7c57b21bbebdb/src/unix/mod.rs#L632-L638
So forcing freebsd11 also forces that link name, but what happens when this is built against FreeBSD 10 on Rust CI? Does it actually end up linking without the specific version?
I think the reason this hit autocfg in particular is just that it's used in a build script, and those are built with -Cprefer-dynamic, so it will link to libstd.so that was itself linked in Rust CI's environment. (Versus regular builds using libstd.rlib that will link locally.)

Does it actually end up linking without the specific version?

Isn't the C library dynamically linked here ? As in, shouldn't it pick the FreeBSD12 C library and try to find there the<EMAIL_ADDRESS>symbol ?

So forcing freebsd11 also forces that link name, but what happens when this is built against FreeBSD 10 on Rust CI?

So this is the bug. We should add a freebsd10 cfg macro until Rust CI is upgraded to FreeBSD 11, and only enable that when building as part of libstd. Cirrus-CI has a freebsd-10-4-release-amd64 image, we should add that to CI to reproduce this and test that no regressions are introduced.

So this is the bug. We should add a freebsd10 cfg macro until Rust CI is upgraded to FreeBSD 11, and only enable that when building as part of libstd. Cirrus-CI has a freebsd-10-4-release-amd64 image, we should add that to CI to reproduce this and test that no regressions are introduced.

No, I don't think that's it.  Very few symbols changed between FreeBSD 10 and 11, and fstatat was not among them.  Could LIBC_CI be getting set somehow?

I don't know how - searching rust-lang/rust for LIBC_CI doesn't reveal anything.
I set up a freebsd10 build job here (https://github.com/rust-lang/libc/pull/1491) and tried to use the different link names, but that doesn't appear to make a difference.

I can reproduce the problem without using autocfg or build.rs.  But I still don't know why Rust is using the wrong symbol version.  Could it be building libc without using the build.rs at all?  That would do it.
use std::path::PathBuf;

#[test]
fn t() {
    let pb = PathBuf::from(".");
    println!("{:?}", std::fs::metadata(&pb).unwrap());
}

I can reproduce the problem without using autocfg or build.rs. But I still don't know why Rust is using the wrong symbol version.

First, what's the wrong symbol ? I suppose that the bug is that instead of picking the symbol that we use for FreeBSD11, the fstatat symbol (generic one) gets used, and that happens to point to a different symbol than the FreeBSD11 one in FreeBSD12. Is that it?
If so, then #1491 should fix that. It detects FreeBSD10, and uses the same symbols as FreeBSD11. It's not a great fix, but might do.

You can use cargo build -v to see all of the rustc commands, including whatever cfg options you expect.

A better fix would be to either migrate rust-lang/rust to FreeBSD11, or to downgrade libc to target FreeBSD10 by default.

I don't think #1491 will fix the problem.  IIUC, build.rs should be emitting cargo:rustc-cfg=freebsd11 whenever LIBC_CI is undefined.  That should've pulled in the correct link names for FreeBSD 11.  And yet rust isn't using them.

@pietroalbini @cuviper is there a way to find the build logs for that particular nightly version ?
There we should be able to see if --cfg freebsd11 is passed when building libc as part of libstd.

If I didn't mess myself, libstd on nightly is currently build using libc 0.2.51.
And this version of libc doesn't provide --cfg freebsd11 in build.rs.

Cargo.toml versions are treated as minimum semver requirements, but it may still use something newer with semver compatibility. Cargo.lock tells you the actual versions used for the whole workspace.

Oh, but I did miscopy the versions earlier... that nightly change here wes really https://github.com/rust-lang/libc/compare/0.2.60...0.2.61 -- sorry for that confusion!

@gnzlbg there are no specific jobs for nightly builds. AFAIK most recent merge that completes before 00:00 UTC is promoted as nightly.
Libc isn't built in verbose mode in Rust PRs so you cannot tell which features are enabled from the logs.

@cuviper if libstd is using 0.2.61 then that might explain this. IIRC, the build.rs being used there had a bug for freebsd and wasn't passing --cfg freebsd11 by default. That was fixed in 0.2.62, so maybe bumping libc in rust-lang/rust to 0.2.62 fixes this issue.

E.g. see here: https://github.com/rust-lang/libc/compare/0.2.60...0.2.61#diff-a7b0a2dee0126cddf994326e705a91eaR18
If the freebsd version is 10, like for Rust CI, then no --cfg freebsdxy is passed to cargo... as opposed to 0.2.62, where this was fixed, and a default of --cfg freebsd11 is used.

maybe bumping libc in rust-lang/rust to 0.2.62 fixes this issue.

Updating getrandom in https://github.com/rust-lang/rust/pull/63806 pulled libc = 0.2.62 so the answer should come soon.

I tried to build rust from scratch.  5000 seconds later it crashed with the same bug.  Updating libc to 0.2.62 didn't help.  Now I'm trying to build using a local checkout of libc.  But it's not working.  When I try to patch libc to use a local path, I get errors like this.  Can anybody more experienced with building rust help me:
Updating only changed submodules
Submodules updated in 0.04 seconds
   Compiling libc v0.2.64 (/usr/home/asomers/src/rust/libc)
   Compiling bootstrap v0.0.0 (/usr/home/asomers/src/rust/rust/src/bootstrap)
    Finished dev [unoptimized] target(s) in 8.29s
Building stage0 std artifacts (x86_64-unknown-freebsd -> x86_64-unknown-freebsd)
   Compiling libc v0.2.64 (/usr/home/asomers/src/rust/libc)
error: the feature `cfg_target_vendor` has been stable since 1.33.0 and no longer requires an attribute to enable
  --> /usr/home/asomers/src/rust/libc/src/lib.rs:28:13
   |
28 |     feature(cfg_target_vendor, link_cfg, no_core)
   |             ^^^^^^^^^^^^^^^^^
   |
   = note: `-D stable-features` implied by `-D warnings`

error: unused attribute
  --> /usr/home/asomers/src/rust/libc/src/lib.rs:34:1
   |
34 | #![no_std]
   | ^^^^^^^^^^
   |
   = note: `-D unused-attributes` implied by `-D warnings`

error: crate-level attribute should be in the root module
  --> /usr/home/asomers/src/rust/libc/src/lib.rs:34:1
   |
34 | #![no_std]
   | ^^^^^^^^^^

error: aborting due to 3 previous errors

error: Could not compile `libc`.

Simply commenting out the offending lines produces other, different build errors.  It's as if libc were getting built with the wrong options.  But removing the [patch.crates-io] and instead updating the dependency in each subcrate produces the same results.

@asomers set https://github.com/rust-lang/rust/blob/815dec9db156284b4f57a4ec34182ffc89218242/config.toml.example#L398 to false.

Actually, updating to 0.2.62 does fix the problem.  Earlier when I said that it didn't, it's because I didn't do a full build; I took a shortcut.


Wanted to perform Classification task on Sentence Pair

Hi ThilinaRajapakse,
Greetings!
I wanted to build a classification model for Sentence Pair; to be precise its Question and Paragraph pair to predict whether the particular question and the paragraph are a match or not!
I am using Squad data set for training and wanted to use a custom data set for evaluation.
Also, the string length of the question will be very small as compared to the paragraph.
Can I use the same code set with slight changes or do we need to make a major change for it?
Please guide me.
This is rather a request than an Issue, pardon me for using this window for my requirement.
Kathir.

Data for eg:
Question:
When did Namibia stop being a German colony?
Context/Paragraph:
The dry lands of Namibia were inhabited since early times by San  Damara  and Namaqua  and since about the 14th century AD by immigrating Bantu who came with the Bantu expansion  Most of the territory became a German Imperial protectorate in 1884 and remained a German colony until the end of World War I  In 1920  the League of Nations mandated the country to South Africa  which imposed its laws and  from 1948  its apartheid policy  The port of Walvis Bay and the offshore Penguin Islands had been annexed by the Cape Colony under the British crown by 1878 and had become an integral part of the new Union of South Africa at its creation in 1910

I think this could be better framed as a sentence prediction task rather than a classification task. Something akin to this perhaps. What do you think?

Thank you very much for your response, the post that you have shared is about finding similarity based on its semantics, as mentioned in the post "If we can manually label some data, the results might be even better." I have created a labeled data set from Squad 2.0 and wanted to build a supervised model trained over Squad data and can predict unseen sentence pair.
Something like using the self.text_b = text_b component of the tools.py from your guide. Something similar to this from Gluon, the challenge with gluon's guide is that it is not mentioned how to evaluate the model.
Please advise.

I'm still not seeing how this could be a classification task, unless you were to just concatenate the answers with the questions (some with the corresponding answer, others with random answers), and create a dataset containing matches vs non-matches. That doesn't really feel like a good solution to me, but it is something that could be tried I suppose.
Personally, I would go with sentence prediction. You could try the BertForNextSentencePrediction model and fine-tune it for your task. See this.
I'm sorry, but I'm not familiar with Gluon. I'm not sure what you don't understand regarding evaluating the model though. Can you elaborate?


Fixed URL in CreateMultiple

@anjakuzev Hi, thanks for opening PR to fix the url issue. Give the fact that are sdks are generated we are not accepting PRs and prefer issues. We will take this fix into the account when making our next go-sdk release.


WARN: <IP_ADDRESS>.a - for monitor SPN 5322 AFT NMHC Converting Catalyst Incorrect

WARN: <IP_ADDRESS>.a - for monitor SPN 5322 AFT NMHC Converting Catalyst Incorrect
Criteria excludes NMHC Converting Catalyst ... but it is flagged anyway.  V3.0.3
See #902 for detailed info on <IP_ADDRESS>.a and Table A-4.
WARN: <IP_ADDRESS>.a - Engine #1 (0) response indicates denominator for monitor SPN 5322 AFT NMHC Converting Catalyst System Monitor has not incremented by one
Start Test 11.8 - DM20: Monitor performance ratio
14:31:15.5914 Destination Specific DM20 Request to Engine #1 (0)
14:31:15.5934 18EA00F9 [3] 00 C2 00 (TX)
14:31:16.2089 18C2F900 [74] 40 00 11 00 CA 14 F8 00 00 01 00 B8 12 F8 00 00 11 00 BC 14 F8 00 00 00 00 C6 14 F8 00 00 11 00 F2 0B F8 00 00 11 00 EA 0C F8 00 00 00 00 F8 0B F8 03 00 11 00 C9 14 F8 00 00 11 00 EC 0B F8 00 00 00 00 EF 0B F8 00 00 11 00
DM20 from Engine #1 (0):  [
Num'r /  Den'r
Ignition Cycles                                                       64
OBD Monitoring Conditions Encountered                                 17
SPN 5322 AFT NMHC Converting Catalyst System Monitor          0 /      1
SPN 4792 AFT 1 SCR System                                     0 /     17
SPN 5308 AFT 1 NOx Adsorber Catalyst System Monitor           0 /      0
SPN 5318 AFT Exhaust Gas Sensor System Monitor                0 /     17
SPN 3058 Engine EGR System Monitor                            0 /     17
SPN 3306 Variable Valve Timing and/or Control                 0 /      0
SPN 3064 AFT DPF System Monitor                               3 /     17
SPN 5321 Engine Intake Manifold Pressure System Monitor       0 /     17
SPN 3052 Engine Misfire System Monitor                        0 /      0
SPN 3055 Engine Fuel System Monitor                           0 /     17
]
WARN: <IP_ADDRESS>.a - Engine #1 (0) response indicates denominator for monitor SPN 5322 AFT NMHC Converting Catalyst System Monitor has not incremented by one
WARN: <IP_ADDRESS>.a - Engine #1 (0) response indicates denominator for monitor SPN 5308 AFT 1 NOx Adsorber Catalyst System Monitor has not incremented by one
// Since monitor 5308 was not sent with unavailable numerators and denominators, the second warning message is correct for this SCR related monitor.
End Test 11.8 - DM20: Monitor performance ratio
<IP_ADDRESS> Warn Criteria
a. Warn if any response indicates denominator for SCR, EGR, NOx sensor, boost, and fuel system have not incremented by one.
b. Warn if any ECU response shows:
i. any monitor denominator greater than the general denominator;
ii. general denominator greater than the ignition cycle counter (SPNSP 3048); or
iii. if any numerator greater than the ignition cycle counter.
c. Compare all values to values recorded in part 1.
i. Warn if any value (numerator, denominator, or ignition cycle counter) is less than their corresponding value in part 1.
d. If more than one ECU reports DM20 data, warn if general denominators or ignition cycle counts do not match from all ECUs.

Documentation to #902 will suffice.


Lee Algorithm

Overview

Write code for Lee Algorithm in C++.
Add that code into a directory named "Graphs", if the directory doesn't exist, create one and add the code file.

Please take care of these things while creating the pull request.

The code file was added to the correct directory.
Code quality looks good.
The programming language used is the same as mentioned in the issue.

I can contribute here. Consider assigning me to this issue.
Thanks.
@vashuteotia123


Pretrained model

Dear Nicheformer authors,
We are exceited to see your new released nichefomrer model which can be used as the fundation or backbone of single cell deep learning training for downstearm task.  Would you kindly provide your pretrained model and usage document to benefit the reader and in turn make your model more infuential.
Thank you
Rena

Hi @xim2016,
thanks for your interest in using nicheformer!
We are sharing pretraining weights through mendeley data. A draft version can be accessed here:
https://data.mendeley.com/preview/87gm9hrgm8?a=d95a6dde-e054-4245-a7eb-0522d6ea7dff
I will also add this information to the readme so it's easier accessible! thanks!
I am closing your comment as resolved, but feel free to open it again in case of further questions!


fixed memory management bugs

This pull request fixes two bugs related to memory management in the C version of the implementation (found in the c-micrograd folder).
Bug #1
Original:
Value** make_values(float* arr) {
    size_t len = sizeof(arr) / sizeof(arr[0]);
    // code
}

This results in unintended behavior because sizeof(arr) does not return the total number of bytes the array stores. It returns the size of the pointer to the array itself which is 4 or 8 bytes, regardless of the length of the array. As a result, I modified the function to take in "len" as an input and changed calls to the function where needed.
Bug #2
Original:
Value* neuron_forward(Neuron* neuron, Value** x) {
    Value* sum = make_value(0);
    // more code here
    if (neuron->nonlin) {
        Value* sum = leaky_relu(sum);
    }
    return sum;
}

This results in unintended behavior because it redeclares sum inside the scope of the if statement and, as a result, does not return the sum with leaky_relu applied to it. This also sometimes leads to segmentation faults during training. All I did to fix this was remove "Value *" from the line inside of the if statement.
Fixed code:
Value* neuron_forward(Neuron* neuron, Value** x) {
    Value* sum = make_value(0);
    // more code here
    if (neuron->nonlin) {
        sum = leaky_relu(sum);
    }
    return sum;
}

Amazing! @zroe1
Thanks for actually creating such a properly structured PR.

I'm merging the changes right now.
We don't really have tests, at the moment, but maybe if the projects start building more momentum we can start a more TDD approach.


Added GPL guard in optimization solver that uses libqp

Targetted at fixing #3704

Fine to merge from my side (if you tested the build with GPL turned off)

Fixed in 8f9021fc9da57160d4d658ddeb9789740595a6f5


Fix broken peerdavid GitHub links

Fixes https://github.com/sqfmi/watchy-docs/issues/36.
Updates peerdavid's GitHub links to https://github.com/peerdavid/wos.
cc @peerdavid
Background
The last good commit from the peerdavid/Watchy repo is https://github.com/peerdavid/Watchy/commit/3a32880b93c926f6ac5d996ee8d7ebffbdfe0136.  Here's a link to the currently-shipped repo with this path, pinned to this commit:
https://github.com/peerdavid/Watchy/tree/3a32880b93c926f6ac5d996ee8d7ebffbdfe0136/examples/WatchFaces/David
However, the README.md from the same repo at the current master reads:

THIS REPO IS NO MORE UPDATED OR MAINTAINED. WE MOVED TO https://github.com/peerdavid/wos

Unfortunately, it looks like this was a refactor that has been abandoned, as README.md from the new repo states:

Watchy OS (WOS)
I'm currently woring on WatchyOS (WOS) - its an alternative to the official
Watchy code. Instead on heavly relying on inheritance, this project is structured
by different components which are controlled by a kernel. This should provide
more flexibility and it should become easier for developers to add new
features.
More updates are comming soon.

However, as of this writing, the last update was from 8 months ago.  In addition, the nice README.md from the peerdavid/Watchy repo is not present in the new repo.
However, this does reflect the latest work by peerdavid, and I think they would appreciate linking to their latest stuff instead of pinning their old stuff to an old commit.

Are there any changes you'd like me to make to this PR?

This looks great, thanks for fixing the links!


chore(master): release 0.101.0-alpha

:robot: I have created a release beep boop
0.101.0-alpha (2024-05-09)
Features

new (2936e0f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/mafqla/yalis-blog/releases/tag/v0.101.0-alpha :sunflower:


When creating RKE clusters, expand the options section

When creating k8s clusters that use RKE, the options are not expanded open, which makes it hard to know which k8s version is going to be deployed by default.
From UX, I think it'd be better if it was expanded so people could see the options immediately.

Version: Master 2.2 (11/26/18)
Confirmed fixed. Tested with all RKE providers. Cluster options section is now automatically opened.


require-atomic-updates: document.title (false positive)

I'm using eslint 6.0.1 and believe I'm getting a false positive for the require-atomic-updates rule. Here's a code sample which reproduces the false-positive:
async function test()
{
	document.createElement("div");
	await Promise.resolve();
	document.title = "Test";
}
test();

The line document.title = "Test"; (above) produces this error:
Possible race condition: `document.title` might be reassigned based
on an outdated value of `document.title`. (require-atomic-updates)

However, I noticed that if I change document.title to window.document.title the error goes away:
async function test()
{
	document.createElement("div");
	await Promise.resolve();
	window.document.title = "Test";
}
test();

This issue was moved here:
https://github.com/eslint/eslint/issues/11967

Thanks for moving the issue to the correct repo!


Upload model checkpoints on the Hugging Face Hub.

Hi there,
Congrats on creating such a brilliant library and for also releasing AWQ kernels that work w/ metal as well. I'm VB I lead the advocacy efforts for Open Source  ML at Hugging Face. I saw that the model checkpoints are currently hosted on a Dropbox. It'd be great if you could upload and share the models on the Hugging Face Hub!
The model checkpoints could reside under your org: https://huggingface.co/mit-han-lab
In general this ensures better discovery of both your library and the checkpoints.
In the process we can also integrate it with the huggingface_hub python library to programmatically download the checkpoints as well. This would ensure seamless caching of the models as well.
Happy to help you with this process.
Congrats, and I'm looking forward to these checkpoints on the Hub.
Cheers!
VB

(happy to also take this conversation over on the slack channel too)


fix(select): correct invalid inline spacing

Closes #2113
This PR fixes the padding and positioning for the select inputs and invalid icons
We also now show the hover state on the input field when the user hovers over the invalid icon

I just spoke with Anna IRL and the hover color should be $hover-ui instead of ui-01 for inline dropdown.

@designertyler made that change, it should be in the netlify link now


FileTarget: Fix file archive race-condition.

Fix #1608

This change is

Guess we don't have a Mutex on Silverlight

Current coverage is 80% (diff: 80%)

Merging #1646 into master will increase coverage by <1%

@@             master      #1646   diff @@
==========================================
  Files           273        273
  Lines         16699      16727    +28
  Methods        2653       2660     +7
  Messages          0          0
  Branches       1840       1843     +3
==========================================
+ Hits          13271      13305    +34
+ Misses         3009       3002     -7
- Partials        419        420     +1

Powered by Codecov. Last update b483611...72e4a4e

@304NotModified unfortunately, I cannot produce the error from #1608 anymore, even with the old NLog.dll (it stopped happening; I don't know why). We must probably make a hidden package again so viseu can test again.


Increase the padding-bottom in Scholarship detail page

Description
Page: Scholarship detail
The padding-bottom of the first section, where breadcrumb and title are, looks tight.

Expectation
The padding-bottom space should be 64px.

Hey @kgodey , @krysal  is this issue resolved or I can take this?

@Aakash2408 This is already fixed in #70, just waiting for review.


Visual regression test suite prototype

Plan

For every PR, via existing CircleCI builds
Running both on Storybook stories, and integration tests with Puppeteer
Running multiple "projects" is documented
GitHub PR status
Do not require Percy approvals
Set to auto-approve where relevant
Next steps: trial all of the above on wagtail-fork project, incl. PR workflow
Looking for volunteers to review
Scott has a little bit of experience with Percy and is happy to take a look
Naomi is happy to review the Pull Request side of things to see how that can work for others.

Tasks

[x] Make prototype on wagtail-fork
[ ] Review by UI team
[ ] Run past core team

Testing / review plan
UI team review, Scott & Naomi

Prototype: check! https://github.com/thibaudcolas/wagtail-fork/pull/4.
I will keep this issue opened while we gather feedback, but would recommend people comment on https://github.com/thibaudcolas/wagtail-fork/pull/4 directly so it’s all in one place.


What date format is it using? ISO 8601 ?

Use ISO 8601 format. Add it to radome specification.
http://www.wikiwand.com/en/ISO_8601

It uses ISO, check dependencies. Might be better to add it to the method documentation than to the README.
https://github.com/hyperoslo/NSString-HYPDate/blob/master/NSString-HYPDate.podspec

great, just a small mentioning about that in the readme would give a lot of credits, reliability and trust.

closing issue because of lack of activity, reopen if needed


Blockprecon

Codecov Report
Patch coverage: 57.47% and project coverage change: -15.85 :warning:

Comparison is base (e2d82c9) 83.51% compared to head (4e7fe80) 67.67%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##           master      #26       +/-   ##
===========================================
- Coverage   83.51%   67.67%   -15.85%
===========================================
  Files          19       20        +1
  Lines         922      996       +74
===========================================
- Hits          770      674       -96
- Misses        152      322      +170

Impacted Files
Coverage Δ

src/ExtendableSparse.jl
100.00% <ø> (ø)

src/parallel_ilu0.jl
0.00% <0.00%> (-96.80%)
:arrow_down:

src/factorizations.jl
68.18% <54.54%> (ø)

src/blockpreconditioner.jl
58.69% <58.69%> (ø)

src/ilu0.jl
72.41% <59.61%> (-27.59%)
:arrow_down:

src/jacobi.jl
74.28% <72.72%> (-13.72%)
:arrow_down:

src/parallel_jacobi.jl
68.57% <72.72%> (-15.43%)
:arrow_down:

src/pardiso_lu.jl
77.77% <78.57%> (+8.21%)
:arrow_up:

src/amg.jl
90.00% <80.00%> (-10.00%)
:arrow_down:

src/iluzero.jl
84.61% <80.00%> (-1.10%)
:arrow_down:

... and 4 more

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


Improved cython support

better to_python/from_python signatures

according to @aguinet this now compiles but the result is incorrect. I need to update the tests suite to showcase that.

@aguinet Just found the issue: you're converting extended slices calls to a[b,c] which in C++ calls the operator[] with one argument, using the comma as the sequence operator and not the argument separator. Yopu should generate a(b,c) instead. Can you confirm it works in that setup?


API: Enable remote write and otlp receivers by default

A bit related to https://github.com/prometheus/prometheus/issues/14410 but suggesting a new approach.
Both endpoints have been in Prometheus for some time now and we consider them both stable. Up until now they were hidden by default and needed a flag to enable them. This PR suggests to enable them by default.

So far we have merged breaking changes like this to release-3.0. Over there the remote-write-receiver flag has already be dropped. I'd propose to add the otlp change there as well.

That makes sense @roidelapluie thanks for bringing this up. In that case I'll close the PR. Bartek made a point about enabling this through config, I think thats also interesting.


test(table): auto collapse rows

Describe pull-request
Fix flaky test
Issue Linking:

Jira: revisit flakey tests

How to test
run: npm run test in root directory (tegel)
Checklist before submission

[x] I have added unit tests for my changes (if applicable)
[x] All existing tests pass
[x] npm run build-all without errors

Screenshots
Expand row 1 && collapse row 2

Expand row 2 && collapse row 1

Additional context
Tried to simplify the test a bit
Can add test for row 3 and 4 if needed, but might be redundant to test the same thing. Trying to keep down the amount of tests that we have.
Let me know in comments if you have any inputs

I'm getting this error when I attempt to run the tests locally:
3 failed
    src/components/dropdown/test/basic/dropdown.e2e.ts:50:3 › tds-dropdown-basic › reset() method resets the dropdown
    src/components/dropdown/test/filter/dropdown.e2e.ts:100:3 › tds-dropdown-filter › toggle dropdown visibility and select option two
    src/components/dropdown/test/multiselect-filter/dropdown.e2e.ts:7:3 › tds-dropdown-multiselect-filter › When focusing on the input it should clear itself

Can you please double check that after you pull this branch that you run npm run build and then npm run test ?
Sometimes missing build can cause test to fail.

I have checked this one, but unfortunately 2/4 runs end up in test not passing :(

@theJohnnyMe I refactored the flaky test into screenshots instead. Please have a look!

I still get 2/4 or 1/4 failing when running this locally. Converting it to Draft, let's discuss what we will do with this.


added php book list on en books file

What does this PR do?
Added https://books.goalkicker.com/PHPBook/ for php en books file
For resources
Description
Followed template of md file modified
Why is this valuable (or not)?
This focuses on php tutorials, coding, etc
How do we know it's really free?
I tried downloading the pdf from the site and it's free with all php notes
For book lists, is it a book? For course lists, is it a course? etc.
This is a PDF and based on readme.md this is categorized under books
Checklist:

[ ] Read our contributing guidelines
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction)

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

duplicate


RHIROS-686 removed text from pie chart in report

Description
removed text from pie chart in report
Jira: https://issues.redhat.com/browse/RHIROS-686
Screenshot:

References:
https://github.com/RedHatInsights/frontend-components/blob/95cee1de51/packages/pdf-generator/src/components/Chart.js#L96
https://codesandbox.io/s/agitated-swanson-9jzm4e?file=/index.js

Codecov Report

Merging #128 (fed263c) into main (cd73434) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

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

@@            Coverage Diff             @@
##             main     #128      +/-   ##
==========================================
- Coverage   23.09%   23.06%   -0.03%
==========================================
  Files          45       45
  Lines         879      880       +1
  Branches      152      152
==========================================
  Hits          203      203
- Misses        631      632       +1
  Partials       45       45

Impacted Files
Coverage Δ

...rc/Components/Reports/Common/ExecutiveFirstPage.js
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

Thank you @PreetiW and @karelhala for review.


is there any way to deposit and withdraw osmo or atom ?

is there any examples with cosmwasm smart contracts in osmosis which works related to deposit/withdraw functionality of osmo tokens ?

@sbnair could you give more context about it? do you mean IBC-ing in and out of the chain or some other thing?

the issue has been inactive, will close this now and if you have any question, please reopen this again


Expose metrics in quarkus

fixes #128

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/127/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/128/


some problem of run ./minidbg hello

Did i wrong in some step?

i get this same error.
then i cloned from forked repository which have 39 commits, still there is error, but at lease i can see the minidbg> prompt:

i can debug minidbg with cgdb, start with cgdb -args ./minidbg ./variable
i can fix this error by changing
m_load_address = std::stoi(addr, 0, 16);
into
m_load_address = std::stol(addr, 0, 16);
in void debugger::initialise_load_address()


Previewers are not very responsive compared to telescope

Info

Operating System: Arch Linux
Shell: zsh
Terminal: kitty
nvim --version: NVIM v0.8.0-dev-nightly
fzf --version: 0.31.0 (a0ef898)
sk --version: 0.9.4

[ ] The issue is reproducible with minimal_init.lua

fzf-lua configuration

require("fzf-lua").setup {
	fzf_bin = "sk",
	winopts = {
		preview = {
			-- default = 'bat',
			delay = 0
		}
	}
}

Description
fzf-lua previewers have a really noticeable delay, while telescope is basically instant. I tried setting delay to 0, but it doesn't help at all, the delay still feels exactly like it did before with fzf. With sk it feels more responsive but causes an error: https://im.pepega.club/r1k1sy.mp4

This is most likely unrelated to fzf-lua, fzf has an intentional (IMO it’s a good thing) debounce delay of 100ms, doesn’t matter if you’re using bat previewer or builtin, fzf still needs to fire the command (a neovim --headless … shell command) to let fzf-lua know it needs to update the previewer.
Quite honestly I don’t see this as an issue, the preview still opens fast enough without it being spammy, why would anyone need an immediate response from the previewer while holding down arrow?

It's an issue for me because it feels pretty weird to have a huge delay on the previewer while scrolling. I guess I'll try patching fzf to remove the delay

It does remove the delay in terminal, but it's still super slow in nvim

It does remove the delay in terminal, but it's still super slow in nvim, even with the bat previewer somehow? Works perfectly fine with ./fzf --preview "bat --color=always {}"

Maybe because it still needs to run neovim --headless and connect over RPC to the main instance, try with previewer = 'bat_native', does it make any difference?

Btw, I'm not sure what went wrong in your setup, maybe it's not getting called properly? here's mine with delay = 0, as you can see it's pretty immediete:

Seems to be called fine :shrug:

Does it behave the same with minimal_init.lua?
See my updated comment screencast (with delay), the behavior in your video with the default delay is odd, with 100ms delay it shouldn't even attempt to display the preview until the key is released.

With minimal_init.lua and `delay=2000`` the delay seems to be about 5s, weird

I watched your video again in detail, something is definitely off, it's not supposed to be like that, I also ran mine with bat previewer (winopts.preview.delay doesn't natter in this case) it's flying for me, this requires a deeper investigation.

I feel like this could be related to me using neovim-git, I'll try downgrading

That was it :thinking:

Probably something related to the RPC comms between the instances.
Is it now working as expected with delay = 0?

Or not? Still i don't feel any difference between 100 and 0 https://im.pepega.club/fvbhl9.mp4

Or not? Still i don't feel any difference between 100 and 0 https://im.pepega.club/fvbhl9.mp4

Something is still off, this doesn’t seem like 100ms with the default delay.

OHH, right, the minimal_init.lua doesn't clear plugins, it's working as expected after i nuked the packer directory, maybe you shouldn't disable auto_clean :sweat_smile:

OHH, right, the minimal_init.lua doesn't clear plugins, it's working as expected after i nuked the packer directory, maybe you shouldn't disable auto_clean 😅 Time to figure out which plugin was slowing it down

Issues that require clearing the plugin directory to solve are extremely rare I’d feel so bad nuking people’s configs :)
I might consider changing the strategy of minimal unit to a temporary download and using PACKPATH.
Keep this thread updated with your findings which plugin caused this?

I feel like it might be a lot of things combined, not sure yet

Can I somehow get the time preview takes to fully render?

Can I somehow get the time preview takes to fully render?

Not without modifying the source

Closing since this we discovered this isn’t a bug, feel free to open if you want need my help or want to continue the discussion.


[EN] Feedback for: /web/tools/chrome-devtools/profile/evaluate-performance/timeline-tool?hl=en

please update Timeline part，It's so old

@kaycebasques @pbakaus - please review and assign as appropriate

Hey @riskers I'm in the process of updating all of the Profile docs

Hey @riskers, the doc has been updated!
Thanks for your feedback


Use transparent-looking background

The grayscale background made it a bit hard for me to tell what the output picture looks like, so I replaced it with this background.

I have no idea if that's preferable, so I figured I'd ask.

That's a nice improvement, thanks!


Logging request and response body

Hi guys, I need some help using Spring Cloud Gateway.
I am filtering a Request (Post and Get) redirecting because I need to log the request and response on AWS firehose.
My logging must have for the Request the Method Value, Uri address, Header and Body (as a json). And for response must have Status Code, Header and Body.
My problem is, how do I get the body of the request and response from ServerWebExchange? I tried many things, but none of them worked.
My code:
@Component
class GatewayGlobalFilter(var logging : LoggingUseCase): GlobalFilter, Ordered {

    override fun filter(exchange: ServerWebExchange,
                        chain: GatewayFilterChain): Mono<Void> {

        val uuid = UUID.randomUUID()

        return chain.filter(exchange).doFirst {
            Mono.just(logRequest(exchange, uuid)).subscribe(
                    logging::sendRequest,
                    Throwable::printStackTrace
            )
        }.then(
            Mono.fromRunnable{
                logging.sendResponse(logResponse(exchange, uuid))
            }
        )
    }

    private fun logRequest(exchange: ServerWebExchange, uuid: UUID): MyRequest {

        val jsonHeader = gson.toJson(exchange.request.headers)
        val jsonBody = ???
        val request = MyRequest(
                exchange.request.methodValue,
                exchange.request.uri.toString(),
                jsonHeader,
                jsonBody,
                uuid.toString()
        )
        return request
    }

    private fun logResponse(exchange: ServerWebExchange, uuid: UUID): MyResponse {

        val jsonHeader = gson.toJson(exchange.response.headers)
        val jsonBody = ???
        val response = MyResponse(
                exchange.response.rawStatusCode!!,
                jsonHeader,
                jsonBody,
                uuid.toString()
        )
        return response
    }

    override fun getOrder(): Int = -1
}

Hi, does anyone knows how I solve my problem?

@rafael-coelho-amaro
you can refer class ModifyRequestBodyGatewayFilterFactory and ModifyResponseBodyGatewayFilterFactory in Spring Cloud Gateway to get body of request or response.

org.springframework.cloud.gateway.filter.factory.rewrite.ModifyRequestBodyGatewayFilterFactory and org.springframework.cloud.gateway.filter.factory.rewrite.ModifyResponseBodyGatewayFilterFactory  is part of Spring Cloud Gateway source code and github address is here

reactor netty also has logging see https://stackoverflow.com/questions/54117061/springcloudgateway-log-incoming-request-url-and-corresponding-route-uri

See https://github.com/spring-cloud/spring-cloud-sleuth/issues/1690#issuecomment-857657756
In the example project, you'll find code on how to log the requests and response using Logbook and how to add traceId and spanIds if you want to use spring-cloud-sleuth.

Hello @ctlove0523 and @spencergibb, do you have a working example using ModifyResponseBodyGatewayFilterFactory? I have a project where we were able to get the modify request filter working however when we applied the same logic to try and log the response with the modify response filter we noticed that the filter gets instantiated but the rewriteFunction is never actually called.
Here's how we are creating the Filter:
ModifyResponseBodyGatewayFilterFactory.Config()
                .setRewriteFunction(
                    String::class.java,
                    String::class.java
                ) { exchange: ServerWebExchange?, responseBody: String ->
                    logger.info("Response Body: {}", responseBody)
                    Mono.just(responseBody.toString())
                }

Do you know what might be the issue with this implementation? Thank you in advance!

https://github.com/spring-cloud/spring-cloud-gateway/blob/73429eb69ab9ae5c165fd946124a40d1c6307b11/spring-cloud-gateway-sample/src/main/java/org/springframework/cloud/gateway/sample/GatewaySampleApplication.java#L75-L101

Closing due to age of the question. If you would like us to look at this issue, please comment and we will look at re-opening the issue.

Is issue this already closed?

你好，你的邮件我已经收到，每天会在晚上查看邮件并回复。急事请打电话


dispatch() helper with resolving class from ioc container and arguments

This allows you dispatch a job from anywhere with automatic class resolution.
dispatch(JobName::class, 'arg1', 'arg2');

i wrote basic test, but have no idea how to test job arguments.
all tests passing, backward compatibility should be ok.

You can just use Bus::dispatch(App::makeWith()). Thanks.

Well, this is what i'm basically doing inside the function. But i made it much shorter, more intuitive and easier to mentally parse. I thought this is what Laravel is about :)
You make use of dynamic arguments with many other functions and methods - why not this one?


cannot run schema registry with ssl enabled: network password is not correct

Description
hi
I am facing an issue when setting my keystore.p12 in SchemaRegistryConfig.SslKeystoreLocation . I get an error saying the network password is not correct when running on a windows server 2016. This happens even when the password is blank. Strangely it works on my local with same keystore and truststore. Locally i am running windows 10
Has anyone encountered a similar problem or know the cause?
How to reproduce
run a kafka producer on Windows server 2016 with ssl
            var schemaRegistry = new SchemaRegistryConfig
            {
                Url = schemaRegistryUrls,
                SslKeystoreLocation = $"yourp12keystore",
                SslKeystorePassword = "",
                SslCaLocation = $"yourtruststore"
            };
           _cachedSchemaRegistryClient = new CachedSchemaRegistryClient(schemaRegistry);

=========
Please provide the following information:
Application:
Framework > netcoreapp3.1
Confluent.SchemaRegistry, Version=<IP_ADDRESS>
Confluent.Kafka Version="1.7.0"
Hosting server:
Windows server 2016
Keystore created using keytool in jks format and then converted to p12
Key is rsa

error:
Exception: Internal.Cryptography.CryptoThrowHelper+WindowsCryptographicException: The specified network password is not correct.
at Internal.Cryptography.Pal.CertificatePal.FilterPFXStore(Byte[] rawData, SafePasswordHandle password, PfxCertStoreFlags pfxCertStoreFlags)
at Internal.Cryptography.Pal.CertificatePal.FromBlobOrFile(Byte[] rawData, String fileName, SafePasswordHandle password, X509KeyStorageFlags keyStorageFlags)
at System.Security.Cryptography.X509Certificates.X509Certificate..ctor(String fileName, String password, X509KeyStorageFlags keyStorageFlags)
at System.Security.Cryptography.X509Certificates.X509Certificate2..ctor(String fileName, String password)
at Confluent.SchemaRegistry.CachedSchemaRegistryClient.SetSslConfig(IEnumerable`1 config)

i'd need to spend time investigating this, outside my immediate expertise.
happy to look into if this if it's identified as a bug.

i'd need to spend time investigating this, outside my immediate expertise. happy to look into if this if it's identified as a bug.

Hi mhowlett,
After digging a bit more into it i have excluded confluence as being the culprit. the issue seems related to the keyvault itself or how it is being read by the server. I don't suppose this issue is relevant to this repository although would be nice if anyone experiencing the same problem could share their findings

Hi @ruifrvaz
I have the exact same issue and I'm still struggling with it.
Did you find the solution?
Obrigado!

Stuck with the same, any other solution rather than upgrade the server to be windows server 2019?
It is all regarding the encryption protocol of AES256SHA256 which is not supported by windows 2016 build number <19xx


Slug sections should have well background on browse pages

Pages that use atomic elements with slug headings such as any of the "Related X" molecules should have a well background so that they look like a pre-footer.
Looks like this is happening across multiple browse pages.
Examples
Protecting against credit discrimination
Protecting against fraud
Sending money abroad Spanish
Money tips and basics for servicemembers

This issue is affecting browse-basic and browse-filterable pages.


[Event Request] Codeunit::"Catalog Item Management" - Function CreateItemFromNonstock - OnBeforeCreateItemFromNonstock

We like to request the following Event:
Object: Codeunit::"Catalog Item Management"
Function: CreateItemFromNonstock
Publisher Event: OnBeforeCreateItemFromNonstock
Reason: To implement custom business logic
Where is the event placed:
procedure CreateItemFromNonstock(Nonstock2: Record "Nonstock Item")
begin
OnBeforeCreateItemFromNonstock(Nonstock2);
if NewItem.Get(Nonstock2."Item No.") then
Error(Text000, Nonstock2."Item No.");
Nonstock2."Item No." :=
GetNewItemNo(
Nonstock2, StrLen(Nonstock2."Vendor Item No."), StrLen(Nonstock2."Manufacturer Code"));
Event Code:
[IntegrationEvent(false, false)]
procedure OnBeforeCreateItemFromNonstock(var NonstockItem: Record "Nonstock Item")
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Update all godoc.org URLs to pkg.go.dev.

See dogmatiq/dogma#112 and https://github.com/dogmatiq/dogma/commit/b3c44070d40e06ef521bec040e0729d9bc84450b for an example.
This is blocked by the milestone itself, because pkg.go.dev only shows tags.

This is no longer blocked, pkg.go.dev now seems to sure untagged repos: https://pkg.go.dev/github.com/dogmatiq/infix.


"npx chappe build" on Windows gives wrong directory structure

Running npx chappe build on a Windows environment seems to be generating a weird directory structure: after a certain depth, the pre-rendered HTML files for each guide is stored under a subdirectory called index.md, as can be seen here:
https://paste.sparked.host/umiboqehec.txt
Running the same command on Linux, against the same repository, yields the correct results as expected:
https://paste.sparked.host/zutahoyapo.txt

Hello there!
Unfortunately, Chappe was not built for and tested for Windows. I also don't have any Windows platform to test it on.
I'd accept PRs for a fix. Thank you!

Hm, I wonder how you guys test docs at Crisp...
Anyway, back to the point. It probably has to do with one of the many deprecated dependencies used by Chappe (possibly urix? it's a few levels deep in the dependency tree). Unfortunately, I don't have the time to try to fix this, so I'll see if running this under WSL yields different results.

We all run on macOS, on which everything works just fine, and then we build for production on Linux which also works fine.
Let me know if you find anything.


as for REGION_IGNORE

There's something I'd like to ask. Why BOURGOGNE FRANCHE COMTE is ignored?
https://github.com/sherpya/geolite2legacy/blob/master/geoname2fips.py#L445
In the OSS I use, there is the following source code, I expect that the region_code is A6, but because it is being ignored it has become 00.
https://github.com/matomo-org/matomo/blob/ac07aa40497901c7f2a7a99166a88a1b72265d53/plugins/UserCountry/LocationProvider/GeoIp.php#L210
    private static function getTestIpAndResult()
    {
        static $result = null;
        if (is_null($result)) {
            // TODO: what happens when IP changes? should we get this information from piwik.org?
            $expected = array(self::COUNTRY_CODE_KEY => 'FR',
                              self::REGION_CODE_KEY  => 'A6',
                              self::CITY_NAME_KEY    => 'Besançon');
            $result = array(self::TEST_IP, $expected);
        }
        return $result;
    }

I just realized, the cause is that not match the region name of fips-10-4 and Locations.csv of MMDB. isn't it?
eg:

fips-10-4
Franche-Comte
https://github.com/datasets/fips-10-4/blob/master/data/data.csv

FRA6	region region	Franche-Comte

MMDB Locations
Bourgogne-Franche-Comte

$ grep 3033123 ./GeoLite2-City-Locations-en.csv
3033123,en,EU,Europe,FR,France,BFC,Bourgogne-Franche-Comte,25,Doubs,Besançon,,Europe/Paris,1

they are two different territories now, so it's directly mappable without adding any single city to one or another region, I've tried but it would take ages
https://en.wikipedia.org/wiki/List_of_FIPS_region_codes_(D–F)#FR:_France

Thank you so much for your lucid explanations. I get it.
Since 1 January 2016, it is part of the new region Bourgogne-Franche-Comté.

It is difficult to completely clear.


Newcomer doc 1: Project initialization route quickstart

Describe the feature you would like
A how-to guide that walks the user through the steps of initializing and configuring a new project with

environments
Flextesa with custom sandbox config
LIGO compilation
origination to a sandbox and test-net

Is this feature solving a problem?
It's currently difficult for a new user to understand the sequence of steps needed to get a new project up and running
Please share any additional details you have?
No response
Code of Conduct

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

Blocked by #387

Will proceed to complete and release this doc without waiting for #387
Issue #493 has been created to track implementing the updated output once the bug has been fixed


WindowsFile appends additional newlines to content

I'm seeing an extra \r\n\r\n on all content strings. Switching to the file download code in winrm-fs (/cc @mwrock) should fix this I think as it base64's the content before echoing it over WinRM.

+1 lets use it


Final score race condition (Episode-10)

In the Episode-10 branch, sometimes when the enemy hits a player the final score will read:
"Your final score was:"  (note, no actual score)
Sometimes it will print out the score.
It seems like by the time the update_final_score_text runs, there may or may not be anything in the
mut game_over_event_reader: EventReader<GameOver>,
I'll see if I can pinpoint it and raise a PR, but I'm brand new to Bevy so it may not be immediately evident to me.

The  high_scores_updated  is always working and I think that is because the system is specified as .add_system(update_score.run_if(in_state(AppState::Game)))
So it will always catch it on the current frame.
By the time the update_final_score_text is running, the frame may have already passed, and the events (if I understand correctly) only live for the duration of the frame.
I believe this is happening because the handle_game_over is reading from the GameOver event, and then during that frame will set app_state_next_state.set(AppState::GameOver);.
It seems like this  switch to  the GameOver app state is happening a frame later, in which case the GameOver event is gone.. and thus not able to be read by update_final_score_text.
I still don't have a fix, but I believe that is at least somewhat the gist of the issue.

Hi zendril! I met the same problem. I think update_final_score_text can actually capture the event. However, the text_query could have nothing matched.

We can write .add_systems(Update, update_final_score_text), without the run_if() state condition, to ensure update_final_score_text will capture the GameOver event. However, the text_query sometimes can not find the matched entity like this:

A possible solution is to get rid of GameOver event, and to use HighScore Resource. Like this:

I test it for several times and it just work fine.
Since we use last().unwrap(), we should keep the run_if condition as following:

Or the codes will panic because at first there is nothing in HighScore.

Great discussion folks! 😄

Fixed by https://github.com/frederickjjoubert/bevy-ball-game/pull/8


ci: support multiple os

Signed-off-by: Jason Liu<EMAIL_ADDRESS>Ⅰ. Describe what this PR does
support both MacOS and Ubuntu in the CI workflow.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews

Codecov Report

Merging #162 (3236891) into main (49dfdbe) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 3236891 differs from pull request most recent head 8ac941a. Consider uploading reports for the commit 8ac941a to get more accurate results

@@           Coverage Diff           @@
##             main     #162   +/-   ##
=======================================
  Coverage   57.05%   57.05%
=======================================
  Files          87       87
  Lines        7989     7989
=======================================
  Hits         4558     4558
  Misses       3029     3029
  Partials      402      402

Flag
Coverage Δ

unittests
57.05% <ø> (ø)

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

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 49dfdbe...8ac941a. Read the comment docs.

It might be too slow to run on Mac, can it be made optional？

/hold cancel

It might be too slow to run on Mac, can it be made optional？

@hormes I've tried almost every possible solution but without success. Let's merge this PR firtst, and I'll open an issue in here.

/lgtm
/approve