I updated last version of jsView in my application, after that depends does not working.
myFuction.depends = [entity,"PropertyObject.**"]
Before update to last version it worked.
Someone knew what had changed?
Thank
It seems to work for me. Can you provide a simple repro sample, which worked on the previous version and fails after the update?
Even better, report a new issue here: https://github.com/BorisMoore/jsviews/issues, and include a repro sample there
.
Related
I am getting the error here in this Travis build, and I cannot reproduce it locally. Yes, I realize that I do not have a minimal reproducible example, but I do know that it happens within tidyselect::vars_select(). Has anyone else encountered this before? I cannot find any mention of lang_unnamespace() in a Google search.
See if modifying your travis yaml to include the dev versions of the tidyverse packages help.
It looks like you're not calling rlang::lang_unnamespace() directly, correct? That function appears to have been removed, but tidyselect::vars_select() is still trying to call it.
I arbitrarily went back to the beginning of the year to see this old version.
The file doesn't even exist in today's version.
I just upgraded 2sxc to 09.08.00 and an app suddenly stopped working.
So what we called in the template was:
data-latitude='#Content.Lat.Replace(",",".")'
data-longitude='#Content.Long.Replace(",",".")'
And that worked fine, but after the upgrade, it does not render the coordinates anymore, so in the source, I can see data-latitude data-longitude but no values.
Any ideas what I should change?
I'm not sure but there was an issue with numbers being zero instead of null when not set, causing side-effects. It will be fixed in 9.10 to be released next week. Please check that first, otherwise post your question again.
Daydream is a chrome extension (by /segmentio on github) that records your actions into a Nightmare (automated testing) script.
I'm trying to create a tutorial for how to use it but it is not producing a consistent/accurate script when I repeat a simple user journey. Some actions are being missed from the end script in some instances and then being recorded successfully on another occasion.
This is the issue documenting my exploration on github: https://github.com/dwyl/learn-daydream-and-nightmare/issues/8
Initially I recognised the issue when navigating to a new tab in a test and so I commented on an existing issue on the subject on Segment's repo: https://github.com/segmentio/daydream/issues/31
The issue was first raised by another user in September 2016 and has not received any response so I think it's unlikely they will respond.
- Has anyone come across this problem using Daydream? and did you find a solution?
- Is there a specific action which may be causing this bug?
- Can anyone see any issues in the segmentio code that could be causing this?
Thanks :)
I have this patch developed for mailman-2.1.13, and I would like to port it to mailman-2.1.15
I never did this before, so I'm asking for advices here. How would you go about this task ? Here are my thoughts on the subject :
I could search the 2.1.15 codebase for code segments corresponding to the patch, but I would miss any new part depending on the patched code.
I could look at the diff between 2.1.13 and 2.1.15 and search for parts conflicting with the patch, at the risk of drowning into the many changes between the versions
I could simply rewrite the patch but I would need to understand all the logic of the patched application, which could be quite long ...
Your advices are welcome !
The keywords for search are "rebase", "merge" and "conflict".
A conflict occurs when different parties make changes to the same document, and the system is unable to reconcile the changes. A user must resolve the conflict by combining the changes, or by selecting one change in favour of the other.
You would find that resolving conflicts (e.g. porting patch to newer version) is usually not trivial operation and cannot be done correctly without deep understanding of code you work with.
Really depends on the change in main code base from mailman-2.1.13 to mailman-2.1.15, but sometimes it is easier to rewrite patch from scratch, sometimes it is sufficient to merge changes from patch to new version and try to fix the conflicts/problems it makes.
I would start with finding out what was the original problem that patch wanted to solve and how it was solved. Then look to 2.1.15 code and find out if the original problem is still there and if it is possible to apply the patch directly (internals didn't change so much in meantime) or new approach must be applied.
I have been using Rstudio a great deal these days but recently noticed that my commands are not being stored in the history any longer. I don't know then this started, but it might have been with the install of the most recent version. Any ideas on what the issue may be?
Thanks,
This is a bug that we introduced in v0.93.73 and fixed in v0.93.75. Please try updating to the latest version at http://www.rstudio.org/download/desktop/.
Thanks and sorry for the inconvenience!
If everything is normal (i.e., no bugs) there should be a checkbox under Tools > Options > General which says Always save history (even when not saving .RData). This should be checked "Yes". Then look for the hidden file .RHistory in the present working directory and there your command history is.
(This comment is less for the OP than for a googler who stumbles across this question.)