A way to build a URL route

Hello!
I have a service with eight http endpoints and i need to build urls for it with multiple different parameters. Are there any way to implement something like url_for in flask:
Example:
class Service:
    @http('GET', '/url-one/<token>')
    def handle_url_one(self, request, token):
        pass

    @rpc
    def get_url_one(self):
        return '/url-one/' + token   # This is not DRY and error-prone approach
        # Wanted: return self.url_for(self.handle_url_one, token)

Thanks!

Nameko HTTP is built on Werkzeug, which is the WSGI library that underpins Flask. url_for is one of the conveniences that Flask adds, so it's not available out of the box.
It's not that hard to implement though. Nameko entrypoints attribute the service methods that they decorate, so you can inspect the service class to find them. This snippet should get you started:
from nameko.extensions import ENTRYPOINT_EXTENSIONS_ATTR
from nameko.web.handlers import http, HttpRequestHandler
from nameko.rpc import rpc

class Service:
    name = "serv"

    @http('GET', '/url-one/<token>')
    def handle_url_one(self, request, token):
        pass

    @rpc
    def get_url_one(self, token):

        entrypoints = getattr(self.handle_url_one, ENTRYPOINT_EXTENSIONS_ATTR)
        routes = [
            entrypoint.url for entrypoint in entrypoints
            if isinstance(entrypoint, HttpRequestHandler)
        ]
        return routes

Returns ['/url-one/<token>']. The logic you need to substitute the arguments into the string must exist in werkzeug somewhere.

Perfect, thank you! I can use werkzeug's Rule to instantiate a url rule, and build url map (werkzeugs Map) which can resolve urls with parameters.
The documentation is here: http://werkzeug.pocoo.org/docs/0.14/routing/#werkzeug.routing.MapAdapter.build
Thank!

I have created basic implementation. Check it out: https://gist.github.com/asyncee/afff12559e364b0665c89b0e53341c28

Nice!

This issue was moved to https://discourse.nameko.io/t/a-way-to-build-a-url-route/299


IGAPP-597: Migrate tools to typescript

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.
Fixes failing builds in #586. Hopefully not too many builds will fail in our next releases.

Not tested.

Tested a few commands.
sentry-release should als be converted, why have you skipped it?

Because this was only done to fix the build errors in #586 and converting sentry-release was not required. Since we initially decided not to convert tools to typescript at all I think that is fine. The least possibly breaking changes the better.


JSON payload (4638970 bytes) is larger than allowed (limit: 2097152 bytes).

When I verify contracts by standard input JSON  error output at web page: JSON payload (4638970 bytes) is larger than allowed (limit: 2097152 bytes).

hello, @youngqqcn , could you provide your standard JSON input (https://pastebin.com/ or smth)

Fixed in https://github.com/blockscout/blockscout-rs/pull/332. Now the maximum payload size may be specified via configuration variables. Adapted in smart-contract-verifier-v1.0.0 release


Set correct reference to shell_profiles.

fubarhouse_python -> fubarhouse_nvm

I noted this in an overhaul I've been working on in the past few days, but thank you!

@joestewart I've added the overhauled role early for you - there was some testing to be completed on RedHat, but it adds support for Darwin and RedHat among many other systematic improvements.
It's essentially ready for use and the vms I look after are beginning to use the new roles.

Thanks!  The simplified defaults are very helpful.  That and the Redhat support were the next two things that I had noted. :)
Maybe time for a release tag?
thanks again, seems to be working great.

@joestewart I'll organise a release tag once testing is complete across all the updated roles. There are some dependency issues on redhat I wish to either document or resolve on the python and pm2 roles, but the changes are universal among all of them other than the behat role which I might look at overhauling.
Apart from that, after documentation is updated and the meta files are correctly structured I'll certainly mark these roles as v1.0. :)


chore(release): v0.11.0 🎉

:robot: I have created a release beep boop
0.11.0 (2023-07-16)
Features

contents: enable declaring best practice contents based on project context (dfa75c3), closes #28

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ehmpathy/declapract/releases/tag/v0.11.0 :sunflower:


luci-app-samba4: add new UCI option "enable_extra_tuning"

add new UCI option "enable_extra_tuning"

Depends on openwrt/packages#12630

Note:
Normally every change should be packed into a separate commit.
Then these changes could be better cherry-picked.
Please keep this in mind in the future when you create a pullrequest.
Any change that does something different and is not too concatenated should be put into a separate commit.
I will merge this now.
Thanks for your contribution


Directional output

Audio should be sent to left or right output devices (depending on frequency.)

Not sure how feasible this is with "wav" format. More research required.

This may not actually be needed since the Tacview playback functionality provides this functionality. Moving to nice-to-have.


Windows test won't run under .NET 5.0 on AppVeyor

For now, we should just disable it

:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on:

GitHub Release
NuGet Package


[01_hello_saga] Fix invalid import

01_hello_saga
Issue in readme.md:
There is an invalid import in the code - the same viewer import twice. Context shows that it was about importing the setter.

Thanks


luci-base: add validation for APN datatype

Signed-off-by: Nicholas Smith<EMAIL_ADDRESS>Adds a new datatype/validation for APN (Access Point Name)

Use like this:
o = s.taboption('general', form.Value, 'apn',
			_('APN'),
			_("Setting the appropriate APN for your SIM and data subscription is recommended."));
o.datatype = 'apn';

Not sure about JS performance optimization logic, but I am not sure if it is wise to define this new rarely used validation function as the first one.
I would move the definition further down the possible evaluation queue.

Not sure about JS performance optimization logic, but I am not sure if it is wise to define this new rarely used validation function as the first one.
I would move the definition further down the possible evaluation queue.

Excellent point, I will move it down to the bottom, or near the bottom of the list.

Hmm, I think an APN datatype is a little bit too specific to go into the validation module. I'm slightly in favor of doing a custom validator function instead:
o.validate = function(section_id, value) {
    if (!/^[a-zA-Z0-9\-.]*[a-zA-Z0-9]$/.test(value))
        return _('Invalid APN provided');

    return true;
};

I guess that is doable, but I thought it would fit here because phonedigit is included.  What is your reservation for expanding the scope of the built-in validators based on?  Are we trying to keep the scope limited to IP-based networking and system administration tasks?  If so, then should we remove phonedigit?  If this gets included then luci-proto-modemmanager, luci-proto-qmi, and luci-proto-3g can use it straight away.


Zuul swallows exceptions from upstream microservices

Hey,
When an upstream microservice responds with let's say a 503 because of a throttling, Zuul's ribbonCommand will retry 1 more time. If that retry fails as well, the ribbonCommand fails, tries to find the fallback, and responds with a Forwarding error (500).
Because we'd like to tell the client whether it's a timeout or throttling or another issue, it would be useful to propagate the error through the gateway to the client, preferably as a nested cause of the Forwarding error.
What do you think about this?

I think that could be useful.

btw, https://jmnarloch.wordpress.com/2015/09/16/spring-cloud-zuul-error-handling/

SO discussion http://stackoverflow.com/questions/35294218/zuul-ribbon-exception-always-returns-500-response/35301837#35301837

So RestClient specifically treats a 503 differently.

@spencergibb so now zuul will forward 4xx errors properly? Cool, thanks.

@rozhok I'm unable to reproduce that. Any help there would be appreciated (sample project would be good).


fix: ForwardingLogger should foward block param

Also added tests to verify the default forwarding logger level, and to make sure it actually forwards logs.
Fixes #1599

@BrianHawley please review the EasyCLA.
If you accept it, we will proceed with a review of this PR.
Thank you.

@arielvalentin license accepted, thanks.

This seems to also be busted when using Ougai as the logger.

This introduced a bug if the logger used is Semantic Logger
OpenTelemetry error: no block given (yield)

coming from https://github.com/open-telemetry/opentelemetry-ruby/blob/main/sdk/lib/opentelemetry/sdk/forwarding_logger.rb#L41

Thanks, @adamk9k! I'll open an issue for this to take a closer look. If you know what needs to be done to fix the problem, please feel free to open a PR.

Thanks, @adamk9k! I'll open an issue for this to take a closer look. If you know what needs to be done to fix the problem, please feel free to open a PR.

Thank you @kaylareopelle in the meantime I've figured out what the issue was. It was coming from common/lib/opentelemetry/common/utilities.rb version 0.20.0 when it looked like this
def untraced
  Context.with_value(UNTRACED_KEY, true) do |ctx, _|
    yield ctx
  end
end

upgrading to 0.21.0 that includes this https://github.com/open-telemetry/opentelemetry-ruby/pull/1634 fixed it.

@adamk9k, that's great news! It sounds like nothing further needs to be done, and https://github.com/open-telemetry/opentelemetry-ruby/issues/1738 can be closed. Is that correct?

@kaylareopelle yes, thank you and sorry for the noise.

@adamk9k, no problem! Thanks for the update!


error while loading shared libraries: libjson-c.so.3 Ubuntu 20.04

I am afraid I cannot provide the version (it is not 2.18 from the repositories, but a newer version) because newsboat fails to load since it appears that libjson-c3 has been replaced with libjson-c4 in Ubuntu 20.04. Newsboat was working fine prior to me upgrading from 18.04 to 20.04.

There are a couple ways for you to fix this:

build Newsboat against the library you have;
install the library that the old build of Newsboat wants;
install Newsboat from the Snap Store, which carries a newer version that Ubuntu APT repos.

How did you install a newer version on Ubuntu 18.04? It's probably easiest for you to repeat the same process on Ubuntu 20.04.

Thank you. I compiled from source on Ubuntu 18.04. I took your suggestion, but make stops with the following error which I cannot decipher
g++ -std=c++11 -O2 -ggdb -Iinclude -Istfl -Ifilter -I. -Irss -Itarget/cxxbridge/libnewsboat-ffi/src/ -Werror -Wall -Wextra -Wunreachable-code -DLOCALEDIR='"/usr/local/share/locale"' -I/usr/include/x86_64-linux-gnu -I/usr/include/libxml2 -I/usr/include/json-c -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600  -o src/feedlistformaction.o -c src/feedlistformaction.cpp src/feedlistformaction.cpp: In member function ‘virtual bool newsboat::FeedListFormAction::process_operation(newsboat::Operation, bool, std::vector<std::__cxx11::basic_string<char> >*)’: src/feedlistformaction.cpp:303:34: error: ‘*((void*)& exit_code +1)’ may be used uninitialized in this function [-Werror=maybe-uninitialized]   303 |      v->show_error(strprintf::fmt(_("Browser returned error code %i"), *exit_code));       |                    ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/feedlistformaction.cpp:277:34: error: ‘*((void*)& exit_code +1)’ may be used uninitialized in this function [-Werror=maybe-uninitialized]   277 |      v->show_error(strprintf::fmt(_("Browser returned error code %i"),       |                    ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~   278 |        exit_code.value()));       |        ~~~~~~~~~~~~~~~~~~          cc1plus: all warnings being treated as errors make: *** [Makefile:172: src/feedlistformaction.o] Error 1

This warning comes from a third-party library we use, and it's pretty innocuous. I think we know what we're doing there :)
We turn warnings into errors to nudge users into reporting these things, so thanks for doing exactly that! Looks like we are not seeing this in CI because we don't compile with optimizations enabled on Ubuntu 20.04. I'll think what should be done about this.
Meanwhile, you can turn this error back into a warning by running CXXFLAGS="-Wno-error=maybe-uninitialized" make.

I cannot thank you enough; I would have never been able to sort this out without your help. Installed fine now. Happy days

Cool, glad you got it working! By the way, the warnings that you mentioned are now fixed by https://github.com/newsboat/newsboat/pull/1347, so 2.22 release won't have them. Funny that once you've reported them, our CI started displaying them as well :)

I need to reopen this issue. Trying to install 2.22, I now get two errors:
cc1plus: error: unrecognized command line option ‘-Wno-unknown-warning-option’ [-Werror] and src/itemlistformaction.cpp:196:33: error: ‘*((void*)& exit_code +1)’ may be used uninitialized in this function [-Werror=maybe-uninitialized]   196 |     v->show_error(strprintf::fmt(_("Browser returned error code %i"), *exit_code));       |                   ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/itemlistformaction.cpp:179:33: error: ‘*((void*)& exit_code +1)’ may be used uninitialized in this function [-Werror=maybe-uninitialized]   179 |     v->show_error(strprintf::fmt(_("Browser returned error code %i"), *exit_code));       |                   ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I tried to adapt the flag for this warning to be ignored, using
CXXFLAGS="-Werror=maybe-uninitialized" to no avail.

I need to reopen this issue. Trying to install 2.22, I now get two errors:
cc1plus: error: unrecognized command line option ‘-Wno-unknown-warning-option’ [-Werror] and src/itemlistformaction.cpp:196:33: error: ‘*((void*)& exit_code +1)’ may be used uninitialized in this function [-Werror=maybe-uninitialized]   196 |     v->show_error(strprintf::fmt(_("Browser returned error code %i"), *exit_code));       |                   ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/itemlistformaction.cpp:179:33: error: ‘*((void*)& exit_code +1)’ may be used uninitialized in this function [-Werror=maybe-uninitialized]   179 |     v->show_error(strprintf::fmt(_("Browser returned error code %i"), *exit_code));       |                   ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I tried to adapt the flag for this warning to be ignored, using
CXXFLAGS="-Werror=maybe-uninitialized" to no avail.

I need to reopen this issue. Trying to install 2.22, I now get two errors:
cc1plus: error: unrecognized command line option ‘-Wno-unknown-warning-option’ [-Werror] and src/itemlistformaction.cpp:196:33: error: ‘*((void*)& exit_code +1)’ may be used uninitialized in this function [-Werror=maybe-uninitialized]   196 |     v->show_error(strprintf::fmt(_("Browser returned error code %i"), *exit_code));       |                   ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/itemlistformaction.cpp:179:33: error: ‘*((void*)& exit_code +1)’ may be used uninitialized in this function [-Werror=maybe-uninitialized]   179 |     v->show_error(strprintf::fmt(_("Browser returned error code %i"), *exit_code));       |                   ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I tried to adapt the flag for this warning to be ignored, using
CXXFLAGS="-Werror=maybe-uninitialized" to no avail.

I need to reopen this issue. Trying to install 2.22, I now get two errors:
cc1plus: error: unrecognized command line option ‘-Wno-unknown-warning-option’ [-Werror] and src/itemlistformaction.cpp:196:33: error: ‘*((void*)& exit_code +1)’ may be used uninitialized in this function [-Werror=maybe-uninitialized]   196 |     v->show_error(strprintf::fmt(_("Browser returned error code %i"), *exit_code));       |                   ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ src/itemlistformaction.cpp:179:33: error: ‘*((void*)& exit_code +1)’ may be used uninitialized in this function [-Werror=maybe-uninitialized]   179 |     v->show_error(strprintf::fmt(_("Browser returned error code %i"), *exit_code));       |                   ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I tried to adapt the flag for this warning to be ignored, using
CXXFLAGS="-Werror=maybe-uninitialized" to no avail.

Reproduced. Please compile with CXXFLAGS="-Wno-error" to turn these errors back into warnings. Sorry they keep popping up, and thanks once again for reporting them!

Mere CXXFLAGS="-Wno-error=maybe-unitialized" doesn't work for a fairly bizarre reason: GCC doesn't support -Wno-unknown-warning-option, but doesn't complain about it unless there are other diagnostics. So when -Wmaybe-unitialized is triggered, GCC also prints a message about -Wno-unknown-warning-option. In the presence of -Werror, both messages are turned into errors. Even if we use -Wno-error=maybe-unitialized to demote that one back to the "warning" level, the message about the unsupported option is still treated as an error. I didn't find a way to selectively demote it to a warning, so I have to recommend -Wno-error.
I think this whole issue is caused by https://github.com/newsboat/newsboat/commit/f7f6d61cbdd5062e4bf3370e90f5f580ec12f1d6. My second assumption there is not entirely correct: we run newer compilers with -O3, not the default -O2, and so get a different set of warnings. I'll submit a PR that re-enables -O2 in all builds.
I'll also go ask the maintainer of optional-lite if this warning can be fixed upstream.

Reproduced. Please compile with CXXFLAGS="-Wno-error" to turn these errors back into warnings. Sorry they keep popping up, and thanks once again for reporting them!

Mere CXXFLAGS="-Wno-error=maybe-unitialized" doesn't work for a fairly bizarre reason: GCC doesn't support -Wno-unknown-warning-option, but doesn't complain about it unless there are other diagnostics. So when -Wmaybe-unitialized is triggered, GCC also prints a message about -Wno-unknown-warning-option. In the presence of -Werror, both messages are turned into errors. Even if we use -Wno-error=maybe-unitialized to demote that one back to the "warning" level, the message about the unsupported option is still treated as an error. I didn't find a way to selectively demote it to a warning, so I have to recommend -Wno-error.
I think this whole issue is caused by https://github.com/newsboat/newsboat/commit/f7f6d61cbdd5062e4bf3370e90f5f580ec12f1d6. My second assumption there is not entirely correct: we run newer compilers with -O3, not the default -O2, and so get a different set of warnings. I'll submit a PR that re-enables -O2 in all builds.
I'll also go ask the maintainer of optional-lite if this warning can be fixed upstream.

Confirming solution works. Thank you once again!

Confirming solution works. Thank you once again!

I'll also go ask the maintainer of optional-lite if this warning can be fixed upstream.

I'm pedalling back on this because I can't write a simple reproducer. Apparently this can only be triggered with a complex enough code, where optimizer no longer sees enough of the program to decide if the variable is initialized or not. I don't think this is something that optional-lite can fix, so I'm not going to file an issue with them.

I'll also go ask the maintainer of optional-lite if this warning can be fixed upstream.

I'm pedalling back on this because I can't write a simple reproducer. Apparently this can only be triggered with a complex enough code, where optimizer no longer sees enough of the program to decide if the variable is initialized or not. I don't think this is something that optional-lite can fix, so I'm not going to file an issue with them.


chore(config): check if param description contains unnecessary stuff

@robertsLando Like we talked about. This found a ton of warnings - I could use some help here:
Found 0 errors and 470 warnings!
@blhoward2 do you have a script to clean the descriptions?

Essentially. I have a function setup to parse over all the files and write it back. Changing what it does in the middle is just a few lines. I've been using it to fix things as I go, or like when I rewrote the metadata.
What needs cleaned?

Essentially. I have a function setup to parse over all the files and write it back. Changing what it does in the middle is just a few lines. I've been using it to fix things as I go, or like when I rewrote the metadata.
What needs cleaned?

Indentation in descriptions, check if description contains default/min/max and remove that too

Indentation in descriptions, check if description contains default/min/max and remove that too

If you now run the lint script locally you'll see about 470 warnings. Those need fixing.

If you now run the lint script locally you'll see about 470 warnings. Those need fixing.

I'll take a look.

I'll take a look.

Love new lint config :heart_eyes:

Since there's an influx of new contributors, this should be merged ASAP - will update the branch.

FYI I started working on pulling out the similar descriptions. I already went and hand jammed the ones that require changes to the label or unit...I just need to figure out why iterating the parameters in the file isn't working.


Initialize global mutext/sem by NXMUTEX_INITIALIZER and SEM_INITIALIZER

Summary
Continue the work: https://github.com/apache/incubator-nuttx/pull/6965
Impact
Code refactor
Testing
Pass CI

Hmm, it's too hard because the first commit is too big and has several changes other than the global muetx/sem initialization.

@masayuki2009 please review again.

@gustavonihei could you please review ESP32 related files?

@xiaoxiang781216
Please rebase this PR to the latest master.

@xiaoxiang781216 Please rebase this PR to the latest master and resolve the conflicts.

Done.

@masayuki2009 @pkarashchenko please review again.

@masayuki2009 @pkarashchenko do you have more comment or merge it if no?

I do not have more comments. Let's wait one more day to get feedback from @masayuki2009
I will merge the change if there will be no more comments.


Integration test with Capybara

For this PR I tested some functionalities of the app using RSpec and Capybara.
✅  Login page 👨💻
✅  User index page 📄
✅  User show page 💻
✅  User post index page ✍  ⌨
✅  Post-show page 🖥  📃

Thanks @DeliceLydia


update rayEllipsoid Param inverseRadii to radii

the param radii may be better than inverseRadii

Thank you so much @jiangheng90 ! :smile:


Cleaned up some extraneous whitespace characters

@JosephTLyons Looks good, thanks! I'll try not to add any more. :smile:


Unclosed connections with SPARQL::CLIENT

Hi there,
I've been struggling with a problem for a while now in my rails of unclosed connections leading to the app exceeding its limits and returning errors like:
Error during failsafe response: Too many open files @ rb_sysopen - /app/app/views/errors/internal_server_error.html.erb
After making sure every open-uri request is closed and no luck solving the problem I've started investigating deeper.
using lsof I've noticed each page request delivers the following
TCP <IP_ADDRESS>:52703-><IP_ADDRESS>:http (CLOSE_WAIT)
ruby    8093 jcwitt   50u     IPv4 0x47acd29a34c3cb9b        0t0        TCP <IP_ADDRESS>:52800-><IP_ADDRESS>:http (CLOSE_WAIT)
ruby    8093 jcwitt   51u     IPv4 0x47acd29a34bd9b9b        0t0        TCP <IP_ADDRESS>:52803-><IP_ADDRESS>:http (CLOSE_WAIT)
ruby    8093 jcwitt   52u     IPv4 0x47acd29a2bec3f7b        0t0        TCP <IP_ADDRESS>:52804-><IP_ADDRESS>:http (CLOSE_WAIT)
ruby    8093 jcwitt   53u     IPv4 0x47acd29a33acf23b        0t0        TCP <IP_ADDRESS>:52704-><IP_ADDRESS>:http (CLOSE_WAIT)
ruby    8093 jcwitt   54u     IPv4 0x47acd29a2df4723b        0t0        TCP <IP_ADDRESS>:52705-><IP_ADDRESS>:http (CLOSE_WAIT)
and as the app gets used the number of (CLOSE_WAIT) files keeps climbing, about 5 per page requests.
Using the IP, I learned that these requests are being made with the following snippet of code
sparql = SPARQL::Client.new(sparqlendpoint) result = sparql.query(query) return result
BTW I'm using sparql-client (~> 2.0).
So I'm wondering if I'm doing something wrong with the way I'm using SPARQL::Client or perhaps I've found a bug and SPARQL::Client should be closing connections and is not.
https://github.com/ruby-rdf/sparql-client/blob/develop/lib/sparql/client.rb#L726-L731
Among other places a http request is being opened at line 729.
Is getting closed anywhere?
I appreciate any help you can provide.

The connection is opened in SPARQL::Client#initialize, and is used for queries and updates using the resulting instance. It would normally be garbage collected, and the connection closed when the instance goes out of scope, as with general Ruby object management.
The gem uses Net::HTTP::Persistent, which does support a shutdown method. We should add a test to verify that this is called when the class is garbage collected.
We could also add a close method, which would make this explicit, but would need to clear the reference to Het::HTTP::Persistent, freeze the instance, and catch any further attempt to use it.
I would expect that the connection would be closed when the client instance is deallocated.

I would expect this kind of garbage collection as well,
The docs say as much

If you don't call shutdown, that's OK. Ruby will automatically garbage collect and shutdown your HTTP connections when the thread terminates.
(https://www.rubydoc.info/github/carlhuda/bundler/Net/HTTP/Persistent)

...which is why I am confused that the CLOSE_WAITS never go away but keep piling up.
But it really appears that these connections are not getting garbage collected. My rails app runs for about 12 hours, but then reliably crashes and return "Too many files open" errors for every subsequent attempt to open a new connection.
As mentioned above running lsof in development that the number CLOSE_WAIT files continues to climb.
Is there anything I can do, at the present, to force close the connection with modifying the sparql-client library directly?
Here's the code where I'm instantiating the SPARQL::CLIENT
sparql = SPARQL::Client.new(sparqlendpoint)
https://github.com/lombardpress/lbp.rb/blob/master/lib/lbp/query.rb#L33
I would love to force close the connection with something like sparql.close()
Or is there way to force close all open Net::HTTP::Persistent connections. Basically force garbage collection.

@jeffreycwitt can you try the "finish-connection" branch to see if it fixes your problem, it's in PR #87.

@gkellogg I'm now using the finish-connection branch now and the problem still seems to be persisting.
I've added a rails profiler.
And you can see here that via the sparql-client / net-persistant libraries 4 http calls are being made per page load to my sparql endpoint

Here you can see the output of lsof after 3 calls. There are now 12 open connections, the most page request still has 4 "ESTABLISHED" connection, the previous 8 request have moved from "ESTABLISHED" to "CLOSE_WAIT"

After a little more time, and no further requests, all "ESTABLISHED" requests move to "CLOSE_AND_WAIT" but the CLOSE_AND_WAIT connections never (seem) to go away, as you can see below.

On production server, this will continue until it reaches the open file limit, which on Heroku is 10,000 open files. Then I have to restart the server.
If you have any other ideas, I would really love to hear them. Thanks again for all the help thus far.
P.s. here are the links to my implementation of the sparql/client code.
First in my ruby gem (lbp.rb) in the Lbp::Query class
https://github.com/lombardpress/lbp.rb/blob/master/lib/lbp/query.rb#L33
The Lbp::Query class is then extended in the the "LombardPress-Web App", but the same Lbp::Query.query() method defined in the above link is used again and again through the LombardPress-Web App, as seen below.
https://github.com/lombardpress/lombardpress-web/blob/master/app/models/misc_query.rb

Can yo provide me with. Minimal example that reprocessing the problem? I beeeieve the issue lies in Net::HTTP::Persistant

Ok,
if you can close this branch of the lbp.rb gem
https://github.com/lombardpress/lbp.rb/tree/feature/close-wait-test
then run bundle

I just ran this again dbpedia's SPARQL endpoint as well to make sure my SPARQL endpoint wasn't doing something weird.
I get the same result, established connections, turning to close_and_wait, that don't seem to every fully close.

Hi @gkellogg,
just wondering if my gem branch was sufficient for you to recreate the problem. Let me know what I can do to help track down the issue. Should we create an issue with Net::HTTP::Persistent ???

I’ve been at W3C TPAC all week, so haven’t had a chance to follow up. When I can reproduce, perhaps we’ll be able to see if Net::HTTP::Persistent is indeed implicated. We’d need a reproducible use case.

Ok no worries whatsoever.
I think have a created a reproducible use case. Whenever you have time see my post above: https://github.com/ruby-rdf/sparql-client/issues/86#issuecomment-431565395.
Let me know if you don't think this is sufficient or can't reproduce yourself. I was able to reduce the problem with both my SPARQL endpoint and the dbpedia SPARQL endpoint .
Best,
jw


react native support

see https://github.com/iamcal/js-emoji/pull/106
@iamcal let me know if you want the uglify build on here as well.

Coverage remained the same at 90.146% when pulling cf0313fb2cd6553980427d059674d4249e2c6e2b on jasondibenedetto:master into 0c44c758859b64b4fb1b325b3ef24f1804b40412 on iamcal:master.

merged in #122


Update node version to the latest

Description
The latest node version is 14.17.3 as of writing and this fixes #86.

lgtm, thanks


feat(util): Add more verbose output to spawn process

/roast me

@kamilogorek would you mind reviewing my changes as well?


Update PyTorch to v2.1.0

Update PyTorch and dependencies to v2.1.*

[ ] Update AV to v11.0
[ ] Update PyTorch to v2.1.0
[x] Update sentencepiece to v0.1.99
[x] Update torchtext to v0.16.0
[x] Update torchvision to v0.16.0
[x] Update torchdata to v0.7.0

Pytorch v2.1.1 is likely to be tagged soon.

PyTorch v2.1.1 is tagged. So we can target the following versions:

[ ]  Update AV to v11.0
[ ]  Update PyTorch to v2.1.1
[X]  Update sentencepiece to v0.1.99
[ ]  Update torchtext to v0.16.1
[ ]  Update torchvision to v0.16.1
[ ]  Update torchdata to v0.7.1

As we see that there is a difference in the ffmpeg versions needed for torchvison and AV, we have decided to keep AV at v10.0.0.

Refreshed PyTorch to v2.1.1
Refreshed Sentencepiece to v0.1.99
Refreshed Torchtext to v0.16.1
Refreshed Torchvision to v0.16.1
Refreshed Torchdata to v0.7.1

[ ] Refreshed PyTorch to v2.1.2

[ ] Refreshed Sentencepiece to v0.1.99

[ ] Refreshed Torchtext to v0.16.1

[ ] Refreshed Torchvision to v0.16.1

[ ] Refreshed Torchdata to v0.7.1

Please refer: https://github.com/open-ce/pytorch-feedstock/pull/119


openldap: fix build if openssl or cyrus_sasl are overridden to null

Motivation for this change
Compiling openldap.override { cyrus_sasl = null; } results in an evaluation error.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @lovek323

Sorry everyone, rebasing against master instead of staging by accident completely made github subscribe a lot of people to this PR, you might wanna unsubscribe. 😑

Sorry everyone, rebasing against master instead of staging by accident completely made github subscribe a lot of people to this PR, you might wanna unsubscribe. 😑

Can we add a flag for this? Overwriting an input with null is not that nice.

Sure.

Can we add a flag for this? Overwriting an input with null is not that nice.

Sure.

Other than that LGTM.

Other than that LGTM.

@sternenseemann you did not rebase cleanly and left a merge conflict in.

Should be fine now.

openldap.override { withCyrusSasl = true; }

Also cross compiles to aarch64-multilib.

What GitHub merge method did you use? Apparently this is one where it loses all commit messages except for the (in this case slightly out of date) PR title and number? Would be nice to use one which preserves the commit messages even when squashing.

Squashing. The is no never method to squash and keep the title. I would need to force push that to your branch.

@SuperSandro2000  Please don’t squash PRs with sensible commits.

Rebase them instead

Alternatively, squash them locally to keep all descriptions and then push the squashed commit before merging. All extended descriptions that @sternenseemann wrote just went away.

Alternatively, squash them locally to keep all descriptions and then push the squashed commit before merging. All extended descriptions that @sternenseemann wrote just went away.

git sometimes takes 10 minutes to force push other peoples branches and runs out of memory. I am to lazy to wait for that.


[Error] Function not registered: PC_Init

I get this error when I run the server. Where I need to put it to work?

Attach full server_log.txt

[21:06:47] [Info] Loading plugin: sscanf
[21:06:47] [Info]
[21:06:47] [Info]  ===============================
[21:06:47] [Info]
[21:06:47] [Info]       sscanf plugin loaded.
[21:06:47] [Info]
[21:06:47] [Info]          Version: 2.13.2
[21:06:47] [Info]
[21:06:47] [Info]    (c) 2022 Alex "Y_Less" Cole
[21:06:47] [Info]
[21:06:47] [Info]  ===============================
[21:06:47] [Info]
[21:06:47] [Info] Loading plugin: mysql
[21:06:47] [Info]  >> plugin.mysql: R41-4 successfully loaded.
[21:06:47] [Error] Skipping legacy plugin 'pawncmd'; There is an open.mp compatible version you can find here: https://github.com/katursis/Pawn.CMD/releases , make sure to download x.x.x-omp version.
[21:06:48] [Error] Function not registered: PC_Init
[21:06:48] [Error] File or function is not found
[21:06:48] [Error] File or function is not found
[21:06:48] [Info] Legacy Network started on port 7777
[21:06:52] [Error] File or function is not found
[21:06:52] [Info]
[21:06:52] [Info]  ===============================
[21:06:52] [Info]
[21:06:52] [Info]      sscanf plugin unloaded.
[21:06:52] [Info]
[21:06:52] [Info]  ===============================
[21:06:52] [Info]
[21:06:52] [Info] plugin.mysql: Unloading plugin...
[21:06:52] [Info] plugin.mysql: Plugin unloaded.

I resolved it. My fault is I putted the dll file in plugins.


RPC call author_insertKey failed, Method not found

substrate version:
➜  substrate git:(7e9a2ae78) ./target/release/substrate --version
substrate 2.0.0-alpha.8-7e9a2ae78-x86_64-macos

start substrate:
./target/release/substrate purge-chain --dev

./target/release/substrate --dev

call author_insertKey:
curl http://localhost:9933 -H "Content-Type:application/json;charset=utf-8" -d \
               '{
        "jsonrpc":"2.0",
        "id":1,
        "method":"author_insertKey",
        "params":["aura","strategy barely old print movie april gossip interest velvet endorse clever office","0x0ed4b40d52c0fd128b01774817656570ef7fe9a4497bf2a05fbc830e11"]
    }'

i got error:
{"jsonrpc":"2.0","error":{"code":-32601,"message":"Method not found"},"id":1}

in apps ui also has this problem

i found run cmd flag can fix this problem
--rpc-methods=Unsafe

Yeah there was a bug, that was fixed on master.

In my case, it's throwing this error when I pass my Polkadot account's mnemonic and address in the above author_insertKey method as below:
curl http://localhost:9933 -H "Content-Type:application/json;charset=utf-8" -d
'{
"jsonrpc":"2.0",
"id":1,
"method":"author_insertKey",
"params":["aura","weird god heaven reopen may infant since behold fall census love curb","0x5DcEwS93cx8dfWbU5zB5pwgcjs7yFQbt3tEaqvHHE6xzEEUy"]
}'
{"jsonrpc":"2.0","error":{"code":-32602,"message":"Invalid params: invalid hex character: w, at 6."},"id":1}


Indicate range for editor.suggest.maxVisibleSuggestions

Testing https://github.com/Microsoft/vscode/issues/71084

It would be helpful to know the range of editor.suggest.maxVisibleSuggestions. For example, it would be nice to know that there is a max of 12 items.

@aeschli What's the recommended approach here. The bounds are defined in the scheme, should I copy them into the label or should this be part of the "type-label"?

Added the max to the message and bumped that to 15


Ability to lookup printer at runtime

Currently, the printer name/type has to be specified in code.
We want to pass the printer name etc as parameter to printViaNetwork() and printViaBluetooth()

You can use the Printer().getNetPrinters() method to find all printers on the network, but you must know the model name in advance... This is unfortunately how brother designed their API. You can of course keep a list of many model names, and then iterate them all to find all the printers of various types.
You can also do direct printing via USB, but again, you need to know the model type in advance.

Instead of passing the printer model as a parameter, it would probably be best to set it from another method, so all the methods in the printer library that require the model can reference it globally, without it needing to be passed around constantly.

Thank you very much for the input @gordol .
Most apporeciated

fixed in https://github.com/MenelicSoftware/cordova-plugin-brother-label-printer/pull/3


Significant BLE Slowness After Reconnection on Android 15 QPR1 with RxAndroidBle

Describe the bug
After successfully connecting and bonding with a BLE device using RxAndroidBle, subsequent connections experience significant delays, particularly during MTU requests and characteristic read/write operations. This issue is observed primarily on devices running Android 15 QPR1 Beta and appears to be related to changes in the Bluetooth stack on this version.
To Reproduce
Steps to reproduce the behavior:

Pair and connect to a BLE device using RxAndroidBle.
Disconnect the device or restart the BLE peripheral.
Attempt to reconnect and perform the same operations.
Observe the significant delay in operations during the reconnection phase.

Expected behavior
BLE connections should be stable and fast across initial and subsequent reconnections, similar to the behavior observed on Android 14 and below.
Smartphone:

Device: Google Pixel 6, Google Pixel 9
OS: Android 15 QPR1 Beta 4.1 (Build: AP41.240726.010 - August 29, 2024)
Library version: RxAndroidBle 1.18.1

Logs from the application when bug occurs

Start of connection and noticeable delay during MTU request
2024-09-04 19:03:43.205 12221-12439 [Bluetooth...vity L:119 app.theranica.neriviomigra           D  QUEUED   ConnectOperation(128601542)
2024-09-04 19:03:43.207 12221-12361 [Bluetooth...vity L:119 app.theranica.neriviomigra           D  STARTED  ConnectOperation(128601542)
2024-09-04 19:03:43.211 12221-12363 BluetoothGatt           app.theranica.neriviomigra           D  connect() - device: XX:XX:XX:XX:17:3F, auto: false
2024-09-04 19:03:43.590 12221-12461 BluetoothGatt           app.theranica.neriviomigra           D  onClientConnectionState() - status=0 clientIf=6 connected=true device=00:A0:50:0D:17:3F
2024-09-04 19:03:44.600 12221-12451 [Bluetooth...$2$2 L:352 app.theranica.neriviomigra           D  Requesting MTU
2024-09-04 19:03:44.614 12221-12363 BluetoothGatt           app.theranica.neriviomigra           D  configureMTU() - device: XX:XX:XX:XX:17:3F mtu: 512
2024-09-04 19:03:47.607 12221-12453 [Bluetooth...$2$1 L:470 app.theranica.neriviomigra           D  Retrying MTU request: attempt 1
2024-09-04 19:03:48.928 12221-12461 BluetoothGatt           app.theranica.neriviomigra           D  onConfigureMTU() - Device=00:A0:50:0D:17:3F mtu=512 status=0
2024-09-04 19:03:48.937 12221-13137 [Bluetooth...vity L:119 app.theranica.neriviomigra           D  FINISHED MtuRequestOperation(104128157) in 4328 ms

Delay in characteristic read after service discovery
2024-09-04 19:03:48.958 12221-12363 BluetoothGatt           app.theranica.neriviomigra           D  discoverServices() - device: XX:XX:XX:XX:17:3F
2024-09-04 19:03:48.967 12221-12461 BluetoothGatt           app.theranica.neriviomigra           D  onSearchComplete() = Device=00:A0:50:0D:17:3F Status=0
2024-09-04 19:03:48.973 12221-13137 [Bluetooth...vity L:119 app.theranica.neriviomigra           D  STARTED  CharacteristicReadOperation(204334072)
2024-09-04 19:03:50.909 12221-12461 [Bluetooth...vity L:118 app.theranica.neriviomigra           I  MAC='00:A0:50:0D:17:3F'     onCharacteristicRead(), status=0, value=[uuid='71387662-eb78-11e6-b006-92361f002671', hexValue=[31, 20, 30, 20, 65, 62, 39, 33, ...]]
2024-09-04 19:03:50.913 12221-13137 [Bluetooth...vity L:119 app.theranica.neriviomigra           D  FINISHED CharacteristicReadOperation(204334072) in 1938 ms

Further delays in characteristic read/write operations
2024-09-04 19:03:51.901 12221-12461 [Bluetooth...vity L:118 app.theranica.neriviomigra           I  MAC='00:A0:50:0D:17:3F'     onCharacteristicRead(), status=0, value=[uuid='71387662-eb78-11e6-b006-92361f002671', hexValue=[31, 20, 30, 20, 65, 62, 39, 33, ...]]
2024-09-04 19:03:51.903 12221-13137 [Bluetooth...vity L:119 app.theranica.neriviomigra           D  FINISHED CharacteristicReadOperation(114573011) in 974 ms

Additional context

We have attempted multiple potential workarounds, such as refreshing the GATT cache using reflection via BluetoothGatt, setting connection priorities, enhancing disconnection handling, and re-bonding the device on each connection attempt. None of these have resolved the issue.
The problem does not occur on Android 14 or below, indicating a possible change in the Bluetooth stack behavior on Android 15.
Restarting the Bluetooth adapter or the entire device temporarily resolves the issue but does not provide a long-term fix.
We are also in communication with Google regarding this issue in their issue tracker: Google Issue Tracker.

We are looking for any insights or suggestions from your side that might help us further investigate or work around this issue. If there's any additional information or specific scenarios you need, please let us know.

Thank you for the report. Have you seen any library logs that would have onConnectionUpdated part? I wonder if these have been changed on Android 15

@dariuszseweryn Thank you for your reply. I enabled debug logging for RxAndroidBle and tested both the first-time connection (with pairing/bonding) and subsequent connections to the BLE device. Here is what I observed:
First-Time Connection (Pairing/Bonding):

The connection request prompts for pairing and bonding as expected, and all operations, including MTU requests and characteristic reads/writes, complete swiftly without noticeable delays.
The onConnectionUpdated log does not appear immediately after this initial connection.

Subsequent Connections (After Initial Pairing/Bonding):

After the first successful pairing connection, subsequent connections (which do not require bonding again) exhibit significant delays.
The following log lines are observed from both the BluetoothGatt and the RxAndroidBle library during the subsequent connection:
2024-09-07 12:45:53.716 22572-22732 BluetoothGatt           app.theranica.neriviomigra           D  onConnectionUpdated() - Device=00:A0:50:0D:17:3F interval=396 latency=0 timeout=200 status=0
2024-09-07 12:45:53.719 22572-22732 [Bluetooth...vity L:118 app.theranica.neriviomigra           I  MAC='00:A0:50:0D:17:3F'      onConnectionUpdated(), status=0, interval=396 (495.00 ms), latency=0, timeout=200 (2000 ms)
The delay occurs particularly during the MTU request phase (taking about 4 seconds) and characteristic read operations.

Behavior Across Multiple Devices:

This pattern is consistent across different BLE devices. Switching to a new device results in a quick initial connection with pairing, but subsequent connections become slow again unless we reset the Bluetooth stack (e.g., turning Bluetooth off/on or restarting the phone). Turning Bluetooth off/on typically resolves the slowness temporarily, though not always. Restarting the phone generally restores stability for a longer period, but the issue has been observed to reoccur after some time.
Once the slowness occurs in the connection, all subsequent operations involving characteristic reads and writes are also delayed. For example, in our app, starting or pausing a treatment for a medical device involves writing commands to the BLE device and reading responses using readCharacteristic from the RxAndroidBle library.

Our Implementation:
In our implementation, the MTU request is made immediately after establishing a connection and before discovering services, as shown in our code snippet:
bleDevice.establishConnection(false)
    .flatMapSingle { rxBleConnection ->
        logD(LogCategory.Bluetooth, "Connection established")
        bleConnection = rxBleConnection
        Single.timer(1, TimeUnit.SECONDS)
    }
    .flatMapSingle {
        logD(LogCategory.Bluetooth, "Requesting MTU")
        bleConnection?.requestMtu(512)?.timeout(6, TimeUnit.SECONDS)
    }
    .flatMapSingle {
        logD(LogCategory.Bluetooth, "MTU request success")
        logD(LogCategory.Bluetooth, "Discovering services")
        bleConnection?.discoverServices()
    }

Request for Your Insights:
Based on these observations, it seems that something may change in the BLE stack after the initial connection and bonding. Could changes in how the onConnectionUpdated event is handled on Android 15, or another factor, be contributing to this behavior?
We would greatly appreciate any insights or recommendations you might have to further investigate or work around this issue.
Thank you again for your assistance!

My suspicion: It may be that Android 15 negotiates lower connection priority after initial setup.
You could check if the connection parameters are updated on Android 14 — I guess not.
As a workaround, setting connection priority after it was changed by Android 15 could help.

Thank you for your suggestion regarding setting the BLE connection priority after it was changed by Android 15. I implemented this workaround as follows:
After establishing the connection, I set the BLE connection priority to CONNECTION_PRIORITY_HIGH to ensure stable communication. Here is a brief code snippet showing the implementation:
bleDevice.establishConnection(false)
    .flatMapSingle { rxBleConnection ->
        logD(LogCategory.Bluetooth, "Connection established")

        val localBleConnection = rxBleConnection
        bleConnection = localBleConnection

        // Apply workaround for Android 15 and above
        if (isAndroid15andAbove()) {
            localBleConnection.requestConnectionPriority(
                BluetoothGatt.CONNECTION_PRIORITY_HIGH,
                2, TimeUnit.SECONDS
            )
                .doOnComplete { logD(LogCategory.Bluetooth, "Connection priority set to high") }
                .andThen(Single.timer(1, TimeUnit.SECONDS)) // Delay for 1 second
        } else {
            Single.timer(1, TimeUnit.SECONDS)
        }
    }
    .flatMapSingle {
        logD(LogCategory.Bluetooth, "Requesting MTU")
        if (isAndroid15andAbove()) {
            bleConnection?.requestMtu(512)?.timeout(6, TimeUnit.SECONDS)
        } else {
            bleConnection?.requestMtu(512)?.timeout(3, TimeUnit.SECONDS)
        }
    }

Observations:

On Android 14, the onConnectionUpdated log is not triggered at all after establishing any connection (both first-time and subsequent connections), suggesting that this behavior of triggering onConnectionUpdated might be new or specific to Android 15.

Initial testing shows promising results, with improved connection stability and reduced delays on Android 15.

Thank you again for your support!


Rules based override of tradition effects/localization.

Given changes in #3. Rules may be applied in extra links after all of the base mappings.
link = { ck3 = { tradition = tradition_seafaring } eu4 = { naval_forcelimit_modifier = 0.1 } }
Would be overridden with.
link = { ck3 = { tradition = tradition_seafaring } eu4 = { may_explore = yes } modifier = { heritage = heritage_north_germanic} }
The keywords underneath modifier will all have associated rules defined somewhere in the DynamicIdeasMapper scope. When creating an idea group, the mapper will map a CK3 tradition to it's base EU4 effect unless an override rule is true for that culture. Then the alternate EU4 effect will apply for that culture only. A new localization identifier will have to be dynamically crafted and the localizations copied over as described in #9.

Rules will have

An identifier "heritage"
A precedence level "0"
- A link can have multiple rules, in this case start with the valid links with the lowest precedence rule.
- If there are more than one. Go to the next rule in each remaining link.
- Given rules exclusionary principle this can never result in a tie.
A function testing the rule
- The rule may have many states to test against but they must be Exclusionary.
- E.g. True if culture has provinces in region is invalid because cultures can have provinces in more than one region.
- True if culture has more provinces in region than any other region is valid because it can only be true for one region at a time.


Push SQL user defined functions and imports into LogicalPlan

This will allow us to provide better, earlier error messages when invoking functions, executing queries and mounting views and modules.
Currently, functions are simply inlined at SQL layer which means there is no good way to validate that a function is semantically correct without actually calling that function. If we actually add a representation for functions at the LogicalPlan level, we will be able to verify a function body in isolation of any particular arguments it may receive when being invoked.

@jdegoes , @alissapajer -> can y'all comment on the relative importance of this and hence prioritization.

Another concrete example @natefaubion just brought up is that calling a function with the wrong number of arguments currently yields a "Function Not Found" error which is rather confusing. That's so that user defined functions don't shadow library functions (if they have a different argument, but if user defined functions were in LP, it would make it possible to provide a better error message without shadowing.

So, this ticket will provide better error messages for the user when using functions. @jedesah are there other specific errors you know of that will be made possible besides the one you just mentioned?
@zeeiyerWork I think the priority of this ticket should be driven by customer needs. When customers need these better error messages then we can get this done. To my knowledge it's not blocking anything from an engineering point of view.

@alissapajer It will also provide earlier compile errors when mounting a module. Currently, it's possible to mount anything that parses, even if it's otherwise complete gibberish. Only when the function is called will we find that out. I recall complaining a few times about functions not being pushed to LP in the discussion when you reviewing my imports PR, but I don't remember everything I complained about 😄
But I agree that it should be driven by the priority of providing this better experience to the user. If modules are mostly used by the frontend to implement sane sharing of dashboards then I don't think  this is likely to be very visible to users. If, however, users start using functions and modules heavily "manually" to structure their own queries then this is likely to become much more visible and frustrating for them.
It's a little bit of technical debt because we might build around the current implementation, but my prediction is that the interest rate will be very low so I don't think that needs to be an important factor in deciding when to implement this.

@alissapajer, @jedesah  -> Better error messaging is a business priority - but given how packed current iterations are - scheduling this for a 4.3.x release target (i.e. October iteration)


Default name of the create NATS module CR button is rendered wrong

Description
Default name of the create NATS module CR button is rendered wrong (see attached).
Expected results
The button label should say "Create NATS".
Actual results
The button label says "Create NAT".

/remove-lifecycle stale

/reopen

No longer valid, product standards says that there should be only Create.


[BUG] There is no button to change the interface in roblox, please fix it

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
v2.8.1
What problem did you encounter?
There is no button to change the interface in roblox, please fix it
Bloxstrap Log
N/A

they removed it for now because it was unstable to support, at a later date maybe it will be added again.

it is REMOVED but the v4 menu (minus chrome) still works, soo
just add this:
{
"FFlagEnableMenuControlsABTest":false,
"FFlagEnableV3MenuABTest3":false,
"FFlagEnableInGameMenuChromeABTest3":false,
"FFlagEnableInGameMenuChromeABTest4":false,
"FFlagEnableInGameMenuControls":true,
"FFlagEnableInGameMenuModernization":true,
"FFlagEnableInGameMenuChrome":false
}

"The engine setting preset for the Roblox escape menu version has been removed. It's become increasingly unstable overtime as Roblox continues to make breaking changes to how it works. It may be readded at a later date when we can support it properly."


Crash fix due to bookmarks authority on prod variant

Title (required)
Fixes #1967
Description (required)
The authority for prod variant wasn't set properly as a result of which the app was crashing.
Tests performed (required)
Tested on prodDebug variant. Crash no longer happens.

Codecov Report

Merging #1977 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1977   +/-   ##
======================================
  Coverage    4.37%   4.37%
======================================
  Files         211     211
  Lines       10632   10632
  Branches      954     954
======================================
  Hits          465     465
  Misses      10132   10132
  Partials       35      35

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 e8f4a28...8a6c416. Read the comment docs.

Tested tutorial, login, home, media detail view, favoriting and unfavoriting a self-photo, explore, favoriting and unfavoriting a non-self-photo, about page.
2.8.5-debug-pr-1977~8a6c416c (prodDebug) on Samsung Galaxy S6 with API level 25.
2.8.5-debug-pr-1977~8a6c416c (prodDebug) on Galaxy Nexus (simulated) with API level 28.
All working, and bug no longer occurs.


FMG-131: fix removing a form from the list when it is the only one on…

… the page

Related to: PR

Related to: PR


Submodel Digital Nameplate for Industrial Equipment (02006) - sematicID in ECLASS not found

I could not found the semanticID's for SMC Markings (0173-1#01-AGZ673#001) and Marking (0173-1#01-AHD206#001) in ECLASS.
For the (old) ZVEI-SMT the Blocks could be found. I am thankful for any guidance where to find the Blocks for the actual template in ECLASS.

The ECLASS blocks 0173-1#01-AGZ673#001 (SMC Markings) and 0173-1#01-AHD206#001 (SMC Marking) were introduced with ECLASS 14.0 on 2023-11-20


DPI Scaling: Text input box too large on high-DPI screens

As can be seen in the image below, the text input box and the text inside it is way too large on high-DPI setups (in my case 2x scaling):

Using latest master (39a8e8193c3bee320e11e6c57fdc6927b3f3558e)

On this device I have the issue that the the CTRL + F window, is small at the beginning and then suddenly changes size, not exactly sure from where that is coming from.

just downloaded chatterino and this is still an issue on chatterino 2.5.1. I played a little with windows compatibility settings for high-dpi but that just makes it worse.

@nevotheless can you try enabling the beta branch in your settings then trying the 2.5.2-beta.1 version? it should have improved high dpi support on windows

hmmm it certainly looks more native to the dpi. But doesn't seem to respect the scaling like other apps do. (My scaling is 200% which is recommended by windows)
After the update the sizes in chatterino looking more uniform but tiny as hell.

I don't have a UHD monitor at my disposal, but the last time I tried one, it ✨ just worked ✨. Are you sure your Chatterino is scaled correctly? Did you try the default settings (e.g. on a portable version)? Are you sure you're using the Qt 6 builds?

the chatterino installation is as default as it can be. After restarting chatterino after the update it looks different / better now (tabs are correct size, chat size seems to be correct, just some minor line hight shenanigans with the input box left)


Milestone v0.6.0 Prep

Please leave a comment with things/issues you think we should work on during the v0.6.0 milestone

https://github.com/openservicemesh/osm/issues/1912
https://github.com/openservicemesh/osm/issues/1909
https://github.com/openservicemesh/osm/issues/1907
https://github.com/openservicemesh/osm/issues/1797
https://github.com/openservicemesh/osm/issues/1895


Logging directly related model attributes

Hi!
I need to save the value of my id and not the id in the properties field.
<?php

namespace App;

use Illuminate\Contracts\Auth\MustVerifyEmail;
use Illuminate\Foundation\Auth\User as Authenticatable;
use Illuminate\Notifications\Notifiable;
use Spatie\Activitylog\Traits\LogsActivity;

class User extends Authenticatable
{
    use Notifiable, LogsActivity;

    /**
     * The attributes that are mass assignable.
     *
     * @var array
     */
    protected $fillable = [
        'name', 'email', 'password', 'id_rol'
    ];

    protected static $logAttributes = ['name', 'email', 'rol.nombre'];
    //protected static $logFillable = true;
    //protected static $logOnlyDirty = true;

    /**
     * The attributes that should be hidden for arrays.
     *
     * @var array
     */
    protected $hidden = [
        'password', 'remember_token',
    ];

    /**
     * The attributes that should be cast to native types.
     *
     * @var array
     */
    protected $casts = [
        'email_verified_at' => 'datetime',
    ];

    public function rol(){
        return $this->belongsTo('App\Rol');
    }

}

Hey,
could you get into more detail? Right now I've no idea what you try to accomplish and why it doesn't work. If you want to log the user ID simply add it to the list of loggable attributes. Even if I don't know why the ID should be monitored because if it's changeable it isn't an ID.


Basic Level Driver Code

Implement the most basic level flow including the timeout code, points, and a goal. Take the current screen and put it in a debug screen.

Includes the time and expose to environment


Set Kafka retention to 1 Week

Test and Verified
Compare with Install and Upgrade working environments. Check settings to Kafka by: /opt/cm-well/conf/kafka/server.properties
Tested environment over a week, each day tested Kafka queue for the first infoton at the queue by: kafka-simple-consumer-shell.sh --broker-list localhost:9092 --max-messages 1 --offset -2 --partition 0 --print-offsets --topic persist_topic
Close & Moving to Done


Notifying users of future service outages and changes

There needs to be some mechanism -- on the initial HydroShare page -- that notifies users of future events like downtime and releases.  The way this is typically done is as follows:

In an admin interface, someone like Michael writes a message with a start and end date, specifying the outage or change to be made. Most systems allow one to also specify a "posting date" so that one can write notifications that appear in the future. This particular design is based upon the notification system in ExpressionEngine, upon which www.cuahsi.org is based. It is typical.
Then we write code that shows those notifications on the start page, for which the posting date >= today and the end date <= today.
When the end date is passed, the notification automatically disappears but is kept in a history. Thus, users can view past notifications on a history page, as desired. .

We have an MOTD now. Closing this.


mvc instalation

Hello,
I need some help installing the react-color in an mvc project.
Can you install it on a new mvc project as an example and upload it?
Thanks!!!

I'm not sure what you mean by an MVC project? Please provide me with a link
to your project with the colo picker in it and I am happy to debug it.
On Thu, Jun 15, 2017 at 11:54 PM hgonzalez<EMAIL_ADDRESS>wrote:

Hello,
I need some help installing the react-color in an mvc project.
Can you install it on a new mvc project as an example and upload it?
Thanks!!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/casesandberg/react-color/issues/361, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AEa0JKpD4dG4pOvx2qs_1JxO3PmXka1iks5sEiaagaJpZM4N8F1B
.

I want to install the widget in a Microsoft project MVC 5.
See the reference (https://www.asp.net/mvc)

Can you send me a link to the project where you tried to implement it? Happy to try and debug it

https://github.com/DiamontCP/mvc-react-color
They are only twoo thinks in this repo.

New mvc project.
Form example.

It will be great if you can commit separate:
a) the react needed files for the installation.
b) A basic usage of the widget in the for I created.
I think it will be a good contribution for all the .Net community for using you're witget.
Thanks 4 all.

Hi Case, have you seen my last post?
Thanks

Hey @DiamontCP, I, unfortunately, do not know .NET or MVC so I can't be of much help. If you have code where you can get it implemented I am more that happy to take a look and help out with a form example.
I think a good first step would be to try and get NPM modules working within MVC: https://stackoverflow.com/questions/37935524/how-to-use-npm-with-asp-net-core

Hi Case,
Thanks you much for the info. It is a very good approach what I am looking for.
If you think it would be useful, I can try it and do a tuto of this for those .net developers who want to use yours pickers.

That would be great! Feel free to post your findings in here so that anyone searching about it will be able to find info about it :)


[Client/Server] Exotic character break the encryption

Description
If using äö (or anything else exotic) with reverse/matrix methods, it fails on Client/Server but not on console.
Steps to Reproduce the Problem

Send a message through the client encrypted with reverse/matrix.
:boom:

Expected Behavior
Get the proper encrypted/decrypted message.
Reproduces how often: [What percentage of the time does it reproduce?]
Every time.
Additional info
Related to #7.

This issue does not manifest itself, if both server and client are running on same windows mahchine.

See also issue #7 since these are related, as a-rmz referenced above.

Issue #7 patch fixed this problem, so the issue can be closed.

Fixed in #7.


Again cannot change config file with new versions.

Hi, i saw in changelog that the new version of this mod have a "Config file fix" but with the latest versions of tinker and mantle the issue is back again.
I donwloaded the files from twitch app, and are the latest for 1.12.2. When i change the config file nothing happens, i tried creating new world, recreating the config file.. nothing, its like the mod doesnt read the config file at all. even the minmodifiers doesnt work.

Tinker tool leveling 1.0.3
tinker construct <IP_ADDRESS>
Mantle  <IP_ADDRESS>
Forge 2657

Same problem here, config values are ignored. Using TinkerToolLeveling 1.0.3 with TConstruct <IP_ADDRESS>

Cannot reproduce, works fine for me. Maybe you don't have proper rights on the file system, or you entered an invalid value?

Cleanup, closing old tickets.


Clarify why a specific hostname is expected in the server certificate

My proposed clarification for
https://github.com/matrix-org/matrix-doc/issues/3321

(we also need sign-off per the contributing guidelines. Easiest way is to leave a Signed-off-by: Your Name<EMAIL_ADDRESS>comment here, but the full range of options are described in the guidelines)

Signed-off-by: Niels Basjes<EMAIL_ADDRESS>


Ambiguity of nested hpx::future's.

When future < T >  is created using a function returning a future < T >  instead of a T, the outer future is not made ready until the inner future is complete.
However, when a futue< void > is created using a function returning a future< void > instead of void, the outer future is made ready as soon as the inner future is returned - which could be (and often is) before the inner future is made ready.
Example:
hpx::future<void> fut = hpx::async( []() {
     do_work();
     return hpx::async( []() {
        do_more_work();
     };
});

Given the behavior of nested non-void futures, one would expect fut would not be made ready until after do_more_work() is executed. Apparently (from bugs I have fixed in Octo-tiger) this is not the case. Instead fut is made ready when the inner future is created and returned, which is (usually) before do_more_work() is complete.
I have fixed two bugs in Octo-tiger that were of this type, and each time the bugs were not readily reproducible and took many days and SUs to narrow down the problem and confirm I had fixed it.
Is this the intended behavior of nested void futures or is this a bug?

This is intended behavior. How could the outer future not become ready if the inner future is available?

Just to clarify: for the code snippet you showed, the outermost future should not become ready before do_more_work() finished executing, however here:
hpx::future<hpx::future<void>> fut = hpx::async( []() {
     do_work();
     return hpx::async( []() {
        do_more_work();
     };
});

the returned outer future will become ready as soon as the inner async has returned. In other words, the automatic unwrapping of future<future<void>> to future<void> should make sure that the collapsed future becomes ready only once the original inner future has become ready.

There must be a bug then, because I don't think that's what is happening. I will try and reproduce it with a smaller code sample.

You might be able to create a succinct test case that uses exceptions. If the outer future is ready too early, then any exceptions thrown by the inner future have no place to go any more.

Hi Erik
Can you give me an example where the outer future is ready too early. I
think that always outer future will be ready after the inner one
completes(because may depend on inner future) and in case of exception in
outer future I think inner future will not execute . If I'm wrong please
correct me!
On 31 May 2017 at 22:28, Erik Schnetter<EMAIL_ADDRESS>wrote:

You might be able to create a succinct test case that uses exceptions. If
the outer future is ready too early, then any exceptions thrown by the
inner future have no place to go any more.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/STEllAR-GROUP/hpx/issues/2667#issuecomment-305250793,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARQQr9ON5ZdKffIZuSK8qxZq835MsVyFks5r_Zw9gaJpZM4Nr1Bp
.

@Praveenv98 The original code Dominic showed above exposes this behavior.

I am having trouble reproducing this behavior with a simple code, and the Octotiger bug I thought I had fixed by explicitly getting the inner futures before return appears to be popping back up again. (Though it takes longer before it happens). At this point I'm no longer 100% convinced the HPX bug I think is there actually exists, it may still be a bug in my own code.

@dmarce1 You were right after all. The current code allows to implicitly convert a future<future<T>> (where T != void) to a future<void> which possibly leads to problems as this operation does not unwrap the nested future but just discards the result value of the outer future.
Doing the same for a future<future<void>> --> future<void> is correctly performing the required unwrap, however.
I will create a patch which inhibits the former conversion at compile time.


Keeps trying to log in despite the number of failed attempts > IBEAM_MAX_FAILED_AUTH

Describe the bug
The app keeps trying to authenticate even if the number of attempts exceeds IBEAM_MAX_FAILED_AUTH
To Reproduce
Steps to reproduce the behavior:

docker run --env IBEAM_ACCOUNT=your_account123 --env IBEAM_PASSWORD=your_password123 -p 5000:5000 --name ibeam ibeam
The result is:
(...)
2021-09-11 19:44:39,711|I| No active sessions, logging in...
2021-09-11 19:44:50,199|E| Error displayed by the login webpage: Invalid username password combination
2021-09-11 19:44:57,264|E| Error displayed by the login webpage: Invalid username password combination
2021-09-11 19:45:04,312|E| Error displayed by the login webpage: Invalid username password combination
2021-09-11 19:45:11,367|E| Error displayed by the login webpage: Invalid username password combination
2021-09-11 19:45:18,429|E| Error displayed by the login webpage: Invalid username password combination
2021-09-11 19:45:25,452|E| Error displayed by the login webpage: Invalid username password combination
2021-09-11 19:45:32,480|E| Error displayed by the login webpage: Invalid username password combination
2021-09-11 19:45:39,462|E| Error displayed by the login webpage: Invalid username password combination
2021-09-11 19:45:46,475|E| Error displayed by the login webpage: Invalid username password combination
2021-09-11 19:45:53,479|E| Error displayed by the login webpage: Invalid username password combination
2021-09-11 19:45:56,625|I| Authentication process failed
2021-09-11 19:45:57,156|I| ############ Starting IBeam version 0.3.0 ############
2021-09-11 19:45:57,193|I| Starting maintenance with interval 60 seconds
2021-09-11 19:46:57,336|I| No active sessions, logging in...
2021-09-11 19:47:06,991|E| Error displayed by the login webpage: Invalid username password combination
2021-09-11 19:47:14,134|E| Error displayed by the login webpage: Invalid username password combination
(...)

Expected behavior
The "Invalid username password combination" error shouldn't be displayed more than 5 times (default for IBEAM_MAX_FAILED_AUTH)
Environment
IBeam version: 0.3.0
Docker image or standalone: docker
Python version (standalone users only):
OS: Ubuntu 20.04.3 LTS
Additional context
N/A
Suggest a Fix
N/A

Thanks for providing more detail on this @popiol 👍
I've looked into the issue and noticed that IBeam currently doesn't capture the Invalid username password combination as failed attempts as I used to think that these don't cause an account lockout. Instead, it checks for a text containing failed to indicate a failure that contributes to locking out the account.
I've just checked your suggestion and indeed the Invalid username password combination also can lead to an account lockout. I'll add it to the pre-emptive shutdown in the next version - thanks for pointing it out 😊

@popiol new release candidate image docker pull voyz/ibeam:0.4.0-rc1 has just been released with the fix taking Invalid username password combination as a condition contributing to MAX_FAILED_AUTH. Give it a shot when you have a chance 👍

Looks good thanks!

Closing this as v0.4.0 just got released which should fix this issue. Feel free to open a new issue if you'd like to continue the discussion 👍 Thank you for participating!


Idea - Remove "All images" and make the element linked

At the bottom there is "ALL IMAGES". It's a good function but it takes up space.
Idea

My idea is to remove "ALL IMAGES" link at the bottom.
Make the element name "Images" linked to all the images.

So, when clicking "Images" we go to all the images. Else we hover to get the images for this page.
Maybe it will conflict with the behavor of mobile devices, if they click to show the dropdowns?

Thought about it, but thinking that making the label a link would really create problems on mobile devices. So not atm.

Ok, I'm fine with it.


Extra long "Issues checking in progress..." whitch finish with "memory leak" exception

Current behavior
It looks like this, but it was fixed: https://github.com/TypeStrong/fork-ts-checker-webpack-plugin/issues/426
Make file: Api.ts
/* eslint-disable */
/* tslint:disable */
import { HttpClient } from "./http-client";

export class Api<SecurityDataType = unknown> {
  constructor(private http: HttpClient<SecurityDataType>) {}

    abc1 = () => this.http.request();
    abc2 = () => this.http.request();
    abc3 = () => this.http.request();
}

and http-client.ts
/* eslint-disable */
/* tslint:disable */

/** Overrided Promise type. Needs for additional typings of `.catch` callback */
type TPromise<ResolveType, RejectType = any> = Omit<Promise<ResolveType>, "then" | "catch"> & {
  then<TResult1 = ResolveType, TResult2 = never>(
    onfulfilled?: ((value: ResolveType) => TResult1 | PromiseLike<TResult1>) | undefined | null,
    onrejected?: ((reason: RejectType) => TResult2 | PromiseLike<TResult2>) | undefined | null,
  ): TPromise<TResult1 | TResult2, RejectType>;
  catch<TResult = never>(
    onrejected?: ((reason: RejectType) => TResult | PromiseLike<TResult>) | undefined | null,
  ): TPromise<ResolveType | TResult, RejectType>;
};

export interface HttpResponse<D extends unknown, E extends unknown = unknown> extends Response {
  data: D;
  error: E;
}

export class HttpClient<SecurityDataType = unknown> {
  public request = <T = any, E = any>(): TPromise<HttpResponse<T, E>> => {
    return '' as any;
  };
}

try to compile, you will see that "Issues checking in progress..." process take extra long time ~15 sec.
I dont know why, but if you Copy-Paste http-client.ts to Api.ts directly this check take <1 sec.
This files make this lib https://github.com/acacode/swagger-typescript-api with ~1000 this.http.request, and each this.http.request() took ~7 sec of checking. When I do this in intel i7 CPU, after ~30 min of compiling I got error about memory leak.
Video: https://user-images.githubusercontent.com/3511307/108701953-4a842480-7511-11eb-9924-7f3c0c60acd0.mp4
Environment

fork-ts-checker-webpack-plugin: 6.1.0
typescript: 3.9.9
eslint: 6.8.0
webpack: 4.46.0
os: Linux mint 18.3 KDE

Could you check If tsc --watch --noEmit is working correctly?

Ssory for delay. Same with tsc --watch --noEmit.
Video: https://user-images.githubusercontent.com/3511307/108986783-2eac8a00-769b-11eb-9f9e-27f914830c8d.mp4
@piotr-oles

Then it's a TypeScript's issue - please report it on the TypeScript repo :)

For a large project, is taking about 15 minutes to Issues checking in progress... to complete

Is it working faster with tsc --watch --noEmit? Have you tried disabling eslint?

I disable eslint and is the save exactly about 15 minutes for Issues checking in progress.. to complete. I try almost everything. Where do I add this flags --watch --noEmit  on webpack.config?

You shouldn't run webpack, but tsc directly to see if there is an issue in the TypeScript itself :) So the command is as I said: tsc --watch --noEmit, or more exactly ./node_modules/.bin/tsc --watch --noEmit

@piotr-oles I run tsc --watch --noEmit and it does take about the same time to Starting compilation in watch mode...

So it's an issue with TypeScript. You can try profile types resolution: https://github.com/TypeStrong/fork-ts-checker-webpack-plugin#profiling-types-resolution. You can also create a ticket in TypeScript, but I would suggest profiling first - maybe there is a one particular type that is causing the slowdown


Flow module

mitmproxy/flow.py currently clocks at 1,200 lines and I'm afraid that I'll get lost in it at some point and won't find a way out... :smirk:
This is an initial low-effort PR to start a discussion on how we could reorganize things. My initial proposal would be to split flow.py into a flow module:

Split flow.py into mitmproxy.flow....

io (FlowWriter, FilteredFlowWriter, FlowReader, read_flows_from_paths)
master (FlowMaster)
modules/extensions/??? (AppRegistry, ReplaceHooks, SetHeaders, StreamLargeBodies, ClientPlaybackState, ServerPlaybackState, StickyCookieState, StickyAuthState)
state (State/FlowState, FlowStore, FlowView)

Move mitmproxy.flow_export into mitmproxy.flow.export
Move mitmproxy.flow_format_compat into mitmproxy.flow.compat (or mitmproxy.flow.io?)
Use mitmproxy/flow/__init__.py to provide a reasonable interface (as with netlib.http)

@mitmproxy/devs, what do you think?

Good idea!
I'm a bit afraid git might loose track of the history if we move things around in such big chunks. But I'm willing to pay the price for better maintainability.

This looks good to me. One comment on this particular patch that goes for the codebase generally is that we way, way over use ```from X import Y`` constructions, which is now beginning to impact code legibility.


DOC: Integrate docs on saving existing array to disk

The text from #101 is nice but I'd like to include it within the "persistent arrays" tutorial section. Also needs to be modified so travis builds don't fail.

New docs here: http://zarr.readthedocs.io/en/2.2-docs/tutorial.html#persistent-arrays


Vue is complaining about a performance issue because BToast component is reactive

Describe the bug
The newest version of Vue (3.5) is triggering a warning in console about a performance issue because BToast component is reactive:

Vue received a Component that was made a reactive object. This can lead to unnecessary performance overhead and should be avoided by marking the component with markRaw or using shallowRef instead of ref.
Component that was made reactive:  {__name: 'BToast'…

From what I can see, this is due to toasts being a ref in toastPlugin.ts. Can toasts be made a shallowRef or the component mark with markRaw?
Reproduction
https://stackblitz.com/edit/github-jqognj?file=src%2FApp.vue
Used Package Manager
npm
Validations

[X] Have tested with the latest version. This is still alpha version and sometime things change rapidly.
[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

The same problem with "useModalController". Similar error ...

https://github.com/bootstrap-vue-next/bootstrap-vue-next/pull/2176


feat: Use AutoScalingGroup instead of EC2 instance

Now autoscaling group is controlling the number of EC2 instances with a simpler unregistering lambda function.

hi ~~ @gotodeploy ,  did you run yarn build to update API.md on your local laptop ?

@guan840912 I appreciate you to point out why the build failed.

hi @gotodeploy, I have some ideas, can we discuss them on twitter or mail<EMAIL_ADDRESS>?

@guan840912 Sent PM on slack(cdk-dev).


Where is the Bridge.aspect source code?

I can't find any helpful abort how to intergate Bridge.aspect in my project. Please help.

Bridge.Aspect is currently not publicly available, but we do plan to include with the 16.0 release.

thank you


Critic and discriminator

Hi!
I am trying to understand the Deep Reinforcement Learning part. I know that the actor outputs is a set of stroke parameters based on the canvas status and target image and the discriminator give (to the actor)  a reward at each step . But what about critic? What is the input and the output for the actor? I am reading the paper but I do not understand this part.
thank you so much

Please refer to paper Figure 4. In model-based version, the input of critic includes rendered image and target image. In model-free version, the input of critic includes current canvas, target image and the action.

And if the reward is given by the discriminator, what is the critic output?. I am looking paper Figure 2, but I don't understand.
Sorry I am a beginner in  Deep Reinforcement Learning .
thank you so much again.

The critic predict the expected accumulated rewards after this step. Note the discriminator just gives reward for this single step. Feel free to ask me questions :)

Thank you very much for your help again.
Also, the actor produces five strokes in each step. The discriminator gives a reward for each strokes generated and after this five strokes in this step, the critic give the accumulated rewards.
am I understanding the algorithm right?
thank you :)

A litte detail: the critic predict the expected reward in the future (until this episode over, contain this single step reward).

Great!
Finally what is Q(s, a) in Figura 2 b?
thanks for your help!

The expected reward after perform the action a in the state s (contain this single step reward). :)

Thanks for all!
In the code, on update_gan why canvas = state[:,:3] and get = state[:,3:6]?
what contains exactly the variable state?

https://github.com/megvii-research/ICCV2019-LearningToPaint/blob/83dc2b6129feeeb56a0cb1fd91d3ffdb9d288616/baseline/env.py#L87
Canvas, Target Image and #Step.

and in play() what about state = torch.cat((state[:, :6].float() / 255, state[:, 6:7].float() ?


(PUP-3779) confine hpux password spec

Ruby 2.1.5 on Windows does not contain Etc::Password.passwd due to not
having HAVE_STRUCT_PASSWD_PW_PASSWD defined when it was compiled -
https://github.com/ruby/ruby/blob/v2_1_5/ext/etc/etc.c#L691-L693.
Ruby 2.0.0 did not have this and passwd was not guarded by an ifdef -
https://github.com/ruby/ruby/blob/v2_0_0_598/ext/etc/etc.c#L682
This goes for both x86 and x64 versions of Ruby. Since Etc is not used
on Windows, it is safe to confine this spec to only run on POSIX
systems.

@ferventcoder let's merge this guy once Travis is good

Still waiting...

CLA signed by all contributors.


Corrected wrong value in the categorical variables notebook

The solution1.py file expects 50 but it's actually 49. This can also be easily checked in the notebook Categorical Variables - Solution, where the calculation with numpy also gives 49.

Thank you for reporting the bug. This has been fixed with this PR.


Java RMI: prevent multiple tickets for same client

In the Sockets exercise, the TicketManager issues only one ticket per client, based on the InetAddress of the client. Implement something similar for Java RMI. However, the client address is identified by a string rather than an InetAddress. See RemoteServer.getClientHost().
Possible ways to implement:

Use generics on TicketImpl and the TicketManager.
Convert InetAddress to String, or vice versa.
Keep both InetAddress and String in TicketImpl.

Converting is not a good idea, since neither of the formats is canonical. Generics would work, but I feel they'd make the code unnecessarily complicated for no good reason. I'll go with the third option. This would also allow to check on both hostname and resolved InetAddress in the future.
Note that none of this is in any way secure. I'm just doing it to possibly trigger some harmless error cases during the classroom exercises.

oops... I'm keeping a reverse lookup map from InetAddress to Ticket. Will need a second map.

Hehe, this change proved useful. Some students were actually trying to use tickets requested on their neighbour's machine.


Select default values not working for objects

Bug, feature request, or proposal:
Proposal, (maybe) Bug
What is the expected behavior?
Select should allow for default selected values that are not strings.
What is the current behavior?
MatSelect does not allow for default selected values if the values being used are any datatype other than strings.
For example, I frequently use *ngFor to create an option list, and then use an object as the value of a MatOption to be able to store/use more than just a string when a user selects a value.
What are the steps to reproduce?
https://stackblitz.com/edit/angular-material2-issue-default-select
What is the use-case or motivation for changing an existing behavior?
I always use objects as values for MatOption inside MatSelect because an object is much more useful than a string value when a user selects an option.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 5.2.x
Angular Material 5.2.x
Is there anything else we should know?
I have a feeling there is a better (more correct) way to be able to link an object to a MatSelect option, but passing it in as a value seems most intuitive to me.

To make the last select show the default value changing the code to this:
optionsObjects = [
  {value: 1, display: 'Option 1'},
  {value: 2, display: 'Option 2'},
  {value: 3, display: 'Option 3'},
];
selectedObject = this.optionsObjects[0];

The third box has the same problem, the object reference is not the same.

The following is from material.angular.io/components/select/api

@Input()
compareWith: (o1: any, o2: any) => boolean

A function to compare the option values with the selected values. The first argument is a value from an option. The second is a value from the selection. A boolean should be returned.

Using that it should be possible to solve the problem.

@mucbits is correct, mat-select compares the objects by reference by default. You can use compareWith to have some custom comparison logic.


How to watch the typeDefs file?

This plugin doesn't register changes to the typeDefs.graphql file. I noticied that inside the documentation the suggestion is to delete the cache before starting:

Each time you modify a GraphQL file, the node_modules/.cache/babel-loader folder must be cleared for the changes to take effect. I recommend prepending the relevant script in your package.json and rerunning the script when you change a GraphQL file:

{
 "scripts": {
   "start": "rm -rf ./node_modules/.cache/babel-loader && node index.js"
 }
}

The problem with this is what happens when you want to watch for changes and restart your server?
  "start": "nodemon --exec babel-node ./src -e js,graphql"

If I start my app using nodemon with babel-node to work fast and efficiently, changes to typeDefs will trigger a restart, but they don't show up in the schema because of the cache issue.

Possibly "start": "nodemon --exec rm -rf ./node_modules/.cache/babel-loader && babel-node ./src -e js,graphql"?

I don’t really like the idea of putting an ‘rm -rf... ‘ into an automated package.json script like that.

Sorry, I'm afraid that's the best I can do. As I mentioned in issue 39 there's nothing I can do about this from inside a babel plugin. There's a link in that issue to an external discussion with more info.

rm -rf ./node_modules/.cache/babel-loader
didn't work for me but this did:
"dev": "nodemon -e js,graphql --exec 'rm -rf ./node_modules/.cache && babel-node src/index.js'"


Various improvements for newer django and pymemcache.

Please don't merge until Django 3.2 is released. I'll open this as a draft for now.
There have been various improvements to pymemcache and we will also have a built-in backend in Django 3.2+.
I've also added some commits to test with newer versions of Python and Django, as well as modernising some of the packaging.

@Surgo This is following on from django/django#13310 ready for when Django 3.2 is released.


Is this project abandoned?

Hello!
Over nine months ago I was searching for a Resident Evil 2 Remake randomizer, that would work better than the current "popular" Benn Powell one. I stumbled upon this, and saw that this project actually had a lot of commits, however, when I tried to download the latest release and execute the executable, nothing happened - the executable didn't work at all. I tried launching it in a terminal, but still, not even a single line of output. I thought to myself "this project is probably still WIP, I will take a look at it a few months later", and left it aside for now.
Over the last half a year I have been checking up on this project every now and then, and for some time it was growing, but when I opened it in late July, I saw that the project hadn't received a commit in a bit. I thought to myself "this is just open source things - the developer is taking a break" or something, and at the start of august the project did receive some commits, but only to never receive any again.
The latest build still doesn't do anything - I open it up and it immediately closes. The project hasn't gotten any commits for the last 4 months. I want to ask this - is this project abandoned? Will it never be finished? Of course, although sad, it is understandable. This is open source at the end of the day, and you get absolutely no monetary gain from developing this.

Abandoned, no but definitely on pause at the moment. I operate a lot of side projects in addition to multiple jobs IRL so I haven't been able to devote as much time to this project as I would have liked post-SGDQ 2024.
The current state of this project is... it works-ish but only part of the RPD is randomized with soft-lock prevention, the rest is randomized but might be in such a way that you'd be soft-locked. There is also a nagging issue where sometimes it'll crash the game on item pickup. Seems to happen 1% of the time but when it does, its a CTD with an access violation attempting to read a null pointer.
It also targets DirectX 11 and the non-RTX build of the game at the moment. So RTX build or DirectX 12 rendering mode means it won't attach or render the UI.


Messaging for disabled blockchain sync

We need to add a banner to the diagnostics page to explain the changes to blockchain sync

                 <button type="button" class="btn-close" data-bs-dismiss="alert" aria-label="Close"></button>
What happened to sync percentage?

Helium has converted all existing hotspots into light hotspots. Sync percentage and other blockchain features are now handled by validators, not hotspots. We appreciate your patience with any issues during the transition period.
                 More Information

    <button type="button" class="btn-close" data-bs-dismiss="alert" aria-label="Close"></button>

What happened to sync percentage?

Helium has converted all existing hotspots into light hotspots. Sync percentage and other blockchain features are now handled by
        validators, not hotspots. We appreciate your patience with any issues during the transition period.

    More Information


Workbench UI Take action button is disabled when enum declared in function signature

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Create a function with the following signature:

enum AnswerType { No, Yes}

function vote(uint questionIndex, AnswerType answer) public {

Configure the function and declare its parameters:
 "Parameters": [
                        {
                            "Name": "questionIndex",
                            "Description": "Question number",
                            "DisplayName": "Question number",
                            "Type": {
                                "Name": "int"
                            }
                        },
                        {
                            "Name": "answer",
                            "Description": "Selected question option",
                            "DisplayName": "Answer to the question",
                            "Type": {
                                "Name": "enum",
                                "EnumValues": ["No", "Yes"]
                            }
                        }

Create the application on the Workbench UI app and you won't be able to trigger the Take Action button. All data is correct but the button will remain disabled

Any log messages given by the failure

Expected/desired behavior

When all data types validations are passed on the UI you must be able to trigger the action.

Note: I guess this is a UI related bug as triggering the function throught the REST api works like a charm.
OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Thanks for reporting! This is fixed for the next Workbench release.