profile
viewpoint

jbeder/yaml-cpp 2339

A YAML parser and emitter in C++

jbeder/fractran 14

Fractran interpreter in Fractran

jbeder/homebrew 1

The missing package manager for OS X.

jbeder/pdfsort 1

Sort a pdf that was created from two single-sided scans.

jbeder/yaml-cpp.new-api 1

Automatically exported from code.google.com/p/yaml-cpp.new-api

jbeder/airsonos 0

AirPlay to Sonos

jbeder/beancount 0

Beancount: Double-Entry Accounting from Text Files.

jbeder/javapoet 0

A Java API for generating .java source files.

jbeder/sh 0

Python process launching

jbeder/yaml-cpp.core 0

Automatically exported from code.google.com/p/yaml-cpp.core

startedjbeder/yaml-cpp

started time in 3 hours

fork 91social/yaml-cpp

A YAML parser and emitter in C++

fork in 11 hours

issue openedjbeder/yaml-cpp

Questions about static libraries

I built a static library of yaml, hoping to use it in VS2019, but I used it in the same way that I used the static library before, and prompted me "error LNK2038: mismatched item of "RuntimeLibrary" detected: value "MD_DynamicRelease" does not match value" MT_StaticRelease"", does anyone know why this is? I am sure I am using static library lib in the project。 I am using VS2019, windows10.

created time in 14 hours

startedjbeder/yaml-cpp

started time in 17 hours

startedjbeder/yaml-cpp

started time in a day

startedjbeder/yaml-cpp

started time in a day

fork ArthurWater/yaml-cpp

A YAML parser and emitter in C++

fork in a day

startedjbeder/yaml-cpp

started time in a day

startedjbeder/yaml-cpp

started time in a day

fork JamesStroebe/yaml-cpp

A YAML parser and emitter in C++

fork in a day

startedjbeder/yaml-cpp

started time in 2 days

startedjbeder/yaml-cpp

started time in 2 days

issue commentgoogle/dagger

Compiler errors on java 11

Update

So, in a successful build we would have:

  • Processing round 1
    • ModuleProcessingStep: Defers processing ApplicationModule (It references DataBindingComponent, which is not yet valid).
  • Processing round 2
    • ModuleProcessingStep: Processes ApplicationModule (DataBindingComponent is now valid -- generated in round 1)

However, in Java 11 with kapt something is going wrong.

In processing round 2, DataBindingComponent is not a valid type (even though DataBindingComponent appears to be generated at some point). This means that calling TypeMirror#getKind() on the type returns an ERROR kind rather than a DECLARED kind. Weirdly though, SuperficialValidation thinks the DataBindingComponent type is valid because rather than checking its TypeMirror#getKind(), it uses a TypeVisitor, which is incorrectly visiting #visitDeclared() even though the corresponding type is an ErrorType. I can't find specific documentation, but this definitely seems like another related bug, since I would expect it to visit #visitError() in this case.

So what does this mean for Dagger?

From Dagger's perspective, we initially think DataBindingComponent is valid in round 2 because of the bug in the visitor, so we go ahead and process ApplicationModule. Then, we realize the provides method is actually returning an ErrorType and we fail with the error message in https://github.com/google/dagger/issues/2144#issuecomment-712436284.

Again, I don't think there's much Dagger can really do in this case. We're relying on the underlying type system, so if the type is invalid we can't really make it valid. This appears to be a deeper issue between kapt and java 11.

You can try filing a bug with kapt, although I'm not sure if the project is still actively fixing issues.

You might also want to file a bug with the androidx.databinding library. For example, this doesn't seem to be a in issue with other generated types like AutoValue. For example:

@Module
class ApplicationModule {
  @AutoValue static abstract class Foo {}

  // This type is valid with kapt and java 11
  @Provides
  AutoValue_ApplicationModule_Foo provideFooAutoValue() {
      return new AutoValue_ApplicationModule_Foo();
  }

  // This type is invalid with kapt and java 11
  @Provides
  DataBindingComponent provideDataBindingComponent() {
      return new DataBindingComponent() {...};
  }
}

Possible Workarounds

  1. Avoid binding DataBindingComponent directly, and either extend or wrap it Instead (see https://github.com/google/dagger/issues/2144#issuecomment-731908754). However, note that this is really just a hack that relies on the fact that Dagger currently doesn't inspect the super types directly, but the underlying bug is still there and may cause issues later if Dagger starts relying on it.
  2. Avoid using kapt in this situation -- it works with annotationProcessor
  3. Avoid using java 11 in this situation -- it works with java 8.
auras

comment created time in 2 days

issue commentgoogle/dagger

Hilt: Question, How to reuse a module and provide its bindings

For anyone coming to this issue, the solution provided by @bcorso works with a bit of adjustment, since the injection has not happened yet, you will get an NPE exception if you access the fooWidgetListdataSource so you can't have @Inject annotation on it like @Inject FooWidgetListdataSource fooWidgetListdataSource; instead, you can access your dependence with an entry point interface

override val widgetListRepository: WidgetListRepository by lazy {
        EntryPoints.get(this, ManageEntryPoint::class.java).manageRepository()
    }

    @EntryPoint
    @InstallIn(FragmentComponent::class)
    interface ManageEntryPoint {

        @Named(MANAGE)
        fun manageRepository(): WidgetListRepository
    }
MRezaNasirloo

comment created time in 2 days

startedjbeder/yaml-cpp

started time in 2 days

issue openedjbeder/yaml-cpp

OSS-Fuzz integration

Hi

Given the popularity of Yaml-cpp I was thinking that it would be nice to set up continuous fuzzing of Yaml-cpp, by way of OSS-Fuzz. In this PR: https://github.com/google/oss-fuzz/pull/4713 I have done exactly that, namely created the necessary logic from an OSS-Fuzz perspective to integrate Yaml-cpp. This includes developing initial fuzzers as well as integrating into OSS-Fuzz.

Essentially, OSS-Fuzz is a free service run by Google that performs continuous fuzzing of important open source projects. The only expectation of integrating into OSS-Fuzz is that bugs will be fixed. This is not a "hard" requirement in that no one enforces this and the main point is if bugs are not fixed then it is a waste of resources to run the fuzzers, which we would like to avoid.

If you would like to integrate, could I please have an email(s) that will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats. Notice the emails affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.

David

created time in 2 days

delete branch google/dagger

delete branch : test_341659347

delete time in 2 days

push eventgoogle/dagger

Dagger Team

commit sha d67d2f6fc74a2c0129f198bba1cb36c98bdc4a97

[Hilt Documentation]: docs baseline 2 PiperOrigin-RevId: 344235493

view details

push time in 2 days

PR closed google/dagger

[Hilt Documentation]: docs baseline 2 cla: yes

[Hilt Documentation]: docs baseline 2

+0 -0

0 comment

0 changed file

copybara-service[bot]

pr closed time in 2 days

push eventgoogle/dagger

Dagger Team

commit sha d67d2f6fc74a2c0129f198bba1cb36c98bdc4a97

[Hilt Documentation]: docs baseline 2 PiperOrigin-RevId: 344235493

view details

push time in 2 days

create barnchgoogle/dagger

branch : test_341659347

created branch time in 2 days

PR opened google/dagger

[Hilt Documentation]: docs baseline 2

[Hilt Documentation]: docs baseline 2

+2 -2

0 comment

1 changed file

pr created time in 2 days

delete branch google/dagger

delete branch : test_344007461

delete time in 2 days

PR merged google/dagger

Internal change cla: yes

Internal change

+0 -0

0 comment

1 changed file

copybara-service[bot]

pr closed time in 2 days

push eventgoogle/dagger

Dagger Team

commit sha b7b842394fb9887eb52471477dad8028c4a5d922

Internal change PiperOrigin-RevId: 344215146

view details

push time in 2 days

push eventgoogle/dagger

Dagger Team

commit sha b7b842394fb9887eb52471477dad8028c4a5d922

Internal change PiperOrigin-RevId: 344215146

view details

push time in 2 days

push eventgoogle/dagger

Dagger Team

commit sha fb43cf16454538518468bdbcf3b15c0853439c1e

Internal change PiperOrigin-RevId: 344007461

view details

push time in 2 days

issue openedjbeder/yaml-cpp

Build error: undefined reference to vtalbe for YAML::BadConversion

I'm trying to compilate tkDNN

And I''m getting this error

This is the package version

created time in 2 days

fork fracassetti-stf/yaml-cpp

A YAML parser and emitter in C++

fork in 2 days

push eventgoogle/dagger

Dagger Team

commit sha 91cee55ce01d196afc844e4849e7a5ae1e9777a3

Internal change PiperOrigin-RevId: 344007461

view details

push time in 2 days

more