[svn:fx-trunk] 12962: Fix for ASDoc not saving event type for [Bindable] metadata tag

Revision: 12962
Revision: 12962
Author:   [email protected]
Date:     2009-12-15 10:32:23 -0800 (Tue, 15 Dec 2009)
Log Message:
Fix for ASDoc not saving event type for metadata tag
QE notes: None.
Doc notes: None
Bugs: SDK-24706
Reviewed By:Corey
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24706
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
Which correspondents fine with the
device "hw:0,3"
in my mpd.conf alsa section.
Also sound worked fine withh this config before I started installing ffmpeg-svn and alikes
hokasch:
I tried changing the mixer to "Master" but that did not change much.

Similar Messages

[svn:fx-trunk] 9336: Fix "ant asdoc" target

Revision: 9336
Author:   [email protected]
Date:     2009-08-14 20:20:44 -0700 (Fri, 14 Aug 2009)
Log Message:
Fix "ant asdoc" target
QE notes: None.
Doc notes: None
Tests run: checkintests
Is noteworthy for integration: No.
Modified Paths:
    flex/sdk/trunk/asdoc/build.xml

[svn:fx-trunk] 11999: Fixed: ASC-3889 - Using setting in a for loop causes Verify error

Revision: 11999
Revision: 11999
Author:   [email protected]
Date:     2009-11-19 11:37:09 -0800 (Thu, 19 Nov 2009)
Log Message:
Fixed: ASC-3889 - Using setting in a for loop causes Verify error
Notes: emit pop after callstatic to a void function to balance the stack.
Reviewer: jodyer+
Testing: asc,tamarin,flex checkin tests
Ticket Links:
    http://bugs.adobe.com/jira/browse/ASC-3889
Modified Paths:
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/semantics/CodeGenerator.java

Blacklisting the ahci module does indeed get rid of the error. Would be nice to figure out why it was conflicting with the ahci module though.
I have not yet tried the 173xx drivers, but the latest drivers for the Quadro FX 580 are the 256.53 drivers according to nvidia.
Posted at the nV forums (http://www.nvnews.net/vbulletin/showthread.php?t=155282), so we'll see what they suggest.

[svn:fx-trunk] 5802: Fix ant asdoc target to work with the new manifest files.

Revision: 5802
Author: [email protected]
Date: 2009-03-31 09:14:44 -0700 (Tue, 31 Mar 2009)
Log Message:
Fix ant asdoc target to work with the new manifest files.
QE Notes: None.
Doc Notes: None.
tests: checkintests
Modified Paths:
flex/sdk/trunk/asdoc/build.xml

Thats good news.

[svn:fx-trunk] 8706: Fix broken ASDoc comment

Revision: 8706
Author:   [email protected]
Date:     2009-07-21 06:35:30 -0700 (Tue, 21 Jul 2009)
Log Message:
Fix broken ASDoc comment
QE notes: -
Doc notes: -
Bugs: -
Reviewer: -
Tests run: - checkintests
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/core/FlexHTMLLoader.as
    flex/sdk/trunk/frameworks/projects/flash-integration/src/mx/flash/UIMovieClip.as

Welcome back everyone.
Hope you all had good holidays.
Cheers
glenn
tinylion development & design

[svn:fx-trunk] 7538: fix broken ASDoc comment

Revision: 7538
Author:   [email protected]
Date:     2009-06-03 13:51:37 -0700 (Wed, 03 Jun 2009)
Log Message:
fix broken ASDoc comment
QE Notes: None
Doc Notes: None
Bugs: -
Modified Paths:
    flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/ChannelSet.as

Welcome back everyone.
Hope you all had good holidays.
Cheers
glenn
tinylion development & design

[svn:fx-trunk] 5203: Fix broken ASDoc comment

Revision: 5203
Author: [email protected]
Date: 2009-03-08 11:43:31 -0700 (Sun, 08 Mar 2009)
Log Message:
Fix broken ASDoc comment
QE Notes: None
Doc Notes: None
Bugs: -
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/layout/LayoutBase.as

Welcome back everyone.
Hope you all had good holidays.
Cheers
glenn
tinylion development & design

[svn:fx-trunk] 5037: Fix broken ASDoc comments

Revision: 5037
Author: [email protected]
Date: 2009-02-23 07:29:40 -0800 (Mon, 23 Feb 2009)
Log Message:
Fix broken ASDoc comments
QE Notes: None
Doc Notes: None
Bugs: -
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/IGraphicElement.as

Welcome back everyone.
Hope you all had good holidays.
Cheers
glenn
tinylion development & design

[svn:fx-trunk] 5352: Fix ant asdoc target.

Revision: 5352
Author: [email protected]
Date: 2009-03-17 12:56:23 -0700 (Tue, 17 Mar 2009)
Log Message:
Fix ant asdoc target.
QE Notes: None.
Doc Notes: None.
tests: checkintests
Modified Paths:
flex/sdk/trunk/asdoc/build.xml
flex/sdk/trunk/frameworks/mxml-2009-manifest.xml

[svn:fx-trunk] 7795: fix locale names used in resource bundles for simplified Chinese and traditional Chinese .

Revision: 7795
Author:   [email protected]
Date:     2009-06-12 12:18:13 -0700 (Fri, 12 Jun 2009)
Log Message:
fix locale names used in resource bundles for simplified Chinese and traditional Chinese . zh_cn to zh_CN and zh_tw to zh_TW
bug: https://bugs.adobe.com/jira/browse/SDK-21174
qa: localization team (yes)
checkintests: pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21174
Modified Paths:
    flex/sdk/trunk/modules/compiler/build.xml

I'm more of a 1.3 chick myself, but the words are the same just in a different language.
1. Is Tomcat running?
2. Have you configured the ajp13 connector on 8009 in Tomcat? (Should it be ajp13 for Apache 2.0? - I really must upgrade)

[svn:fx-trunk] 11723: Fix broken ASDoc example

Revision: 11723
Author:   [email protected]
Date:     2009-11-12 12:50:17 -0800 (Thu, 12 Nov 2009)
Log Message:
Fix broken ASDoc example
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/asdoc/en_US/mx/effects/examples/AddItemActio nEffectExample.mxml

Welcome back everyone.
Hope you all had good holidays.
Cheers
glenn
tinylion development & design

[svn:fx-trunk] 6423: Fix broken ASDoc comment

Revision: 6423
Author: [email protected]
Date: 2009-04-30 10:11:43 -0700 (Thu, 30 Apr 2009)
Log Message:

Welcome back everyone.
Hope you all had good holidays.
Cheers
glenn
tinylion development & design

[svn:fx-trunk] 10230: Fix for ASDoc not handling img tag correctly

Revision: 10230
Author:   [email protected]
Date:     2009-09-14 08:54:44 -0700 (Mon, 14 Sep 2009)
Log Message:
Fix for ASDoc not handling tag correctly
QE notes: None.
Doc notes: None
Bugs: SDK-22902
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-22902
Modified Paths:
    flex/sdk/trunk/asdoc/templates/asdoc-util.xslt

Welcome back everyone.
Hope you all had good holidays.
Cheers
glenn
tinylion development & design

GEP is not of right type for indices! [Vivado HLS 2014.4, 2015.2, synthesis internal error]

[Vivado HLS 2014.4, 2015.2, synthesis internal error]
Hello,
I am randomly getting an error "GEP is not of right type for indices". (check the included files)
Some time it is presented as internal error sometimes GEP error appears.
If i reset vivado HLS error disappears dissapear and if i run synthesis again it works.
But problem is not the interface itself. Design is top big to share (and quite unusual with very specific needs). I would like to make a sample, but i don't know what error means and I don't know what causing the issue.
Did anyone met this error?
Does anyone have any idea what is causing the problem? (If i find out, I will make a samle. )
explanations for types in sources:
descrFifo_r and descrFifo_w are instances of Multififo and all arrays are defined with
#pragma HLS ARRAY_PARTITION variable=xx complete dim=1
multififo is implementation of multichannel fifo it to same block ram in one cycle only one channel can write and only one can make read request and only one can collect delayed data
It is tested and works in HW

Hello,
Thank you debrajr you gave me hope that that issue is fixable.
I removed associated ARRAY_PARTITION directives, it did not help.
I used script to remove all ARRAY_PARTITION directives and error seems to be the same.
So i tried to remove all the pragma and result is still same.
(If i compile my code, it runs with 0 Valgrind errors/warnings, so there is not pointer mismatch or any other problem of this kind, from c++ point of view, everythink seems to be OK)
But I found line, which causes the bug.
From some reason sometimes reading from MultiFifo<...>.bm_rd.dout fail with this error.
Today I found that sometimes I accidentaly read from very different output interface (not even connected with Multififo<>), I have fixed this section I did not met any synthesis errors for long time, that could mean that the issue was this impossible access on this interface.
Is there some way to let Vivado HLS write out all internal problems? Somethink like debugmod?
Is there way to write for example top 10 critical paths ? It would be really helpfull.
It tooks me nearly 3 days to debug this and this project is small (just ~1500 lines of code)....
Problem fixed for now.

I am comparing two documents. The "Not Responding" event happens for over 30 minutes.

I am comparing two documents using FM 11 on Windows 7. The "Not Responding" event happens for over 30 minutes. When should I force the application to quit?

It sounds like your installation is corrupted. I don't know what two checkmarks you mean, but when the Setup Assistant starts it collects some personal information after which it will return you to your normal Desktop. If it isn't doing that, then something is not right.
I think you will need to shut down the computer, then reboot. If you are able to reboot, then check About This Mac under the pple menu to see what version of OS X it shows is installed. If it shows 10.9.x then do the following:
Repair the Hard Drive and Permissions - Mavericks, Lion/Mountain Lion
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported then click on the Repair Permissions button. When the process is completed, then quit DU and return to the main menu. Select Restart from the Apple menu.

[svn:fx-trunk] 12962: Fix for ASDoc not saving event type for [Bindable] metadata tag

Similar Messages

Maybe you are looking for