Can't import the named export 'useState' from non EcmaScript module (only default export is available) Can't import the named export 'useState' from non EcmaScript module (only default export is available)

I have a react functional SPFx component in VS Code and use SPFX-fast-serve.
I am trying to use react-tooltip  "react-tooltip": "^5.27.0", as installed via npm
I then use that within a functional component as follows:
npm ls react-tooltip
<EMAIL_ADDRESS>C:\Users\Guy.Martinello\Documents\repos\Approvals
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
└──<EMAIL_ADDRESS>
import ReactTooltip from 'react-tooltip';

<ReactTooltip
	id="RequestReasonTooltip"
	place="bottom"
	content="Hello world! I'm a Tooltip"
/>

I have also tried as follows:
import { Tooltip } from 'react-tooltip'
<Tooltip
      id="RequestReasonTooltip"
      place="bottom"
      content="Hello world! I'm a Tooltip"
  />

./lib/webparts/traceApprovals/components/ApprovalRequests/ApprovalRequest.js
 @ ./lib/webparts/traceApprovals/components/Header.js
 @ ./lib/webparts/traceApprovals/components/TraceApprovals.js
 @ ./lib/webparts/traceApprovals/TraceApprovalsWebPart.js
./node_modules/react-tooltip/dist/react-tooltip.min.mjs 7:15955-15956
Can't import the named export 'useState' from non EcmaScript module (only default export is available)

Within my SPFX project, I do not see a webpack file - but do have a webpack.extend.js which I have updated as follows:
module.exports = function (buildOptions, webpackConfig) {
    // Your custom webpack configurations go here. For example:
    webpackConfig.resolve.alias = {
        "react-dom$": "react-dom/profiling",
    };

    // Add the rule for .mjs files
    webpackConfig.module.rules.push({
        test: /\.mjs$/,
        include: /node_modules/,
        type: 'javascript/auto',
    });

    return webpackConfig;
};

I have also installed react-scripts - as shown below with the rest of package.json

{
    "name": "approvals",
    "version": "2024.02.29",
    "private": true,
    "engines": {
        "node": ">=16.13.0 <17.0.0 || >=18.17.1 <19.0.0"
    },
    "main": "lib/index.js",
    "scripts": {
        "build": "gulp bundle",
        "clean": "gulp clean",
        "test": "gulp test",
        "typecheck": "tsc",
        "typecheck:watch": "tsc -w",
        "serve": "fast-serve"
    },
    "dependencies": {
        "@emotion/react": "^11.11.4",
        "@emotion/styled": "^11.11.5",
        "@fluentui/react": "^7.204.0",
        "@microsoft/sp-component-base": "1.18.0",
        "@microsoft/sp-core-library": "1.18.0",
        "@microsoft/sp-lodash-subset": "1.18.0",
        "@microsoft/sp-office-ui-fabric-core": "1.18.0",
        "@microsoft/sp-property-pane": "1.18.0",
        "@microsoft/sp-webpart-base": "1.18.0",
        "@mui/material": "^5.15.20",
        "@pnp/graph": "^3.12.1",
        "@pnp/logging": "^3.18.0",
        "@pnp/sp": "^3.6.0",
        "@pnp/sp-commonjs": "^2.15.0",
        "@pnp/spfx-controls-react": "3.15.0",
        "immer": "^10.0.3",
        "react": "17.0.1",
        "react-dom": "17.0.1",
        "react-scripts": "^5.0.1",
        "react-tooltip": "^5.27.0",
        "tslib": "2.3.1"
    },
    "devDependencies": {
        "@microsoft/eslint-config-spfx": "1.18.0",
        "@microsoft/eslint-plugin-spfx": "1.18.0",
<EMAIL_ADDRESS>"0.1.0",
        "@microsoft/sp-build-web": "1.18.0",
        "@microsoft/sp-module-interfaces": "1.18.0",
        "@rushstack/eslint-config": "2.5.1",
        "@types/react": "17.0.45",
        "@types/react-dom": "17.0.17",
        "@types/react-tooltip": "^4.2.4",
        "@types/webpack-env": "~1.15.2",
        "ajv": "^6.12.5",
        "eslint": "8.7.0",
        "eslint-plugin-react-hooks": "4.3.0",
        "gulp": "4.0.2",
        "spfx-fast-serve-helpers": "~1.18.0",
        "typescript": "4.7.4"
    }
}

tsconfig is as follows:
{
    "extends"<EMAIL_ADDRESS>    "compilerOptions": {
        "target": "es2017",
        "forceConsistentCasingInFileNames": true,
        "module": "esnext",
        "moduleResolution": "node",
        "jsx": "react",
        "declaration": true,
        "sourceMap": true,
        "experimentalDecorators": true,
        "skipLibCheck": true,
        "outDir": "lib",
        "inlineSources": false,
        "noImplicitAny": true,
        "noUnusedParameters": false,
        "noUnusedLocals": false,
        "allowSyntheticDefaultImports": true,
        "esModuleInterop": true,
        "typeRoots": [
            "./node_modules/@types",
            "./node_modules/@microsoft",
            "@types/react-tooltip"
        ],
        "types": [
            "webpack-env",
        ],
        "lib": [
            "es2017",
            "dom",
            "es2015.collection",
            "es2015.promise"
        ]
    },
    "include": [
        "src/**/*.ts",
        "src/**/*.tsx",
        "declaration.d.ts"
    ],
    "exclude": [
        "node_modules",
        "**/*.spec.ts"
    ]
}

Note please that if I try to add             "@types/react-tooltip" to the         "types" array, I receive the following error:
[{
	"resource": "/c:/Users/Guy.Martinello/Documents/repos/Approvals/tsconfig.json",
	"owner": "typescript",
	"severity": 8,
	"message": "Cannot find type definition file for<EMAIL_ADDRESS>The file is in the program because:\n    Entry point of type library '@types/react-tooltip' specified in compilerOptions",
	"source": "ts",
	"startLineNumber": 1,
	"startColumn": 1,
	"endLineNumber": 1,
	"endColumn": 2
}]

My outdated modules - in the event that there are version dependencies:
npm outdated
Package                              Current   Wanted   Latest  Location                                          Depended by
@fluentui/react                      7.204.0  7.204.0  8.118.8  node_modules/@fluentui/react                      Approvals
@microsoft/eslint-config-spfx         1.18.0   1.18.0   1.20.1  node_modules/@microsoft/eslint-config-spfx        Approvals
@microsoft/eslint-plugin-spfx         1.18.0   1.18.0   1.20.1  node_modules/@microsoft/eslint-plugin-spfx        Approvals
@microsoft/rush-stack-compiler-4.7     0.1.0    0.1.0    0.1.1<EMAIL_ADDRESS> Approvals
@microsoft/sp-build-web               1.18.0   1.18.0   1.20.1  node_modules/@microsoft/sp-build-web              Approvals
@microsoft/sp-component-base          1.18.0   1.18.0   1.19.0  node_modules/@microsoft/sp-component-base         Approvals
@microsoft/sp-core-library            1.18.0   1.18.0   1.19.0  node_modules/@microsoft/sp-core-library           Approvals
@microsoft/sp-lodash-subset           1.18.0   1.18.0   1.19.0  node_modules/@microsoft/sp-lodash-subset          Approvals
@microsoft/sp-module-interfaces       1.18.0   1.18.0   1.20.1  node_modules/@microsoft/sp-module-interfaces      Approvals
@microsoft/sp-office-ui-fabric-core   1.18.0   1.18.0   1.19.0  node_modules/@microsoft/sp-office-ui-fabric-core  Approvals
@microsoft/sp-property-pane           1.18.0   1.18.0   1.19.0  node_modules/@microsoft/sp-property-pane          Approvals
@microsoft/sp-webpart-base            1.18.0   1.18.0   1.19.0  node_modules/@microsoft/sp-webpart-base           Approvals
@pnp/graph                            3.12.1   3.25.0    4.2.0  node_modules/@pnp/graph                           Approvals
@pnp/logging                          3.18.0   3.25.0    4.2.0  node_modules/@pnp/logging                         Approvals
@pnp/sp                                3.6.0   3.25.0    4.2.0  node_modules/@pnp/sp                              Approvals
@pnp/spfx-controls-react              3.15.0   3.15.0   3.18.1  node_modules/@pnp/spfx-controls-react             Approvals
@rushstack/eslint-config               2.5.1    2.5.1    3.7.0  node_modules/@rushstack/eslint-config             Approvals
@types/react                         17.0.45  17.0.45   18.3.3  node_modules/@types/react                         Approvals
@types/react-dom                     17.0.17  17.0.17   18.3.0  node_modules/@types/react-dom                     Approvals
@types/webpack-env                    1.15.3   1.15.3   1.18.5  node_modules/@types/webpack-env                   Approvals
ajv                                   6.12.6   6.12.6   8.16.0  node_modules/ajv                                  Approvals
eslint                                 8.7.0    8.7.0    9.5.0  node_modules/eslint                               Approvals
eslint-plugin-react-hooks              4.3.0    4.3.0    4.6.2  node_modules/eslint-plugin-react-hooks            Approvals
gulp                                   4.0.2    4.0.2    5.0.0  node_modules/gulp                                 Approvals
immer                                 10.0.3   10.1.1   10.1.1  node_modules/immer                                Approvals
react                                 17.0.1   17.0.1   18.3.1  node_modules/react                                Approvals
react-dom                             17.0.1   17.0.1   18.3.1  node_modules/react-dom                            Approvals
tslib                                  2.3.1    2.3.1    2.6.3  node_modules/tslib                                Approvals
typescript                             4.7.4    4.7.4    5.4.5  node_modules/typescript                           Approvals

Any help would be much appreciated.

As you've probably seen on our troubleshooting page, the rule you added to the webpack config should fix this issue.
Best I can think of is that it's not getting applied correctly, but I'm unfamiliar with your setup to be able to say for certain. Also not sure how it being an SPFx project would break anything, never worked with it.
Also, @types/react-tooltip was for v4, so don't bother with that for v5.
Are you able to provide a sample repo that mirrors the basic configurations from your project so we can reproduce the issue?


Implement basic C# translation parser plugin

This PR implements a basic C# translation parser plugin. It extracts Tr, TrN, Atr and AtrN calls from C# scripts and generates entries for the POT file generator. The implementation is very basic compared to the GDScript translation parser because we can't properly parse C# source code for obvious reasons.
I have no prior C++ experience at all. I only implemented this because I needed it for my project.

this is neat, we're currently not working in master at the moment. We'll have to come back and look at this after we got all the rebranding stuff done and into master.

Is it possible to write this feature in C#? Just like the C# export feature, if write this feature in C#, should have an advantage in parsing the C# source code.

I would also like to see this type of feature sent upstream to Godot, though yeah probably a better plan if this could be done from C# for source code parsing reasons.

Since we've re-assessed our position on sending things upstream by default recently, we can take a look at this closely soon

Changes to this PR were already requested, the author has not come back.


still getting crash on startup issue with tempus aspect.

still getting the following crash
crash-2022-02-13_10.32.09-client.txt
however, i might have found something related to the issue. thaumicjei has a config file called thaumicjei_itemstack_aspects and so far its the only place i can find that has anything related to the tempus aspect. the following is what is listed:
{
"aspect": "Tempus",
"items": [
"{id:"quark:duskbound_lantern",Count:1s,Damage:0s}",
"{id:"charm:ender_pearl_block",Count:33s,Damage:0s}",
"{id:"minecraft:clock",Count:10s,Damage:0s}",
"{id:"minecraft:ender_pearl",Count:5s,Damage:0s}",
"{id:"forestry:engine_clockwork",Count:7s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"careerbees:eternalframe",Count:15s,Damage:0s}",
"{id:"chickenchunks:chunk_loader",Count:3s,Damage:1s}",
"{id:"extrautils2:ingredients",Count:3s,Damage:2s}",
"{id:"extrautils2:chunkloader",Count:2s,Damage:0s}",
"{id:"extrautils2:grocket",Count:3s,Damage:3s}",
"{id:"extrautils2:grocket",Count:3s,Damage:4s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"extrautils2:indexerremote",Count:4s,Damage:0s}",
"{id:"extrautils2:klein",Count:7s,Damage:0s}",
"{id:"extrautils2:drum",Count:10s,Damage:3s}",
"{id:"extrautils2:interactionproxy",Count:15s,Damage:0s}",
"{id:"gendustry:genetics_processor",Count:3s,Damage:0s}",
"{id:"randomthings:endermailbox",Count:7s,Damage:0s}",
"{id:"randomthings:entitydetector",Count:7s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"randomthings:enderletter",Count:3s,Damage:0s}",
"{id:"randomthings:enderbucket",Count:3s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"randomthings:timeinabottle",Count:7s,Damage:0s}",
"{id:"openblocks:builder_guide",Count:7s,Damage:0s}",
"{id:"openblocks:elevator",Count:3s,Damage:0s}",
"{id:"openblocks:elevator",Count:3s,Damage:1s}",
"{id:"openblocks:elevator",Count:3s,Damage:2s}",
"{id:"openblocks:elevator",Count:3s,Damage:3s}",
"{id:"openblocks:elevator",Count:3s,Damage:4s}",
"{id:"openblocks:elevator",Count:3s,Damage:5s}",
"{id:"openblocks:elevator",Count:3s,Damage:6s}",
"{id:"openblocks:elevator",Count:3s,Damage:7s}",
"{id:"openblocks:elevator",Count:3s,Damage:8s}",
"{id:"openblocks:elevator",Count:3s,Damage:9s}",
"{id:"openblocks:elevator",Count:3s,Damage:10s}",
"{id:"openblocks:elevator",Count:3s,Damage:11s}",
"{id:"openblocks:elevator",Count:3s,Damage:12s}",
"{id:"openblocks:elevator",Count:3s,Damage:13s}",
"{id:"openblocks:elevator",Count:3s,Damage:14s}",
"{id:"openblocks:elevator",Count:3s,Damage:15s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:1s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:2s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:3s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:4s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:5s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:6s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:7s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:8s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:9s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:10s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:11s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:12s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:13s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:14s}",
"{id:"openblocks:elevator_rotating",Count:2s,Damage:15s}",
"{id:"openblocks:generic",Count:3s,Damage:9s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"openblocks:pedometer",Count:7s,Damage:0s}",
"{id:"thaumadditions:salt_essence",Count:1s,tag:{Aspects:[{amount:1,key:"Tempus"}]},Damage:0s}",
"{id:"thaumadditions:vis_pod",Count:5s,tag:{Aspect:"Tempus"},Damage:0s}",
"{id:"thaumadditions:crystal_block",Count:6s,tag:{Aspect:"Tempus"},Damage:0s}",
"{id:"thaumicbases:endersapling",Count:7s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"wrcbe:tracker",Count:3s,Damage:0s}",
"{id:"thaumcraft:mirror_essentia",Count:3s,Damage:0s}",
"{id:"appliedenergistics2:wireless_access_point",Count:1s,Damage:0s}",
"{id:"appliedenergistics2:quantum_link",Count:9s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"appliedenergistics2:wireless_terminal",Count:1s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"appliedenergistics2:wireless_terminal",Count:1s,tag:{internalMaxPower:1600000.0d,internalCurrentPower:1600000.0d},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"appliedenergistics2:spatial_storage_cell_16_cubed",Count:20s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"appliedenergistics2:spatial_storage_cell_128_cubed",Count:60s,Damage:0s}",
"{id:"appliedenergistics2:material",Count:81s,Damage:34s}",
"{id:"appliedenergistics2:material",Count:27s,Damage:33s}",
"{id:"appliedenergistics2:material",Count:9s,Damage:32s}",
"{id:"appliedenergistics2:material",Count:3s,Damage:9s}",
"{id:"appliedenergistics2:material",Count:2s,Damage:41s}",
"{id:"appliedenergistics2:part",Count:2s,Damage:301s}",
"{id:"thaumcraft:crystal_essence",Count:1s,tag:{Aspects:[{amount:1,key:"Tempus"}]},Damage:0s}",
"{id:"thaumcraft:phial",Count:10s,tag:{Aspects:[{amount:10,key:"Tempus"}]},Damage:1s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"enderio:item_coord_selector",Count:3s,Damage:0s}",
"{id:"enderio:item_redstone_timer_filter",Count:7s,Damage:0s}",
"{id:"chisel:offsettool",Count:3s,Damage:0s}",
"{id:"ae2wtlib:infinity_booster_card",Count:1s,Damage:0s}",
"{id:"bloodmagic:teleposer",Count:7s,Damage:0s}",
"{id:"conarm:invisible_ink",Count:3s,Damage:0s}",
"{id:"quark:arrow_ender",Count:3s,Damage:0s}",
"{id:"bibliocraft:clock",Count:7s,Damage:0s}",
"{id:"bibliocraft:clock",Count:7s,Damage:1s}",
"{id:"bibliocraft:clock",Count:7s,Damage:2s}",
"{id:"bibliocraft:clock",Count:7s,Damage:3s}",
"{id:"bibliocraft:clock",Count:7s,Damage:4s}",
"{id:"bibliocraft:clock",Count:7s,Damage:5s}",
"{id:"bibliocraft:clock",Count:7s,Damage:6s}",
"{id:"darkutils:timer",Count:7s,Damage:0s}",
"{id:"darkutils:material",Count:3s,Damage:1s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"darkutils:charm_null",Count:6s,Damage:0s}",
"{id:"endreborn:item_ingot_endorium",Count:21s,Damage:0s}",
"{id:"endreborn:item_raw_endorium",Count:7s,Damage:0s}",
"{id:"endreborn:item_advanced_ender_pearl",Count:3s,Damage:0s}",
"{id:"endreborn:item_end_rune",Count:3s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:item_world_mirror",Count:65s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:tool_pickaxe_endorium",Count:47s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:tool_sword_endorium",Count:31s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:tool_hoe_endorium",Count:31s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:tool_axe_endorium",Count:47s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:tool_shovel_endorium",Count:15s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:ender_bow",Count:15s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:ender_sword",Count:86s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:tool_magnifier",Count:15s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:entropy_wand",Count:15s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:armour_chestplate_obsidian",Count:15s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:armour_leggings_obsidian",Count:15s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"endreborn:armour_helmet_helmet",Count:15s,Damage:0s}",
"{id:"endreborn:block_rune",Count:2s,Damage:0s}",
"{id:"funkylocomotion:teleporter",Count:1s,Damage:0s}",
"{id:"cfm:digital_clock",Count:7s,Damage:0s}",
"{id:"cfm:digital_clock",Count:7s,Damage:1s}",
"{id:"cfm:digital_clock",Count:7s,Damage:2s}",
"{id:"cfm:digital_clock",Count:7s,Damage:3s}",
"{id:"cfm:digital_clock",Count:7s,Damage:4s}",
"{id:"cfm:digital_clock",Count:7s,Damage:5s}",
"{id:"cfm:digital_clock",Count:7s,Damage:6s}",
"{id:"cfm:digital_clock",Count:7s,Damage:7s}",
"{id:"cfm:digital_clock",Count:7s,Damage:8s}",
"{id:"cfm:digital_clock",Count:7s,Damage:9s}",
"{id:"cfm:digital_clock",Count:7s,Damage:10s}",
"{id:"cfm:digital_clock",Count:7s,Damage:11s}",
"{id:"cfm:digital_clock",Count:7s,Damage:12s}",
"{id:"cfm:digital_clock",Count:7s,Damage:13s}",
"{id:"cfm:digital_clock",Count:7s,Damage:14s}",
"{id:"cfm:digital_clock",Count:7s,Damage:15s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"gb:gring16",Count:7s,Damage:0s}",
"{id:"gb:end_gring6",Count:7s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"gb:gring8",Count:30s,Damage:0s}",
"{id:"mysticalagriculture:chunk",Count:7s,Damage:19s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"rftools:storage_module",Count:7s,Damage:6s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"rftools:charged_porter",Count:15s,Damage:0s}",
"{id:"rftools:clock_module",Count:7s,Damage:0s}",
"{id:"rftools:slowness_module",Count:7s,Damage:0s}",
"{id:"rftools:remote_storage",Count:15s,Damage:0s}",
"{id:"rftools:matter_transmitter",Count:11s,Damage:0s}",
"{id:"rftools:matter_receiver",Count:11s,Damage:0s}",
"{id:"rftools:destination_analyzer",Count:15s,Damage:0s}",
"{id:"rftools:matter_booster",Count:11s,Damage:0s}",
"{id:"rftools:redstone_transmitter_block",Count:3s,Damage:0s}",
"{id:"rftools:counter_block",Count:7s,Damage:0s}",
"{id:"rftools:timer_block",Count:7s,Damage:0s}",
"{id:"rftools:ender_monitor",Count:3s,Damage:0s}",
"{id:"logisticspipes:pipe_remote_orderer",Count:3s,Damage:0s}",
"{id:"logisticspipes:pipe_inventory_system_connector",Count:3s,Damage:0s}",
"{id:"logisticspipes:pipe_firewall",Count:3s,Damage:0s}",
"{id:"mob_grinding_utils:absorption_upgrade",Count:15s,Damage:0s}",
"{id:"planarartifice:dimensional_singularity",Count:30s,Damage:0s}",
"{id:"xreliquary:mob_charm_fragment",Count:7s,Damage:8s}",
"{id:"rsgauges:automaticswitch4",Count:7s,Damage:0s}",
"{id:"rsgauges:daytimeswitch_glass1",Count:7s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"tg:pouch_ender",Count:7s,Damage:0s}",
"{id:"tg:book_holder",Count:15s,Damage:0s}",
"{id:"tg:part_stab_1",Count:15s,Damage:0s}",
"{id:"tg:teleportator_core",Count:15s,Damage:0s}",
"{id:"tg:teleportator_frame",Count:1s,Damage:0s}",
"{id:"tg:teleportator_floor",Count:2s,Damage:0s}",
"{id:"torchmaster:frozen_pearl",Count:3s,Damage:0s}",
"{id:"actuallyadditions:block_player_interface",Count:56s,Damage:0s}",
"{id:"actuallyadditions:block_ranged_collector",Count:7s,Damage:0s}",
"{id:"actuallyadditions:block_phantomface",Count:11s,Damage:0s}",
"{id:"actuallyadditions:block_phantom_placer",Count:8s,Damage:0s}",
"{id:"actuallyadditions:block_phantom_liquiface",Count:8s,Damage:0s}",
"{id:"actuallyadditions:block_phantom_energyface",Count:8s,Damage:0s}",
"{id:"actuallyadditions:block_phantom_redstoneface",Count:8s,Damage:0s}",
"{id:"actuallyadditions:block_phantom_breaker",Count:8s,Damage:0s}",
"{id:"actuallyadditions:block_misc",Count:15s,Damage:6s}",
"{id:"actuallyadditions:block_misc",Count:15s,Damage:8s}",
"{id:"actuallyadditions:block_item_repairer",Count:11s,Damage:0s}",
"{id:"actuallyadditions:block_phantom_booster",Count:11s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"actuallyadditions:item_void_bag",Count:3s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"actuallyadditions:item_tele_staff",Count:33s,tag:{Energy:250000},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"actuallyadditions:item_tele_staff",Count:33s,tag:{Energy:0},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"actuallyadditions:item_drill_upgrade_fortune_ii",Count:11s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"actuallyadditions:item_phantom_connector",Count:7s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"cyclicmagic:book_ender",Count:26s,tag:{},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"cyclicmagic:ender_dungeon",Count:3s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"astralsorcery:itemwand",Count:3s,tag:{astralsorcery:{}},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"astralsorcery:itemwand",Count:3s,tag:{astralsorcery:{AugmentName:"astralsorcery.constellation.aevitas"}},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"astralsorcery:itemwand",Count:3s,tag:{astralsorcery:{AugmentName:"astralsorcery.constellation.discidia"}},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"astralsorcery:itemwand",Count:3s,tag:{astralsorcery:{AugmentName:"astralsorcery.constellation.vicio"}},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"astralsorcery:itemwand",Count:3s,tag:{astralsorcery:{AugmentName:"astralsorcery.constellation.armara"}},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"astralsorcery:itemwand",Count:3s,tag:{astralsorcery:{AugmentName:"astralsorcery.constellation.evorsio"}},Damage:0s}",
"{id:"computercraft:peripheral",Count:3s,Damage:1s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"computercraft:pocket_computer",Count:2s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"computercraft:pocket_computer",Count:2s,tag:{upgrade:"computercraft:wireless_modem"},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"computercraft:pocket_computer",Count:2s,tag:{upgrade:"computercraft:advanved_modem"},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"computercraft:pocket_computer",Count:2s,tag:{upgrade:"computercraft:speaker"},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"computercraft:pocket_computer",Count:2s,Damage:1s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"computercraft:pocket_computer",Count:2s,tag:{upgrade:"computercraft:wireless_modem"},Damage:1s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"computercraft:pocket_computer",Count:2s,tag:{upgrade:"computercraft:advanved_modem"},Damage:1s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"computercraft:pocket_computer",Count:2s,tag:{upgrade:"computercraft:speaker"},Damage:1s}",
"{id:"portalgun:item_dust_ender_pearl",Count:3s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"portalgun:item_miniature_black_hole",Count:18s,Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"portalgun:item_portalgun",Count:13s,tag:{lastFired:1b,width:1,channelName:"Chell",grabStrength:4,uuid:"Global",username:"Global",height:2},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"portalgun:item_portalgun",Count:13s,tag:{lastFired:1b,width:1,channelName:"Atlas",grabStrength:4,uuid:"Global",username:"Global",height:2},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"portalgun:item_portalgun",Count:13s,tag:{lastFired:1b,width:1,channelName:"P-body",grabStrength:4,uuid:"Global",username:"Global",height:2},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"portalgun:item_portalgun",Count:13s,tag:{lastFired:1b,width:1,channelName:"Creative Inventory",grabStrength:4,uuid:"5aaf7c295a474cd38018a458d47991df",username:"AceTheWildCard",height:2},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"portalgun:item_portalgun",Count:13s,tag:{lastFired:1b,width:1,channelName:"Creative Inventory Type #2",grabStrength:4,uuid:"5aaf7c295a474cd38018a458d47991df",username:"AceTheWildCard",height:2},Damage:0s}",
"{ForgeCaps:{"astralsorcery:cap_item_amulet_holder":{}},id:"portalgun:item_portalgun",Count:13s,tag:{lastFired:1b,width:1,channelName:"Creative Inventory Type #3",grabStrength:4,uuid:"5aaf7c295a474cd38018a458d47991df",username:"AceTheWildCard",height:2},Damage:0s}",
"{id:"ebwizardry:spell_book",Count:3s,Damage:116s}",
"{id:"ebwizardry:spell_book",Count:3s,Damage:38s}",
"{id:"ebwizardry:spell_book",Count:3s,Damage:84s}",
"{id:"rftools:storage_terminal",Count:7s,Damage:0s}"
]
},
the file is in JSON format and is fairly large in size, so i cannot post the file itself.

right so i removed magic bees and ive gotten past the point where it crashes trying to start up. it might be something in my configs, but im not sure which one. any ideas?

reinstall magic bees, remove the thaumic jei json file, retry. see if it crashes

i will do that in the morning.

still crashing with the same crash
crash-2022-02-14_09.36.51-client.txt

okay, i have literally re-downloaded your entire modlist by individually downloading all mods shown in the crash log, it doesn't crash. I genuinely don't know what's the problem here then.

strange... well, if other people come forward with this issue then maybe it can be solved in the future. for now ill just not use magic bees. just keep in mind this is a potentially rare issue

this is definitely a rare issue. crazy to say but i think this is neither magic bees or PA's fault. magic bees definitely has Tempus. something is forcing magic bees to unload tempus for some reason.


Enable HTTP unit test

$subject
Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #15716 into master will increase coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #15716      +/-   ##
============================================
+ Coverage      6.88%     6.9%   +0.02%
- Complexity     1781     1785       +4
============================================
  Files          1384     1384
  Lines         70583    70611      +28
  Branches       9071     9076       +5
============================================
+ Hits           4859     4878      +19
- Misses        65230    65236       +6
- Partials        494      497       +3

Impacted Files
Coverage Δ
Complexity Δ

...org/ballerinalang/langserver/SnippetGenerator.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...etions/builder/BFunctionCompletionItemBuilder.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...lerinalang/langserver/common/utils/CommonUtil.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...xtproviders/FunctionDefinitionContextProvider.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...erinalang/langserver/completions/util/Snippet.java
0% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...ain/java/org/ballerinalang/net/http/BHttpUtil.java
5.83% <0%> (+2.07%)
10% <0%> (+3%)
:arrow_up:

...net/http/nativeimpl/connection/ResponseWriter.java
49.2% <0%> (+4.76%)
6% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e13fc74...638a376. Read the comment docs.


Saving the trained posterior.

Is it currently possible to do save the trained posterior weights. For example, after this line
posterior = inference.build_posterior(density_estimator)
may be in torch like way. Is it currently possible to do it? I could not find in tutorials or otherwise.
Thanks.

Hi, thanks for creating the issue! The posterior can be pickled, see here.
Feel free to reopen if this does not solve your issue!
Michael


hideColumn, what should be changing ?

I'm trying to persist the visibility change of cols, so when a columnVisibilityChanged event happens, I save it to the database.
After some debugging, I noticed that it was always saving visible as true.
After doing some digging, I noticed that when a column changes from the menu $scope.hideColumn is setting :
$scope.col.colDef.visible = false;
However the actual saved value is col.visible, I'm not 100% sure what the fix should be, should hideColumn be affecting just colDef, or both ?
or are changes to colDef reflected back to the visible at a later time ? (So I'd be saving too early)
I'm not 100% sure as I can't really reproduce this on the website demos.

It seems to work here: http://plnkr.co/edit/3CHTMu0SbHbq1NsHEKDj?p=preview
I just added the grid menu into the tutorial, so you can hide a column, save state, then show it again, then restore state.  It appears to hide correctly, so it must be working?

Hi Paul
I am trying to save the state automatically on any user action on the ui-grid. Hence in the below event I am calling the saveState.save method.
$scope.$on('hide-menu', function (event) {
$scope.state = $scope.gridApi.saveState.save();
alert($scope.state.columns[1].visible);
});
In this case the visible value is always true.
With Regards
Sandeep B

Could you provide a plunker that demonstrates that?  Then I can look at it.

No update in > 2 weeks. Closing.


init not working on macOS

Unsure on what is happening but refresh init is not creating the default yml file.
Note that the refresh.yml.bak file is just my backup file to submit this issue.
Also note that the project is outside GOPATH and it seems to make no difference if GO111MODULE=on is set.
> ls -l
total 24088
-rw-r--r--@ 1 gus  staff       130 25 Aug 18:28 Makefile
-rwxr-xr-x  1 gus  staff  12272428 25 Aug 18:26 backend*
-rw-------  1 gus  staff      2930 25 Aug 18:24 go.mod
-rw-------  1 gus  staff     39189 25 Aug 18:24 go.sum
-rw-r--r--@ 1 gus  staff      2235 25 Aug 17:38 main.go
drwxr-xr-x  5 gus  staff       160 25 Aug 12:52 pkg/
-rw-r--r--@ 1 gus  staff       997 25 Aug 18:27 refresh.yml.bak
drwxr-xr-x  4 gus  staff       128 25 Aug 14:27 vendor/
> refresh init
Refresh (1.4.0)

> ls -l
total 24088
-rw-r--r--@ 1 gus  staff       130 25 Aug 18:28 Makefile
-rwxr-xr-x  1 gus  staff  12272428 25 Aug 18:26 backend*
-rw-------  1 gus  staff      2930 25 Aug 18:24 go.mod
-rw-------  1 gus  staff     39189 25 Aug 18:24 go.sum
-rw-r--r--@ 1 gus  staff      2235 25 Aug 17:38 main.go
drwxr-xr-x  5 gus  staff       160 25 Aug 12:52 pkg/
-rw-r--r--@ 1 gus  staff       997 25 Aug 18:27 refresh.yml.bak
drwxr-xr-x  4 gus  staff       128 25 Aug 14:27 vendor/

Unable to get any more verbose output from the binary.
refresh run runs without the config file but does not work:
> refresh run
Refresh (1.4.0)

2019/08/25 18:32:49 No configuration loaded, proceeding with defaults
refresh: 2019/08/25 18:32:49 === Rebuild on: :start: ===
refresh: 2019/08/25 18:32:49 === Running: go build -v -o   (PID: 48379) ===
refresh: 2019/08/25 18:32:50 === Building Completed (PID: 48379) (Time: 759.844718ms) ===
refresh: 2019/08/25 18:32:50 === fork/exec : no such file or directory
 ===

However it works fine when I manually create a refresh.yml file.

This happens for me as well.

Same here, however it does work if you explicitly specify the path to the config file, e.g. refresh init -c refresh.yml.

This also is confirmable for me as well.


limbo: initial client testcases

Adds two initial client verification testcases, both of which use email subjects and email NCs.

I'm not going to have time to give this a proper review in the near-time frame, not sure how you'd like to proceed.

I'm not going to have time to give this a proper review in the near-time frame, not sure how you'd like to proceed.

No worries. I was thinking I could merge this as-is (since the existing limbo harness upstream should skip them), but this can also sit until you have more review time + I have the time to finish the actual client implementation, which will probably be next week at the earliest 🙂

If you want to just merge it as a starting point, I don't object. (I don't
think I reviewed all the original server test cases either)
On Mon, Mar 4, 2024 at 1:42 PM William Woodruff @.***>
wrote:

I'm not going to have time to give this a proper review in the near-time
frame, not sure how you'd like to proceed.
No worries. I was thinking I could merge this as-is (since the existing
limbo harness upstream should skip them), but this can also sit until you
have more review time + I have the time to finish the actual client
implementation, which will probably be next week at the earliest 🙂
—
Reply to this email directly, view it on GitHub
https://github.com/C2SP/x509-limbo/pull/196#issuecomment-1977227598, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAGBGNVY7B6TT2YOPENWDYWS6BRAVCNFSM6AAAAABDD3IY2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZXGIZDONJZHA
.


Investigate sorting edges by combined degree of adjacent edges

In the current assembly code, edges in the "shared interesting k-mers" graph are processed in order of overlap: the largest overlaps first. I should investigate processing instead by node degree: high-degree nodes are less likely to lead to a premature truncation of the contig due to a sequencing error.

Fixed by #89.


*: Makefile: use dwz to reduce binary size

With v8.5.0 tikv-server:

uncompressed:              1.7G (as reference only)
zlib-gnu compressed:       465M (without this commit)
zlib-gnu compressed + dwz: 406M (with this commit)

Looks like https://sourceware.org/bugzilla/show_bug.cgi?id=24764 that was mentioned has been resolved in 2019.
See also: https://github.com/tikv/tikv/pull/5820

What is changed and how it works?

Issue Number: ref #4107

What's Changed:
Makefile: use dwz to reduce binary size

Related changes

[ ] PR to update pingcap/docs/pingcap/docs-cn:
[ ] Need to cherry-pick to the release branch

Check List
Tests

[ ] Unit test
[ ] Integration test
[x] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Release note

None

/cc @glorv

/check-issue-triage-complete
/ok-to-test

I'm not quite familiar with dwz. After compressed by it, can we get meaningful debug info when printing stack?

With a binary that was had dwz run on it:
Thread 1 "tikv-server" received signal SIGINT, Interrupt.
0x00007efc4a71323d in syscall () from /lib64/libc.so.6
(gdb) bt
#0  0x00007efc4a71323d in syscall () from /lib64/libc.so.6
#1  0x00005559a4f1b364 in std::sys::unix::futex::futex_wait (futex=0x7efc4a04b4b8, expected=4294967295, timeout=...) at src/sys/unix/futex.rs:62
#2  std::sys_common::thread_parking::futex::Parker::park (self=...) at src/sys_common/thread_parking/futex.rs:52
#3  std::thread::park () at src/thread/mod.rs:1066
#4  0x00005559a2c4bf85 in futures_executor::local_pool::run_executor::{closure#0}<core::result::Result<pd_client::client::RpcClient, pd_client::errors::Error>, futures_executor::local_pool::block_on::{closure_env#0}<pd_client::client::{impl#0}::new_async::{async_fn_env#0}>> (thread_notify=<optimized out>)
    at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-executor-0.3.15/src/local_pool.rs:99
#5  std::thread::local::LocalKey<alloc::sync::Arc<futures_executor::local_pool::ThreadNotify, alloc::alloc::Global>>::try_with<alloc::sync::Arc<futures_executor::local_pool::ThreadNotify, alloc::alloc::Global>, futures_executor::local_pool::run_executor::{closure_env#0}<core::result::Result<pd_client::client::RpcClient, pd_client::errors::Error>, futures_executor::local_pool::block_on::{closure_env#0}<pd_client::client::{impl#0}::new_async::{async_fn_env#0}>>, core::result::Result<pd_client::client::RpcClient, pd_client::errors::Error>> (self=<optimized out>, f=...)
    at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:270
#6  std::thread::local::LocalKey<alloc::sync::Arc<futures_executor::local_pool::ThreadNotify, alloc::alloc::Global>>::with<alloc::sync::Arc<futures_executor::local_pool::ThreadNotify, alloc::alloc::Global>, futures_executor::local_pool::run_executor::{closure_env#0}<core::result::Result<pd_client::client::RpcClient, pd_client::errors::Error>, futures_executor::local_pool::block_on::{closure_env#0}<pd_client::client::{impl#0}::new_async::{async_fn_env#0}>>, core::result::Result<pd_client::client::RpcClient, pd_client::errors::Error>> (f=...)
    at /root/.rustup/toolchains/nightly-2023-12-28-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/thread/local.rs:246
#7  futures_executor::local_pool::run_executor<core::result::Result<pd_client::client::RpcClient, pd_client::errors::Error>, futures_executor::local_pool::block_on::{closure_env#0}<pd_client::client::{impl#0}::new_async::{async_fn_env#0}>> (f=...) at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-executor-0.3.15/src/local_pool.rs:86
#8  futures_executor::local_pool::block_on<pd_client::client::{impl#0}::new_async::{async_fn_env#0}> (f=<error reading variable: Cannot access memory at address 0x168>)
    at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-executor-0.3.15/src/local_pool.rs:315
#9  pd_client::client::RpcClient::new (cfg=<optimized out>, shared_env=..., security_mgr=...) at components/pd_client/src/client.rs:65
#10 0x00005559a313aa71 in server::common::TikvServerCore::connect_to_pd_cluster (config=0x7fff72c6a010, env=..., security_mgr=...) at components/server/src/common.rs:316
#11 0x00005559a316639a in server::server::TikvServer<raft_log_engine::engine::RaftLogEngine, api_version::ApiV1>::init<raft_log_engine::engine::RaftLogEngine, api_version::ApiV1> (
    config=<error reading variable: Cannot access memory at address 0x0>, tx=...) at components/server/src/server.rs:339
#12 server::server::run_impl<raft_log_engine::engine::RaftLogEngine, api_version::ApiV1> (config=..., service_event_tx=..., service_event_rx=...) at components/server/src/server.rs:162
#13 0x00005559a2233f9a in server::server::run_tikv (config=..., service_event_tx=..., service_event_rx=...) at components/server/src/server.rs:233
#14 tikv_server::main () at cmd/tikv-server/src/main.rs:249

This looks ok to me. Anything else we should test?

To be able to run dwz it needs to be installed. Not sure where this is configured as I can only find Dockerfile and Dockerfile.FIPS that install build dependencies, but this seems to be broken ( #17894  ).

/cc @wuhuizuo


Removed unused gateway.

golang.org/x/net/context is legacy. With go1.9 there should be type aliases now which no longer requires importing both context packages.
Do you have go1.8 or lower installed by any chance?

Yup, I did not update to go 1.9 yet, removing that change then (:

OK, I think we have some Travis bug or default travis logic when there is no Travis.yaml ): https://travis-ci.org/improbable-eng/promlts/builds/296370778?utm_source=github_status&utm_medium=notification
We need to merge https://github.com/improbable-eng/promlts/pull/14 first

Removing this PR in favor of clean https://github.com/improbable-eng/promlts/pull/15


Require python >= 3.7

There is a timeout in conda env create -n cta-dev --file environment.yml on Travis when building for Py3.8
Is this reason for concern? I restarted the build this morning once .. hoping it was just a mishap on travis.... no luck

@dneise it worked yesterday with the first commit... Ah, but that probably was still using the wrong version.

It is a missing eventio for python 3.8 I think.

Erm .. I see to be missing the point here ... it is still failing no?

Yes, because there is no conda package of eventio for python 3.8. @kosack will upload it shortly.

Ah I see ... thanks


Compatibility with usbip-attached devices

After applying the patch in #144, I'm able to proxy a local device (Yubikey 5) successfully to the target machine. I'm testing whether Cynthion could be useful for establishing an over-the-network USB proxy, and so I've extended this test to try proxying the same device when attached via usbip. While the initial results seem positive, the test ultimately fails with the Yubikey and all other devices I've tried.
Here's an outline of the desired state:

Yubikey attaches to RPi A via USB
RPi A runs usbip bind and usbipd to advertise the device
RPi B runs usbip attach to mount the device.
RPi B connects to cynthion via control and runs usbproxy.py
macOS device connects to cynthion via target C in order to consume the proxied device

I'm currently able to complete all steps without error and can see the proxied device listed on the USB bus from system info on macOS, but I don't get any other signs of life from the device at this point.
From a troubleshooting perspective, I've observed the following:

Running the same test with a USB keyboard provides similar results. The keyboard appears in the macOS device list, but it doesn't transmit any keystrokes.
Following steps 1-3 above, the Yubikey (and keyboard) work properly over the usbip link when tested from RPi B
Moving the Yubikey to connect directly on RPi B, I am able to run usbproxy.py and perform a successful authentication (and type with the keyboard) exactly as though it was attached directly to the Mac.

Assuming that this setup should work, I'm happy to provide any logs or additional details to aide with troubleshooting and replication. The objective in this case is to be able to test and demonstrate phishing resistant authentication flows against a variety of end-user devices that the members of my mostly remote team would like to centralize and access via web-based KVM. If we can get this working, I'm eager to get my hands on a few more Cynthions in order to centralize our pool of test devices.

We've had https://github.com/greatscottgadgets/facedancer/issues/25 open for a long time with nobody working on it. I think we assumed that we would need a new Facedancer backend, but I guess it ought to be possible with usbip attach on the Facedancer control host. (A special backend would be nice for cross-platform support.)
Can you show us the Facedancer console output?


New Docker Swarm cluster will not create a service using a volume driver

Description
After creating a new docker swarm cluster and attempting to create a service using a volume driver, the deployment hangs. You will get a service ID in return but then sits in a pending state
indefinitely. I'm required to deploy a stateless service (as if the cluster has to initialize first) and then deploy the service using a volume driver.
This has been tested using VirtualBox and ScaleIO environments with consistent results with REX-Ray. Using a local volume (--mount type=volume,target=/data) has no issues. The issue is only present when using Swarm with a volume driver and not running a normal docker container with a volume driver.
Steps to reproduce the issue:

Create new 3 new machines (this is going to be using virtualbox. This should yield same results on AWS)

$ docker-machine create -d virtualbox vbox01 && docker-machine create -d virtualbox vbox02 && docker-machine create -d virtualbox vbox03

When using the VirtualBox SOAP API service for the first time, disable authentication:

$ VBoxManage setproperty websrvauthlibrary null

Start the VirtualBox SOAP API to accept API requests from the REX-Ray service in a new terminal window:

$ vboxwebsrv -H <IP_ADDRESS> -v

Install REX-Ray as a service. If using in AWS, you can try using the official AWS REX-Ray EBS plugin or continue installing as a service.

$ docker-machine ssh vbox01 "curl -sSL https://dl.bintray.com/emccode/rexray/install | sh" && docker-machine ssh vbox02 "curl -sSL https://dl.bintray.com/emccode/rexray/install | sh" && docker-machine ssh vbox03 "curl -sSL https://dl.bintray.com/emccode/rexray/install | sh"

Add the REX-Ray configuration file (change REX-Ray config file if deploying to AWS as service using the REX-Ray configuration generator) :

$ docker-machine ssh vbox01 "sudo tee -a /etc/rexray/config.yml << EOF
libstorage:
  service: virtualbox
  integration:
    volume:
      operations:
        mount:
          preempt: true
virtualbox:
  endpoint: http://<IP_ADDRESS>:18083
  volumePath: /Users/$USER/VirtualBox/Volumes
  controllerName: SATA"

$ docker-machine ssh vbox02 "sudo tee -a /etc/rexray/config.yml << EOF
libstorage:
  service: virtualbox
  integration:
    volume:
      operations:
        mount:
          preempt: true
virtualbox:
  endpoint: http://<IP_ADDRESS>:18083
  volumePath: /Users/$USER/VirtualBox/Volumes
  controllerName: SATA"

$ docker-machine ssh vbox03 "sudo tee -a /etc/rexray/config.yml << EOF
libstorage:
  service: virtualbox
  integration:
    volume:
      operations:
        mount:
          preempt: true
virtualbox:
  endpoint: http://<IP_ADDRESS>:18083
  volumePath: /Users/$USER/VirtualBox/Volumes
  controllerName: SATA"

Start the REX-Ray Service:

$ docker-machine ssh vbox01 "sudo rexray start" && docker-machine ssh vbox02 "sudo rexray start" && docker-machine ssh vbox03 "sudo rexray start"

Create the Docker Swarm Cluster

$ VBOX01IP=$(docker-machine ssh vbox01 "ifconfig | sed -En 's/<IP_ADDRESS>//;s/.*inet (addr:)?(([0-9]*\.){3}[0-9]*).*/\2/p' | grep 99")
$ docker-machine ssh vbox01 "docker swarm init --advertise-addr $VBOX01IP --listen-addr $VBOX01IP"
$ VBOXSWARMTOKEN=$(docker-machine ssh vbox01 "docker swarm join-token -q worker")
$ docker-machine ssh vbox02 "docker swarm join --token $VBOXSWARMTOKEN $VBOX01IP:2377" && docker-machine ssh vbox03 "docker swarm join --token $VBOXSWARMTOKEN $VBOX01IP:2377"

Precreate the volume (optional):

$ docker-machine ssh vbox01 "sudo rexray volume create pgdata --size=8"

Try and deploy a container requiring a volume driver:

$ docker service create --replicas 1 --name pg -e POSTGRES_PASSWORD=mysecretpassword \
--mount type=volume,target=/var/lib/postgresql/data,source=pgdata,volume-driver=rexray \
--constraint 'node.role == worker' postgres

You will get a result that never deploys to a node:
docker@vbox01:~$ docker service ps pg
ID                  NAME                IMAGE               NODE                DESIRED STATE       CURRENT STATE           ERROR               PORTS
n1u32wpwk3gt        pg.1                postgres:latest                         Running             Pending 38 seconds ago
docker@vbox01:~$

Remove the service and deploy a stateless service

docker@vbox01:~$ docker service rm pg
pg
docker@vbox01:~$ docker service create --name red --replicas 3 redis
ipcvdwlh05b01ei7jngwfbvte
docker@vbox01:~$ docker service ps red
ID                  NAME                IMAGE               NODE                DESIRED STATE       CURRENT STATE            ERROR               PORTS
xpe6ptx3fdmh        red.1               redis:latest        vbox03              Running             Running 38 seconds ago
y5ub03cnckve        red.2               redis:latest        vbox01              Running             Running 13 seconds ago
asmhkc564lxv        red.3               redis:latest        vbox02              Running             Running 38 seconds ago
docker@vbox01:~$

Now remove the redis service and redploy the postgres service with a volume driver and it works.

docker@vbox01:~$ docker service rm red
red
docker@vbox01:~$ docker service create --replicas 1 --name pg -e POSTGRES_PASSWORD=mysecretpassword \
> --mount type=volume,target=/var/lib/postgresql/data,source=pgdata,volume-driver=rexray \
> --constraint 'node.role == worker' postgres
nwb6q66fawmmb0bc7zyq84lx7
docker@vbox01:~$ docker service ps pg
ID                  NAME                IMAGE               NODE                DESIRED STATE       CURRENT STATE           ERROR               PORTS
kelft7bf55l9        pg.1                postgres:latest     vbox03              Running             Running 3 seconds ago

Describe the results you received:
Docker Swarm is not able to create an initial service using a volume driver until a stateless service has been deployed to all hosts first.
Describe the results you expected:
I expect Docker Swarm to create the service using a volume driver once the swarm cluster has been created.
Additional information you deem important (e.g. issue happens only occasionally):

Refer to information in https://github.com/codedellemc/rexray/issues/781

I've tried enabling experimental flag in docker to see the Swarm log but there are no logs being created.  (https://github.com/docker/docker/tree/master/experimental):

sudo vi /etc/docker/daemon.json
{
    "experimental": true
}

Output of docker version:
This symptom has been seen since as far back as 1.12.1
docker@vbox01:~$ docker version
Client:
 Version:      17.04.0-ce
 API version:  1.28
 Go version:   go1.7.5
 Git commit:   4845c56
 Built:        Wed Apr  5 18:45:47 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.04.0-ce
 API version:  1.28 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   4845c56
 Built:        Wed Apr  5 18:45:47 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:
docker@vbox01:~$ docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 17.04.0-ce
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 7
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local rexray
 Network: bridge host macvlan null overlay
Swarm: active
 NodeID: lru2q97d6mivop1ctl0wv90p3
 Is Manager: true
 ClusterID: jpygx3amq2s5sxq1j5m6g8lbi
 Managers: 1
 Nodes: 3
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
 Manager Addresses:
  <IP_ADDRESS>:2377
Runtimes: runc
Default Runtime: runc
Init Binary:
containerd version: 422e31ce907fd9c3833a38d7b8fdd023e5a76e73
runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.4.59-boot2docker
Operating System: Boot2Docker 17.04.0-ce (TCL 7.2); HEAD : c69677f - Thu Apr  6 16:26:16 UTC 2017
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 995.8MiB
Name: vbox01
ID: ONLX:FBGF:LDZ4:FTYU:7SN6:MJ4G:JQCB:HXGN:IKAL:7K6W:SAJM:MTJL
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 32
 Goroutines: 157
 System Time: 2017-04-10T17:41:10.923769415Z
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
Results are seen using VirtualBox and ScaleIO on VirtualBox and ScaleIO on VMware. Have not tested on AWS using REX-Ray.

This is probably due to "lazy loading" of legacy (non-managed) plugins; when deploying a task, swarm looks for nodes that support the specified volume-driver, however, the volume-driver is not loaded until a volume with that driver was created on the node. Support for "managed" plugins in swarm mode is actively being worked on, and should resolve this.
/cc @anusha-ragunathan if my interpretation of the issue at hand is correct/likely 😅

@thaJeztah , your explanation is correct.
But the observation of "Docker Swarm is not able to create an initial service using a volume driver until a stateless service has been deployed to all hosts first." is incorrect. Steps 9 and 11 are identical and there's nothing that a stateless service deployment does to plugin discovery.
Is there a volume on vbox03 created using this driver, after the initial service creation? That would trigger the lazy load of the plugin and explain why the service creation succeeds the second time around.

@anusha-ragunathan @thaJeztah
yes, steps 9 and 11 are identical. It shows that trying to do it in step 9 fails. step 10 deploys as service without a volume driver. then try to do it once again in step 11 and it succeeds.
REX-Ray is talking to a backend storage platform (whether it's AWS EBS Volumes, ScaleIO Volumes, VirtualBox Media, etc). The volumes ARE NOT being created on the nodes themselves. We are talking about centralized storage.

I can confirm this issue is not present when using the managed plugin. only legacy plugins.

@kacole2 : I think the reason step 10 matters in this case, is because the redis image creates a volume called /data. Deploying such a service indirectly results in probing all drivers which activates the plugin and hence step 11 succeeds. If you tried deploying a busybox service in step 10, I think step 11 would continue to not deploy the service.

Close issue, since this behavior is expected of v1plugins.


Email address instead of lan id

Hey guys
Is there a way of implementing this so the user can enter their email rather than their account id?
Looking at using this as part of an ADFS solution where the users login with the email loaded in the AD email field.
Thanks

Our apologies. This is out of scope.


⚠ Turnos 24x7 has degraded performance

In e3df3fd, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 914 ms

Resolved: Turnos 24x7 performance has improved in df36210.


NIFI-5984: Enabled Kerberos Authentication for PutKudu

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Reviewing...

The code LGTM, I'm not able to give it a try right now unfortunately. Just one question though: does it take care of the ticket renewal? or is the underlying implementation taking care of it? (asking since the client is initialized in the OnScheduled method)

UGI will take care of the relogin, but I think only if the UGI.doAs is used to execute the action.  If the PR is updated to use KerberosAction from nifi-security-utils org.apache.nifi.security.krb.KerberosAction, it will handle expired tickets.

@jtstorck I pushed another commit that I believe addresses all review feedback and rebases against master in order to resolve a conflict that was introduced.

Thanks for the updates and this contribution, @markap14!
Tested this against a kerberized cluster (HDFS, Impala, Kudu), creating Impala tables stored in Kudu, inserting data into Kudu with the PutKudu processor configured to use a KerberosCredentialsService.
LGTM, +1.  Merging to master!

Hello.
I still have issues with expired tickets, I have to restart the processor every week with nifi 1.9.2

@zorel Is this still an issue for you? If so we should file a jira.

@zorel Is this still an issue for you? If so we should file a jira.

Yeah, I'm not part of the team anymore, but it seems they still have the problem, every week. I'll see with them if/when they upgrade to 1.10 to see if it still happens. Thanks


CameraKitGallery.getImageForTapEvent not returning valid  URI

Description
I am trying to use the gallery to open an image and send it to our api however it seems as though the url filepath is incorrect
async onTapImage(event) {
    const id = event.nativeEvent.selected;
    const image = await CameraKitGallery.getImageForTapEvent(event.nativeEvent);
     console.log("here");

    let imageSize = {
        size: {width, height},
        offset: {x: 0, y: 0,},
    };

    if (image) {
             ImageEditor.cropImage(image.imageUri, {offset:{x:0,y:0},size:{width:imageSize.width, height:imageSize.height}}, (imageURI) => {
                ImageStore.getBase64ForTag(imageURI, (base64Data) => {
                    this.setState({ticketImage: base64Data, open: true});
                }, (reason)  => console.log(reason))
             }, (reason) => console.log(reason));
     }
}

Additional Information
The file path works on android but fails on ios.
Any ideas?
Cheers

I am having the same issue.  I am able to see a selectedImageId if I log the image in the developer console, but no image URL.


Mod does not work with mod security enabled

How to reproduce:

Use latest Minetest developer version or set Minetest setting secure.enable_security=true
Start a world with intllib

The game is unable to start.

Closed because it is not intllib's fault.
https://forum.minetest.net/viewtopic.php?f=11&t=4929&p=239212#p239212


MySQL 5.7.8 JSON datatype

An forward thinking plans for the new data type?
https://dev.mysql.com/doc/refman/5.7/en/json.html

Just looking for someone to make a pull request, or when we get to it. See #1267


Provide a user friendly message if the server is unavailable

At the login page, currently, if the server is unavailable, we get a message"username does not exist" which is not correct.
Please provide a user friendly message indicating that the server is not available at the moment.

Should be addressed in Alpha.27


Update alz_checklist.en.json

This pull request is related to the GitHub issue https://github.com/Azure/review-checklists/issues/743. In fact there is a reference to DDOS
enforcement for public IP on 2 entries in the checklist (D01.03 and D06.06). I am suggesting the removal of the D01.03 because it is only related to application landing
zones. The D06.06 cover all Virtual networks with public IP and its link is pointing to the reference architecture.  The removal of D01.03 is not impacting the numbering
of other entries. The next entry after fetching the check list is D02.01.

@hgotar1 can you look into the merge conflict pls

The JSON tag for D01.03 seems to be gone after sync (fetch) another pull request may have successfully remove it already


Update install-deps.sh to support intel arch on macOS

Description
Adding support for macOS intel architecture in trivy dependency download in install-deps.sh
Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
support for macOS intel architecture in trivy dependency download in install-deps.sh
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline


Better framework flag

https://github.com/wio/wio-core/blob/2679930176add3f6752b1e4286fd4169da1b0d95/cmd/wio/dependencies/cmake-text-generator.go#L10
AVR shouldn't be hardcoded in

Will be fixed incoming pull request. Almost finished


Fix the plugin's domain-extension problem

I propose to this PR to remove everything related to wildfly ( the jboss-deployment-structure, GroupManagementEntityProviderFactory and GroupManagementEntityProvider). A check in Quarkus is needed for them.

GroupManagementEntityProviderFactory and GroupManagementEntityProvider should not be removed... they are still used to call the liquibase update script ;)
Removed the jboss-deployment-structure ;)

I propose to this PR to remove everything related to wildfly ( the jboss-deployment-structure, GroupManagementEntityProviderFactory and GroupManagementEntityProvider). A check in Quarkus is needed for them.

GroupManagementEntityProviderFactory and GroupManagementEntityProvider should not be removed... they are still used to call the liquibase update script ;) Removed the jboss-deployment-structure ;)

You are right. Good job!


⚠ ClamAV has degraded performance

In e6d02cc, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 194 ms

Resolved: ClamAV performance has improved in 02dd017.


flaky crashes false positive

1.Test Environment
V8 version: 7.8.0
Ubuntu 16.04
Timeout config: 380ms
2.Issues
I find some crashes files generated by fuzzilli, when I want to reproduce the crashes by running d8, but most of them doesn't crash d8 or any errors.(I use the same machine and d8 tool to reproduce the crash.)

Command line as bellow:
  v8/out/fuzzbuild/d8 --debug-code --expose-gc --single-threaded --predictable --allow-natives-syntax --interrupt-budget=1024 --no-arguments crash_1566514916227_18444_flaky_4.js

Results:
[COV] no shared memory bitmap available, skipping
[COV] edge counters initialized. Shared memory: (null) with 565526 edges

Test shows:

Total Samples:                4996990
Interesting Samples Found:    8601
Valid Samples Found:          2874108
Corpus Size:                  1032
Success Rate:                 57.52%
Timeout Rate:                 2.76%
Crashes Found:                8
Timeouts Hit:                 137813
Coverage:                     17.26%
Avg. program size:            93.80
Connected workers:            0
Execs / Second:               18.27
Total Execs:                  5768202

3.Questions
Whether the flaky crashes are false positive?Please check the flaky crashes in the attachment.

flaky_crashes.zip

I'm now tracking attempts to improve handling of non-reproducible crashes here: https://github.com/googleprojectzero/fuzzilli/issues/42 Feel free to try some of the things I noted there to hopefully get an idea of what is happening


nextjs  DarkThemeToggle show Warning

Describe the bug
A clear and concise description of what the bug is.
Warning: Prop `fillRule` did not match. Server: "null" Client: "evenodd"
    at path
    at svg
    at IconBase
    at HiSun
    at button
    at DarkThemeToggle (webpack-internal:///(app-client)/./node_modules/.pnpm/flowbite-react@0.4.4_flowbite@1.6.5_react-dom@18.2.0_react@18.2.0_tailwindcss@3.3.2/node_modules/flowbite-react/lib/esm/components/DarkThemeToggle/DarkThemeToggle.js:19:28)
    at Flowbite (webpack-internal:///(app-client)/./node_modules/.pnpm/flowbite-react@0.4.4_flowbite@1.6.5_react-dom@18.2.0_react@18.2.0_tailwindcss@3.3.2/node_modules/flowbite-react/lib/esm/components/Flowbite/Flowbite.js:20:21)

To Reproduce
Steps to reproduce the behavior:
    <Flowbite>
      <DarkThemeToggle />
    </Flowbite>

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information:

Device:
Resolution:
OS:
Browser:
Version:

Project information:

Tailwind: 3.3.2
Flowbite: 1.6.5
Flowbite React: 0.4.4
Type: nextjs

Additional context
system default dark mode

This is really weird to be happening inside the DarkThemeToggle. I see how it can be related to #738 now, but at the same time, I don't believe that the proposed solution on that PR is the right answer. We should be careful by removing features from the library, and if we think that this is the only solution, maybe first, bring it to the discussion.
What would be the pros and cons to remove the user preference stuff from the ThemeContext? If we remove it, what would be the approach to the users that want to implement it by themselves? Also, it would be a breaking feature... So, it should be documented.

Fixed in the latest release, v0.7.0


Upgrade to final GWT 2.8.0

@dgutierr

I'm getting an error while trying to execute from command line  "mvn gwt:run"
[INFO] --- gwt-maven-plugin:2.8.0:run (default-cli) @ dashbuilder-webapp ---
[INFO] create exploded Jetty webapp in /home/dgutierr/Devel/git/dashbuilder/dashbuilder/dashbuilder-webapp/src/main/webapp
[INFO] Super Dev Mode starting up
[INFO]    workDir: /tmp/gwt-codeserver-5414296489078017909.tmp
[INFO]    Loading Java files in org.dashbuilder.FastCompiledDashbuilderShowcase.
[INFO]    Ignored 3 units with compilation errors in first pass.
[INFO] Compile with -strict or with -logLevel set to DEBUG or WARN to see all errors.
[INFO]    Module setup completed in 23456 ms
[INFO]
[INFO] The code server is ready at http://<IP_ADDRESS>:9876/
[INFO] Warning! The CLI is running in a non-modular environment and cannot load commands from management extensions.
[ERROR] Unable to start embedded HTTP server
[ERROR] com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries)
[ERROR] 	at org.jboss.errai.cdi.server.gwt.EmbeddedWildFlyLauncher.start(EmbeddedWildFlyLauncher.java:113)
[ERROR] 	at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:634)
[ERROR] 	at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:923)
[ERROR] 	at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:706)
[ERROR] 	at com.google.gwt.dev.DevMode.main(DevMode.java:430)
@csadilek is there anything I'm missing? :-)

@dgutierr please run mvn clean gwt:run and share the full log / stack trace. The fact that the server is not starting up is not related to this upgrade. Maybe you had another (stale) instance running? Starting up fine here on two different machines...

Hey @csadilek , @dgutierr ,it works fine -> +1
@dgutierr you have to use the "clean" goal as well when running SDM, as the previous built generate some assets that have to be clean and are rebuilt once on the process-resources phase. So just running "mvn clean gwt:run" works fine. Thanks guys

Closed: 8b19baef56fcdf6f4097d6646dc4efa66880eef4


Prevent's "Brian's bomb" by manually clearing metrics on each test class

As discussed in https://github.com/openzipkin/zipkin/issues/1811, the
current prometheus client isn't fit for usage in tests until
@brian-brazil changes his mind. This copy/pastes bomb prevention where
bomb is the application failing to start due to prometheus state error
on duplicate metric registration (the dupe is because a servlet filter
creates and hides a metric).

closed via 8973e1a6627afacdf6238cf94f3e9fffc6f3648f


Laravel 5??

Any idea if this works on laravel 5

Hi @jccp2,
I plan to do this during the next weeks.
For the moment it doesn't work.
Cheers,
Tortue Torche

I really like your package and I would love to see it work under laravel 5. Looking forward to your update.

@dailez Thank you for your support.
I've started to update Authority-Controller to be compatible with Laravel 5.
Some tests aren't passing yet but I hope to release an alpha version next week.
Cheers,
Tortue Torche

I make some good progress, now all tests pass !
I still need to update the installation instructions and the Laravel demo

@tortuetorche  thank you its an awesome package, I am new to laravel so im just getting to know the internals if not I would jump in and help. when its ready and you pushed it ill give it a try at least I can help you find bugs and fix what ever I can.

Authority-Controller 2.0 now supports Laravel 5 !
It's an alpha release, so you need to tweak the composer.json file of your Laravel 5 application.
Add a repositories option:
{
	//...
	"repositories": [
		{
			"type": "vcs",
			"url": "https://github.com/stayallive/authority"
		},
		{
			"type": "vcs",
			"url": "https://github.com/stayallive/authority-l5"
		}
	],
	//...
}

Then add these two options:
{
	//...
	"prefer-stable": true,
	"minimum-stability": "dev"
}

Here a composer.json sample.
Feel free to reopen this issue if you have some problems with Authority-Controller 2.0.

By the way, I also need to update the Wiki docs, so I plan to do this in a couple of weeks.
Have fun,
Tortue Torche.

By the way, I also need to update the Wiki docs, so I plan to do this in a couple of weeks.
Have fun,
Tortue Torche.


Add example of default guilds in app commands guide

Summary

Adds examples for setting default guilds for app commands to the docs guide.
Examples include using bot constructor, plugin constructor, and command decorator.
This seems to be a common question in the server.
Checklist

[x] I have run nox and all the pipelines have passed.

May be useful to mention that if you set command guilds or plugin default enabled guilds to an empty tuple then the relevant command(s) will be global even if the BotApp instance has default_enabled_guilds specified

yeah that's a good tip


Version 3.0 Update

Looks awesome. Excited to get this deployed.

@antonargunov Sorry to be annoying but can you update the screenshot of the prefab with the new settings config? I can change the readme here.

@aaustin I updated screenshop

Let's do this 👍

@aaustin @antonargunov Hey guys, one thing i noticed is the fact, that you are adding "https" schemes depending on the custom domain or live app links. But when i look into my branchdashboard the marketing links are not https but http:

As you can see this is only the case when using real custom domains. When using the default stuff which branch provides you with, it remains a https adress.
I dont know whethe or not that is a problem, but i was changing the manifest to http manually just to be sure it works properly.

This is what i mean inside the manifest:

Im changing it to http just before i build it because my marketing links are http adresses

Tagged this in an issue to pull it out of this thread and PR https://github.com/BranchMetrics/unity-branch-deep-linking/issues/43


[config] include the default user configuration header

ot-nrf528xx uses the compile option
-DNRF_802154_PROJECT_CONFIG=\"platform-config.h\" to specify the
Nordic library configuration file. Some build systems do not support this
usage.
This commit includes the default user implemented configuration header
file to avoid specifying the configuration file.

LGTM 👍 we will incorporate the change to RD.
Just for my curiosity, could you elaborate on the build system that does not allow to specify the define? We do support a lot of different compilers/IDEs and indeed sometimes the " character has to be prepended with strange patterns of backslashes 😄

Google has an internal build system. This internal build system doesn't support using the -D to specify the header file.


feat: add TB and LR tree view to the dependency viewer

This adds a tree view to the dependency viewer.

Toggle to switch between TB and LR view
Toggle to hide pure markdown (enabled by default)
On double click will focus on that cell in the editor
On single click for a node or edge will show a popup for description
Some bug fixes to the minimap view (not much visually changed here)

Areas of improvement

the top buttons design
the panel design

Future work, pending feedback:

show the flow of execution while nodes are running
show staleness in the DAG
more settings (currently can hide "pure markdown" cells)

The fit view button is nice. Is it possible to automatically resize/fit view as the pane is dragged?

I have this on the minmap. i didnt like it as it could move your state/position unexpectedly. but if you don't think its that jarring, i can add it

I'm unable to click on edges in the mini-map. Can we support that?

I didn't port this over. i will, but the edges kinda overlap so its not super useful, but i can for parity.

In the future, maybe (not this PR): add an option to show mo edges?

Yea I can, also can hear from feedback

The fit view button is nice. Is it possible to automatically resize/fit view as the pane is dragged?

actually - i can fit on drag


Workaround for CI host memory limit

Adds line
sudo prlimit -lunlimited --pid $$

to .github/workflows/ci.yml
Proof that this works:
Fails: https://github.com/nod-ai/iree-amd-aie/pull/332
Passes: https://github.com/nod-ai/iree-amd-aie/pull/330

With this workaround, can we add SD3 tests to ci now? https://github.com/nod-ai/iree-amd-aie/pull/286

With this workaround, can we add SD3 tests to ci now? #286

In theory yes, although it'll be slow. Let's be selective. I'm also working on making the baseline computation faster.


split radial scale lineArc setting into two settings

labelPoints controls the visibility of angle lines and point labels
gridLines.circular toggles how the radial lines are drawn. When false, straight lines are drawn. When true, circular lines are drawn.
Allows creating charts that look like:

Resolves #3082
API Change
This is technically a breaking API change since the old setting, lineArc is no longer used. I don't know if this will cause problems since I think this setting is only used internally and it is not well documented.

Made the changes suggested above. For now, I just use opts.angleLines.display since there is no opts.pointLabels.display setting. I can add the second setting if we want it. I think the logic would then change to be opts.angleLines.display || opts.pointLabels.display since we'd want the behaviour if there are no lines but there are labels and vice versa.

User should be able to choose to display lines without labels and vice-versa, so angleLines.display and pointLabels.display should be independent, setting one should not force display the other one, meaning that if we introduce pointLabels.display later, it will be a breaking change! Or I misunderstood your point.
Else, if displaying labels depends on displaying lines, pointLabels should be a child of angleLines: angleLines.labels.display.

Agreed, I will add the pointLabels.display setting. I think users will want to do this independently of the lines so we should support it.

Added the pointLabel.display setting and used it accordingly. Removed the 2 spurious references to labelPoints in the docs

@simonbrunel when you get a chance, can you review again?

Looks good, I would also add support for angleLines: false and pointLabels: false as shortcut for both *.display: false (as we have for legend / title).


[Help Wanted] Mobile Usability issues detected on https://developers.mattermost.com/

See below

Unfortunately the report doesn't contain which pages are causing these issues, so this ticket will involve

investigating where the issues occur
resolving the issues

I will try it.

Sorry, have no ideia where this is happening.

@JorgeMadson thank you for helping investigate!
@justinegeffen do you know if there's a way to find out where this mobility issue exists? I tried to investigate as well, but couldn't find where it's happening.

That is very odd. It's not in our search console properties (as you probably saw). I've raised it with the Marketing team.

I think I've found the issue, @jasonblais. It only happens on iPhone 5/SE and similar sized mobile phones.
Happy to submit a PR!

Thank you @lucievr! Would love to see a PR if you're open to help resolve


add admissionRequest in ctx

Changes

:broom: This PR associated the admissionv1.AdmissionRequest object the webhook received with the context.
adds a unit test

/kind

Fixes #2656

Release Note

Docs

We should remove the HTTP request from the context in favour of the AdmissionRequest

https://github.com/knative/pkg/blob/main/webhook/conversion.go#L59
converion webhook also uses this function - we would not be able to remove it I guess unless we also support Request *ConversionRequest

conversion webhook also uses this function - we would not be able to remove it I guess unless we also support Request *ConversionRequest

Yeah let's do that and add helpers for ConversionReview


feat(tutorial): complete step 1 - Hursley

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

tutorial step 1

Removed

nothing removed

:+1::skin-tone-2:   Looks good - I have recorded your completion of this step!


Create a text layout mechanism for interacting with large-ish bodies of text.

When working with larger bodies of text (like > 4 words), measuring the bounds of text gets really expensive. You can see here how slow the prog gets while editing text.

I think I could write a layout "engine" that only re-renders and re-measures each new word, and saves each processed word in a map keyed by the word itself.
Attached are the prof and ps files from a similar run.
Thu-Aug-18-09:48:52-PDT-2016 copy.txt
Thu-Aug-18-09:48:52-PDT-2016 copy.pdf

@Peaker - sorry to pull you in on my project, but you probably have experience with rendering lots of text with lamdu. Have you run into this problem before? What are you using to render and layout text in lamdu?

A little more spelunking and it looks like it's FTGL via graphics-drawingcombinators, added in https://github.com/lamdu/lamdu/commit/f9aa3a403aacfad9c967cec945662ad576cf0b78

Font rendering was far harder than I anticipated.
Text has no width, really, but a bounding box and an "advance".
We switched from FTGL which doesn't have subpixel rendering to freetype-gl with some minor modifications, that does. It's also a c codebase around libfreetype so easier to compile everywhere.
It does the width computations for us and I've not noticed slowness of text geometry computations, but I've not done extensive profiling either.

Thanks for that, I'm checking out freetype-gl now, which may make this ticket moot.
Sent from my iPhone

On Aug 18, 2016, at 11:15 AM, Eyal Lotem<EMAIL_ADDRESS>wrote:
Font rendering was far harder than I anticipated.
Text has no width, really, but a bounding box and an "advance".
We switched from FTGL which doesn't have subpixel rendering to freetype-gl with some minor modifications, that does. It's also a c codebase around libfreetype so easier to compile everywhere.
It does the width computations for us and I've not noticed slowness of text geometry computations, but I've not done extensive profiling either.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Lost my email and someone is messing around in my phone

Thanks for participating in the XGBoost community! We use https://discuss.xgboost.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking.  You are always welcomed to post on the forum first :)
Issues that are inactive for a period of time may get closed. We adopt this policy so that we won't lose track of actionable issues that may fall at the bottom of the pile. Feel free to reopen a new one if you feel there is an additional problem that needs attention when an old one gets closed.
For bug reports, to help the developer act on the issues, please include a description of your environment, preferably a minimum script to reproduce the problem.
For feature proposals, list clear, small actionable items so we can track the progress of the change.

Please do not post an issue with empty content.

Found it..thanks


[Release-1.27] - Bump containerd to >= v1.7.17

Backport fix for Bump containerd to >= v1.7.17

#10120

Validated - https://github.com/rancher/distros-test-framework/actions/runs/9356902283/attempts/1#summary-25755407260


app-pipeline should not continue with stages when one has an error

When a stage fails in the pipeline, the "Dev - Build Image" for example, the following stages should not be run. In the attached image the three stages after the failure all show green which, at least to me, is concerning. It leaves me wondering if something was in fact rolled out.

@thomasmckay it may look like it in OpenShift but in Jenkins it will show failure at Dev - Build Image and the following stages.

As Joe mentions this is a visualization bug in the console, and the log / accessing the Jenkins job should clarify what happened.
The bug is already reported in
https://github.com/openshift/origin-web-console/issues/2509 so I believe we can close it here.


Jongo future?

Hello folks!
My simple question is about the wonderful jongo:
@bguerout What is the future of jongo for the next releases?

Hello,
Fixing bugs as fast as possible with new semantic versioning.
Moving to new MongoDatabase API (lot of work)

See more informations about this topic in #254


What changed between alpha-8-5340 and beta-1 regarding arrays

I was trying to upgrade reiz to use edgedb beta-1/2 in the weekend though I guess I burnt a lot of time while investigating some queries resulting in an empty set instead of what is expected from them. This only happened when running under the 1.0-beta.1+gc654bc4cd.d20210222 but not 1.0-alpha.8+dev.5340.g76e0688b. Here is a reproducer;
CREATE DATABASE test_reiz;
\c test_reiz;

START MIGRATION TO {
    module ast {
        type arguments {
            multi link posonlyargs -> arg;
            multi link args -> arg;
        }
        type arg {
            required property arg -> str;
        }
    }
};

POPULATE MIGRATION;
COMMIT MIGRATION;

INSERT ast::arguments {
    posonlyargs := {
        (INSERT ast::arg { arg := 'bar' })
    },
    args := {
        (INSERT ast::arg { arg := 'baz' })
    }
};

SELECT ast::arguments
FILTER (
    WITH
        sequence_50150f83 := array_agg(.posonlyargs),
        sequence_12faedad := array_agg(.args)
    SELECT (
        len(sequence_50150f83) = 1
        AND len(sequence_12faedad) = 1
        AND sequence_50150f83[0].arg = 'bar'
        AND sequence_12faedad[0].arg = 'baz'
    )
);

Expected screenshot;

Current result;

As it can be seen, the select returns the proper value under alpha-8 but returns an empty under beta-1. This seems like a really weird behavior, but I don't know when exactly it got broken. (OS: ubuntu 20)

This is an unfortunate regression from 1ee59553667b5922798291f40d14750f2ec65866, which apparently wasn't caught by the test suite.


A new way of checking updates

Currently we have the @Updatifier annotation and the UpdatifierService. I understand this was made before @windy1 introduced the Asset API. I have been messing with the Asset API and have managed to think of a way that will allow plugin devs not even depend on Updatifier and still manage to have the integration. So here it goes: (Warning: Big wall of text)

Every plugin can have a file in the assets/<pluginId>/ called updatifier.conf which can have contents similar to this:
############################
# Support for Ore
############################
# Basically a true or false. Since all
# plugins have a unique id on ore,
# this will allow just that one line
# and plugins can get updates.
############################
ore : true
############################
# Support for GitHub
############################
# Same as the annotation/ service
############################
github : {
    repoOwner: <user/org>
    repoName: <repo>
    version: <version>
}

Use Cases

Allows developers to have support for Updatifier without having to depend on it.
Makes the plugin more extendable as more services like maven, bitbucket can be added.
Other usecases that I can't think of right now :confused:

This can allow for the Updatifier API to be removed(maybe deprecate first :yum:)

I would love discussion on this.
Edit by @liach:
Fixed a wrong poke...

This looks like a really interesting idea! Thanks for suggesting it, I will definently think about implementing it.
Pinging @liach to take a look at this.

So I thought about how to make the github section more refined github section.
github : {
    owner : <repo_owner>
    name : <repo_name>
    meta : {
      version : <current_version>
      prefix : "v"
      suffix : "suffix"
    }
}

the meta data is optional. prefix and suffix are completely used to format the url string. If version is given, then then that version is used else plugin's version from plugincontainer is used.

@Flibio I want to start working on this... Any changes you want in here?

Nothing specific, just what you described above.

I am switching from HOCON to JSON.

closing as ore will now supersede this


Feature Request: search organization repos

Feature Requested
Hi, thanks for the great work. I started using this project and so far so good.
I think add the following two options to this project would be great:

input github token via configure workflow of alfred ui
using the input access token, search organization repos

Do you have plan for this?
Thanks in advance.
Relevant Screenshot
No response
Checklist

[X] The feature would be useful to more users than just me.

Hi, in the latest version, I added the ability to specify a $GITHUB_TOKEN via Alfred workflow configuration as an alternative to exporting it in your .zshenv: https://github.com/chrisgrieser/gitfred/releases/download/1.1.0/gitfred.alfredworkflow
For the organization repos, I am not too sure about it. Reason being, that I simply do not use GitHub organization, and are thus not familiar with what would be needed here. I am open to PRs adding support for that though.


document on ssr = true is not defined

Hello
I'm using nuxt and would like to know if its possible that there is currently a bug in vue-meta regarding of a document call on SSR: vue-meta line 825:
function _updateClientMetaInfo (options) {
  if ( options === void 0 ) options = {};

  var ssrAttribute = options.ssrAttribute;

  /**
   * Performs client-side updates when new meta info is received
   *
   * @param  {Object} newInfo - the meta info to update to
   */
  return function updateClientMetaInfo (newInfo) {
    var htmlTag = document.getElementsByTagName('html')[0];

  var htmlTag = document.getElementsByTagName('html')[0];
                  ^

ReferenceError: document is not defined

If ssrAttribute is set, and the server tries to render, vue-meta throws error. Any idea if this intend to work like this? I posted this on nuxt as well: https://github.com/nuxt/nuxt.js/issues/449
Thanks

Not sure if related, but you can also have a look on my latest comment https://github.com/nuxt/nuxt.js/issues/449#issuecomment-290976803

Should be fixed with the last version (I will update nuxt.js soon)


Welcome page shows wrong app name when multiple apps are present

Steps to reproduce:
➜ lotus new bookshelf && cd bookshelf && bundle
➜ bundle exec lotus generate app admin
➜ bundle exec lotus server

Visit http://localhost:2300.
It shows this screen:

If you give a close look at the instructions they say:
bundle exec lotus generate action admin home#index --url=/

It reports admin instead of web as name.

Little help: error on this line :smile:

We should probably introspect env['PATH_INFO'] and decide the name of the application at the runtime.
Given two apps:
# config/environment.rb
Lotus::Container.configure do
  mount Admin::Application, at: '/admin'
  mount Web::Application, at: '/'
end

For request GET /, we should show "web", while for GET /admin we should pick "admin".
Hint: Application#path_prefix can be useful to solve this problem.


Review: Additional examples for other data

Dear authors,
I appreciated the documentation and associated paper. The simplicity of the implementation and seemingly overlapping functions and methods for the different data types is useful for the beginning.
I have some small comments relating to documentation which could help the lower level user adapt and utilise the project.
First, it would be helpful to also be able to replicate the examples in your research paper as they are slightly different to the example you provide on the repository.
While the API functions were very well documented,  there are two interrelated cases I think would greatly benefit the project.

Not being familiar with the xrarry python type I had to search a little while to be able access individual data, i.e., the specific EMG channel , this would be handy for those wanting to look at a specific channel for example

The examples provided on the repository as well as within your research paper are centered around EMG data. Given you present the toolbox as a complete package for all biomechanical data - some additional example for Markers and Angles would be nice to see.

I appreciated the documentation and associated paper. The simplicity of the implementation and seemingly overlapping functions and methods for the different data types is useful for the beginning.

We would like to thank you for those kind words.

First, it would be helpful to also be able to replicate the examples in your research paper as they are slightly different to the example you provide on the repository.

We have kept exactly the same example as the one presented in the documentation here.
The only difference is in the first few lines when we do the muscle selection.
We wanted to omit these lines because they are entirely dependent on the file you are working with and we wanted to keep the example short for the paper.
It would have been difficult to distribute a c3d file with the paper so we chose to work with a dummy file that already contains the desired muscles.
Let us know if you want to add these lines to the paper example so that the two examples are exactly the same.

Not being familiar with the xarray python type I had to search a little while to be able access individual data, i.e., the specific EMG channel , this would be handy for those wanting to look at a specific channel for example

We agree that the data structure requires some instructions.
The documentation contains instructions for accessing the data, accessing metadata, doing calculations and graphics, etc.
We repeatedly mention the use of  xarray and refer users to their documentation, which contains much more information for manipulating the data.

The examples provided on the repository as well as within your research paper are centered around EMG data. Given you present the toolbox as a complete package for all biomechanical data - some additional example for Markers and Angles would be nice to see.

We completely agree and we will add the following example in the documentation:
This example consists of calculating the elbow joint angle from skin markers. It uses Markers, Angles and Rototrans.
rt_arm_in_global = Rototrans.from_markers(...)
rt_lower_arm_in_global = Rototrans.from_markers(...)

rt_arm_in_global_T = Rototrans.from_transposed_rototrans(rt_arm_in_global)
rt_lower_arm_in_arm = rt_arm_in_global_T * rt_lower_arm_in_global
angles = Angles.from_rototrans(rt_lower_arm_in_arm, seq)
angles.plot()

Thank you for the replies and the additional details provided, as well the links to the relevant documentation they were exactly the examples I was looking for.
From my point of view the changes and explanations you have given here sufficiently address my concerns


Add another call to ensure compatibility with zk 3.4

Prevents using container parents as it breaks compatibility with zk 3.4.x servers. This logic is ported from PrimarySelectorClient.

Codecov Report

Merging #14567 (7011b83) into master (ea4d766) will decrease coverage by 41.83%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master   #14567       +/-   ##
=============================================
- Coverage     41.83%    0.00%   -41.84%
=============================================
  Files          1494       20     -1474
  Lines         87696     6384    -81312
  Branches      10451     1608     -8843
=============================================
- Hits          36691        0    -36691
+ Misses        48021     6384    -41637
+ Partials       2984        0     -2984

Impacted Files
Coverage Δ

...r/src/main/java/alluxio/master/table/Database.java
0.00% <0.00%> (-14.34%)
:arrow_down:

.../src/main/java/alluxio/master/table/Partition.java
0.00% <0.00%> (-5.81%)
:arrow_down:

...rc/main/java/alluxio/worker/grpc/WriteRequest.java
0.00% <0.00%> (-5.55%)
:arrow_down:

.../src/main/java/alluxio/master/journal/Journal.java
0.00% <0.00%> (-3.84%)
:arrow_down:

...ter/src/main/java/alluxio/master/table/Domain.java
0.00% <0.00%> (ø)

...ain/java/alluxio/master/ZkMasterInquireClient.java

...luxio/exception/status/AlluxioStatusException.java

...ter/journal/JournalMasterClientServiceHandler.java

...c/main/java/alluxio/cli/fs/command/PinCommand.java

...ava/alluxio/underfs/ConsistentUnderFileSystem.java

... and 1469 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ea4d766...7011b83. Read the comment docs.

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.6 please