search for: reactiv

...ltiprocess) heavyFunction <- function(n){ Sys.sleep(n) print(n) } ui <- fluidPage( actionButton("go","Show the data"), textOutput("result0sec"), textOutput("result10sec") ) server <- function(input,output,session){ data0 <- eventReactive(input$go,{ heavyFunction(0) }) data10 <- eventReactive(input$go,{ future(heavyFunction(10)) }) output$result0sec <- renderText({ data <- data0() print(data) }) output$result10sec <- renderText({ data <- data10() data%...>%print() })...

I''m pleased to announce a new project: Reactive What is that? It''s a desktop application framework that is highly inspired by Rails. Thus it is MVC oriented and has built-in features like scaffolds. It currenty uses wx as it''s view system. The current release is pre-alpha, but you may already play with it. Refer to http://w...

Andrey, I believe that on Xen we should disable kasan, would like confirmation from someone on xen-devel though. Here's the thing though -- if true -- I'd like to do it *properly*, where *properly* means addressing a bit of architecture. A simple Kconfig slap seems rather reactive. I'd like to address a way to properly ensure we don't run into this and other similar issues in the future. The CR4 shadow issue was another recent example issue, also introduced via v4.0 [0]. We can't keep doing this reactively. Let's go down the rabbit hole for a bit. HAVE_ARCH...

Andrey, I believe that on Xen we should disable kasan, would like confirmation from someone on xen-devel though. Here's the thing though -- if true -- I'd like to do it *properly*, where *properly* means addressing a bit of architecture. A simple Kconfig slap seems rather reactive. I'd like to address a way to properly ensure we don't run into this and other similar issues in the future. The CR4 shadow issue was another recent example issue, also introduced via v4.0 [0]. We can't keep doing this reactively. Let's go down the rabbit hole for a bit. HAVE_ARCH...

...kgroups. If I went to the network neighborhood and tried to open the workgroup of my samba server I got an error message saying that the workgroup "mygroup" was not available. So I minimized the settings in the global section of my smb.conf and I was able to open "mygroup". I reactivated the most important options like "interfaces" and "hosts allow", which didn't seem to be the problem. But when I reactivated "valid users" containing 4 users, I was not able to browse "mygroup" any more. So, is it possible, that the ability to open...

...done something wrong, so I have no idea what happened here. On Fri, 2023-02-24 at 17:58 -0800, Michael de Gans wrote: > My freedesktop gitlab account?was deactivated and I can't fathom why. I > can't log in and can't reset my credentials. If possible, I'd like to have > it reactivated since I make an occasional contribution to GStreamer. > Apologies if this isn't the place to ask, but there doesn't seem to be an > admin contact anywhere. > > ---------- Forwarded message --------- > From: GitLab <gitlab at gitlab.freedesktop.org> > Date: Fri,...

...switch a few computers from one Internet provider to a different one. Both Internet providers feed into the same network, one at 192.168.0.1 and the other at 192.168.0.254. So to change from one provider to the other I run nmtui to change the gateway and dns server addresses, then deactivate and reactivate the connection and I'm done. It's just takes a few minutes, but I'm wondering if there's a way to automate this a bit so instead of having to run nmtui and change all of those numbers, then deactivate and reactivate the connection, I could just have each configuration saved as a...

Hi everyone. This is a real noob question that I''m hoping someone out there can help me with. I have followed the tutorial How to Ad created_by and updated_b<http://wiki.rubyonrails.com/rails/show/Howto%20Add%20created_by%20and%20updated_by>y and it works ok for retrieving the data. I''m using the Login_Generator. I cannot get it to work on create or update. I think

...Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: dan at reactivated.net QA Contact: xorg-team at lists.x.org Created attachment 131742 --> https://bugs.freedesktop.org/attachment.cgi?id=131742&action=edit full dmesg log On the Acer Z20-730 laptop, the nouveau driver crashes during boot with: [ 4.041108] nouveau 0000:01:00.0: pci: failed t...

...e next week. > > While a solution is likely possible here I'd like for us to notice how > two features have gone now under our nose for Xen on v4.0 which have > issues. Proactive maintainer reviews would detect these issues but we > can't bet on these, and testing is just as reactive and slow. I'm Hmm, I see you saying 'Proactive maintainer review would detect' these but that assumes that the maintainer would even be copied on these patches? None of the Xen maintainers were copied on this. And while we all strive to be pro-active I have to remind you maintainers...

...e next week. > > While a solution is likely possible here I'd like for us to notice how > two features have gone now under our nose for Xen on v4.0 which have > issues. Proactive maintainer reviews would detect these issues but we > can't bet on these, and testing is just as reactive and slow. I'm Hmm, I see you saying 'Proactive maintainer review would detect' these but that assumes that the maintainer would even be copied on these patches? None of the Xen maintainers were copied on this. And while we all strive to be pro-active I have to remind you maintainers...

I've missed that one, already a month ago! investigation needed... -- Arnaud ---------- Forwarded message ---------- From: Daniel Drake <dsd at gentoo.org> Date: 2008/5/26 Subject: [fprint] libusb-1.0 enters beta To: fprint at reactivated.net Hi, libusb-1.0 has entered beta. http://www.reactivated.net/weblog/archives/2008/05/libusb-10-enters-beta/ libusb-1.0 is the lowest level component required by the asynchronous development work that I've been doing over the last few months. Stabilising and releasing libusb-1.0 is t...

...gt; > While a solution is likely possible here I'd like for us to notice how > > two features have gone now under our nose for Xen on v4.0 which have > > issues. Proactive maintainer reviews would detect these issues but we > > can't bet on these, and testing is just as reactive and slow. I'm > > Hmm, I see you saying 'Proactive maintainer review would detect' these > but that assumes that the maintainer would even be copied on these patches? > > None of the Xen maintainers were copied on this. That is a damn shame. More on this below. >...

I'm planning to upgrade my asterisk 1.4.4 to 1.4.6. usually for asterisk upgrade i delete modules directory and include, then compile the new version. Since i have couple of G729 Licenses on this server installed, would i need to call Digium to reactivate these Licenses? Is there any better and faster way of upgrade asterisk? Possibly without losing G729 License? Thanks! _________________________________________________________________ Play free games, earn tickets, get cool prizes! Join Live Search Club.? http://club.live.com/home.aspx?icid=CLUB...

Guys, I need some input on best practices from the group regarding choosing between a reactive and proactive approach when determining setup for a host. Let me explain. I have an "apt" module that takes care of setting up common apt settings and provide the basic "sources.list" for the managed hosts - debian on servers and ubuntu on desktops. I have chosen to keep the...

...on$clientData$url_protocol session$clientData$url_hostname session$clientData$url_pathname session$clientData$url_port session$clientData$url_search But then when I try to use this code in my server function the bellow Error appears: > urlSearch <- session$clientData$url_search Error in .getReactiveEnvironment()$currentContext() : Operation not allowed without an active reactive context. (You tried to do something that can only be done from inside a reactive expression or observer.) Could anyone help with this? Considering that the reactive I will not use this value to renderText or to put...

...disable kasan, would like confirmation Why? This is the first of heard of this. > from someone on xen-devel though. Here's the thing though -- if true > -- I'd like to do it *properly*, where *properly* means addressing a > bit of architecture. A simple Kconfig slap seems rather reactive. I'd > like to address a way to properly ensure we don't run into this and > other similar issues in the future. The CR4 shadow issue was another > recent example issue, also introduced via v4.0 [0]. We can't keep > doing this reactively. > > Let's go down the ra...

...disable kasan, would like confirmation Why? This is the first of heard of this. > from someone on xen-devel though. Here's the thing though -- if true > -- I'd like to do it *properly*, where *properly* means addressing a > bit of architecture. A simple Kconfig slap seems rather reactive. I'd > like to address a way to properly ensure we don't run into this and > other similar issues in the future. The CR4 shadow issue was another > recent example issue, also introduced via v4.0 [0]. We can't keep > doing this reactively. > > Let's go down the ra...

...allmodconfig and allyesconfig builds, but I don't see other option for now. > from someone on xen-devel though. Here's the thing though -- if true > -- I'd like to do it *properly*, where *properly* means addressing a > bit of architecture. A simple Kconfig slap seems rather reactive. I'd > like to address a way to properly ensure we don't run into this and > other similar issues in the future. The CR4 shadow issue was another > recent example issue, also introduced via v4.0 [0]. We can't keep > doing this reactively. > > Let's go down the ra...

...allmodconfig and allyesconfig builds, but I don't see other option for now. > from someone on xen-devel though. Here's the thing though -- if true > -- I'd like to do it *properly*, where *properly* means addressing a > bit of architecture. A simple Kconfig slap seems rather reactive. I'd > like to address a way to properly ensure we don't run into this and > other similar issues in the future. The CR4 shadow issue was another > recent example issue, also introduced via v4.0 [0]. We can't keep > doing this reactively. > > Let's go down the ra...