fix: Can not request data larger than 4MB with grpc (#330)

Description
There is no way to change the grpc default option before.So when respond is larger than 4MB this error occured. I fix this bug by adding grpc options to dapr options
Issue reference
#330
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Extended the documentation

Hi! Thanks a lot for your PR, amazing to see the nice contribution.
I reviewed your PR and while I think it tackles the issue, we were aiming towards a more general approach for the entire DaprClient side of things.
What we were thinking of is to solve this at the DaprClient side of things. Here we push DaprClientOptions where we would like to add something such as maxBodySizeMb: number that propagates to both HTTP and gRPC (we have 2 protocols, so both should be adapted for it)
https://github.com/dapr/js-sdk/blob/22fa4077bd7295c6158c90c241c7f79351d9a038/src/implementation/Client/DaprClient.ts#L85
https://github.com/dapr/js-sdk/blob/22fa4077bd7295c6158c90c241c7f79351d9a038/src/types/DaprClientOptions.ts#L16
This way we can configure both HTTPServer and GRPCServer and abstract the logic for the end consumer
https://github.com/dapr/js-sdk/blob/22fa4077bd7295c6158c90c241c7f79351d9a038/src/implementation/Server/HTTPServer/HTTPServer.ts#L45
https://github.com/dapr/js-sdk/blob/22fa4077bd7295c6158c90c241c7f79351d9a038/src/implementation/Server/GRPCServer/GRPCServer.ts#L45
Putting all of this together would result in the DaprClient that could be instantiated like this:
const client = new DaprClient(daprHost, daprPort, CommunicationProtocolEnum.HTTP, {
    maxBodySizeMb: 10
});

Is this something you could help with?
P.S. We also can't merge a PR without the tests, so please add those as well

thx, Ur idea seems better.I will try to write better and add some tests about this feature.

/ping @JY29

Closing in favor of #381


Added topicoptions.WithWriterTrace option for attach tracer into …

…separated writer
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

Codecov Report
Base: 59.71% // Head: 47.34% // Decreases project coverage by -12.36% :warning:

Coverage data is based on head (c81df07) compared to base (25bc782).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff             @@
##           master     #463       +/-   ##
===========================================
- Coverage   59.71%   47.34%   -12.37%
===========================================
  Files         240      237        -3
  Lines       25988    25548      -440
===========================================
- Hits        15518    12096     -3422
- Misses       9478    12615     +3137
+ Partials      992      837      -155

Flag
Coverage Δ

1.16.x
33.51% <0.00%> (-25.92%)
:arrow_down:

1.18.x
36.42% <0.00%> (-23.05%)
:arrow_down:

1.19.x
36.40% <0.00%> (-23.29%)
:arrow_down:

connection
10.56% <0.00%> (+0.16%)
:arrow_up:

database_sql
?

discovery
8.78% <0.00%> (+0.13%)
:arrow_up:

e2e
33.51% <0.00%> (-18.64%)
:arrow_down:

integration
?

macOS-latest
36.39% <0.00%> (-0.04%)
:arrow_down:

ratelimiter
?

scripting
10.65% <0.00%> (-0.31%)
:arrow_down:

table
?

topic
26.93% <0.00%> (-0.07%)
:arrow_down:

ubuntu-latest
47.33% <0.00%> (-12.33%)
:arrow_down:

unit
36.42% <0.00%> (-0.07%)
:arrow_down:

windows-latest
?

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

Impacted Files
Coverage Δ

topic/topicoptions/topicoptions_writer.go
12.50% <0.00%> (-0.84%)
:arrow_down:

internal/value/cast.go
0.00% <0.00%> (-100.00%)
:arrow_down:

meta/consumed_units.go
0.00% <0.00%> (-100.00%)
:arrow_down:

internal/xsql/valuer.go
0.00% <0.00%> (-100.00%)
:arrow_down:

internal/ratelimiter/options/acquire.go
0.00% <0.00%> (-100.00%)
:arrow_down:

internal/ratelimiter/config/config.go
6.25% <0.00%> (-81.25%)
:arrow_down:

internal/coordination/config/config.go
6.25% <0.00%> (-81.25%)
:arrow_down:

retry/errors.go
0.00% <0.00%> (-80.00%)
:arrow_down:

table/types/types.go
12.76% <0.00%> (-78.73%)
:arrow_down:

internal/ratelimiter/client.go
0.00% <0.00%> (-77.56%)
:arrow_down:

... and 86 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Add Katex render options

Added Katex options to the component that currently aren't available.
This PR adds the options "throwOnError" and "errorColor" to the latex-maths component, defaulting to their standard default values if they are not specified.

throwOnError=boolean. If true, KaTeX will throw a ParseError when it encounters an unsupported command. If false, KaTeX will render the unsupported command as text in the color given by errorColor. (default: true)
errorColor:=string. A color string given in the format "#XXX" or"#XXXXXX". This option determines the color which unsupported commands are rendered in. (default: #cc0000)

Existing tests all pass and 4 new test have been added to verify the additions.

Thank you @74monkeys, apologies for the delay getting this merged in.


Adjustable attributes for get_psm3

iotools has a fixed ATTRIBUTES variable. I would like to be able to change this in get_psm3. Is there a reason we can't make attributes an input to the function get_psm3?

I've wanted the same thing.  Note that you can change the ATTRIBUTES list before making the API call, so the functionality does exist, it's just a little awkward to use:
pvlib.iotools.psm3.ATTRIBUTES = [
    'ghi', 'dni', 'dhi', 'air_temperature', 'wind_speed', 'surface_albedo',
    'clearsky_dhi', 'clearsky_dni', 'clearsky_ghi', 'cloud_type'
]
meta, df = pvlib.iotools.get_psm3(40, -80, api_key, email, '2019', 30, True)

If anyone does open a PR for this, they could also edit the docstring to include 2019 and t*y-2019 in the list of acceptable years because those are available now.

Probably a good idea to add attributes as a kwarg, based on what I saw on the NSRDB webinar yesterday there are a number of new columns of data either available or soon to be added.

Taking a look at this as part of a general update to the PSM3 wrapper.  I'm waffling on where a new attributes kwarg should be added in the signature.  An optional parameter at the end, to maintain backwards compatibility?  A new required parameter near the beginning?  Input is welcome.  Current signature for reference:
def get_psm3(latitude, longitude, api_key, email, names='tmy', interval=60,
             leap_day=False, full_name=PVLIB_PYTHON, affiliation=PVLIB_PYTHON,
             timeout=30):

I suggest attributes=ATTRIBUTES anywhere before timeout. I don't have any concerns about maintaining kwarg order for backward compatibility. I'm willing to considered a required argument if others think it's a good idea.


FIX: correctly displays unread indicator in titles

Hm, so we're back to the design where indicators are next to labels? 😃
iirc, it was like that originally. Then we decided it's too close to avatars (that use green as status indicators) so we moved them all the way to the right (+ a margin). We're reverting that change? cc: @discourse/designers (gotta try the new team mention 😛)

Hm, so we're back to the design where indicators are next to labels? 😃
iirc, it was like that originally. Then we decided it's too close to avatars (that use green as status indicators) so we moved them all the way to the right (+ a margin). We're reverting that change? cc: @discourse/designers (gotta try the new team mention 😛)

I'm not seeing any change in the placement of the green/blue unread indicator here.

really ? I tried how it was before my PR and it was next to label, I guess it was not  in non-sidebar... what a hell...

Really we can't have such big difference between sidebas/non sidebars, it makes 0 sense


Can not add document by using Input by editor

manually input by editor not successfully
After input a list of object by using input by editor. It not successfully create a new document

Hi @Sang2306 ,
could you paste your input code or screenshots here to help me find out.

Hi @Sang2306 ,
Just paste some screenshots here to help me reproduce that.

Hi @Sang2306
You can try same action again, and memory the task number show below, then go tasks page to check this task detail for debug,
I will close this issue if you can not give me any feedback, cause I can not reproduce this problem. i😅


Sort ddoc table of functions in range package

A search on a sorted list is so much nicer, especially for humans.

Other than that, LGTM. Thanks!

Whoa, another one ready to merge but sleeping for 26 days now? Time to merge! We'll clean up any messes later, if necessary.

Auto-merge toggled on


Support more unit tests from Spark 3.3/3.4

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Gluten has ported the major part SQL based unit tests from Spark 3.2 branch, however upstream Spark has added more unit tests in 3.3 and 3.4 branch. Gluten does not check for those new tests
Describe the solution you'd like
Gluten should check for those new tests from Spark 3.3/3.4
The existing unit tests in Spark 3.2 should be refactored as common unit tests.

In Spark 3.2 gluten should check those common unit tests
In Spark 3.3 gluten should check those common unit tests and the new tests in 3.3

Describe alternatives you've considered
N/A
Additional context
N/a
CC: @zzcclp

Here's the list of different tests in Spark 3.3 vs. Spark 3.2
https://gist.github.com/zhouyuan/8c41cb1b579b3ca5bb5879ff7260c139
So there are two kinds of changes:

newly added tests
modified tests over Spark 3.2 due to API change

Exclude should be able to resolve a persistent view from Spark 33 test in https://github.com/oap-project/gluten/pull/1996 due to below issue.

Below tests need to be fixed for Spark 3.3
execution/adaptive/GlutenAdaptiveQueryExecSuite.scala
execution/benchmarks/ParquetReadBenchmark.scala
execution/datasources/json/GlutenJsonSuite.scala

```
- Various partition value types
- Various inferred partition value types
- Various partition value types
- Various inferred partition value types
- SPARK-32908: maximum target error in percentile_approx

- SPARK-36825, SPARK-36854: year-month/day-time intervals written and read as INT32/INT64
- support batch reads for schema
- SPARK-36182: read TimestampNTZ as TimestampLTZ
- SPARK-36797: Union should resolve nested columns as top-level columns
- SPARK-37371: UnionExec should support columnar if all children support columnar
- SPARK-36280: Remove redundant aliases after RewritePredicateSubquery
- SPARK-36182: read TimestampNTZ as TimestampLTZ
- SPARK-39833: pushed filters with project without filter columns
- SPARK-36825, SPARK-36854: year-month/day-time intervals written and read as INT32/INT64
- support batch reads for schema
- SPARK-36794: Ignore duplicated key when building relation for semi/anti hash join

Spark 3.4.1 has been a stable release, will gluten support 3.4 in the near future?

closing with new issues opened


Fix DI Extension class deprecation with Symfony 7.1

The "Symfony\Component\HttpKernel\DependencyInjection\Extension" class is considered internal since Symfony 7.1, to be deprecated in 8.1; use Symfony\Component\DependencyInjection\Extension\Extension instead. It may change without further notice. You should not use it from "Presta\SitemapBundle\DependencyInjection\PrestaSitemapExtension".

Thanks


Fix small issues not without feature consequences.

Ok, so I removed the instanceof check.

Thank you!


Player Resize pushes "recommended" column underneath the page header

Screenshot was taken with "static header" and "player gap" off, but neither setting seems to affect this behavior.
Firefox 38 beta
YTC build 514

What is your player size settings?

I reset all settings to internal defaults before checking this. Settings under Player Size are as follows:
Enable resize: On
Default player size: Default
Small resize button: Default
Large resize button: 720p
Player aspect: 16:9

Do you get the issue with the experimental player? You can try it out at https://www.youtube.com/testtube.

No, it seems to be working properly with the experimental player. The issue only occurs with the default player.

hmm. I tried with the default player and I couldn't recreate your issue.

I have a similar issue, the "views counter"  is not showing, I've tried to change the position with the UI placement thing but it still does not shows up. Resizing the player still carries the issue.

The following sequence always causes the issue to occur:

Reset YTC settings to default.
Change "Small resize button" setting to "Default"
Toggle "Theater/Default mode" button to Default or refresh the page

Just took a look through Firefox's Inspector to see what might be causing it, and it seems that watch7-sidebar-contents needs margin-top offset by +30px to line it up directly with the top of the video player.

@brunobxb how did you do that dark theme?

@PASAf I use this style: https://userstyles.org/styles/92164/youtube-lights-out-a-dark-youtube-theme

@Zarggg I will see if it can somehow figure out a way to recreate your issue.

@brunobxb take a look at #1768.

@YePpHa Thanks, it worked just fine. I edited the css sheet...


Implement "Lattice" view in Dashboard

Currently, the dashboard shows an overview of a single wasmcloud_host, though you cannot access multiple hosts in the same dashboard. After #73 , multiple hosts will be able to run on different ports on the same machine, but as it is today multiple hosts can be connected to the same lattice.
If it's technically possible, the wasmcloud dashboard should be able to display a "lattice" view that shows all hosts connected to the same lattice, allowing remote control of each of them. I can see this being technically challenging until #5 is implemented, so it may depend on that issue before we can issue commands to remote hosts via the dashboard.

Depends on #136

Waiting on #222 because control interface changes will require a good bit of modification in the dashboard, and that will be fundamental to remote control multiple hosts

Above is the current user experience when looking at a dashboard where there are multiple hosts. You can see there are two instances of an actor running, on two different hosts. I like this, and this is essentially what this issue is referring to as a "Lattice View", where all resources in a lattice are shown on a single dashboard.
As a part of #155, we'll want to support operations on multiple hosts in a lattice from the same view. Currently, operations like "Start Actor" and "Start Provider" are invocations on the Host API, so there's no way to use them to start an actor on a remote host.
I think the simplest solution for the MVP is to allow users to filter resources by-host in a multi-checkbox fashion on the lattice dashboard. This semi-depends on #155 as it assumes that we're able to know what hosts are running in a lattice. This would allow the dashboard view to be a lattice view and able to control individual hosts, even remotely on the control interface.
This would require modals like Start Actor to include a Host ID parameter for the control interface query, which could be a dropdown list similar to link definitions as long as we have access to hosts that don't already have running resources (we'll want to appropriately handle host heartbeats and/or the host started event).

An alternative to this is to have a dashboard for the full lattice view which is essentially read-only and doesn't allow for individual host modifications (link definitions would be allowed as they are lattice wide), and then have individual host dashboards alongside the left side of the screen. This would be fairly scalable, up until about 20 hosts in the same lattice can fit on the menu bar on the left side (by the time we have someone running 20 hosts in a real workload, we'll be past MVP) This would allow us to easily designate which host is the local running host, and allow operations like Start actor from file for that local host.
Would love some thoughts here @autodidaddict @stevelr on if you like a single view that can be configured to view individual hosts, or multiple views including an overall lattice view and additional host views that only show information for a specific host. My goal is to make it easy for you to tell what information you're looking at in the dashboard and what operations you can perform on a specific host.

For MVP I would think it would be ok to show all hosts or exactly one. In the filter one case, all the dialogs would populate with the correct host id

Agree the UI should be unambiguously clear whether you are viewing filtered or not

@stevelr I like your idea for showing all hosts information or exactly one. That will be simpler to implement for MVP and will still be useful

I like the idea of a filter that alters the dashboard view from "everything" to just one host. Nice and clean.


1.5.4 displaying incorrect number of unread messages

YakYak 1.5.4 is showing the wrong number of unread messages on OSX 10.15.2
Here there was only 2 unread messages but it shows 8 in the tray:

Here there is one unread message but it shows 10 in the chat window:

This was accurate on 1.5.3

I believe it's now incorrect in all previous versions as this was a result of a protocol change from Google.
It's accurate again on 1.5.5 (beta)

I just upgraded to the latest 1.5.5 (beta) release, and I'm still seeing this issue.

I am also seeing this issue.

me too

This issue is still present in the latest version. Please don't close the issue until it is fixed.

This issue is still present in the latest version. I just installed the latest beta and tested it. It still shows 9 unread messages when I have 0, 10 unread messages when I have 1, etc. Please don't close the issue until it is fixed.

I've pinned it so that the bot doesn't try to close it

Is this still happening in the latest release (1.5.11 or 1.5.12 beta)?


Provide -dbgsym packages

This is not a bug report, but rather a feature request for the ppa packages.
So I've recently observed a crash in pipewire-pulse and even have a coredump of the process. In order to report a bug upstream, I'd like to provide the stack trace to help fixing the bug. However, the ppa-repository is currently missing the -dbgsym variants of the packages.
Would it be possible to provide them, too?

https://launchpad.net/~pipewire-debian/+archive/ubuntu/pipewire-upstream/+packages?field.name_filter=pipewire&field.status_filter=published&field.series_filter=jammy
install *.ddeb files.
If it solves the problem please close it.

So there is no way to use the package manager for that? It sounds a bit inconvenient, especially if the package is updated, isnt it?

see : https://askubuntu.com/questions/487222/how-to-install-debug-symbols-for-installed-packages

But ddebs.ubuntu.com does only contain outdated pipewire-bin-dbgsym packages - its active on my system. The ones from this repo are not available via apt.

Yes probably need to download manually and give "sudo dpkg -i *.ddeb". Or even search on google, this is more generic not related to pipewire.
Thank you.

The debug packages contain the debug symbols for the binaries compiled. Thus they have to be created together with the binary packages. It just doesnt make sense that anyone else could provide them.

*.ddeb are provided with binaries see above link. What I am telling probably you have to download them from launchpad from the same PPA. Or google it how to make it possible your package manager install them like normal package installation when you want with some extra options or args.
Yes I know it doesn't make sense if someone provide *ddeb package as they have symbol files for debugging purpose with gdb or needed to generate backtraces. So please go ahead with download them manually and install them from the same PPA. Or search on google how to make possible your package manager install them from the same PPA.
Thank you.

Okay, the trick was to add main/debug to the sources.list file


Allow sharded cluster with custom directory/executable provider to be restarted

Problem description
If a sharded cluster is started in a custom directory, stopped and then restarted again, it fails. The underlying reason appears to be that the files specified via the cluster-config-file directive cannot be reused.
Proposed solution
When a RedisInstance is stopped, its redis.conf is parsed and all cluster-config-file directives looked up. All of these cluster config files are resolved against the folder the Redis executable resides in and, if present, are deleted.

I like what it does but I don't like the way it does it. Not that there is anything immediately wrong, it is just not my style. I've been wanting to work on this but I just can't seem to find the time. I hope you are not waiting for this to get done soon, I'm swamped.

Thanks for the feedback :) I am not waiting for it to be done soon. We just stumbled over it at work but have a workaround.
If you have any specific ideas as to how you would tackle this bug I could offer to implement another solution to it - once you have the time for it, of course!
Have a nice Sunday


Rejects PHP Short Tags

Although short tags have every reason to be rejected, it still causes some issues during validation. Consider the following:

<? echo $variable; ?>

The validator responds, "li is not a valid self closing tag." Similar for <?= ?> as well. The more civilized older brother, <?php ?>, works fine.

This should be fixed with the above commit.


[Question] Is this will made Storefront Reference Architecture deprecated (SFRA) ?

Hello everyone,
I juste begin reading SFCC documentation and I wondering if this sample application introduce the new way to use SFCC ?
If no, what is the difference between this and SFRA ?
Thank you very much.

Hi,
Thanks for your question.
Commerce Cloud wants to make it easy for development teams to get started building with our latest Commerce Platform innovations. The Storefront Sample Application provides an example implementation of these latest innovations, so that development teams can learn how to build their own storefront experiences on top of our headless platform using the NodeJS SDK and Salesforce Commerce API.
Sample App is not a replacement for SFRA and is not meant to deprecate SFRA. Below are some points that differentiate sample app from SFRA

The sample application shows you a recommended approach for building a storefront against our new headless platform, but it is not a complete and fully functional storefront reference application.
The sample application is not a replacement for Storefront Reference Architecture (SFRA). It does not have full feature parity with a reference application like SFRA. Not every use-case is covered, and tested for performance
The sample application, unlike SFRA, is not meant to be an out of the box production storefront application. It is meant to give you some guidance and understanding about how to get started, and help with adoption of our latest platform technologies, however, it is not intended to be a starting point to launch your storefront

I hope this helps!

Thanks a lot for this very clear explanation.

Hi @p-mehta-sf
Is there any way to migrate current SFRA to this sfcc sample application?


 Iris-messenger is also sometimes slowed down by hundreds of "signature did not match" errors that I'll need to debug.
It's noteworthy that iOS safari seems to have none of these performance issues, so it should be fixable.


Remove popout styles

Removes the popout styles, as discussed in #3635.
I've left the logoPosition code for now, we can delete in a few weeks when we're confident no one has complained about the popout removal and we go ahead with closing #3635 for good.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @PyvesB!

  Generated by :no_entry_sign: dangerJS against 774f86ab68e6c884e65d2d0abd0f2fc94f79252e

Good call, that case had slipped out of my mind!


Modify string discovery

Different binaries using different encodings for strings. The user should be able to specify what type of strings they wish to search for either as a global preference or preferably via a more flexible capability in the strings view.

Closing this as complete as the advanced preferences can now specify a list of unicode blocks to consider when searching for strings. #1334 is now tracking the broader issue of custom strings


perf(proxy): deletion of an undeclared property

Coverage increased (+0.02%) to 97.607% when pulling 6f0ba4a41c964f73dab02e4160b6c43fe865e4d7 on aleclarson:perf3 into 9345f1336145e4df84149ee55ea8dde267156e90 on mweststrate:master.

Coverage increased (+0.02%) to 97.607% when pulling 6f0ba4a41c964f73dab02e4160b6c43fe865e4d7 on aleclarson:perf3 into 9345f1336145e4df84149ee55ea8dde267156e90 on mweststrate:master.


Cleanup NetBeans license header for module db.core

Review and cleanup the license header in db.core
Oracle donated NetBeans to the Apache Software Foundation.
Your task now is to replace the old license header that has Oracle (and/or Sun Microsystems
and/or NetBeans) in it with the standard Apache Software Foundation license header.
For an empty file that supports headers you must add the Apache license header.
Note that you have to use the proper license header for Java, .properties or HTML files.
Look at the nearby files for templates and copy-paste the license header.
When done commit the changes with a commit message that starts with first line
"[NETBEANS-54] Module Review " and a message body describing your review.
See a longer explanation about what we are doing here: https://cwiki.apache.org/confluence/display/NETBEANS/List+of+Modules+to+Review
Please announce in a comment when you have started work.
Files that need to be looked at in db.core:
db.core/src/org/netbeans/modules/db/core/resources/SQLTemplate.sql
db.core/src/org/netbeans/modules/db/sql/history/jaxb.index
db.core/test/private.properties.template
db.core/test/unit/data/mysql5.0/dbcreate.sql
db.core/test/unit/data/mysql5.0/dbdata.txt
db.core/test/unit/data/mysql5.0/dbdel.sql
db.core/test/unit/data/mysql5.0/dbselect.sql
db.core/test/unit/src/org/netbeans/modules/db/sql/history/sql_history.xml

Already have PR in apache.


Improve layout of lyrics

To do

Deal more than a syllable per note. Find examples for unit tests scores Fixed PR #57
special MusicXML marks: end-line, end-paragraph, humming, laughing. What to do?
Improve layout

Engraving problems

spacing problem when lyrics takes more space than notes

extend line must go until prev note to next note with lyrics ==>

need to access ALL NOTES in order, not only those with lyrics ==>

this introduces a new layout pass on all notes ==> layout lyrics with notes? this will
solve the spacing problem when lyrics takes a lot of space. Just create the
syllables shapes, to determine spacing. Later, when spacing done, auxiliary
elements (hyphens, extend lines) will be engraved.

hyphens MUST be placed once this and next syllabus are layouted ==> either
a) when layouting a syllable, must check if pending hyphen and layout it; or
b) two pass engraving: first syllables and then hyphenation

add space between staves for lyrics:

Data about number of lyric lines can be stored in Instrument. This could help to add
space in layout. But not sure, as only systems with lyrics should get the additional
sapce.

Fails if language Japanese: proper font not selected

Pull request #58 fixed layout of lyrics.


Dilated Convolution with NCHW format

Greetings!
I am using Dilated Convolution of DNNL 1.1.
My input is 4 dimension and with the format of NCHW.
I set the dilation as an Int array of length 2, e.g. int[2]{2, 2}, dilation value of 1.
The result I got from DIFF_SRC is unexpected, it seems it has done dilation for the first dimension, N.
the (n, ., ., .) has the same result as calculated by BLAS api.
the (n + 1, ., . ,.) is a zero-filled tensor, which I think it has been applied dilation, skipped.
May I ask how to disable the dilation on the N dimension if the input is a batch.
Thanks.

Can you please provide a dnnl/mkl-dnn version including hash, and a reproducer?

Closing as there's not enough data to investigate. Feel free to reopen with additional information.


Option parsing from environment variables

It would be super nice/helpful to parse an options value from an Environment variable value as well taking what is passed in the command line call as the priority over the ENV variable. For CLI's that run in CI or automated environments this is super helpful as it would allow not having to print the value in the ENV variable and could keep it hidden. Not only that but it would be very convenient for repeated uses on commands!
import ArgumentParser

struct MyCommand: ParsableCommand {
    @Option(name: .shortAndLong, help: "The API Secret.", env: "SERVICE_API_SECRET")
    var secret: String
}

Usage:
mycommand --secret QWERTY12345
or
mycommand (where SERVICE_API_SECRET='QWERTY12345'

Yes. We have been working on this already, and we’ll open a PR within the next week or two. There are still a lot of open questions about how to do this right, and we’d love to get feedback from everyone.

Awesome, I am happy to provide some feedback on a PR!

@danieleggert Any update on the progress of this?

@danieleggert Any update on the progress of this?

Please check out #109 — it’s almost done.

any updates?

any updates?

still waiting😭

I this still on the roadmap?

@rauhul, do you have a preference on @KyleLeneau's proposal in this issue vs @danieleggert implementation in https://github.com/apple/swift-argument-parser/pull/109 vs something new like auto-magically populate values based on command names and argument names. For example, if we have a root command tart and sub-command push with a --populate-cache flag then set it automatically to a value of TART_PUSH_POPULATE_CACHE if defined?

I was thinking about a different approach where the parsing pipeline is composed of ArgumentValueProviders, the command line would be one such provider. I haven't fleshed out the idea but the benefit is that users could add their own argument providers depending on their use cases.
e.g. we could provide support out of the box for json config files, environment, .env files, NSUserDefaults, etc...

Any word on this? #109 got closed during the Swift branch transition and doesn't look like a replacement was created.


Added support for maxWidth and minWidth options for regions

Why do you want them? What's the use case?

When you are using wavesurfer for something like audio trimming. Region indicates are that will remain. And in that case you can limit user to minimum and maximum length of trimmed audio.

Merged, thanks!


Wonderful Survey! Add of a new work.

Thanks for the wonderful survey. We would like to add a new work: Matryoshka Query Transformer for Large Vision-Language Models. Paper: https://arxiv.org/abs/2405.19315 code: https://github.com/gordonhu608/MQT-LLaVA.
This model adds a new perspective in efficiently utilize visual tokens for Multimodal LLMs. Thank you so much ahead for considering our work.

Great work, We have added it to this repo and will include the paper in our next version.


Want to improve the styling of the support us section in navbar

Is your feature request related to a problem? Please describe.
I want to give styling to navbar support section option
Describe the solution you'd like
I want to give transparent background to it,it matches the UI of the website
#Screenshot

I am interested to work on this issue under GSSoC 2023 as a contributor

I am interested to work on this issue. Kindly assign it to me. I'll work on the appearance of the 'support us' page and form.
@akshitagupta15june @HimanshuNarware


Fix simulation on macOS

From my testing, modifying DYLD_LIBRARY_PATH to include the directories where the .dylibs are stored fixed the issue.
TBD how Bazel fails to set it accordingly and/or how we can fix that

some notes here: https://github.com/bazelRio/bazelRio/pull/25#issuecomment-927206912

I think my best guess at this point is some SIP / code signing issue? Can you try disabling SIP on your mac and running simulation? I don't think I can do that on my work machine.


SQLite3 Child entites do not get added when parent is added.

SQLite3 Child entites do not get added when parent is added.
Example:

var teacher = new Teacher
{
    Name = "John",
    Students =
    {
         new Student { Name = "Batman" }
    }
}

await dbContext.Teachers.AddAsync(teacher);
await dbContext.SaveChangesAsync();

In this scenario the student doesn't get added unless I specify
await dbContext.Students.AddAsync(student);

Is this by design?
Further technical details
EF Core version: 1.1.0
Database Provider: Microsoft.EntityFrameworkCore.Sqlite 1.1.0
Operating system: Windows
IDE: Visual Studio 2017

Dupe of #7298. Workaround is to use Add instead of AddAsync. The async method just adds overhead in all but very obscure scenarios.


If number of visible slides > number of slides, loop works only on one direction

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 5.2.1.

Platform/Target and Browser Versions: all major updated

Live Link or JSFiddle/Codepen or website with isssue: http://jaumeferrete.net/_jaumeferrete/dev/bienalfemsa/en (scroll down, right below the banner "upcoming programs and events" there is the swiper)

What you did
I have a regular swiperjs structure with this initalization, including slidesPerView: 'auto' and loop: true, so loopedSlides: 8
  var swiperEvents = new Swiper ('.swiper-container.events', {
    // Optional parameters
    loop: true,
    slidesPerView: 'auto',
    loopedSlides: 8,
    updateOnWindowResize: true
  })

Expected Behavior
I would expect loop to work with any number of slides, 1, 2, 3, 4 , no matter how many of them are visible in the first place. So even if I have 2 slides, but I am showing 4 on initial view (2 slides + 2 duplicate) I would expect loop to work.
Actual Behavior
When the ammount of visible slides are less than the total number of slides (so at least one duplicate is already showing when the swiper is initialized) loop does not work in both directions. slidePrev works forever but slideNext hits a wall after a number of slides, which I believe is the number of visible slides. In other words loop does not work with slideNext at all.
I tried looking for similar issues but can't seem to find the right keywords.

This is probably the same issue as :  #2942

in my case was looping only once only in larger screen, this happened because slidesPerView was > than the actual slides in the DOM


Change Promises to follow ES6 Promises/A+ spec

Q.defer() generates a Deferred object, which is no longer recommended as part of the Promise spec.
This is currently used in a couple of places:

src/js/file-manager.js
src/widget/geo/geopicker.js

As part of this change, I also request changing the Promise library from Q to lie, as lie does not provide extra functionality beyond the Promises/A+ spec, so this will make it simpler to follow the spec in future.

Totally agree with removing deferred usage. I think I have already removed the additional Q features I had been using previously, so swapping with lie is fine with me.
Thanks
https://github.com/kobotoolbox/enketo-express/issues/237


More Email and SMS Sending Options

https://azure.microsoft.com/en-us/services/communication-services/
https://sendgrid.com/

https://www.twilio.com/sendgrid/email-api


Multi directional resizing

Goal
Make resizing from all supported directions function like the current E/S/SE do.
Details
This is almost entirely taken from the great work done in this PR https://github.com/react-grid-layout/react-grid-layout/pull/1377 by ludovic (I don't know how to ping/tag him or else I would). I'd like to make sure all his work is acknowledged here so I made sure everything he did has him as the commit author. If this gets squash merged can we make sure this is co-authored by him?
The changes I made were to address some of the comments that @STRML had in the two videos he posted. Resizing should now be properly constrained to the container and all sides but the bottom.
I plan on cleaning up and consolidating some of this code to make it all a bit neater, but wanted to get this up as early as I could to solicit any other feedback you may have.
Video of the change in action
https://github.com/react-grid-layout/react-grid-layout/assets/580086/13dc529a-5ae1-4118-91aa-4f9b0e4d2f63

Something I was thinking of that wasn't handle in the original PR was when resizing with the "n" handle. If there are GridItem's above it, it probably makes sense to perform an operation similar to what happens when resizing via "w" or "e" when there is a coliision (neighbouring GridItem's get pushed to make room for the expanding GridItem).
If that makes sense I can introduce that functionality as well.

Thanks for this PR.
n resizing should behave the same as if you moved the GridItem up: it should push the collided item below the colliding one.

@STRML my coworker @MarkHarper addressed the n resizing issue (and also factored in some other compaction issues while he was at it.
Looking forward to your feedback!

Working through the tests still, hoping to get that up tomorrow at some time.

Should be good for another review @STRML

@STRML just want to nudge you on this so it doesn't get too stale (and to make sure this is relatively top of mind for me if there is more feedback that needs to be addressed)

Yup, taking a look at the tests/lint stuff now.

Tests are passing locally but failing in CI, looking into it further

I also had my coworker run it locally and he didn't get any failures either. Any hunch on what could be the culprit @STRML?

Make sure you're rebased on master?

Yea just saw the change you pushed, will rebase shortly.

Looks good now. I took a look into the security audit CI failure as well, but wasn't sure what the failure was caused by.

This works really well!!! Thanks for all your help.

Thanks for all the reviews, appreciate it!

Any chance of this feature being carried over to react-resizable too please?


wasi: allows closing stdio file descriptors

This allows wasm to close stdio file descriptors such as STDOUT(1). This will not close the underlying host resource as that would break a lot of folks doing logging to the console.
Thanks a lot to @vyskocilm for making this easy to identify and fix!
$ cat > fclose.c <<EOF
#include <stdlib.h>
#include <stdio.h>

int main() {
    int ret = fclose(stdin);
    if (ret != 0) {
        perror("fclose <stdin>");
    }
    exit(ret);
}
EOF

$ zig cc --target=wasm32-wasi fclose.c -o fclose.wasm
$ go build -o wazero ./cmd/wazero/...
$ ./wazero run fclose.wasm

Fixes #953

ps I also double-checked that char device detection still works (ad-hoc)


Add ToString() methods to ordinary typedef structs

We are running into an issue where we have implemented BOOL.ToString() => ((bool)this).ToString(); This clashes with this change. Obvious solution would be to rename the winforms ToString to something else.
Does returning to hex value for BOOL make sense though?

I could imagine CsWin32 special casing BOOL to print a boolean value. However since some uses of BOOL stick more values into it than the customary two, it may indeed be useful to print its full value as an integer.

Another option is to notice that your compilation already defines a ToString method and suppress automatic generation.


$animateProvider.classNameFilter silently fails

Note: for support questions, please use one of these channels: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#question. This repository's issues are reserved for feature requests and bug reports.
Do you want to request a feature or report a bug?
Bug.
What is the current behavior?
$animateProvider.classNameFilter silently fails by throwing an exception and eating it. This effectively stops the whole application from working without any messages or error in the console, or anywhere else. This results in the infamous "white screen of death".
The error that is thrown (and eaten) is an Angular exception that manages to point to a nonexisting url:
Error: [$animate:nongcls] http://errors.angularjs.org/1.5.7/$animate/nongcls?p0=ng-animate

I have no way of knowing what this "nongcls" error might mean.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://plnkr.co or similar (template: http://plnkr.co/edit/tpl:yBpEi4).
In any app, include ngAnimate module and add a config to the module:
.config(function ($animateProvider) {
   $animateProvider.classNameFilter(/ng-animate/);
})

What is the expected behavior?
It should just do as described in the API documentation. And if anything, certainly should not eat its exceptions. That's horrible for development!
What is the motivation / use case for changing the behavior?
It's eating exceptions. And it doesn't work as described.
Which versions of Angular, and which browser / OS are affected by this issue? Did this work in previous versions of Angular? Please also test with the latest stable and snapshot (https://code.angularjs.org/snapshot/) versions.
Angular 1.5.7 release, Windows 10, Firefox 47.
This project is an upgrade from Angular 1.3.16, and back then, this worked fine, even in the same browser.
Other information (e.g. stacktraces, related issues, suggestions how to fix)
There seems to be an undocumented check against some magic value in angular.js (yep, it's not even in angular-animate.js, it's in the core for some reason):
this.classNameFilter = function(expression) {
    if (arguments.length === 1) {
      this.$$classNameFilter = (expression instanceof RegExp) ? expression : null;
      if (this.$$classNameFilter) {
        var reservedRegex = new RegExp("(\\s+|\\/)" + NG_ANIMATE_CLASSNAME + "(\\s+|\\/)");
        if (reservedRegex.test(this.$$classNameFilter.toString())) {
          throw $animateMinErr('nongcls','$animateProvider.classNameFilter(regex) prohibits accepting a regex value which matches/contains the "{0}" CSS class.', NG_ANIMATE_CLASSNAME);

        }
      }
    }
    return this.$$classNameFilter;
  };

Like I said, this is undocumented, so perhaps this is a bug in the documentation, perhaps in the code. The worst thing, I cannot stress enough, is that this exception is not thrown, but eaten.

I get  a very nice exception in http://plnkr.co/edit/WYIkjYnZU1l1Ng3JPDEc?p=preview
The error has no documentation though, I agree that needs to be fixed.


Filtering point cloud on the z axis

The point cloud is detecting the ground. But I do not want it to detect it. I have looked at some filtering tools and found this: http://wiki.ros.org/laser_filters
But this is an angular filtering. I want a parallel straight line above the ground, where I can type in in which height the line should filter. Do you know a tools which works like this? I am using a tof camera

I'm having a similar problem, i'm using a 16 lines, 20° tilted lidar and zed stereo camera to provide oodometry, however i'm not able to tell the mapping process how to discard the lidar lines hitting the ground to be labelled as obstacles.
I have highlighted the same area in the three images

I can provide further info if necessary
Thank you


build out correct interface

Ashleys-MacBook-Pro:changes-stream-rust ag_dubs$ cargo run
   Compiling changes-stream v0.1.0 (file:///Users/ag_dubs/rust/changes-stream-rust)
error[E0277]: the trait bound `(): futures::Future` is not satisfied
  --> src/lib.rs:31:59
   |
31 |     self.work = Some(client.get(self.db.parse().unwrap()).and_then(f));
   |                                                           ^^^^^^^^ trait `(): futures::Future` not satisfied
   |
   = note: required because of the requirements on the impl of `futures::IntoFuture` for `()`

error[E0308]: mismatched types
  --> src/lib.rs:31:22
   |
31 |     self.work = Some(client.get(self.db.parse().unwrap()).and_then(f));
   |                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected type parameter, found struct `futures::AndThen`
   |
   = note: expected type `F`
   = note:    found type `futures::AndThen<hyper::client::FutureResponse, (), Fr>`

error: aborting due to 2 previous errors

error: Could not compile `changes-stream`.

To learn more, run the command again with --verbose.


Support Python 3.9

Is your feature request related to a problem? Please describe.
Currently Azure CLI can't be installed on Python 3.9, causing different errors on different platforms.
For example, on Windows
Building wheels for collected packages: bcrypt, cryptography, PyNaCl
...
  Building wheel for cryptography (PEP 517) ... error
  building '_openssl' extension
  error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
  ----------------------------------------
  ERROR: Failed building wheel for cryptography

This is because older versions of bcrypt, cryptography, PyNaCl don't distribute wheels for Python 3.9. For example, cryptography 2.9.2 only distributes cryptography-2.9.2-cp38-cp38-win_amd64.whl.
Users will have to either

install gcc or Microsoft Visual C++ to build these dependencies from source, or
use an older version of Python (https://github.com/MicrosoftDocs/azure-docs-cli/issues/2407).

Describe the solution you'd like
The latest versions of bcrypt, cryptography, PyNaCl all use Stable Application Binary Interface (*-cp36-abi3-win_amd64.whl) to build wheels so that they can be installed on Python 3.9 without building source code.
Azure CLI should support Python 3.9 by bumping these dependencies:

[x] bcrypt 3.2: #17369
[x] cryptography 3.3.1: #15687
[x] PyNaCl 1.4: #17369

Python 3.9 support

Python 3.9 support

Also, the first beta release of Python 3.10 is coming at the beginning of May.

in azure cli pip --version is 3.9 but finction app version is 3.10 getting the http 500 error , and will check in the logs request module not found already we called latest version request module in requirements.txt, is it related to python version issue?


An R package that wraps your code

Hi,
I wrapped your C++ code into an package for the R language. See RcppConcaveman. Then I tried it and I compared it to the R package concaveman that is a wrapper to the original JavaScript code from mapbox using V8.
I found that the output of your implementation is different than the one from the original version. See image below. The read is the original one, the blue is yours

Also I benchmarked it and I found that it was slower than the original JS code. See RcppConcaveman.
I'd like to have your opinion of these two points.

Do you have an idea where the two implementations diverge?
Do you have an idea where your implementation can be speed-up?

Thank you

Hi Jean-Romain,
Thank you for taking interest in my implementation of concaveman. We should
determine what exactly is going on by implementing unit tests for all the
routines that are present in concaveman-cpp and compare their outputs to
the JS homologues. Small deviations can accumulate over the course of a
complex algorithm like this and in the end give seemingly very different
results.
As to the speed-up I had different experience myself, as well as reported
by other users, e.g.
https://github.com/sadaszewski/concaveman-cpp/issues/5#issuecomment-537427384
I would prioritize the unit tests before looking into performance. If you
were willing, we could work on this together, albeit pretty slowly on my
side because I  am seriously overloaded. What do you think?
Best regards,
--
Stanislaw
On Wed, 18 Mar 2020 at 17:01, Jean-Romain<EMAIL_ADDRESS>wrote:

Hi,
I wrapped your C++ code into an package for the R language. See
RcppConcaveman https://github.com/Jean-Romain/RcppConcaveman. Then I
tried it and I compared it to the R package concaveman
https://github.com/joelgombin/concaveman that is a wrapper to the
original JavaScript code from mapbox using V8
https://cran.r-project.org/web/packages/V8/index.html.
I found that the output of your implementation is different than the one
from the original version. See image below. The read is the original one,
the blue is yours
[image: Rplot]
https://user-images.githubusercontent.com/3872279/76980276-62b9ef80-690f-11ea-87a3-005c81a36049.jpeg
Also I benchmarked it and I found that it was slower than the original JS
code. See RcppConcaveman
https://github.com/Jean-Romain/RcppConcaveman#benchmarks.
I'd like to have your opinion of these two points.

Do you have an idea where the two implementations diverge?
Do you have an idea where your implementation can be speed-up?

Thank you
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sadaszewski/concaveman-cpp/issues/10, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKQRXIUBY4OTO55CXFJWBTRIDV6FANCNFSM4LOU2VSA
.

I would prioritize the unit tests before looking into performance.

Of course

we could work on this together

My knowledge about JS is limited to few scripts copy/pasted for websites in the early 2000's but yes why not. I started to clean your code. I mean, I put the rtree in a separate file and I re-indented the code in a way I can read it more easily.  So I can now go more in depth in the code.

As to the speed-up I had different experience myself, as well as reported by other users, e.g.

So somebody already wrapped your code in a R package. The code is strictly identical to mine but yet I can reproduce the benchmark and the version proposed by this user is 5x faster. I will investigate. It's weird.

On Wed, 18 Mar 2020 at 18:52, Jean-Romain<EMAIL_ADDRESS>wrote:

I would prioritize the unit tests before looking into performance.
Of course
we could work on this together
My knowledge about JS is limited to few scripts copy/pasted for websites
in the early 2000's but yes why not. I started to clean your code. I mean,
I put the rtree in a separate file and I re-indented the code in a way I
can read it more easily. So I can now go more in depth in the code.

Perfect. Looking at rtree would be a great place to start. Unit tests for
rbush (the library used by JS concaveman) are available here:
https://github.com/mourner/rbush/blob/master/test/test.js
It would be a great first step to implement the same in C++. Please let me
know if you think this is feasible.
Best regards,
--
Stanislaw

As to the speed-up I had different experience myself, as well as reported
by other users, e.g.
So somebody already wrapped your code in a R package. The code is strictly
identical to mine but yet I can reproduce the benchmark and the version
proposed by this user is 5x faster. I will investigate. It's weird.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sadaszewski/concaveman-cpp/issues/10#issuecomment-600775445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKQRXJMBRMRS6Z33X5M2L3RIEC7JANCNFSM4LOU2VSA
.

Ok for speed it is my fault. It a mistake I added I my R configuration and g++ was not longer compiling with -02. One question solved.

For your information. Your version is 50 times faster when there are very few points (probably because of the overhead introduced by calling JavaScript in R via a V8 wrapper) and tend to be 2 times faster with a lot of points.


⚠ ClamAV has degraded performance

In 2f4beb5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 95 ms

Resolved: ClamAV performance has improved in 68fbaaa.


JAMES-3752 Allow disabling ImapChannelUpstreamHandler heartbeat handler

Jira: https://issues.apache.org/jira/browse/JAMES-3752

Documentation in server/apps/distributed-app/docs ?

yes, it's already in pr
server/apps/distributed-app/docs/modules/ROOT/pages/configure/imap.adoc

Rebase please :-P

Rebase master

Rebase master


pull request for e2e test at 01/12/2017 22:56:13

:white_check_mark: Validation status: passed
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.


mix.scripts/styles/combine() should accept a folder

Just realized that you can't pass a folder path to mix.scripts(), mix.styles(), or mix.combine(). We need to add support for this.

@JeffreyWay Is this recursive or not? AFAIK **/* usually means recursive.
And how does it handle case when we have css, js and others files in one folder?
Thanks.

It's recursive.
You can do mix.scripts('folder/path'), which will combine all nested files. Or mix.scripts('folder/path/*.js') will limit it to only JS files.

Thanks


sbt updates should notify users they may be time consuming

I am unsure if this is the right way to go about this - it seems like maybe the 'reason' variable may have some further information (i.e. "is this the first time sbt is getting run") but I am unsure where apply is called.  Either way, if sbt is being updated, it is likely that the dependencies will also be updated, taking quite some time.
There are a few things I am interested in reviewers commenting on:

Firstly, is this the right way to go about this?
Second, should I have written tests?  It doesn't look like there are many (any?), so I would love to pair up with someone on that since I am new to scala.

Thanks in advance for your help -
James

Since this is about displaying messages on screen, I'm ok with not accompanying test, given that you can run it locally and see that it works.

OK - I changed it so all updates will notify the user that they could take time.  There is another way to do this only for updates to sbt, I could create a string and append it to the println message in the event that it is sbt that is being updated, but that would still tie us to sbt and no other updates.
Also, I squashed the commits down.

@eed3si9n @dwijnand Thanks for your help!


Add upcoming feature flag to SE-0414 to match inclusion in compiler

An upcoming feature flag is included for SE-0414 in the definition of upcoming features in the compiler.
However, the proposal states that there are no source compatibility issues introduced by this feature: https://github.com/apple/swift-evolution/blob/main/proposals/0414-region-based-isolation.md#source-compatibility
This PR adds the upcoming feature flag to the proposal header. The header also includes the new 'Enabled in Swift 6 language mode' annotation to indicating when the feature will be enabled.
However, typically a proposal describes what breaking changes are gated by the upcoming feature flag.
Is there any additional information as to what this upcoming feature flag enables, what changes will take effect if it is enabled prior to Swift 6 language mode?
Will the upcoming feature flag turn on the entire region based isolation feature in Swift 5 language mode?
I would be happy to add any additional information provided to this PR so the effect of the flag is documented in the proposal.
// cc-ing authors and review manager to ask for additional information and ensure this PR is correct
@gottesmm @JTurcotti @hborla

However, the proposal states that there are no source compatibility issues introduced by this feature: https://github.com/apple/swift-evolution/blob/main/proposals/0414-region-based-isolation.md#source-compatibility

Ah, this is incorrect. I think this section of the proposal was not updated after it was revised. The decision notes from both rounds of review include changes the impact source compatibility:

https://forums.swift.org/t/returned-for-revision-se-0414-region-based-isolation/69123
https://forums.swift.org/t/accepted-with-modifications-se-0414-region-based-isolation/70051

Ah, this was already handled when this proposal was accepted, so the diff is now zero.


VerifyCode(secret, code, n, out slice) returns invalid timeslice value

The new methods are working great for my application, but there seems to be a bug.
I am getting slice values that are separated by as little as 6 seconds, and they are not multiples of 30 seconds.  Here is some code:
 for (; ; )
            {
                Console.Write("Enter the Google code: ");
                string code = Console.ReadLine();
                if (code == "")
                    break;

                if (tfa.VerifyCode(secret, code, 2, out slice))
                {
                    if (slice <= lastMatchingTimeSlice)
                        Console.WriteLine("Code is valid, but you already used it");
                    else
                    {
                        Console.WriteLine("Valid code!");
                        lastMatchingTimeSlice = slice;
                    }
                }
                else
                    Console.WriteLine("Invalid code");

                Console.WriteLine();
            }

I assume the timeslice value is supposed to be a unix timestamp rounded down to the previous 30 second boundary, and that it represents the timeslice associated with the matched code.
But I see the following values on one iteration:
slice =<PHONE_NUMBER>
lastMatchingTimeslice =<PHONE_NUMBER>

Is this a bug?  What I am seeing is that my code fails to detect  code reuse if the same code is entered twice.

Can you show the code where you create the tfa object? Are you sure the period isn't set to 6 seconds?

DAMNED... rushed it too hard. There's a bug indeed... instead of timeslices it tracks timestamps. I'll see what I can do.

Must've been too tired from coding all day. It now returns a timeslice instead of a timestamp.
Update your nuget package and it should be fine. 1.3.3

Yes, all is well now.  Thank you.


A release of 4.2

Would it be possible to make a release of version 4.2, on top of this commit?
https://github.com/httpcache4j/httpcache4j/commit/09064268b801d0dee15049f473a7efbc52ae2c2d
FINN.no has an in-house fork of httpcache4j which seems to be based on the code base in that commit. If it were released upstream, it would make it much easier for us to work with the project upstream, since it's much easier to reason about changes.

See if this solves your problem.
Get back to me if this works.
https://oss.sonatype.org/content/repositories/orgcodehaushttpcache4j-1006


[fix] uninitialized constant Cms::PublicFilter::Sass

Coverage decreased (-7.6%) to 70.681% when pulling 8b1a7dc31ce30b1b7b5b51135033ae7c13cf5d39 on itowtips:fix-sass-issue into 9900bf679f18fd52bd09fbfd9df58718b2b57c44 on shirasagi:master.


feat(cta): merging components into one

Related Ticket(s)
#8841
Description
This PR merges all the CTA components into one
Changelog
Changed

CTA is now an individual component that contains the other CTA components within

@IgnacioBecerra this is looking awesome!
We will probably need to update this file here too: https://github.com/carbon-design-system/carbon-for-ibm-dotcom/blob/main/packages/web-components/tools/get-rollup-config.js#L108-L110.
And looks like some tests need some updating since the storybook changed!

@IgnacioBecerra This looks nice from what I can tell from a design perspective :D
A few questions:

Based on the decision to go with Option 1 stated in #8841: Should the CTA story be removed? Or are we keeping that to show how the different CTAs variations?
Do we need to update the functional specs to state that the "CTA" is no longer pulling from a CTA component?

Thanks for the review Olivia!

I feel like we should keep the CTA story since it is still a component that adopters can use, and they might not know about it if it's not there.
Hm I don't think I understand this question, all of these CTA component variations are under the same component with this new PR.

@IgnacioBecerra I think I may have mis-understood the direction when I first read the issue. All good!

@oliviaflory Ah, gotcha! Yeah we're gonna need to, we'd only need a single functional spec for the CTA component. The different types should be denoted in them.


Exchange Metadata Update and Discussion

Hi all,
After a long time of issues and confusion regarding exchange metadata, I finally implemented a solution, which I think is best based on feedback and discussions from the community.
Please see: https://github.com/timmolter/XChange/wiki/Design-Notes section Exchange Metadata.
The metadata for the exchanges (including the currency pairs) should be loaded and accessed from one place and one place only - the Exchange object. This data can be accessed from all the service classes and is loaded once during initialization.
Please test where you can, as I don't have access to all the affected exchanges, especially Kraken, as I had to change the way the currency pairs are parsed.
Also, only a few of the exchanges actually have this 100% perfectly implemented as of right now. It would be appreciated if you could take a look at the code for the exchanges you actively deal with and update the remoteInit method and the hard-coded JSON file appropriately. A good working example is: BleutradeExchange.java.
Please also give feedback on any parts of my implementation including throwing an ExchangeException surrounding the remoteInit() call in BaseExchange.

I should also mention that the default behavior has now changed to always call remoteInit() during the creation of the Exchange instance. It's talked about in the above Wiki link, but for the lazy, I wanted to make that clear here.

If you are going to create an exchange, you will be using the network, right? I wasn't a big fan of that either at first, but can you name one concrete problem with that? Unit testing maybe? Do we need a different mechanism? I'm open to solid reasoning.
It's now exchange.getExchangeSymbols(). I updated the Wiki now. I had a typo there previously.

Can we at least get getExchangeSymbols() back until remoteInit() works as intended?

You can call whatever methods you like on the Raw interfaces. If I took one out somewhere, I apologize.
I purposely do not want the ability to get exchange symbols from both metadata AND through the base service or any generic service method because that causes one of the main problems I'm trying to solve, which is that people are confused on where to code in that functionality and where to call for that data. People seem to be using both places and coding in both places and it's diverging into somewhat of a mess both for devs and users. At version 4.0.0, we decided to move that metadata to it's own special object, and provided some needed functionality for supplementing data not on the exchanges, via the JSON files. V4.1.0 I see as ironing out this mess, and there will be some pain at first, i understand your frustration, but I honestly think it's a small price to pay for what will be a huge step in the right direction for devs and users alike (and for me tending to the resulting issues that keep coming up).

I can think of two good reasons not to make a network call when an Exchange instance is created.

There are going to be times when a user needs to make an Exchange instance directly before placing an order. Most of the demos are examples of this. In the case of exchanges with overly-aggressive throttling (like Kraken), consecutive API calls with no pause in between may result in the second request being rejected. So now a proper implementation would include Thread.sleep being used after getting an Exchange.

In Android, all network calls need to be made on a background thread. This change forces lines  where an Exchange instance is initialized to be put on a background thread, which I don't think is how XChange was meant to be implemented.

I'm also very much against calling remoteInit() (or any other network calls) during Exchange initialization. All of the issues mentioned above seem very valid.
There is no recovery mechanism for situations when remoteInit() repeatedly fails (eg. server/network issues, incorrect/outdated implementation of remoteInit() in the XChange submodule, or others) but other API calls (like market data or placing orders) may succeed, which makes XChange unusable in such cases.
@timmolter can you provide reasons why you decided to include remoteInit in the initialization? (I looked for them both in the wiki and in your above comments, sorry if I missed it.)

@mmazi it was added because many users complaint about exceptions when getting available currency pairs.
My proposition was to add a flag to skip remoteInit() and leave the default behavior as is now.

That solution seems reasonable to me.
On Tue, Jul 12, 2016, 8:42 AM Rafał Krupiński<EMAIL_ADDRESS>wrote:

@mmazi https://github.com/mmazi it was added because many users
complaint about exceptions when getting available currency pairs.
My proposition was to add a flag to skip remoteInit() and leave the
default behavior as is now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/timmolter/XChange/issues/1282#issuecomment-232035539,
or mute the thread
https://github.com/notifications/unsubscribe/ADQIwiiDhSZ6kJHfS4QtYqCBhRECWtGvks5qU4vMgaJpZM4I6xfa
.

Thanks for your input. I'm mostly concerned with a solution that is the most useful/helpful for the most people. So it sounds like a remoteInit flag is all that is now needed, with it being true by default. I'll add that. Feel free to provide more feedback.

My proposition was to add a flag to skip remoteInit() and leave the default behavior as is now.

Seems fine to me too.

OK, I refactored this. See BTERMetaDataDemo for how it works.
One question I have is: What should be the default setting remoteInit true or false?

@timmolter remoteInit should be true, we're adding it to allow a custom initialization for more advanced scenarios. Multiple issue reports showed that most users expect exchange client just working.

I agree with it defaulting to true. The case where it needs to be turned
off is not common, and the average user will probably just expect all meta
data to be up to date automatically.
On Fri, Oct 14, 2016, 7:50 AM Rafał Krupiński<EMAIL_ADDRESS>wrote:

@timmolter https://github.com/timmolter remoteInit should be true,
we're adding it to allow a custom initialization for more advanced
scenarios. Multiple issue reports showed that most users expect exchange
client just working.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/timmolter/XChange/issues/1282#issuecomment-253779539,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADQIwqRhHWEMNPwmWqP7zYR-07Mt-IqTks5qz2xpgaJpZM4I6xfa
.

OK, I set it to true. Thanks!


Update Create-a-Tenant-VM.md

edited the resource id variable passed in step 4 to match the same one that was passed in step 3 of "Create a VM and connect to a Virtual Network by using the Windows PowerShell Network Controller cmdlets"

@george-guirguis : Thanks for your contribution! The author(s) have been notified to review your proposed change. @AnirbanPaul


Better transaction pool error

This trivial change makes debugging experience so much nicer by turning this:
2022-06-10 04:44:12 (offchain call) Error submitting a transaction to the pool: Transaction pool error

Into this:
2022-06-10 04:44:12 (offchain call) Error submitting a transaction to the pool: Transaction pool error: Transaction cannot be propagated and the local node does not author blocks

I think a better fix would be to just fix the Display impl so that it properly prints out the error message.
In general we don't want to print errors through Debug anywhere in the client code if we can help it. (e.g. if the error has a backtrace attached then Display will print it out nicely formatted while Debug will be an unreadable mess dumped on a single line)

Agree, changed to make it print errors using Display

bot merge


Open on a Diagsession file to call Open on the contained Etl resource

This change is to allow the RPS PerfView extension to work with .Diagsession file types. Extensions like RPS that extend the OnFileOpen for .diagsession files need to access the contained Etl resource. The PerfView.DiagSessionPerfViewFile object that is passed in (as pathToFile string) provides access to the Etl file, as an item in its Children collection. However, the PerfView.EtlPerfViewData that is returned does not have any useful data because the Etl file has not had its Open method exercised yet. I did not see a way to force Open on the Etl file from w/n the extension, and I'm not sure that would be the right approach. Instead, the change adds logic to the Open sequence of the .diagsession to also Open the contained Etl resource. The Open sequence calls AddEtlResourcesAsChildren, which is where I now call Open on the first discovered Etl file. I am doing the work on the existing worker for the .diagsession Open, so I created an OpenOnExistingWorker wrapper for the Etl file.

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

@danlev1

The PerfViewTreeItem object model definitely has some warts, but I don't wish to make it worse.    In particular making some parts of the object (in this case a DiagSession file) more expanded (but not completely expanded), feels bad, and that seems to be what is going on here.
It sounds like you are just trying to get your extension working, that has a 'OnFileOpen' hook.   Thus you have the PerfVIewFile, and you just need the ability to open any desired child.
I want to understand why the solution is not just to use the 'Open' method on the child you need.    If it is simply that you don't know how to get a 'parentWindow' and 'StatusBar', it is the case that in other places we use GuiApp.MainWindow and GuiApp.MainWindow.StatusBar to do that.    I don't think that is so bad (indeed, if I were to do it over, I probably would probably create such a default).
There may be other issues that I don't understand.  Please bring them up.   I am interested in understanding your problem enough to give you good advice about the best way to accomplish it.

Thanks Vance! I was not aware of the GuiApp reference and will be exploring that route. I am not seeing GuiApp.MainWindow.StatusBar. Is it an extension?

I am not seeing GuiApp.MainWindow.StatusBar. Is it an extension?
StatusBar is a control on the Main window (See MainWindow.xaml line 135).   If you search for 'MainWindow.StatusBar' you will find it being used a few dozen places where there is not an obviously better place to log things.

Thanks for the feedback. While I see GuiApp.MainWindow.StatusBar calls in the PerfView codebase, I do not see a way to access the StatusBar via the extension project. The project has a reference to PerfView.exe and PresentationCore/PresentationFramework, but GuiApp.MainWindow.StatusBar does not resolve and the project will not build. Am I missing a required reference?
From: Vance Morrison<EMAIL_ADDRESS>Sent: Thursday, December 14, 2017 8:44 AM
To: Microsoft/perfview<EMAIL_ADDRESS>Cc: Dan Leviant<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Microsoft/perfview] Open on a Diagsession file to call Open on the contained Etl resource (#464)
I am not seeing GuiApp.MainWindow.StatusBar. Is it an extension?
StatusBar is a control on the Main window (See MainWindow.xaml line 135). If you search for 'MainWindow.StatusBar' you will find it being used a few dozen places where there is not an obviously better place to log things.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fperfview%2Fpull%2F464%23issuecomment-351766671&data=04|01|danlev%40microsoft.com|b7557d515d254f70a0cf08d54311d5c1|72f988bf86f141af91ab2d7cd011db47|1|0|636488666243047574|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=64RiU%2B6Nq%2FvgiBAobp4TPhmEqfmGwCUYSCVIX1lDdZc%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAgs3K4EqN8moTmdCP3CyysEyt1uHDkU_ks5tAVA8gaJpZM4Q90x8&data=04|01|danlev%40microsoft.com|b7557d515d254f70a0cf08d54311d5c1|72f988bf86f141af91ab2d7cd011db47|1|0|636488666243047574|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=R6HNnAut9i1hrNhShTAV3PH9AWGshtDZasmvYHHTgdE%3D&reserved=0.

The problem is that WPF items are internal by default, so the field is not accessible outside the PerfView executable.
As a trial work-around, we could add this
       public StatusBar GetStatusBar() { return StatusBar; }

But I think a different change is better, where Open has a overload that takes no arguments and implicitly does its work in the 'default' window and StatusBar (that is GuiApp.MainWindow and GuiApp.MainWIndow.StatusBar).
Vance

Codecov Report

Merging #464 into master will increase coverage by 0.04%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #464      +/-   ##
==========================================
+ Coverage   17.52%   17.57%   +0.04%
==========================================
  Files         216      216
  Lines      123061   123228     +167
  Branches    11865    11884      +19
==========================================
+ Hits        21570    21654      +84
- Misses     100630   100710      +80
- Partials      861      864       +3

Flag
Coverage Δ

#2017
17.57% <0%> (+0.04%)
:arrow_up:

#Debug
17.57% <0%> (+0.04%)
:arrow_up:

#Release
100% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

src/PerfView/PerfViewData.cs
4.22% <0%> (-0.02%)
:arrow_down:

src/TraceEvent/ZippedETL.cs
21.22% <0%> (-2.14%)
:arrow_down:

src/PerfView/StackViewer/PerfDataGrid.xaml.cs
34.02% <0%> (-0.21%)
:arrow_down:

src/PerfView/CommandLineArgs.cs
3.77% <0%> (-0.02%)
:arrow_down:

src/PerfView/CommandProcessor.cs
0.17% <0%> (-0.01%)
:arrow_down:

src/PerfView/GuiApp.cs
0% <0%> (ø)
:arrow_up:

src/PerfView/StackViewer/StackWindow.xaml
100% <0%> (ø)
:arrow_up:

src/TraceEvent/RegisteredTraceEventParser.cs
41.56% <0%> (+0.09%)
:arrow_up:

src/PerfView/StackViewer/StackWindow.xaml.cs
26.32% <0%> (+2.18%)
:arrow_up:

Continue to review full report at Codecov.

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

Added Open and OpenOnExistingWorker wrappers that default to use the internal GuiApp.MainWindow and GuiApp.MainWindow.StatusBar in order to simplify the call from an extension.

Closing I rebased the files in PR #544


CNI workload: Change the probe from readinessProbe to startupProbe.

This patch changes the probe in curl-deployment.yml from
readinessProbe to startupProbe for the following reasons:

readinessProbe is periodic and with default period interval of 1
second, it significantly loads kubelet effecting the pod
readiness as the scale increases.

startupProbe is enough to check if CNI has done its job of wiring
the networking of the pods.

Below are the tests on AWS 120 node cluster with 4000 iterations
of kubelet-density-cni
With readinessProbe - ContainerReady
"P99": 80928,
"P95": 66161,
"P50": 9526,
"max": 671045,
"avg": 19321,
With startupProbe - ContainerReady
"P99": 11872,
"P95": 9609,
"P50": 4862,
"max": 18487,
"avg": 5329,

Signed-off-by: Numan Siddique<EMAIL_ADDRESS>Description
Fixes

I can test it out.
Do you know how http probe works ?   If kubelet runs the probe outside of the curl pod (my understanding is that http probe is run by kubelet by not execing to the pod,  I could be wrong though),  then I don't think we will be testing the actual networking from the curl pod to the service and it will be only testing if the server pod is listening on the server port or not.

I can test it out.
Do you know how http probe works ? If kubelet runs the probe outside of the curl pod (my understanding is that http probe is run by kubelet by not execing to the pod, I could be wrong though), then I don't think we will be testing the actual networking from the curl pod to the service and it will be only testing if the server pod is listening on the server port or not.

You are right, we are stuck with exec probes then. Exec probes do tend to be expensive for kubelet/cri-o as well.

We probably could find other ways.
But that would probably require changes in kube-burner.   Maybe each curl pod can log the timestamp when it first successfully curled.  And later kube-burner has to scrape through all the logs and measure the time it took for the curl pod to come up.
This definitely would be very invasive and I'm not sure if it's even  a good idea to worth exploring it :)
Until then "Exec" it is.


[language-service] parsing error for string template variables in a "default argument value" position

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
I'd love to be able to extract default argument values into constants, so I can:

avoid "magic values" in the schema
use the constant default values inside other functions

This is the pattern I'd like to implement:
const schema = gql`
  type ImageAsset {
    src(
      height: Int
      width: Int = ${DEFAULT_WIDTH}
    ): ImageSource!
  }
`;

... which unfortunately leads to a parsing error: Syntax Error: Unexpected ")".

Expected Behavior
vscode-graphql should understand that this is, at the very least, "some default value" (understandable that it probably won't be able to grab the exact value — that would be pretty awesome, though!)
Steps To Reproduce
const schema = gql`
  type ImageAsset {
    src(
      height: Int
      width: Int = ${DEFAULT_WIDTH}
    ): ImageSource!
  }
`;

Environment
- VSCode extension `graphql.vscode-graphql` Version: 0.7.5
- OS: MacOS Ventura (13.0 Beta, build 22A5352e)

Anything else?
No response

@ezracelli the problem here is that graphql-js validate (called by the lsp server) doesn’t understand the template replacement going on here - it just sees a broken graphql string. It should be replacing template string expressions with whitespace in this case as it does with completion and other features

I am encountering the same issue, idid you find a workaround @ezracelli ?

I did not, unfortunately! Just dealt with the red squiggles :grin:


Bundling and publishing extensions as npm packages

Are there any docs that explain how to bundle an extension and publish it as an npm package in the same way you did with the default extensions? Is that possible?
I'm trying to use the vscode-js-debug extension and bundle it as part of my web app. However, it seems like it wasn't designed to work with VSCode Web. I understand that it's possible to have the adapter on the server side, as shown in the demo, but I want to keep the adapter on the client side and attach the VSCode debugger to a running Node.js process.
I understand if this issue might be outside the project's scope so feel free to close it.

Are there any docs that explain how to bundle an extension and publish it as an npm package in the same way you did with the default extensions? Is that possible?

2 rollup plugins are published, they can be used to transform a vsix file or a directory to an importable extension

I'm trying to use the vscode-js-debug extension and bundle it as part of my web app. However, it seems like it wasn't designed to work with VSCode Web. I understand that it's possible to have the adapter on the server side, as shown in the demo, but I want to keep the adapter on the client side and attach the VSCode debugger to a running Node.js process.

If you want you client to be attached to the adapter, you'll need a channel between them. That is exactly what is demoed in the demo here. But you wont be able to reuse the vscode-js-debug to do that.
An alternative is to use the extension host server, and run the debug adapter server side


Endless re-importing with plugins written in GDScript

Operating system or device - Godot version:
Arch Linux x86_64 - Godot 2.1 alpha compiled with  dde995a5134d2421f987200542e50547484d956f
Issue description (what happened, and what was expected):
Editor auto re-import changed files once and once again cannot be stopped.
Steps to reproduce:

Create a project and copy the demo plugin demos/plugins/custom_import_plugin folder into addons under the project.
Active the Silly Materia Importer plugin in project setting.
Copy the demo file addons/custom_import_plugin/test.mtxt outside of the project and import with the Silly Materia Importer plugin.
Edit and save the import source file test.mtxt.
Back to the editor it would start re-import an never stop.

Link to minimal example project
https://drive.google.com/open?id=0B0AolAabr5edQl9KekdWeUdWOWM

This bug kills importers below:

Tiled Importer
Atlas Importer


Add drone ci

Fixes #XXXX.

Description

Fixed the bug ...
Renamed the class ...
Added a forbidden-apis entry ...

This PR has:

[ ] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

Key changed/added classes in this PR

MyFoo
OurBar
TheirBaz

Hi @stuartmclean, thank you for your contribution. Would you please update your PR description properly? It would be nice if it explains how Drone CI is different from Travis CI, why we need it, and how it could be integrated with Github.


vm: allow parsing scientific JSON numbers

Close #3069.
The first commit fixes state difference at block 2336911@T5. After that the new state difference at block 2342940@T5 occurs:
state differs at 2342940, block 254985ed16cb865742971a93b16aa6888aa20ccc7082d56f9e59d2e53ca151ea
transaction 4c9e33b29bb75ae2a77e180f82879195fe541afa04aabe0e4a1a1ec858629938:
--- http://localhost:20332
+++ http://seed1t5.neo.org:20332
@@ -1,2 +1,2 @@
-(*result.ApplicationLog)(0xc00030f7c0)({
+(*result.ApplicationLog)(0xc000039840)({
Container: (util.Uint256) (len=32 cap=32) 38996258c81e1a4a0ebeaa04fa1a54fe959187820f187ea7e25ab79bb2339e4c,
@@ -9,3 +9,3 @@
Stack: ([]stackitem.Item) (len=1 cap=1) {
-    (*stackitem.Array)(0xc0002625a0)(Array)
+    (*stackitem.Array)(0xc0003e2840)(Array)
},

different state found
exit status 1

Something tells me that it's still the same JSON-related issue, but from some other side of view, see the new numbers at the 105 instruction ("[9.05e+28,1.871e+21,3.0366e+32,1e+30]"):
anna@kiwi:~/Documents/GitProjects/nspcc-dev/neo-go$ ./bin/neo-go query tx 4c9e33b29bb75ae2a77e180f82879195fe541afa04aabe0e4a1a1ec858629938 -r http://localhost:20332 -v
Hash:			4c9e33b29bb75ae2a77e180f82879195fe541afa04aabe0e4a1a1ec858629938
OnChain:		true
BlockHash:		254985ed16cb865742971a93b16aa6888aa20ccc7082d56f9e59d2e53ca151ea
Success:		true
Signer:			NMQUeV1hPhNCM4k8x8dXFA25Y8oiDER8yZ (CalledByEntry)
SystemFee:		0.03349697 GAS
NetworkFee:		0.00132852 GAS
Script:			DEBeQh5b5nPV+E55v8+REMpGUqYjEioobzZQ6QSbLQTmCuLHMBJEdCEGkml/wSeg3HT+YKInSL5D0l6M72Kas6XBEcAMIQI3Q0to88Qvxv82bpGWEPmmjbsyesk4dtdqegUcoK8nZhHADCVbOS4wNWUrMjgsMS44NzFlKzIxLDMuMDM2NmUrMzIsMWUrMzBdE8AfDAt1cGRhdGVQcmljZQwUb6vCut1+dKyebIdJvOFmVK9KBbtBYn1bUg==
INDEX    OPCODE       PARAMETER
0        PUSHDATA1    5e421e5be673d5f84e79bfcf9110ca4652a623122a286f3650e9049b2d04e60ae2c730124474210692697fc127a0dc74fe60a22748be43d25e8cef629ab3a5c1    <<
66       PUSH1
67       PACK
68       PUSHDATA1    0237434b68f3c42fc6ff366e919610f9a68dbb327ac93876d76a7a051ca0af2766
103      PUSH1
104      PACK
105      PUSHDATA1    5b392e3035652b32382c312e383731652b32312c332e30333636652b33322c31652b33305d ("[9.05e+28,1.871e+21,3.0366e+32,1e+30]")
144      PUSH3
145      PACK
146      PUSH15
147      PUSHDATA1<PHONE_NUMBER>655072696365 ("updatePrice")
160      PUSHDATA1    6fabc2badd7e74ac9e6c8749bce16654af4a05bb
182      SYSCALL      System.Contract.Call (627d5b52)

Go node stack:
anna@kiwi:~/Documents/GitProjects/nspcc-dev/neo-go$ curl -d '{ "jsonrpc": "2.0", "id": 1, "method": "getapplicationlog", "params": ["4c9e33b29bb75ae2a77e180f82879195fe541afa04aabe0e4a1a1ec858629938"] }' localhost:20332 | json_pp
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   642  100   502  100   140   245k  70000 --:--:-- --:--:-- --:--:--  313k
{
   "result" : {
      "txid" : "0x4c9e33b29bb75ae2a77e180f82879195fe541afa04aabe0e4a1a1ec858629938",
      "executions" : [
         {
            "gasconsumed" : "3316532",
            "trigger" : "Application",
            "notifications" : [],
            "exception" : null,
            "vmstate" : "HALT",
            "stack" : [
               {
                  "type" : "Array",
                  "value" : [
                     {
                        "value" : "90499999999999999999932891136",
                        "type" : "Integer"
                     },
                     {
                        "type" : "Integer",
                        "value" : "1871000000000000000000"
                     },
                     {
                        "type" : "Integer",
                        "value" : "303659999999999999994193741086720"
                     },
                     {
                        "value" : "1000000000000000000024696061952",
                        "type" : "Integer"
                     }
                  ]
               }
            ]
         }
      ]
   },
   "jsonrpc" : "2.0",
   "id" : 1
}

C# node stack:
anna@kiwi:~/Documents/GitProjects/nspcc-dev/neo-go$ curl -d '{ "jsonrpc": "2.0", "id": 1, "method": "getapplicationlog", "params": ["4c9e33b29bb75ae2a77e180f82879195fe541afa04aabe0e4a1a1ec858629938"] }' seed1t5.neo.org:20332 | json_pp
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   641    0   501  100   140    532    148 --:--:-- --:--:-- --:--:--   680
{
   "id" : 1,
   "result" : {
      "executions" : [
         {
            "notifications" : [],
            "gasconsumed" : "3316532",
            "exception" : null,
            "vmstate" : "HALT",
            "stack" : [
               {
                  "type" : "Array",
                  "value" : [
                     {
                        "value" : "90499999999999993918259200000",
                        "type" : "Integer"
                     },
                     {
                        "value" : "1871000000000000000000",
                        "type" : "Integer"
                     },
                     {
                        "value" : "303660000000000004445016810323968",
                        "type" : "Integer"
                     },
                     {
                        "value" : "1000000000000000019884624838656",
                        "type" : "Integer"
                     }
                  ]
               }
            ],
            "trigger" : "Application"
         }
      ],
      "txid" : "0x4c9e33b29bb75ae2a77e180f82879195fe541afa04aabe0e4a1a1ec858629938"
   },
   "jsonrpc" : "2.0"
}

Thus, the PR is not finished, I'll keep investigating.

It turns out that increasing the digint parsing precision from the default up to maximum allowed (big.MaxPrec, as in the current version of this PR) helps and the resulting NeoGo node stack for the second statediff transaction is the following:
anna@kiwi:~/Documents/GitProjects/nspcc-dev/neo-go$ curl -d '{ "jsonrpc": "2.0", "id": 1, "method": "getapplicationlog", "params": ["4c9e33b29bb75ae2a77e180f82879195fe541afa04aabe0e4a1a1ec858629938"] }' http://localhost:20332 | json_pp
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   642  100   502  100   140   163k  46666 --:--:-- --:--:-- --:--:--  208k
{
   "result" : {
      "txid" : "0x4c9e33b29bb75ae2a77e180f82879195fe541afa04aabe0e4a1a1ec858629938",
      "executions" : [
         {
            "vmstate" : "HALT",
            "exception" : null,
            "notifications" : [],
            "trigger" : "Application",
            "gasconsumed" : "3316532",
            "stack" : [
               {
                  "value" : [
                     {
                        "type" : "Integer",
                        "value" : "90500000000000000000000000000"
                     },
                     {
                        "type" : "Integer",
                        "value" : "1871000000000000000000"
                     },
                     {
                        "type" : "Integer",
                        "value" : "303660000000000000000000000000000"
                     },
                     {
                        "value" : "1000000000000000000000000000000",
                        "type" : "Integer"
                     }
                  ],
                  "type" : "Array"
               }
            ]
         }
      ]
   },
   "id" : 1,
   "jsonrpc" : "2.0"
}

These values are exactly the same values that user provides as an input to updatePrice method: [9.05e+28,1.871e+21,3.0366e+32,1e+30]. And these values are stored in the contract storage which affects the state. However, now I see three problems here:

The C# node values differ from the expected, which means inaccuracy in big numbers parsing on the C# node side.
We can't provide the same solid integers parsing for values that are bigger than big.MaxPrec allows.
C# node allows to unmarshal floats from scientific notation (like 1.2345e+3), and it must be no-op. However, I've checked the current testnet, there are no such situations when someone provides floating point scientific number to StdLib's deserializeJSON.

I've described the proposed solution in the https://github.com/neo-project/neo/issues/2879.

Technically, this PR makes everything that possible to makes things better. But we won't go further than 2342940@T5 without https://github.com/neo-project/neo/issues/2879 resolution.

States match up to the current T5 height:
anna@kiwi:~/Documents/GitProjects/nspcc-dev/neo-go$ go run scripts/compare-states/compare-states.go http://localhost:20332 http://seed1t5.neo.org:20332
at 0: 9c1361fbbe2a0ce31910f992cbdfb8afee6f178e5d1aabdd1c6f2af90440e239 vs 9c1361fbbe2a0ce31910f992cbdfb8afee6f178e5d1aabdd1c6f2af90440e239
at 2441424: f00416df2782e5bc3c7d7b92cabd81e17a2b75089a0652460bc164dde4c60a19 vs f00416df2782e5bc3c7d7b92cabd81e17a2b75089a0652460bc164dde4c60a19

Mainnet check is in progress.

Mainnet states match up to the current height:
anna@kiwi:~/Documents/GitProjects/nspcc-dev/neo-go$ go run ./scripts/compare-states/compare-states.go http://localhost:10332 http://seed1.neo.org:10332
at 0: bb2bd2dfee742024b966cdf757c6235044cb9e0ce43497ad0eb27c49b8bdf4fe vs bb2bd2dfee742024b966cdf757c6235044cb9e0ce43497ad0eb27c49b8bdf4fe
at 3849893: 35519c007dfaefea7c483f93eca989ed9b5f2be05707ef7cdf8779987713fec9 vs 35519c007dfaefea7c483f93eca989ed9b5f2be05707ef7cdf8779987713fec9

Ready to be released.


For web page loaders

Feature request
It will be really cool if we can specify a website like : www.example.edu/* and it would get all the possible accessible pages from it and load it using WebBaseLoader.
Motivation
I'm always frustrated when I have to make a list of websites and pass it in the loader. Instead, using this way we can query the loader and we can get all the relevant web pages.
Your contribution
Not sure how I can contribute.

Hey, sure. You can close this issue as I already made a PR and have it
solved!
On Tue, Sep 12, 2023 at 9:03 AM dosu-beta[bot] @.***>
wrote:

Hi, @jackfrost1411 https://github.com/jackfrost1411! I'm Dosu, and I'm
here to help the LangChain team manage their backlog. I wanted to let you
know that we are marking this issue as stale.
From what I understand, you requested a feature to specify a website and
have the WebBaseLoader load all accessible pages from that website. You
mentioned that you were unsure how you could contribute to this feature.
Currently, there hasn't been any activity on the issue, and it remains
unresolved.
Before we close this issue, we wanted to check with you if it is still
relevant to the latest version of the LangChain repository. If it is,
please let us know by commenting on the issue. Otherwise, feel free to
close the issue yourself, or it will be automatically closed in 7 days.
Thank you for your understanding and for your contribution to the
LangChain project! Let us know if you have any further questions or need
any assistance.
—
Reply to this email directly, view it on GitHub
https://github.com/langchain-ai/langchain/issues/6081#issuecomment-1716009424,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALUAQ2FAQXWORU22ZT4XHI3X2CBUBANCNFSM6AAAAAAZEKF6AI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Age Accumulation Buckets

Looks like build is breaking, could you fix that?

Before we start combining buckets to make the custom buckets requested by MSM, it would be worthwhile to spend a bit of time figuring out why the age "16" doesn't show up in the data.. is there a bug in the parsing code somewhere? Does the data itself just not include it?


See if passing keys etc in Travis job can be more transparent

https://docs.gradle.org/current/userguide/build_environment.html

If the environment variable name looks like ORG_GRADLE_PROJECT_prop=somevalue, then Gradle will set a prop property on your project object, with the value of somevalue. Gradle also supports this for system properties, but with a different naming pattern, which looks like org.gradle.project.prop.

Interpret and see if we can use the above

No value - refactor at will while programming


Lack support of qint32 in tf.nn.tanh

According to the doc, the tanh operation supports floating point inputs as well as fixed point inputs of type qint32. However, in the latest master, a TypeError raised when running following code:
import tensorflow as tf
sess = tf.InteractiveSession()
x = tf.constant([1.,2.,3.], dtype=tf.float32)

from tensorflow.python.ops.gen_array_ops import quantize_v2
x_quant = quantize_v2(x, min_range=0., max_range=4., T=tf.qint32)
y_quant = tf.nn.tanh(x_quant[0])

The complete error message is
TypeError: Value passed to parameter 'x' has DataType qint32 not in list of allowed values: float16, float32, float64, complex64, complex128

According to the backend function _tanh in gen_math_ops.py:
def _tanh(x, name=None):
  r"""Computes hyperbolic tangent of `x` element-wise.

  Args:
    x: A `Tensor`. Must be one of the following types: `half`, `float32`, `float64`, `complex64`, `complex128`.
    name: A name for the operation (optional).

It shows that it doesn't support qint32.

@dr4b The Python docstring for tanh and sigmoid says they support various types, e.g. qint32, but fail when those types are passed.
CC: @girving

We gladly accept pull requests on the docs!
(or I can go change the docstring.  What is the actual list of possible types?  We currently seem to say "float, double, int32, complex64, int64, or qint32" which is quite a bit off from "float16, float32, float64, complex64, complex128" in the error message OR the backend "half, float32, float64, complex64, complex128".)

This is just a Python doc error: the C++ op registrations use a reasonable set of types (https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/ops/math_ops.cc#L193) but the Python wrapper does not (https://github.com/tensorflow/tensorflow/blob/master/tensorflow/python/ops/math_ops.py#L2061).


landscape.io: reduce number of reported errors

I checked and there are a few that don't make sense.
I'll go through this and clean it up a bit.

👋 Hey! Thanks for this contribution. Apologies for the delay in responding!
We've decided to rearchitect Storj, so that we can scale better. You can read more about this decision here. This means that we are entirely focused on v3 at the moment, in the storj/storj repository. Our white paper for v3 is coming very, very soon - follow along on the blog and in our Rocketchat.
As this repository is part of the v2 network, we're no longer maintaining this repository. I am going to close this for now. If you have any questions, I encourage you to jump on Rocketchat and ask them there. Thanks!