zz.007
zz.007
// allocate不一定>=8个字节吧?可能抛异常,没影响么 ByteBuffer byteBuffer = ByteBuffer.allocate(mappedFile.getFileSize() - mappedFile.getWrotePosition()); byteBuffer.putInt(BLANK_MAGIC_CODE); byteBuffer.putInt(mappedFile.getFileSize() - mappedFile.getWrotePosition()); ```if (len + blank > mappedFile.getFileSize() - mappedFile.getWrotePosition()) { if (blank < MIN_BLANK_LEN) { logger.error("Blank {} should ge...
- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate. ### Ⅰ. Issue Description saga模式下加载DefaultResourceManager的initResourceManagers()方法中,EnhancedServiceLoader会默认以兼容模式同时加载org.apache和io.seata下的SataResourceManager, 也就是SAGA指向两个Manager,但添加到resourceManagers中被覆盖了只添加io.seata下的对象,导致org.apache和io.seata混乱。 ``` protected void initResourceManagers() {...
## Question When I start a sample with shadow feature, it complains 'Table not exist', are there some configs that i'm missing or making wrong? version: 5.5.0 shadow config: config.yaml...
## Question There's no official sample of this kind, I have configured the following but can't rollback, so could anyone provide a sample? thx. shardingsphere: 5.5.0 seata: 2.1.0 ``` ......
## Question shardingsphere: 5.5.0 config.yaml: ``` rules: - !SINGLE tables: - "*.*" - !SHADOW dataSources: shadowDataSource: productionDataSourceName: ds shadowDataSourceName: ds_shadow tables: t_user: dataSourceNames: - shadowDataSource shadowAlgorithmNames: - user_id_insert_match_algorithm - user_id_delete_match_algorithm...