pdxjohnny

GitHub Webhook Events

Sample JSON files

$ python webhook_event_logger.py -R pdxjohnny/scitt-api-emulator

pdxjohnny

diff --git a/scitt_emulator/ccf.py b/scitt_emulator/ccf.py
index 06296f8..452c801 100644
--- a/scitt_emulator/ccf.py
+++ b/scitt_emulator/ccf.py
@@ -78,13 +78,13 @@ class CCFSCITTServiceEmulator(SCITTServiceEmulator):
         key = jwcrypto.jwk.JWK()
         key_bytes = pathlib.Path(self._service_private_key_path).read_bytes()
         key.import_from_pem(key_bytes)
-        return [
-            {

pdxjohnny

r"""
## 2023-04-19 @pdxjohnny Engineering Logs

- https://github.com/digitalbazaar/pyld
- SECURITY Unmaintained since Aug 6th 2020
- `jsonld.set_document_loader(jsonld.aiohttp_document_loader(timeout=...))`
- https://github.com/wolfi-dev/os/commit/40c24089d4a16c594d3e30c4c232e14fa18ce6e2
  - nats for guac
- node 20 enables the binary packaging we wanted for activitypub starter kit

pdxjohnny

# Updated version: https://github.com/intel/Multi-llms-Chatbot-CloudNative-LangChain/blob/1bd6a844ebc57245f9fba8e7a87cde489cc4734d/2__LLMs_Proxy/server.py#L12-L34
import pathlib
from pprint import pprint

import yaml
import kubernetes
import kubernetes.client
from kubernetes.client.rest import ApiException
from kubernetes import client, config

pdxjohnny

Alice Omega Alpha

Entities working on Alice use thread intel/dffml#1406 as a way to communicate to others what you are working on. Each day has a log entry. Comment with your thoughts, activities, planning, etc. related to the development of Alice, our open source artificial general intelligence.

The thread is used as a communication mechanism for engineers so that others can have full context around why entities did what they did during their development process. This development lifecycle data helps

pdxjohnny

.terraform/
*.pem
*.tf
*.tfstate
*.yaml
*.backup
istio-*/
cert-manager-*/
*.swp
env

pdxjohnny

Rolling Alice: Progress Report 1: Where are we

https://www.youtube.com/watch?v=dI1oGv7K21A&list=PLtzAOVTpO2jYt71umwc-ze6OmwwCIMnLw

Okay, so we are going to do our series of tutorials on building Alice, our software architect. And so as a part of that we're going to do a bunch of engineering log videos, just the same as we do the weekly sync stuff. So this is going to be not like the weekly sync where we do, you know, it's more of like an office hours. This is more of, you know, whoever's working on something will stream what they're working on so that there's, you know, basically like you can

pdxjohnny

DSSE (Digital Signature over Software Artifacts) and COSE (CBOR Object Signing and Encryption) are both specifications that deal with securing the integrity of data, but they serve slightly different purposes and are used in different contexts.

1. DSSE (Digital Signature over Software Artifacts):

   • DSSE is a specification designed to enable the secure signing of a variety of software artifacts, such as binaries, container images, and software bill of materials (SBOMs).
   • It aims to provide a single, flexible, and secure signature format for these artifacts.
   • DSSE is often used in the context of software supply chain security.
   • It is not tied to a specific serialization format and can be used with JSON, Protobuf, or any other format of the user’s choice.
   • DSSE is designed to be agnostic of the key management system or public key infrastructure (PKI) being used.

2. COSE (CBOR Object Signing and Encryption):

pdxjohnny

{
  "body": "These are the engineering logs of entities working on Alice. If you\r\nwork on [Alice](https://github.com/intel/dffml/tree/alice/docs/tutorials/rolling_alice/0000_architecting_alice#what-is-alice) please use this thread as a way to communicate to others\r\nwhat you are working on. Each day has a log entry. Comment with your\r\nthoughts, activities, planning, etc. related to the development of\r\nAlice, our open source artificial general intelligence.\r\n\r\nThis thread is used as a communication mechanism for engineers so that\r\nothers can have full context around why entities did what they did\r\nduring their development process. This development lifecycle data helps\r\nus understand more about why decisions were made when we re-read the\r\ncode in the future (via cross referencing commit dates with dates in\r\nengineering logs). In this way we facilitate communication across\r\nboth time and space! Simply by writing things down. We live an an\r\nasynchronous world. Let's communicate like it.\r

pdxjohnny

{
  "body": "These are the engineering logs of entities working on Alice. If you\r\nwork on [Alice](https://github.com/intel/dffml/tree/alice/docs/tutorials/rolling_alice/0000_architecting_alice#what-is-alice) please use this thread as a way to communicate to others\r\nwhat you are working on. Each day has a log entry. Comment with your\r\nthoughts, activities, planning, etc. related to the development of\r\nAlice, our open source artificial general intelligence.\r\n\r\nThis thread is used as a communication mechanism for engineers so that\r\nothers can have full context around why entities did what they did\r\nduring their development process. This development lifecycle data helps\r\nus understand more about why decisions were made when we re-read the\r\ncode in the future (via cross referencing commit dates with dates in\r\nengineering logs). In this way we facilitate communication across\r\nboth time and space! Simply by writing things down. We live an an\r\nasynchronous world. Let's communicate like it.\r