Space erroneously removed between a pair of coordinates

I got a weird error. After turning off all conversions I still got the error. It turned out that svgo had removed a space in a path resulting in a concatenation of two separate values into one value.
Unfortunately, the problem is intermittent. After several tries on the same file I got a couple of successful ones and a couple of bad ones. The error always showed up in this particular path, but in different places.
original coordinate pair:
3.027 6.943
Converted coordinate pair:
3.0276.943
Here is the complete path that gets trashed. The error happens towards the end of the path (about 15 pairs from the end)
Input path:
<path d="M7.455,3.079C7.345,3.079 7.235,3.108 7.125,3.167C7.017,3.227 6.892,3.326 6.754,3.465C6.714,3.504 6.672,3.548 6.627,3.597C6.581,3.646 6.532,3.697 6.483,3.751C6.433,3.805 6.382,3.86 6.332,3.915C6.282,3.973 6.233,4.027 6.185,4.08C6.261,4.215 6.339,4.351 6.419,4.486C6.498,4.622 6.577,4.753 6.657,4.879C6.738,5.005 6.818,5.123 6.902,5.233C6.985,5.344 7.068,5.439 7.151,5.52C7.233,5.602 7.318,5.665 7.402,5.712C7.485,5.759 7.57,5.783 7.653,5.783L7.689,5.783L7.689,5.914C7.621,5.932 7.559,5.945 7.501,5.954C7.443,5.963 7.369,5.967 7.279,5.967C7.187,5.967 7.1,5.945 7.017,5.901C6.934,5.857 6.852,5.797 6.775,5.72C6.697,5.643 6.621,5.553 6.545,5.45C6.472,5.348 6.399,5.237 6.327,5.119C6.254,5.001 6.183,4.878 6.111,4.751C6.04,4.624 5.967,4.499 5.893,4.376C5.879,4.392 5.86,4.414 5.833,4.441C5.808,4.468 5.782,4.497 5.757,4.526C5.729,4.555 5.704,4.582 5.682,4.608C5.658,4.633 5.642,4.652 5.632,4.664L5.632,5.935L5.224,5.935L5.224,2.935L5.632,2.935L5.632,4.37C5.668,4.326 5.713,4.273 5.763,4.212C5.814,4.152 5.869,4.088 5.926,4.02C5.984,3.953 6.043,3.883 6.104,3.811C6.164,3.741 6.223,3.673 6.28,3.609C6.335,3.544 6.39,3.484 6.441,3.429C6.492,3.373 6.536,3.326 6.572,3.289C6.644,3.217 6.71,3.158 6.769,3.11C6.827,3.064 6.886,3.027 6.943,3.001C7,2.975 7.06,2.956 7.121,2.945C7.184,2.935 7.254,2.929 7.334,2.929C7.371,2.929 7.404,2.93 7.431,2.935C7.458,2.939 7.48,2.944 7.496,2.949L7.496,3.079L7.455,3.079Z" style="fill:rgb(35,31,32);fill-rule:nonzero;"/>

Output path:
<path d="M7.455,3.079C7.345,3.079 7.235,3.108 7.125,3.167C7.017,3.227 6.892,3.326 6.754,3.465C6.714,3.504 6.672,3.548 6.627,3.597C6.581,3.646 6.532,3.697 6.483,3.751C6.433,3.805 6.382,3.86 6.332,3.915C6.282,3.973 6.233,4.027 6.185,4.08C6.261,4.215 6.339,4.351 6.419,4.486C6.498,4.622 6.577,4.753 6.657,4.879C6.738,5.005 6.818,5.123 6.902,5.233C6.985,5.344 7.068,5.439 7.151,5.52C7.233,5.602 7.318,5.665 7.402,5.712C7.485,5.759 7.57,5.783 7.653,5.783L7.689,5.783L7.689,5.914C7.621,5.932 7.559,5.945 7.501,5.954C7.443,5.963 7.369,5.967 7.279,5.967C7.187,5.967 7.1,5.945 7.017,5.901C6.934,5.857 6.852,5.797 6.775,5.72C6.697,5.643 6.621,5.553 6.545,5.45C6.472,5.348 6.399,5.237 6.327,5.119C6.254,5.001 6.183,4.878 6.111,4.751C6.04,4.624 5.967,4.499 5.893,4.376C5.879,4.392 5.86,4.414 5.833,4.441C5.808,4.468 5.782,4.497 5.757,4.526C5.729,4.555 5.704,4.582 5.682,4.608C5.658,4.633 5.642,4.652 5.632,4.664L5.632,5.935L5.224,5.935L5.224,2.935L5.632,2.935L5.632,4.37C5.668,4.326 5.713,4.273 5.763,4.212C5.814,4.152 5.869,4.088 5.926,4.02C5.984,3.953 6.043,3.883 6.104,3.811C6.164,3.741 6.223,3.673 6.28,3.609C6.335,3.544 6.39,3.484 6.441,3.429C6.492,3.373 6.536,3.326 6.572,3.289C6.644,3.217 6.71,3.158 6.769,3.11C6.827,3.064 6.886,3.0276.943,3.001C7,2.975 7.06,2.956 7.121,2.945C7.184,2.935 7.254,2.929 7.334,2.929C7.371,2.929 7.404,2.93 7.431,2.935C7.458,2.939 7.48,2.944 7.496,2.949L7.496,3.079L7.455,3.079Z" style="fill:#231f20;fill-rule:nonzero"/>

Here is the complete SVG file (renamed to .txt to enable uploading)
test.txt

Seems to be correlated: https://github.com/smooth-code/svgr/issues/342

No, it doesn't related, and is totally ok. See #1137, it's some other software doesn't support correct SVG.


Permission denied in logstash pipeline

I am creating custom configuration for logstash and in docker-compose I am using:
logstash:
    build:
      context: logstash/
    volumes:
      - ./logstash/config/logstash.yml:/usr/share/logstash/config/logstash.yml:ro
      - ./logstash/pipeline:/usr/share/logstash/pipeline:ro
      - ./logstash/data:/usr/share/logstash/data

In logstash/pipeline I am placing two files, i.e. one main.conf and a filter.conf.
In the first one:
input {

  file {
    path => "/usr/share/logstash/data/a_huge_logfile.log"
    start_position => "beginning"
  }

}

When logstash service starts:
logstash_1       | [2018-03-21T17:06:38,391][FATAL][logstash.runner          ] An unexpected error occurred! {:error=>#<Errno::EACCES: Permission denied - /logstash_data>, :backtrace=>["org/jruby/RubyDir.java:449:in `mkdir'", "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/fileutils.rb:253:in `fu_mkdir'", "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/fileutils.rb:227:in `block in mkdir_p'", "org/jruby/RubyArray.java:1818:in `reverse_each'", "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/fileutils.rb:225:in `block in mkdir_p'", "org/jruby/RubyArray.java:1734:in `each'", "uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/fileutils.rb:211:in `mkdir_p'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-file-4.2.1/lib/logstash/outputs/file.rb:278:in `open'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-file-4.2.1/lib/logstash/outputs/file.rb:135:in `block in multi_receive_encoded'", "org/jruby/RubyHash.java:1343:in `each'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-file-4.2.1/lib/logstash/outputs/file.rb:134:in `block in multi_receive_encoded'", "org/jruby/ext/thread/Mutex.java:148:in `synchronize'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-file-4.2.1/lib/logstash/outputs/file.rb:133:in `multi_receive_encoded'", "/usr/share/logstash/logstash-core/lib/logstash/outputs/base.rb:90:in `multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator_strategies/shared.rb:13:in `multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/output_delegator.rb:49:in `multi_receive'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:479:in `block in output_batch'", "org/jruby/RubyHash.java:1343:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:478:in `output_batch'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:430:in `worker_loop'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:385:in `block in start_workers'"]}

From within the specific container:
bash-4.2$ ls -ald /usr/share/logstash/data/
drwxrwxr-x 5 logstash logstash 4096 Mar 21 16:44 /usr/share/logstash/data/

Where does the permission error come from?

Hi thx for the feedback;
The combination of 1) and 2) gave me this:
logstash_1       | [2018-03-22T08:20:43,161][FATAL][logstash.runner          ] An unexpected error occurred! {:error=>#<ArgumentError: Path "/usr/share/logstash/data/queue" must be a writable directory. It is not writable.>, :backtrace=>["/usr/share/logstash/logstash-core/lib/logstash/settings.rb:448:in `validate'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:230:in `validate_value'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:141:in `block in validate_all'", "org/jruby/RubyHash.java:1343:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/settings.rb:140:in `validate_all'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:264:in `execute'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/clamp-0.6.5/lib/clamp/command.rb:67:in `run'", "/usr/share/logstash/logstash-core/lib/logstash/runner.rb:219:in `run'", "/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/clamp-0.6.5/lib/clamp/command.rb:132:in `run'", "/usr/share/logstash/lib/bootstrap/environment.rb:67:in `<main>'"]}
logstash_1       | [2018-03-22T08:20:43,182][ERROR][org.logstash.Logstash    ] java.lang.IllegalStateException: org.jruby.exceptions.RaiseException: (SystemExit) exit

I tried to chmod back to 1000:1000 and 777 everything and still getting the initial error..

chmod 777 is generally a bad idea, but chown 1000 is indeed mandatory on Linux.
What surprises me is this error message: Permission denied - /logstash_data. I don't see this directory in your configuration, yet it's causing trouble.

From within the logstash container:
bash-4.2$ sudo ls
bash: sudo: command not found
bash-4.2$ find / -iname "*logstash_data*"
find: ‘/var/cache/ldconfig’: Permission denied
find: ‘/var/lib/yum/history/2018-01-07/4’: Permission denied
find: ‘/var/lib/yum/history/2018-01-07/3’: Permission denied
find: ‘/var/lib/yum/history/2018-01-07/1’: Permission denied
find: ‘/var/lib/yum/history/2018-01-07/2’: Permission denied
find: ‘/var/lib/machines’: Permission denied
find: ‘/root’: Permission denied
find: ‘/proc/tty/driver’: Permission denied

That's expected and perfectly fine since logstash doesn't run as root. I don't see any logstash related directory here.

Aha, interesting, looks like it's trying to create that directory:
org/jruby/RubyDir.java:449:in mkdir'"`

Looks to me like you started with some sample config (this? https://gist.github.com/nicolaihald/5dd066aa29b312252c7485c32f4b0b77) and forgot to clean the reference to that particular directory in one of your pipeline files?

Yes I am using /logstash_data in my output pipeline, it just came to me.
I am switching it to /data which gets created on the container either way and is owned by logstash user.
many thanks.

Just for the record, my pipeline is (supposed to be) and I have extremely simplified things using:
a) 0_1_input.conf
input {

  file {
    path => "/usr/share/logstash/data/some_log_file.log"
  }
}

b) 0_2_output.conf
output {
    stdout {
      codec => json_lines
    }
  }

However the combined docker-compose logs are stuck forever at this point:
logstash_1       | Sending Logstash's logs to /usr/share/logstash/logs which is now configured via log4j2.properties
logstash_1       | [2018-03-22T10:40:12,781][INFO ][logstash.modules.scaffold] Initializing module {:module_name=>"netflow", :directory=>"/usr/share/logstash/modules/netflow/configuration"}
logstash_1       | [2018-03-22T10:40:12,810][INFO ][logstash.modules.scaffold] Initializing module {:module_name=>"fb_apache", :directory=>"/usr/share/logstash/modules/fb_apache/configuration"}
logstash_1       | [2018-03-22T10:40:13,745][WARN ][logstash.config.source.multilocal] Ignoring the 'pipelines.yml' file because modules or command line options are specified
logstash_1       | [2018-03-22T10:40:15,091][INFO ][logstash.runner          ] Starting Logstash {"logstash.version"=>"6.2.2"}
logstash_1       | [2018-03-22T10:40:15,852][INFO ][logstash.agent           ] Successfully started Logstash API endpoint {:port=>9600}
logstash_1       | [2018-03-22T10:40:19,128][INFO ][logstash.pipeline        ] Starting pipeline {:pipeline_id=>"main", "pipeline.workers"=>4, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>50}
logstash_1       | [2018-03-22T10:40:19,968][INFO ][logstash.pipeline        ] Pipeline started succesfully {:pipeline_id=>"main", :thread=>"#<Thread:0x58cb91de run>"}
logstash_1       | [2018-03-22T10:40:20,272][INFO ][logstash.agent           ] Pipelines running {:count=>1, :pipelines=>["main"]}

The input file does exist: (following is from within the container:
bash-4.2$ ls -al /usr/share/logstash/data/some_log_file.log
-rwxrwxrwx 1 logstash logstash 727460 Mar 22 09:17 //usr/share/logstash/data/some_log_file.log

Looks good to me. Don't you see any data in Elasticsearch?

Kibana says:

Couldn't find any Elasticsearch data

Either way I am not sending them explicitly to ES;
The question is why the above simple configuration does not just simply print the contents of
path => "/usr/share/logstash/data/some_log_file.log"
to stdout.

Looks good to me. Don't you see any data in Elasticsearch?

@pkaramol unfortunately I have no idea about the stdout output. Did you ask in the Elastic discussion forums?
Regardless, since the initial problem is now solved I'm gonna go ahead and close this.
You can still comment below of course.


Fix IE11 option select bug

https://trello.com/c/AIVquUYj/1988-ccsrequests-re-g-cloud-12-filters-not-working
IE11 does not support element.remove(), so we can replace with element.parentNode.removeChild(element)
Tested on Browserstack and local Windows VM.

Tested on Browserstack and local Windows VM

Have you tested on Chrome?

Tested on Browserstack and local Windows VM

Have you tested on Chrome?

Chrome, Firefox, Safari and mobile browsers look good to me


getMaxSupportedCssHeight performance issue

Can you make the maxSupportedCssHeight variable shared across all grids on the page (similar to the scrollbarDimensions variable)? Otherwise, it is called on every grid initialization, which is slow in IE7 (about 250ms). With only 1 grid it's not too noticeable, but I have a page with about 15 grids on it (for various popup information) and performance becomes an issue.
Thanks for considering the change.

Implemented in https://github.com/mleibman/SlickGrid/commit/6634f168da6a03ce36a4a63c83f9acd1c33cbd5d.


Review/897/refactoring

I split my post-review work into two parts. This one deals with refactoring only.

Also, I feel we should be using dashed - rather than underscored - fields for serialized sensor/asset attributes in our database. This should results in a more consistent experience to API/UI users in the long run. We could of course make that a separate issue, but we are introducing two new fields in #897, so we might as well tackle those there. What do you think @victorgarcia98?
If you agree, let's hold off on refactoring until merging this PR and also after considering my next post-review PR, to save us the merge conflicts.

Also, I feel we should be using dashed - rather than underscored - fields for serialized sensor/asset attributes in our database. This should results in a more consistent experience to API/UI users in the long run. We could of course make that a separate issue, but we are introducing two new fields in #897, so we might as well tackle those there. What do you think @victorgarcia98?

You're right, this is worth its own issue. In any case, we should mix dashed and underscored in the DB.

If you agree, let's hold off on refactoring until merging this PR and also after considering my next post-review PR, to save us the merge conflicts.


Acala network stake $ACA not support

Acala network stake $ACA not support，https://github.com/AcalaNetwork/Acala/issues/2668#issue-2035739696

:link: zboto Link

Hi @okmind, here you have a list of all pallets and calls supported by the Acala Ledger app. Can you tell me which is the one that is not supported?
Check also that if you are using NanoS, you'll need to install the XL version.
https://github.com/Zondax/ledger-acala/blob/main/README.md

OK. There is my ledger information and acala version
Ledger: Nano X
Acala version: 3.2180.2

As Bryan stated https://github.com/AcalaNetwork/Acala/issues/2668#issuecomment-1850985170 staking is not supported in Ledger Acala app. According to acala docs, you have an option with proxy.


Preventing XSS

Not sure if I'm missing something obvious here, but how do I prevent XSS?
I've been able to insert a script alert function into the database and I can't see anywhere to add the validator to prevent this.
Line 32 on src/resources/views/usersmanagement/show-user.blade.php

{!! trans('laravelusers::laravelusers.showing-user-title', ['name' => $user->name]) !!}

This should be {{ }} instead of {!! to prevent raw output
Thanks

Looking at the code, there are several places where the code is rendering raw HTML instead of sanitized text. For example, the show-user.blade.php, Line 32 is using:
{!! trans('laravelusers::laravelusers.showing-user-title', ['name' => $user->name]) !!}

but should ideally be:
{{ trans('laravelusers::laravelusers.showing-user-title', ['name' => $user->name]) }}

If $user->name is not sanitised, it allows XSS issues like <script>alert('XSS');</script> being outputted on the page. There are a few instances of this issue in the code.

Validators are in the controller.
https://github.com/jeremykenedy/laravel-users/blob/master/src/App/Http/Controllers/UsersManagementController.php
It’s supposed to render raw HTML and xss is protected by the csfr token.
If you make a or to update the rules I accept it.

Unfortunately, the CSRF token is not protecting against a user entering <script>alert('XSS');</script> into the "name" field. The blade will output this as a raw script tag allowing code execution.

If the rules are updated I will accept the pr.
Thanks

If I don't see a PR come across this AM I am going to take a closer look at this and its high priority.

Sorry, I'm not using this library. I just discovered this issue in a project while conducting a security review. Depending on the user of the "name" field, the issue can be resolved using rule 'regex:/[a-zA-Z\-\' ]+$/' or built-in validation rule alpha_dash.
The regex rule allows any alpha characters as well as dashes, apostrophes and spaces, which should be sufficient for names.

#65 PR submitted, might need further implementation around resource translation strings

Thank you both!

I also added strip_tags https://github.com/jeremykenedy/laravel-users/commit/44bee8aecf6074c5aa90192d66b9d35ca24cf339


Fix API so linking with c++ projects is possible

I mean, it works lmao

Merged in master, thanks for the contribution!


Add resource filtering when retrieving personal contact address in SBL

Description
UnitProfiles controller exposes an endpoint that accepts a list of organization numbers and returns a set of PartyNotificationContactPoints.
This endpoint should be extended to accept a resource id as input and only return contact points that accept notifications related to the resource.
Tasks

[x] Implement lookup model to use as request body that contains list of org numbers and resourceId{
	"resourceId": "app_ttd_apps-test",
	"organizationNumbers": ["1234567", "1234567"]
}

[x] Alter InvalidEndpoint in unit endpoint consumer to also check for matching service filter
[x] Remove obsolete endpoint that takes GUID as input.
[x] QA
[x] Manual test

Acceptance criteria

[x] When querying personal contact address for unit only users that have specified the resource or no resources at all should be included in the result set
[ ] If no resource is included in lookup, no user registered contact points are included in the response

[ ] If no resource is included in lookup, no user registered contact points are included in the response

This is not the case. The endpoint does return contact points. Provided that the user has registered contact info without a specific service selected. So if the ServiceNotificationOptions is null or empty. In that case the resource id is not used in filtering.
This behavior is okay, but it also means that Notification needs to abstain from performing the call to Profile in cases where resource is unspecified.

Tested ok.


Extended memory games not working!

3DS: B9S 1.3 + Luma 8.1.1
Sumo isn't working, hangs on blackscreen, Hard reset needed,

Will work on fixing the issue tonight
On Oct 25, 2017 11:28, "Quazi Irtiza"<EMAIL_ADDRESS>wrote:

B9S 1.3 + Luma 8.1.1
Sumo isn't working
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Ordim3n/A9SP/issues/5, or mute the thread
https://github.com/notifications/unsubscribe-auth/APhmeEbiyHDIJ22Fcy33gAWqy59WKXqBks5sv1OCgaJpZM4QGMmv
.

Same as issue#4


Spec Export not working

I actually get an error message.
I'm running Sketch 52.2 and Sketch Measure 2.7.6.

Please Help!

https://github.com/utom/sketch-measure/pull/474#issuecomment-429220811
Solved! Thanks!

在哪里获取2.7.6版本，我的也失效了

I followed all of your un-install and re-install instructions to the T. I'm working with Sketch version 54.1. I tried downloading your latest zip file to install the 2.7.8 version of Measure but when I install it I'm still seeing the 2.7.7 version showing up in my plugin manager. Please advise or send the latest file asap.


[feature] Plugins de medio de pago

//Description
Implementación de plugin de medio de pago y plugin de pago.
Se agregaron algunos ajustes en Hooks para que se integren mejor con plugins.
//Issue related
Closes #
Requirements

[ ] Coverage > 90%

Note:

[ ] Android Lint check

Note:

[ ] Code Style checked

Note:

[ ] Tested with "Don't keep Activities" configuration.

Note:
If impacts documentation (new components, inputs or outputs?)

[ ] PR to develop-docs

Note:

@nfortunato Travis tira error por lo siguiente:
PaymentVaultPresenterTest.MockedView is not abstract and does not override abstract method showPluginOptions

Codecov Report

Merging #763 into develop will decrease coverage by 0.29%.
The diff coverage is 8.4%.

@@            Coverage Diff             @@
##           develop     #763     +/-   ##
==========================================
- Coverage    24.78%   24.48%   -0.3%
==========================================
  Files          253      264     +11
  Lines        18144    18482    +338
  Branches      1539     1575     +36
==========================================
+ Hits          4497     4526     +29
- Misses       13137    13443    +306
- Partials       510      513      +3

Impacted Files
Coverage Δ

...main/java/com/mercadopago/model/PaymentResult.java
86.2% <ø> (ø)
:arrow_up:

...ain/java/com/mercadopago/GuessingCardActivity.java
0% <ø> (ø)
:arrow_up:

...va/com/mercadopago/preferences/FlowPreference.java
89.88% <ø> (ø)
:arrow_up:

...va/com/mercadopago/core/MercadoPagoComponents.java
18.39% <ø> (ø)
:arrow_up:

...om/mercadopago/providers/CheckoutProviderImpl.java
0% <0%> (ø)
:arrow_up:

...rc/main/java/com/mercadopago/CheckoutActivity.java
0% <0%> (ø)
:arrow_up:

...a/com/mercadopago/components/LoadingComponent.java
0% <0%> (ø)
:arrow_up:

...ain/java/com/mercadopago/PaymentVaultActivity.java
26.99% <0%> (-0.19%)
:arrow_down:

...ercadopago/providers/PaymentVaultProviderImpl.java
42.85% <0%> (ø)
:arrow_up:

...a/com/mercadopago/plugins/PaymentResultAction.java
0% <0%> (ø)

... and 49 more

Continue to review full report at Codecov.

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


Income vs Expense Uh-oh! error

Defective ToolKit Feature Name: Income vs Expense report
Expected Behavior
Not crash
Actual Behavior
Crash
Steps to Reproduce the Behavior

Select Reports
Select Income vs Expense
Crash

Now since the toolkit remembers settings, I can't look at any reports because it crashes immediately upon selecting the reports button.
I do have some income that doesn't have a payee (perhaps in a split?). The previous version had an annoying popup that warned me about it. Every time. I don't know if that is related.
Export of Toolkit Settings (Bottom Left of Settings Page)
[{"key":"accountTransactionSearch","value":true},{"key":"accountsDisplayDensity","value":"1"},{"key":"accountsEmphasizedOutflows","value":true},{"key":"accountsSelectedTotal","value":true},{"key":"accountsStripedRows","value":true},{"key":"activityTransactionLink","value":true},{"key":"budgetBalanceToZero","value":true},{"key":"budgetProgressBars","value":"both"},{"key":"budgetQuickSwitch","value":false},{"key":"budgetRowsHeight","value":"1"},{"key":"categoryActivityPopupWidth","value":"1"},{"key":"changeEnterBehavior","value":true},{"key":"checkCreditBalances","value":true},{"key":"checkNumbers","value":true},{"key":"collapseExpandBudgetGroups","value":true},{"key":"collapseSideMenu","value":false},{"key":"colourBlindMode","value":false},{"key":"currentMonthIndicator","value":true},{"key":"daysOfBuffering","value":true},{"key":"daysOfBufferingHistoryLookup","value":"12"},{"key":"editButtonPosition","value":"2"},{"key":"enableRetroCalculator","value":true},{"key":"enlargeCategoriesDropdown","value":true},{"key":"enterInRegisterNow","value":true},{"key":"exportTransactions","value":false},{"key":"goalIndicator","value":true},{"key":"goalIndicatorWarningColor","value":true},{"key":"googleFontsSelector","value":"0"},{"key":"hideAOM","value":false},{"key":"highlightNegativesNegative","value":true},{"key":"importNotification","value":true},{"key":"incomeFromLastMonth","value":"1"},{"key":"l10n","value":"0"},{"key":"largerClickableIcons","value":false},{"key":"monthlyNotesPopupWidth","value":"1"},{"key":"moveMoneyAutocomplete","value":false},{"key":"moveMoneyDialog","value":false},{"key":"pacing","value":"0"},{"key":"printingImprovements","value":true},{"key":"privacyMode","value":"0"},{"key":"reconciledTextColor","value":"0"},{"key":"removePositiveHighlight","value":true},{"key":"removeZeroCategories","value":true},{"key":"reports","value":true},{"key":"resizeInspector","value":true},{"key":"rightClickToEdit","value":true},{"key":"runningBalance","value":false},{"key":"seamlessBudgetHeader","value":false},{"key":"showIntercom","value":true},{"key":"splitKeyboardShortcut","value":true},{"key":"splitTransactionAutoAdjust","value":true},{"key":"squareNegativeMode","value":true},{"key":"swapClearedFlagged","value":false},{"key":"toBeBudgetedWarning","value":false},{"key":"toggleSplits","value":false},{"key":"toggleTransactionFilters","value":"2"},{"key":"warnOnQuickBudget","value":true}]

System Settings
ToolKit Version: 0.7.2
Operating System (Mac/Windows/Etc): Windows
Browser (Chrome/Firefox/Safari): Chrome
Browser Version:  Version 52.0.2743.116 m
Other Extensions: LastPass, Addblock+

@darthnice this is a duplicate of #504 and a fix will be available in our next release :D thanks!

Is this any better for you in v0.7.3? It should be.

I'll go ahead and close this off as it seems to be resolved for others that were experiencing the same issue. If you're still having trouble please let us know.

Yes it fixed it. On vacation and didn't log in to YNAB for a few days. Thanks!


Connect database to docker image in our end to end tests

Not exactly sure of the best way to go about this but we will need to connect a working database to our docker image to run our cypress tests against for it to truly be 'end to end'.

Is this need to be done in this sprint?

Old ticket, this is done


I want to contribute for translation to Spanish

How can begin?

anyone?

Please check the Telegram group: https://t.me/joinchat/AOpS_1GWEumgdvpczbTlIg
You can ask there, but the project is sleepy ;)

dear teach me pls how can translate to es, de and fr


Suggestion: async block instead of top-level await

I'm interested in hearing people's opinion on addressing the issue of "main" modules by using an "async block".
async {
  const dynamic = await import('./dynamic-thing.mjs');
  const data = await fetch(dynamic.url);
  console.log(data);
}

// same as
(async () => {
  const dynamic = await import('./dynamic-thing.mjs');
  const data = await fetch(dynamic.url);
  console.log(data);
})();

It seems that the main use for top-level await is for "main" modules that initialize and wire together a bunch of other modules. This is easily solves with an IIAFE, but it's ugly.
This problem reminds me of the issue JavaScript had before the introduction of const, let, and blocks. If we wanted a local variable and not pollute the greater function scope or even worse the global scope, we had to create IIFEs. But then lexical scoping and bare blocks were introduced. So, why not apply a similar solution to a similar problem?
In terms of how an async block would behave in the middle a normal function, it should work the same as an IIAFE. It's just sugar to make main modules more pleasant. I believe async blocks should be easier to include in the language without much trouble and the limitations know to top-level await.

Duplicate of #11?

I'm interested in hearing people's opinion on addressing the issue of "main" modules by using an "async block".

Many of the illustrative examples might not occur in a "main" module but a supporting module, e.g. reading an ini file in a module exporting the configuration.
"async blocks" still have the drawback of requiring extra indentation. There is not much advantage over IIAFEs. That said, they have been discussed before, e.g. here or there; there even is a proposal.

closing. duplicate of #11


Can’t subscribe/unsubscribe ?

Steps to reproduce:
In inbox click the speaker icon to flip its state
Pull down to refresh.
The icon is back to its previous state
Anyone else?
Sent with GitHawk

So it comes from this line:
https://github.com/GitHawkApp/GitHawk/blob/8452d73ab9aab9db3891dce102c4b1574acc95d0/Classes/Notifications/Notification%2BNotificationViewModel.swift#L44
I guess the issue is that the notification hasn't been read yet, so it won't disappear. The behavior could be that marking this also marks the notification read? There isn't any other real way to get "watching" status from the V3 API. I guess we could also fetch this info in the GraphQL request for the issue.

Question as it’s “semi” related. Is there, conceptually a way to unmark a marked item in your inbox as read to add back to active badge count.

@ijm8710 Sadly there's not 😢 I wish there were so I could unmark things


[Request]: Add support for Genshin Impact FPS unlocker

Is your request related to a problem?
No
How is the feature request related to the problem?
Adds the ability to run Genshin Impact above 60fps using external tool.
Describe your proposed solution
By adding the integration of this project
https://github.com/34736384/genshin-fps-unlock
Describe alternatives you've considered
I know this can break the game's ToS, but having this as an option would be good. If this proposal got refused, then fine by me.
Additional context
No response

Hi! Thank you for submitting enhancement request for our project!
Unfortunately, due to inherent risk of the Genshin FPS unlocking method (direct memory read/write), we can not implement said feature. For further read, you can go to my comment on the other thread at the link below
https://github.com/CollapseLauncher/Collapse/issues/104#issuecomment-1510430982
Thank you for your understanding!

@farsdewibs0n
You can somewhat achieve this unofficially and on your own risk.
Using this method, you can even add more/other software to run before running Genshin like GIMI, DXVK libs, ReShade etc. (may require modification)

Advanced settings - Enabled ✅
Commands to be executed before the game is launched - Enabled ✅
Force exit launched process when Game is closed/stopped - Disabled ⛔

Code:
powershell.exe -Command "$unlockerpath='C:\Genshin Impact FPS Unlocker'; cd $unlockerpath; while (-not (Get-Process -Name 'GenshinImpact' -ErrorAction SilentlyContinue)) { Start-Sleep -Seconds 1 }; Stop-Process -Name 'GenshinImpact' -Force; (Get-Process -Name 'unlockfps_nc' -ErrorAction SilentlyContinue) | Stop-Process -Force; Start-Process \"$unlockerpath\\unlockfps_nc.exe\""
You only need to change "$unlockerpath='C:\Genshin Impact FPS Unlocker" to your own path where you copied/downloaded fps unlocker (unlockfps_nc.exe)

Problems I noticed with this method:

Collapse Launcher doesn't count play time correctly


Download Docker-Compose-v2 automatically if necessary

Fixes #62
Continue #87

Don't open a PR every time and git push -f directly onto the original branch

git push -f
ok

/ok-to-test

/retitle Download Docker-Compose-v2 automatically if necessary

Delete the download docker-compose logic from CI for test the patch is working

Delete the download docker-compose logic from CI for test the patch is working
You missed that comment

Fixed by #104
/close


Update miscellaneous-examples.md

Sorry, but I'm gonna have to decline this. There are many things in this that don't fit with the rest of the guide, such as:

It doesn't provide any description of what the snippet does.
It assumes this would need to go in a different file, and doesn't follow this guide's command handling syntax.
It doesn't comply with the ESLint config file we use.

But the biggest thing would be that it's simply too niche; I don't think many users who read the guide could benefit from this, which is the guide's goal.
Thanks anyway, though!


automatic cleanup of upgrade jobs

Is your feature request related to a problem? Please describe.
This controller purposely orphans upgrade jobs after they have been scheduled to make reasoning about system state less of a shot-in-the-dark but this can result in jobs and their pods, long since complete, hanging around and polluting kubectl output. We should consider cleaning up stale jobs every so often.
Describe the solution you'd like
Upgrade jobs of a certain age, regardless of the status of plans which were applied, should be cleaned up and removed from the system (this includes their pods). This would probably be most easily accomplished by integrating with the TTL Controller for Finished Resources
Describe alternatives you've considered
Mark and sweep effected by this controller itself.
Additional context
See the kubectl output in #23. Pods that incur a reboot as part of the upgrade job will in many cases end up in the Unknown state along with a second run of the pod. This may be confusing and shouldn't persist eternally.

Good idea! Using the TTL controller could make sense as this doesn't involve any other component which would need to be installed. It certainly would have to be configurable, probably in the Plan spec...

I opened a corresponding issue in rancher for our QA to track: https://github.com/rancher/rancher/issues/25929

Addressed via #48 and #49


crash backoff in dapr operator after upgrade to 1.4.3 (helm doesn't upgrade CRDs definitions)

In what area(s)?

/area operator
What version of Dapr?

1.4.3
Expected Behavior
dapr operator starts correctly
Actual Behavior
crash backoff in dapr operator after upgrade to 1.4.3.
Related:

https://github.com/dapr/dapr/pull/3732
https://github.com/dapr/dapr/issues/3731

Running debug with helm doesn't apply CRD changes:
helm3 upgrade --install dapr dapr/dapr --version=1.4.3 --namespace dapr-system --dry-run --debug
More info: https://github.com/dapr/dapr/issues/3731#issuecomment-941191734
time="2021-10-11T12:18:35.519609747Z" level=info msg="log level set to: info" instance=dapr-operator-9bc45d8fc-czqd9 scope=dapr.operator type=log ver=unknown time="2021-10-11T12:18:35.519784194Z" level=info msg="metrics server started on :9090/" instance=dapr-operator-9bc45d8fc-czqd9 scope=dapr.metrics type=log ver=unknown time="2021-10-11T12:18:35.520200483Z" level=info msg="starting Dapr Operator -- version 1.4.3 -- commit a8ee30180e1183e2a2e4d00c283448af6d73d0d0" instance=dapr-operator-9bc45d8fc-czqd9 scope=dapr.operator type=log ver=unknown I1011 12:18:36.573546       1 request.go:655] Throttling request took 1.044726144s, request: GET:https://<IP_ADDRESS>:443/apis/coordination.k8s.io/v1?timeout=32s time="2021-10-11T12:18:36.73283813Z" level=info msg="Dapr Operator is started" instance=dapr-operator-9bc45d8fc-czqd9 scope=dapr.operator type=log ver=unknown I1011 12:18:36.732953       1 leaderelection.go:243] attempting to acquire leader lease dapr-system/operator.dapr.io... time="2021-10-11T12:18:36.940709962Z" level=info msg="getting tls certificates" instance=dapr-operator-9bc45d8fc-czqd9 scope=dapr.operator type=log ver=unknown time="2021-10-11T12:18:36.940842904Z" level=info msg="tls certificates loaded successfully" instance=dapr-operator-9bc45d8fc-czqd9 scope=dapr.operator type=log ver=unknown time="2021-10-11T12:18:36.941303961Z" level=info msg="starting gRPC server" instance=dapr-operator-9bc45d8fc-czqd9 scope=dapr.operator.api type=log ver=unknown time="2021-10-11T12:18:36.941386697Z" level=info msg="Healthz server is listening on :8080" instance=dapr-operator-9bc45d8fc-czqd9 scope=dapr.operator type=log ver=unknown time="2021-10-11T12:18:37.944396942Z" level=info msg="starting webhooks" instance=dapr-operator-9bc45d8fc-czqd9 scope=dapr.operator type=log ver=unknown I1011 12:18:37.944450       1 leaderelection.go:243] attempting to acquire leader lease dapr-system/webhooks.dapr.io... panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x13e901a] goroutine 436 [running[]: github.com/dapr/dapr/pkg/operator.patchCRDs({0x18e43b0, 0xc0007bf7c0}, 0x0, {0xc000ade270, 0x1, 0x0})     /home/runner/work/dapr/dapr/pkg/operator/webhooks.go:121 +0x4fa created by github.com/dapr/dapr/pkg/operator.RunWebhooks     /home/runner/work/dapr/dapr/pkg/operator/webhooks.go:68 +0x665
I tried a downgrade to 1.4.2 and now I can't apply a Subscription:
unable to recognize "": no matches for kind "Subscription" in version "dapr.io/v2alpha1"
Steps to Reproduce the Problem
Upgrade from 1.4.2 to 1.4.3
Release Note

RELEASE NOTE:

https://github.com/dapr/dapr/issues/3731#issuecomment-941191734

/assign


Fix UID upload to new project with same UID bug

/upload/uid respects the project label when uploading and so will not upload to other projects
Review Checklist

Tests were added to cover all code changes
Documentation was added / updated
Code and tests follow standards in CONTRIBUTING.md

Good catch @hkethi002
I presume step 2 below will behave the same if step 1 was an upload to /upload/uid at different project?

Reaper uploads via /upload/reaper with session uid abc
Client uploads via /upload/uid to same group, different project with session uid abc

I assume that if steps 1 and 2 are reversed, we would end up with 1 session and not 2. It is still the responsibility of clients that use /upload/reaper to ensure their uid values are globally unique.

Correct, the upload/uid endpoint only considers the sessions/acquisitions in the project that was provided by the client and so anything that was uploaded to another project is ignored.

Thanks for writing a test as well, and for finding the bug. LGTM!


Loop expression creates "Failed to produce diagnostic for expression"

Description
The code below when compiled with swiftc produces the error message

test.swift:3:1: error: failed to produce diagnostic for expression; please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the project

Steps to reproduce
Put the below in a file test.swift and compile with swiftc -c test.swift
let a = ["a" : ["b" : "c"]]
let b = a["a"]
for (_, _) in b {
}

Expected behavior
Useful error message
Environment

Swift compiler version info: swift-driver version: 1.62.15 Apple Swift version 5.7.2 (swiftlang-<IP_ADDRESS>.5 clang-14<IP_ADDRESS>)
Target: x86_64-apple-macosx13.0

This is fixed in 5.8 which came with latest Xcode. Can you please verify and close?

With
% swift --version
swift-driver version: 1.75.2 Apple Swift version 5.8 (swiftlang-<IP_ADDRESS>.2 clang-14<IP_ADDRESS>.100)
Target: x86_64-apple-macosx13.0

I now get
% swiftc -c test.swift
test.swift:3:15: error: for-in loop requires '[String : String]?' to conform to 'Sequence'; did you mean to unwrap optional?
for (_, _) in b {

This looks reasonable. Issue closed.

Duplicate of #61363


Fix: explicitly set nativeHandles to false during glFactory::initTexture

explicitly set nativeHandles to false during glFactory::initTexture, as the nativeHandles could be set to true by the previous texture taking the slot.

good catch, thanks!


New english words, translated to Catalan & Spanish

Changes

Added vampire, witcher and zombie to English
Translated to Spanish
Translated to Catalan

Should be fine now 👍🏻

The bot will be updated during the night with the new translation file 😉


Cleanup the Plotly example

References
With #171 now merged, explicitly setting the renderer might not be required anymore.

Code changes
Example update.

User-facing changes
More concise code in the Plotly example notebook.

Backwards-incompatible changes
None

Looking good on RTD:

Amazing! thanks for making Plotly look awesome in JupyterLite <3


Test-Module: Import Az.Accounts should not be required

if azure: false in metadata, import of Az.Accounts should not be required during testing.
https://github.com/Azure/autorest.powershell/blob/b9d6f405cc4370634b916543e97ea7fb84ae0063/powershell/resources/assets/test-module.ps1#L32
a simple comment this line if azure: false
Resources isnt really needed either but doesnt stop testing.

If azure:false, Az.Accounts will not be imported actually.

@dolauli  see screen shots, azure = false, but still tries to import az.accounts.


Javascript in the Webview is not executed on iOS with new RN architecture from 13.0.0

Bug description:
JS is not executed inside Webviews on iOS from react-native-webview 13.0.0.
Anything in <script> tags or onclick callbacks are not executed.
Version 12.4.0 or using the old RN architecture works fine.
To Reproduce:

Create new RN app
Run yarn add react-native-webview
Run (cd ios && RCT_NEW_ARCH_ENABLED=1 pod install)
Paste this component into your App.tsx:

import WebView from 'react-native-webview';
import React from 'react';
import {
  View,
} from 'react-native';

function App(): JSX.Element {
  return (
      <View
        style={{
          marginTop: 20,
          height: 560,
          width: 300,
        }}>
        <WebView
          source={{
            html: `
            <html lang="en">
  <head>
    <script>alert('Loading WebView')</script>
  </head>

  <body>
        <button type="button" onclick="alert('clicked button')">Trigger alert</button>
  </body>
</html>`,
          }}
        />
      </View>
  );
}

export default App;

Expected behavior:

An alert showing "Loading Webview" shows up
When clicking on the button, "clicked button" shows up

Screenshots/Videos:
No alert show up.
Environment:

OS: iOS
OS version: tested in 16.4, 16.3
react-native version: 0.71.8
react-native-webview version: 13.0.0

@louiszawadzki I ran into a similar issue on an older version (v11). Javascript events were just not being triggered anymore. It still worked on other dev's systems, so what fixed it in the end for me was recloning the repo 🤷♂ hope this helps

I can confirm, this is a regression in 13.x.
We have been working towards integrating the WebView into our app for a while, I tried to upgrade to the latest and seems JS is not being evaluated at all.
Going back to 12.4.0 is working properly in this regard.

Same for me - v13+ does not have Javascript while 12.4 does.
Who can look into this?

Looked into and published #3041. Thank you all for the report! The change is simple enough that I encourage you to try patching the library in the meantime.

Ah, I had mentioned this issue in the PR, but I guess I had too many other words in between "fixes" and the issue number, so the auto-linking/closing didn't work 😛


file attributes of zipped folders are not applied on extraction

there is this piece of code in AbstractExtractFileTask.java
    if (fileHeader.isDirectory()) {
        if (!outputFile.exists()) {
            if (!outputFile.mkdirs()) {
                throw new ZipException("Could not create directory: " + outputFile);
            }
        }
    } else if (isSymbolicLink(fileHeader)) {

so whenever the extraction comes across a directory in the zip file, upon visiting or creating it the attributes stored in the zip won't get applied. I guess this could be fixed by the following (I successfully tested on Windows with hidden dirs):
    if (fileHeader.isDirectory()) {
        if (!outputFile.exists()) {
            if (!outputFile.mkdirs()) {
                throw new ZipException("Could not create directory: " + outputFile);
            }
        }
        UnzipUtil.applyFileAttributes(fileHeader, outputFile);
    } else if (isSymbolicLink(fileHeader)) {

This would need some testing on Linux/Mac as well. Which I cannot do right now. Especially some obscure settings might prevent e.g. other files from being extracted into read-only folders afterwards etc.

You are right. This file attributes should be applied in the if-block as you mentioned. I will test this on mac/linux and include a fix in the next release.

You are right. This file attributes should be applied in the if-block as you mentioned. I will test this on mac/linux and include a fix in the next release.

Issue fixed in v2.7.0 which was released today.


fix(uiSelectChoices): prevent template element from being modified

Previously, the .ui-select-choices-row element got deleted whenever the linked scope got destroyed which prevents rendering of the options in some cases.

@zollinger I'm going assume this is in reference to #1365?
I need one of you to open an issue with a Repro just to confirm there is a problem and this does resolve it, before I go ahead and merge. (Up until no one else has reported this problem and there have been many versions since the changes - so I just want to be sure this is good to merge).

I added a second commit which prevents tElement from leaking to the link function scope.

@zollinger I was thinking to ask you to do that. Thanks very much!

I'm not entirely sure what to test here. Adding and removing elements to the DOM is the job of AngularJS, so I we should do or test that here. Then the second change is about working with the linked element in link phase, which is obvious.


Issue with GPU Computation Execution in CUDA Mode

Hello,
I have been working on a CUDA program based on the example provided in ex1p and ex14p. However, it seems that while the GPU is being initialized, the computations are still being executed on the CPU.
Compared to the MPI version, I only added Device device(device_config); in the main code and defined the device of CUDA. I also recompiled the code in MFEM_USE_CUDA = YES.
Could you please advise if there are additional modifications required in the code after selecting the device?
Thank you for your assistance.
Best regards,
Xiaotian

Take a look at the "Device sample runs" section in the beginning of the source file -- they represent ways to run the code utilizing primarily the GPU.
Also, if using a parallel MFEM build, I recommend building HYPRE with GPU support as well, see https://mfem.org/building/#cuda-version-of-mfem.

Take a look at the "Device sample runs" section in the beginning of the source file -- they represent ways to run the code utilizing primarily the GPU.
Also, if using a parallel MFEM build, I recommend building HYPRE with GPU support as well, see https://mfem.org/building/#cuda-version-of-mfem.

Thank you for your reply! The information from the link was very helpful. I confirmed that I followed the correct steps for installation and compilation, and other CUDA programs are also running normally.
I tried the "Device sample runs" section and modified my code accordingly. I compared the computation times for choosing GPU versus CPU. However, the computation time for choosing GPU was slightly longer than the latter, so I suspect that the computation part of my code is not running on the GPU.
If it's only necessary to add const char *device_config = "cpu"; and Device device(device_config); at the code level, then perhaps the code is not the issue. I should continue to look for problems hidden in other aspects.

I forgot to mention this before: take a look at https://mfem.org/gpu-support -- it has some useful information about running MFEM on GPUs.

I forgot to mention this before: take a look at https://mfem.org/gpu-support -- it has some useful information about running MFEM on GPUs.

Thank you


version

Coverage increased (+20.9%) to 20.896% when pulling dd2716cf2a025918d7f11e08bd72d7b3442dc23b on aljesusg:Connect_to_backend into 4743a5bf7aca9cad51fb32c23c2537b2140fed07 on ManageIQ-Exchange:master.


Supress [Blitz Guard]: /api/guard/queries/getAbility is not secured

What is the problem?
getAbility is not meant to be wrapped with Guard.authorize, therefore the middleware should suppress the message by default.

https://github.com/ntgussoni/blitz-guard-recipe/pull/2


Fix Mac Issues

Adjust dealloc observer to fix more leak issues when freeing objects.
Fix issue with closing and opening multiple windows.
Add tests to make sure instances are being freed.
No longer terminates the whole app on exit, just stops/starts until app is actually terminated.
Tests now pass on Arm processor.
Fix missing dealloc for text view.
Release pixel format.

Should fix #1089 and #1100
Needs some additional testing from someone else, as Mac seems to have vast inconsistency issues between OSX versions and architecture.

Everything looks good to me as far as I can tell. The new association methods will hopefully help.
I made a small edit to the new unit test to make pytest happy, and will merge after the current run is complete.


bug: sidebar is not consistent

Describe the bug
currently the sidebar is not consistent, it is getting shorter width for some videos and perfect for some
Expected behavior
need to be consistent sidebar for all videos
Screenshots or GIFs

are you working on this issue?
no, anyone can pickup this if @hkirat feels this is an issue and approve it

working on this


Support swiftly fixing quick fix errors one after another

Testing #194072
Repro:

Create 2 errors on a line
cmd+.
enter
wait a second
cmd+.
enter

Doing this slowly works fine:

Doing it quickly fails:

I've had some folks has mentioned this before as well (not just in the context of this feature) - It's an issue with how the diagnostics are formed. (like how sometimes you hit ctrl + . for the quickfix menu before the error shows up in anticipation of the quickfix being there)
Will do some exploration on how we can optimize this (may be resolved with how I'm handling multiple quickfixes, mentioned in your issue here https://github.com/microsoft/vscode/issues/194222)

@justschen the error underline never went away though, so could we be optimistic about this and assume it's still valid if the range for that problem didn't change?

You're right, that's interesting. I'll give it a look 🤔

@mjbvz I think this might have something to do with the LSP side of things? I've seen some related issues about errors not being picked up fast enough and people hitting ctrl + . anticipating an error, but the diagnostics have not shown up yet.

Yes seems like a duplicate of #117812. Right now we have to manage passing diagnostics to TS Server and these easily get out sync the server


NUTCH-2935 DeduplicationJob: failure on URLs with invalid percent encoding

catch IllegalArgumentException when unescaping percent-encoding in URLs
if one URL of two compared URLs is valid, keep it as non-duplicate
add unit tests for DeduplicationJob

Thanks, @lewismc! For the Common Crawls it just took some time to hit a bad URL which also somehow slipped through the URL filters and normalizers during injection.


feat (sidebar) allow chat without any files selected.

Small change to allow a user to remove all files without closing the sidebar. I've created this as a result of this issue: https://github.com/yetone/avante.nvim/issues/970.
I'm not sure if it was intended that the sidebar would close when the file context was removed as the WinClosed auto command is closing the entire sidebar.
Happy to find another way if we'd prefer to have the selected files container not visible after all files have been deleted.
Raised PR as a result of this isssue: https://github.com/yetone/avante.nvim/issues/970
After:

With this change only, the prompt sent to the llm needs to be changed.
For instance it contains
[...]
All changes to files must use this *SEARCH/REPLACE block* format.
ONLY EVER RETURN CODE IN A *SEARCH/REPLACE BLOCK*!
[...]

If there are no files, it does not make sense

@CyprienRicque that's a good point. It should be fairly simple to alter the system prompt.
Does this warrant introducing a new mode such as "chatting" with a different system prompt & avanterules file? Or should we simply omit parts of the prompt when there are not context files?
Excuse my ignorance but what would the impact of leaving those references in the system prompt?

I think that having extra useless guidelines does in fact alter the model performance, but only from experience using these models.
I believe adding a chatting mode with dedicated avanterules file is a great idea.


Upgraded Nippy to 3.1.1

Codecov Report

Merging #295 (72c6411) into develop (3ea740d) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##            develop       #295   +/-   ##
===========================================
  Coverage   100.000%   100.000%
===========================================
  Files            36         36
  Lines          3065       3065
===========================================
  Hits           3065       3065


LC issue - cannot do a non-empty take from an empty axes

I got this error while running the LC command for energy range from 100MeV to 10000MeV however it works well for energy range from 100MeV to 500000MeV and it gives the result.dat file and the plots. Could you help me fix this problem.
/home/hep/enrico/enrico/plotting.py:344: RuntimeWarning: divide by zero encountered in log10
optimal_markersize = (0.5+4./(1.+np.log10(len(y))))
/home/hep/enrico/enrico/plotting.py:345: RuntimeWarning: divide by zero encountered in log10
optimal_errorlinewidth = (0.2+2./(1.+4.*np.log10(len(y))))
Traceback (most recent call last):
File "/home/hep/enrico/bin/enrico_plot_lc", line 30, in
lcobject.PlotLC()
File "/home/hep/enrico/enrico/lightcurve.py", line 223, in PlotLC
self._PlotLC()
File "/home/hep/enrico/enrico/lightcurve.py", line 469, in _PlotLC
plt.ylim(ymin=max(plt.ylim()[0],np.percentile(Index[~uplimIndex],1)*0.1),
File "/home/hep/anaconda2/envs/fermi/lib/python2.7/site-packages/numpy/lib/function_base.py", line 3699, in percentile
interpolation=interpolation)
File "/home/hep/anaconda2/envs/fermi/lib/python2.7/site-packages/numpy/lib/function_base.py", line 3425, in _ureduce
r = func(a, **kwargs)
File "/home/hep/anaconda2/envs/fermi/lib/python2.7/site-packages/numpy/lib/function_base.py", line 3816, in _percentile
x1 = take(ap, indices_below, axis=axis) * weights_below
File "/home/hep/anaconda2/envs/fermi/lib/python2.7/site-packages/numpy/core/fromnumeric.py", line 123, in take
return take(indices, axis, out, mode)
IndexError: cannot do a non-empty take from an empty axes.

Maybe there are no detections in that energy range so y is empty abd then the log fails, but it shouldn't spit that error. Let me have a look and maybe get a workaround ...

Ok, that is actually a strange error indeed. Can you provide a minimal example that produces it? I would like to do some tests.


as_ptr()'s use of *mut is misleading

as_ptr() returns a *mut _ pointer. This isn't an error by itself, but under Rust's memory model, this pointer is derived from shared/immutable &self, and therefore doesn't have permission to mutate self, so the mut of the pointer is misleading.
https://github.com/sfackler/foreign-types/blob/393f6ab5a5dc66b8a8e2d6d880b1ff80b6a7edc2/foreign-types-shared/src/lib.rs#L89
I assume this is for convenience, because C APIs aren't diligent about const vs mut distinction. However, this is a gotcha, because C APIs that take *mut may actually mutate the object, and that is UB from Rust's perspective.
Could you add .as_mut_ptr() that takes &mut self to provide a pointer safe for mutation?

The structure of Opaque is designed to prevent mutation through the *mut from being UB: https://github.com/sfackler/foreign-types/blob/393f6ab5a5dc66b8a8e2d6d880b1ff80b6a7edc2/foreign-types-shared/src/lib.rs#L14.
Even for C APIs that are const-correct, C's notion of constness is distinct enough from Rust's that & <-> *const and &mut <-> *mut doesn't really work.

The &self is a pointer to UnsafeCell (semantically through a PhantomData). Why is it being tagged as Frozen?

Could it be because UnsafeCell in PhantomData has zero size, and doesn't exist in memory? If it was Opaque(UnsafeCell<ActualForeignSizedType>) then it would map to an address space.

I think there's a difference between PhantomData<UnsafeCell<*mut ()>> and UnsafeCell<PhantomData<*mut ()>>, with only the latter registering as using interior mutability

I'll note again: rustc currently treats UnsafeCell differently whether it's inside PhantomData or not! See this playground, click "Show LLVM IR", and inspect the result; the function taking &PhantomData<UnsafeCell<*mut ()>> gets marked with noalias readonly, while &UnsafeCell<PhantomData<*mut ()>> gets marked with readnone.
If you add extern types to the mix, you'll see the exact same LLVM IR as for &UnsafeCell<PhantomData<*mut ()>> (LLVM will even merge the functions because of that).

See also discussion from https://github.com/rust-lang/unsafe-code-guidelines/issues/236#issuecomment-1637072799, this is still not determined

I think you accidentally used the same link twice.

Apologies, I've fixed it now.


Fixing some errors in MA SDK

Amplitude Developer Docs PR
Fixing some things in the Marketing Analytics SDK
Deadline
ASAP
Change type

[X] Doc update.

PR checklist:

[X] My documentation follows the style guidelines of this project.
[X] I previewed my documentation on a local server using mkdocs serve.
[X] Running mkdocs serve didn't generate any failures.
[X] I have performed a self-review of my own documentation.

@yuhao900914 -- made some small updates to the SDK. Please review.


Is there an alternative to the IN keyword that allows in-partition queries with an array value to be parameterised?

Can't find a definite answer to this - want to understand how to do a query with the following goals

In-partition query
Filter clause is based on an array of values (potentially in the hundreds)
Array of values should be parameterised

#18640 mentions that the IN keyword is suitable for (1).
From the IN keyword docs following:

If you include your partition key in the IN filter, your query will automatically filter to only the relevant partitions.

but does not specify how we can specify an array value such that it is parameterised.
https://github.com/Azure/azure-cosmosdb-node/issues/247 mentions ARRAY_CONTAINS is suitable for (2) and (3), but does not mention whether it will be an in-partition query.
What would the recommended approach for constructing such a query? In my particular use case, the array of values is not user-specified, so I could just use the IN keyword and construct an expression, but would like to know if there's a suitable alternative.

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

ID: 531c6fcf-6cb8-f229-d15e-d26111b5ff85
Version Independent ID: e77c5aa5-6201-ee8d-12bc-e706b1e06b9c
Content: SQL keywords for Azure Cosmos DB
Content Source: articles/cosmos-db/sql-query-keywords.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @timsander1
Microsoft Alias: tisande

@JasonPan Thank you for the feedback. We are actively investigating and will get back to you soon.

@JasonPan Would it be possible to share some pseudo code of the query you want to build, that way it will be easier to see if query is really possible to write or not based on your description. Also if possible please attach few documents on which we can run the query on.

@JasonPan Awaiting your response on above comment.

@JasonPan It has been a while we heard from you.
We will proceed to close this issue now.
If you need further assistance, please post this issue on StackOverflow or Microsoft Q&A for better visibility


Document the properties added to the http.IncomingMessage

Hi,
I am currently helping to maintain the Typings definitions for the request package.
I noticed that request adds the following properties to the response object: request, toJSON, caseless, body, read so the result object is no longer a "pure" http.IncomingMessage.
Why are these properties not documented ?
Are they deprecated ? Is it just something forgotten in the doc ? (but I checked your tests and I did not found anything about these properties). Basically, are these properties reliable or should we keep them hidden ?

Good question. Unfortunately there is a ton of state attached here and there in request and no one really knows what the initial plan was, or whether there was one in the first place. So these are just state vars for the most part, that are not meant to be used outside of the module, probably without toJSON because that's used for serialization, I guess :)

Then it should at least document toJSON and explain that it is safe to use JSON.stringify on this response.

Feel free to update the docs and submit a PR about it :+1:
Here is what's been said about response.toJSON.
I guess caseless can be used too, in case you know that it's there. So I'm assuming that there are people out there that depend on it.

I almost finished refactoring the documentation, it helped me to spot some other issues (ie. elapsedTime is an other property added to the response (but not always), the auth option is not consistent, etc.)
The README.md became huge with the time, so I separated it in smaller "guides" files and an api.md file with a full overview with the API and clearly stating every option with its type and default value.
I'll submit a PR as soon as possible.

Sounds great! It will be interesting for me to see it. However huge changes require more time to review and merge.
Also note that we have a separate repository for documentation that we plan to use in future. It's hosted at http://request.js.org

Oh, this is great !
Thank you for pointing me to this, I think that it better suits this documentation repository then.
It's still a work in progress, but you can take a look at my refactor-doc branch.
I finished my first iteration on the options (in doc/api.md), I left some blanks when I wasn't sure about the types or default values, the description is mostly unchanged. What I would like is to clearly define the interfaces, not only the main options but also for the AuthOptions, OAuthOptions, etc. (for the moment it's spread across the whole README.md)

I'll take a look at it. BTW I recently pushed something similar about the rewrite I'm working on here. I think everything from the legacy request docs, from the new rewrite, and from request-promise should be placed in request.js.org.
So we should keep that in mind when organizing the categories and the markdown files in that repository.
As for the legacy auth, oauth etc options - I can help you with that.

@demurgos I like how you have divided the readme into pieces. I have only one concern about the API docs, generally sorting the options alphabetically is a great idea, but we need to support grouping them semantically as well. This probably can be achieved via GitBook plugin and some basic JSON data structure.

Yes, I noticed that you still grouped the features thematically in the new interface repository. I'll restore the original organization.
I moved my changes to a fork of request.github.io and started to actually document the missing properties/methods on IncomingMessage. So I'll close this issue to open a new one on the repo for the doc.

Sounds good! I'll figure out something about the GitBook plugin, a little jQuery will do :) I really want to have the alphabetical order for the options as well. Unless you are familiar with the module that ordering is better.

I was also considering this sort of solution, but I'm not really sure if that's that necessary.
After all, either you don't know the API and the thematic classification more helpful or you know the API and search some details (and then its pretty easy anyway to search the page).
Here is a reordered version.
I'm pretty satisfied with this structure (name, type [, default] & description) to describe the options but I'm still experimenting for the presentation of the package API. Using a website with directories really helps in organizing the API and has some benefits: ie. the anchor links work great for the options.

I like it. The problem is I changed the directory structure today :) Just copy all of your directories and files into docs/request-legacy. We'll figure out the navigation later. Folders next and promises can be removed in your case.

Ok, thank you for you feedback :)


Module not found: Error: Can't resolve '~/package.json' in ...

Hello, this is the output of webpack --watch --env.tns --env.android.
I can't say if it's really an issue, because the application starts and run on the emulator without any problem. IIRC I got the same messages even before your last commits.
paolo@tk:hello-ns-vue $ tns create hello-ns-vue --template https://github.com/tralves/nativescript-vue-webpack-template
paolo@tk:tmp $ cd hello-ns-vue/
paolo@tk:hello-ns-vue $ webpack --watch --env.tns --env.android

Webpack is watching the files…

(node:22188) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.
Hash: 412e5b51b04e54721432
Version: webpack 2.6.1
Time: 5099ms
           Asset       Size  Chunks                    Chunk Names
       bundle.js    11.2 kB       0  [emitted]         bundle
      app.css.js  267 bytes       1  [emitted]         app.css
       vendor.js    1.53 MB       2  [emitted]  [big]  vendor
         app.css    13.9 kB          [emitted]
images/apple.jpg     277 kB          [emitted]  [big]
  images/vue.png    6.62 kB          [emitted]
    package.json   89 bytes          [emitted]
      starter.js   41 bytes          [emitted]
  [22] ../~/tns-core-modules/ui/layouts/stack-layout/stack-layout.android.js 1.01 kB {2} [built]
  [23] ../~/tns-core-modules/ui/placeholder/placeholder.android.js 698 bytes {2} [built]
  [26] ../~/tns-core-modules/http/http.js 1.83 kB {2} [built]
  [27] ../~/nativescript-vue/dist/index.js 258 kB {2} [built]
 [116] ./JsComponent.js 86 bytes {0} [built]
 [117] ./vendor-platform.android.js 74 bytes {2} [built]
 [118] ./app.scss 41 bytes {0} [built]
 [119] ./VueComponent.vue 2.12 kB {0} [built]
 [120] ../~/tns-core-modules/bundle-entry-points.js 3.29 kB {2} [built]
 [121] ./app.js 515 bytes {0} [built]
 [122] ./vendor.js 102 bytes {2} [built]
 [124] ./app.css 41 bytes {1} [built]
 [152] ../~/tns-core-modules/ui/layouts/wrap-layout/wrap-layout.android.js 1.41 kB {2} [built]
 [164] ../~/nativescript-css-loader?{"minimize":false}!../~/nativescript-theme-core/css/core.light.android.css 13.9 kB [built]
 [165] ../~/nativescript-css-loader/lib/css-base.js 1.51 kB [built]
    + 153 hidden modules

WARNING in ../~/tns-core-modules/profiling/profiling.js
Module not found: Error: Can't resolve '~/package.json' in '/tmp/hello-ns-vue/node_modules/tns-core-modules/profiling'
 @ ../~/tns-core-modules/profiling/profiling.js 113:20-45
 @ ../~/tns-core-modules/ui/frame/frame.android.js
 @ ../~/tns-core-modules/ui/frame/activity.android.js
 @ ./vendor-platform.android.js
 @ ./vendor.js

WARNING in ../~/tns-core-modules/ui/styling/style-scope.js
Module not found: Error: Can't resolve '~/package.json' in '/tmp/hello-ns-vue/node_modules/tns-core-modules/ui/styling'
 @ ../~/tns-core-modules/ui/styling/style-scope.js 24:20-45
 @ ../~/tns-core-modules/ui/page/page-common.js
 @ ../~/tns-core-modules/ui/page/page.android.js
 @ ../~/tns-core-modules/bundle-entry-points.js
 @ ./vendor.js
Child extract-text-webpack-plugin:
       [0] ../~/nativescript-css-loader/lib/css-base.js 1.51 kB {0} [built]
       [1] ../~/nativescript-css-loader?{"minimize":false}!../~/nativescript-theme-core/css/core.light.android.css 13.9 kB {0} [built]
       [2] ../~/resolve-url-loader?{"silent":true,"absolute":false,"sourceMap":false,"fail":false,"keepQuery":false,"debug":false,"root":null}!../~/nativescript-css-loader?{"minimize":false}!../~/nativescript-dev-webpack/platform-css-loader.js!./app.css 390 bytes {0} [built]
Child extract-text-webpack-plugin:
       [0] ../~/css-loader/lib/css-base.js 2.26 kB {0} [built]
       [1] ../~/css-loader?{"url":false}!../~/sass-loader/lib/loader.js!./app.scss 190 bytes {0} [built]
Child extract-text-webpack-plugin:
       [0] ../~/css-loader/lib/css-base.js 2.26 kB {0} [built]
       [1] ../~/css-loader?{"url":false}!../~/ns-vue-loader/lib/style-compiler?{"vue":true,"id":"data-v-0f0e8576","scoped":true,"hasInlineConfig":false}!../~/sass-loader/lib/loader.js!../~/ns-vue-loader/lib/selector.js?type=styles&index=0&bustCache!./VueComponent.vue 209 bytes {0} [built]
Hash: 90c28bf983fc71c67f9d
Version: webpack 2.6.1
Time: 111ms
       Asset      Size  Chunks             Chunk Names
     app.css   13.9 kB          [emitted]
package.json  89 bytes          [emitted]
  starter.js  41 bytes          [emitted]
    + 161 hidden modules

WARNING in ../~/tns-core-modules/profiling/profiling.js
Module not found: Error: Can't resolve '~/package.json' in '/tmp/hello-ns-vue/node_modules/tns-core-modules/profiling'
 @ ../~/tns-core-modules/profiling/profiling.js 113:20-45
 @ ../~/tns-core-modules/ui/frame/frame.android.js
 @ ../~/tns-core-modules/ui/frame/activity.android.js
 @ ./vendor-platform.android.js
 @ ./vendor.js

WARNING in ../~/tns-core-modules/ui/styling/style-scope.js
Module not found: Error: Can't resolve '~/package.json' in '/tmp/hello-ns-vue/node_modules/tns-core-modules/ui/styling'
 @ ../~/tns-core-modules/ui/styling/style-scope.js 24:20-45
 @ ../~/tns-core-modules/ui/page/page-common.js
 @ ../~/tns-core-modules/ui/page/page.android.js
 @ ../~/tns-core-modules/bundle-entry-points.js
 @ ./vendor.js

Yeah, those warnings are bothering me too. Didn't have time to look into that. Let's leave this issue here until someone figures it out.

Maybe useful for more detail:
$ webpack --watch --env.tns --env.android --display-error-details

News. I noted that it's like if the tilde symbol doesn't get expanded.

Module not found: Error: Can't resolve '~/package.json' in '/tmp/hello-ns-vue/node_modules/tns-core-modules/ui/styling'

In fact, if you add . to the modules list in webpack.config.js and do this:
$ pwd
/tmp/hello-ns-vue
mkdir ./~
$ cp package.json ./~/

the webpack --watch --env.tns --env.android command compiles just fine. Obviously we can't create the ./~ directory as a part of the project, but I see there is an alias directive and wonder if we could use something like:
...
resolve: {
  alias: {
    '~': '.'
  },
  ...
},
...

It works, but to me it seems more a workaround than a solution.  What do you think?

hum... maybe that's may the the right actually.
Maybe '~': path.join(__dirname, 'tns') would be better.

Fixed with #18.


Checkout links not working on firefox

Hey,
Can you share more details on this?

i have same error,
use createCheckout api get checkoutUrl https://{store}.lemonsqueezy.com/checkout/custom/{x}?signature={x}
then i use window.LemonSqueezy.Url.Open(checkoutUrl) is work.
but use window.open(checkoutUrl, '_black') get 404, redirected to {store}.lemonsqueezy.com/checkout

I found out that when I cleared the cookies, it worked fine.

The fix for this is on the way.


Fix package content URL request parameter type

LOWER_VERSION is a string not an integer.

Docs Build status updates of commit 57a24d4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/api/package-base-address-resource.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 209a641:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/api/package-base-address-resource.md
:white_check_mark:Succeeded
View

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.


Downloader processor issues

Extracted from #18

Specify resource url to csv and 3 fields (actual csv contains 9 fields)
Pass these parameters to downloader

Expected:
3 fields are exported
Actual:
Row length (9) doesn't match fields count (3)

Second try:

Specify url and 9 fields
2 Pass these parameters to downloader

Expected:
Downloader matches field names to csv column names
Actual:
Matching doesn't happen, fields must be specified in the order as they appear in csv.


lsp: provide doc:show in hover, if available

I am new to elvish. I am enjoying elvish very much, thank you!
The built in LSP feature in elvish is very useful but a bit basic at the moment.
One thing that I am running into while reading or writing elvish scripts in an editor (where I am connected to a elvish -lsp) is that I constantly need to refer to the documentation about a particular function (e.g. printf etc) in order to learn the finer aspects of the function.
This means I need to constantly do doc:show in the shell or refer to the elvish website and this breaks my editing "flow".
This PR automatically shows the doc:show (if available) for anything on the cursor in a hover.
The implementation is quite simple and it could be more sophisticated but it's working quite well for me.

Here is a sample screenshot of the hover feature in action:

@xiaq @krader1961 @zzamboni -- Would greatly appreciate a review and/or feedback on this feature... Thanks :-) !

Hi, thanks for the contribution. I usually review PRs in a FIFO manner, but here are some high-level feedback:

The MarkdownShowMaybe function seems unnecessary because you can just take the original Markdown source. The source function also already handles builtin commands.

The code to decide whether to look up doc is rather simplistic - for example, if you hover over the printf part of echo printf the doc of printf probably should not pop up.

Feel free to address those before I get back to this again, but this is a useful starting point and I wouldn't mind merging this as-is if you prefer.

Thanks !

The code to decide whether to look up doc is rather simplistic - for example, if you hover over the printf part of echo printf the doc of printf probably should not pop up.

Yes, this can definitely be improved.
Current algorithm

Find a leaf node that has a range which includes the current cursor position
Does the leaf node text have documentation? If so, simply return the documentation

This approach has some false positives like showing hover for echo printf that you pointed out.
Better Algorithm

Find a leaf node that has a range which includes the current cursor position
Once a leaf node is found, see if it is the correct type of node that could have documentation. We could use the parent property to also traverse the tree upwards if this information lies at a higher level of the tree
If the leaf node is found acceptable, see if there is any documentation. If so, return the documentation

I found the parsing/AST code a bit intimidating and was not sure how I should approach (2).
Can you provide some pointers for (2) ? Is there a pretty printer of some sort for the parse tree to get a feel of it ?
If you think it is too complicated to communicate tips for (2) then you could merge this commit as-is as you mentioned and improve upon it as you see fit.

Can you provide some pointers for (2) ? Is there a pretty printer of some sort for the parse tree to get a feel of it ?

There is already one place that does it, the completer for commands: https://github.com/elves/elvish/blob/66a4c590eb5002ab560f5498e8c6cf1f3d3b401f/pkg/edit/complete/completers.go#L77
The code is very concise thanks to some abstractions defined in node_path.go, but the basic idea is walking upwards from the leaf, and see if (1) we get a sequence of Primary, Indexing, Compound and Form nodes, and (2) the Compound node is equal to the Head field of the Form node.


[material-ui][drawer] Customize sidebar mini variant drawer backgroundColor

How do i change the background Color of the mini variant drawer

Fixed it!
added backgroundColor:"green" to the const closedMixin = (theme) => ({}) andconst openedMixin = (theme) => ({})

Fixed it!
added backgroundColor:"green" to the const closedMixin = (theme) => ({}) andconst openedMixin = (theme) => ({})


Added fixes for new Array()

Just never use new Array(n) again. Use Array.from({ length: n }). It's a way handy.


Change Socket / TLSSocket Implemention

All of the  TCP/UDP/TLS Socket has different API right now, lets keep it under one standard by defining an interface.

UDP Socket is unable to be in the same interface as TCP/TLS. I will put it into another "mailbox" interface instead of "StandardClientSocket" and "StandardServerSocket".
BTW, TCP / TLS is implemented in Commit 0a0afb002dc5f5b0d43d1c98b4323898fa98ab7d

UDP Socket is standardized by MailSenderSocket / MailRecieverSocket. Single Client and Server will be followed. Examples of the new interface will come later.

Now UDP Socket has UDPClientAndServerSocket / UDPClientSocket / UDPServerSocket. All of them are in MailSenderSocket / MailRecieverSocket or both interfaces.

Examples now added and now working on websocket. Issue will be closed.


counting data not been recorded on DB

Hi
Performing tests, the counting data on the mongodb is only been saved for the first 1min.
I tested several videos and even the counter is still running, the data on the DB stops around 1min.
The video completes, the total counter is displayed on the screen and the data on the database only shows like if recorded for seconds.

This is very similar to previous error reported.
Database not showing any data when the button is pressed
checking logs, but no errors. Counter on the screen increases but database not loading and/or not recording data

I just tried briefly on a long file (3 min) and it worked... Do you have the bug for streams also ?

are you testing with or without docker ?

hi, i was able to repro several times
yes, without  docker
This is/was not happening on beta1....
Error below:
21749:0x3f85790] 29928937 ms: Scavenge 1353.1 (1424.2) -> 1352.3 (1425.2) MB, 7.4 / 0.0 ms  (average mu = 0.062, current mu = 0.000) allocation failure
[21749:0x3f85790] 29928964 ms: Scavenge 1353.1 (1425.2) -> 1352.3 (1425.7) MB, 3.5 / 0.0 ms  (average mu = 0.062, current mu = 0.000) allocation failure
[21749:0x3f85790] 29929022 ms: Scavenge 1353.2 (1425.7) -> 1352.4 (1426.2) MB, 3.6 / 0.0 ms  (average mu = 0.062, current mu = 0.000) allocation failure
<--- JS stacktrace --->
==== JS stack trace =========================================
0: ExitFrame [pc: 0x3a8b9205be1d]
1: StubFrame [pc: 0x3a8b9205d3a6]

Security context: 0x2bc94ef1e6c1
2: insert [0x1499dbc49e81] [/home/odc/odcb2/opendatacam/node_modules/mongodb/lib/core/sdam/server.js:~371] [pc=0x3a8b938dd81b](this=0x10282668b981 ,ns=0x3237d6c95b21 <String[19]: opendatacam.tracker>,ops=0x3237d6c959a9 <JSArray[1]>,options=0x3237d6c95959 <Object map = 0x2cd0bce698...
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 0x8fb090 node::Abort() [node]
2: 0x8fb0dc  [node]
3: 0xb031ce v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
4: 0xb03404 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
5: 0xef7462  [node]
6: 0xef7568 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [node]
7: 0xf03642 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [node]
8: 0xf03f74 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node]
9: 0xf06be1 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [node]
10: 0xed0064 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [node]
11: 0x11701ee v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [node]
12: 0x3a8b9205be1d
Aborted (core dumped)
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR<EMAIL_ADDRESS>start: PORT=8080 NODE_ENV=production node server.js
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

I guess this is an issue with node.js / mongodb package
Could you try to

remove the node_modules folder in opendatacam
run npm install again

Also which version of node do you have ?  you can know by typing node --version ... Maybe you can try upgrading or installing again... not sure..

Since beta.1 the only changes was to upgrade the package version of mongodb from 3.3.x to 3.5.x .

Hi
I reinstall npm install and same error
i have version 10.20.1
If i click on the data , i get unexpected error has occurred or doesn't show anything at all.
any suggestions ?

not sure, could you try this:

Install opendatacam with docker to see if you have the same issue, if it is the case this would mean that there is a bug with this mongodb version...

If you don't have the bug, try resinstalling mongodb on your machine: https://github.com/opendatacam/opendatacam/blob/master/documentation/USE_WITHOUT_DOCKER.md#mongodb-for-generic-ubuntu-machine-with-cuda-gpu

Hi.
It looks like this version doesn't work. Beta 1 with 3.3.x works and with this Beta 2  3.5.x, doesnt.
This happens on non-docker version.,

Hi
after checking the errors, I have to run
npm update
After I did this, the recording of data started to work fine.

Yes, I think npm install should have done too .. you had some problem that didn't install the latest mongodb


feat: update readme with simple instructions for running systems

What?
Adds a simple example in the README for how to run a Mava system.
Extra
Sets the default number of environments to 16 so that systems can be run on any hardware out of the box.

:rocket:


Show private IP in Nodebalancers details

When I use the firewall, I need the private IP of the Nodebalancers but can't find this information in the details page. I am required to create a linode server so that I can get the private IP and use it to configure the firewall.

Hey @thinhbuzz, currently there is no way to get the exact private IP of a Nodebalancer because Nodebalancers are highly available and may use multiple private IP addresses to reach your Linodes. You should be able to allow connections from the following range <IP_ADDRESS>/24 in your firewall to get this to work.
Source: https://github.com/linode/docs/pull/5786/files#diff-9ffba81f79e5dec52c5fcc137807be89aa2dc27315a7cacc347317cf951a82c3R76

@bnussman-akamai thanks for your info


Include artifact coordinates in documentation

Hello,
currently I found it quite a hassle to find the atrifact coodinates to use with maven or gradle.
It would be great if you could include a brief maven configuration like https://github.com/spring-projects/spring-data-mongodb#maven-configuration
Otherwise thanks for your awesome work.

Thanks for the request @boerngen-schmidt.
This will be covered in gh-499 in the section "Getting Started -> Installing Spring Authorization Server".
I'll close this as a duplicate.


Nuxt3 yarn dev missing styles

Environment
Nuxt project info: (copied to clipboard)                                                                                10:21:32

Operating System: Darwin
Node Version:     v18.16.1
Nuxt Version:     3.13.2
CLI Version:      3.14.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction

https://stackblitz.com/edit/github-zwhk6w?file=src%2Fpages%2Findex.vue

git clone https://github.com/krmao/nuxtjs.git
git checkout pc
yarn install --check-files
yarn dev

Describe the bug
afteryarn dev please visit on http://localhost:3000/ and will see that no style such as 'root-container' not in html
I have tried all ways such as upgrade nuxt version but not work, any one can help me?
Additional context

Logs

https://stackblitz.com/edit/github-zwhk6w?file=src%2Fpages%2Findex.vue

what do you mean? reproduction is here https://stackblitz.com/edit/github-zwhk6w?file=src%2Fpages%2Findex.vue

Hi,
Most other tailwind css classes are there.
Where exactly are you defining those "layout-container", "page-container", "head-container", etc classes?
Because they do not appear to be from tailwind nor are they defined on your other css/scss files (?)

Hi @ptdev , thank you for the response,
the style is in app.vue src/pages/index.vue

will see the style on product build
yarn build
node .output/server/index.mjs

so the style exists in product mode, but missing in dev mode.

Could you reduce your reproduction to the relevant issue? E.g. removing all unnecessary modules, files and so on.

Hi again,
It's most definitely some configuration or conflict issue.
See the following screenshot, where if you remove the selected lines, it appears to fix the issue.

thanks, it's helpful, both works.
this option I followed the official document https://nuxt.com/docs/getting-started/configuration#with-vite
so may be this is a code bug or document bug?

Could you reduce your reproduction to the relevant issue? E.g. removing all unnecessary modules, files and so on.

thank you for the response, the issue key is found by ptdev descripted, offictial document options has conflicts
vue: {
    features: {
        customElement: true
    }
}

// or

vue: {
    customElement: true //idea depreated
}


Initial routing for profile-ids

An initial routing for profile-id's. Works both for user and search results.
TODO: tests, disable edit from search results. Refactor code. Made some delicious spaghetti.

[skip ci]


[BUG]: Initial position not set when velocity controller is loaded

Issue Description
When attempting to set the initial position of the manipulator using the initial_value state interface param for ros2_control, the position is never set when a velocity controller is loaded. This error occurs only in simulation. I have reported the issue at gz_ros2_control as well (see here.
Steps to Reproduce
Launch angler with SITL and a controller with a velocity command interface:
ros2 launch angler_bringup angler.launch.py use_sim:=true

Observe the initial position was not set. :cry:
Expected Behavior
The robot is set to the configured initial position.
Error Message
No response
Runtime Environment
This is run inside the development container with ROS Rolling and Gazebo Garden.
Additional Context
I implemented the initial_position_setter as a temporary hack for this while I wait for a response/fix.

The ros2_control folks have resolved this issue. Just need to do some additional testing with it and then I can remove the dependency on my fork


lock_api nightly feature

Is the nightly feature for lock_api still necessary? 1.36 has const fns, and I'm not really sure why there's a const_mutex() function in parking_lot but not a const constructor in lock_api; it's not like a RawMutex can be non-const or something, it has to have a INIT associated constant.

It's because there are restrictions on const fn functions with generic bounds, which means that those functions do not compile on stable.

Ah, gotcha, thanks.


chore(infra): bumps prow to latest release

This update is important in order to enable the handling of a repository GitHub event.
It has been merged in these two PRs as of late:

https://github.com/kubernetes/test-infra/pull/25105
https://github.com/kubernetes/test-infra/pull/25222

Not sure how this is related besides the fact that it triggers build of this layer, as it's not cached
Step 7/17 : RUN dnf -y upgrade --refresh &&     dnf -y install dnf-plugins-core https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm &&     dnf -y config-manager --set-enabled powertools &&     dnf -y install git make libtool patch which ninja-build golang                    autoconf automake libtool cmake python2 python3 nodejs                    gcc-toolset-9 gcc-toolset-9-libatomic-devel annobin-annocheck                    java-11-openjdk-devel jq file diffutils lbzip2 &&     dnf -y clean all
 ---> Running in 0c8376a3c386
CentOS Linux 8 - AppStream                      150  B/s |  38  B     00:00
Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist

The command '/bin/sh -c dnf -y upgrade --refresh &&     dnf -y install dnf-plugins-core https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm &&     dnf -y config-manager --set-enabled powertools &&     dnf -y install git make libtool patch which ninja-build golang                    autoconf automake libtool cmake python2 python3 nodejs                    gcc-toolset-9 gcc-toolset-9-libatomic-devel annobin-annocheck                    java-11-openjdk-devel jq file diffutils lbzip2 &&     dnf -y clean all' returned a non-zero code: 1

centos 8 is dead. We need to port them to centos stream as we did with 2.2 images.
Quickest fix is to revert any change to 2.0 or 2.1 dockerfile that uses centos 8.

@jwendell This is based on what's available on the main branch - I haven't changed anything here besides the prow commit hash which triggers the image rebuild. That means that building this stuff on e.g. my local env will result in this error regardless. What does it take to move to centos:stream8 besides changing the base image?

It takes testing. Making sure that all packages are available (a simple build should be enough for this, if the build passes, we are good). But I think the real test is when it runs the jobs. Some packages might have changed (for instance, compiler versions).
So, I'd just create a jira ticket so we can follow up on this, and I'd just reverted any change in Dockerfiles that use centos8.

I'd just reverted any change in Dockerfiles that use centos8

Then it will use outdated checkconfig and pr-creator. I am not sure how relevant it is, but maybe it's better to simply bump it to centos:stream8 as part of this PR? WDYT?
I also fail to understand how is K8S_TEST_INFRA_VERSION used in the affected images. I see it's being used in builder image (go-1.16), but is this env variable used outside of the docker image (at runtime)?

@jwendell I built all the affected images using centos:stream8 without problems. Shall I do some more verification locally?

Run the test suites?
I'm not a big fan of mixing PR's like this. If you really want to go this route, please create another PR switching to centos stream. After it gets merged, we could merge this one.

Run the test suites?

Which one? How?

I'm not a big fan of mixing PR's like this. If you really want to go this route, please create another PR switching to centos stream. After it gets merged, we could merge this one.

Mixing or not - if we don't make the images buildable, as I said before - proxy builds will be using out-of-sync prow binaries. Also whenever you run ./tools/bump_prow.sh you will face the same issue again. So I believe fixing the image this way or the other is an integral part of this PR.

If you have time to fix it yourself, please do it. I just wanted to give you a quick workaround. If you want to do it on this PR, please make it a separate commit (and add the don't squash label).
After you do this, you can trigger a fake PR in istio and operator PR's for the 2.0 and 2.1 branches and watch the results. If there's any failure due to the new image, you can follow up and issue another PR fixing those.

I'm on the same page - I don't like quick and temporary workarounds - they quickly become permanent. I am willing to spend time fixing it, not only because it is blocking adding upstream sync automation I worked on lately, but primarily because I don't like having technical debt.
I don't agree though about not squashing - if we separate them we will have one commit which will be faulty and the follow-up one with a fix. Is this really what we want?

After you do this, you can trigger a fake PR in the projects/branches that use those images and watch the results. If there's any failure due to the new image, you can follow up and issue another PR fixing those.

Thanks for the explanation - I will do this. I assume this will involve our envoy builds?

I don't agree though about not squashing - if we separate them we will have one commit which will be faulty and the follow-up one with a fix. Is this really what we want?

The bump to centos stream can be the first commit

Thanks for the explanation - I will do this. I assume this will involve our envoy builds?

I guess so, along with proxy. You'd need to check which jobs use centos 8 image.

Ok after quick reprocessing of this thread I think I will go ahead with separated PR for centos fix first and only then we can take care of this PR.

/retest


which torch version in human process

I'm grateful that you can open-source this work. I'd like to run it on my own dataset and use the human pose script to generate the SMPL. However, the documentation doesn't provide the PyTorch version. Could you please provide the PyTorch version, or offer a Docker image that can directly execute the human pose script? @ziyc

I'm grateful that you can open-source this work. I'd like to run it on my own dataset and use the human pose script to generate the SMPL. However, the documentation doesn't provide the PyTorch version. Could you please provide the PyTorch version, or offer a Docker image that can directly execute the human pose script? @ziyc

@cedricgsh
I can run generate the SMPL steps In cuda11.8 pytorch 2.5.1

@zzz5y but I cannot install neural_renderer in cuda11.8 pytorch2.5.1

From the debug message,It seems that you need to install a pytorch compiled by cuda11.8.


[TC-46] - Update TO client for psql API changes.

Updated the TO client to work with API changes with psql.  This fixes TC-46

thanks @mitchell852!


fix Not Like condition example to be correct

Coverage remained the same at 100.0% when pulling dcf646006e730a2f598c0f6b26d6fd920dbad35f on nise-nabe:fix-doc-is-not-like into 9518750e2d5aca07ea33f68e39b1f733c842c406 on mybatis:master.


Make epw_path required, and modify bld matrix, zone, SchDef, BEMDef to more human-readable format.

@chriswmackey
This PR now makes the epw_path argument for simulation required. And implements the changes to the bld, zone properties and BEMDef, SchDef classes, so that bldtype, builtera, and zones are identified by a string rather then position in a matrix.
S

@chriswmackey
Just added those changes. Should be good to merge!

Thanks! Merged.


[Popper] Animated scale not considered in position on mount

When a popper trigger/reference is rendered inside a scaled animated parent the resulting position does not account for this.
https://codesandbox.io/s/spring-bash-4wzz3o?file=/App.js

Possibly fixed by #2092, will check manually.

See below – didn't have this issue in previous versions:
https://github.com/radix-ui/primitives/assets/3652743/a9cd69b9-1333-4767-bc83-ba46e4259838


7.6-homework

生产实习7.6

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Totem Config :  Parent Config Support

As a totem user, I need ability to specify the parent configuration for my repositories totem config.

Resuming work again on this ticket


Why is this project dead?

Where is the owner, why not accept pullrequests?
Select a trusted person and give him rights to manage this project.

@arasatasaygin , I guess its a good project and a good number of people are using it.
It would be really nice if you can make it active or give someone merging rights.

Hey thanks for your interest. I'm on it https://github.com/arasatasaygin/is.js/issues/186


update-window.sh should handle both etcd and etcd2 installation.

Right now the update-window.sh won't work properly on etcd2 installation - it would just randomly reboot etcd2 members without reboot locking.

Note: @kayrus is working on a different approach to this concept.

Locksmith 0.3.4 has support for reboot windows. Once this hits Stable (should be next week), we will no longer need this workaround.

@joshix not yet.

Locksmith 0.3.4 has support for reboot windows. Once this hits Stable (should be next week), we will no longer need this workaround.

Has this become true?

Has this become true?

Yes.

Closing in favor of stock reboot window support in later versions of locksmith (0.3.4+)