All workflows

Showing runs from all workflows

2500+ workflow runs

Reorganize adapters into a new DPSynth/adapters sub-directory (pure move).
completed successfully:
Google GitHub Admin: Actions Workflow Security Scan#661:Pull request#122synchronizebycopybara-service[bot]Bot
cl/961187766
Aug 12, 202641s
Reorganize adapters into a new DPSynth/adapters sub-directory (pure move).
completed successfully:
Unittests#746:Pull request#122synchronizebycopybara-service[bot]Bot
cl/961187766
Aug 12, 20265m 31s
Reorganize adapters into a new DPSynth/adapters sub-directory (pure move).
completed successfully:
GitHub Actions Scan#665:Pull request#122synchronizebycopybara-service[bot]Bot
Aug 12, 202616s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
completed successfully:
Unittests#745:Pull request#129synchronizebycopybara-service[bot]Bot
cl/963507541
Aug 12, 20264m 52s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
completed successfully:
Google GitHub Admin: Actions Workflow Security Scan#660:Pull request#129synchronizebycopybara-service[bot]Bot
cl/963507541
Aug 12, 202642s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
completed successfully:
GitHub Actions Scan#664:Pull request#129synchronizebycopybara-service[bot]Bot
Aug 12, 20269s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
completed successfully:
Google GitHub Admin: Actions Workflow Security Scan#659:Pull request#129synchronizebycopybara-service[bot]Bot
cl/963507541
Aug 12, 202646s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
failed:
Unittests#744:Pull request#129synchronizebycopybara-service[bot]Bot
cl/963507541
Aug 12, 20265m 7s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
completed successfully:
GitHub Actions Scan#663:Pull request#129synchronizebycopybara-service[bot]Bot
Aug 12, 202610s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
failed:
Unittests#743:Pull request#129synchronizebycopybara-service[bot]Bot
cl/963507541
Aug 12, 20265m 9s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
completed successfully:
Google GitHub Admin: Actions Workflow Security Scan#658:Pull request#129synchronizebycopybara-service[bot]Bot
cl/963507541
Aug 12, 202645s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
completed successfully:
GitHub Actions Scan#662:Pull request#129synchronizebycopybara-service[bot]Bot
Aug 12, 20269s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
completed successfully:
GitHub Actions Scan#661:Pull request#129openedbycopybara-service[bot]Bot
Aug 12, 20268s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
completed successfully:
Welcome First-Time Contributors#47:Pull request#129openedbycopybara-service[bot]Bot
Aug 12, 202621s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
completed successfully:
Google GitHub Admin: Actions Workflow Security Scan#657:Pull request#129openedbycopybara-service[bot]Bot
cl/963507541
Aug 12, 202654s
Remove DPMechanism boilerplate for primitives, keeping only the pure function numpy implementations. The DPMechanism abstraction is mainly useful to reason and allocate budget to a composition of different mechanisms. But these primitives are not used directly in the mechanism, only via the "Initializer" mechanisms. Hence they do not need to implement the DPMechanism protocol. This change quite significantly simplifies primitives.py, moving the appropriate dp event characterization logic directly to the appropriate Initializer.
cancelled:
Unittests#742:Pull request#129openedbycopybara-service[bot]Bot
cl/963507541
Aug 12, 20262m 8s
Add NestedTabularSynthesizer for typed/nested tabular data under dpsynth/google/research/activity_logs.
completed successfully:
Google GitHub Admin: Actions Workflow Security Scan#656:Pull request#83synchronizebycopybara-service[bot]Bot
cl/940786768
Aug 12, 202650s
Add NestedTabularSynthesizer for typed/nested tabular data under dpsynth/google/research/activity_logs.
completed successfully:
Unittests#741:Pull request#83synchronizebycopybara-service[bot]Bot
cl/940786768
Aug 12, 20264m 36s
Add NestedTabularSynthesizer for typed/nested tabular data under dpsynth/google/research/activity_logs.
completed successfully:
GitHub Actions Scan#660:Pull request#83synchronizebycopybara-service[bot]Bot
Aug 12, 20268s
Refactor DiscreteMechanism to use Composition instead of Inheritance.
completed successfully:
GitHub Actions Scan#659:Pull request#127synchronizebycopybara-service[bot]Bot
Aug 12, 202616s
Refactor DiscreteMechanism to use Composition instead of Inheritance.
completed successfully:
Google GitHub Admin: Actions Workflow Security Scan#655:Pull request#127synchronizebycopybara-service[bot]Bot
cl/962810453
Aug 12, 202643s
Refactor DiscreteMechanism to use Composition instead of Inheritance.
failed:
Unittests#740:Pull request#127synchronizebycopybara-service[bot]Bot
cl/962810453
Aug 12, 20262m 32s
Refactor domain YAML serialization to include explicit attribute types. For now, we only include type info when *saving* the domain information. When loading the domain information, we still match on type-specific fields for backwards compatibility with old YAML files. We log a clear warning with actionable advice (re-save the domain). In the future, we will match based on type and raise an error if the field doesn't exist.
completed successfully:
Unittests#739:Pull request#126synchronizebycopybara-service[bot]Bot
cl/962499647
Aug 12, 202626m 0s
Refactor domain YAML serialization to include explicit attribute types. For now, we only include type info when *saving* the domain information. When loading the domain information, we still match on type-specific fields for backwards compatibility with old YAML files. We log a clear warning with actionable advice (re-save the domain). In the future, we will match based on type and raise an error if the field doesn't exist.
completed successfully:
Google GitHub Admin: Actions Workflow Security Scan#654:Pull request#126synchronizebycopybara-service[bot]Bot
cl/962499647
Aug 12, 202643s
Refactor domain YAML serialization to include explicit attribute type…
cancelled:
Unittests#738:Commita8cc5a5pushedbycopybara-service[bot]Bot
main
Aug 12, 20263s

ProTip! You can narrow down the results and go further in time using the filter or the other filters available.