Merges Master to Live. See commits for details.

Docs Build status updates of commit b16e050:
:clock10: Full build: the average full build time is 12 min(s) 27 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit b16e050:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/advanced-threat-protection/Get-AtpPolicyForO365.md
:white_check_mark:Succeeded
View (exchange-ps)

skype/skype-ps/skype/Get-CsTeamsComplianceRecordingApplication.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsTeamsComplianceRecordingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsComplianceRecordingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsComplianceRecordingApplication.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsComplianceRecordingPairedApplication.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsComplianceRecordingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsComplianceRecordingApplication.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsComplianceRecordingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlineDirectoryUser.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsComplianceRecordingApplication.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsComplianceRecordingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/skype.md
:white_check_mark:Succeeded
View (skype-ps)

teams/teams-ps/teams/Get-Team.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-Team.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 0829ce4:
:clock10: Full build: the average full build time is 12 min(s) 27 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 0829ce4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/advanced-threat-protection/Get-AtpPolicyForO365.md
:white_check_mark:Succeeded
View (exchange-ps)

skype/skype-ps/skype/Get-CsTeamsComplianceRecordingApplication.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsTeamsComplianceRecordingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsComplianceRecordingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsComplianceRecordingApplication.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsComplianceRecordingPairedApplication.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsComplianceRecordingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsComplianceRecordingApplication.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsComplianceRecordingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlineDirectoryUser.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsComplianceRecordingApplication.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsComplianceRecordingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/skype.md
:white_check_mark:Succeeded
View (skype-ps)

teams/teams-ps/teams/Get-Team.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-Team.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update calculator.js

Implemented _check function in each of the operation.

Delete me and write your Pull Request message here!

Have now done the right thing? Check then get back to me.


Enable passing String and custom struct boxed slices across ABI and implement TryFrom for custom structs

Closes:
https://github.com/rustwasm/wasm-bindgen/issues/111
https://github.com/rustwasm/wasm-bindgen/issues/2452
https://github.com/rustwasm/wasm-bindgen/issues/168
https://github.com/rustwasm/wasm-bindgen/issues/2231
The vectors are converted across the ABI by converting their elements to/from JsValues.
It was necessary to change the way relevant traits (e.g. WasmDescribe, IntoWasmAbi etc.) are implemented. It's impossible to implement these for Box<[#name]> in codegen.rs because implementing traits on generic types is only allowed in the crate in which the trait is defined. Naively adding a blanket implementation on the wasm-bindgen side doesn't work either because it conflicts with the implementation for JsObjects. The solution was to create traits like VectorIntoWasmAbi etc. that are implemented on the concrete type and contain the implementation for IntoWasmAbi etc. for vectors of that type. JsObjects are blanket implemented as before, and struct types are implemented in codegen.rs. Due to the way these traits are defined, Rust requires implementing types to be Sized, so they can't be used for the String implementations.
Converting structs from JsValues was accomplished by adding an unwrap function to the generated JavaScript class, and calling that from Rust.

Thanks for the PR, but judging from the size here, the description, and the title, this seems like a significant change. Can you describe the change in some more detail at a high level and explain what's in the patch internally?
Additionally I think it'd probably be good to ensure CI is green.

@alexcrichton No worries Alex, and thank you for taking a look.
My motivation for writing this PR was frustration with wasm-bindgen's limited ability to pass vector types (Vec<T> and Box<[T]>) back and forth between Rust and JS. Previously, it was only possible to do this where T is a primitive type, a JsValue, or a type implementing JsCast (which is for types representing a value in JavaScript, where it's possible to cast them to a JsValue for free). The ability to pass vectors of other types such as String (https://github.com/rustwasm/wasm-bindgen/issues/168) and especially exported structs (https://github.com/rustwasm/wasm-bindgen/issues/111) has been a popular request. So far people have had to use some unfortunate workarounds to do this.
There are a few traits that are necessary to implement to allow for bidirectional conversion of a type between Rust and JS:

WasmDescribe, which serialises the type (not a value but the type itself) so that the CLI tool can generate JS code to correctly handle the conversion.
IntoWasmAbi, which converts a value of the type into a form that can be passed directly to JS. For anything other than primitive types this is essentially a pointer and a length, so the JS side can read the data itself from the WASM memory.
FromWasmAbi, which is the inverse of IntoWasmAbi. This takes the simple values that can be passed directly from JS and constructs a value of the type.

These traits are blanket implemented for Vec<T> wherever they are implemented for Box<[T]>.
The basis of this PR is the use of the existing implementations of these traits for Box<[JsValue]> for other types, by converting these types to and from JsValues. For a type T: Into<JsValue> + TryFrom<JsValue> we can implement IntoWasmAbi for Box<[T]> by mapping it to convert each value to a JsValue using into(), and then convert the resulting Box<[JsValue]> as normal. Similarly FromWasmAbi can be implemented by converting the given ABI values to a Box<[JsValue]> and then converting it back to Box<[T]> using try_from() in a map. My implementation panics if any element's conversion fails. I figured this is acceptable based on the behaviour of other implementations of FromWasmAbi when the wrong type is passed which seems to just be undefined.
The JS side can just treat this the same way as any other JsValue vector, so the implementation of WasmDescribe for Box<[JsValue]> can be used.
The downside of this approach is that it involves a lot of calls between Rust and JS, which might be a performance bottleneck in some situations. At least it's no worse than the workarounds people are doing anyway. It can be optimised in future if anyone finds a more performant way of doing it.
A naive approach would be to implement these traits with a blanket implementation on Box<[T]> where T: Into<JsValue> + TryFrom<JsValue>, which I attempted but it didn't compile because it conflicts with the blanket implementations for implementors of JsObject. So I created another trait: JsValueVector, which has the blanket implementation. I wrote a macro js_value_vectors that generates concrete implementations of IntoWasmAbi etc. using the blanket implementation of JsValueVector for the given types. Currently the only thing calling this macro is String.
Implementing the needed traits for exported structs was a little more challenging.
Firstly, it's impossible to implement e.g. IntoWasmAbi for Box<[T]> from outside of the wasm-bindgen crate. This is because of the rule that traits can only be implemented on arbitrary types in the crate in which they are defined. I solved this problem by creating another set of traits: WasmDescribeVector, VectorIntoWasmAbi etc. that basically define the behaviour of WasmDescribe, IntoWasmAbi etc. respectively for Box<[T]> when they are defined on a concrete type T. I created blanket implementations so that implementing e.g. VectorIntoWasmAbi for T automatically implements IntoWasmAbi for Box<[T]>. I had to refactor out the blanket implementations for JsObject so that they implement my new traits since the original traits can only have one blanket implementation.
Secondly, there was no good way to recover an instance of an exported struct from a JsValue with which to implement the necessary TryFrom<JsValue> for JsValueVector to work. I added an __unwrap function to the JS wrapper for exported structs. This simply unwraps it to the underlying exported struct instance.
Could you or maybe @chinedufn advise me on https://github.com/rustwasm/wasm-bindgen/blob/main/crates/shared/src/schema_hash_approval.rs ? The comment reads:
// Whenever the lib.rs changes, the SCHEMA_FILE_HASH environment variable will change and the
// schema_version test below will fail.
// Proceed as follows:
//
// If the schema in this library has changed then:
//  1. Change this APPROVED_SCHEMA_FILE_HASH to the new hash.
//
// If the schema in this library has changed then:
//  1. Bump the version in `crates/shared/Cargo.toml`
//  2. Change the `SCHEMA_VERSION` in this library to this new Cargo.toml version

I think the top option might be supposed to say 'not changed'? Should version numbers be bumped in general in PRs for this project? I assumed this would be done on master when it's time for a new release.
Please let me know if anything needs to be clarified or if there are any amendments you would like.

Any follow-ups on this PR? Would be a useful feature to have when working with wasm-bindgen.

Hi! any follow-ups on this? this is a very nice/important feature that is missing in in bindgen, it would do great for this project for this to be reviewed

Thanks for the review @Liamolucko . I did this work last year because I wanted this feature for a project I was working on at the time. However, it's no longer a priority for me. I have other work to do and I don't forsee myself making time for this in the foreseeable future.
Please feel free to pick up where I left off. I had accepted, painfully, that this work had gone to waste, so I'm very grateful that you're rescuing it. Thank you.

Was replaced by https://github.com/rustwasm/wasm-bindgen/pull/3554.


[WIP] phase restricted generators

Currently just sampled for epoch processing

Getting an error when writing state to yaml file. Looks like it's having trouble writing an embedded object within state.  slot: 9 is the first field of state.latest_block_header.
Traceback (most recent call last):
  File "main.py", line 54, in <module>
    create_suite('voluntary_exit',    'mainnet', lambda: generate_from_tests(test_process_voluntary_exit, 'phase0')),
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/gen_base/gen_runner.py", line 111, in run_generator
    yaml.dump(suite, f)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/main.py", line 439, in dump
    return self.dump_all([data], stream, _kw, transform=transform)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/main.py", line 453, in dump_all
    self._context_manager.dump(data)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/main.py", line 801, in dump
    self._yaml.representer.represent(data)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/representer.py", line 84, in represent
    node = self.represent_data(data)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/representer.py", line 111, in represent_data
    node = self.yaml_representers[data_types[0]](self, data)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/representer.py", line 359, in represent_dict
    return self.represent_mapping(u'tag:yaml.org,2002:map', data)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/representer.py", line 1017, in represent_mapping
    node_value = self.represent_data(item_value)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/representer.py", line 111, in represent_data
    node = self.yaml_representers[data_types[0]](self, data)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/representer.py", line 349, in represent_list
    return self.represent_sequence(u'tag:yaml.org,2002:seq', data)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/representer.py", line 933, in represent_sequence
    node_item = self.represent_data(item)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/representer.py", line 111, in represent_data
    node = self.yaml_representers[data_types[0]](self, data)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/representer.py", line 359, in represent_dict
    return self.represent_mapping(u'tag:yaml.org,2002:map', data)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/representer.py", line 1017, in represent_mapping
    node_value = self.represent_data(item_value)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/representer.py", line 121, in represent_data
    node = self.yaml_representers[None](self, data)
  File "/Users/djrtwo/dev/ethereum/eth2.0-specs/test_generators/operations/venv/lib/python3.6/site-packages/ruamel/yaml/representer.py", line 392, in represent_undefined
    raise RepresenterError('cannot represent an object: %s' % (data,))
ruamel.yaml.representer.RepresenterError: cannot represent an object: slot: 9

Gotta switch gears for evening. This the last thing we need to do before v0.7.0 release

sorry, fixed typo :sweat_smile:

Ok, ran all generators, and it runs within ~16 minutes, and produces 400MB worth of yaml test vectors. However, I had excluded the mainnet attestation operation tests, as there are single test cases in there, that take over 12 minutes to run with the mainnet configuration. (tried, profiled, created call-graphs, compared ssz-implementations, but to no avail: the tests are just running insane amounts of hash-tree-root calls (incl recursive, in the tens of millions of calls....)
I recommend to comment out the test-generator line in operations/main.py to disable those super slow mainnet tests:
        # create_suite('attestation',       'mainnet', lambda: generate_from_tests(test_process_attestation, 'phase0')),

Instead, we can release without them, and re-enable when we have SSZ caching, instead of just a small zero-hash optimization. Or someone has to invest some serious time in changing those tests, while still keeping them compatible with the original test intentions.


Allow the SecondaryCursor value of sync'd cursors to match the Y-axis value of each sub-chart

Sync'd cursors that display across multiple charts currently correspond to the primaryCursor & secondaryCursor of the chart that's hovered over.

While the primaryCursor works as expected, ideally we'd have an option to set the secondaryCursor value to the Y-axis of each sub chart (independent of the Y-axis value of the chart that's hovered over).
Following this logic in the image above - the Y axis for chart #2, Series #1 should be 60 instead 90.
This could be achieved by allowing the secondaryCursor to be specified at the chart level via a reference to the global "activeSeriesIndex" and "activeDatumIndex" that are set by the hover-over criteria.
The custom styles code sandbox demonstrates a usecase around setting the activeSeriesIndex and activeDatumIndex via a the state var.

The other workaround: we could expand the logic around tooltips so on hover the corresponding tooltip shows up on each sub-chart.

Tutorial available here that outlines a potential workflow: https://swizec.com/blog/tooltips-and-state-across-various-d3-charts-in-a-react-dashboard

Due to a massive overhaul and rewrite of React Charts to TypeScript and a massively upgraded public API, this issue is being bulk closed for triage. The latest version can be tested via the react-charts@beta tag. Documentation is in the process of being upgraded, but thankfully, everything is fully typed now, so you can explore the API that way for now.
If, after testing or playing with the v3 beta, you believe your issue is still not addressed or relevant, feel free to open a new issue.


How to prevent popping-up xdg-open dialog from Ubuntu chrome while opening specific link?

Is there a way to dismiss the dialogue using python selenium or using some configuration file changes in chrome installation ?

So far as I know you need to add missing schema to xdg config.

Hi @vania-pooh I am using the chrome image which create by Selenoid, could I know how to add the missing schema?

@cjmme should use xdg-mime command so far as I know.


expose the Timeout exception to the wrapped computation

Implements basvandijk/unbounded-delays#5.

And yet another unbounded-delay, this time from my side ;). I like the name you suggested. I made a new pull request for the updated isTimeout branch, so I'll close this one.


Draw Interaction removeLastPoint not acting as expected

Describe the bug
When enabling the Draw interaction and calling the removeLastPoint function, the draw layer does not update.
To Reproduce
Steps to reproduce the behavior:

Add the Draw Interaction to the map with type: 'Polygon'
Draw a polygon and mid draw, call the removeLastPoint function
Observe that the polygon you were drawing does not update
Call removeLastPoint again and find that the line segment that was supposed to be removed in the 1st call is now removed.
Click on the map again to resume drawing and see that the segment of call 2 is now removed and drawing has commenced as expected

Expected behavior
On removeLastPoint call, update the map with the original geometry with the last drawn segment removed
Relevant Code
https://github.com/openlayers/openlayers/blob/v6.3.1/src/ol/interaction/Draw.js#L817

I encountered this problem too. This seems to be an issue with touch use. When used with mouse, the last coordinate in "sketchCoords_" is continuously updated when the mouse is moved. With touch devices, the last coordinate is not updated, so the removeLastPoint operation in fact removes the second last coordinate, but for the user it looks like nothing is done as the last pointer coordinate is the same and the drawing does not seem to change. However, if you now click to another point, this last point is behaving correctly.
Possible workaround would be to fake a pointer move event to the last accepted coordinate after the removeLastPoint operation, so that for example in polygon draw the closing line would be updated to the last coordinate too. With mouse the next movement of mouse would update this anyway.
Another possibility would be to delete two last coordinates in case a touch device is used. Maybe this could be detected by comparing the two last coordinates in sketchCoords_ as they should be equal if a touch device is used. I am not sure if this would update the sketch-lines, though.

This is still an issue and shouldn't be closed if it's still a problem

This is still an issue and shouldn't be closed if it's still a problem

This is still an issue and shouldn't be closed if it's still a problem

Did you try v6.5.0? What exactly is the remaining issue you are seeing?

Did you try v6.5.0? What exactly is the remaining issue you are seeing?

This is still somehow broken in v6.6.0.
The drawn geometry does update, but the last point is altered wrong until you move the mouse. Then the geometry is correct again.
I traced it down to this line: https://github.com/openlayers/openlayers/commit/0bd04eafe015e61e1df28b1c3c7d52239c9a57ca#diff-91329c8a038835b6a5e7bae5e13f15e7fa5499b3414f0e094a5bfe347efc5a32R912
And the same for polygons. I guess it was an attempt to fix the removal of points with touch.
I made a simple example here: https://8c2mi.csb.app/, right click removes the last point

The position of the draw vertex is intentional the way it is now. To make it visually more apparent what was changed.

I think this problematic if I remove the second point of a line or polygon. If I have a style that does not draw single points and remove the second point, the whole feature disappears until I move the mouse. This was seen as error by the users.

The cleanest solution is probably to render the sketch point in some way, but with a modified condition you could make the sketch point appear at the last clicked location:
condition: (event) => {
      if (
        event.originalEvent.pointerType === "mouse" &&
        event.originalEvent.button === 2
      ) {
        draw.removeLastPoint();
        const moveEvent = new MapBrowserEvent("pointermove", map, event.originalEvent);
        draw.handleEvent(moveEvent);
        draw.handleEvent(moveEvent);
        return false;
      }
      return true;
    }


The slider ball blinks when user drag the slider ball left right in find menu

SEVERITY:  Major
MODULE:  Bubble chart
Platform: MAC (10.11.1) / Safari 9.0
RELEASE: v0.13.5
STEPS TO REPRODUCE:

Navigate to the URL : http://tools-stage.gapminderdev.org/tools/bubbles
Bubble Map Chart will be loaded.
Click any country check box in find
Now drag slider right left under the name of countries

ACTUAL RESULTS:
The slider ball blinks when user drag the slider right left
EXPECTED RESULTS:
The slider ball should not blink when user drag the slider right left
SCREENSHOT:

Can not reproduce. Retest please.


crypto\aes\aesni-sha256-x86_64.asm:4396: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4396: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4400: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4400: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4407: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4407: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4410: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4410: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4414: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4414: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4421: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4421: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4424: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4424: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4428: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4428: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4435: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4435: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4438: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4438: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4442: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4442: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4449: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4449: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4452: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4452: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4458: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4458: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4460: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4460: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4463: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4463: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4465: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4465: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4467: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4469: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4469: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4476: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4476: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4478: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4478: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4480: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4480: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4482: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4482: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4486: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4486: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4490: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4490: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4494: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4494: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4498: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4498: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4500: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4500: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4502: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4502: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4506: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4506: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4510: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4510: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4512: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4512: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4516: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4516: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4518: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4518: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4521: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4521: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4523: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4523: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4525: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4527: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4527: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4534: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4534: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4535: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4544: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4544: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4545: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4545: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4546: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4546: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4547: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4547: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4548: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4548: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4549: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4549: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4550: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4550: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4551: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4551: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4552: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4552: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4553: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4553: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4554: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4554: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4555: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4555: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4556: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4556: error: comma, colon, decorator or end of line expected after operand
crypto\aes\aesni-sha256-x86_64.asm:4557: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4558: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4559: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4560: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4563: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4564: error: label `aesni_cbc_sha256_enc_shaext' inconsistently redefined
crypto\aes\aesni-sha256-x86_64.asm:4173: info: label `aesni_cbc_sha256_enc_shaext' originally defined here
crypto\aes\aesni-sha256-x86_64.asm:4564: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4568: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4580: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4581: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4583: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4584: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4586: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4587: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4591: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4593: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4594: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4597: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4601: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4602: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4605: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4607: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4608: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4614: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4616: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4618: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4619: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4620: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4621: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4622: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4623: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4624: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4625: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4626: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4627: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4628: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4629: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4631: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4632: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4636: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4637: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4638: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4639: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4640: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4641: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4643: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4650: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4651: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4652: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4653: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4654: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4655: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4656: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4657: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4658: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4659: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4660: warning: `PTR' is not a NASM keyword [-w+ptr]
crypto\aes\aesni-sha256-x86_64.asm:4674: error: label `se_handler' inconsistently redefined
crypto\aes\aesni-sha256-x86_64.asm:4568: info: label `se_handler' originally defined here
crypto\aes\aesni-sha256-x86_64.asm:4674: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4676: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4691: error: label `se_handler.pdata' inconsistently redefined
crypto\aes\aesni-sha256-x86_64.asm:4677: info: label `se_handler.pdata' originally defined here
crypto\aes\aesni-sha256-x86_64.asm:4691: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4694: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4699: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4703: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4707: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4712: error: parser: instruction expected
crypto\aes\aesni-sha256-x86_64.asm:4713: warning: label alone on a line without a colon might be in error [-w+label-orphan]
NMAKE : fatal error U1077: '"C:\vcpkg\downloads\tools\nasm\nasm-2.16.01\nasm.exe"  -Ox -f win64 -DNEAR -g -o crypto\aes\libcrypto-lib-aesni-sha256-x86_64.obj "crypto\aes\aesni-sha256-x86_64.asm"' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.35.32215\bin\Hostx64\x64\nmake.exe" /LU                 _build_libs' : return code '0x2'
Stop.

Maybe duplicate of #24832.

1>    See logs for more information:
1>      C:\vcpkg\buildtrees\openssl\install-x64-windows-static-dbg-nmake-out.log
1>      C:\vcpkg\buildtrees\openssl\install-x64-windows-static-dbg-nmake-err.log

Corrected: Maybe duplicate of #30645.

1>    See logs for more information:
1>      C:\vcpkg\buildtrees\openssl\install-x64-windows-static-dbg-nmake-out.log
1>      C:\vcpkg\buildtrees\openssl\install-x64-windows-static-dbg-nmake-err.log

Closed as duplicate of https://github.com/microsoft/vcpkg/issues/30645.


Add Part12Step11Controller and Associated Unit Testing

Update the project to include a new test for DM58 messaging.  Implementation is defined below:

Due to the renumbering required to accomadate the new step covered in #90 this is new part12 step 12


Support aws-cdk version 2.165.0 or newer

Describe the bug
The @aws-quickstart/eks-blueprints package currently requires aws-cdk version 2.162.1. However, our project is using aws-cdk version 2.165.0, which causes a dependency conflict.
Expected Behavior
The @aws-quickstart/eks-blueprints package should support the latest version of aws-cdk.
Current Behavior
The installation fails with the following error:
npm error Could not resolve dependency:
npm error peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm error node_modules/@aws-quickstart/eks-blueprints
npm error<EMAIL_ADDRESS>from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
Reproduction Steps

Set aws-cdk version to 2.165.0 in package.json.
Install dependencies using npm install.
See the dependency conflict error.

Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.165.0
EKS Blueprints Version
No response
Node.js Version
v23.4.0
Environment details (OS name and version, etc.)
Mac os
Other information
If not will be updated soon. Can I possibly get an ETA?

@yaakov-khodorkovski-lendbuzz we are planning to create a patch release with the latest CDK version.
However, it should not be an issue for you to move to the latest version of the CDK now. We pinned the version to the one we tested against using peerDependencies.  Please see this doc: https://aws-quickstart.github.io/cdk-eks-blueprints/getting-started/#configure-your-project.
here is an extract that may be relevant for you:

Note: after the initial installation, upgrading the version of CDK to an incompatible higher/lower version will produce a warning, but will succeed. For community support (submitting GitHub issues) please make sure you have a matching version configured.

This will be the preferred method.
You can also use an npm override mechanism similar to the one we used here: https://github.com/aws-samples/cdk-eks-blueprints-patterns/blob/main/package.json#L50.
In both cases you can run npm install -f to force the version that is different from the one we tested against.

Okay , Thank you for your fast response 🙏


Impossible to specify destination specific option

Hi,
The client library is very well made, but it's currently impossible to add destinations specific option.
In my particular case, I want to be able to add or remove a Tag when using the Identify call and Vero destination. In the documentation it says to pass an object called tags in the Vero integration object for example:
analytics.identify('324LKJF', {
    email<EMAIL_ADDRESS>}, {
    integrations: {
        Vero: {
            tags: {
                id: '235FAG', // This is optional! If not defined, we default to the event's userId (ie: 324LKJF)
                action: 'add',
                values: ['warriors', 'giants', 'niners']
            }
        }
    }
})

But the .NET library only support setting an individual integration to true or false via the SetIntegration("Vero", true) method.
It would be nice to not have to call the HTTP API endpoint in order to succesfully pass the tags.
Thanks

Closed by #80


Permits Table Schema

Permits
Holds the permit details associated with some credits.

Field
Type
Description
Example Value

id
int8
Unique identifier for the permit entry.
101

created
timestamptz
Timestamp when the permit was created.
2023-09-15T11:20:23.004Z

updated
timestamptz
Timestamp when the permit was last updated.
2023-09-15T11:22:40.050Z

network
smallserial
Network identifier.
100

token
CHAR(42)
Token associated with the permit.
0xe92E133E0b41519A2Ce9Dd4D7945Fa863463a97e

amount
int8
Amount associated with the token for the permit.
150000000000000000000

nonce
int8
Nonce associated with the permit.
8802044552...

deadline
int8
Deadline associated with the permit.
115792089237316195423570985008687907853269984665640564039457584007913129640000

beneficiary
CHAR(42)
Destination address for the permit's transfer.
0x4008FE2190c8F3E18098aeB4A40bb8eC149a342d

owner
CHAR(42)
Owner of the credit.
0xf88da4592C791213e52840d120E7E0B38B818bD2

signature
CHAR(132)
Signature associated with the credit.
0xecb65ed54b2ee7a0ffad5aff8314eef684f80dcb78c18b4ea9f588e083a0fa114546d466befa23cb81d040957615b5b1ad08966b64c5778802e5e115cdcd39241b

/start

@pavlovcik deadline is out of range for type int8

/ask what data type should we use

Oh I just realized something. This is a config error I think.

/ask what data type should we use

@pavlovcik deadline is out of range for type int8
I am trying to move existing data from permit to the new table, so the number is from one of the permit data that is apparently out of range for it

Chatgpt also recommended timestamptz but unsure if that's valid. I have to check in a bit I'm a bit occupied at the moment

This is the deadline<PHONE_NUMBER>37316195423570985008687907853269984665640564039457584007913129639935

Chatgpt also recommended timestamptz but unsure if that's valid. I have to check in a bit I'm a bit occupied at the moment

I'd do the research and make use of what works best

Had to make deadline, nonce and amount numeric, bigint or int8 did not cut it

Had to make deadline, nonce and amount numeric, bigint or int8 did not cut it

This means i'd have to change the Debit amount to numeric too, int8 supports up to 1e18 but no permit amount is just going to be 1 ETH or equivalent.
So it goes past 18 and int8 returns an out of range error

Another idea I might add to a new scope, but we can save so much on memory if we have a foreign key to recognized partner wallet address, and recognized token addresses.
bounty hunter address should be a foreign key also.

Still in review

Going to test the new implementations


Fix IO Re-run

Problem
The IO monad implementation could re-run actions under certain combinations of TransformWith. See the below example for a fairly minimal reproducible case:
runIO(
  quote(query[Person].insert(_.name -> lift(name)).returning(_.id)) // will execute twice
).flatMap { id =>
   if (id < 0) {
     IO.failed(new NegativeIdException("wierd id: " + id))
   } else {
    IO.successful(Some(id))
   }
}.recoverWith {
  case t: SomeNotMatchedExceptionType => // not matched exception type
    IO.successful(None)
}

This was enough to trigger the insert to run twice. Thankfully, in our case we had a unique constraint exception so this didn't actually produce multiple inserts. Other users might not be so lucky.
The first commit in this PR demonstrates the failing case, the second commit contains the fix.
Solution
The flatMap and recoverWith IO transformations should not return this, but rather an instance of FromTry when the success / failure cases don't actually execute the provided transform function.
I changed a few unrelated IO transformations to re-use scala.util.{Success, Failure} instances instead of re-creating them.
Checklist

[x] Unit test all changes
[x] Update README.md if applicable
[ ] Squash commits that aren't meaningful changes
[x] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

what a terrible bug, thanks for the fix! Yes, I'll make sure it's included in the release.

I'm guessing that the failures in quill-orientdb aren't related to changes I've made here since master also has failures for the last few days. Let me know if there's anything I need to do to get this PR mergeable for the 2.5.0 release.

Updated PR to satisfy codacity and use AtomicInteger instead of var. I guess in theory it might matter to async contexts.

@pettyjamesm yeah, travis ci doesn't seem to be a good solution for a project of the this size. We've tried a few things but nothing seems to make it stable. We should probably look for sponsorship so we can have a proper CI. Meanwhile, I've deleted all caches and restarted the failed jobs, let's see if that fixes the build

Hooray! That seems to have worked. Feel free to squash two commits down when you merge this PR.

awesome!


Binary search on retrieval

Since keys are added in byte order, a binary search would work, and it'd be insanely efficient (O(log n) as opposed to O(n)).
Is there already a function for this that I'm missing, and if not, is there a chance of this being implemented?

@libeclipse The Cursor is used to lookup data and it uses a binary search: https://github.com/boltdb/bolt/blob/master/cursor.go#L252

@benbjohnson Sorry if this is obvious, but I'm not sure how I'd use that method. The closest documented thing that I can find is Seek(), but its behaviour when it doesn't find a key isn't appropriate for my use.

@benbjohnson Not sure if I'm understanding this correctly.
So a binary search searches an ordered list for a distinct value, right? So what the Seek() function should do is take a single byte slice as an input, perform a binary search on the contents, and return that entry. If it cannot locate the input key, then it should return a nil.
If it does do that, I think it should be re-worded as the current docs are misleading. However, if it doesn't do that and instead, when it cannot find the input key it returns the next key in the database, the documentation is pretty accurate and I think that the Seek() function is not useful for my purpose. In this case, could you recommend a method to to the former aforementioned task, i.e. a standard binary search.


[BEAM-6102] Update Dataflow worker container to beam-master-20181128

R: @angoenka

Run Java PostCommit

LGTM
Please self merge after the test pass.


links to minified js on readme are broken

Thanks @dylanjw - I'll patch this up tonight.

Ah rats. Sorry, will get to this today.

Fixed.


Cannot Setting proxy

Hei there,
I'm try-ing to use your apps, but at my computer the internet is using proxy.
that make the apps doesn't work. can you add setting proxy fitur?
Thank you

Proxies are taken into account in the source code. As far as I know the application uses the system proxy (if any). Maybe if you gives us some more details we can have a look


Received http2 header with status: 404

What version of OpenTelemetry are you using? 0.17.0
What version of Node are you using? v14.15.5
Please provide the code you used to setup the OpenTelemetry SDK
const traceCollectorOptions = {
  serviceName: 'basic-metric-service',
  url: 'https://domain.com:443'
}
const traceExporter = new CollectorTraceExporter(traceCollectorOptions)
const traceprovider = new BasicTracerProvider({
  exporter: traceExporter,
  interval: 5000
});
traceprovider.addSpanProcessor(new SimpleSpanProcessor(traceExporter));
traceprovider.register();

What did you do?
I had a ton of problems getting grpc to work though traefik, for for some reason it would only work when using a dedicated port, until I tried adding port's to the url. If using http://domain.com:80 instead of http://domain.com then things worked. I just don't see why there is a need to add port ? But grpc will only work if port is included for me. So I try using https://domain.com or https://domain.com:443 but I still get "Received http2 header with status: 404".
I assumed https was not supported, so I turned to my C# code, and here everything is reverse?!?
If I set Endpoint on the otlpOptions to http://domain.com or http://domain.com:80 I get "Received http2 header with status: 404" but if I use https://domain.com or https://domain.com:443 it works.
So clearly https, is working, it's just not working for the nodejs library. (no idea why http is not working from C# even with
AppContext.SetSwitch("System.Net.Http.SocketsHttpHandler.Http2UnencryptedSupport", true); set )
Since I would prefer to use https, I'm creating the issue for the nodejs client about how to make it work for https, if that is possible ?
What did you expect to see?
No errors when using https
What did you see instead?
Received http2 header with status: 404

I have copy and pasted a bit in the two open telemetry samples.
In this oteltest repo I added a simple nodejs example that sends a few spans, and a C# console app that does the same. in Program.cs you can swap between using http or https
and in tracing.js you can also swap between http and https
I added a few valid certificates in acme.json that the default docker-compose / traefik is using, if you want to create your own, I left the dns01 config for setting up traefik to request lets encrypt certificates using DNS hosted at google.
As you can see, the C# example has no issue sending spans using https toward https://otel.localhost.openiap.io but the nodejs version only works using http://otel.localhost.openiap.io:80 ( and not http://otel.localhost.openiap.io witch I still think is weird )

Any progress on this ? Do you need me to update the certificates in the sample ?
I just tested with<EMAIL_ADDRESS>and the error has changed to
{"stack":"Error: 13 INTERNAL: Received RST_STREAM with code 0\n    at Object.callErrorFromStatus (C:\\code\\openflow\\node_modules\\@grpc\\grpc-js\\build\\src\\call.js:31:26)\n    at Object.onReceiveStatus (C:\\code\\openflow\\node_modules\\@grpc\\grpc-js\\build\\src\\client.js:179:52)\n    at Object.onReceiveStatus (C:\\code\\openflow\\node_modules\\@grpc\\grpc-js\\build\\src\\client-interceptors.js:336:141)\n    at Object.onReceiveStatus (C:\\code\\openflow\\node_modules\\@grpc\\grpc-js\\build\\src\\client-interceptors.js:299:181)\n    at C:\\code\\openflow\\node_modules\\@grpc\\grpc-js\\build\\src\\call-stream.js:145:78\n    at processTicksAndRejections (internal/process/task_queues.js:75:11)","message":"13 INTERNAL: Received RST_STREAM with code 0","code":"13","details":"Received RST_STREAM with code 0","metadata":"[object Object]","name":"Error"}

Not sure if anyone is reading this, but tried updating all packages from 0.19.0 to 0.21.0
Now, it does not even work with http anymore ... Same error as above ...
Am I using the product wrong? Are we not supposed to connct the client library to and instance of opentelemetry-collector ? If not, then what are suppose to be use to collect the metrics and spans ?

I'll look into your sample code today

I have update the repo with a fresh certificate, since the old one had expired.

Not sure if related, but I just saw the same error when I didn't configure the otlp-grpc exporter with secure credentials:
const grpc = require("@grpc/grpc-js");

provider.addSpanProcessor(
  new SimpleSpanProcessor(
    new CollectorTraceExporter({
      url: '<secure-endpoint>',
      credentials: grpc.credentials.createSsl(), // I was missing this line, which defaults to grpc.credentials.createInsecure() if unspecified
      metadata
    })
  )
);

Port handling was updated in an exporter rewrite a while ago and we just didn't close this issue at the time. This should be fixed.


Fix an issue were a token refresh might break dev session start

WHY are these changes introduced?
There is was a race condition were a token refresh triggered while dev session create was in progress, would stop the creation process and stop dev from working.

WHAT is this pull request doing?
Remove some unnecessary checks, we don't need to validate if the session is "initializing" or not. That is preventing the creation after the refresh to work.

How to test your changes?

Post-release steps

Measuring impact
How do we know this change was effective? Please choose one:

[ ] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[ ] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[ ] I've considered possible documentation changes

/snapit


[bug] drag-region doesn't work correctly on windows touchscreen device

Describe the bug
I can drag with mouse, but not touchscreen
Reproduction

npx create-tauri-app, choose react, and typescript
in tauri.conf.json, change the tauri.windows:

"windows": [
      {
        "decorations": false,
        "fullscreen": false,
        "height": 300,
        "resizable": true,
        "title": "",
        "width": 200,
        "alwaysOnTop": true
      }
    ]

App.tsx:

import React from 'react';

import './App.css';

function App() {

  return (
    <div className="App">
      <header className="App-header">
        <div data-tauri-drag-region style={{
          backgroundColor: "#111",
          padding: 20
        }}>
          Floating Hotkey
        </div>

      </header>
    </div>
  );
}

export default App;

App.css

.App {
  text-align: center;
}

.App-header {
  background-color: #282c34;
  min-height: 100vh;
  display: flex;
  flex-direction: column;
  align-items: stretch;
  justify-content: start;
  font-size: calc(10px + 2vmin);
  color: white;
}

should get something like this:
https://user-images.githubusercontent.com/36293056/180617696-e115d8dd-e7b6-493a-91e8-4cf81da61ac6.mp4
Expected behavior
touchscreen should behave same as mouse drag
Platform and versions
npm run tauri info

><EMAIL_ADDRESS>tauri
> tauri "info"

Environment
  › OS: Windows 10.0.22000 X64
  › Webview2: 103.0.1264.62
  › MSVC:
      - Visual Studio Community 2019
  › Node.js: 16.6.0
  › npm: 7.19.1
  › pnpm: Not installed!
  › yarn: 1.22.17
  › rustup: 1.24.3
  › rustc: 1.61.0
  › cargo: 1.61.0
  › Rust toolchain: stable-x86_64-pc-windows-msvc

Packages
  › @tauri-apps/cli [NPM]: 1.0.5
  › @tauri-apps/api [NPM]: 1.0.2
  › tauri [RUST]: 1.0.5,
  › tauri-build [RUST]: 1.0.4,
  › tao [RUST]: 0.12.2,
  › wry [RUST]: 0.19.0,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../build
  › devPath: http://localhost:3000/
  › framework: React

App directory structure
  ├─ .git
  ├─ node_modules
  ├─ public
  ├─ src
  └─ src-tauri

Stack trace
Compiling...
Compiled with warnings.

Warning
(11:3) autoprefixer: start value has mixed support, consider using flex-start instead

Search for the keywords to learn more about each warning.
To ignore, add // eslint-disable-next-line to the line before.

WARNING in ./src/App.css (./node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[1]!./node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[1].oneOf[5].use[2]!./node_modules/source-map-loader/dist/cjs.js!./src/App.css)
Module Warning (from ./node_modules/postcss-loader/dist/cjs.js):
Warning

(11:3) autoprefixer: start value has mixed support, consider using flex-start instead

webpack compiled with 1 warning
No issues found.

Additional context
No response

anything I can do to solve the issue?

you could try to replicate data-tauri-drag-region but with touchstart event
 document.addEventListener('touchstart', (e) => {
    if (e.target.hasAttribute('data-tauri-drag-region')) {
      e.preventDefault()
      appWindow.startDragging();
    }
  })

@deepseapenguin can you check if the above solution works? appWindow comes from import { appWindow } from '@tauri-apps/api/window'.

@lucasfernog hi I tried that code, but I get an error: Property 'hasAttribute' does not exist on type 'EventTarget'.

that's weird, could you try executing the above snippet in the dev console?

@amrbashir I pasted the code in dev console, and when I try to drag it with touch, I got alot of this error

I don't know why are u getting this error tbh but we it doesn't matter now, since we confirmed that we need to first add support for this in upstream.

/upstream tauri-apps/tao

Getting the same issue but its not scrolling like in the video. It just doesn't seem to pay attention to the event but the correct element goes darker with the touchscreen touch.

Encountered the same problem, is there a solution now?

This issue is caused by the elastic oversrcool of webview2, can it be fixed?

Is there any solution for this issue or not yet?

The problem is still not solved, it is due to the webview2 features caused by ElasticOverscroll, in the edge browser to disable the elastic features can be eliminated, but in the windows touch device tauri still exists in the problem

How is this going now?

https://github.com/MicrosoftEdge/WebView2Feedback/issues/2243#issuecomment-1448819425

This solution allows to enable drag region feature to support touch screens (inherits @njfewr solution) and exclude some items from drag region (follows roadmap proposal #6362), and it disables elastic overscroll:
--enable-features=msWebView2EnableDraggableRegions --disable-features=ElasticOverscroll to tauri.conf.json > .tauri.windows.additionalBrowserArgs
[data-tauri-drag-region] {
	-webkit-app-region: drag;
}

[data-tauri-drag-region-exclude] {
	-webkit-app-region: no-drag;
}

do this pass your test?


[BUG] Runtime error Demo version .

There is an error on the demo version.
You can check from this image:

Encountered the same problem today.

Thanks @xuhaoteoh and @tanersekmen for reporting this issue. Currently both (@GirishPatel and @lalitpagaria) the maintainers are busy with something. Would you like to work on fixing it, we will guide you.

@lalitpagaria thank you for your message :)

@xuhaoteoh and @tanersekmen please check now as we have fixed the issue with HF space obsei app.

Hello Lalit, when I checked the Obsei app, there was no problem. Thank you so much for your interest.


fix forge divan armor

Divan Boots had the wrong id in constants>forge.js
This PR:

Fixes the divan armor id for all 4 pieces
For easier future debugging, it prints in the browser console an error with the item id of the unknown forge item

Can be tested here for the next 13h: http://localhost:32464/stats/kilarox/Cucumber#Skills


Consider a larger sized inputs and outputs arrays for the fungible tokens

The underlying circuit library supports arbitrary number of inputs and outputs, but the top-level circuit must have a fixed size. The fixed size is due to the fact that a ZKP circuit design must not have different steps of computation dependent on the input values. Having variable sized arrays is not possible as a result, because that would cause the circuit runtime to perform different computations dependent on the number of elements in the arrays.
At the moment all top level circuits (in the /zkp/circuits folder) for fungible tokens use 2-sized arrays for both inputs and outputs. Either array can have a 0-valued UTXO so that transactions with either single input or single output can be supported.
With the above, the following combinations of transactions can be supported:

2 inputs, 2 outputs
1 input, 2 outputs (the 2nd element in the inputs array is set to 0)
2 inputs, 1 output (the 2nd element in the outputs array is set to 0)
1 input, 1 output (2nd element in the inputs and outputs array are set to 0)

If we want to support larger sized inputs and outputs, we need the following layers to be updated:

top level circuits, plus the corresponding proving keys, verification keys (optional if verification is only performed by the Solidity verifier code) and the solidity verifier
solidity tokens implementations

Having a larger sized inputs and outputs means that, when not all input elements are used, meaning they are set to 0, all computations are still carried out as if they were non-zero elements, yet the results are not compared with the public inputs. This effectively multiplies the cost of the proof generation, although verification time is still constant thanks to SNARK.
The most efficient way from the runtime point of view is having the exact sized inputs. However this means for every circuit, we need many copies of derived artifacts: verifier contracts, unit tests, etc. Maintenance will be a big headache.

One proposal is having a small number of sizes to cover the majority of the use cases:

2-sized inputs: this probably covers 80% of the cases
10-sized inputs: this is much more expensive to use, in terms of proof generation. this size can be made even larger, since it's only used in rare occasions anyway


Added method to boot user into live chat

Can this be merged or a development version be pushed to npm so i can try this out?

Yes, I have published the new version on npm. You can install and use it now @AyoCodess


Ability to set/force Aspect Ratio per feed

I have some feeds that happen to be 4:3 but when using Cumulus TV, it forces these to be widescreen.  Problem is everyone looks like they have gained weight.  Would be great if in the edit channel screen, and in the json file there was a way to be able to force a certain channel to show as 4:3 with black bars either side or 16:9.  Maybe have a few other aspect ratios as well for good measure.
In the Settings for the app itself, one could change the colour of the black bars to grey or white.
This change may be one that requires changes to ChannelSurfer if this is possible.

Yeah I know it's an issue. I'm not sure how to solve it at the moment.
There's probably a way to do this automatically, but for now it's forced to
16:9.
On Fri, Mar 4, 2016, 8:50 PM Alan Cramer<EMAIL_ADDRESS>wrote:

I have some feeds that happen to be 4:3 but when using Cumulus TV, it
forces these to be widescreen. Problem is everyone looks like they have
gained weight. Would be great if in the edit channel screen, and in the
json file there was a way to be able to force a certain channel to show as
4:3 with black bars either side or 16:9. Maybe have a few other aspect
ratios as well for good measure.
In the Settings for the app itself, one could change the colour of the
black bars to grey or white.
This change may be one that requires changes to ChannelSurfer if this is
possible.
—
Reply to this email directly or view it on GitHub
https://github.com/Fleker/CumulusTV/issues/108.

That's why there should be a way within each channel to force an aspect ratio.  Even if this was implemented on the backend only, that you can add the setting within the JSON instead of needing to build a GUI for it.
{
"number": "1337", //Channel Number
"name": "Aquarium", //Channel Title
"logo": "logo.jpg", //Channel Logo
"url":"stream.m3u8", //Channel stream or website url
"splashscreen":"" //Optional splashscreen instead of default one
"aspect": "4:3" //Sets Aspect Ratio
"genres":"NEWS,MUSIC" //Comma separated array of channel genres
}

I know it could be set manually as a last resort, having the video player
know the correct ratio without extra work would be ideal.
On Mar 19, 2016 3:00 AM, "Alan Cramer"<EMAIL_ADDRESS>wrote:

That's why there should be a way within each channel to force an aspect
ratio. Even if this was implemented on the backend only, that you can add
the setting within the JSON instead of needing to build a GUI for it.
{
"number": "1337", //Channel Number
"name": "Aquarium", //Channel Title
"logo": "logo.jpg", //Channel Logo
"url":"stream.m3u8", //Channel stream or website url
"splashscreen":"" //Optional splashscreen instead of default one
"aspect": "4:3" //Sets Aspect Ratio
"genres":"NEWS,MUSIC" //Comma separated array of channel genres
}
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/Fleker/CumulusTV/issues/108#issuecomment-198649384

I should probably remove the forced aspect ratio and let the player do what makes sense.

If that option exists.... Otherwise implementing something within the json
for each channel would work also. I believe aspect ratio is part of the
xmltv spec.
On 17 Aug. 2016 5:56 am, "Nick"<EMAIL_ADDRESS>wrote:

I should probably remove the forced aspect ratio and let the player do
what makes sense.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Fleker/CumulusTV/issues/108#issuecomment-240226969,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADIfytujxY6J033gli7zoS563o8MB_Q3ks5qghzfgaJpZM4Hp4AC
.

I've tested some of my streams with TIF, and found it correctly identifies the stream as 4:3 or 16:9.  Assuming this love will be in the next release of Cumulus TV as it will have the same library attached now?  If so, this may not be required.

If so, then it should work as expected

Seems 1.7.1 is still forcing videos to 16:9 when the source video is 4:3.  Unsure if there is some code behind the scenes in Cumulus that does this.  As mentioned when using the TIF demo and using the exact same m3u8 stream, it correctly shows the 4:3 videos in 4:3 aspect ratio with black bars left and right.

I've been looking into it. I think I'm doing something wrong that's causing it to stretch out.

I think you should also keep, among other modes, the current mode too!


Port the changes related to handling of unbonds in global-state-update-gen to feat-2.0

This ports the changes made in #4828 to feat-2.0.

bors r+

bors r+

bors r+


Add deity list to readme.

Sure, that's better than making people read the file.  Should probably put it in a --help switch someday, but this is good for now.

Oh, thanks!


Upgrade metabase image tag

Metabase 0.41.5 is available and It also includes Log4j upgrade change.

Thanks for contributing. Please also bump chart version, app version in Chart.yaml and update document in /charts/metabase/README.md accordingly


update a date field to null

Hi @crisfervil  , I have this issue , trying to set to null a date , I get this error .

This is may code :
var account = {} ;
account.accountid = '7D0C0490-9934-E611-80C3-005056AC0018' ;
account.name =  "now3" ;
account.new_deliverdate =  null ;
crm.update("account", account );
What am I doing wrong ,
Thanks in advance .

Hi Gabriel. I'll have a look at this case and come back to you ASAP

@GabrielGab I've published the version 0.0.15 to npm. This should fix the problem. Please let me know if it works!

Works fine! Thank you!
On Nov 23, 2016 8:22 AM, "Cristhian Fernandez"<EMAIL_ADDRESS>wrote:

@GabrielGab https://github.com/GabrielGab I've published the version
0.0.15 to npm. This should fix the problem. Please let me know if it works!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/crisfervil/DynamicsNode/issues/12#issuecomment-262488963,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMWke4dT-ocCtArJvNxYizyCDfxLN8-qks5rBCH0gaJpZM4K3uBV
.


See if we can somehow use .gitignore

From @petdance on March 18, 2012 2:10
I don't think we want to use .gitignore automatically, but maybe in ack 2.1 we can do something like add a --ignorefile=.gitignore.
Copied from original issue: petdance/ack2#28

From @dnblankedelman on March 18, 2012 2:18
And perhaps support .hgignore as well? I'm not an hg user, but I bet others would find that helpful as well.

That's why I figured it would be a --ignorefile and people could specify whatever file they wanted.
Although now I see that .gitignore and .hgignore use different formats.

Yes, I think we should do plugins for 2.1
This feature, however, I don't think should need to be a plugin.  I think it would be simple enough to do without having to have a plugin.  The big point of plugins is, in my mind, to include code that would take up a lot of code or execution time in the base ack, or would require a module.  I don't think this feature would do either of those things.

From @hoelzro on March 18, 2012 11:57
What do you think of doing plugins for Ack 2.1?  I think this would be a great example plugin.

From @hoelzro on March 18, 2012 14:15
Hmm...I suppose we differ on what should and shouldn't be a plugin.  I think a generic ignore file is "core-worthy", but as soon as we start to cater to specific use case (ex. Git/Hg integration), that's what I consider "plugin-worthy".

Actually, I'd make .gitignore standard, and .hgignore a plugin because it's more complex.
But this is all down the road.

From @hoelzro on May 11, 2013 16:24
See also #144, #272.

From @georgexsh on February 12, 2014 6:23
+1 for this
with git, ignore file not only in .gitignore, but also $GIT_DIR/info/exclude, see gitignore(5)

From @moll on May 22, 2014 15:59
Any news on this? Any plugins or anything?

Sorry, no.  We don't even have a plugin architecture yet. :-(

From @sheerun on January 20, 2015 1:26
+1 --ignore-dir entires in ackrc grow larger and larger, because I can't simply ignore what's in gitignore

From @medikoo on October 24, 2014 9:18
+1
Following what's in .gitignore is mostly what I expect, and current defaults are too invasive

.gitignore is all globs, right?  The .gitignore would be the only place that ack handles globs.
Does anyone know how Windows Git does .gitignore?
Handling .gitignore is not a CYJ.  (Can't you just...)

From @hoelzro on January 20, 2015 4:41
Thanks everyone for chiming in.  ack2 is in a bit of a code freeze at the moment; @petdance would like to go through everything that's changed since 2.14 so that 2.16 can be released, and we don't want to heap any more work on at the moment.  If anyone is willing to submit a pull request implementing the feature, however, we can merge it in once 2.16 is released!

From @hoelzro on January 20, 2015 17:38
I don't know for sure, but I'm guessing that gitignore on Windows works pretty much the same as on OS X/Linux, maybe with some accounting for case insensitivity.
.gitignore can contain more than just globs; you can have inverted expressions (ex. ignore all .jar files, except for those under deps), or relative paths (ex. ignore all jars in /.mvn or something).  Absolute paths introduce an especially sinister level of complexity, since they're absolute with respect to the root of the working tree.  Which means we would have to detect the root of the working tree, which means respecting GIT_WORK_TREE and GIT_DIR.  And let's not forget that there's not just one gitignore file; you have .gitignore, $GIT_DIR/info/exclude, the config setting core.excludesfile, and anything else I forgot to mention.  Long story short, that would be a lot of git implementation details to put into ack, and frozen to which ever version's implementation we would port over.
That being said, we could shell out to git ls-files, but then we have to handle the case where someone doesn't have git installed, or isn't in a git repository, and reconcile potential differences between versions of Git.  So even that route is frought with peril.
My suggestion is this:  if you really want this feature, write a shell wrapper around ack to call git ls-files and populate ACK_OPTIONS based on its output, and then call ack.  If we end up implementing this feature, it probably won't be for a while.

From @SethTisue on January 20, 2015 18:54
fwiw, from issues like e.g. https://github.com/ggreer/the_silver_searcher/issues/100 it appears the ag folks went the route of parsing .gitignore themselves (apparently imperfectly)

From @naggie on February 1, 2017 12:28
alias gack="git ls-files -oc --exclude-standard | ack -x" is what I use.

From @pmorch on March 12, 2016 12:42
Perhaps one way to achieve this without supporting .gitigore directly in ack could be to write a script that generates a $PROJECT/.ackrc from all the .gitignore files (and whatnot) in the project.
Probably not trivial to write if all the corner cases must be supported. @hoelzro wrote:

And let's not forget that there's not just one gitignore file; you have .gitignore, $GIT_DIR/info/exclude, the config setting core.excludesfile, and anything else I forgot to mention.

This would certainly scratch my itch right now:
cd $PROJECT
$ACK/contrib/generate-ackrc-from-gitignore.pl . > .ackrc
ack pattern

Also, then it isn't baked directly into ack.

From @naggie on March 16, 2017 9:45
Good idea, I agree with you that ack should not parse .gitignore files.
One caveat with that alias is that submodules are listed by the git command and they are directories -- ack then (correctly) complains about the directories.
With git 2.11+, the --recurse-submodules option may be used which should work around this, and of course match files within submodules which might not be desired.
Here's the same command with the long options which are semantic so better for docs:
alias gack="git ls-files --others --cached --exclude-standard | ack -x"

I don't want ack to have to dig into .gitignore files, but we can put the git line in the docs.

Does my heart good to see people using ack -x.

We are not going to parse .gitignore.

re parsing .gitignore, which above comment says we aren't doing, there's a new modules or two that would outsource doing that if we don't want to do it ourselves but would like to be able to DWIM.

Text::Gitignore - Match .gitignore patterns
It combines Text::Glob and File::FnMatch functionality with several ".gitignore"-specific tweaks....

Parse::Gitignore - parse .gitignore files [does matching too]

Parse a .gitignore file and check whether a file matches it....
https://metacpan.org/search?q=gitignore

No, if you give ack a list of files you're going to process, then it ignores all type filtering.  It's the same as if you typed ack --js foo.php, you'd be searching the foo.php file, despite the --js.  If you specify a list of files, ack assumes you know that's what you want.


Note generator app

Description
I developed a Notes Generator Tool to generate concise, structured notes from various types of input in other to provide students with clear, summarized learning materials.
Related Issue
https://github.com/orgs/marvelai-org/projects/8/views/1?pane=issue&itemId=89621248&issue=marvelai-org%7Cmarvel-ai-backend%7C129
Type of Change

[ ] New feature: A non-breaking change that adds "Note generator" feature to the app.
[ ] Documentation update: New feature code is well documented
[ ] Test enhancement: Adding or updating tests; no production code change.

Proposed Solution

Input Handling

Implementation:

Built logic to accept three types of input: plain text, file uploads (PLAIN TEXT, CSV, PDF, DOCX), and URLs (websites, YouTube.
Used helper functions (extract_text_from_file, extract_text_from_url) for modularity, making the code extensible for future input types.

Design Decisions:

Modularized input parsing to support easy integration of new file formats.
Used mock-based testing to isolate file and URL handlers.

Notes Generation Logic

Implementation:

Developed an executor function that coordinates input parsing, focus-based filtering, and AI-driven note summarization.
Used flexible output structures (bullet points, paragraphs, tables) to match user preferences.

Design Decisions:

Separated content preprocessing and notes generation for clarity and maintainability.
Added an optional "focus" parameter to tailor notes to specific topics, improving usability.

Output Formats

Implementation:

Created functions to export notes in plain text, DOCX, and PDF formats using libraries like docx and FPDF.

Design Decisions:

Chose widely used formats to ensure compatibility with users' needs.
Structured output generation modularly to enable quick addition of new export formats.

Core Architecture

Implementation:

Organized code into a structured folder hierarchy (app/features/notes_generator/) for maintainability.
Used core.py for primary logic and tools.py for reusable helper functions.

Design Decisions:

Followed a clean architecture with clear separation of responsibilities to improve scalability and readability.
Emphasized reusability with helper abstractions.

Testing

Implementation:

Created unit tests (test_core.py, test_tools.py) for all primary and helper functions using PyTest.
Covered normal operations, edge cases, and error handling.

Design Decisions:

Prioritized test-driven development (TDD) to ensure code reliability.
Mocked dependencies for isolated testing and ensured 100% coverage for core functionalities.

Logging and Error Handling

Implementation:

Added comprehensive logging to track errors and user inputs for debugging.

Design Decisions:

Followed platform standards for consistent and meaningful error reporting.
Prioritized user-friendly error messages to enhance user experience.

Extensibility and Maintainability

Implementation:

Used metadata files (metadata.json) to define input parameters for validation.
Documented all functions with type hints and docstrings.

Design Decisions:

Focused on future-proofing by using modular and extensible code structures.
Prioritized readability with consistent naming conventions and clear comments.

How to Test
Test Configurations

Ensure you have the necessary dependencies installed:
pip install -r requirements.txt
Run the tests:
PYTHONPATH=./ pytest app/features/notes_generator/tests/test_core.py

Test Cases and Expected Outcomes

test_executor_text_input_valid:

Description: Tests the executor function with valid text input.
Expected Outcome: The function should return a status of "success".

test_executor_file_input_valid:

Description: Tests the executor function with valid file input.
Expected Outcome: The function should return a status of "success".

test_executor_invalid_file_type:

Description: Tests the executor function with an unsupported file type.
Expected Outcome: The function should raise a ValueError.

test_extract_text_from_file:

Description: Tests the extract_text_from_file function with a valid file.
Expected Outcome: The function should return the extracted text.

test_extract_text_from_url:

Description: Tests the extract_text_from_url function with a valid URL.
Expected Outcome: The function should return the extracted text.

Unit Tests

test_executor_text_input_valid:

Tests the executor function with valid text input.

test_executor_file_input_valid:

Tests the executor function with valid file input.

test_executor_invalid_file_type:

Tests the executor function with an unsupported file type.

test_extract_text_from_file:

Tests the executor function with dummy.pdf file.

test_extract_text_from_url:

Tests the executor function with valid YouTube video ID

Documentation Updates
N/A

[ ] I have performed a self-review of my code.

[ ] I have commented my code, particularly in hard-to-understand areas.

[ ] I have made corresponding changes to the documentation.

[ ] New and existing unit tests pass locally with my changes.

[ ] Any dependent changes have been merged and published in downstream modules.

Additional Information
I am look forward to your review and feedback

Hey @Haryohmi, please, check this guidelines about how to create your own Marvel AI Tool for better enhancements: https://lab.realityai.tech/posts/how-to-create-your-marvel-ai-tool


LibWasm: Implement most of iNxM SIMD operations

With this we pass an additional ~2100 tests.
There's still some test cases in the iNxM tests that fail with this PR, but they are somewhat weird.

I checked out @Enverbalalic's original PR to see if I could help with the UBSAN issue (since I ran into similar issues with some other Wasm instructions) and I talked with them about it. I'm now listed as a co-author to Enver's original commit.

LGTM, LGTM.


ROX-16458: Disable PSPs by default in generate commands

Why we need this change? Can you update description?

Shouldn't this stay enabled by default - if for pre-v1.25 Kubernetes is to be believed, it would only create PSP for <v1.25, right?

@ludydoo ping :)


Unrelated test output logging to console

Current staging has test output logging to the console. But the test output is from a completely separate challenge.
I am working in HTML & HTML5 but keep getting
frame.js:77 Block scope i is:  block scope
frame.js:77 Function scope i is:  block scope

I haven't seen this again. Closing


Added prompt tweaker notebook

Actually it looks like changes to the PREAMBLE in the notebook aren't taking effect. It looks like it's being taken from:
kai/kai/data/templates/mf_preamble.txt.
Editing that file and restarting changes the prompt.

Whoops! Will fix!

@jmontleon Fixed

ACK, that fixed it!


Use github access token for git mirroring

Hello,
The official document describes that there are 2 ways to authenticate to access git repository when git mirroring, which are password-based authentication and OpenSSH key.
However, I wonder if we could use github access token as authentication key

github access token: https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token

Hi, @2017029570 that's a good suggestion!
We definitely need to support accessing GitHub using an access token.


Typescript issue with return type of ThemedCssFunction

Version
styled-components: 3.1.6
Reproduction
The issue occurs when using the css() helper and passing the return value into one of the styled component factory methods.
Steps to reproduce
Try the following code in a TypeScript project:
const contentWrapperStyles = css`
    margin: 30px;
`

const ContentWrapper = styled.div(contentWrapperStyles)

Expected Behavior
It should compile without type errors
Actual Behavior
Argument of type 'InterpolationValue[]' is not assignable to parameter of type 'TemplateStringsArray'.
  Property 'raw' is missing in type 'InterpolationValue[]'.

Possible Solution
I was able to get it working by modifying the return type for ThemedCssFunction in stylde-components.d.ts. I added this type:
export type InterpolationTemplateStringsArray = InterpolationValue[] & TemplateStringsArray

And used it as follows:
export interface ThemedCssFunction<T> {
  (strings: TemplateStringsArray, ...interpolations: SimpleInterpolation[]): InterpolationTemplateStringsArray;
  <P>(strings: TemplateStringsArray, ...interpolations: Interpolation<ThemedStyledProps<P, T>>[]): FlattenInterpolation<ThemedStyledProps<P, T>>[];
}

(the original return type of the first function signature was InterpolationValue[])
I don't know if this is a proper solution, but if so I'm happy to submit a PR.
Workarounds
In the meantime, I found 2 workarounds:

const ContentWrapper = styled.div${contentWrapperStyles}`
const ContentWrapper = styled.div(contentWrapper as InterpolationValue[] & TemplateStringsArray)

I think it would be better to fix the issue at its source, but these workarounds aren't too bad (with the second one I'd create a reusable type alias)...

const contentWrapperStyles = css`
    margin: 30px;
`

const ContentWrapper = styled.div(contentWrapperStyles)

The ocde here is actually invalid and doesn't comply with our API. Our css mixin helper doesn't return [string[], ...Interpolation], but (Interpolation | string)]] (these are of course not valid typings but just to make this a little clearer)
Instead you should always do this:
styled.div`
  ${contentWrapperStyles}
`

Hope this helps 👍

Oh ok, thanks. I assumed it was valid syntax because it worked fine in plain JS.

@mbrowne It'll probably work fine as long as you don't use interpolations; but that's more coincidental than not :wink:
Please refer to the docs if you haven't seen them yet, as they have more examples around usage 😀 https://www.styled-components.com/docs

FYI the reason I was trying to do it that way was because I was importing contentWrapperStyles from a separate file (because this is for my main App component and I don't want it to get too big). But this is fine:
styled.div`
  ${contentWrapperStyles}
`


Multitouch support

Needed multi touch support, and originally thought the multi-touch repo was iOS only because of the iOS folder. Looks like from the issues it doesn't work on android anyway, so here we are. Feedback appreciated.

Supports two sliders
Update callback to return both values
Deprecate minimumTrackTintColor and maximumTrackTintColor in favor of trackColor and trackHighlight color
Moved render to bottom of file to make it easier to find ^_^
updated Example to show off new multi touch
Updated readme to support these changes

will this be merged?

Is this PR merge?

Any update on this?

I don't think the author is supporting this repo anymore since he hasn't merged anything in a long time. That being said I also don't have time to resolve conflicts on this but if anyone else wants to take over, feel free.

@jgornick made a new PR #142 and it has no conflict. But as you mentioned this repo is not supported anymore.

https://github.com/react-native-community/react-native-audio-toolkit/issues/124

@doctadre any plans resolving conflic?


[FEATURE] Want to add a Hover effect on the buttons of the SnapGrid Home page

Description
A hover effect can be added on the buttons of the SnapGrid Home page
Expected Behavior
On hovering over the button, colors will change and some other hover effects will be applied.
Actual Behavior
On hovering there is no effect on the buttons .
Screenshots (if applicable)

Can you assign me this issue under Hactoberfest 2023?


Alternate java nth ugly number

Assigned Issue Number?
#001
Language Opted?
C/C++/Python/Java/...
Number of files added or updated?
1/2/3
Name of these files?
main folder => sub_folder => ... => ... =>  file.py
example :
Algorithms => Searching => Linear_Search => Linear_Search.py
Checklist

[ ] I was assigned for this otherwise my PR will be rejected.
[ ] I've read the contribution guidelines.
[ ] I've written code by myself. No Plagiarism allowed
[ ] I've referred the correct issue number.
[ ] I've filled up this entire template correctly.

:star2: this repository and support.

DSA-Library/Algorithms/DP/nth_ugly_number/Ugly.java


Add sphinx-docgen

This needs to be looked at ASAP how to integrate this

Delayed to next sprint

Done


Bagged trees and Random forests

Should be a full draft. Looks like we have some merge conflicts. I'll fix those and then probably get it merged in.

This merge conflict brought to you entirely by #29. I'll see if I can get the GH Actions stuff and branch deploy to work this weekend.


[IOS] react-native-haptic-feedback (2.3.3) not working on iphone 14pro

I tried use this example in my code, but nothing happen (no vibration and sound). Could you tell me what should I check on the device or in the project? Thanks.
const onPress = () => {
      const options = {
        enableVibrateFallback: true,
        ignoreAndroidSystemSettings: false
      }

      ReactNativeHapticFeedback.trigger('impactLight', options)

      // some actions on Press
}

IOS Version 18.0.1
iPhone 14 Pro
"react-native-haptic-feedback": "^2.3.3",
"react-native": "0.75.4",
On the device settings: Accessibility->Touch->Vibration is ON

Sorry! I have found the problem! It isn't the problem of this library!
On the device settings: Settings -> Sound & Heptics -> Keyboard Feedback -> Heptic -> ON


AngularJS2-Learning dead link

This guy looks link dead.  Great list by the way... So much learning to do.

Hi Michael, thanks for heads up! I have replaced it with link to https://github.com/jmcunningham/AngularJS-Learning, which is even older, but possibly still interesting for historical purposes. 😄


tidy up

Eliminate unwraps, improve some comments and move some code around a lil
Removes server module, which is not in use and accidentally checked in at some point

@madninja shall we consider adding -W clippy::unwrap_used to clippy's args in CI. It won't pass right now, but can be a goal.

@madninja shall we consider adding -W clippy::unwrap_used to clippy's args in CI. It won't pass right now, but can be a goal.

oh so -D clippy::all doesn't make unwrap_used a warning? annoying.. My only concern is that there are a couple of places where using unwrap is actually ok

oh so -D clippy::all doesn't make unwrap_used a warning? annoying.

Yeah, it's a terribly-named group, since it effectively means "default", rather than actually "all". -D clippy::all` seems to just turn default warns into denies.
unwrap looks to be grouped in clippy::restriction group.
clippy::pedantic is even more fun.


Possibly change approach on progress

May need more than just a "completed" status for task inst and segs, may want a more general status like
type status = `Completed | `Uncompleted | `Discarded

May also need to rename the data structure from progress to something else to make more sense

Partial progress via PR #40
PR splits stores into three groups: "uncompleted", "completed", "discarded"

Final progress via PR #41


Cannot run node TASKs: $PATH not sourced correctly

VSCode Version: 1.47.2
OS Version: macOS 10.14.6

Steps to Reproduce:

Add a new task: {
   "label": "Test node",
   "type": "shell",
   "command": "node",
   "args": [
     "-v"
   ]
 }

Run task
Result: It cannot find node!

Executing task in folder dbux: node -e "console.log('hi!');" <
/bin/bash: node: command not found
The terminal process "/bin/bash '-c', 'node -e "console.log('hi!');"'" failed to launch (exit code: 127).

I would argue that this is a substantial problem, because it prevents me from using any node-based task.

Does this issue occur when all extensions are disabled?: Yes
Analysis
This issue has previously been discussed in https://github.com/microsoft/vscode/issues/29412
Here is some more relevant info:

If I open a terminal window, and do which node, I get:

/Users/domi/.nvm/versions/node/v13.12.0/bin/node

We know that nvm injects it's paths into $PATH via .bashrc and, as discussed in #29412, .bashrc is not executed explicitely.

NOTE: my .bashrc does not have the "no-interactive" part in it. It should always execute.
This is Ok... Let's assume .bashrc is just not sourced

@dbaeumer pointed out that the correct $PATH should be sourced for VSCode at start-up anyway, and then be inherited by the shell.

For this, @joaomoreno recommended checking Dev Tools -> project.env.PATH, which for me is actually correct:
> process.env.PATH
<- "stuff:/Users/domi/.nvm/versions/node/v13.12.0/bin:morestuff"

However, tasks' $PATH is just not right. I verified with this task:{
   "label": "Test node",
   "type": "shell",
   "command": "echo",
   "args": [
      "$PATH"
   ]
}

/usr/gnu/bin:/usr/local/bin:/bin:/usr/bin:.

So the problem is that the $PATH is not inherited from VSCode despite the team's own assumption of that to be the case.
Thoughts?

I have found a workaround for now: run bash as a login shell (-l), and supply command as parameter (-c):
{
  "label": "Test node",
  "type": "shell",
  "command": "bash",
  "args": [
    "-lc",
    "--",
    "node -v"
  ],
}

v13.12.0

@Domiii do you have any options set outside the task in your tasks.json, like this?
{
	// See https://go.microsoft.com/fwlink/?LinkId=733558
	// for the documentation about the tasks.json format
	"version": "2.0.0",
	"options": {
		"env": {
			"one": "one"
		}
	},
	"tasks": [
		{
			"label": "npm",
			"type": "npm",
			"script": "watch",
			"problemMatcher": [
				"$ts-webpack-watch"
			],
			"group": {
				"kind": "build",
				"isDefault": true
			}
		}
	]
}

@alexr00 No options, nothing. The whole thing is just:
// tasks.json
{
  "version": "2.0.0",
  "tasks": [
  // ...
  ]
}

@Domiii when you opened the dev tools with Developer: Toggle Developer Tools and checked project.env.PATH, did you do it from the exact same window that you see this issue in VS Code in?

I found the problem: I had "terminal.integrated.inheritEnv": false in my User settings. Probably from a while back where I was advised to add it to workaround some other issue I had.
Anyway, all is good. Thanks for the continued support! :)


Clarify captures documentation

Some proposals:

Add a few words about captures to this section:
https://github.com/thomashoneyman/purescript-halogen-hooks/blob/main/docs/01-Hooks-At-A-Glance.md#the-effect-hook

Change the language here to clarify that captures is not an optional performance enhancement, but that it is required. (obvious in hindsight when looking at the type signature, but this might still trip-up future readers too).
https://pursuit.purescript.org/packages/purescript-halogen-hooks/0.4.3/docs/Halogen.Hooks#v:captures
When I originally read "Used to improve performance", I assumed this worked like Halogen.HTML.memoized, where you can optionally choose to use it. https://pursuit.purescript.org/packages/purescript-halogen/5.0.0/docs/Halogen.HTML#v:memoized

Add a note about how captures is necessary in the useTickEffect docs too. https://pursuit.purescript.org/packages/purescript-halogen-hooks/0.4.3/docs/Halogen.Hooks#v:useTickEffect
Also, I see "array" mentioned here a lot, but the first argument looks like a record.

I agree that the captures documentation could use some improvement and with the three places you've identified as places it could see changes.

Change the language here to clarify that captures is not an optional performance enhancement, but that it is required.

This is an artifact from an older version of the code where captures produced an Array MemoValue so you could in fact provide an empty array (useTickEffect [] do ...). That's also the reason for the references to "array" rather than "record". However, in the current version you have to use captures each time, capturing an empty record if you don't have any dependencies.
I'd like to loop back around to this to update the documentation and ping you with the changes for your review.