search for: yaml

...:: elf/Mips/got16-2.test lld :: elf/Mips/got16-micro.test lld :: elf/Mips/got-page-32-micro.test lld :: elf/Mips/got-page-64-micro.test lld :: elf/Mips/got-page-64.test lld :: elf/X86_64/sectionchoice.test lld :: elf/X86_64/sectionmap.test lld :: mach-o/arm-interworking.yaml lld :: mach-o/arm-shims.yaml lld :: mach-o/data-only-dylib.yaml lld :: mach-o/executable-exports.yaml lld :: mach-o/exe-offsets.yaml lld :: mach-o/exported_symbols_list-undef.yaml lld :: mach-o/fat-archive.yaml lld :: mach-o/flat_namespace_undef_error.yaml lld :: mac...

.../Mips/got16-2.test > lld :: elf/Mips/got16-micro.test > lld :: elf/Mips/got-page-32-micro.test > lld :: elf/Mips/got-page-64-micro.test > lld :: elf/Mips/got-page-64.test > lld :: elf/X86_64/sectionchoice.test > lld :: elf/X86_64/sectionmap.test > lld :: mach-o/arm-interworking.yaml > lld :: mach-o/arm-shims.yaml > lld :: mach-o/data-only-dylib.yaml > lld :: mach-o/executable-exports.yaml > lld :: mach-o/exe-offsets.yaml > lld :: mach-o/exported_symbols_list-undef.yaml > lld :: mach-o/fat-archive.yaml > lld :: mach-o/flat_namespace_undef_error.yaml > ll...

...cro.test >> lld :: elf/Mips/got-page-32-micro.test >> lld :: elf/Mips/got-page-64-micro.test >> lld :: elf/Mips/got-page-64.test >> lld :: elf/X86_64/sectionchoice.test >> lld :: elf/X86_64/sectionmap.test >> lld :: mach-o/arm-interworking.yaml >> lld :: mach-o/arm-shims.yaml >> lld :: mach-o/data-only-dylib.yaml >> lld :: mach-o/executable-exports.yaml >> lld :: mach-o/exe-offsets.yaml >> lld :: mach-o/exported_symbols_list-undef.yaml >> lld :: mach-o/fat-archive.yaml >>...

Hi Rui, et al., I was experimenting yesterday with building lld on my POWER7 PPC64/Linux machine, and ran into an unfortunate problem. When running the regressions tests under lit, almost all of the tests fail like this: terminate called after throwing an instance of 'std::system_error' what(): Resource temporarily unavailable ... 5 libc.so.6 0x00000080b7847238 abort +

I've been working on reading and writing yaml encoded documents for the lld project. Michael Spencer added the YAMLParser.h functionality to llvm/Support to help in parsing yaml documents. That parser greatly helps at the syntax level, but you still need to hand write a lot of semantic checking and then convert the various node types in to s...

So something doesn''t look right for me when running puppet apply -e ''include ...'' for looking heria via facter fact. I have hiera configure as this, :backends: - yaml :hierarchy: - common - ''%{env_name}'' :yaml: :datadir: /var/lib/hiera/data and, a file envXX.yaml store in the datadir, and I can run *hiera xyz env_name=envXX* to get the the value of abc associate with xyz. Yet, if I export the value variable...

Hi, I am trying to use Hiera in puppet 3 and I have two nodes that both need the same configuration. In this case they are two web servers which have the same apache configuration. Rather than creating two seperate hiera files for node1.yaml and node2.yaml is there a way to group these by role (e.g. webserver.yaml)? I want to avoid duplicating the configuration if possible and keep the data in hiera. Thanks! Joe -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscr...

On Oct 22, 2012, at 5:07 PM, Nick Kledzik wrote: > On Oct 22, 2012, at 4:40 PM, Sean Silva wrote: >> Hey Nick, what's the status on YAML IO? The other thread seems to have died. > > I'm waiting on Michael Spencer's feedback. To better understand how a client would use YAML I/O. I've completely rewritten the ReaderYAML and WriterYAML in lld to use YAML I/O. The source code is now about half the size. But more...

...>> thinking if we should have a vector of Readers, and have a function >> isMyFormat in each of them. >> >> Any reader that knows to handle, goes ahead and parses the file. >> >> On a side note, we currently use .objtxt as an figure out if the file is >> a YAML file or not. I have added FIXME's in the code, if we could some kind >> of magic (or) a better way to figure out if the file is YAML ? >> >> Thanks >> >> Shankar Easwaran >> >> -- >> Qualcomm Innovation Center, Inc. is a member of Code Aurora Foru...

...000Z" => true *Directory structure* [root@puppet-dev puppet]# tree /etc/puppet/environments/ -d -L 2 /etc/puppet/environments/ ├── development │ ├── hieradata │ └── modules └── production ├── hieradata └── modules *Configuration file* [root@puppet-dev puppet]# cat /etc/hiera.yaml --- :hierarchy: - %{environment} - %{operatingsystem} - common :backends: - yaml :yaml: :datadir: ''/etc/puppet/environments/%{environment}/hieradata/'' *Test manifest* class hiera_test { $packages = hiera(''sshpackages'') notify { $pa...

> To better understand how a client would use YAML I/O. I've completely rewritten the ReaderYAML and WriterYAML in lld to use YAML I/O. The source code is now about half the size. But more importantly, the error checking is much, much better and any time an attribute (e.g. of an Atom) is changed or added, there is just one place to update t...

I am working on building a facter tag based node classifier similar to https://github.com/jordansissel/puppet-examples/tree/master/nodeless-puppet/. However, I have run into an issue where I cannot use puppet''s require file ability to push the yaml file containing the facts file to the client because it would require two runs of puppet to pickup changes. Consequently, I have written into the facter ruby script the ability to connect to puppet''s restful api and get the yaml file from the private store. This works fine in irb, ruby, an...

Michael, To validate the refactor of YAML Reader/Writer using YAML I/O. I updated all the test cases to be compatible with YAML I/O. One issue that was a gnarly was how to handle the test cases with archives. Currently, we have test cases like: --- atoms: - name: foo # more stuff --- archive: - name bar.o atoms:...

...should have a vector of Readers, and have a function >>> isMyFormat in each of them. >>> >>> Any reader that knows to handle, goes ahead and parses the file. >>> >>> On a side note, we currently use .objtxt as an figure out if the file is >>> a YAML file or not. I have added FIXME's in the code, if we could some kind >>> of magic (or) a better way to figure out if the file is YAML ? >>> >>> Thanks >>> >>> Shankar Easwaran >>> >>> -- >>> Qualcomm Innovation Center, Inc....

I figured I''d post here before submitting a ticket, but I''m seeing some confusing stuff when dealing with YAML now. I was using it to freeze objects in my database, and so i had some data already around to mess with. I upgraded both Ruby (1.8.3 -> 1.8.4) and Rails ( -> 1.1RC1) and this junk started. I''ve outlined the problem in two pastes, which I''ll paste below. ----1 ### This...

...Readers, and have a function >>>> isMyFormat in each of them. >>>> >>>> Any reader that knows to handle, goes ahead and parses the file. >>>> >>>> On a side note, we currently use .objtxt as an figure out if the file is >>>> a YAML file or not. I have added FIXME's in the code, if we could some >>>> kind >>>> of magic (or) a better way to figure out if the file is YAML ? >>>> >>>> Thanks >>>> >>>> Shankar Easwaran >>>> >>>> --...

So I talked with Shankar on IRC on this topic, and here's a suggestion. 1. Use a magic comment to determine if it's a YAML file. I'd propose "#!obj" as a YAML file magic because of similarity of Unix shebang. YAML reader skips this first line because it's a comment line in YAML grammar. 2. Add "target" field to YAML to represent what machine type the object type represents. For example, if...

Has anyone else ran into this? debug: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content: Executing ''diff -u /var/tmp/facts.yaml /tmp/puppet-file20121214-13448-933j3r-0'' notice: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content: --- /var/tmp/facts.yaml 2012-12-14 00:53:20.000000000 +0000 +++ /tmp/puppet-file20121214-13448-933j3r-0 2012-12-14 00:55...

Hi Nick, I had a few questions :- 1) Is there a way to validate that the input file is of a valid format, thats defined by the YAML Reader ? 2) How are you plannning to represent section groups in the YAML ? 3) How are you planning to support Atom specific flags ? Is there a way already ? (This would be needed to group similiar atoms together) 4) Are you planning to support representing shared libraries too in this model...

# is a line comment chracter in YAML so it's valid. That's why I wrote a simple magic "comment". On Thu, Oct 10, 2013 at 6:21 PM, Shankar Easwaran <shankare at codeaurora.org>wrote: > On 10/10/2013 5:00 PM, Rui Ueyama wrote: > >> On Thu, Oct 10, 2013 at 9:16 AM, Shankar Easwaran >> <shan...