text:
Cmake problem

I have a rviz_plugin project, that's used catkin_make build it and can add it in rviz.
But now I have a new need which put the rviz_plugin project in a cmake project. And I used cmake build all project successfully, but when I use the plugin in rviz, it give a bug back.
Bug info like that:
The class required for this panel, 'graph_rviz_plugin/Line graph', could not be loaded. Error: Could not find library corresponding to plugin graph_rviz_plugin/Line graph. Make sure the plugin description XML file has the correct name of the library and that the library actually exists.
How can I resolve it? Please give some advices for me, thanks!
Environment

OS Version: Ubuntu 20.04
ROS Distro: [Noetic]

This question should be better asked at https://answers.ros.org. Please, post real issues and bug reports here only.
Did you check that rospack finds your plugin: https://answers.ros.org/question/298919/rospack-can-not-find-my-plugin/

Sorry and thank you.

authors: AaronWaxson rhaschke

repo: ros-visualization/rviz


text:
fix libqglviewer-qt4 and libqglviewer-qt4-dev debian jessie rules

Follow up of https://github.com/ros/rosdistro/pull/14424/
libqglviewer-qt4-dev: https://packages.debian.org/stretch/libqglviewer-dev-qt4
libqglviewer-qt4: https://packages.debian.org/stretch/libqglviewer2-qt4

@ahornung FYI

@ahornung Now that the rosdep rule is fixed you will need to rerun bloom to take the new rule into account and get octovis passing for all platforms (except armhf where I blacklisted octovis because the libqglviewer package doesn't exist for this platform)
Thanks!

Thanks for taking care, @mikaelarguedas. Will rerun right now.

source: gharchive/pull-request

authors: ahornung mikaelarguedas

repo: ros/rosdistro

license_type: permissive

license_source: github-api


text:
random_numbers: 0.3.1-0 in 'melodic/distribution.yaml'

upstream repository: https://github.com/ros-planning/random_numbers
release repository: https://github.com/ros-gbp/random_numbers-release.git
distro file: melodic/distribution.yaml
bloom version: 0.6.2
previous version for package: null

random_numbers

no changes

I think you'll need to cut a new release so that your email for the buildfarm email rather than the previous maintainer.
Looking at the release repo it looks like the release you made for melodic is 0.3.1-0 and not 0.3.1-1. You can use bloom to generate the PRs automatically and it will pick up the exact version number (X.Y.Z-Inc)

both good points. Closing this one.

authors: mikaelarguedas nuclearsandwich


text:
Remove mocap packages (REP 144 Fix)

Packages removed to meet with REP 144 (https://github.com/ros/rosdistro/pull/39475#issuecomment-1894443133), replaced by https://github.com/ros/rosdistro/pull/39615 and https://github.com/ros/rosdistro/pull/39616

Hii @fmrico, there is no value in updating Foxy as it is EOL, can you please update the PR to have changes to Humble only?

Hi @quarkytale, I have just restored Foxy file

authors: fmrico quarkytale


text:
test codecov

test folders should be ignored in the analysis.

Codecov Report

Merging #155 (ccd197f) into master (8e8a2d9) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #155     +/-   ##
=========================================
  Coverage   31.31%   31.31%
=========================================
  Files          64       32     -32
  Lines        7888     3944   -3944
  Branches     3950     1975   -1975
=========================================
- Hits         2470     1235   -1235
+ Misses       2064     1032   -1032
+ Partials     3354     1677   -1677

Impacted Files
Coverage Δ

...c_parameter/test/rclc_parameter/test_parameter.cpp

ros_ws/src/alu0oqea19/rclc/rclc/src/rclc/client.c

...c/1k7ce2609y/rclc/rclc/test/rclc/test_executor.cpp

.../rclc/rclc_examples/src/example_parameter_server.c

...609y/rclc/rclc_examples/src/example_service_node.c

...rc/alu0oqea19/rclc/rclc/test/rclc/test_service.cpp

...rc/1k7ce2609y/rclc/rclc/src/rclc/executor_handle.c

.../src/1k7ce2609y/rclc/rclc/test/rclc/test_timer.cpp

ros_ws/src/alu0oqea19/rclc/rclc/src/rclc/service.c

...s/src/alu0oqea19/rclc/rclc/src/rclc/subscription.c

... and 86 more

Continue to review full report at Codecov.

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

@mergify backport galactic foxy

@norro the rclc_lifecycle does not have a subfolder test/rclc_lifecycle as in rclc and rclc_parameter. You might want to fix this when you have time. This required a different rule to ignore the test files for this package: rclc_lifecycle/test/*instead of test/**/*:
ignore:
  - "rclc/test/**/*"
  - "rclc_examples/**/*"
  - "rclc_lifecycle/test/*"
  - "rclc_parameter/test/**/*"

Let me know, when you have fixed it, then I'll update the codecov file. But we can also live with the current package folder structure.

@pablogs9 @ralph-lange @norro With this fix, the code coverage of rclc repository increased to 59% (from 31% where test and rclc_examples folders were included).

authors: JanStaschulat codecov-commenter

license_source: bigquery


text:
Updated description of clang compile command

The description was incorrect but the command was.

I think I changed it, tell me if I need to do something else


text:
Keep GitHub Actions up to date with GitHub's Dependabot

Fixes warning at the bottom right of
https://github.com/rossjrw/pr-preview-action/actions/runs/8246680558

https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot
https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem

@rossjrw Your review, please.

repo: rossjrw/pr-preview-action

license: MIT


text:
Issue updating ticket - " 'module' object has no attribute 'get_template_from_string' "

I'm very new to django-helpdesk; I've looked at locales and included the template context processors in settings.py, but I keep getting the problem below when updating a ticket. I notice a similar stack trace when I run ./manage.py get_email. Can you please point me in the right direction?

Appears to be related to Django 1.8 removing get_template_from_string (#315) and needs to be properly addressed.

I'll try a fix myself if I have time  - for now I'l downgrade to an earlier django version. Please let me know if there is a way I can help.

Yes, this is related to a function deprecated in Django 1.8. I have a branch that fixes several issues with django 1.8. Should you run into any problems, let me know.

hi, i fixed this issue, i making the next, in views folder, in staff.py file added the next line in imports
from django.template import Engine
and changed, this line
comment = loader.get_template_from_string(comment).render(Context(context))
for this line
comment = Engine().from_string(comment).render(Context(request,context))
this worked for me, because if you is intalling django-helpdesk in a version newer(python >2.7 or django >1.8), get_template_from_string is incompatible.
pdt:  sorry for the english.
regards.

Thanks for adding your fix @leidyj
@rossp There's now at least three versions of a fix for this (this latest one, @flinz's and my own); do you have any thoughts on how you'd like to handle providing for compatibility with multiple Django versions?
I have found arteria/django-compat really helps with this kind of thing and has been worth adding the extra dependency for me.
Otherwise, as I understand the current Django release policy, since anything deprecated in version X is still supported through version X+1, IMO, it's simplest to support a range of 3 major releases (X - 1, X, X + 1). IIRC, currently django-helpdesk's minimum version is 1.5 and it works out-of-the-box through 1.7 -- so it fits this 3 major versions pattern. It is probably possible to provide 1.8 support without using any compatibility shims just by dropping 1.5 support (I say 'probably' because I'm not sure whether this release policy was already in place at the time of 1.5, but even if not, 3 versions seems like a good policy going forwards).
Anyway, if you let me know what your preferences are for handling this I'll try to package the version-compatibility fixes up into a PR that meets the corresponding criteria.

Thank you so much guys and sorry I haven't been able to follow this up.
I believe we should follow Django's policy of Current and Previous release. Given the decently long lead times for new major releases, we should be able to support eg Django 1.9 on release day, possibly stopping official support for 1.7 at that time. I do not believe our little project should support LTS releases given the project isn't even at 1.0 yet.
Any chance you can submit a pull request with your branch of 1.8 changes that covers more than just this template issue?

Great! I will submit a PR for 1.8 compatibility, dropping support for <=1.6, by this weekend.

On 20 ส.ค. 2558, at 06:48, Ross Poulton notifications@github.com wrote:
Thank you so much guys and sorry I haven't been able to follow this up.
I believe we should follow Django's policy of Current and Previous release. Given the decently long lead times for new major releases, we should be able to support eg Django 1.9 on release day, possibly stopping official support for 1.7 at that time. I do not believe our little project should support LTS releases given the project isn't even at 1.0 yet.
Any chance you can submit a pull request with your branch of 1.8 changes that covers more than just this template issue?
—
Reply to this email directly or view it on GitHub.

@reduxionist next to templating issues, be sure to watch out for compatibility with the helpdesk tests. Django 1.8 removed some deprecated classes, so I had to adapt the quicktest.py (to fix those missing classes and ensure backwards compatibility) [https://github.com/flinz/django-helpdesk/commit/55dd80fa0621d9535bbd7672c57e9c5394a1159b & https://github.com/flinz/django-helpdesk/commit/05625d0bfd92cb3113d0e00808ef1cba596e9e71] and rename the test classes themselves to a common test_X.py scheme to make them auto-discoverable.
I am unsure whether my renaming approach is the most straight forward, maybe you can have a second look.

Thanks for the tips @flinz! I will be sure to refer to (and probably cherry-pick and/or rebase from) the referenced commits. I had to work this past weekend so I probably won't get back to it until this weekend, however.

@reduxionist are you still on this (submitting a PR with 1.8, dropping <=1.6)?
Otherwise: what (besides changes in my branch) is there to do? Do you have a branch I can work off?

Alex, I haven't gotten around to this yet unfortunately, your own branch remains best starting point!

On 13 ต.ค. 2558, at 16:38, Alex Seeholzer notifications@github.com wrote:
@reduxionist are you still on this (submitting a PR with 1.8, dropping <=1.6)?
Otherwise: what (besides changes in my branch) is there to do? Do you have a branch I can work off?
—
Reply to this email directly or view it on GitHub.

@rossp this can be closed.

source: gharchive/issue

authors: dominicfollett flinz leidyj reduxionist rossp

repo: rossp/django-helpdesk


text:
Behaviors are not accessible through code

Let's say I'm using Anko or other DSL library to write my views through code. How can I set the behavior of the BottomBar? There should be a method to set the behaviour through code and it should be a priority.

yeah currently there doesn't seem to be a way of doing this because it needs to know in advance those behaviors to know how to render things in the first place. This restriction might or not change in the next big release of the library when we are trying to add custom tabs/badges and things like that.

authors: mradzinski yombunker

repo: roughike/BottomBar


text:
Turn off bar hiding when scrolling

How can I prevent my bottom bar from hiding while scrolling?

@slikasgiedrius With the versions 2.3.0 and up, in shy mode, you can show / hide the bar as follows:
// Show:
bottomBar.getShySettings().showBar();
// Hide:
bottomBar.getShySettings().hideBar();
On non-shy mode, it's up to you how to hide / show it, since the BottomBar is just a regular View.

The bottom bar is hiding while scrolling. Non of these fields are working

its not supposed to...check on your code

Do you really understand my question?
What I need is some code which would change the current behaviour of bottom bar. I need to make my bottom bar always visible, when user scrolling as well..

I understand your question very well and unless you set the shy mode the bottom bar by default never hides on scrolling.

I am just initialising this bottom bar and setting them as active. I am not doing anything with shy modes etc etc.

Kindly send the layout code for the activity where you are placing the bottom bar it will be much better to see where the problem is that way

It looks like the other developer added shy parameter inside xml.. I am really sorry, the problem is off. Huge thanks !

authors: slikasgiedrius wangerekaharun


text:
🛑 Fossil based IRC Log is down

In 1d5712e, Fossil based IRC Log (https://rouilj.dynamic-dns.net/fossil/roundup_irc_logs/doc/trunk/log/roundup/) was down:

HTTP code: 503
Response time: 2089 ms

Resolved: Fossil based IRC Log is back up in 481f72a.

repo: rouilj/RoundupAssets


text:
Error: [route-node][buildPath] '{routeName}' is not defined

Getting Error: [route-node][buildPath] '{routeName}' is not defined on upgrade to 8.0.0, even though my router looks like this:
<RouterProvider router={createRouter([
  { name: 'href', path: '/href' },
  { name: 'typehref', path: '/type/href' },
  { name: 'foo/href', path: '/foo/href' },
  { name: 'bar/href', path: '/bar/href' },
])}>
  ...stuff...
</RouterProvider>

What do I need to do to fix?
     Error: [route-node][buildPath] '{routeName}' is not defined
        at RouteNode.buildPath (/Users/me/dev/foo/node_modules/route-node/src/RouteNode.ts:203:13)
        at Object.router.buildPath (/Users/me/dev/foo/node_modules/router5/dist/index.js:138:36)
        at BaseLink.Object.<anonymous>.BaseLink.buildUrl (/Users/me/dev/foo/node_modules/react-router5/dist/index.js:123:28)
        at BaseLink.Object.<anonymous>.BaseLink.render (/Users/me/dev/foo/node_modules/react-router5/dist/index.js:156:25)

I had this same problem and it took me a while to get to the bottom of it because I thought the problem was with my route definition as well, but was happened for me was one of my routes was rendering a component that contained a  component, and the  had an invalid routeName parameter set (I had a route called "analysis.videos" but the  routeName was going to "analysis.video"). Previous versions didn't seem to throw an exception but v8 does.

I have consistently 5-10% of users have met this problem. I do not know how to fix it, because all the routes are correct.

authors: ivansergeev lance-swoop lid2000

license: mit


text:
Consider idlgen::author_class to replace idlgen::base

template <typename T = void, typename... I>
struct author_class
{
}

struct Foo : FooT<Foo>, idlgen::author_class // Can omit the template type if no base
{
}

Benefit:

Consistency with other authored type support (although this would make Foo an implementation type and also authored type)
Simplify the implementation to check for impl runtime class (no need to rely on checking Foo inherits FooT, with first param being Foo)

This godbolt shows simply using variadic template is enough. No need to separate T and I.

We are also not validating the first argument has to be a class or whatever, so no need to separate for this reason as well.
But, since idlgen::base is now used for interface requires. This issue requires updating author_interface as well.
TODO

[ ] author_class<>
[ ] author_interface<>
[ ] remove idlgen::base

Decided to make author_class a non-template. Base specification remains unchanged (i.e. devs should use idlgen::base).

...From sample app's usage it looks quite verbose. Considering one of the core usage of idlgen is XAML authoring, not unifying author_class and base means all xaml pages/components have to write these two tag types.
Will implement idlgen::author_class<WUXC::Page>.

repo: roxk/idlgen


text:
🛑 ShredX is down

In 1f9701a, ShredX (https://shredx.in/) was down:

HTTP code: 504
Response time: 5509 ms

Resolved: ShredX is back up in f8b4b0e.

repo: rpharaniya/websites-uptime-monitor


text:
🛑 Maxx Techno Cast is down

In 20a1549, Maxx Techno Cast (http://maxxtechnocast.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Maxx Techno Cast is back up in 7b58212.


text:
🛑 dumb.lunar.icu is down

In 5db7a78, dumb.lunar.icu (https://dumb.lunar.icu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: dumb.lunar.icu is back up in 627da96 after 18 minutes.

repo: rramiachraf/dumb-instances


text:
Workaround for Genius

Proxy server to bypass Cloudflare protection
https://github.com/FlareSolverr/FlareSolverr

This repo is golang anwyay, so it's not bound to OpenSSL, which makes masking your TLS fingerprint (JA3) not hard (and a lot less bloated than spawning a headless browser)
https://github.com/Danny-Dasilva/CycleTLS

@brian6932 @xbdmHQ, I've implemented the JA3 spoofing into the request client.
Could you give the latest commit a try, and see if the Cloudflare issue is still occurring.

I don't host an instance, nor have I experienced a cf issue with this repo. I'm sure it happens, but I don't even know what errors are encountered, sorry if I led you on, was just providing an option.

authors: brian6932 rramiachraf xbdmHQ

repo: rramiachraf/dumb


text:
delete branch

@David-Pena can I delete the branch you created and I already merged?

My bad, I thought I already deleted it.
i just deleted it now


text:
Animate UIImage

Is there any way to make a smooth cross-fade before setting image? I use SDWebImage category on UIImageView. I checked the source code and I don't seem to find a way to set image with transition, it simply sets image itself without anyway to wrap this operation into UIView animation or something..

check this https://github.com/rs/SDWebImage/pull/702
animating the appearing image is outside the scope/purpose of this library. Thanks

authors: mythodeia pronebird

repo: rs/SDWebImage


text:
"Could not connect" without any logs

Feedback:

"Could not connect" without any logs. How can I check what the problem is. I am able to connect with my and and mongo CLI.

You can simply check logs by using web app version. But if you get Could not connect without any logs, this means somethings internal is broken. It would be better if you can send me back the webapp's logs, otherwise I can't see what's going on.

repo: rsercano/mongoclient


text:
Fix for react by not setting globals

Fixes two issues when using this library with webpack and react:

midiMap is being used as a global. Fix by just making it a var

The library is messing with the global window object, which is breaking react for some reason. The fix was to not set values on window, but I also just simplified and reformatted up that part of the code

Thanks for your interest in Wad.js! However, something doesn't seem quite right in this code that you changed. When I load up your fork in the GUI application (in the GUI folder), I'm unable to get microphone access. There's an error in the console: wad.js:2530 Error setting up microphone input:  TypeError: Illegal invocation
It's possible that I'm having problems because the function navigatorGetUserMedia is no longer a property of the navigator object. In past versions of Wad.js, I used Function.prototype.bind to avoid assigning to the window or navigator, while still retaining the link between navigator and getUserMedia.

Thanks for taking a look. There were two problems with the this binding that should be fixed now,  although I wasn't able to get the GUI example app to do much more than produce some horrible shrieking sound, even on the master branch.
Let me know if there are any instructions for testing.

That horrible shrieking sound was probably just microphone feedback (sound goes in your mic, out your speakers, and right back into your mic, which causes the audio signal to amplify rapidly). If you use headphones, or an external microphone, you probably won't get such bad feedback.
There aren't really any instructions for testing, but there should be. I usually just load up the GUI app and make some quick loops, making sure that microphone and MIDI access work.
Thanks for contributing!

authors: mattbierner rserota

repo: rserota/wad


text:
login failure

login failed and returned status code 200. login json: {"status": 400, "items": [], "status_description": "bad-request", "status_detail": "No user is identified with this information."}
These same credentials work with this other library: https://github.com/alexlincoln/dropcam.

Hmm, not sure why it works with the other API, but I was able to log in as usual, but I had to use my email address instead of the username. Did you convert your account from dropcam to nest yet?

I cannot log in either, and get a 403 error (unauthorized).

Hey guys, sorry for the late response... is this still an issue? I haven't updated my (really) old dropcam's firmware since they were acquired by nest, but I can still login using my account, I just can't get any camera data.
>>> from dropcam import Dropcam
>>> Dropcam("XXXX", "XXXX")
<dropcam.Dropcam object at 0xae2c90>

@ylmeng I just re-read your comment: make sure you're using the same email address you use to log in to your nest.com account:
>>> Dropcam("my-email-address@foobar.com", <password>)

authors: rsgalloway ylmeng zachheine

repo: rsgalloway/dropcam


text:
No changes after upgrade to 0.5.0

Not seeing the 'Selected Text' option for Anki fields nor the 'Ignored Subtitle Languages' setting despite the app telling me I'm running version 0.5.0. I used the Windows installer and performed an upgrade. Also tried to uninstall and reinstall but no luck.

Oops, I will fix shortly.

I made a mistake in the build/release of just the Windows versions, so I have updated them without changing the version number. Please try again!

Perfect thanks!

authors: chriskempson rsimmons

repo: rsimmons/voracious


text:
Add shared example group that we can use in each repo to enforce minimization of stdlib usage

(Continuing from rspec/rspec-expectations#730...)
Given our goal of minimizing how much of the stdlib we use (so as to not to give users a green suite when they forget to load the bits they use), it would be useful to enforce it via some specs that enforce an "allowed stdlibs" whitelist.  Using something new from stdlib would require an intentional decision to add to that list and hopefully over time we can shrink it.  It could also be used to help us accurately document what stdlib pieces we do use.
My idea for how to do this is similar to the warning prevention.  We can use $" (aliased as $LOADED_FEATURES when english is loaded) to get a list of what all has been loaded:
➜  ~  ruby -e 'puts $"' --disable=gem
enumerator.so
/Users/myron/.rubies/ruby-2.1.5/lib/ruby/2.1.0/x86_64-darwin12.0/enc/encdb.bundle
/Users/myron/.rubies/ruby-2.1.5/lib/ruby/2.1.0/x86_64-darwin12.0/enc/trans/transdb.bundle

So, we can run that and capture what is loaded by default, and then run that again with all the lib files from a particular rspec project loaded.  We can subtract them to get everything loaded by that project.  We can further subtract off all the RSpec internal files. That should leave all the external stuff (stdlibs and external gems like diff-lcs) that are currently being loaded, and we can easily compare that to a whitelist and fail if they get out of sync.

/cc @JonRowe

repo: rspec/rspec-support


text:
Possible to run current noetic-devel code on ros kinetic installed on my machine?

I am sorry if my questions are silly.
I want to know if I can take the 0.9.1 version on noetic-devel branch and run on ros kinetic in my local machine? The code I am using right now was downloaded using sudo apt-get ros-kinetic-teb-local-planner, so I guess it is still way back in terms of updates. I would like to use the code with the most recent code, which I believe to be on the noetic-devel branch.
Any help/suggestions/advice is more than welcome

if you compile the code yourself it might work.
but some functionality might not be available if the linked noetic libraries are not compatible to their kinetic-versions

if you compile the code yourself it might work.
but some functionality might not be available if the linked noetic libraries are not compatible to their kinetic-versions

authors: omair-khalid torgeros


text:
Empty for loops

i tried to convert http://code.jquery.com/jquery-git.js in the website
http://js2coffee.org/
then after, i tried the converted code back again and there are errors:
error in the http://js2coffee.org/
Error: Parse error on line 582: Unexpected 'TERMINATOR'
http://coffeescript.org/
UNMATCHED OUTDENT ON LINE 3269
by the way, the converted one is almost 50% less than the original code.. nice job in the web based converter

i tried converting the minified version of the library, theres an error too..

Renamed the issue to be more descriptive of the actual bug.

this isnt fixed yet..
I tried converting http://code.jquery.com/jquery-git.js to coffee script..
then I tried the coffee to js in the new tab in the website:
Error: Parse error on line 582: Unexpected 'TERMINATOR'
I assume js to coffee and coffee to js is consistent.
tried too the minified version

@keichii: who said it was fixed?

@rstacruz changed my topic but I think the issue here is much broader than you think imho
to close this issue, the js and the converted coffee script must be the same 100% and vice versa.
use
http://code.jquery.com/jquery-git.js
http://code.jquery.com/jquery-1.7.1.min.js
http://code.jquery.com/jquery-1.7.1.js

Error: Parse error on line 586: Unexpected 'TERMINATOR'
http://jsfiddle.net/3WaRg/

authors: keichii michaelficarra rstacruz


text:
Triggered reload in command button code wires events over and over again...

Wrote some code to add a record to the database from an inline row I created in the footer of the Bootgrid. I simply created a "command-add" as a command button, and upon click -- insert record in the database and return to reload the grid (GET from the server to reload the data). When this occurs, the "on" events get wired again, thus creating two inserts. The more times I do it, the more it gets re-wired:
$(document).ready(function () {
        $("#grid-basic").bootgrid({
            ajax: true,
            url: "@Url.Action("GetRoles")",
            formatters: {
                "commands": function (column, row) {
                    return "<button type=\"button\" class=\"btn btn-xs btn-default command-edit\" data-row-id=\"" + row.role_id + "\"></button> " +
                           "<button type=\"button\" class=\"btn btn-xs btn-default command-delete\" data-row-id=\"" + row.role_id + "\"></button>";
                }
            }
        }).on("loaded.rs.jquery.bootgrid", function () {
            /* Executes after data is loaded and rendered */
            $(this).find(".command-edit").on("click", function (e) {
                alert("You pressed edit on row: " + $(this).data("row-id"));
            }).end().find(".command-delete").on("click", function (e) {
                alert("You pressed delete on row: " + $(this).data("row-id"));
            }).end().find(".command-add").on("click", function (e) {
                $element = $("#add-role-text");
                $("#add-role-text-group").removeClass("has-error has-feedback");

                // Validate element
                if ($element.val() == "") {
                    $("#add-role-text-group").addClass("has-error has-feedback");
                } else {
                    // Text is valid; fire off Save
                    $.ajax({
                        type: "POST",
                        url: "@Url.Action("AddRole")", // the method we are calling
                        contentType: "application/json; charset=utf-8",
                        data: JSON.stringify({ description: $element.val() }),
                        dataType: "json",
                        success: function (data) {
                            $("#grid-basic").bootgrid("reload");
                        }
                    });
                }
            })
        });
    });

Is this a bug or do I need to unhook the hooks before the reload?
UPDATE: I'm assuming this has something to do with the reload re-rendering the buttons, but not the footer, thus I'm wiring the event over and over again.

I'm not clear what your html is, but your analysis looks right: every time you load that grid, you're adding a new click handler. That's not a bootgrid problem and I'm sure you can work out how to avoid doing it.
I just stick one click handler on the grid's click.rs.jquery.bootgrid event at initialization time, then suck the event target out of that and do the business. You need to mod bootgrid a fraction to get the target - there's a ticket I created here for that.

You are reloading the grid every time you add a new record, right?
 $("#grid-basic").bootgrid("reload");

Which means, the event loaded is being called again.
You should be removing event handlers from the buttons before adding then again:
.on("loaded.rs.jquery.bootgrid", function () {
   //Remove event handlers
   $(this).find(".command-edit").off();
   $(this).find(".command-delete").off();
   $(this).find(".command-add").off();

   $(this).find(".command-edit").on("click", function (e) {
     alert("You pressed edit on row: " + $(this).data("row-id"));
   }).end().find(".command-delete").on("click", function (e) {
     alert("You pressed delete on row: " + $(this).data("row-id"));
   }).end().find(".command-add").on("click", function (e) {
     /* Yout button logic */
   });
});

You are reloading the grid every time you add a new record, right?
 $("#grid-basic").bootgrid("reload");

Which means, the event loaded is being called again.
You should be removing event handlers from the buttons before adding then again:
.on("loaded.rs.jquery.bootgrid", function () {
   //Remove event handlers
   $(this).find(".command-edit").off();
   $(this).find(".command-delete").off();
   $(this).find(".command-add").off();

   $(this).find(".command-edit").on("click", function (e) {
     alert("You pressed edit on row: " + $(this).data("row-id"));
   }).end().find(".command-delete").on("click", function (e) {
     alert("You pressed delete on row: " + $(this).data("row-id"));
   }).end().find(".command-add").on("click", function (e) {
     /* Yout button logic */
   });
});

Thank you so much man, in my case "$(".clearFilters").off();" did work. Since this button was on the top of the grid, was not placed in every row.
jobsTable.on("loaded.rs.jquery.bootgrid", function () {
$(".clearFilters").off();
$(".clearFilters").click(function() {
**** code was here ****
});
});

authors: jlrolin lcguida omerfarukaslan philwig

repo: rstaib/jquery-bootgrid


text:
Improve docs for mode arg of spark_write_*()

The sparklyr docs for spark_write_*() include a mode arg but lack a reference to where one can determine the set of possible values for that arg.  I think the correct reference is http://spark.apache.org/docs/latest/sql-programming-guide.html#save-modes.
I had intended to make a PR, but I noticed multiple occurrences of #' @param mode for each function in conjunction with #' @inheritParams spark_write_csv.  So, I wasn't certain whether the same ref could serve all funcs (and if so whether the individual #' @param mode lines should be dropped in favor of a single inherited param.
Some guidance would be appreciated.  Relevant R file.

@russellpierce all the instances of @param mode under data_interface.R would support those. Would be great if you can send a PR with something like:
#' @param mode Specifies the behavior when data or table already exists. Supported values include: error, append, overwrite and ignore.

You would also have to regenerate the docs with roxygen, using RStudio Build Menu -> Document

Should that text be provided at each function or just once under spark_write_csv with the individual @param mode entries dropped?

I'll pick this up next week.  I'll default to dropping the extra mode statements unless I hear otherwise.

@russellpierce we would want to change each function since all of the functions under the data_interface.R support those values.
I don't think we are currently sharing doc @param across that file, so unless you want to refactor into a single parameter block, we would want to change each of them.
Thanks for giving this a shot.

authors: javierluraschi russellpierce

repo: rstudio/sparklyr


text:
Blitz timeouts with EasyEngine

Did a quick comparison of the same site on two instances:

with W3TC Page (memcached), Object Cache (memcached), and W3TC Browser cache enabled. - My current setup

with EasyEngine Nginx fastcgi cache, Nginx Browser cache, and w3tc object cache (memcached).

Test site was a copy of real full wordpress site with more than 500 posts.
Attached are the Blitz results. EE Nginx settings are default. I am not sure if EE Nginx settings should be optimized but I am surprised to see the big difference. @rahul286 any thoughts would be much appreciated.

Did you verify fastcgi cache was working correctly?
Please share URL you tested.

https://www.blitz.io/
I'll try to incorporate some of these tests/results into my workflow.  Thanks.

www.htpcbeginner.com was the test site.
Yes, fastcgi cache is working:

Here are the links to full blitz reports:

https://www.blitz.io/report/671aa8181fe71068232f458e2f6eef05
https://www.blitz.io/report/671aa8181fe71068232f458e2f4bdd13

with W3TC Page (memcached), Object Cache (memcached), and W3TC Browser cache enabled. - My current setup

What was web server config in other case? Was it nginx/apache?

with EasyEngine Nginx fastcgi cache, Nginx Browser cache, and w3tc object cache (memcached).

Did you test with pagespeed on/off? What was command used to create EE site?
If you have both setup available can I check wordpress admin and server config for both cases?

Nginx, MySQL, PHP5-FPM, Memcached, and Opcache.
Nginx with pagespeed (but disabled in site config), MariaDB, PHP5-FPM, FastCGI cache, Memcached, and Opcache. ee site create htpcbeginner.com --wpfc.

I found that with pagespeed the CPU usage was 5-6 times higher. That was a brief test and did not dig deeper.
pagespeed still included in nginx.conf. Should exclude that?

Nginx, MySQL, PHP5-FPM, Memcached, and Opcache

Was it custom nginx config or generated by EE?

pagespeed still included in nginx.conf. Should I exclude that?

Ya. Please turn off pagespeed and test again.

I have the EE setup (2) active right now which I can give you access. If you want the other setup (1), I will have to flip the DNS (but I can provide shell access without flipping DNS).
If so, let me know how I can forward the details privately.

Wow!!! Big difference with pagespeed completely off. Now EE results much better and I had to run it twice just to make sure.

With EE I had 34 more errors but the response times were much improved and stable. Not sure why pagespeed slows the site down so much.
https://www.blitz.io/report/671aa8181fe71068232f458e2f6cb3bb

I just verified an EE site and it works nice!
Before pagespeed update - https://www.blitz.io/report/671aa8181fe71068232f458e2f04567c
I will be running same test with pagespeed soon.

Yours is even better. How do you have such low response times, is it because rtcamp.cloudapp.net is a blank WP site?
And why does pagespeed slow the site down - opposite of what it is expected to do.

I think it would depend on what pagespeed is doing.  I will test with pagespeed off.  I know I am probably asking it to do too much.  It has to parse all the output before sending it to the browser, but thought that if the content was cached, the time getting the file to PS would be minimal, or PS could cache that output, so it's not crunching each and every time.

Blank site should not matter as once a page is cached, it matter of nginx reading a static file from fastcgi-cache which is stored in memory (tmpfs) in EE.
Lower response time could be because of location of server may be closer to blitz test server.

I also faced similar error rate with pagespeed - https://www.blitz.io/report/671aa8181fe71068232f458e2f4b10bc
I will try to check pagespeed config.
By default when ee enables pagepseed, it only enable support. One need to play with pagespeed filters and this part cannot be automated as it depends on site's markup.

@cm896 @rahul286 Thanks for spending time on this.

I just remembered a discussion from rtcamp forum - http://community.rtcamp.com/t/fastcgi-cache-related-questions/2076/2
I will check  https://groups.google.com/forum/#!msg/ngx-pagespeed-discuss/vzSq8XQPGmM/9mE11D-9U8YJ in morning.

Meanwhile, if anyone finds anything concrete in thread https://groups.google.com/forum/#!msg/ngx-pagespeed-discuss/vzSq8XQPGmM/9mE11D-9U8YJ or anywhere else on the web, please let us know.

@htpcBeginner Thanks for sharing your information, the insight into the added overhead PS is adding to the average response time will help me debug and I will test with it disabled, even though the client loves the boost to the page rank score shown.
All the credit goes to @rahul286.  I am only a bystander, trying to read, learn and improve.  I am using the debug slides/suggestion from @rahul286 to find my client's site speed issues.  Thanks @rahul286 for all the great work and suggestions, it's appreciated.

@rahul286  One last question. EE by default sets worker_rlimit_nofile to 100000. Should this be customized based on hardware?
I also have worker_processes to 2 (2 core VPS) instead of EE's auto and worker_connections to 2048 instead of EE's default 4096.

Because of the above results, I will be moving to EE. Next up is removing W3TC and settling on object cache solution with either memcached or redis.

I guess this thread has answer - https://developers.google.com/speed/pagespeed/module/downstream-caching. I will try to test this tomorrow. But if anyone tries and gets it working, please share config/results.
EE's copy of nginx already has ngx_cache_purge purge module compiled in it so that step can be skipped.
About other questions:

I also have worker_processes to 2 (2 core VPS) instead of EE's auto and worker_connections to 2048 instead of EE's default 4096.

Auto always means equal to number of cores, which is recommended. In your case, it would have been 2 only with auto.

EE by default sets worker_rlimit_nofile to 100000. Should this be customized based on hardware?

Ya. I do not have formula for it but I prefer to set higher limits. My idea is to not let a server hit its own limit before OS limits. But again, I set it randomly and it worked. Before that my load tests were failing quite early.

Next up is removing W3TC

We also want to remove W3TC and hence added support for pagespeed. If pagespeed works nicely, we can use it for minify and CDN.
I loved W3TC in early days but it seems bloated now. So I also want to remove it from my servers asap.

Thanks @rahul286. Exactly the reason why I tried pagespeed - minifying and CDN.

minifying and CDN

BTW basic CDN can be done using nginx subs_filter
For minify, if pagespeed refuses to work again, I am planning to try some wp plugin.
But I really wish pagespeed to work!

Good to know. My second option after pagespeed for minifying is autoptimize.https://wordpress.org/plugins/autoptimize/

During my clients testing, we pulled all the files to AWS's cloudfront/S3 bucket.  From Digital Ocean, I didn't notice any speed gain in the images being served.  When I profiled those resources, the CDN didn't offer any advantages, it had a few negative pagespeed impacts though, 1, images from the CDN could not be converted to webp, or inlined, or optimized for sizes.  GTmetric, Page Rank were both dinged when I served images from the CDN rather than from the site under page speeds control.  We backed the CDN out and allow page speed to serve those images in favor of the better score, since there wasn't a content delivery improvement.  For this client, SPDY and SSL were the improvements.  I think removing the CDN and plugin to manage it, although we were handling it through W3tc plugin, and then testing with having page speed handling it with
CDN Support
pagespeed MapRewriteDomain cdn.example.com www.example.com;
Link to one analysis of SPDY + SSL over CDN: https://thethemefoundry.com/blog/why-we-dont-use-a-cdn-spdy-ssl/

@htpcBeginner Have you looked at this one:  https://wordpress.org/plugins/wp-minify-fix/
This one was updated and email blast sent out today - it has a pro version too:
https://wordpress.org/plugins/wp-smushit/
I'd rather not have a WP plugin handle this stuff, and allow PS to handle it.  I have a feeling my WP install is already over bloated with plugins and it's killing the performance.

Good stuff about CDN. That is what I am finding with CDN tests and hence why I am not using CDN currently.
I am going to leave minify off for now until we know something more about pagespeed, which is my preference.

The problem we have encountered with pagespeed concatenating and minifying js/css is the url length limit, so all scripts, and all css don't make it into one file.  That's a bummer, and not all the plugins are not playing nice.  Some suggestions to help PS handle these were to:

remove the query strings appended to the css and js enque'ed files.
remove the id's for the css includes/calls.

A custom filter worked to resolve both these issues.
// Remove query string from static files
function remove_cssjs_ver( $src ) {
if( strpos( $src, '?ver=' ) )
$src = remove_query_arg( 'ver', $src );
return $src;
}
add_filter( 'style_loader_src', 'remove_cssjs_ver', 10, 2 );
add_filter( 'script_loader_src', 'remove_cssjs_ver', 10, 2 );
function remove_style_id($link) {
return preg_replace("/id='.*-css'/", "", $link);
}
add_filter('style_loader_tag', 'remove_style_id');
I thought to maybe re-write the file names so more could be smushed together in one call to the server, but we eventually had to back this out since the smushed JS sometimes didn't completely function correctly.  So now we are back to 20 css requests, and 26 js requests, which surprisingly still delivers a 94% GTmetric score.  :(

Update:
Please check for related discussion - https://groups.google.com/forum/#!msg/ngx-pagespeed-discuss/vzSq8XQPGmM/9mE11D-9U8YJ
Current way is to configure downstream caching in pagespeed. But in my test it did not perform well and was too complex to setup.
Pagespeed developer is working on simplifying this - https://groups.google.com/d/msg/ngx-pagespeed-discuss/vzSq8XQPGmM/vAOyCN_JH0cJ
I am not sure how long it will take but I will prefer to wait till then.

Update:
http://www.jefftk.com/downstream-caching-draft
So far downstream caching seems to be only workaround.
Need to check:

[ ] weather downstream-caching works at all with php/mysql crash
[ ] how it works with full-page redis and fastcgi-cache
[ ] scale - HTML response rate should be similar to non-pagespeed variant
[ ] multiple sites - can it work nicely for 100s of sites on a single server. Will each site will need two blocks?

We no longer support pagespeed so we won't be able to look further in this. Sorry.

repo: rtCamp/easyengine


text:
ISIS hold timer for a neighbor is always ~60sec irrespective of the neighbor's hold time

Bug Description:
ISIS adjacency exists between a Router (R1) and a Bngblaster. On R1, hold timer is configured as 180sec. And from blaster it is expected that it announces the neighbor to be down after 180sec. But it is observed that it declares the neighbor to be down in approximately  60sec.
Version (bngblaster -v): Version: 0.7.9
JSON configuration:
    "interfaces": {
        "tx-interval": 1,
        "rx-interval": 1,
        "io-slots": 4096,
        "network": [
            {
                "interface": "SN-14-S4",
                "address": "131.0.0.2/24",
                "gateway": "131.0.0.1",
                "isis-instance-id": 1,
                "isis-level": 2
            }
        ]
    },
    "isis": [
        {
            "instance-id": 1,
            "area": [
                "49.0001/24"
            ],
            "system-id": "1921.6800.1007",
            "router-id": "192.168.1.7",
            "hostname": "BBL1",
            "hello-padding": true,
            "sr-base": 70000,
            "sr-range": 2000,
            "sr-node-sid": 7002,
            "teardown-time": 15,
            "lsp-tx-interval": 5,
            "lsp-tx-window-size": 5
                    }
                ]
            }

Steps to reproduce the behavior:

Configure 180sec hold time on R1
Make the ISIS neighbor down on R1

Expected behavior:
Bngblaster is expected to declare the neighbor to be down in 180sec
Bngblaster log for isis:
Jul 05 16:13:49.797809 ISIS L2 adjacency UP on interface SN-14-S4
Jul 05 16:13:50.488119 Resolve network interfaces
Jul 05 16:13:50.488205 All network interfaces resolved
Jul 05 16:16:50.206916 ISIS RX L2-LSP PDU checksum error on interface SN-14-S4
Jul 05 16:17:49.502686 ISIS P2P-Hello timeout on interface SN-14-S4
Jul 05 16:17:49.502735 ISIS L2 adjacency DOWN on interface SN-14-S4
Jul 05 16:21:20.883952 Received signal Interrupt (2), initiating teardown

Fix merged to dev!

Fixed in 0.7.10!

authors: DivyaBharathiS GIC-de

repo: rtbrick/bngblaster


text:
How to get the "stable" version with release branches?

https://docs.readthedocs.org/en/latest/versions.html says "We also create a stable version, if your project has any releases."
Is it possible to have the "stable" version if I'm using release branches, or does "stable" only work for release tags?
I currently have a "master" and "1.0.1" branch, but I don't see the option to build a "stable" version in my admin panel (I would like to have "/en/stable/" point to the "1.0.1" branch). How is this supposed to work, exactly? My docs are at http://docs.citationstyles.org/en/latest/.

It's also unclear to me what a "release" means in version control terms here. Tag? Branch? GitHub release notes without the "pre-release" bit set?

I noticed that the RTD documentation was recently updated to clarify that the "stable" version is only available when there are "tagged releases". See https://github.com/rtfd/readthedocs.org/commit/c5f696edba17376c54747fed786f7346fafb54e6
That said, I pushed some tags to my repository, and I still don't see any option to build "stable". (see also https://github.com/rtfd/readthedocs.org/pull/1046#issuecomment-73639262 )

I've had tags on my project for a while and I still don't see a "stable" option for my project either.  I think the original docs were set up before any tags were added, is it possible that it doesn't re-check after you've added tags?

I'm also unclear on how the stable branch is determined.
My project has the following branched

1.2-line : Latest stable release line
dev : Development branch
pypi: Latest release on PyPI

I also use git tags for releases.
I released a 2.0.0a1 version which is now on both the dev and pypi branch. The stable version on RTD shows up as the 2.0.0a1. This is incorrect; I would expect it to show the latest release on the stable 1.2-line branch.
Does RTD do any parsing of version numbers according to, e.g. semver.org or PEP440 to determine which is the stable branch? If not, it would be a nice feature to add. It would also be great if we could specify which git branch should be used for the stable version docs.

readthedocs basically goes through all the versions you see in the admin panel and takes the names there and parses them with distlib. So all the strings like 'v1.0', 2.0.0a1 etc should work. Branch names like master will fail during parsing and then be left out when trying to figure out the available version numbers.
The distlib version in use is 0.1.2 which is quite old, so if some versions are parsed unexpectedly than that's probably the reason. distlib 0.1.2 is following PEP-386 for parsing, where as the "newer" Python community probably expects PEP-440.
@sloria I think your problem is directly related to that. Maybe we should upgrade the distlib library.

@rmzelle We have merged a change which might have fixed the problem with you not beeing able to build a staging version. Is this possible for you now?

I got it to work a while back (https://readthedocs.org/projects/citation-style-language/). Not sure how, but I did switch back and forth between GitHub repos, which might have done the trick.

Great :)

authors: ericholscher gregmuellegger mboersma rmzelle sloria tisdall


text:
Expose ENV variable to build environment for build step

Expose the current build step to the build environments. This would allow for step detection and executing commands during specific build steps.

@agjohnson can you explain this issue a little more?
BTW, is this issue still relevant?

Updated the description. I think this is probably a valid feature, but low priority

authors: agjohnson humitos


text:
ImportError: cannot import name get_apps

Hi.
I try to install ReadTheDocs on Ubuntu 14.04 LTS however,  as the docs says that I need to run ./managepy syncdb - there is no such command syncdb, it is sync data. When I run this, I get the bellow error. Can you tell  me what is wrong and update your docs so I can install this? Thanks!
./manage.py syncdata
[11/Jul/2017 02:26:33] root:120[13211]: INFO Generating grammar tables from /usr/lib/python2.7/lib2to3/Grammar.txt
[11/Jul/2017 02:26:33] root:120[13211]: INFO Generating grammar tables from /usr/lib/python2.7/lib2to3/PatternGrammar.txt
Traceback (most recent call last):
File "./manage.py", line 11, in
execute_from_command_line(sys.argv)
File "/opt/rtd/local/lib/python2.7/site-packages/django/core/management/init.py", line 353, in execute_from_command_line
utility.execute()
File "/opt/rtd/local/lib/python2.7/site-packages/django/core/management/init.py", line 345, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/rtd/local/lib/python2.7/site-packages/django/core/management/base.py", line 348, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/rtd/local/lib/python2.7/site-packages/django/core/management/base.py", line 399, in execute
output = self.handle(*args, **options)
File "/opt/rtd/local/lib/python2.7/site-packages/django_extensions/management/utils.py", line 58, in inner
ret = func(self, *args, **kwargs)
File "/opt/rtd/local/lib/python2.7/site-packages/django/utils/decorators.py", line 184, in inner
return func(*args, **kwargs)
File "/opt/rtd/local/lib/python2.7/site-packages/django_extensions/management/commands/syncdata.py", line 67, in handle
from django.db.models import get_apps
ImportError: cannot import name get_apps

Thanks for working to get Read the Docs into your organization. We currently don't have time to support local installs for free as a core team. This is explained in more depth here: http://docs.readthedocs.io/en/latest/open-source-philosophy.html#unsupported -- I will close this issue because of this policy.
We do offer paid hosting for companies at readthedocs.com, as well as paid support for local installs.

authors: AdnreiHN ericholscher


text:
[Support] Can't reset password

Details

Project URL: nimble.readthedocs.io
Read the Docs username (if applicable): p.dmitriev@nimble.com

I am trying to reset the password for p.dmitriev@nimble.com through https://readthedocs.org/accounts/password/reset/.
Expected Result
An email with a password reset link will arrive in p.dmitriev@nimble.com mailbox.
Actual Result
No email arrived.

@rmihael can you check your SPAM folder or similar? Seems to be related to your own email account.
I just reset my own password and I got the proper email in my inbox.

I checked all folders, no signs of this email. Other emails arrive just fine.
The only thing that is special about this account is that it was disabled for some time and now re-enabled. Could it be that your email delivery service applies some weird rules for such accounts?

@humitos, can you suggest any other action that I can take? We cannot fix documentation because of this problem. Is it possible to change account's email to something else that belongs to our domain? devadmin@nimble.com will work for me. I can confirm this change from p.dmitriev@nimble.com mail.

@humitos, sorry to bother you, but this problem is blocking us. Is there anything that I can do to recover access to this account?

@rmihael Hi! Don't worry. I don't know what's the process here, so I'm asking to not screw anything :)
I'm sorry that I don't have the solution yet.

@rmihael, I sent an email to p.dmitriev@nimble.com from my readthedocs.org email account. Please respond to that email to confirm your ownership over the account in question.

@davidfischer, I just replied. Thank you for help.

Thanks I received it and sent a temporary password to that email. I'm glad we got this sorted out.

Thank you so much!

authors: davidfischer humitos rmihael


text:
restapi: decouple ProjectViewSet from the pk

We may want to hook the very same viewset under a different
router in order to lookup by slug and not pk. If we use
lookup_field instead of hardcoding it in the views, it becomes
easier.

As a side note let me add that v1 has the undocumented property that it supports out of the box using the slug as primary key that the v2 does not have.

Updated the PR after reivew

Can we have the request changes removed reconsidered after my answer please?

Ping :)

@agjohnson care to reconsider your review after https://github.com/rtfd/readthedocs.org/pull/4192#discussion_r194901317 please?
This one would make #4286 trivial for projects endpoints at least

Ping

@xrmx its in our radar. please keep wait some days!

I'm not convinced yet that this is something that we need to change in our code base.

We may want to hook the very same viewset under a different router in order to lookup by slug and not pk

Because of this problem, among others, we are creating APIv3. So, if this PR doesn't fix a bug I think we shouldn't make this changes to be able to extend the API code for something that will be covered in APIv3 and put this energy in that PR instead.

@humitos This PR cleans the code up to make it reusable instead of requiring people to copy & paste it. It's not extending the API so it's not adding more maintenance burden for you.
So while these changes don't fix any bug, they help reducing the downstream diff so that it would be easier to track upstream and forward fixes and features back.

Rebased to fix conflict errors

Rebased, any chance this can be merged please?

authors: humitos safwanrahman xrmx


text:
AttributeError: 'Tensor' object has no attribute 'ndim'

Hi Ryan.
I am a beginner and trying to learn deep learning.
I was following your recipe summarization code and I got below 'ndim' attribution error when I was running predict.ipynb.
The below error happens when I execute the codebloc:
model = Sequential()
model.add(rnn_model)
if activation_rnn_size:
model.add(SimpleContext(name='simplecontext_1'))
Here is the full error:

AttributeError                            Traceback (most recent call last)
 in ()
3
4 if activation_rnn_size:
----> 5     model.add(SimpleContext(name='simplecontext_1'))
C:\ProgramData\Anaconda3\envs\tensorflow\lib\site-packages\keras\models.py in add(self, layer)
330                  output_shapes=[self.outputs[0]._keras_shape])
331         else:
--> 332             output_tensor = layer(self.outputs[0])
333             if isinstance(output_tensor, list):
334                 raise TypeError('All layers in a Sequential model '
C:\ProgramData\Anaconda3\envs\tensorflow\lib\site-packages\keras\engine\topology.py in call(self, x, mask)
570         if inbound_layers:
571             # This will call layer.build() if necessary.
--> 572             self.add_inbound_node(inbound_layers, node_indices, tensor_indices)
573             # Outputs were already computed when calling self.add_inbound_node.
574             outputs = self.inbound_nodes[-1].output_tensors
C:\ProgramData\Anaconda3\envs\tensorflow\lib\site-packages\keras\engine\topology.py in add_inbound_node(self, inbound_layers, node_indices, tensor_indices)
633         # creating the node automatically updates self.inbound_nodes
634         # as well as outbound_nodes on inbound layers.
--> 635         Node.create_node(self, inbound_layers, node_indices, tensor_indices)
636
637     def get_output_shape_for(self, input_shape):
C:\ProgramData\Anaconda3\envs\tensorflow\lib\site-packages\keras\engine\topology.py in create_node(cls, outbound_layer, inbound_layers, node_indices, tensor_indices)
164
165         if len(input_tensors) == 1:
--> 166             output_tensors = to_list(outbound_layer.call(input_tensors[0], mask=input_masks[0]))
167             output_masks = to_list(outbound_layer.compute_mask(input_tensors[0], input_masks[0]))
168             # TODO: try to auto-infer shape
C:\ProgramData\Anaconda3\envs\tensorflow\lib\site-packages\keras\layers\core.py in call(self, x, mask)
639         if 'mask' in arg_spec.args:
640             arguments['mask'] = mask
--> 641         return self.function(x, **arguments)
642
643     def get_config(self):
 in simple_context(X, mask, n, maxlend, maxlenh)
12     activation_energies = K.batch_dot(head_activations, desc_activations, axes=([2],[2]))
13     # make sure we dont use description words that are masked out
---> 14     assert mask.ndim == 2
15     print(mask[:, None ,:maxlend])
16     activation_energies = K.switch(mask[:, None, :maxlend], activation_energies, -1e20)
AttributeError: 'Tensor' object has no attribute 'ndim'

Hi - can you try switching the backend to Theano? I ran into this problem as well, and switching backends resolved the issue for me.


text:
Multi-metadata

A very useful feature for reflection systems like RTTR is to be able to attach multiple copies of the same metadata key, each with a different value.
A simplified example taken from some production code in a game engine with a reflection system very similar to RTTR:
REFLECT(FooNode)
(
  // used by node graph UI to enumerate the events an instance of FooNode can emit
  node::event<EventA>(),
  node::event<EventB>(),
  node::event<EventC>()
)
.method("something", &type::something)
.property("thing", &type::thing);

Notably that interface doesn't even require an explicitly-named metadata key and instead just keys metadata by the type of the metadata itself. However, an interface that still requires the user to specify keys but allowed multiple values would be good on its own. Key-less metadata is not explicitly required, though it can be a further convenience (perhaps by just using the type of the value as the key if no key is explicitly specified?).

You can do this right now.
RTTR_REGISTRATION
{
    registration::class_<foo>("foo")
        .method("func", &foo::func)
        (
            metadata("one key", std::make_tuple(node::event<EventA>(),
                                                node::event<EventB>(),
                                                node::event<EventC>()))
        )
}

Making the metadata implicit is not something I would prefer.
It just nice to read, that the following data is metadata.
Just think about following situation:
RTTR_REGISTRATION
{
    registration::class_<foo>("foo")
        .method("func", &foo::func)
        (
            metadata("A", "value"),
            metadata("B", "value"),
            metadata("C", "value"),
            default_arguments(nullptr),
            policy::meth::discard_return
        )
}

instead of:
RTTR_REGISTRATION
{
    registration::class_<foo>("foo")
        .method("func", &foo::func)
        (
            node::event<EventA>(),
            node::event<EventB>(),
            node::event<EventC>(),
            default_arguments(nullptr),
            policy::meth::discard_return
        )
}

Having this metadata function makes the registration code more readable.
Btw. the metadata gets moved into an std::array, so no memory is wasted.
A quote from boost python:

Remember the Zen, Luke:

"Explicit is better than implicit"

"In the face of ambiguity, refuse the temptation to guess"

A single key is non composable (can't have functions that easily add groups of metadata to a class, or macros, etc.), and more explicit to boot. :)

I mean that separate keys is more explicit.

I do not really get it.
Do you want something like JSON?
variant var = prop.get_metadata("key1.key2.key3");

No.
I think the Event case I gave early is a good example, but I'm not sure how to better phrase it.
Adding multiple values to a single key has composability problems. I'm forced to list out all Event metadata in a single place and can't easily build up that list using helper functions. This can be important for composition-based class design, among other things.
It also ends up being a problem for inheritance, though an easier one to deal with: you just end up forcing the end-user querying metadata to walk the inheritance hierarchy to find all base's metadata. Helper functions could then deal with combining the metadata from the class hierarchy. But such workarounds shift the composition cost to every query instead of once at registration time.

This can be important for composition-based class design, among other things.

What has the metadata to do with "composition-based class design"?
Maybe you can show me the other way around, show me an interface where you can retrieve your multiple key-to-value metadata? Sorry, but I don't get it otherwise.
What I can assure you is, this metadata wrapper function is needed and cannot be left away.

What has the metadata to do with "composition-based class design"?

I need metadata of the same type on a single class that comes from multiple sources. Sticking with the Event example, it is very common to have a type that can receive a great many events: the ones it can receive, the ones that parents can receive, and the ones that inner data members can receive.

Maybe you can show me the other way around, show me an interface where you can retrieve your multiple key-to-value metadata

// inefficient way that fills in a vector
// take vector as inout so user can opt to reuse the allocated space
vector<Event> events;
my_type->query_metadata<Event>(key, events);
for (Event const& ev : events) ...

// faster way
strongly prefering a returned range and not a returned vector
for (Event const& ev : m_type->query_metadata<Event>(key)) ...

Our codebase is littered with constructs like those for network protocol generation, UI generation, component validation, asset conditioning, etc.
For registration, that can look like:
auto& r = registration::class_<foo>("foo")
  (
    foo::Inner::compose()
   )
  .method(...)
  ( ... );

Assuming foo::Inner::compose() returns a function object whose operator() takes the registration builder type, RTTR can invoke that object (akin to how IOStreams manipulator functions compose). That then allows for Foo to have metadata injected into it from other sources that are not necessarily under the direct control of Foo.
Not being able to do that means that the loops up above have to not only manually iterate over Foo to find its copy of key and then manually search parents for key but then also iterate through each and every member of both Foo and all parents to see if they have a new composable_key or such. Turns into a pain, and a pain that's pushed out into every single call sight (or a helper) instead of localized in the internals of type registration.
If that hasn't made my case, I admit defeat and am perfectly fine with this request being closed. :)

What I can assure you is, this metadata wrapper function is needed and cannot be left away.

Of course. It's a perfectly reasonable API design.

authors: acki-m seanmiddleditch

repo: rttrorg/rttr


text:
gitcommit CWD doesn't seem to work properly

Using this config:
grunt.initConfig({
    gitcommit: {
        'default': {
            options: {
                message: 'test',
                cwd: '../../builds/'
            },
            files: [{
                src: ['release.tar'],
                expand: true,
                cwd: '../../builds/',
            }]
        }
    }
})

It fails to commit as the resulting action is to make the CWD = ../../builds/ as expected, but then tries to find the file as  ../../builds/release.tar, which throws a fatal error in the git command due to files being used outside the working directory (of git).
Any ideas about how to get around this?

i made it work using the 'directory' key instead of 'cwd'

Same problem here. My project folder structure looks as following:
/project/frontend - here is my Gruntfile.js and my frontend html app
/project/webapp - here is my backend application.
Each folder has an own git repo.
My build process copies files from /project/frontend/app to /project/webapp/frontend .
I want to git add and git push for both repo. But when I set the options.cwd to <%= yeoman.dist %> (which points to /project/webapp) then I receive the following error message:
Running "gitadd:build" (gitadd) task
fatal: ../webapp: '../webapp' is outside repository
How can I git add/commit/push any git repo outside my Gruntfile.js folder?

same issue here... :+1: for a fix

same here

authors: barkoczi camsjams dominikwilkowski gbaumgart whallz

repo: rubenv/grunt-git


text:
Adding translation for Brazilian Portuguese language (pt-BR)

Added translation for the pt-BR locale, simply copied the files from the en locale and translated them.
If anything is wrong or incorrect, please, contact me.
Thanks!

Thanks!

authors: ramirovjr rubenwouters

repo: rubenwouters/crm-launcher


text:
Account list empty

Hi,
I tried to use the ForceInteractiveSignIn() method in the AuthenticationUiController script in the Start() method but then this error showed up (see screenshot).
From what I understand it's searching for credentials that are retrieved from the GetAccountAsync() in the original code.  When I tried to use the method it is saying me that my accounts variable is empty, am I missing something?
Thank you.

Hi ThomasVRAI, are you still having the same problem?

Hi ThomasVRAI, are you still having the same problem?

I'm having the same issue.
Any chance setting up an app on your Azure for demonstrating it working, and exporting a Unity package that is completely setup for us?

Hi @rubit0 did this issue every get resolved? I've just come across the same issue after setting up the example project

Greetings @WoodingMP , this project isn't maintained anymore and I suppose in the last 2 years the Graph API has changed somewhat. As an alternative you can access MS Graph via the standard web API but doing so would still require some leg work.


text:
POC usage of node pattern generic parameters

https://github.com/rubocop-hq/rubocop-rspec/pull/804#discussion_r438747249
Support introduced in https://github.com/rubocop-hq/rubocop-ast/pull/31
Presumably generic parameters support will land in RuboCop 1.0 or 1.0.1 worst case.

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[-] Added tests.
[-] Updated documentation.
[-] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

RuboCop 0.8.7 we're currently depend on depends on rubocop-ast 0.1.0, and rubocop-ast has this feature baked-in. So this change is safe to merge without expecting breakages with earlier RuboCop versions.

Green.

repo: rubocop-hq/rubocop-rspec


text:
Layout/RescueEnsureAlignment issue with proc using embedded rescue

Expected behavior
No error ;)
Actual behavior
Error:
An error occurred while Layout/RescueEnsureAlignment cop was inspecting /Users/cheerfulstoic/github/fishbrain/rutilus-api.side/test.rb:4:2.
Mention the following information in the issue report:
0.61.1 (using Parser 2.5.3.0, running on ruby 2.5.3 x86_64-linux)

Steps to reproduce the problem
A file with just this code fails:
utc_zone_parse =
  proc do |datetime_string|
    utc_zone.parse(datetime_string)
  rescue ArgumentError
    raise "Date/time string was in an invalid format: #{datetime_string}", nil
  end

This doesn't fail:
utc_zone_parse =
  proc do |datetime_string|
    begin
      utc_zone.parse(datetime_string)
    rescue ArgumentError
      raise "Date/time string was in an invalid format: #{datetime_string}", nil
    end
  end

RuboCop version
[dependabot/bundler/rubocop-0.61.1 !?] > bundle exec rubocop -V
0.61.1 (using Parser 2.5.3.0, running on ruby 2.5.3 x86_64-darwin17)

Same with
runtime_info =
  Timeout.timeout(5) do
    maintenance_task.vhost.runtime_info
   rescue StandardError
     false
  end

Seems like there's a deeper problem than what #6552 addresses. No longer sure that is the correct location for a fix. 🤔

I also get this error for the following code:
valid = begin
          URI.parse(value).is_a?(URI::HTTP)
        rescue URI::InvalidURIError
          false
        end

I have more examples if needed.

My original issue was using 0.61.1 though...  I don’t think this is resolved yet...  I see the CHANGELOG about the new fix, but it doesn’t seem to be released yet

Oh, looking closer I see it was closed via the commit (sorry, I was on my phone before).  Look forward to 0.61.2 ;)

authors: Drenmi Flipez cheerfulstoic codebycliff

repo: rubocop-hq/rubocop


text:
Improve some error messages

These are some changes I made a while ago, but forgot to PR.
The idea is to make some error messages less ambiguous. Not sure if many people may have been confounded by the previous wording like me, but I feel the new wording leaves no room for misinterpretation?
Quoting one of my comments in https://github.com/rubocop-hq/rubocop/issues/5184 for the rationale:

The thing is the message is not refering to "line alignment" but to "parameter alignment", that's what I find confusing since as I see it whereas lines are aligned (they have the same number of leading whitespace), parameters are not (they are distanced differently to the beginning of the line).

That's why I think "Make sure all lines containing the parameters of a method call have the same indentation" or something along those lines would be more clear. At least I wouldn't have got wrong expectations about what this cop should do.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[ ] Run rake default or rake parallel. It executes all tests and RuboCop for itself, and generates the documentation.

Two general suggestions:

I think “Make sure …” should instead be “Ensure …”.
And “containing x on y” should instead be “containing x of y”.

I am however not a native English speaker…

Thanks for the suggestions @bquorning! I had the same thought about the second point, but as a non notive speaker myself either, I couldn't figure out which one was the correct one. Regarding the same point, looks better to me, I'll add it!

Is there an agreement in @rubocop-hq/rubocop-core that the changes improve the names? To me, personally, the new messages sound a bit more confusing.

Other than finding debatable that parameters like
a(1,
  2, 3
  4)

can be considered "aligned", I also find confusing the "if they span more than one line" part. It seems to imply that you don't consider multiple parameters on the same line as "aligned" but you make an exception or something. I don't get it.

I get your point, but I think a better message then the proposed one would be:
Ensure that all lines containing elements of a hash literal are vertically aligned.
Or
Align vertically all lines containing elements of a hash literal.
However, it many language context I've seen the wording Align vertically hash literal/array/whatever elements. and it seems most people understand what they are supposed to do.

I'm not sure what's unclear/confusing about the new message though. I wanted to explitcitly avoid the term "align" since I find it ambiguous in this context.
However, you're very right that I may be the only one finding this confusing, and I already understand what this cop is trying to achieve, so... Feel free to close this if you think this is fixing a non issue!

ping @bbatsov. What do you think? Should I close this PR?

Yeah, I guess we can close this PR for now.

authors: bbatsov bquorning deivid-rodriguez


text:
Fix a false negative for Rails/TransactionExitStatement

Follow up https://github.com/rubocop/rubocop-rails/pull/674#issuecomment-1107330877
Revert "[Fix #669] Fix a false positive for Rails/TransactionExitStatement"
This reverts commit d9ec02de75d95337e7dc2a8f876ba8a4874276c1 and tweak a spec.
So this PR fixes a false negative for Rails/TransactionExitStatement when return is used in rescue.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[ ] If this is a new cop, consider making a corresponding update to the Rails Style Guide.

Should this cop also be enabled for .with_lock?

This PR is not for that purpose. It can be treated as another story. Please open an issue with details if you like :-)

authors: ixti koic

repo: rubocop/rubocop-rails


text:
[Fix #11173] Fix an incorrect autocorrect for Style/CollectionCompact

Fixes #11173.
This PR fixes an incorrect autocorrect for Style/CollectionCompact when using reject with block pass arg and no parentheses.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!

authors: bbatsov koic

repo: rubocop/rubocop


text:
[Fix #13402] Fix a false positive for Lint/SafeNavigationConsistency

Fixes #13402.
This PR fixes a false positive for Lint/SafeNavigationConsistency when using unsafe navigation with both && and ||.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

This PR fixes a false positive for Lint/SafeNavigationConsistency when using unsafe navigation with both && and ||.

The title speaks about false negatives. :-)

Oops! That is a typo and I fixed it.


text:
Update User Agent string to provide additional information

Description
Please describe your pull request in detail.
Related Issue
Resolve #506
Motivation and Context
Allows for better and more detailed monitoring on which SDKs on which versions of PowerShell
How Has This Been Tested?
Unit tests have been created to validate assumptions in the code
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:
Go over all the following points, and put an x in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!

[X] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTION document.
[X] I have updated the CHANGELOG file accordingly for the version that this merge modifies.
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.

It's ready for review, after discussion with @drew-russell, we decided to base64 encode the platform information in the user agent header.

repo: rubrikinc/rubrik-sdk-for-powershell


text:
SVG may take a long time to display in IRuby in a browser

If you try to display a scatter plot of data that contains a large number of samples, the browser may freeze.
Numo.noteplot
  plot SomeBigData
end

In this case, he PNG format may be more appropriate than the SVG format.
Of course, the SVG format is good for displaying small sized data.
So there is no best format for every situation.
One solution is to be able to specify the format.
Numo.noteplot
  set :term, :png
  plot SomeBigData
end

Numo.noteplot(format: :png)
  plot SomeBigData
end

Numo::Noteplot.set_format :png

etc...

But I do not know if this is really good.

This is a lazy way
Numo.gnuplot
  set :term, :png
  set :output, "hoge.png"
  plot SomeBigData
end
open "hoge.png"

@kojix2
'pngcairo' may be best terminal type for every situation.
pngcairo:

png:

This issue is old and will be closed.
When I think about it, this is not a problem that should be handled on the numo-narray side. My bad.

This issue is old and will be closed.
When I think about it, this is not a problem that should be handled on the numo-narray side. My bad.

repo: ruby-numo/numo-gnuplot


text:
Fix ENOENT error when readline is not loaded

Update -- I believe this error has nothing to do with Rails, but was exposed because my version of Ruby 3.3 did not have readline built properly. When readline could not be loaded, it falls back to the code which calls gets, and if there is a filename in ARGV, it will try to load that file as input to rdbg. I think the fix remains -- it's the same as https://github.com/ruby/debug/issues/156
A simple way to replicate it would be to move readline.so out of the way in your local ruby installation, and then with the programm in test.rb:
require 'debug'
debugger

then run this ensuring there's a file path in ARGV, e.g. ruby test.rb. This should hit the error.
Further update -- I think this may ultimately be because the readline-ext gem is no longer bundled as of Ruby 3.3 (https://bugs.ruby-lang.org/issues/19616); this means that by default, readline.so (or readline.bundle) will not load, and we will hit this code path.

Original report message:
Under Ruby 3.3, without this change, running tests under Rails (7.1.3) using the bin/rails test command fails.
Either way, making this change seems to fix it. The error is very reminiscent of that described in https://github.com/ruby/debug/issues/156, where a similar fix was required.
I apologise but I am not sure how to express this failure in a test, but I can confirm that the build does not fail under Ruby 3.3 either with or without my proposed change.
I should say that I'm running this on an M1 Pro processor, and I have a colleague using an Intel mac who cannot replicate this, so perhaps that's involveD?
The failure can be expressed in two ways. If a whole test file is being run (e.g. bin/rails test test/models/thing_test.rb, then it looks like the whole contents of the file are being passed to rdbg:
(rdbg) nil
(rdbg) (rdbg) false
(rdbg) (rdbg) eval error: (rdbg)//private/tmp/thing/test/models/thing_test.rb:1: syntax error, unexpected end-of-input, expecting ';' or '\n'
...gTest < ActiveSupport::TestCase
...                               ^
nil
(rdbg) eval error: (rdbg)//private/tmp/thing/test/models/thing_test.rb:1: syntax error, unexpected end-of-input
test "stuff" do
               ^
nil
(rdbg) #<ThingTest:0x000000012409ebe0>
(rdbg) true
(rdbg) eval error: (rdbg)//private/tmp/thing/test/models/thing_test.rb:1: syntax error, unexpected `end'
nil
(rdbg) eval error: (rdbg)//private/tmp/thing/test/models/thing_test.rb:1: syntax error, unexpected `end'
nil
(rdbg) Really quit? [Y/n]

If a specific line is passed (e.g. bin/rails test test/models/thing.rb:4), then the failure is different:
(rdbg) #<Thread:0x000000011eae9c40@DEBUGGER__::SESSION@server /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:179 run> terminated with exception (report_on_exception is true):
/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/console.rb:146:in `gets': No such file or directory @ rb_sysopen - test/models/thing_test.rb:6 (Errno::ENOENT)
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/console.rb:146:in `gets'
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/console.rb:146:in `readline'
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/local.rb:78:in `block in readline'
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/local.rb:90:in `block in setup_interrupt'
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:1981:in `intercept_trap_sigint'
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/local.rb:83:in `setup_interrupt'
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/local.rb:77:in `readline'
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:444:in `wait_command'
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:404:in `block in wait_command_loop'
	from <internal:kernel>:187:in `loop'
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:403:in `wait_command_loop'
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:329:in `process_event'
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:254:in `session_server_main'
	from /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:212:in `block in activate'
nil
#<Errno::ENOENT: No such file or directory @ rb_sysopen - test/models/thing_test.rb:6>
@@@ #<Thread:0x0000000102a5b308 run>
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:1251:in `backtrace'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:1251:in `block in wait_next_action_'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:1249:in `each'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:1249:in `rescue in wait_next_action_'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:1244:in `wait_next_action_'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:875:in `block in wait_next_action'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:866:in `block in fiber_blocking'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:866:in `blocking'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:866:in `fiber_blocking'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:875:in `wait_next_action'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:320:in `suspend'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:251:in `on_breakpoint'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/breakpoint.rb:69:in `suspend'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/breakpoint.rb:170:in `block in setup'
 > /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:2633:in `debugger'
 > /private/tmp/thing/test/models/thing_test.rb:7:in `block in <class:ThingTest>'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest/test.rb:94:in `block (3 levels) in run'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest/test.rb:191:in `capture_exceptions'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest/test.rb:89:in `block (2 levels) in run'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:303:in `time_it'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest/test.rb:88:in `block in run'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:412:in `on_signal'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest/test.rb:239:in `with_info_handler'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest/test.rb:87:in `run'
 > /Users/james/.gem/ruby/3.3.0/gems/activesupport-7.1.3/lib/active_support/executor/test_helper.rb:5:in `block in run'
 > /Users/james/.gem/ruby/3.3.0/gems/activesupport-7.1.3/lib/active_support/execution_wrapper.rb:105:in `perform'
 > /Users/james/.gem/ruby/3.3.0/gems/activesupport-7.1.3/lib/active_support/executor/test_helper.rb:5:in `run'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:1126:in `run_one_method'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:378:in `run_one_method'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:365:in `block (2 levels) in run'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:364:in `each'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:364:in `block in run'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:412:in `on_signal'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:399:in `with_info_handler'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:363:in `run'
 > /Users/james/.gem/ruby/3.3.0/gems/railties-7.1.3/lib/rails/test_unit/line_filtering.rb:10:in `run'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:185:in `block in __run'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:185:in `map'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:185:in `__run'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:162:in `run'
 > /Users/james/.gem/ruby/3.3.0/gems/minitest-5.21.2/lib/minitest.rb:86:in `block in autorun'
@@@ #<Thread:0x00000001200d30d8 /Users/james/.gem/ruby/3.3.0/gems/activerecord-7.1.3/lib/active_record/connection_adapters/abstract/connection_pool/reaper.rb:42 sleep>
 > /Users/james/.gem/ruby/3.3.0/gems/activerecord-7.1.3/lib/active_record/connection_adapters/abstract/connection_pool/reaper.rb:48:in `sleep'
 > /Users/james/.gem/ruby/3.3.0/gems/activerecord-7.1.3/lib/active_record/connection_adapters/abstract/connection_pool/reaper.rb:48:in `block in spawn_thread'
["DEBUGGER Exception: /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/thread_client.rb:1255", #<Errno::ENOENT: No such file or directory @ rb_sysopen - test/models/thing_test.rb:6>, ["/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/console.rb:146:in `gets'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/console.rb:146:in `gets'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/console.rb:146:in `readline'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/local.rb:78:in `block in readline'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/local.rb:90:in `block in setup_interrupt'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:1981:in `intercept_trap_sigint'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/local.rb:83:in `setup_interrupt'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/local.rb:77:in `readline'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:444:in `wait_command'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:404:in `block in wait_command_loop'", "<internal:kernel>:187:in `loop'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:403:in `wait_command_loop'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:329:in `process_event'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:254:in `session_server_main'", "/Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:212:in `block in activate'"]]
E

Error:
ThingTest#test_stuff:
Errno::ENOENT: No such file or directory @ rb_sysopen - test/models/thing_test.rb:6
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/console.rb:146:in `gets'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/console.rb:146:in `gets'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/console.rb:146:in `readline'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/local.rb:78:in `block in readline'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/local.rb:90:in `block in setup_interrupt'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:1981:in `intercept_trap_sigint'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/local.rb:83:in `setup_interrupt'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/local.rb:77:in `readline'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:444:in `wait_command'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:404:in `block in wait_command_loop'
    <internal:kernel>:187:in `loop'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:403:in `wait_command_loop'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:329:in `process_event'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:254:in `session_server_main'
    /Users/james/.gem/ruby/3.3.0/gems/debug-1.9.1/lib/debug/session.rb:212:in `block in activate'

I have updated the description with some comments that I think more clearly identify the situation where this issue occurs -- it's nothing to do with Rails, and only occurs when the compiled Readline library cannot be loaded. This is the default case on a new Ruby 3.3 installation, because the readline-ext gem is no longer included by default.

thanks!

repo: ruby/debug


text:
IO#each_codepoint raises an exception at incomplete character before

EOF when conversion takes place

See #175
See [Bug 11444]

Thank you for your contribution, it looks great!
We are getting close to have specs for all core changes in #175!

authors: eregon sgarciac

repo: ruby/spec


text:
Export member list

Resolves #034
Description

Admins and volunteers are now able to export a csv that includes all users of the app. I found these resources helpful while completing this task: http://spaghettirefactory.blogspot.com/2015/05/testing-csv-exportsdownloads-in-ruby-on.html and https://gorails.com/episodes/export-to-csv.
Type of change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not
work as expected)
This change requires a documentation update
Documentation update

How Has This Been Tested?

Screenshots

Hey there @cattywampus or @yarmiganosca! Could I get your review/approval on this? Thank y'all :-)

repo: rubyforgood/babywearing


text:
Feature 46 add org logos

Closes #46

As of now, 5 images are supported, would need a css-grid to accomodate more
Images get picked dynamically from the images folder
Controlled by environment variables
If more images are added, the images would auto-adjust

(ATLAS image as primary)

(ATLAS as secondary)

(ATLAS as primary+secondary)

repo: rucio/webui


text:
chore(main): release 1.0.0

:robot: I have created a release beep boop
1.0.0 (2024-09-09)
Features

add config for packages (f587c56)
add config for packages (996ffd6)
add config for packages (f629ae0)
add config for packages (363ba00)
add config for packages (f870622)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ruijadom/ruijadom-infra/releases/tag/v1.0.0 :sunflower:

repo: ruijadom/ruijadom-infra


text:
Add VAT to per-product order data

Right now we only save the VAT of the entire order. When an order is completed, VAT should be added to each product in the Products custom field sent to Rule.

Added in V2.0 release (#26)

repo: rulecom/woorule