I found a minor defect in the MSL3.2.1b4 and wanted to report it through the proper bug tracker for Modelica as is indicated on GitHub under Development and Contribution.
Below is an example of what I tried to submit (along with changing the various drop down options that are given). However, when I click submit it is indicated as potential spam with the following message:
"Trac thinks your submission might be Spam. To prove otherwise please provide a response to the following."
But no response option is give to indicate it is not spam. I've tried it in Chrome and Internet Explorer thinking it might be a browser issue but neither attempt worked.
Question:
How can one properly contribute to improving Modelica and more specifically Modelica Standard Library?
Sample:
'''Defect''': {{{Modelica.Fluid.Interfaces.PartialTwoPort}}} has what appears to be an incorrect reference for the visibility option of the white triangle portion of the flow direction arrow.
''Example'': When {{{showDesignFlowDirection = false}}}, the blue portion disappears leaving the white triangle hanging out all alone in space.
'''Suggested Correction'''
replace:
{{{visible=allowFlowReversal}}}
with:
{{{visible=showDesignFlowDirection}}}
I went ahead and contacted the Modelica.org webmaster.
I got the following response:
"The trac captcha plugin is currently broken so the usual way to gain
karma to bypass the spam filter does not work."
So that's good to know. Once I'm aware this issue is fixed I will update this answer.
Related
Almost answered here. Which directs us to the code coverage for pull requests page.
However, it doesn't say anywhere what this orange exclamation mark means.
I've hunted high and low to find an article that describes what the orange line means but I'm unable to find an article to link to. Looking at the HTML/CSS elements on the page it is described as a warning.
Here is an example of when it was showing for me:
Looking at the tests I was reviewing, there were certain cases in the linq statement that were not being tested, e.g. when there is more than one lesson with the same name. After getting the other developer to add in this missing test it turned green.
From this, I can deduce that the orange warning will show when there are some test cases that haven't been covered in a block of code. Of course, there may be other reasons as well but this is one I've found.
I want to hide the vertical line as shown in How to hide/disable VSCode LiveShare "Start Discussion".
However, since I have not started a Live Share session, I do not know how to do this.
I would appreciate it if anyone here could help us solve this problem!
I am a new user here and it doesn't appear I can comment yet, so I am posting this as an answer instead, apologies if it is not applicable or for any confusion: More information on what extensions you're using would be helpful. Do you use the GitHub Pull Requests and Issues extension? I recently had the same issue you describe (and had not started LiveShare) and after examination I concluded the vertical line related to the GitHub Pull Requests and Issues extension (which I was not using in practice anyway) and so I uninstalled the aforementioned GitHub extension and that eliminated the unwanted discussion vertical lines. So, if you've been using aforementioned GitHub extension, perhaps the solution relates to that.
I've got a project with many open issues and I'm trying to make sense of what should be done first.
Users often add a "thumb up" when an issue is relevant to them, however I haven't found out any way to see which issues received the most "thumb up".
Is there any built-in or even external tool to find out about this?
Clicking sort by & and a reaction (thumbs up in your case) it should show issues with the most thumbs up reactions.
My site eighttwentydesign is running Joomla 3.0. I have SEF URLs on, and have done for sometime without issue. But today when you go to the site, and click on anything, say portfolio you get the home page under the portfolio's URL, but if you add a leading slash at the end, the right article (portfolio) shows. Additionally, if you click on say "Web Design" it sends you to the Portfolio page. I might add this menu is a menu within Joomla - not be adding internal links manually
Doesn't work: http://www.eighttwentydesign.com/portfolio
Does work: http://www.eighttwentydesign.com/portfolio/
I have checked the .htaccess, and actually reverted it to the original with no luck, I have check Global Config but I can't see anything which may cause this. It was working nicely yesterday. I haven't adapted with any PHP source or anything in the past few weeks, the only notifiable thing I have done is yesterday enabling the Cache - have others experienced problems after doing this? I have disabled it under global config, with no avail.
Exact Joomla Version is 3.0.2 with very few plugins
I do have daily backups, but would rather a solution and be able to figure out a prevention from that, rather than just putting on a band aid.
I've search for a good couple of hours, and aside from just not being able to fix it, it appears no one else is experiencing this, so I am starting to think it may be a bug.
Just as I was about to post this I discovered my solution.
If you are having your SEF URLs display the wrong content then solve it by disabling the Cache plugin. You can do this by doing the following steps
Login to Joomla backend
Navigate to Extensions > Plugins
Go to "System Cache"
Disable system cache
I hope this helps someone in the future as I really struggled to find any answers on this.
I have an MVC2 application and use ReSharper 6.1 - I've heavily customised the Code Inspection Severity and edited what it decides to show as errors, warnings, suggestions and hints, but I cannot seem to stop it from telling me that a specific resource is missing when utilising a HTMLHelper.
So, for instance:
<img src="<%:Url.Content("~/Resources/Image12345.jpg")%>" />
I get an error on every line similar to the above telling me that the path above does not exist - which at design time it does not, but during the build process all of these views are XCOPY'd to a location which contains all of the resources, such as the images, so at the point of running the application all of this path resolution is correct. Because of working in a team of people, some of which are new to ReSharper, I wanted to exclude this error from appearing as it may cause colleagues of mine to start fiddling with something that isn't broken.
ReSharper obviously doesn't know that this isn't an issue and it has no way of knowing which is why I want to turn off this specific bit of analysis. I've found on the whole that ReSharper is massively customizable and in version 6.1 under Inspection Severity there are some new MVC options, which have proved useful - but I can see no way of turning off the inspection for this.
Anybody have any ideas?
There are few options, press ALT+ENTER.
Suppress inspection "Path Error" with comment. You can suppress whole block of code, not only each of tag.
Suppress inspection "Path Error" at all at whole project.
There is new feature of 6.1 - path mapping, but it seems broken in conjunction with MVC.
Set to ignore that specific error by:
Open Soultion Errors Window by ReSharper->Windows->Soultion Errors Window.
Right-click annoying error and select Ignore Error.
See answer for another error for more explanation.
Well - It seems that this particular type of inspection is not currently catered for. I'll see if I can request it with JetBrains and hopefully more granular MVC inspection will be included in the future.
Cheers guys