{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":291368302,"defaultBranch":"master","name":"hcsshim","ownerLogin":"ambarve","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2020-08-29T23:56:44.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/57150885?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1714592533.0","currentOid":""},"activityList":{"items":[{"before":"59ed7b3a4edec7dbd6fdf0b8be016dc5aa023bed","after":"f88442dcf2f4d1c3cf45af3bd8ee969ac584d90b","ref":"refs/heads/blocked_cim_import","pushedAt":"2024-05-30T14:46:13.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"[WIP] Add support for mounting BlockCIM layers\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"[WIP] Add support for mounting BlockCIM layers"}},{"before":"d3ece5fc886225cda4832d408a41e034b2ada7ae","after":"de3d6955b1ed2e06c8391a0a45cd17afa350970d","ref":"refs/heads/cims_merged","pushedAt":"2024-05-27T04:42:44.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Add support for creating and mounting merged CIMs.\n\nCimFS supports merging CIMs and then mounting those merged CIMs as an alternative to creating forked\nCIMs. Advantage of merging CIMs that each CIM can be stored in its own directory. Unlike forked ICMs there is\nno requirement that all CIMs need to be present in the same directory. This commit adds the Go wrappers and\nsome tests for using the new CIM merging APIs.\n\nAlso, fixes a bug related to the return value of CimCloseImage API. This API has void return so we shouldn't\nbe returning anything in our wrapper.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Add support for creating and mounting merged CIMs."}},{"before":"99be46678faedfc84ac1f12f750f9a8fa143219a","after":"59ed7b3a4edec7dbd6fdf0b8be016dc5aa023bed","ref":"refs/heads/blocked_cim_import","pushedAt":"2024-05-20T21:57:25.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"[WIP] support for mounting merged CIMs for rootfs\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"[WIP] support for mounting merged CIMs for rootfs"}},{"before":"73c01f0bb7a10c843caa657d2ed013fb5b25431a","after":"d3ece5fc886225cda4832d408a41e034b2ada7ae","ref":"refs/heads/cims_merged","pushedAt":"2024-05-16T07:43:08.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Add support for creating and mounting merged CIMs.\n\nCimFS supports merging CIMs and then mounting those merged CIMs as an alternative to creating forked\nCIMs. Advantage of merging CIMs that each CIM can be stored in its own directory. Unlike forked ICMs there is\nno requirement that all CIMs need to be present in the same directory. This commit adds the Go wrappers and\nsome tests for using the new CIM merging APIs.\n\nAlso, fixes a bug related to the return value of CimCloseImage API. This API has void return so we shouldn't\nbe returning anything in our wrapper.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Add support for creating and mounting merged CIMs."}},{"before":null,"after":"ac73d94e9806d81f2f8dbe7967f246018abe4a26","ref":"refs/heads/layer_refactor_0.12","pushedAt":"2024-05-01T19:42:13.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Remove unused CimFS related code\n\nCimFS is currently not supported with HyperV isolation. However, we still have code that\nhandles processing of UtilityVM layer during image import. After the layer refactoring\nchange we need to update this code as well. But since this code isn't being used anywhere\nupdating it doesn't make much sense. There are no tests for this either. This code is\nremoved for now and we can add it back later once the plan for running HyperV isolated\ncontainers with CimFS is more solid.\n\nSigned-off-by: Amit Barve \n(cherry picked from commit e0c52cd23b414706ac630ce3d4c9651c3e74c146)\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Remove unused CimFS related code"}},{"before":"8d74e3206d24b9aafbfd868c8412f233e1a5d24d","after":"73c01f0bb7a10c843caa657d2ed013fb5b25431a","ref":"refs/heads/cims_merged","pushedAt":"2024-05-01T17:45:57.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Add support for creating and mounting merged CIMs.\n\nCimFS supports merging CIMs and then mounting those merged CIMs as an alternative to creating forked\nCIMs. Advantage of merging CIMs that each CIM can be stored in its own directory. Unlike forked ICMs there is\nno requirement that all CIMs need to be present in the same directory. This commit adds the Go wrappers and\nsome tests for using the new CIM merging APIs.\n\nAlso, fixes a bug related to the return value of CimCloseImage API. This API has void return so we shouldn't\nbe returning anything in our wrapper.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Add support for creating and mounting merged CIMs."}},{"before":"c211f7a0cbde645cb5ca25b3b05884010b0289a0","after":"8d74e3206d24b9aafbfd868c8412f233e1a5d24d","ref":"refs/heads/cims_merged","pushedAt":"2024-04-30T22:25:00.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Add support for creating and mounting merged CIMs.\n\nCimFS supports merging CIMs and then mounting those merged CIMs as an alternative to creating forked\nCIMs. Advantage of merging CIMs that each CIM can be stored in its own directory. Unlike forked ICMs there is\nno requirement that all CIMs need to be present in the same directory. This commit adds the Go wrappers and\nsome tests for using the new CIM merging APIs.\n\nAlso, fixes a bug related to the return value of CimCloseImage API. This API has void return so we shouldn't\nbe returning anything in our wrapper.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Add support for creating and mounting merged CIMs."}},{"before":"9ff1b0704f7544a4f2e71212682bd23af8c3dcb7","after":"c211f7a0cbde645cb5ca25b3b05884010b0289a0","ref":"refs/heads/cims_merged","pushedAt":"2024-04-30T21:47:46.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Add support for creating and mounting merged CIMs.\n\nCimFS supports merging CIMs and then mounting those merged CIMs as an alternative to creating forked\nCIMs. Advantage of merging CIMs that each CIM can be stored in its own directory. Unlike forked ICMs there is\nno requirement that all CIMs need to be present in the same directory. This commit adds the Go wrappers and\nsome tests for using the new CIM merging APIs.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Add support for creating and mounting merged CIMs."}},{"before":null,"after":"9ff1b0704f7544a4f2e71212682bd23af8c3dcb7","ref":"refs/heads/cims_merged","pushedAt":"2024-04-30T19:42:48.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Add support for creating and mounting merged CIMs.\n\nCimFS supports merging CIMs and then mounting those merged CIMs as an alternative to creating forked\nCIMs. Advantage of merging CIMs that each CIM can be stored in its own directory. Unlike forked ICMs there is\nno requirement that all CIMs need to be present in the same directory. This commit adds the Go wrappers and\nsome tests for using the new CIM merging APIs.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Add support for creating and mounting merged CIMs."}},{"before":"2d61b81d47347cf9b5b494a9f497f3f1423fc90b","after":"e0c52cd23b414706ac630ce3d4c9651c3e74c146","ref":"refs/heads/layer_refactor","pushedAt":"2024-03-26T20:57:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Remove unused CimFS related code\n\nCimFS is currently not supported with HyperV isolation. However, we still have code that\nhandles processing of UtilityVM layer during image import. After the layer refactoring\nchange we need to update this code as well. But since this code isn't being used anywhere\nupdating it doesn't make much sense. There are no tests for this either. This code is\nremoved for now and we can add it back later once the plan for running HyperV isolated\ncontainers with CimFS is more solid.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Remove unused CimFS related code"}},{"before":"a3d1b934d258d667461a1ffc682dbb03ee7afb55","after":"2d61b81d47347cf9b5b494a9f497f3f1423fc90b","ref":"refs/heads/layer_refactor","pushedAt":"2024-03-26T17:47:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Remove unused CimFS related code\n\nCimFS is currently not supported with HyperV isolation. However, we still have code that\nhandles processing of UtilityVM layer during image import. After the layer refactoring\nchange we need to update this code as well. But since this code isn't being used anywhere\nupdating it doesn't make much sense. There are no tests for this either. This code is\nremoved for now and we can add it back later once the plan for running HyperV isolated\ncontainers with CimFS is more solid.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Remove unused CimFS related code"}},{"before":null,"after":"99be46678faedfc84ac1f12f750f9a8fa143219a","ref":"refs/heads/blocked_cim_import","pushedAt":"2024-03-20T21:59:11.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"[WIP] support for importing layers into blocked CIM format\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"[WIP] support for importing layers into blocked CIM format"}},{"before":"b914759b5b6ed833ca00a31f2c1f9792351492b0","after":"a3d1b934d258d667461a1ffc682dbb03ee7afb55","ref":"refs/heads/layer_refactor","pushedAt":"2024-03-18T00:35:10.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Remove unused CimFS related code\n\nCimFS is currently not supported with HyperV isolation. However, we still have code that\nhandles processing of UtilityVM layer during image import. After the layer refactoring\nchange we need to update this code as well. But since this code isn't being used anywhere\nupdating it doesn't make much sense. There are no tests for this either. This code is\nremoved for now and we can add it back later once the plan for running HyperV isolated\ncontainers with CimFS is more solid.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Remove unused CimFS related code"}},{"before":"5e3ccbe118ba0ff536e610a7ab3db0acc6237168","after":"b914759b5b6ed833ca00a31f2c1f9792351492b0","ref":"refs/heads/layer_refactor","pushedAt":"2024-03-14T21:33:13.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Remove unused CimFS related code\n\nCimFS is currently not supported with HyperV isolation. However, we still have code that\nhandles processing of UtilityVM layer during image import. After the layer refactoring\nchange we need to update this code as well. But since this code isn't being used anywhere\nupdating it doesn't make much sense. There are no tests for this either. This code is\nremoved for now and we can add it back later once the plan for running HyperV isolated\ncontainers with CimFS is more solid.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Remove unused CimFS related code"}},{"before":"e9720ad9ecd408c6a175482c497f290ad2319d19","after":"5e3ccbe118ba0ff536e610a7ab3db0acc6237168","ref":"refs/heads/layer_refactor","pushedAt":"2024-03-14T21:03:02.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Remove unused CimFS related code\n\nCimFS is currently not supported with HyperV isolation. However, we still have code that\nhandles processing of UtilityVM layer during image import. After the layer refactoring\nchange we need to update this code as well. But since this code isn't being used anywhere\nupdating it doesn't make much sense. There are no tests for this either. This code is\nremoved for now and we can add it back later once the plan for running HyperV isolated\ncontainers with CimFS is more solid.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Remove unused CimFS related code"}},{"before":"6c17a7a03d62f55f045f96de7044087131725258","after":"e9720ad9ecd408c6a175482c497f290ad2319d19","ref":"refs/heads/layer_refactor","pushedAt":"2024-03-08T07:36:20.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Remove unused CimFS related code\n\nCimFS is currently not supported with HyperV isolation. However, we still have code that\nhandles processing of UtilityVM layer during image import. After the layer refactoring\nchange we need to update this code as well. But since this code isn't being used anywhere\nupdating it doesn't make much sense. There are no tests for this either. This code is\nremoved for now and we can add it back later once the plan for running HyperV isolated\ncontainers with CimFS is more solid.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Remove unused CimFS related code"}},{"before":"3eac324dc6cc05b332357f86c1e16fce3756349e","after":"6c17a7a03d62f55f045f96de7044087131725258","ref":"refs/heads/layer_refactor","pushedAt":"2024-03-08T07:04:43.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Remove unused CimFS related code\n\nCimFS is currently not supported with HyperV isolation. However, we still have code that\nhandles processing of UtilityVM layer during image import. After the layer refactoring\nchange we need to update this code as well. But since this code isn't being used anywhere\nupdating it doesn't make much sense. There are no tests for this either. This code is\nremoved for now and we can add it back later once the plan for running HyperV isolated\ncontainers with CimFS is more solid.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Remove unused CimFS related code"}},{"before":"01f7ab819eccdca6173b6a5a1d829ef5f7323a92","after":"3eac324dc6cc05b332357f86c1e16fce3756349e","ref":"refs/heads/layer_refactor","pushedAt":"2024-03-08T06:35:55.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Remove unused CimFS related code\n\nCimFS is currently not supported with HyperV isolation. However, we still have code that\nhandles processing of UtilityVM layer during image import. After the layer refactoring\nchange we need to update this code as well. But since this code isn't being used anywhere\nupdating it doesn't make much sense. There are no tests for this either. This code is\nremoved for now and we can add it back later once the plan for running HyperV isolated\ncontainers with CimFS is more solid.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Remove unused CimFS related code"}},{"before":"1ef7cc68ab122e69efe40cb1ceaa62d859b5e2b2","after":"01f7ab819eccdca6173b6a5a1d829ef5f7323a92","ref":"refs/heads/layer_refactor","pushedAt":"2024-03-05T18:38:59.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Remove unused CimFS related code\n\nCimFS is currently not supported with HyperV isolation. However, we still have code that\nhandles processing of UtilityVM layer during image import. After the layer refactoring\nchange we need to update this code as well. But since this code isn't being used anywhere\nupdating it doesn't make much sense. There are no tests for this either. This code is\nremoved for now and we can add it back later once the plan for running HyperV isolated\ncontainers with CimFS is more solid.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Remove unused CimFS related code"}},{"before":"67b8035cb3a0478e158e79aad95f84adf33dc4da","after":"1ef7cc68ab122e69efe40cb1ceaa62d859b5e2b2","ref":"refs/heads/layer_refactor","pushedAt":"2024-03-05T18:21:02.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Remove unused CimFS related code\n\nCimFS is currently not supported with HyperV isolation. However, we still have code that\nhandles processing of UtilityVM layer during image import. After the layer refactoring\nchange we need to update this code as well. But since this code isn't being used anywhere\nupdating it doesn't make much sense. There are no tests for this either. This code is\nremoved for now and we can add it back later once the plan for running HyperV isolated\ncontainers with CimFS is more solid.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Remove unused CimFS related code"}},{"before":"388d8c01856d10770a21c19e84401013e921ffde","after":"67b8035cb3a0478e158e79aad95f84adf33dc4da","ref":"refs/heads/layer_refactor","pushedAt":"2024-02-28T23:45:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Refactor layer writer interface\n\nCurrent layer writer interface forces us to calculate the CIM path from the layer path by\nmaking assumptions about CIM storage. This isn't a very good approach, better way is to be\nexplicit about what information the layer writer needs from containerd. This change\nupdates the CIM layer writer to take in layer CIM & parent CIM paths as inputs. This also\nmeans a corresponding changes needs to be made in containerd.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Refactor layer writer interface"}},{"before":"2be3efdc28517b71ad738e9eb0054e823dc1ef18","after":"388d8c01856d10770a21c19e84401013e921ffde","ref":"refs/heads/layer_refactor","pushedAt":"2024-02-28T22:29:08.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Refactor layer writer interface\n\nCurrent layer writer interface forces us to calculate the CIM path from the layer path by\nmaking assumptions about CIM storage. This isn't a very good approach, better way is to be\nexplicit about what information the layer writer needs from containerd. This change\nupdates the CIM layer writer to take in layer CIM & parent CIM paths as inputs. This also\nmeans a corresponding changes needs to be made in containerd.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Refactor layer writer interface"}},{"before":"f758362f5248e921ecd1e53c1231d0f6077e122b","after":"2be3efdc28517b71ad738e9eb0054e823dc1ef18","ref":"refs/heads/layer_refactor","pushedAt":"2024-02-28T22:10:54.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Refactor layer writer interface\n\nCurrent layer writer interface forces us to calculate the CIM path from the layer path by\nmaking assumptions about CIM storage. This isn't a very good approach, better way is to be\nexplicit about what information the layer writer needs from containerd. This change\nupdates the CIM layer writer to take in layer CIM & parent CIM paths as inputs. This also\nmeans a corresponding changes needs to be made in containerd.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Refactor layer writer interface"}},{"before":"7d729e5395ed76c77ba648dafeae4f8be8659010","after":"f758362f5248e921ecd1e53c1231d0f6077e122b","ref":"refs/heads/layer_refactor","pushedAt":"2024-02-28T21:48:54.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Refactor layer writer interface\n\nCurrent layer writer interface forces us to calculate the CIM path from the layer path by\nmaking assumptions about CIM storage. This isn't a very good approach, better way is to be\nexplicit about what information the layer writer needs from containerd. This change\nupdates the CIM layer writer to take in layer CIM & parent CIM paths as inputs. This also\nmeans a corresponding changes needs to be made in containerd.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Refactor layer writer interface"}},{"before":"8bb7864dc735f61384d1d004569fdf2b3222836a","after":"7d729e5395ed76c77ba648dafeae4f8be8659010","ref":"refs/heads/layer_refactor","pushedAt":"2024-02-27T19:39:33.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Refactor layer writer interface\n\nCurrent layer writer interface forces us to calculate the CIM path from the layer path by\nmaking assumptions about CIM storage. This isn't a very good approach, better way is to be\nexplicit about what information the layer writer needs from containerd. This change\nupdates the CIM layer writer to take in layer CIM & parent CIM paths as inputs. This also\nmeans a corresponding changes needs to be made in containerd.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Refactor layer writer interface"}},{"before":"dfbeea369b1007a1894410be5ae406ff99f55a9e","after":"8bb7864dc735f61384d1d004569fdf2b3222836a","ref":"refs/heads/layer_refactor","pushedAt":"2024-02-27T19:29:02.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Refactor layer writer interface\n\nCurrent layer writer interface forces us to calculate the CIM path from the layer path by\nmaking assumptions about CIM storage. This isn't a very good approach, better way is to be\nexplicit about what information the layer writer needs from containerd. This change\nupdates the CIM layer writer to take in layer CIM & parent CIM paths as inputs. This also\nmeans a corresponding changes needs to be made in containerd.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Refactor layer writer interface"}},{"before":"ae464d243477d8246a7224cb14cd76e9381b54d2","after":"dfbeea369b1007a1894410be5ae406ff99f55a9e","ref":"refs/heads/layer_refactor","pushedAt":"2024-02-27T19:04:28.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Refactor layer writer interface\n\nCurrent layer writer interface forces us to calculate the CIM path from the layer path by\nmaking assumptions about CIM storage. This isn't a very good approach, better way is to be\nexplicit about what information the layer writer needs from containerd. This change\nupdates the CIM layer writer to take in layer CIM & parent CIM paths as inputs. This also\nmeans a corresponding changes needs to be made in containerd.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Refactor layer writer interface"}},{"before":"2963edb487f7a0a1abe3868cbf1f5fe7a2ca284d","after":"ae464d243477d8246a7224cb14cd76e9381b54d2","ref":"refs/heads/layer_refactor","pushedAt":"2024-02-27T17:17:18.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"[WIP] All Layer refactor\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"[WIP] All Layer refactor"}},{"before":"e9af6a5adf6a2dce23e9aeb2ed03693275afbb2d","after":"2963edb487f7a0a1abe3868cbf1f5fe7a2ca284d","ref":"refs/heads/layer_refactor","pushedAt":"2024-02-23T01:57:42.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Update import CIM layer interface\n\nUpdates the import CIM layer functions to take the layer CIM path & parent layer CIM Paths as an explicit\nargument instead of generating those paths from layer paths.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Update import CIM layer interface"}},{"before":"b66f83b363d69c12ac60f3d3c7a41f13f40296af","after":"e9af6a5adf6a2dce23e9aeb2ed03693275afbb2d","ref":"refs/heads/layer_refactor","pushedAt":"2024-02-23T01:39:31.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"ambarve","name":"Amit Barve","path":"/ambarve","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/57150885?s=80&v=4"},"commit":{"message":"Update import CIM layer interface\n\nUpdates the import CIM layer functions to take the layer CIM path & parent layer CIM Paths as an explicit\nargument instead of generating those paths from layer paths.\n\nSigned-off-by: Amit Barve ","shortMessageHtmlLink":"Update import CIM layer interface"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEWCEmTAA","startCursor":null,"endCursor":null}},"title":"Activity ยท ambarve/hcsshim"}