hv-install : Install python packages failed to install libvirt-python 6.0.0

Hi,
It is happened in ALIAS lab machines
e23-h19-740xd.alias.bos.scalelab.redhat.com
e23-h17-740xd.alias.bos.scalelab.redhat.com
TASK [hv-install : Install python packages] *********************************************************************************************************************************
Monday 06 February 2023  16:46:16 +0000 (0:01:01.714)       0:01:04.258 *******
failed: [e23-h19-740xd.alias.bos.scalelab.redhat.com] (item={'name': 'libvirt-python', 'version': '6.0.0'}) => {"ansible_loop_var": "item", "changed": false, "cmd": ["/usr/local/bin/pip3", "install", "libvirt-python==6.0.0"], "item": {"name": "libvirt-python", "version": "6.0.0"}, "msg": "stdout: Collecting libvirt-python==6.0.0\n  Downloading libvirt-python-6.0.0.tar.gz (196 kB)\n  Preparing metadata (setup.py): started\n  Preparing metadata (setup.py): finished with status 'done'\nUsing legacy 'setup.py install' for libvirt-python, since package 'wheel' is not installed.\nInstalling collected packages: libvirt-python\n  Attempting uninstall: libvirt-python\n    Found existing installation: libvirt-python 8.0.0\n\n:stderr: ERROR: Cannot uninstall 'libvirt-python'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.\n"}
failed: [e23-h17-740xd.alias.bos.scalelab.redhat.com] (item={'name': 'libvirt-python', 'version': '6.0.0'}) => {"ansible_loop_var": "item", "changed": false, "cmd": ["/usr/local/bin/pip3", "install", "libvirt-python==6.0.0"], "item": {"name": "libvirt-python", "version": "6.0.0"}, "msg": "stdout: Collecting libvirt-python==6.0.0\n  Downloading libvirt-python-6.0.0.tar.gz (196 kB)\n  Preparing metadata (setup.py): started\n  Preparing metadata (setup.py): finished with status 'done'\nUsing legacy 'setup.py install' for libvirt-python, since package 'wheel' is not installed.\nInstalling collected packages: libvirt-python\n  Attempting uninstall: libvirt-python\n    Found existing installation: libvirt-python 8.0.0\n\n:stderr: ERROR: Cannot uninstall 'libvirt-python'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall.\n"}
PLAY RECAP ******************************************************************************************************************************************************************
e23-h17-740xd.alias.bos.scalelab.redhat.com : ok=2    changed=1    unreachable=0    failed=1    skipped=5    rescued=0    ignored=0
e23-h19-740xd.alias.bos.scalelab.redhat.com : ok=2    changed=1    unreachable=0    failed=1    skipped=5    rescued=0    ignored=0
Monday 06 February 2023  16:46:21 +0000 (0:00:04.878)       0:01:09.136 *******
hv-install : Install packages --------------------------------------------------------------------------------------------------------------------------------------- 61.71s
hv-install : Install python packages --------------------------------------------------------------------------------------------------------------------------------- 4.88s
Gathering Facts ------------------------------------------------------------------------------------------------------------------------------------------------------ 2.11s
install-tc : Wait for machine to be ready after reboot --------------------------------------------------------------------------------------------------------------- 0.11s
install-tc : Install packages ---------------------------------------------------------------------------------------------------------------------------------------- 0.09s
install-tc : Wait for machine rebooting ------------------------------------------------------------------------------------------------------------------------------ 0.07s
install-tc : Reboot hypervisor --------------------------------------------------------------------------------------------------------------------------------------- 0.07s
install-tc : Install kernel modules ---------------------------------------------------------------------------------------------------------------------------------- 0.06s
As workaround need replace in /root/jetlag/ansible/roles/hv-install/tasks/main.yml

name: Install python packages
pip:
name: pip
extra_args: --upgrade
loop:

name: Install python packages
pip:
name: "{{ item.name }}"
loop:

name: libvirt-python
name: setuptools_rust
name: sushy-tools

My initial theory here is that the Alias lab has a newer version of RHEL than the scale lab, can we confirm what version of RHEL is deployed by default in the Alias lab?

By default ALIAS lab machines provisioned with RHEL 8.5.
But I upgrade them using the script ./update-latest-rhel-release.sh 8.6 because we use RHEL 8.6 as default hypervisors for OCP deployments.

I see, aside from using newer (ideally less buddy) versions of software is there a particular reason to use something newer than the defaults for just hosting VMs from the lab?  I'm curious if as part of the hypervisor setup we should include an upgrade to the latest rhel and reuse what you provided here.

Closing this as it is now a year later and I actually recommend users to run from the latest RHEL 8 (8.9)


Problem with solar altitude / timezone

When using the attached weatherfile, I get errors with the sun altitude. If the timezone is changed to 0 errors disapear, but there may be two problems: 1) this is not truth (because Spain timezone is +1); 2) I am not sure if this may affect the tracker angle or other calculations somehow.
I let you know that I have download the file from PVGis
I have checked some sunrise and sunset times here and they seems fine. Note that Spain increase 1 hour in spring-summer.
PS Attached file is .txt because is not possible upload .epw. Please change it before use it.
Murcia_tmy_era_37.992_-1.131_2007_2016.txt

Hello Daniel,
Couple questions to track this issue ~ Which version are you using?  Also which kind of errors are you getting? If you could paste a screenshot and identify one of the timestamps that is crashing that be ideal, or if you have an excel where you are tracking the sun position differences.
I know our current master version has some kinds on that and we improved on it on our latest development version. Mostly because sunrise and sunset hours, if the sun rises at let's say 7:40 am, the timestamp for 8 AM will have DNI and DHI values, but since the timestamp from 8 AM reffers to the hour of 7 to 8 the sunposition gets calculated at 7:30 AM , which for this case the sun would be below horizon. I'll try running the Murcia epw on my computer on the latest version see if it struggles too.
Also, it is my understanding EPWs do not consider daylight savings. I'm not sure if PVLib (which is what we are using to get sunposition) I'll investigate that.  I've done some comparisons with SPA before and didn't notice anything odd though ~ https://midcdmz.nrel.gov/solpos/spa.html

Hi Silvana. I am using 0.2.4, but I got the same errors with 0.2.3. Attached is a txt with the text of the errors.
I confirm you that the Murcia EPW file timestamp is according to our winter time (even spring-summer data). I have not seen errors differences among seasons, so I guess this is not the problem.
I have tested someEPW files from European cities and errors are just for some of them (Murcia, Madrid, Coruña, Bordeaux and Paris) while others do not show them (Brussels, Lisbon). Attached you have the weather files.
Lisbon_tmy_era_38.708_-9.137_2007_2016.txt
Madrid_tmy_era_40.417_-3.704_2007_2016.txt
Brussels_tmy_era_50.847_4.352_2007_2016.txt
Coruna_tmy_era_43.057_-8.53_2007_2016.txt
Paris_tmy_era_48.853_2.364_2007_2016.txt
Bordeaux_tmy_era_44.841_-0.58_2007_2016.txt
Errors with Murcia EPW.txt

Hi Daniel,
Can you be more specific with the error you are getting? Is it for gendaylit - hour by hour procedure?  are you following the tracker option? Which day / hour in specific is crashing if you can give me an example for Murcia?
As I mentioned, we have updated the development version to avoid times when then sun is below the horizon., which was causing us to crash on the hour-by-hour analysis. IF this is the same bug you are encountering then I would suggest you use the development version ~ the whole process with the sun position from gendaylit to tracker changed quite a bit so I don't think it'll get bug-fixed in v. 0.2.4.

As a follow up.
I ran a couple tests with the Murcia EPW:

Gendaylit for single axis tracking. Ran correctly days FEb. 16 to March 2.
Gencumsky for tracking the whole year.
Gencumsky for fixed axis tracking the whole year.

Two and 3 ran correctly but gencumsky does return some errors for when sun is below horizon (it still continues) . This is the command that prints the error:

And this is the example of the error message.

It is deciding the sun is below the horizon for 247 hours of the year, but it is considering 4154 hours to create the sky.  This 247 hours represent 15245 W/m2 total of diffuse light not considered, distributed in the following way:

I don't think this represents a big change if we were to fix the executable for gencumsky (which was not developed by us) in terms of improving the simulation.
Anyways I'm not sure if any of these cases covers what you were seeing. I just uploaded a journal on the XandY version for all of these cases I tested above. I can't explore anything else on this issue until you tell me more exactly how to reproduce it, or if this and hte previuos exaplanations make sense and you'd rather just use our new procedure. I'll await your answer :)

Hi Silvana.
I confirm you that the errors you get are the ones I am talking about and I attached in a txt file in a previous comment (Errors with Murcia EPW.txt). I think you have not seen it :-). Sorry because I didnt said that my problem was using gencumsky.
In my case the error comes simulating with gencumsky and tracking but, from your analysis, it seems that the problem comes from gencumsky (it doesnt matter other parameters of the simulation).
I am not sure about what you mean with "use our new procedure". If the problem is from gencumsky, we can just assume that an small part of the radiation is not considered unless the algorithms in gencumsky are changed. Right?
If you need something else, please let me know. Thanks a lot for your effort and anlysis of the problem.

Ah! Excellent, thanks for sending the errors. And yes, it is an error in gencumsky/pvlib combo.
We have addressed this in the new version we are developing.  I don't know how fast it will get transferred to a formal Release version (we are shooting for before May 10th~ release).  I just ran Murcia epw in our hpc for the whole year and this new branch works well. What it does is it sets the sun's zenith angle to 89 for those times where there is DHI value before the sunrise hour, so the trackers position ends up being 0 degree tilt for those. It is a minimum contribution but at least now it doesn't crash! :)
If you need to run something before then, the X and Y branch is in stable conditions to be used right now so download it and try it before we continue doing additions to it. The journals have been documented for the procedural changes too (we simplified a ton of things). Let me know if I can help with anything else, I'm marking this as closed now!

Hi guys,
I'm getting the same error, reading the thread I thought that by updating bifacial_radiance I would be fine but I'm still getting the error message.
Any solution to this problem? When comparing to PVsyst my front and rear irradiation are far off, and when I compare the solar altitude calculated by PVsyst and Radiance (the altitude that is shown in the error message) they are very different.
I've noticed it's a random issue, or better, it only happens at certain latitudes.
Anyone experiencing the same?

Hola,
This thread is kinda old, and I think as we last communicated the sun position calculation for sunrise got fixed, I don't think you should encounter as many occurences of the sun being up and the software ignoring it as before. However , see below:
We were following SAM's sun position calculation, that for 1 hour intervals if the entry reads 11 AM, it calculates the sun position at 10:30 AM. Since May of this year, SAM switched to follow PVSyst, which does 11 AM -- sun position at 11:30 AM. We have thread open to add the option to select if you want a delta before or after the hour (or none) for the next release. This might be the differences you are seeing.
https://github.com/NREL/bifacial_radiance/issues/211
If it's another thing, can you document you're error again with the newer version so we can fix it? Thank you

Well, I'm not 100% sure it is the same problem, I'll try to explain it better.
The first thing to say is that I have ran many simulations successfully, benchmarking GII and GIIrear against PVsyst and found similar numbers. I'm saying this to rule out user errors operating Bifacial Radiance.
Now, when running my script (I'm using GenCumSky) I noticed many lines with the message "Error!  Solar altitude is -7 < -6 degrees and Idh = 129 > 10 W/m^2 on day 8 !Ibn is 0.  Attempting to continue!", for different solar altitudes.
Then, when I computed annual values I noticed GII and GIIrear are far below what I find in PVsyst, like 30% lower, which makes me think the code is leaving many timestamps behind because it considers to be "night" (negative solar altitude).
Is it the same issue? If you think it is I'm hapy to post under 0.3.4
Also, I tried following #211 but haven't managed to find any solution to this problem.

What do you mean Gfront and Grear are 30% below PVSyst? Are you summing all your values for the year, or what is it that you are doing? Even if it missed all the sunrise hours of the year, those hours have very little content of irradiance and would not affect in such a manner the results.
#211 has been solved in one of the latest commits to bifacialvf development branch around the time I created that issue, I just have to copy the code to the  function and push it to development on bifacial_radiance. Maybe I'll speed that up.
Still, that is not what is giving you the discrepancy on results. In general, bifacial radiance also gives higher irradiance values of Grear than PVSyst. Can yo describe what scene parameters are you trying to do? Or maybe share one of your result csv files?

I am summing the cumulative annual values at each tracker position (from irr_1axis_XX.csv, averaging across the module). I agree that it shouldn't have that much impact but it's not what I'm seeing.
Scena is a 1UP tracker, torque tube with 0.12m metal_grey, module dimensions 2.008x1.002, pitch 6.1m, hub height 1.4m.
lat 19.7 long -98.7
Am I forgetting something?
I understand BF Radiance will give higher irradiance for Grear (I'm fine with that), but the GII is 15% less than PVsyst and that's what I don't understand (sorry, bad math previously, 15% is correct).
I added one of the csv results, hope that's what you meant.
Thanks for the help!

Sorry, didn't realize it doesn't support .csv or .rar
irr_1axis_0.0.txt

I ran a simulation using "GetEPW" at the project coordinates and had the same error message, I guess that rules out any problem with the .epw file.
I made some comparisons between the solar altitude in the error messages and PVsyst values for solar altitude (plus another source for solar altitude) and I think when the .epw says 18:00 (which should be irradiation between 17-18) the program is calculating the altitude for 18:30 (or somewhere near this time). Could that be it?

This is part of what I'm mentioning that SAM/PVSyst and bifacial_radiance / bifacialvf calculate hte sun position different.

Still, that doesn't justify 15% difference. Have you tried running the same simulation without the torque tube? the torquetube creates shading that reduces rear irradiance.
Also, you seem to be doing this for tracking. Are you adding all of the values for the other angles too not just the center angle 0.0? Sum columns h of all the angles, and then take the average over the module.
 Are you keeping the same ratios for the module collector width and clerance height in PVsyst?

So from your second picture do you think is fair to say that bifacial_radiance is "one hour ahead"?
Yes, I have created a script that calculates both, the idea was to estimate torque tube shading doing this comparison. But either way, at this point I'm worried that GII values are not matching PVsyst (or close enough), once this is sorted I imagine rear irradiation will come closer as well.
Yes, I'm taking all tracking angles. The thing is I've done similar calculations and comparisons with PVsyst for different sites and it was all fine. I had two cases where I had problems and in both I got the "sun altitude error".
Regarding PVsyst, the first step of my approach is to simulate the exact same conditions in both environments, which means no torque tube (or zero rear shadings) and zero transparency (or a very low value to account for thermal gap), with same dimensions (module dimensions, pitch, hub height, etc).
But back to the error message, if you said the issue should have been corrected in v0.3.4, do you have any clue about anything else that could be triggering the error message? I agree that sunset and sunrise shouldn't contribute that much to the annual irradiation but I can't think of anything else and the only difference to other successful simulations is this error message.

I'll run some comparisons of my own ~ can you let me know at least one weather file you identifeid as working and one that didn't? Thank you!

Hi Silvana, sorry for the late response, holidays..
See attached a zip file containing a pdf with characteristics and PVsyst/radiance comparison for three sites (one working and two not working, same error) and EPW files that I used.
Thank you so much for looking into this!
I've looked around, researched, ran many different simulations and can't find any solution for this, so any help is much appreciated!
Cheers

Ok couple questions, observations while I proceed to test this myself:
Main doubts:

Your tracking limits vary throughout the information of inputs in PVSyst. Site 1 is either 52 or 72.1, site 2 is either 60 or 70.9, and site 3 is either 60 or 69.4.
you are not considering torque tube but you are adding a  2% shading factor. If you can provide some more details on the torquetube (diamterer, distance to the module plane), I can implement that on bifacial_radiance and validate that number.

ther details

I'm not sure what the near shadings is on site 1?
Also not sure what is the GlobInc - 2.05% on site 1?
I'm assuming the axis azimuth of -7 is this:

Also note that this is southern hemisphere (I'm not sure if the standard is to orient the trackers slightly east for Northen Hemispheres and thus for southern hemisphere it would be to orient them slightly west?)

Also on Site2 - what is "Tracker with torque tube gap"? What are you considering there?

@costeladebarata can you send me an email to continue this by mail<EMAIL_ADDRESS>I also have some files to share ~
One more thing. can you tell me how you're importing the EPW into pvsyst? I'm having issue with Cases 1 and 2 for the azimuth angle.
Case 3 looks good:

Case 2 and 1 not so muhc. I probably did something wrong, I have to go back and check:

This where my import notes:
CASE 1:
PVSYST V 6.84 - PRO30
Weather Files imported as Canada EPW (CWEC)
Site: Site1_Costal, Country Australia, Time Zone 10.0
SaveSite: Site1_Costal_EPW    ((this creates the .SIT))
Weatherfile warning: The clearness index of the best  clear days seem high with respect to the clear day model.
CASE 2
PVSYST V 6.84 - PRO30
Weather Files imported as Canada EPW (CWEC)
Site: Site2_Costal, Country Tanzania, Time Zone 3
This Meteo file seems to be OK
SaveSite: Site2_Costal_EPW    ((this creates the .SIT))

Thanks Silvana, will reach out by email and post our findings here later.


Reformat some JSON and remove an option for clang.

Remove -Qunused-arguments.
Signed-off-by: Dan Cross<EMAIL_ADDRESS>

Now you tell me? :-)


visit_MethodInvocation(self, met_invocation)

I visited methodInvocation. But some method invocations are missed.
For example:
Missed:
public static final String LOG_TAG = ACRA.class.getSimpleName();
ErrorReporter localErrorReporter = ErrorReporter.getInstance();
Visited:
MethodInvocation(name='getApplicationContext', arguments=[], type_arguments=[], target=Name(value='paramReportsCrashes'))
MethodInvocation(name='d', arguments=[Name(value='LOG_TAG'), Additive(operator='+', lhs=Additive(operator='+', lhs=Literal(value='"ACRA is enabled for "'), rhs=MethodInvocation(name='getPackageName', arguments=[], type_arguments=[], target=Name(value='paramReportsCrashes'))), rhs=Literal(value='", intializing..."'))], type_arguments=[], target=Name(value='Log'))
MethodInvocation(name='init', arguments=[Name(value='paramReportsCrashes'), Name(value='paramBoolean')], type_arguments=[], target=Name(value='localErrorReporter'))
MethodInvocation(name='setDefaultUncaughtExceptionHandler', arguments=[Name(value='localErrorReporter')], type_arguments=[], target=Name(value='Thread'))
MethodInvocation(name='setReportSender', arguments=[InstanceCreation(type=Type(name=Name(value='HttpPostSender'), type_arguments=[], enclosed_in=None, dimensions=0), type_arguments=[], arguments=[Name(value='paramString')], body=[], enclosed_in=None)], type_arguments=[], target=Name(value='localErrorReporter'))
MethodInvocation(name='checkReportsOnApplicationStart', arguments=[], type_arguments=[], target=Name(value='localErrorReporter'))
package com.facebook.acra;
import android.content.Context;
import android.util.Log;
import com.facebook.acra.reporter.ReportsCrashes;
import com.facebook.acra.sender.HttpPostSender;
public class ACRA
{
public static final ReportField[] ALL_CRASH_REPORT_FIELDS = {ReportField.ATTACHMENT_ORIGINAL_SIZE };
public static final String LOG_TAG = ACRA.class.getSimpleName();
public static final String NULL_VALUE = "ACRA-NULL-STRING";
private static ReportsCrashes mReportsCrashes;
public ACRA() {}
public static ReportsCrashes getConfig()
{
return mReportsCrashes;
}
public static ErrorReporter init(ReportsCrashes paramReportsCrashes, String paramString, boolean paramBoolean)
{
ErrorReporter localErrorReporter = ErrorReporter.getInstance();
if (mReportsCrashes == null)
{
mReportsCrashes = paramReportsCrashes;
paramReportsCrashes = paramReportsCrashes.getApplicationContext();
Log.d(LOG_TAG, "ACRA is enabled for " + paramReportsCrashes.getPackageName() + ", intializing...");
localErrorReporter.init(paramReportsCrashes, paramBoolean);
Thread.setDefaultUncaughtExceptionHandler(localErrorReporter);
if (paramString != null) {
localErrorReporter.setReportSender(new HttpPostSender(paramString));
}
localErrorReporter.checkReportsOnApplicationStart();
}
return localErrorReporter;
}
}
Thanks for your help.

The reason might be that "VariableDeclarator" doesn't implement accept().
Thanks,

This is weird. Could you provide your parsing code? I copy and pasted your Java code and parsed it as follows:
import plyj.parser as plyj
parser = plyj.Parser()

tree = parser.parse_string('''
your code here
''')

import plyj.model as m
class V(m.Visitor):
    def visit_MethodInvocation(self, mi):
        print ' - {}'.format(mi.name)

tree.accept(V())

This prints
 - getSimpleName
 - getInstance
 - getApplicationContext
 - d
 - init
 - setDefaultUncaughtExceptionHandler
 - setReportSender
 - checkReportsOnApplicationStart

which includes the two you're missing.
Incidentally you discovered another bug: My version is missing the getPackageName from the string concatenation. :)

Thanks for your quick reply!
I just added visit_MethodInvocation plyj/example/symbols_visitor.py.
I tried again and found a conflict between field and mi. If they existed together, some mi would be missing.
class V(m.Visitor):
def visit_FieldDeclaration(self, fd):
print 'Field - {}'.format(fd.type.name.value)
def visit_MethodInvocation(self, mi):
print 'Mi - {}'.format(mi.name)

Yes, in this case, it would miss getSimpleName. The current design of the accept methods requires a return value of True from all visitor methods if the children should be recursively visited. If you have a field declaration that has a method invocation as a variable initializer that should be visited, your visit_FieldDeclaration has to return True, otherwise the rest is skipped.
This does not fix the missing getPackageName which, I think, is caused by some inheritance mumbo jumbo...

Thank you very much. And look forward to your update.

Uhm.  This was no bug. Of course getSimpleType is omitted. It's part of the argument list of a method invocation itself and since our visit_MethodInvocation does not return True the visitor does not recurse into it. If you return True, everything is visited as it should.
Feel free to reopen if you still have an issue.


Installation in Contao 4.7.6 nicht möglich

Das Bundle läßt sich nicht installieren. Der Cloud Resolver wirfte mir immer denselben Fehler aus:
`

Resolving dependencies using Composer Cloud v2.0.10
[371.2MiB/5.68s] Loading composer repositories with package information
[371.5MiB/5.79s] Updating dependencies
[2025.7MiB/42.63s] Your requirements could not be resolved to an installable set of packages.
[2025.7MiB/42.63s]
Problem 1
- kmielke/calendar-extended-bundle 1.0.4 requires terminal42/notification_center 1.4.* -> satisfiable by terminal42/notification_center[1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.x-dev] but these conflict with your requirements or minimum-stability.
- kmielke/calendar-extended-bundle 1.0.3 requires terminal42/notification_center 1.4.* -> satisfiable by terminal42/notification_center[1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.x-dev] but these conflict with your requirements or minimum-stability.
- kmielke/calendar-extended-bundle 1.0.2 requires terminal42/notification_center 1.4.* -> satisfiable by terminal42/notification_center[1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.x-dev] but these conflict with your requirements or minimum-stability.
- kmielke/calendar-extended-bundle 1.0.1 requires terminal42/notification_center 1.4.* -> satisfiable by terminal42/notification_center[1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.x-dev] but these conflict with your requirements or minimum-stability.
- kmielke/calendar-extended-bundle 1.0.0 requires terminal42/notification_center 1.4.* -> satisfiable by terminal42/notification_center[1.4.0, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.x-dev] but these conflict with your requirements or minimum-stability.
- Conclusion: don't install kmielke/calendar-extended-bundle 1.0.6
- Installation request for kmielke/calendar-extended-bundle ^1.0 -> satisfiable by kmielke/calendar-extended-bundle[1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6].
- Conclusion: don't install menatwork/contao-multicolumnwizard 3.3.16
- kmielke/calendar-extended-bundle 1.0.5 requires menatwork/contao-multicolumnwizard-bundle 3.4.* -> satisfiable by menatwork/contao-multicolumnwizard-bundle[3.4.0, 3.4.1].
- don't install menatwork/contao-multicolumnwizard-bundle 3.4.0|don't install menatwork/contao-multicolumnwizard 3.3.16
- don't install menatwork/contao-multicolumnwizard-bundle 3.4.1|don't install menatwork/contao-multicolumnwizard 3.3.16
- Installation request for menatwork/contao-multicolumnwizard (locked at 3.3.16, required as ^3.3) -> satisfiable by menatwork/contao-multicolumnwizard[3.3.16].
[2025.7MiB/42.63s] Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.
[677.6MiB/50.20s] Memory usage: 677.64MB (peak: 2317.1MB), time: 50.2s.
[677.6MiB/50.21s] Finished Composer Cloud resolving.
`

Ich habe es eben in einer Contao Managed installiert.
`Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 12 installs, 0 updates, 0 removals

Installing contao-community-alliance/composer-plugin (3.0.9): Downloading (100%)
Installing pimple/pimple (v1.1.1): Loading from cache
Installing contao-community-alliance/dependency-container (2.0.3): Loading from cache
Installing contao-community-alliance/event-dispatcher (2.0.5): Loading from cache
Installing contao-community-alliance/events-contao-bindings (4.4.4): Loading from cache
Installing contao-community-alliance/translator (2.1.3): Loading from cache
Installing menatwork/contao-multicolumnwizard-bundle (3.4.1): Loading from cache
Installing codefog/contao-haste (4.23.4): Downloading (100%)
Installing terminal42/contao-leads (1.4.12): Loading from cache
Installing terminal42/dcawizard (2.4.7): Downloading (100%)
Installing terminal42/notification_center (1.5.6): Downloading (100%)
Installing kmielke/calendar-extended-bundle (1.0.6): Downloading (100%)
codefog/contao-haste suggests installing phpoffice/phpspreadsheet (Required for the Haste\IO\ExcelFileWriter component.)
terminal42/contao-leads suggests installing phpoffice/phpexcel (To enable excel export of lead data.)
Writing lock file
`
Hat wunderbar geklappt.


v1.0.0-alpha

Aggregating all feedback from issues/pull requests.
Issue: #24
Related

[x] #18
[x] #20
[x] #21
[x] #22
[x] #34
[x] #36
[x] #39
[x] #40
[x] #41
[ ] #45 (will handle separately)
[x] #46
[x] #48
[x] #50
[x] #51
[x] #54
[x] #55

@tasti Any news when this  will be released?

Awesome work thanks for this!


Split replace penalty

This PR implements a solution to issue #19. It simply provides the user with the option to turn on 'split_penalty' in the settings, which will add a 0.1 penalty to the edit distance of Alignments that split tokens apart in a replacement.
I have racked my brain and I think there is no issue with setting a penalty of 0.1 for operations that split a token, because it will only impact which Alignment is chosen in cases where the edit distance is equal. The unit tests all still pass, but I added it as a setting instead of hardcoding it in the source so that we might find a way to test it on a larger dataset, maybe with Jan's help/input. Please let me know what you think or if you see any issues with this approach.

mypy is causing all this to fail still, I would appreciate your insight on how to make it be chill about this.


rosdep update fails on Neon (Ubuntu fork)

ROS Kinetic
Steps to reproduce:
rosdep update
Result
Hit https://raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml
Query rosdistro index https://raw.githubusercontent.com/ros/rosdistro/master/index.yaml
Add distro "groovy"

ERROR: Rosdep experienced an error: Could not detect OS, tried ['windows', 'ubuntu', 'slackware', 'rhel', 'qnx', 'osx', 'opensuse', 'opensuse', 'mint', 'linaro', 'gentoo', 'funtoo', 'freebsd', 'fedora', 'elementary', 'debian', 'cygwin', 'centos', 'arch']
Please go to the rosdep page [1] and file a bug report with the stack trace below.
[1] : http://www.ros.org/wiki/rosdep

rosdep version: 0.11.5

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/rosdep2/main.py", line 136, in rosdep_main
    exit_code = _rosdep_main(args)
  File "/usr/lib/python2.7/dist-packages/rosdep2/main.py", line 351, in _rosdep_main
    return _no_args_handler(command, parser, options, args)
  File "/usr/lib/python2.7/dist-packages/rosdep2/main.py", line 359, in _no_args_handler
    return command_handlers[command](options)
  File "/usr/lib/python2.7/dist-packages/rosdep2/main.py", line 545, in command_update
    error_handler=update_error_handler)
  File "/usr/lib/python2.7/dist-packages/rosdep2/sources_list.py", line 466, in update_sources_list
    rosdep_data = get_gbprepo_as_rosdep_data(dist_name)
  File "/usr/lib/python2.7/dist-packages/rosdep2/gbpdistro_support.py", line 147, in get_gbprepo_as_rosdep_data
    ctx = create_default_installer_context()
  File "/usr/lib/python2.7/dist-packages/rosdep2/__init__.py", line 85, in create_default_installer_context
    m.register_platforms(context)
  File "/usr/lib/python2.7/dist-packages/rosdep2/platforms/debian.py", line 50, in register_platforms
    register_linaro(context)
  File "/usr/lib/python2.7/dist-packages/rosdep2/platforms/debian.py", line 64, in register_linaro
    (os_name, os_version) = context.get_os_name_and_version()
  File "/usr/lib/python2.7/dist-packages/rosdep2/installers.py", line 112, in get_os_name_and_version
    os_name = self.os_detect.get_name()
  File "/usr/lib/python2.7/dist-packages/rospkg/os_detect.py", line 621, in get_name
    self.detect_os()
  File "/usr/lib/python2.7/dist-packages/rospkg/os_detect.py", line 591, in detect_os
    raise OsNotDetected("Could not detect OS, tried %s"%attempted)
OsNotDetected: Could not detect OS, tried ['windows', 'ubuntu', 'slackware', 'rhel', 'qnx', 'osx', 'opensuse', 'opensuse', 'mint', 'linaro', 'gentoo', 'funtoo', 'freebsd', 'fedora', 'elementary', 'debian', 'cygwin', 'centos', 'arch']

System:
My OS is KDE Neon - which is a distribution building atop of Ubuntu, so it's 100% Ubuntu compatible.
Contents of /etc/os-release
NAME="KDE Neon"
VERSION="5.7"
ID=neon
ID_LIKE="ubuntu debian"
PRETTY_NAME="KDE neon User Edition 5.7"
VERSION_ID="16.04"
HOME_URL="http://neon.kde.org/"
SUPPORT_URL="http://neon.kde.org/"
BUG_REPORT_URL="http://bugs.kde.org/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Proposal:
the test for name in python should parse ID_LIKE field.

Thanks for the report.
This should probably be filed on the rosdep issues tracker or maybe the rospkg issue tracker (since rospkg is responsible for detecting OS). I believe there is some discussion on either one of those issue trackers about how to handle rebranded OSes like this one.
https://github.com/ros-infrastructure/rosdep/issues
https://github.com/ros-infrastructure/rospkg/issues

To support Neon:
rospkg will need to be extended to successfully detect it. (You can likely use the LSB detect module like Elementary)
and rosdep will need to be extended to show that Neon is an alias to Ubuntu. Here's how Elementary does that
I'm going to close this ticket as there's nothing we need to do in the rosdistro. Please open separate issues on those trackers referencing each other as well as here. Note that since Neon is not a commonly used platform we need to rely on community contributions to add support and testing so pull requests that you've tested will greatly accelerate the process.


Support WKB empty multipolygons

Currently Geo.WKB.decode/2 throws an exception when decoding
an empty multipolygon:
Geo.WKB.decode!("0106000020E610000000000000")
** (MatchError) no match of right hand side value: ""
    (geo) lib/geo/wkb/reader.ex:6: Geo.WKB.Reader.new/1
    (geo) lib/geo/wkb/decoder.ex:35: Geo.WKB.Decoder.decode!/2
    (geo) lib/geo/wkb/decoder.ex:160: Geo.WKB.Decoder.decode_coordinates/2
    (geo) lib/geo/wkb/decoder.ex:50: Geo.WKB.Decoder.decode!/2

This PR fixes it.

This is a bit of a hack fix (5min solution). There is probably a nicer solution for this, but I am not familiar with the code enough. Would be grateful for any guidance.

Looks good! Thanks!

Published: https://hex.pm/packages/geo/3.1.0


Setting domain on cookie prevents it from being read

I am trying to set the domain property so that a cookie can be used on all subdomains; however doing so seems to prevent useCookies from reading the cookie.
import React from 'react';
import { render, screen } from '@testing-library/react';
import { CookiesProvider, useCookies } from 'react-cookie';

const CookieWriter = () => {
  const [, setCookie] = useCookies(['cookie-key']);
  const options = {
    path: '/',

    // uncomment to make test fail
    //domain: '.example.com'
  };
  setCookie('cookie-key', 'cookie-value', options);

  return

;
};

const CookieReader = () => {
  const [cookies] = useCookies(['cookie-key']);

  return
{cookies['cookie-key']}
;
};

describe('', () => {
  test('', async () => {
    render(
      <React.Fragment>
        <CookiesProvider>
          <CookieWriter />
          <CookieReader />
        </CookiesProvider>
      </React.Fragment>,
    );

    expect(screen.getByText('cookie-value')).toBeInTheDocument();
  });
});

Unsurprisingly looks like the same issue is in universal-cookie:
import React from 'react';
import { render, screen } from '@testing-library/react';
import Cookies from 'universal-cookie';

const CookieWriter = ({cookies}) => {
  const options = {
    path: '/',

    // uncomment to make test fail
    //domain: '.example.com'
  };
  cookies.set('cookie-key', 'cookie-value', options);

  return

;
};

const CookieReader = ({cookies}) => {
  return
{cookies.get('cookie-key')}
;
};

describe('', () => {
  test('', async () => {
    const cookies = new Cookies();
    render(
      <React.Fragment>
        <CookieWriter cookies={cookies}/>
        <CookieReader cookies={cookies}/>
      </React.Fragment>,
    );

    expect(screen.getByText('cookie-value')).toBeInTheDocument();
  });
});

we have the same problem. When specifying the domain, the cookies won't show up anywhere.

we have the same problem. When specifying the domain, the cookies won't show up anywhere.

Hi @codeofsumit, did you find any old version that works?

@jaredculp or @codeofsumit also looking to see if either of you found a solution.


Add "readwire" interface to some Graphene Types.

This is useful when you want to read the serialized wire protocol back into objects-in-memory. Although this is rarely used on the client side of graphene networks, at least one particular use case (BitShares blind transfers) exists.
To clarify: this is bytes method in reverse.
The _readwire interface and method signature are pretty horrid, so some redesign might be required.

Codecov Report

Merging #65 into develop will decrease coverage by 1.53%.
The diff coverage is 22%.

@@             Coverage Diff             @@
##           develop      #65      +/-   ##
===========================================
- Coverage    58.97%   57.43%   -1.54%
===========================================
  Files           19       19
  Lines         1153     1203      +50
===========================================
+ Hits           680      691      +11
- Misses         473      512      +39

Impacted Files
Coverage Δ

graphenebase/types.py
38.53% <21.95%> (-2.62%)
:arrow_down:

graphenebase/account.py
65.92% <22.22%> (-2.32%)
:arrow_down:

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 59b3a62...9917fb1. Read the comment docs.

Would it be possible to add unit tests for those?

Instead of calling those methods _rewrite, can we have them fromBytes() and not begin with _. That makes it more obvious and corresponds better with the fromBuffer used in bitsharesJS


[Gifs] Updates on Gifs' image jumping issue

Umbrella issue: https://github.com/carbon-design-system/carbon-website/issues/4048
Changed

Updated new GIFs and images in Components, Patterns, and Designing pages.

@thyhmdo will take a look, fyi "password" is spelled wrong in that image 😅

@thyhmdo The gif is 1216x1216 and the png is 608x608

Same comments as Alison on that one gif. And then I added a comment above about one of your other gifs. Other than that it looks good to me!


APEXMALHAR-2082 Data Filter Operator

Added Data Filter Operator
Marked it as Evolving
Added test cases around variations

http://apex.apache.org/contributing.html page says that branch name should be named with Jira Number

I ran travis command couple of times locally and each time it completed successfully.


Vector2 reports corrupted values

Godot version
v3.4.stable.official [206ba70f4]
System information
Windows 11 and MacOS11.6
Issue description
Vector2 reports wrong values. Example:
print(Vector2(100.1, 99.3))
returns:
(100.099998, 99.300003)
This seems related to #50251.
Steps to reproduce
print(Vector2(100.1, 99.3))
Minimal reproduction project
No response

This is expected behavior, as Vector2 stores 32-bit floating-point values which cannot represent 100.1 and 99.3 perfectly. To avoid this, use an Array to store the values or two separate int variables.


mapdl.solve() problem

When I do the example "https://mapdldocs.pyansys.com/examples/00-mapdl-examples/2d_plate_with_a_hole.html#sphx-glr-examples-00-mapdl-examples-2d-plate-with-a-hole-py" and run the example codes, the solver is stuck and can't calculate the result file. The out file picture and input file picture are shown bellow. It seems there are some problems about the input file. but I don't know why

Can anyone help me ?

Sorry @1990chs, I was working on a different project.  The problem might be due to using 19.5 with the older CORBA interface what we're trying to deprecate in favor of the newer gRPC interface.  I'm going to run the same example on 19.5 on my windows installation to see if I can reproduce this issue.

Sorry @1990chs, I was working on a different project. The problem might be due to using 19.5 with the older CORBA interface what we're trying to deprecate in favor of the newer gRPC interface. I'm going to run the same example on 19.5 on my windows installation to see if I can reproduce this issue.

Thinks!

Sorry @1990chs, been bogged down with several issues right now.  I'll try to get to this during this week or on the weekend.  I'll not forget about this issue.

Thinks

@1990chs I am trying to reproduce this, and I was able to run the examples fine with 2021R1 and the latest pyansys release. What sort of environment are you on? How long did you leave it before stopping the solver?

@1990chs I am trying to reproduce this, and I was able to run the examples fine with 2021R1 and the latest pyansys release. What sort of environment are you on? How long did you leave it before stopping the solver?

Hi, my ansys version is 2019R3 and the pyansys version is 0.57.6 .I will update pyansys in next weekend and try it again

@akaszynski @jgd10
I update the pyansys to the latest version and it can work.So I close this issue


processing html files generated before with grunt-generator and multiple handlebar partials not working

hello,
i have some html files that are not processed. These html files are generated with grunt-generator and handlebar templates before processing them.
Unfortunately i cannot add my project .zip. Github denies my file. So you can get it here:
DROPBOX LINK
In the project files you will find a gruntfile with following tasks to perform, to replicate my issue:
grunt dev and grunt build: after that you find the affected files in server and dist folder.
from the server html files the dist html files are processed.
There are generated 3 html files in the dist folder, demoelements and stickyfooter is working, but index.html is not processed if i uncomment more than one handlebar partial in index.hbs. crosschecked if included html is valid...
if i add the html from the handlebar partials direct into the index,hbs, generate the html file and process afterwards, it works. if i replace the html in the index.hbs with the handlebar partials, index.html is not processed correctly
Oliver

i wasn't able to install the dependencies, .jshintrc is missing and .postinstall.js and maybe other stuff is failing too.
what block type is failing for you? is it the <-- build:include --> ? or which one?

how's it going over there?

feel free to re-open so we can review this further


Browser windows flickering on link hover

Hi there! I just installed Yabai this morning and so far, it's been pretty good! I'm having one issue, though, that is really making it tricky to use effectively.
When I open up my browser (Brave Browser) and hover over just about anything that is a link (popup or not), the browser window starts flickering and jumping around, making it incredibly difficult to click on anything.
Additionally, and this may or may not be related, when I hit CMD + f to open up the find UI in the browser, the dialog never appears. An icon in the URL bar appears as if the find has opened, but that's it.
I've attached a short screen capture and my Yabai configuration file below. I absolutely could just be doing something ridiculous, so if there's something unusual about my configuration, let me know!
Some more details on my specific circumstances:

I have SIP entirely disabled as I try to debug this
I am running a 16" MBP with M1 Max chip
I set up the sudoers file as defined in the installation instructions and ran the M1 specific command in the instructions

Screen Capture

https://user-images.githubusercontent.com/11881203/197441273-8172430f-d557-4b57-962b-5efd48ac0869.mov

Yabai Configuration

# for this to work you must configure sudo such that
# it will be able to run the command without password

yabai -m signal --add event=dock_did_restart action="sudo yabai --load-sa"
sudo yabai --load-sa

# logging on
yabai -m config debug_output on

# default layout
yabai -m config layout bsp

# useless gaps
yabai -m config top_padding 20
yabai -m config right_padding 20
yabai -m config bottom_padding 20
yabai -m config left_padding 20
yabai -m config window_gap 20

yabai -m config external_bar all:30:0

# auto-balance windows
yabai -m config auto_balance off

# split ratios
yabai -m config split_ratio 0.5

# mouse interaction
yabai -m config mouse_modifier alt
yabai -m config mouse_action1 move
yabai -m config mouse_action2 resize

# floating windows always on top
yabai -m config window_topmost on

# window shadows
yabai -m config window_shadow float

# active window borders
yabai -m config window_border on
yabai -m config window_border_width 6
yabai -m config active_window_border_color 0xffa6da95
yabai -m config normal_window_border_color 0xfff4dbd6

# application rules
yabai -m rule --add app="System Preferences$" manage=off
yabai -m rule --add app="Dash$" manage=off
yabai -m rule --add app="Zoom$" manage=off
yabai -m rule --add app="Microsoft Teams$" manage=off

That's all the information I have at the moment, but if there's something else you need from me or some way I can help with the issue, please let me know!

I have the same issue - windows flickering when I hover over links (with google chrome) and "popup windows" (like the search in a browser but also others in different apps) appearing below the main window (visible only when I press Ctrl+up).
One scenario to reproduce some of this is when I toggle a window to float (with a shortcut defined as below) it starts to cover its own popups. When I move the window a little it starts working correctly. Toggling it to managed and back to float breaks it back.
alt - t : yabai -m window --toggle float; yabai -m window --grid 4:4:1:1:2:2
A workaround to fix this that seems to work is to turn off windows_topmost in the config. I don't know if it fixes the flickering too as this one is more random...

I have the same issue on microsoft edge. Is there any way to solve the problem？

Have this exact same problem, quick fix is to just float then tile back the browser window with a shortcut. Currently will test if @mgazda's tip on setting windows_topmost off helps.

I tested this problem in both safari and edge browsers. Is there any good solution?

Have this exact same problem, quick fix is to just float then tile back the browser window with a shortcut. Currently will test if @mgazda's tip on setting windows_topmost off helps.

The problem got back after a while and it is kind of annoying to float and tile again all the time.
Setting windows_topmost off doesn't help

I updated yabai through brew and the problem got fixed. I have no idea what was causing it.

I updated Yabai through brew, but still have same problem, but I found it not happen when I delete rule for safari.
e.g:
#yabai -m rule --add app="^(Microsoft Edge|Safari浏览器)$" manage=on opacity=1.00 border=on


upgrade to cache_resource to remove deprecation warning

fixes https://github.com/blackary/st_pages/issues/18

@senickel I made a different version of this that also supports older versions of streamlit in #21. Thanks so much for the PR and for pointing out the issue!


Squash migrations

Hi everyone,
I would like to know if pumpkin migrations are possible. Check the commands and documentation and I cannot see this function.
Thanks

No, the package has nothing for using Laravel's new squashing system. This is a feature this package really needs because every new tenants needs to go through every single migrations, I have 200+ migrations and it's taking for ever to create a new tenant. I've done some testing there I think is a way to do it -ish:
If you want to squash, you need to run the command on a tenant php artisan tenancy:run schema:dump --tenant=1 this should work correctly and dump database/schema/tenant-schema.dump. This should work when creating a new tenant, if not you might want to force the connection name in the settings to tenant.
Two issues I have:

It is hard coded by Laravel to store and find the schema dump file containing the database connection name. This means when running php artisan migrate for the system database, if you have set as the default connection to "tenant" instead of "system", it will find your dump schema file of you tenant tenant-schema.dump and run it in your system connection. So for this to work you need to make sur your default database connection in config/database.php is set to system.

If you Passport as your main authentication it might conflicts with the above problem, it needs to have the default connection set to tenant. Why exactly, I'm not sure.

Hope this gives you a lead.

@stein-j thank you so much, it's working :)

@mapeveri awesome ! You can close the issue then :)


Update configure-wake-on-lan.md

wakeup is greyed out when connected to a CAS
Summarize the change in the pull request title
Describe your change, specifically why you think it's needed.
Fixes #Issue_Number (if necessary)

@russrimm : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@mestew : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hey @russrimm Thanks for the update to the doc! I tweaked the wording CAS -> Central Administration Site, but kept everything else.
#sign-off

@mestew : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off
Decided to add metadata change while I was here =)


GitHub Setting Disabled by Enterprise

Right now the GitHub token in actions does not allow for write access back to the repository, this is required by our CI and deploy system. It is disabled by Jupyter's GitHub Enterprise.

@choldgraf where should we be asking for help on this sort of stuff? Perhaps @jasongrout is in charge of this, or do we need to open an issue in Jupyter Governance?
We currently can not release a new version on CI.
See jupyter/governance#221

I think that we might be able to work around this by setting the permissions manually in the GitHub Actions configuration for each repository. If I understand it correctly, the screenshot suggests that we can't set the default permissions to write, but I think we can still set the permissions manually in our github actions config.
Here are the GitHub Actions docs on this
And this reminded me of a similar conversation we've had over in JupyterHub. (Here's a search showing how the jupyterhub team manually sets permissions throughout several repos)https://github.com/search?q=org:jupyterhub+"contents:"+language:YAML&type=code&l=YAML.
I think that if we followed a similar pattern and used write for the proper configuration, each repository should have the permissions needed to write:
permissions:
  actions: read|write|none
  attestations: read|write|none
  checks: read|write|none
  contents: read|write|none
  deployments: read|write|none
  id-token: read|write|none
  issues: read|write|none
  discussions: read|write|none
  packages: read|write|none
  pages: read|write|none
  pull-requests: read|write|none
  repository-projects: read|write|none
  security-events: read|write|none
  statuses: read|write|none

Thanks @choldgraf, I did totally read that dropdown wrong and gave up early. Not being able to enable "workflows have read and write permissions", rather than reading it as "default permissions" that can be overridden. This is fixed by adding the following to the changeset workflow yaml:
permissions:
  contents: write
  pull-requests: write

I will respond on the email letting the EC that we figured it out. Sorry for the noise @jasongrout. :)
I will update this on our other repositories now.


Make/Update guide for server owners to enable SLAM for TF2 servers

The FAQ says the following

To play a track in a CS:S or TF2 server, the server must have "sv_allow_voice_from_file" set to "1" and "sv_use_steam_voice" set to "0".

However, the sv_use_steam_voice seems to be deprecated and replaced by sv_voicecodec according to Valve
https://developer.valvesoftware.com/wiki/List_of_TF2_console_commands_and_variables
That's why I was wondering if they could update the guide to properly set up a TF2 server to use SLAM

I seems to enable SLAM in my server, these 2 convars should be enabled on server.cfg
sv_use_steam_voice 0 sv_voicecodec vaudio_celt_high


More than 3 Fragment recreate Fragment Created

Hi @zawadz88
I had a issue while adding more than 3 fragments. the first fragment automatically recreates.
With this the data will not be stable in the first fragment as the view is recreated
So i pulled your code and added a line in to your code in setAdapter method
mPager.setOffscreenPageLimit(stepAdapter.getCount());

Hi @RaghuManickam,
Could you please provide steps to reproduce?
Did that happen when you got to the third fragment and then back to the first one?
If so, that's actually the desired behaviour you get when using a ViewPager. If you don't want to lose that data you save it in onSaveInstanceState and use it later when the fragment gets recreated.
Setting the offscreen limit solves the issue only partially as it does not handle device rotations, system killing the app in the background, etc.
Please tell me if that's issue.

Hi @zawadz88 ,
this is not an issue this can be done as enhancement.
using saved instance will make more code. if we add this line in the setAdapter method we can resolve this easily.
the user may also review back in that case we need to get data from saved instance .

Hi @RaghuManickam,
I see your point. Using saved instance state makes more code however it is still needed if you want to make sure your data does not get lost e.g. on rotation, system killing the app or screen resizing in Nougat's multiwindow.
Increasing the offscreen limit will make the pager keep all the fragments in memory. In case the number of steps is larger this could have a negative impact on the app.
Having said that, I'm thinking about exposing the setOffscreenLimit in a future release. I would not want it to keep all the fragments by default.

Added in 2.0.0


Slack community link invalid

The link to https://slack.paketo.io/ in README.md is invalid
Expected Behavior
I was expecting to be redirected to the current Slack for packeto discussion.

Yes, we've been struggling with this for a bit. I thought we had it fixed but seems to be broken for me. What's weird is that it works if you're already logged into Paketo Slack, so it's deceptive.
In the meantime, you can use this invite link. It should not expire.

Hi,
Is this address supposed to be the same as the original paketobuildpacks.slack.com workspace ?

Just to add to this, it appears that the Slack invite link on your website here: https://paketo.io/community/ is using an expired invite.


Enlarging global_font_size to 30 makes hints completely unreadable

Godot version: 4.2.2.stable
Panku version: 1.7.9 (from GitHub, not available in AssetStore)
Describe the bug
My viewport is set to 4k. The default window is small and the text is also small, so I went ahead and increased size to 30. It displays good, except the hints - they are completely unreadable.
To Reproduce
Try these settings and see how things get blurred out.

Desktop (please complete the following information):

OS: Windows 10

It doesn't look like something viewport resolution or font size related.
Did you set global custom font or custom theme in your project settings?
Can you reproduce the problem on new empty project?

Hmm, I can't reproduce this in empty project:
screenshot

I do have a custom theme that I use on my root GUI control, but I don't believe this should affect Panku... Is there a special place where I can assign a theme / a font to apply to the whole project?
P. S. I also use custom theme for the editor itself, including the font. However, in an empty project this does not affect Panku, so should not be a problem either.

Ah, sorry, an update: I managed to achieve sort of the same result on an empty project:
screenshot

The change that did the trick was to switch the stretch mode of the project from disabled to canvas_items:

Here's the mrp: panku_font.zip

Thanks for providing mrp.
If I get it right, the problem appear only when app window heavily downscaled (like 4k -> fullhd on screenshot). Seems like upstream godot issue, so we can't do much here.

As a temporary workaround I only can propose to get rid of bold fonts in panku console theme, since that font type seems most affected. In res://addons/panku_console/res/panku_console_theme.tres edit RichTextLabel entry bold_font and bold_italic_font settings to some custom font. It can be godot default open sans OpenSans-SemiBold.ttf if you bother to download it, or just slap empty font variation.

Is there a special place where I can assign a theme / a font to apply to the whole project?

Yeah, custom theme in project settings affects whole app, including panku console view. It was my first thoughts when I saw the issue, but it ended I was wrong.

Thank you for the thorough response! I believe the issue is resolved then, so I'm closing at.
Thank's for the help again 🐳


app.sheet.stepOpen, .stepClose and .stepToggle types are missing in definitions

Framework7 version: 6.0.14
Platform and Target: all
Live Link or JSFiddle:

Describe the bug
The Typescript types for the functions on app.sheet.stepOpen(), app.sheet.stepClose() and app.sheet.stepToggle() are missing from the type definitions, leading to errors in Typescript.
To Reproduce
Steps to reproduce the behavior:

Attempt to use app.sheet.stepToggle() in function.
Observe Typescript errors about missing type.

Expected behavior
The types are listed.
Actual Behavior
Observed error:
Property 'stepToggle' does not exist on type '{ create(parameters: Parameters): Sheet; destroy(el: HTMLElement | Sheet |
CSSSelector): void; get(el?: HTMLElement | CSSSelector | undefined): Sheet; open(el?: HTMLElement | ... 1 more ... |
undefined, animate?: boolean | undefined): Sheet; close(el?: HTMLElement | ... 1 more ... | undefined, animate?: boolean |
un...'.ts(2339)

Types are listed as:
(property) Sheet.AppMethods.sheet: {
    create(parameters: Sheet.Parameters): Sheet.Sheet;
    destroy(el: Sheet.Sheet | HTMLElement | CSSSelector): void;
    get(el?: HTMLElement | CSSSelector | undefined): Sheet.Sheet;
    open(el?: HTMLElement | ... 1 more ... | undefined, animate?: boolean | undefined): Sheet.Sheet;
    close(el?: HTMLElement | ... 1 more ... | undefined, animate?: boolean | undefined): Sheet.Sheet;
}

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Methods are missing and also Events, such as:
sheet:stepopen, stepOpen and sheetStepOpen
sheet:stepclose, stepClose and sheetStepClose
sheet:stepprogress, stepProgress and sheetStepProgress

I might be missing something, but my current install of Framework7 v6.0.16 still does not have definitions for the step-related methods on the Sheet AppMethods Interface?
From sheet.d.ts
interface AppMethods {
    sheet: {
      /** create Sheet Modal instance */
      create(parameters: Parameters): Sheet;
      /** destroy Sheet Modal instance */
      destroy(el: HTMLElement | CSSSelector | Sheet): void;
      /** get Sheet Modal instance by HTML element */
      get(el?: HTMLElement | CSSSelector): Sheet;
      /** open Sheet Modal */
      open(el?: HTMLElement | CSSSelector, animate?: boolean): Sheet;
      /** closes Sheet Modal */
      close(el?: HTMLElement | CSSSelector, animate?: boolean): Sheet;
    };
  }

Shouldn't it have method definitions for stepToggle etc?


chore: merge main to develop

We need to wait until bot pushes a new version commit before merging this one.

not required anymore


series: rewrite to be flexible and improve stub.

Change the test suite to accept multiple signatures.
Add HINTS.md explaining how to work the exercise.
Add a example solution using ByteStrings and Sequences.
Add type signature to the stub solution.
Add variables to the stub implementation.

These change also have the effect of allowing to run the test suite with the stub solution.
Related to #421.

These change also have the effect of allowing to run the test suite with the stub solution.

Oh, was it unable to before...?
Oh, indeed it was.
    • Ambiguous type variable ‘t0’ arising from a use of ‘shouldBe’
      prevents the constraint ‘(Eq t0)’ from being solved.

I see.

I agree with every change I see here. Can I take a moment to be a stickler about separate commits?
I think one commit should be "improve stub", and the other commit everything else - everything else seems related, but "improve stub" seemed like the odd duck out in the big commit and seemed like it could go in its own commit. True, that would make the commit very small, but it seemed to make sense to me.
Unless you think the two I mentioned are inextricably linked, in which case sure, just tell me why and then merge it.

You are right, they belong to separated commits. Fixed! :smile:

Oh good, I can edit approve/request changes comments now (we were not able to before, which is why I always make it a separate comment)


Is it possible to clean up memory consumed by loaded language models?

First, I really love your library. I enjoy in using it.
There is just an issue once you loaded all languages, the cache will never clean up. Even when you setup just two languages after words. Is there or can you provide a cleanUp method? Or remove previous cache using another recreating the LanguageDetectorBuilder?
My use case is:
I am loading all languages once a month to detect which languages I need to  support.
After knowing the language set, I load only the subset for further daily detections to free my memory.
The memory is not decreasing since I loaded all languages before.

This is what I try to do :) But when I look on my memory, then it does not decrease after reassigning the new detector. Maybe I do something wrong.... Here is my code:
`private LanguageDetector detector = LanguageDetectorBuilder.fromAllLanguages().build();
public void init(final Set<String> descriptions) {
    final LanguageDetector detector = LanguageDetectorBuilder.fromAllLanguages().build();
    this.detector = LanguageDetectorBuilder.fromIsoCodes639_3(descriptions.stream().map(desc -> detector.detectLanguageOf(desc).getIsoCode639_3()).toArray(IsoCode639_3[]::new)).build();
}`

Is detector an instance variable of another class? If so, then creating the second detectorAll instance is completely unnecessary. Each instance of LanguageDetector carries its own copy of the language models.  This is not good. It's not surprising that you have memory issues then.
I suggest to rewrite the code as follows (not tested):
private LanguageDetector detector = LanguageDetectorBuilder.fromAllLanguages().build();

public void init(final Set<String> descriptions) {
    this.detector = LanguageDetectorBuilder.fromLanguages(
        descriptions.stream().map(desc ->
            detector.detectLanguageOf(desc)).toArray(Language[]::new)
    ).build();
}

Running init() will, however, not immediately free the memory from the unnecessary language models. The JVM's garbage collector decides when to free the memory. The memory will be freed if it is needed by other data. So you don't have to worry about this too much. As long as you don't get any java.lang.OutOfMemoryError, you are fine. I think your problem merely resulted from accidentally loading all language models twice which is never necessary.
Does that solve your problem?

Hi, I am still testing. I don't get any java.lang.OutOfMemoryError but the memory also doesn't decrease :( Hopefully its just the garbage collector.

Hi @YunaBraska, were you able to resolve your problems in the meantime? I'd like to close this issue if you agree because there is nothing that I can do as far as memory consumption is concerned. This is the JVM's business.
In case you don't respond, I will close this issue in the next days. Thank you.

Hi, yes you probably can close it if you cleaning up everything already. I tested many GC's but no one was cleaning it up within 24 hours...


menuRightNavigationController cannot be modified while it's presented

New Issue Checklist

I have read the guidelines for contributing and I understand:

[x] My issue is happening in the latest version of SideMenu.
[x] My issue was not solved in the README.
[x] My issue can not be answered on stackoverflow.com.
[x] My issue is not a request for new functionality that I am unwilling to build and contribute with a pull request.
[x] My issue is reproducible in the demo project.

Issue Description

hi
Installing SideMenu (2.3.0)
error log  :
SideMenu Warning: menuRightNavigationController cannot be modified while it's presented. 2017-03-24 16:20:51.696 Trangell[54206:703340] Warning: Attempt to present <SideMenu.UISideMenuNavigationController: 0x7fdc2b03d800> on <Trangell.DashbordVC: 0x7fdc2ae04400> while a presentation is in progress!

@shahryarjb This is by design.

please help me ! What should I do ?

@jonkykong @shahryarjb  How to resolve this have you found the solution? can you elaborate this


Dropdown/picker field border color too light

Description
Field border color is outdated (one gray too light). This was recently updated in DNA (Spectrum-DNA v5.24.0).
Steps to reproduce

Go to http://opensource.adobe.com/spectrum-css/
Click on Dropdown component
Observe border color for standard (not quiet) dropdown.

Expected behavior
Border color should be one gray up (gray-300 on default, gray-400 on hover and down)
Environment

Spectrum CSS version<EMAIL_ADDRESS>Browser(s) and OS(s): Chrome 81.0.4044.122 on macOS 10.15.4

Additional context
Noticed while verifying Picker (aka dropdown) for React V3

Will be addressed during core tokens migration.


⚠ Bofrost.nl has degraded performance

In d45d963, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1153 ms

Resolved: Bofrost.nl performance has improved in 1eef460.


Fix change node type

This will fix the action change_node_type and as well not break on a 2nd run, since provider expected that a ram type will always be in the output of cluster_status

:+1:

Hi @linuxdynasty!
Can you please update your PR to replace result = [] by [] (2 occurrences)?
@jjasghar what do you mean by "Need a spec"?

@odolbeau by spec i mean a chefspec or integration test. I don't merge any new feature or change without a corresponding test.

I take a look at tests. For now it seems there is very few tests related to the cluster part.
Testing this bug correction means testing the whole cluster part which is pretty hard to achieve. :/

I'm going to close this due to no activity.


XGKS storage overflow error on large plots

Reported by Ansley B Manke on 2 Jun 2003 17:13 UTC
Reported by Andrew Wittenberg 6/2/03
cannot duplicate with v5.42 on linux (actually not at all)

ferret -memsize 420

    NOAA/PMEL TMAP
    FERRET v5.42 (beta)
    IRIX 6.5 - 10/11/02
    30-May-03 17:59

yes? shade randu(x[gx=1:3000:1]+y[gy=1:3000:1])
XgksDuplicatePrimi()  300 Storage overflow has occurred in GKS
XgksDuplicatePrimi()  300 Storage overflow has occurred in GKS
Segmentation fault
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/559

Comment by<EMAIL_ADDRESS>on 2 Jun 2003 17:47 UTC
fixed in parse_command and checked in 6/2/03

Comment by<EMAIL_ADDRESS>on 2 Jun 2003 17:54 UTC
Comments from SH
In the past when we have seen this error ("XgksDuplicatePrimi()  300
Storage overflow") it has indicated that GKS was unable to malloc the
memory that it needed in order to maintain the graphical display list.
(The display list contains the graphics primitives that permit windows to
redraw when you resize them, for example.  The display list is fundamental
to the design of xGKS.  It cannot be side-stepped.)
Some first guesses: (Hans?) Is it possible that there is a Unix "limit"
command in effect that is preventing Ferret (xGKS) from getting the memory
that it is requesting?  Another possibility is in the size of the swap
file.

Comment by<EMAIL_ADDRESS>on 21 Oct 2003 20:16 UTC
Moving from the<EMAIL_ADDRESS>user to the<EMAIL_ADDRESS>user.

Comment by ansley.b.manke on 4 Nov 2008 19:50 UTC
Adding Andrew to the CC list where he is mentioned in the ticket comments.


NS-CACHE: Added support for GET and PUT object ACL

Explain the changes

Added support for PUT object ACL
Added support for GET object ACL
Added configuration param to define behavior: "reject", "pass-through", else default behavior will apply

Issues: Fixed #xxx / Gap #xxx

Missing unit tests

Testing Instructions:

Set the config.ACL_HANDLING parameter to either "reject", "pass-through" or anything else
Make PUT or GET object ACL request

@mcrepeau But you need to rebase from master

@mcrepeau Please again on master and squash to a single commit, so we can merge


Document.cookie examples don't work

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details
The examples on this page no longer work: https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie
It seems you cannot access document.cookie anymore from JavaScript, it always returns an empty string. I'm on Google Chrome/Linux.
Perhaps the examples should be removed and/or notice added.

@1202software @chrisdavidmills umm, I can try looking into what's going on.

After looking a bit on this I got to know that Google Chrome doesn't allow cookie reads / writes from file:// protocol. Other browsers allow that. Chrome allows cookie reads/writes from http protocol only: https://bugs.chromium.org/p/chromium/issues/detail?id=535.

No, this is an issue due to expected security behaviour, as reported in https://support.google.com/chrome/thread/33543699?hl=en (i.e. related to SameSite and iframes). You can see these working if you load the source pages directly in chrome. https://mdn.mozillademos.org/en-US/docs/Web/API/Document/cookie$samples/Example_2_Get_a_sample_cookie_named_test2?revision=1591237
There are a couple of potential problems outlined there. The example is in an embedded iframe with a different domain.
<iframe class="live-sample-frame sample-code-frame" frameborder="0" height="36" id="frame_Example_1_Simple_usage" src="https://mdn.mozillademos.org/en-US/docs/Web/API/Document/cookie$samples/Example_1_Simple_usage?revision=1652690" width="200"></iframe>

From a SameSite cookie perspective on chrome this means that cookies will not be sent by default (it will be set to Lax).
To fix this, first I'd try modifying the examples to add the SameSite as shown - e.g.
document.cookie = "name=oeschger; SameSite=None; Secure;";

That will probably work, but it is possible that the iframe itself will put further restrictions on calling this API (doesn't appear to on quick scan of docs).
@chrisdavidmills Where are the examples on https://mdn.mozillademos.org actually stored/specified? making the change above to add SameSite=None; Secure; would do "no harm" IMO, though there will need to be a note added in docs.

@hamishwillee that's a good question — I'm not really sure how to access those demos.
@escattone , do you how the answer to this?
I'd be in favor of moving those demos across to a repo somewhere under https://github.com/mdn/ at some point.

@chrisdavidmills I think @hamishwillee is right on here (thank you), but I probably won't be able to look into this in more detail until next week due to everything else going on for the launch of Yari a week from today.

@escattone Just a reminder, that this one is still a problem.

@escattone Just a reminder, that this one is still a problem.

Issue moved to mdn/yari #2579 via ZenHub

Issue moved to mdn/yari #2579 via ZenHub


Fix for writing the same allow list twice during agent activation

Addresses Issue #1146 -- failing tenant add with IMA in unusual circumstances (i.e. unreliable mysql connections, or when attempting to run the same tenant -c add command simultaneously from two different tenants).
Signed-off-by: George Almasi<EMAIL_ADDRESS>

Codecov Report

Merging #1150 (9bb07ee) into master (fc9f8bc) will increase coverage by 0.02%.
The diff coverage is 88.88%.

Additional details and impacted files

Flag
Coverage Δ

packit-e2e
72.45% <88.88%> (+0.02%)
:arrow_up:

testsuite
54.17% <88.88%> (+<0.01%)
:arrow_up:

unittests
14.60% <0.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

keylime/cmd/user_data_encrypt.py
38.46% <50.00%> (-4.40%)
:arrow_down:

keylime/ca_util.py
54.51% <100.00%> (ø)

keylime/cloud_verifier_tornado.py
67.25% <100.00%> (+0.07%)
:arrow_up:

keylime/crypto.py
93.39% <100.00%> (-0.19%)
:arrow_down:

keylime/registrar_common.py
59.38% <0.00%> (+0.92%)
:arrow_up:

For the too-many-nested-statements you can just add an ignore comment. The other changes LGTM, but some one else should also look at this before merging.

I agree with @THS-on . Add the ignore and a TODO to mark it. The fix in the first commit is direct, and the refactoring because of the complain is hiding it.
You can later split the rest in a different commit and remove the ignore. I will review also the second one (but I think that I get how you addressed it)

I was looking at the "nested" lint issue and found that the error condition handling in this function is all over the place -- some if statements defer failures to the end of the function, others return immediately.
I saw an opportunity for fixing the indentation issue by front-loading all failures and leaving the rest of the code unindented. But this results in 100+ lines changed for what was originally a 2 line PR.
In the end, it's a choice between a minimalistic semantic fix and a fairly large stylistic fix. You get to choose. If you don't like the latest evolution of the PR I start from scratch with the 2 lines that fix the actual problem.

FWIW even the 2 line semantic fix leaves out the fact that some variables are potentially undefined, depending on the path taken through the code. I would urge a serious review of this function (cloud_verifier_tornado::post) because there be dragons there. But I didn't want to broach the larger subject in this PR.

Al right @aplanas @THS-on I hear you. Going back to the 2-line fix with a lint exception soon(ish). Don't merge anything yet :)

@galmasi I agree that we should refactor this method to make it cleaner. So it  still makes sense to keep your commits and just put them into another PR. Ideally we get https://github.com/keylime/keylime/pull/1139 merged before which also addresses some of the issues.

I think the feeling among the reviewers was to minimize the disruption with this PR -- it's already had too long a life -- and postpone complex fixes.
Without troubling this PR any further, @maugustosilva @mdrocco and myself are finding issues related to operation of IMA at scale and against databases != sqlite. We don't want to hurry and make things worse. We are collecting data for opening a larger issue that can serve as a basis for fixes.

LGTM

To get rid of the test failure you will probably need to rebase on master.

Can you drop the merge commit and make a rebase? I think the history would be a bit more clear : ))
Otherwise LGTM

@aplanas  Dropped the merge and rebased instead.


Current pre-release installer crashes on CentOS

Our pre-release installer for 3.4.1 currently crashes on startup on CentOS
bash-4.2$ bin/vapor
vapor[0x45666f]
/lib64/libc.so.6(+0x36400)[0x2ac715414400]
/glade/u/apps/dav/opt/gnu/9.1.0/lib64/libstdc++.so.6(_ZNSsC2ERKSs+0xb)[0x2ac714bd028b]
vapor[0x4fb99d]
vapor[0x4fe289]
vapor[0x4fe888]
vapor[0x522540]
vapor[0x45f64d]
vapor[0x4b6dd4]
vapor[0x4b7606]
vapor[0x4a3c23]
vapor[0x4344df]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x2ac715400555]
vapor[0x436854]

Scott will provide an instruction on how to build VAPOR on Casper.

Hi @StasJ , could you help me fix the build on casper? I have fixed a few errors but there are json related errors that I don't know how to fix.
My WIP fix build branch is named fix_casper_build and you can feel free to keep working on this branch, or start your new branch.

Hi @StasJ , could you help me fix the build on casper? I have fixed a few errors but there are json related errors that I don't know how to fix.
My WIP fix build branch is named fix_casper_build and you can feel free to keep working on this branch, or start your new branch.

I fixed it.

My investigation goes into a dead end. Here's what I found:

Build from source works well.
3.4 release works well.
3.4.1 and weekly release encounter the reported problem
Generating an installer from source build encounters errors.

So, ideas needed on how to proceed.

@shaomeng a few thoughts that we may have already discussed earlier:

Build a debug installer and see if you can get a better stack trace. You'll probably need to tell dbx where to find the source code.
Run through valgrind
Divide and conquer: Place print statements in the code strategically to try to narrow down the problematic section of the code.

@shaomeng a few thoughts that we may have already discussed earlier:
1. Build a debug installer and see if you can get a better stack trace. You'll probably need to tell dbx where to find the source code.

2. Run through valgrind

3. Divide and conquer: Place print statements in the code strategically to try to narrow down the problematic section of the code.

Thanks for the suggestions. I have located the line where crash happens (https://github.com/NCAR/VAPOR/blob/ca61c4d4ca0f896dc3e3a2442e29356a8e76f5dc/apps/vaporgui/PWidget.cpp#L9) but the line seems fine to me. I now suspect that there are weird things going on with the specific build system, or the specific build process...

We may need to build on an older CentOS system. Perhaps we need to resurrect cisl-garibaldi, or maybe CircleCI has options for older OSes? We may need to wait for @sgpearse to return. Perhaps we should move on to testing

Well, I created a clean CentOS VM and using it I'm able to reproduce the issue with a local build. So, I can keep going for a while now.

Found a class initialization issue and submitted a PR. Hopefully in the future static analysis tools can detect errors like this (#2759).


tsc --version shows 1.5.3 after upgrade to 1.6?

Hello,
I have upgraded typescript to the latest 1.6 release by downloading the VS 2015 installation here: http://www.typescriptlang.org/#Download
However if I open up command prompt and do tsc --version I get 1.5.3

The reason I am suspecting this may be a problem is because when I have a tsconfig.json in my project:
{
  "compilerOptions": {
    "module": "AMD",
    "target": "ES5",
    "noImplicitAny": true,
    "removeComments": true,
    "preserveConstEnums": true,
    "sourceMap": true,
    "listFiles": true,
    "noEmitOnError": true,
    "outDir": "../wwwroot/dist",
      "outFile": "tscompiled.js"
  },
  "files": [
    "app.ts"
  ]
}

and this is the file
/// <reference path="../typings/tsd.d.ts" />
/// <reference path="../typings/es6.d.ts" />
/// <reference path="../typings/core-js.d.ts" />
import {Router} from "aurelia-router";

// my comment!
module Dazinator {
    export class App {
        constructor() {
            this.message = "Welcome To Daz's World ya!"
        }
        message: string;
    }
}

When I build the VS solution, I get an empty 'tscompiled.js' file produce - with a source mapping directive:
//# sourceMappingURL=tscompiled.js.map

If I do a compile form the command line it says it doesn't recognise the outFile argument
![image](https://cloud.githubusercontent.com/assets/3176632/10107159/19dbf5be-63b1-11e5-8ecc-c72709ecb3c9.png)

Looking at the docs - it says outFile is to be used as out is deprecated: https://github.com/Microsoft/TypeScript/wiki/Compiler-Options
Any help would be appreciated!

Doh - this is probably my stupidity.. I am knew to modules!
I am assuming the reason I am getting an empty file is because I am exporting a module - which basically means that the javascript for that module is loaded separately from a distinct js file at runtime and is therefore excluded from the out file that ts is producing - is that correct?

@dazinator Sort of. The target of --out (or --outFile) will get all globally scoped JavaScript in your project. Since your file above is a module (due to the import) that .ts file gets its own .js and then there's no other globally scoped JavaScript to put in your --out target file. We have an issue tracking making it an error when this occurs (an empty file from --out) since it's essentially always the error you've made and confuses people.

@dazinator the reason you are getting 1.5.3 after your TypeScript install is probably that your Visual Studio TypeScript installation has shadowed your npm directory. To fix it you probably need to change your PATH variable. To figure out where things are, open up CMD and type in where cmd

@danquirk - thank you for clarifying this for me :-)
@DanielRosenwasser - I will give that a try, cheers!

@DanielRosenwasser - this is the result of the where tsc

I don't understand though - shouldn't the installer for typescript (vs tools) 1.6 have updated the PATH appropriately?

I think that's a symptom of #2068.

The problem is the path is set as part of installing vs and not intalling typescript; obviously that does not work for updates. This is not the same as https://github.com/Microsoft/TypeScript/issues/2068 which we used to do in the 1.0 time but not since.
@paulvanbrenk is touching this area now, so hopefully we get a fix in next release.

work around just change environment path to new version

@alyahmedaly I don't have an entry in my PATH at all for Typescript. Can try adding one.. but it seems like VS is shadowing the path somehow anyway but will try!

there are two issues here:

path set to C:\program files (x86)\Microsoft SDKs\TypeScript\1.0 if you ever installed TypeScript 1.0, and not removed by further versions. the variable should be in your System Variables, and not in User Variables as shown in the above screenshot. Best way to find out is to use where tsc from a command prompt.
in VS command prompet, you always have the path pointing to C:\program files (x86)\Microsoft SDKs\TypeScript\1.5 even after updating to 1.6.  this environment variable is set in C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\VsDevCmd.bat, edit the file manually to replace:

@rem Add path to TypeScript Compiler
@if exist "%ProgramFiles%\Microsoft SDKs\TypeScript\1.5" set PATH=%ProgramFiles%\Microsoft SDKs\TypeScript\1.5;%PATH%
@if exist "%ProgramFiles(x86)%\Microsoft SDKs\TypeScript\1.5" set PATH=%ProgramFiles(x86)%\Microsoft SDKs\TypeScript\1.5;%PATH%

to
@rem Add path to TypeScript Compiler
@if exist "%ProgramFiles%\Microsoft SDKs\TypeScript\1.6" set PATH=%ProgramFiles%\Microsoft SDKs\TypeScript\1.6;%PATH%
@if exist "%ProgramFiles(x86)%\Microsoft SDKs\TypeScript\1.6" set PATH=%ProgramFiles(x86)%\Microsoft SDKs\TypeScript\1.6;%PATH%

This issue is tracking 2, for 1 please refer to  #2068.
hope that helps.

Yeah 2 is the relevant issue for me. Thanks for the workaround!

Note: Adding it to the %PATH% environment variable is not sufficient. Since C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\VsDevCmd.bat will override this when using the developer command prompt compared to regular cmd prompt. Manually Editing the file is essentially breaking support for patches when installing a patch. (If i am not mistaken, the file will not be overwritten for any new changes within the next update, unless there is a custom action within the installer which overrides the modified time stamp of the file). The change also needs to be present within visual studio installer as well.

Another option for issue 2 outlined by @mhegazy a few posts ago is to simply remove/comment the lines in question in VsDevCmd.bat. Note: this is NOT a good approach if you don't install typescript via npm. However, if you have installed typescript globally via "npm install typescript -g", removing/commenting the lines in question will allow the typescript path to resolve to your global node modules location.

@paulvanbrenk any fixes applicable for this due to the codenamed thing?

You mean low impact installer? No, that won't help much here.. I do think I have a solution, which I'll get in for 2.1

It did not

This path is set by vsdevcmd\ext\typescript.bat which is invoked indirectly by VsDevCmd.bat. After upgrading from 2.5 to 2.7 using the TypeScript SDK installer, the 2.5 path was left intact. I worked around the issue by updating this file.

The snippet that I used in typescript.bat is:
@echo [TEST:%~nx0] Checking for tsc...
where tsc > NUL 2>&1
if "%ERRORLEVEL%" EQU "0" (
    @echo [INFO:%~nx0] Existing tsc found
    goto end
)

It is based on the preexisting :test block. I put it near the top, right above the lines that check for the SDK-based installation of the TypeScript path.

This doesn't seem likely to still be relevant


Pure State file

a State file without PNG, reduce file size for some people
This mode
no State Picture preview

The .PNG statefiles are actually smaller than raw state files as they have compression.


unexpected EOF

when get http://autoproxy-gfwlist.googlecode.com/svn/trunk/gfwlist.txt through goproxy
,it gives unexpected EOF

I get this issue, when some website is not exists.
eg.  http://onlinedpianist.com/
My http proxy set a parent proxy with socks5


Update device name after OS Reload

For addressing tracker 134758781 , after reloading OS, there needs to update hostname based on the new VMPrefix name.
@maximilien This PR is based on @jianqiu PR 173, so please review/merge his PR first before reviewing this one. Thanks.

Guys, please squash the commits. All these small commits should merge into one or two commits. All these small ones only are noise. They add no values at all...

Again, merging to expedite things but we need to follow the guidelines. This will be the last BIG PR I merge. I am very serious. Next time I won't even look at it and reject.
/cc @mattcui @jianqiu @zhanggbj @gu-bin