Default plugin DebugCommands causing Brackets 1.13 not to start up.

Hi Good Day
I have installed brackets 1.13 about a month ago and been having a issue with a default plugin called DebugCommands, this plugin is causing brackets not to start up, does anyone have the same issue ?.
I enabled and disabled each extension one by one to see which extension is causing the issue.
I am running Windows 10, Chrome Version 68.0.3440.106

There is no update in this extension since long. Can you please share your console log? Go to Debug -> Show developer tools
Then please paste that log here.

Hi navch, I had to enable plugin DebugCommands here is the console log as requested,
Less has finished and no sheets were loaded.
2/utils/ExtensionUtils.js:269 Default extension has been disabled on startup: DebugCommands
/command/KeyBindingManager.js:578 Failed to normalize Cmd-Shift-]
/command/KeyBindingManager.js:578 Failed to normalize Cmd-Shift-[
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - start
/utils/NodeDomain.js:144 [NodeDomain] Error loading domain "staticServer": timeout(anonymous function) @ /utils/NodeDomain.js:144
/utils/NodeDomain.js:144 [NodeDomain] Error loading domain "zaggino.brackets-eslint": timeout(anonymous function) @ /utils/NodeDomain.js:144
/extensibility/Package.js:579 [Extensions] Failed to connect to node Arguments[1](anonymous function) @ /extensibility/Package.js:579
/utils/NodeDomain.js:144 [NodeDomain] Error loading domain "AutoUpdate": timeout(anonymous function) @ /utils/NodeDomain.js:144
main.js:589 AutoUpdate : node domain could not be initialized.(anonymous function) @ main.js:589
https://s3.amazonaws.com/extend.brackets/registry.json?_=1534423114765 Failed to load resource: net::ERR_NETWORK_IO_SUSPENDED
https://health.brackets.io/healthDataLog Failed to load resource: net::ERR_NETWORK_IO_SUSPENDED
HealthDataManager.js:203 Error in sending Health Data. Response : undefined. Status : error. Error : (anonymous function) @ HealthDataManager.js:203
https://cc-api-data.adobe.io/ingest Failed to load resource: net::ERR_NETWORK_IO_SUSPENDED
HealthDataManager.js:232 Error in sending Adobe Analytics Data. Response : undefined. Status : error. Error : (anonymous function) @ HealthDataManager.js:232

Are you able to start brackets in this instance as per these logs DebugCommand is disabled in this brackets instance? Apart from this Node is not able to start. A lot of feature in brackets depends on Node but this should not cause any problem in brackets launch. I don't know why Node is not initialized. But If rest of the things are fine maybe you can try reinstalling.

Hi navch
I have reinstalled brackets 1.13 as per request, I am having an issue with brackets not starting up. I have copied and pasted my console output below.
Less has finished and no sheets were loaded.
/command/KeyBindingManager.js:578 Failed to normalize Cmd-Shift-]
/command/KeyBindingManager.js:578 Failed to normalize Cmd-Shift-[
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - start
main.js:313 AutoUpdate : updateHelper.json cannot be parsed, does not exist
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - send,,{"method":"Runtime.evaluate","params":{"expression":"_LD.hideHighlight()"},"id":1}
NodeDebugUtils.js:114 [node-log 3:37:22 PM] WebSocketServer - received - {"type":"connect","url":"http://<IP_ADDRESS>:6169/HTML and CSS/index.html"}
NodeDebugUtils.js:114 [node-log 3:37:22 PM] emitting connect event
NodeDebugUtils.js:114 [node-log 3:37:22 PM] WebSocketServer - received - {"type":"message","message":"{"method":"DocumentRelated","related":{"scripts":{"http://<IP_ADDRESS>:6169/HTML and CSS/main.js\":true},\"stylesheets\":{\"http://<IP_ADDRESS>:6169/HTML and CSS/main.css\":[\"http://<IP_ADDRESS>:6169/HTML and CSS/main.css\"]}}}"}
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - connect - [1,"http://<IP_ADDRESS>:6169/HTML and CSS/index.html"]
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - message - [1,"{"method":"DocumentRelated","related":{"scripts":{"http://<IP_ADDRESS>:6169/HTML and CSS/main.js\":true},\"stylesheets\":{\"http://<IP_ADDRESS>:6169/HTML and CSS/main.css\":[\"http://<IP_ADDRESS>:6169/HTML and CSS/main.css\"]}}}"]
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - send,1,{"method":"Runtime.evaluate","params":{"expression":"_LD.hideHighlight()"},"id":2}
NodeDebugUtils.js:114 [node-log 3:38:26 PM] WebSocketServer - received - {"type":"message","message":"{"id":2}"}
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - message - [1,"{"id":2}"]
Failed to clear temp storage: It was determined that certain files are unsafe for access within a Web application, or that too many calls are being made on file resources. SecurityError
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - send,1,{"method":"Runtime.evaluate","params":{"expression":"_LD.hideHighlight()"},"id":3}
NodeDebugUtils.js:114 [node-log 3:41:05 PM] WebSocketServer - received - {"type":"message","message":"{"id":3}"}
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - message - [1,"{"id":3}"]
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - send,1,{"method":"Runtime.evaluate","params":{"expression":"_LD.hideHighlight()"},"id":4}
NodeDebugUtils.js:114 [node-log 3:41:35 PM] WebSocketServer - received - {"type":"message","message":"{"id":4}"}
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - message - [1,"{"id":4}"]

Not really sure why brackets is not starting. Are you able to start brackets after disabling any extension? Yes then which extension? Can you please share some more details like this happens on any project launch or normal brackets open? What happens if you delete %appdata%/brackets and then relaunch?

Hi navch, I managed to change the the default language for brackets by going to Debug->switch language from system default to English UK. Brackets start up with no error messages but today brackets took three attempts to start up, I may have a buggy extension I have included my console output below,
Less has finished and no sheets were loaded.
2/command/KeyBindingManager.js:747 Cannot assign Tab to brackets_html_boilerplate.expandWithTab. It is already assigned to brackets_html_boilerplate.expandWithTab_addBinding @ /command/KeyBindingManager.js:747
/utils/ExtensionLoader.js:227 [Extension] failed to load C:/Users/Andrew_2/AppData/Roaming/Brackets/extensions/user/brackets-beautify - Error: Load timeout for modules: i18n!nls/strings_unnormalized4,i18n!nls/strings,nls/strings
http://requirejs.org/docs/errors.html#timeouterrback @ /utils/ExtensionLoader.js:227
/utils/ExtensionLoader.js:227 [Extension] failed to load C:/Users/Andrew_2/AppData/Roaming/Brackets/extensions/user/brackets-display-shortcuts - Error: Load timeout for modules: i18n!nls/strings_unnormalized4,i18n!nls/strings,nls/strings
http://requirejs.org/docs/errors.html#timeouterrback @ /utils/ExtensionLoader.js:227
/utils/ExtensionLoader.js:227 [Extension] failed to load C:/Users/Andrew_2/AppData/Roaming/Brackets/extensions/user/ivogabe.icons - Error: Load timeout for modules: dist/preset-dictionary,dist/user-dictionary
http://requirejs.org/docs/errors.html#timeouterrback @ /utils/ExtensionLoader.js:227
/utils/ExtensionLoader.js:227 [Extension] failed to load C:/Users/Andrew_2/AppData/Roaming/Brackets/extensions/user/dnbard.extensions-rating - Error: Load timeout for modules: vendor/q,achievements/achievement,locale/en-US,locale/it,locale/ro,locale/es,locale/ca-ES,locale/sv-SE,locale/tr,locale/uk,locale/de-DE,locale/fr,locale/ru,locale/zh-TW,locale/pl
http://requirejs.org/docs/errors.html#timeouterrback @ /utils/ExtensionLoader.js:227
/command/KeyBindingManager.js:578 Failed to normalize Cmd-Shift-]
/command/KeyBindingManager.js:578 Failed to normalize Cmd-Shift-[
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - start
/utils/NodeDomain.js:144 [NodeDomain] Error loading domain "webSocketTransport": timeout(anonymous function) @ /utils/NodeDomain.js:144
/utils/NodeDomain.js:144 [NodeDomain] Error loading domain "nodeSocketTransport": timeout(anonymous function) @ /utils/NodeDomain.js:144
/utils/NodeDomain.js:144 [NodeDomain] Error loading domain "fileWatcher": timeout(anonymous function) @ /utils/NodeDomain.js:144
/filesystem/FileSystem.js:967 Failed to watch root:  C:/Users/Andrew_2/Documents/Desktop/Programing/ timeout
/project/ProjectManager.js:800 Error watching project root:  C:/Users/Andrew_2/Documents/Desktop/Programing/ timeout(anonymous function) @ /project/ProjectManager.js:800
/utils/NodeDomain.js:144 [NodeDomain] Error loading domain "launcher": timeout(anonymous function) @ /utils/NodeDomain.js:144
/utils/NodeDomain.js:144 [NodeDomain] Error loading domain "FindInFiles": timeout(anonymous function) @ /utils/NodeDomain.js:144
/utils/NodeDomain.js:144 [NodeDomain] Error loading domain "zaggino.brackets-eslint": timeout(anonymous function) @ /utils/NodeDomain.js:144
/extensibility/Package.js:579 [Extensions] Failed to connect to node Arguments[1](anonymous function) @ /extensibility/Package.js:579
/utils/NodeDomain.js:144 [NodeDomain] Error loading domain "AutoUpdate": timeout(anonymous function) @ /utils/NodeDomain.js:144
main.js:589 AutoUpdate : node domain could not be initialized.(anonymous function) @ main.js:589
If I delete %appdata%/brackets, brackets starts up with no issues, I am running brackets as a window user not as an administrator, does brackets need administrator rights to run ?.

Hi navch
I have disabled the following extensions within brackets they are as following,
1.Beautify.
2.Brackets Icons.
3.Display Shortcuts.
4.Extensions Rating.
5.HTML Boilerplate.
The following extensions I have not disabled are as following,
1.Monokai.
2.TypeScript.
Here is my console output from within brackets,
Less has finished and no sheets were loaded.
/command/KeyBindingManager.js:578 Failed to normalize Cmd-Shift-]
/command/KeyBindingManager.js:578 Failed to normalize Cmd-Shift-[
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - start
main.js:313 AutoUpdate : updateHelper.json cannot be parsed, does not exist
2http://<IP_ADDRESS>:9222/json Failed to load resource: net::ERR_CONNECTION_REFUSED
NodeDebugUtils.js:114 [node-log 6:27:05 PM] webSocketTransport closed
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - send,,{"method":"Runtime.evaluate","params":{"expression":"_LD.hideHighlight()"},"id":1}
NodeDebugUtils.js:114 [node-log 6:27:39 PM] WebSocketServer - received - {"type":"connect","url":"http://<IP_ADDRESS>:3433/index.html"}
NodeDebugUtils.js:114 [node-log 6:27:39 PM] emitting connect event
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - connect - [1,"http://<IP_ADDRESS>:3433/index.html"]
NodeDebugUtils.js:114 [node-log 6:27:39 PM] WebSocketServer - received - {"type":"message","message":"{"method":"DocumentRelated","related":{"scripts":{},"stylesheets":{"http://<IP_ADDRESS>:3433/main.css\":[\"http://<IP_ADDRESS>:3433/main.css\"]}}}"}
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - message - [1,"{"method":"DocumentRelated","related":{"scripts":{},"stylesheets":{"http://<IP_ADDRESS>:3433/main.css\":[\"http://<IP_ADDRESS>:3433/main.css\"]}}}"]
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - send,1,{"method":"Runtime.evaluate","params":{"expression":"_LD.hideHighlight()"},"id":2}
NodeDebugUtils.js:114 [node-log 6:27:49 PM] WebSocketServer - received - {"type":"message","message":"{"id":2}"}
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - message - [1,"{"id":2}"]
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - send,1,{"method":"Runtime.evaluate","params":{"expression":"_LD.hideHighlight()"},"id":3}
NodeDebugUtils.js:114 [node-log 6:32:18 PM] WebSocketServer - received - {"type":"message","message":"{"id":3}"}
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - message - [1,"{"id":3}"]
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - send,1,{"method":"Runtime.evaluate","params":{"expression":"_LD.hideHighlight()"},"id":4}
NodeDebugUtils.js:114 [node-log 6:34:06 PM] WebSocketServer - received - {"type":"message","message":"{"id":4}"}
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - message - [1,"{"id":4}"]
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - send,1,{"method":"Runtime.evaluate","params":{"expression":"_LD.hideHighlight()"},"id":5}
NodeDebugUtils.js:114 [node-log 6:35:03 PM] WebSocketServer - received - {"type":"message","message":"{"id":5}"}
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - message - [1,"{"id":5}"]
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - send,1,{"method":"Runtime.evaluate","params":{"expression":"_LD.hideHighlight()"},"id":6}
NodeDebugUtils.js:114 [node-log 6:35:22 PM] WebSocketServer - received - {"type":"message","message":"{"id":6}"}
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - message - [1,"{"id":6}"]
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:84 NodeSocketTransport - send,1,{"method":"Runtime.evaluate","params":{"expression":"_LD.hideHighlight()"},"id":7}
NodeDebugUtils.js:114 [node-log 6:36:28 PM] WebSocketServer - received - {"type":"message","message":"{"id":7}"}
/LiveDevelopment/MultiBrowserImpl/transports/NodeSocketTransport.js:67 NodeSocketTransport - event - message - [1,"{"id":7}"]
I hope this helps you.

Hi navch
Brackets is opening on it's first attempt with no issues, I have disabled the following extensions, they are as follows,

Beautify.
Display Shortcuts.
Extensions Rating.
HTML Boilerplate.

The following extension are enabled, they are as follows,
1.Brackets Icons.
2.Monokai Theme.
3.TypeScript.
I will work through the disabled extensions to see which one is causing the issue, Thank you for your help. I will close this issue.

Sure @Andrew-Snell Great Job. Please update here as well about extension which i causing this problem

Hi @navch
I have been running brackets with the Beautify extension enabled and causing brackets not to load correctly, I have disabled this extension and brackets loaded five times in a row without and issue.
Regards
Andrew

Hi @Andrew-Snell This is working fine for me, As per the extension's use guide
`Brackets Beautify can be run manually on the whole file or on a selection. Use the Toolbar Button with the wand icon, the menu entry Edit > Beautify, the context-menu entry Beautify, or one of the keyboard shortcuts Ctrl-Alt-B (Windows/Linux), Ctrl-Shift-L (Windows), Cmd-Shift-L (Mac), or define your own.
Alternatively it can be enabled to run automatically on save. Use the menu entry Edit > Beautify on Save or the more advanced settings to activate.`
This extension should not kick in on load. Could you please try to debug this?

Hi @navch
I have enabled Beautify extension and will post debug info.
Regards
Andrew

Hi @navch
I have been using brackets for the past two months with no issues, as result I am closing this issue, Thank you for your help.
Regards
Andrew Snell


HTML Comments w/URL Incorrectly Colored

I started a sep. issue with JS having the same problems, but it also happens with HTML comments. Anything in a comment should be grayed out like the screenshot attached.

@grayghostvisuals Thanks..
This should also be fixed with https://github.com/atom/solarized-dark-syntax/pull/72. Gonna be in Atom 1.12.


Apidoc experimental tag

Replaces / closes #11702, #10544
@jahow Please have a look if the correct functions / classes are tagged or any are missing.

I'm still not convinced we want to re-introduce api stability levels, since we removed them for good reason.
An alternative would be to provide a legacy build that exposes the whole library, not just symbols marked @api. Something like ol-full.js.

@MoonE If you agree, I'd like to see #11715 as a replacement for this. #11715 does not address the part of the problem that experimental features are not documented. But I'd see that as motivation to improve the experimental features so they don't need to be called "experimental" any more.


React.createElement: type is invalid when running tests in nx workspace project

Describe the bug
When a test is run under nx workspace react-native app the tests return multiple warnings React.createElement: type is invalid...
To Reproduce
Steps to reproduce the behaviour:

Create nx workspace npx create-nx-workspace@latest my-nx-workspace --preset=react-native --package-manager=yarn
Fill in application name to myapp when asked and select no for cloud builds
cd my-nx-workspace
Install nativebase and add any compoennts into App.tsx in apps/myapp
yarn nx test myapp
See errors

Expected behaviour
When running a test using yarn nx test myapp the tests finish fine without any redundant warnings/errors
CodeSandBox/Snack link
It would be easier for us to debug if you can reproduce the error in a codesandbox link or a snack link. You can use the codesandbox template/snack template.
Logs
╰─$ nx test myapp

> nx run myapp:test
  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at questionIconPath.tsx:6.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/questionIconPath.tsx:9:9)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at questionIconPath.tsx:11.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/questionIconPath.tsx:14:9)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at questionIconPath.tsx:16.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/questionIconPath.tsx:16:65)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at questionIconPath.tsx:5.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/questionIconPath.tsx:5:3)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Check.tsx:9.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Check.tsx:9:23)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Check.tsx:8.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Check.tsx:8:5)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Chevron.tsx:9.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Chevron.tsx:9:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Chevron.tsx:10.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Chevron.tsx:10:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Chevron.tsx:8.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Chevron.tsx:8:5)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Close.tsx:14.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Close.tsx:15:9)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Info.tsx:14.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Info.tsx:14:57)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Info.tsx:15.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Info.tsx:15:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Info.tsx:16.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Info.tsx:16:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Info.tsx:8.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Info.tsx:11:21)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Minus.tsx:8.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Minus.tsx:8:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Minus.tsx:7.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Minus.tsx:7:5)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Sun.tsx:15.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Sun.tsx:15:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Sun.tsx:16.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Sun.tsx:16:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Sun.tsx:17.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Sun.tsx:17:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Sun.tsx:18.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Sun.tsx:18:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Sun.tsx:19.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Sun.tsx:19:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Sun.tsx:20.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Sun.tsx:20:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Sun.tsx:21.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Sun.tsx:21:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Sun.tsx:22.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Sun.tsx:22:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Sun.tsx:23.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Sun.tsx:23:7)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at Sun.tsx:8.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Sun.tsx:11:19)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at ThreeDots.tsx:9.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/ThreeDots.tsx:9:15)

  console.error
    Warning: React.createElement: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

    Check your code at ThreeDots.tsx:8.
        at App (/Users/user/Documents/Projekty/custom/nx-workspace/apps/myapp/src/app/App.tsx:15:64)

      at printWarning (../../node_modules/react/cjs/react.development.js:220:30)
      at error (../../node_modules/react/cjs/react.development.js:196:5)
      at Object.createElementWithValidation [as createElement] (../../node_modules/react/cjs/react.development.js:2215:7)
      at Object.<anonymous> (../../node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/ThreeDots.tsx:8:5)

[BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB.

Platform

NativeBase version [3.2.2]
Device: [testing in jest]
OS: [-]
Browser [-]
Browser version [-]
React Native version [0.62.2]
Expo sdk version [-]
node [17.0.2]
yarn [1.22.17]

Additional information

Add any other context about the problem here.
Is the bug present in both iOS and Android or in any one of them?
If you want your issue to be looked at quicker, please attach a snack reproducible with your issue. Makes it easier for us!

@aqos156 Thanks for reporting, we'll look into this.

@mayank-96 any news? we are experiencing this as well.

I've been able to remove the warning by using ts-jest and by removing the svg-mock in moduleNameMapper in the jest.config.js. I realised the issues were stemming from native-base icons which are probably svg based.
What confuses me the most is the stack trace referencing a file that doesn't exists:
node_modules/native-base/lib/commonjs/components/primitives/Icon/Icons/Sun.tsx
lib only contains js files.

Can you try adding a \\ in front of the .svg like so:
  moduleNameMapper: {
    '.svg': '@nrwl/react-native/plugins/jest/svg-mock',
  },

  moduleNameMapper: {
    '\\.svg': '@nrwl/react-native/plugins/jest/svg-mock',
  },

The above solutions works for me. Here's a function that you can apply to your custom library generator:
function fixSvgModuleNameMapper(tree, root) {
  const path = joinPathFragments(root, "./jest.config.js")
  const config = tree.read(path, "utf-8")

  const svgModuleNameMapperIndex = config.indexOf(
    `".svg": "@nrwl/react-native/plugins/jest/svg-mock"`
  )

  const updatedConfig = applyChangesToString(config, [
    {
      type: ChangeType.Insert,
      index: svgModuleNameMapperIndex + 5,
      text: "$",
    },
    {
      type: ChangeType.Insert,
      index: svgModuleNameMapperIndex + 1,
      text: "\\\\",
    },
  ])

  tree.write(path, updatedConfig)
}

Thank you for sharing these workarounds, everyone -- issue is still relevant. The \\.svg$ adjustment inside jest.config.ts, specifically, worked for me.

Closing this issue for now. Please feel free to reopen.


Error in the challenges solving

error in solve challenge if maximum  belt higher than my current belt

fixed in the follwing commit => 18d6c9027837598a2949b0aae99fcf755b5e23fd
thanks Zidan


Add basic update notification mechanism

Problem statement
Since we're using react router, when we navigate to any page, the html and js is not reloaded.
Until user force-refreshes the page, the app and the backend versions will be divergent.
Solution

FINGERPRINT=uuid is added during the build to .env
Caddy returns this UUID as X-Fingerprint header for API responses
UI tracks this header for /status request
when the header value is changed, most links in UI will refresh the page once, transparently to the user

Testing
Tested on staging
Deploy action1:
https://github.com/spaceshelter/orbitar/actions/runs/5096833950/jobs/9162954788
Deploy action2:
https://github.com/spaceshelter/orbitar/actions/runs/5096844123
Added headers:

Checked that page is refreshed on link click after the deployment.

Also two minor changes creeped in:

НОВОЕ renamed to "NEW"
fixed key error in paginator

@Lexy2 has a good point, it makes sense to reload the page transparently to the user (e.g. on certain navigation events). Marking as draft for now.

Testing changed fingerprint:

Add FINGERPRINT=xxx to your .env file
Load the pages, click links, observe that the pages do not reload. Keep the page open.
Check that the returned header from API calls is X-Fingerprint: xxx
Change the fingerprint value in the .env file to FINGERPRINT=yyy
Stop Caddy: docker stop orbitar-caddy-1
Kill Caddy: docker rm orbitar-caddy-1
Run docker-compose -f docker-compose.dev.yml up caddy to reload
Click any link on the orbitar page.
Observe that the page is reloaded.

Otherwise looks good, I like the new update mechanism way more than an explicit Reload button.

Otherwise looks good, I like the new update mechanism way more than an explicit Reload button.

I thought more about it, there is a chance to simplify its implementation. Will try today.

@Lexy2 , I simplified the reloading logic (add addressed your comment), please check.

If someone has a page open and a server update is deployed, then when this person clicks a link to open a post, for example, the link will open and then the page will reload.
Which is not nice, but much better than attaching an observable to each link tag.


Introduce ClusterBundle API as a copy of Bundle

Initial PR to implement https://github.com/cert-manager/trust-manager/pull/485 - when the design is approved.
/hold

/test pull-trust-manager-smoke


Unnecessary optional for createEntity

It doesn't seem that there are any circumstances in which createEntity() could possibly return Empty, it should always be creating an entity, and the SPAWNING is where the failure would occur
Should be non optional.
Posting per blood recommendation

createEntity would fail if you attempt to create a EntityTypes.PLAYER. Would also fail if the position is not valid (e.g. not on a block for hanging entities)

Throwing an exception with a description of the error may be more usefull and devfriendly than returning an optional.

I like the optional better, as that signifies there are conditions to creating entities, and one won't be created if those conditions aren't met.

If we just return Optional.empty() when conditions are not respected, we will not know what is missing to create the entity. You will see lot of new devs asking for help in the forum because they can't create an entity and they don't know why.

When posted, we hadn't realized that A case did exist for a failure, the Player entity.  Even an invalid location was believed to only throw errors during the spawning process.  But since there is this fringe case that could produce a null, in accordance to Rule #1 make sure any null can never be exposed, keeping this wrapped in optional is fine, and given the knowledge, I for one will just take it straight to the get() without worrying about checking and unwrapping when creating every other entity except a player...
I wash my hands of the complaint/observation on the grounds that one case was presented that we could not think of that counterproved it, thus defeating the reason for posting;  but if others wish to run with this idea for discussing optional vs a thrown exception feel free, but I give the devs the power to shut this open issue down when they want, and will not close it myself.

I hate to say this, but, I have had this method in mind to add a required Cause, much like the reasoning that spawnEntity requires a Cause. The reasoning is that plugins may decide to cancel the entities construction, likewise, spawn limits can be enforced by plugins, and a whole lot of other reasons.

Yegegorix - to be honest, 99% of the optional.empty returns could have that same argument - "Why?"
Instead say "hmm, think of that like a null, why can it be null in this case after all?"  I dont see it as any special situation different from any other empty returning a failure or empty.

What I'm gathering though, is that we could very well return a sort of tristate object with the optional entity, so you can get the resulting entity still wrapped in an Optional, AND still get the reason why your entity is null, namely from an event, position, etc.

Closing as the API is as it is intended to be.

I do not agree. createEntity failing will never happen during normal use, it is only in exceptional cases indicative of some failure in the plugins logic (namely trying to spawn players and if an exception is thrown in the entity ctor) and hence should be error cases.
There is no case where a call to createEntity is going to fail 'some of the time'. Either it will work every time or the plugin has an error and it will fail every time.

@Deamon5550
Very well but not acceptable to let a server crash happen (and any damage that occurs cause of it) when the creation of said Entity can be safely performed. The only drawback is developer feedback on why their EntityTypes.PLAYER failed to spawn (lol).
I simply will never accept crashing the server intentionally if an API is used wrongly. That is when API is re-visited and re-designed.

Something like 99% of uses originate from event listeners or scheduled tasks which catch and report exceptions rather than crashing the server. An API being wrongly used is a developer error and is exactly when you want to throw errors (hence why we use checkNotNull/checkArgument rather than just putting a little log message and returning).

@Zidane while removing the optional would result in an exception being thrown, it would definitely not throw an exception that would crash the server. If we wanted to avoid exceptions altogether, we'd never checkNotNull etc. Using the API wrongly in this case is valid to say that the only time we'd never return a created entity is if the API was used wrongly, in which case we most definitely want to print an exception. In essence, let bad code fail.

@gabizou @Deamon5550
Good points from both of you' I've reconsidered and this can be added to 5.0's changelog.


[PE-D][Tester B] Unclear if the time and date for the upcoming delivery command is inclusive or non-inclusive of the time itself.

When the due date is exactly on the date and time requested, they are not shown in the upcoming command as shown below. The first screengrab is of the command and the second screengrab is the result.

The app works as intended when the input is 17:01 for the time instead so i suspect the input was probably non-inclusive. However, it would be recommended to also specify this in the user guide.

Labels: type.DocumentationBug severity.Medium
original: RezwanAhmed123/ped#13

Mentioned inclusivity in UG


Cannot import tensorflow 1.0.1 after compiled from source

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): y
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 1.0.1
Python version: 2.7
Bazel version (if compiling from source): 0.5.3
CUDA/cuDNN version: x
GPU model and memory: x
Exact command to reproduce: import tensorflow

Describe the problem
I successfully built tensorflow 1.0.1 from source using optimization flags with the command bazel build -c opt --copt=-mmmx --copt=-msse --copt=-msse2  -k //tensorflow/tools/pip_package:build_pip_package. After that, I activated my virtualenv and issued a pip install /tmp/tensorflow_pkg/tensorflow-1.0.1-cp27-cp27mu-linux_x86_64.whl to install in the virtual env this compiled from source version. When I try to import tensorflow in the python code, I receive a error (showing it with -v flag from python interpreter activated) showed below in the source code / logs session.
Source code / logs
# /home/ubuntu/miniconda3/envs/tf_exp/lib/python2.7/site-packages/numpy/ma/extras.pyc matches /home/ubuntu/miniconda3/envs/tf_exp/lib/python2.7/site-packages/numpy/ma/extras.py
import numpy.ma.extras # precompiled from /home/ubuntu/miniconda3/envs/tf_exp/lib/python2.7/site-packages/numpy/ma/extras.pyc
# /home/ubuntu/miniconda3/envs/tf_exp/lib/python2.7/site-packages/tensorflow/python/pywrap_tensorflow.pyc matches /home/ubuntu/miniconda3/envs/tf_exp/lib/python2.7/site-packages/tensorflow/python/pywrap_tensorflow.py
import tensorflow.python.pywrap_tensorflow # precompiled from /home/ubuntu/miniconda3/envs/tf_exp/lib/python2.7/site-packages/tensorflow/python/pywrap_tensorflow.pyc
dlopen("/home/ubuntu/miniconda3/envs/tf_exp/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow.so", 102);
Illegal instruction (core dumped)

@flavioschuindt Can you retry from the latest sources?

@tatatodd Ok, I had some progress here. I tried all the stpes above in a VirtualBox ubuntu machine. It seems that VirtualBox is not fully activating all of these CPU instructions, so in runtime (import tensorflow) I got this error. Do you know how to fully activate it in VirtualBox?

@flavioschuindt In your description, I do not see that if you ran this command to build the pip package:
bazel-bin/tensorflow/tools/pip_package/build_pip_package /tmp

Without this, it is possible you have a stale pip package and not building the latest one.

Yes, I ran this command. The whl package was properly built, but when tried to run it in vagrant I received the error that I mentioned previously.

I think you are right, you are not emulating the right cpu in virtualbox. Try building w/o the --copt=-mmmx --copt=-msse --copt=-msse2 and make sure that works.

This issue is automatically closed due to lack of activity. Please re-open if this is still an issue for you. Thanks!


Editor: Split "Lookup Symbol" and "Go to Definition" functionality

See #100680.

I'm not sure which option is better from a user experience perspective, for now I've used the easiest to implement option (since Ctrl+LMB is hardcoded into CodeEdit):

Ctrl+LMB - Lookup Symbol (Open Documntation).
Ctrl+Shift+LMB - Go to Definition.

It would also be nice to merge #95821 first so that the behavior is deterministic. And optionally add a GitHub search for native symbols.

I’m not a fan of this proposal simply because I use both of these functionalities a LOT when I code, and a) having to hold two modifiers when clicking is cumbersome, and b) having to think which of these I need to press.

I’m not a fan of this proposal simply because I use both of these functionalities a LOT when I code

It's okay, it's just a draft, I'm happy to hear other opinions and find a better solution.

a) having to hold two modifiers when clicking is cumbersome

Another suggestions:

Ctrl+LMB and Alt+LMB;
Ctrl+LMB and Ctrl+RMB.

b) having to think which of these I need to press

I'm afraid that in the future you'll have to think about what you want to get. Previously, the same combination is used for opening the built-in help for native symbols and jumping to the source location for custom symbols. But we could also 1. open the documentation for custom symbols (this is especially useful for addons) and 2. search the source location on GitHub for native symbols.
As for modifiers, I think maybe we should change the order. Given that there are now tooltips for documentation, perhaps Ctrl+LMB should be used to jump to the definition, and the alternative combination (whichever we choose) should be used to open the documentation.

As for modifiers, I think maybe we should change the order. Given that there are now tooltips for documentation, perhaps Ctrl+LMB should be used to jump to the definition, and the alternative combination (whichever we choose) should be used to open the documentation.

Exactly what I think it would be the best to implement from now on. Tooltips remove the need to jump to the documentation.

Thanks for sharing your considerations @dalexeev!
What about:

Ctrl + LMB goes to definition, unless native symbol; then it goes to documentation.
Alt + LMB goes to documentation.

Note that when we talk about Ctrl here, that it's actually Cmd here on macOS :)

I like the change but only when I'm interacting with code that has finished documentation or is more mature.
Maybe by default ctl-click goes to the code, unless there is a comment like #mature at the top.
I also like the alt click or other click behavior.


Bug fix/fix restart test

Scope & Purpose
It seems the tests logic of launchin instances was flawed.

[x] :hankey: Bugfix

was fixed by https://github.com/arangodb/arangodb/pull/17009


Reorganizing the woof/ directory structure

I worried that the directory structure is getting a little disorganized. Currently it looks like the following:
audio/
code/
    tutorial1-code.html
images/
snipets/
    tutorial1-snipet1.html
    tutorial1-snipet2.html
    tutorial2-snipet2.html
index.html
tutorial1.html
tutorial2.html

I think it could be a little cleaner organizing things by tutorial instead of by the type of file:
index.html
tutorial1/
    index.html
    step1.html
    step2.html
    step3.html
    image1.jpg
    audio1.jpg
tutorial2/

One benefit is that this makes it more clear which audio and images go with which project.
The downside of this approach is that I don't have a single directory that I can share with teachers as "the answer" to WoofJS projects.
Also, I'd prefer calling the snipet files "steps" because I think that's more clear.

I like this organization. What if we made a "tutorials" directory to hold all the tutorial# directories? That way the teachers can still be pointed to one spot.

tutorials/
  tutorial1/
    index.html

The woof/ directory I proposed is very similar to the tutorials/ directory you proposed above. The only difference is that my woof/ directory has one extra file: index.html for the homepage for Woof projects.
So I'm not sure what your proposal adds, and it makes the URLs longer like coding.space/woof/tutorials/apple-catcher where my proposal keeps them the same coding.space/woof/apple-catcher.

I proposed to create a tutorials directory - in addition to everything you
listed - to address the downside you mentioned of not being able to point
teachers to one place for the answer key.
Right now I believe that they are being pointed to https
://github.com/stevekrouse/coding.space/tree/master/woof/cod
https://github.com/stevekrouse/coding.space/tree/master/woof/codee
If we added a tutorials directory, they could instead be pointed to
https://github.com/coding.space/tree/master/woof/tutorials
They could then select which tutorial folder to go to from there.
On Apr 17, 2017 4:10 PM, "Steve Krouse"<EMAIL_ADDRESS>wrote:

The woof/ directory I proposed is very similar to the tutorials/
directory you proposed above. The only difference is that my woof/
directory has one extra file: index.html for the homepage for Woof
projects.
So I'm not sure what your proposal adds, and it makes the URLs longer like
coding.space/woof/tutorials/apple-catcher where my proposal keeps them
the same coding.space/woof/apple-catcher.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stevekrouse/coding.space/issues/45#issuecomment-294577086,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACAI8XHpUE-YJ5zncxt6jW8dSfKTi2SJks5rw8cjgaJpZM4M-Cvs
.

Oh, I think I see what you mean. We could keep a separate directory for the final steps of each project. That works but I don't love having an additional step when you add a project to the curriculum.
Is that what you're saying? I still don't see why we'd need to nest the directories like you show as opposed to keeping it flat like we currently have in code/.

I don't think we're quite on the same page still. Are you proposing to get rid of the code/ directory or keep it? If the former, where would you point teachers to view the answer key? If the latter, what did you mean when you said "The downside of this approach is that I don't have a single directory that I can share with teachers as "the answer" to WoofJS projects."?

Here's my reasoning for having a nested directory:
Bob wants to see the answer key for Candyland Escape. He thinks it's called
Candyland, though, so when he enters a direct URL to get right to the code,
he enters "../woof/candyland" instead of "../woof/candyland-escape" and
gets a 404.
If Bob is instead told to go to "../woof/tutorials", he will then see a
folder for every tutorial and pick the one he wants to see the answers to.
In this instance, he'll click on the Candyland Escape folder. Once inside,
he'll have access to the HTML files for each step and the final project.
But now that I'm writing this out, I guess the instructions for teachers
could be just to find the name of the project and add it to the end of
https://github.com/coding.space/tree/master/woof/
Is that right??
On Apr 17, 2017 4:58 PM, "Steve Krouse"<EMAIL_ADDRESS>wrote:

Oh, I think I see what you mean. We could keep a separate directory for
the final steps of each project. That works but I don't love having an
additional step when you add a project to the curriculum.
Is that what you're saying? I still don't see why we'd need to nest the
directories like you show as opposed to keeping it flat like we currently
have in code/.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stevekrouse/coding.space/issues/45#issuecomment-294591245,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACAI8STqCVy2PihxDx09SgZcyQqQx5D4ks5rw9J1gaJpZM4M-Cvs
.

My original proposal was to delete the code/ directory and just put the code for each project into that project's folder. However, it could keep things simple for teachers looking at the answer key to keep it as it is. We could rename code/ to answer-key/ for clarity.
In the system I proposed originally (with no code/ directory), teachers would go to https://github.com/stevekrouse/coding.space/tree/master/woof/ and see the list of directories of all of the projects, click on the project they wanted, and scan down the list of files for the answer key within that directory.

Got it. Sorry for overcomplicating. I'll get to work on this if that works
for you.
On Apr 18, 2017 10:42 AM, "Steve Krouse"<EMAIL_ADDRESS>wrote:

My original proposal was to delete the code/ directory and just put the
code for each project into that project's folder. However, it could keep
things simple for teachers looking at the answer key to keep it as it is.
We could rename code/ to answer-key/ for clarity.
In the system I proposed originally (with no code/ directory), teachers
would go to https://github.com/stevekrouse/coding.space/tree/master/woof/
and see the list of directories of all of the projects, click on the
project they wanted, and scan down the list of files for the answer key
within that directory.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stevekrouse/coding.space/issues/45#issuecomment-294866702,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACAI8dVaqOEdKa3SodOUK8FWhl3S2LyZks5rxMu-gaJpZM4M-Cvs
.

Maybe let's hold off on it for now. The system we currently have works well enough, so no sense reorganizing a bunch of files for minimal gain. Let's focus on adding more projects and other higher impact projects


Add a linter to check the images' alt text

In order to meet the IBM Accessibility Requirements for the API docs, we need to ensure that all images have appropriate alt text so that users can understand any meaningful visuals. The alt text should serve the same purpose as the images on the page, conveying the same meaning rather than describing visual characteristics. In addition, if an image contains important words for understanding the content, the alt text should include those words as well.
This PR adds a linter to check that all images have alt text. The current invalid images, if any, have been included in an allowlist that will help us to not break CI before the text is added.
If the script detects an image without alt text, it will show an error indicating the file where the image is located and the line where we are using a sphinx directive like .. image:: or .. plot:: that generates an image. Example:
💔 Some images are missing the alt text

Errors found in qiskit_ibm_runtime/fake_provider/__init__.py:
- Error in line 34: .. plot::

Alt text is crucial for making documentation accessible to all users. It should serve the same purpose as the images on the page, conveying the same meaning rather than describing visual characteristics. When an image contains words that are important to understanding the content, the alt text should include those words as well.

To fix the error, the :alt: [Your text here] option must be added under the lines indicated in the error messages. However, If the .. plot:: directive is used, but no image is generated, you can use the option :nofigs:.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 0   changed or added relevant lines in 0 files are covered.
15 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.009%) to 88.934%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
3
91.98%

crates/qasm2/src/parse.rs
12
97.15%

Totals

Change from base Build<PHONE_NUMBER>3:
-0.009%

Covered Lines:
79377

Relevant Lines:
89254

💛  - Coveralls


App crashing upon logging out

The app crashes sometimes when logging out
Metadata
Versions

Version 0.1.0

List of known affected devices

Device: iPhone 11 Pro
OS: iOS 17

-Device: iPhone 14

OS: iPhone 17.1.2

Fixed with version 0.2.11


Schema updates require instance checking

Updates are not checking instance data compatibility. The simplest approach is a global check. Further optimisations can be made later

This is being done correctly now.


Cannot open dataldataset_info.json due to [Errno 2] No such file or directory:' data  dataset info.json!Cannot open dataldataset_info.json due to [Errno 2] No such file or directory:" data dataset info .json'

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
CUDA_VISIBLE_DEVICES=0 python src/train_web.py

Expected behavior
No response
System Info
No response
Others
No response

数据路径改成 D:\LLaMA-Factory-main\data


svelte field in package.json is deprecated

See: https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/faq.md#missing-exports-condition

As usual with deprecation warnings like this the migration path is rather unclear. It looks like you need to change:
{
	"svelte": "./dist/index.js",
        "types": "./dist/index.d.ts"
}

To a construction like this (or actually you need to have both, since some tools are not compatible with this yet 🤦🏻♂):
{
	"exports": {
		".": {
			"types": "./dist/index.d.ts",
			"svelte": "./dist/index.js"
		}
	}
}


Refactor/form plugin spacing

What does this pull request change?

Introduced Stack (spacer/flexbox) component to dm-core
Removed margins from specific elements
Removed duplicate wrapper components
Used Stack component to create spacing in form-plugin

Why is this pull request needed?

Remove individual margins
Less duplicate styling/wrapper components
More uniform spacing of elements

Nice, this will be helpful! :)


Attempt to fix potential compiler segfault in lookup.c

@stefandd I'm going to set this as a draft PR.


CTD when trying to extract a directory.

Сhecked on 1404 and 2205. Open .rda, select any directory (data/config, for example), right-click, "Extract", select path -> crash.

Thanks for reporting!
This should be fixed now on the latest release: https://github.com/lysannschlegel/RDAExplorer/releases/tag/v<IP_ADDRESS>.
Please reopen if the fix doesn't work for you.


KymoTrackGroup._kymo only valid for single source kymo

Why this PR?
KymoTrackGroup._kymo is still used in many places where we require a single source kymograph. Here, added an extra check that raises if KymoTrackGroup._kymos has more than a single item in order to avoid silent bugs where the criterion isn't met.

I see your point, but I think it's actually 2 different scenarios, and this one is more descriptive for certain things. My thinking was that a valid return from ._kymo is used iff there's really 1 source kymo and that's required (flipping). Other instances that can have more than 1 kymo but require the same acquisition settings can read from the 1st instance in ._kymos.
Although conversely, we already use _validate_single_source when it's really required so 😖 I guess the risk is that in the future we could forget to use this validation and just rely on ._kymo by mistake which could lead to a silent bug. I do agree I'd rather not have ._kymos[0] all over the place.
What do you think?

Maybe we should drop the property all-together and make it explicit that you always have to think of the fact that there can be more than one or there could be zero. I guess the [0] is a bit ugly, but it is explicit, and it will lead to a comment nearby every time we do it to justify it (which in this case is a good thing).
It doesn't require that many changes to get this property removal to work.
It would also be nice to add a test for the multi-kymo ensemble_ols considering that we just found that it is untested.


How do I opt in (or implement) the "Native H160 via AccountId20" strategy?

In the /docs/accounts.md it states the following:
The second strategy consists of using fp-account so that AccountId20 is the Account type used for frame_system::pallet::Config::AccountId.
How can someone opt in to this strategy?
Where in code does it have to be changed?
Some guidance would help tremendously for someone new to substrate and would like to get started quickly.
I'd be more than happy to create a PR with detailed explanation of this once I have understood how this works so following devs can make their switch quickly.
Many thanks.

I am also interested in this one

Nice question. You can check out our configuration at https://github.com/darwinia-network/darwinia/blob/main/core/primitives/src/lib.rs#L33-L37. Since there are already several projects based on Frontier that have been running for a long time, feel free to search and test by yourself.

@boundless-forest
Thanks for the reply!
But from what I can see, your link does nothing different from the Frontier runtime template.
I can see that you have H160 as address type in other places which means AccountId20 is used strategy is used?
I guess my real question is, why isn't there some kind of global struct with an associated type where the AccountId type is configurable for all other pallets to derive their behavior from...?
What't the idea here?
Why should we go around and change in a lot of places what the account id type is?
I'm assuming there is some fundamental knowledge that I'm missing about polkadot-sdk that I just don't understand yet.
Would help if someone could enlighten me.

I believe H160 and H256 represents the generic hash type which may or may not be the AccountId where AccountId maybe further constrained version of hashes which is the case most of the time. AFAIK, you don't need to change use AccountId20 everywhere, there is AccountId generic type which just works, also you only need to configure it in frame_system, you can also refer to it with <Runtime as frame_system::Config>::AccountId and it will point to whichever AccountId you are using.


No longer working

Unfortunately the app no longer works due to Parse being shut down in January this year.

Do you have a backup of the Parse storage or even just the schema? The app appears to build everything itself when run against a hosted Parse server, however the stickers part of the app is read only and there is no way to generate it without some more idea of what it should look like :( (P.S. Your app store published version of this app also doesn't work any more and crashes on launch)


vs code cannot validate since a php installation could not be found

It would be nice if we had the option to just dismiss and not see this message again every time when opening .php files in case we don't want any validation. Having to dismiss this notification every time is quite annoying.

"php.validate.enable": false

Thank you very much! I have no idea how I missed that setting though


WIP Performance optimizations for Zinc

To validate this pull request against other sbt modules, please visit this link.

A validation involving this pull request is in progress...

The validator has checked the following projects against Scala 2.12,
tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
1.x
sbt/sbt@78f7658a67b2b3f597186207f1bdbfea67c0d313

zinc
pull/492/head
sbt/zinc@3d1dd67c97a0d2086d0c09d3d1098ceda9fd6393

io
1.x
sbt/io@7f8c185b4a522781d5b6dd21d3002a6bd8cfc08e

librarymanagement
1.x
sbt/librarymanagement@0d21ae6369a3e4054ed434902ea84b2520d21da9

util
1.x
sbt/util@9891f07bda2d7d44be141401ed29abe39d42a43a

website
1.x

:white_check_mark: The result is: SUCCESS
(restart)

Changes look good to me. Had a look at the CI, bincompat checks are failing. We should probably whitelist them.
[error]  * method hashTypeParameters(scala.collection.Seq)Unit in class xsbt.api.HashAPI's type is different in current version, where it is (Array[xsbti.api.TypeParameter])Unit instead of (scala.collection.Seq)Unit
[error]    filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.HashAPI.hashTypeParameters")
[error]  * method hashAnnotations(scala.collection.Seq)Unit in class xsbt.api.HashAPI's type is different in current version, where it is (Array[xsbti.api.Annotation])Unit instead of (scala.collection.Seq)Unit
[error]    filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.HashAPI.hashAnnotations")
[error]  * method hashParameters(scala.collection.Seq,xsbti.api.Type)Unit in class xsbt.api.HashAPI's type is different in current version, where it is (Array[xsbti.api.TypeParameter],xsbti.api.Type)Unit instead of (scala.collection.Seq,xsbti.api.Type)Unit
[error]    filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.HashAPI.hashParameters")
[error]  * method hashDefinitionsWithExtraHashes(scala.collection.Seq)Unit in class xsbt.api.HashAPI does not have a correspondent in current version
[error]    filter with: ProblemFilters.exclude[DirectMissingMethodProblem]("xsbt.api.HashAPI.hashDefinitionsWithExtraHashes")
[error]  * method hashSeq(scala.collection.Seq,scala.Function1)Unit in class xsbt.api.HashAPI does not have a correspondent in current version
[error]    filter with: ProblemFilters.exclude[DirectMissingMethodProblem]("xsbt.api.HashAPI.hashSeq")
[error]  * method hashValueParameters(scala.collection.Seq)Unit in class xsbt.api.HashAPI's type is different in current version, where it is (Array[xsbti.api.ParameterList])Unit instead of (scala.collection.Seq)Unit
[error]    filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.HashAPI.hashValueParameters")
[error]  * method hashAnnotationArguments(scala.collection.Seq)Unit in class xsbt.api.HashAPI's type is different in current version, where it is (Array[xsbti.api.AnnotationArgument])Unit instead of (scala.collection.Seq)Unit
[error]    filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.HashAPI.hashAnnotationArguments")
[error]  * method hashTypes(scala.collection.Seq,Boolean)Unit in class xsbt.api.HashAPI's type is different in current version, where it is (Array[xsbti.api.Type],Boolean)Unit instead of (scala.collection.Seq,Boolean)Unit
[error]    filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.HashAPI.hashTypes")
[error]  * method visitTypeParameters(scala.collection.Seq)Unit in class xsbt.api.Visit's type is different in current version, where it is (Array[xsbti.api.TypeParameter])Unit instead of (scala.collection.Seq)Unit
[error]    filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.Visit.visitTypeParameters")
[error]  * method visitDefinitions(scala.collection.Seq)Unit in class xsbt.api.Visit's type is different in current version, where it is (Array[xsbti.api.Definition])Unit instead of (scala.collection.Seq)Unit
[error]    filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.Visit.visitDefinitions")
[error]  * method visitAnnotationArguments(scala.collection.Seq)Unit in class xsbt.api.Visit's type is different in current version, where it is (Array[xsbti.api.AnnotationArgument])Unit instead of (scala.collection.Seq)Unit
[error]    filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.Visit.visitAnnotationArguments")
[error]  * method visitAnnotations(scala.collection.Seq)Unit in class xsbt.api.Visit's type is different in current version, where it is (Array[xsbti.api.Annotation])Unit instead of (scala.collection.Seq)Unit
[error]    filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.Visit.visitAnnotations")
[error]  * method visitValueParameters(scala.collection.Seq)Unit in class xsbt.api.Visit's type is different in current version, where it is (Array[xsbti.api.ParameterList])Unit instead of (scala.collection.Seq)Unit
[error]    filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.Visit.visitValueParameters")
[error]  * method visitParameters(scala.collection.Seq,xsbti.api.Type)Unit in class xsbt.api.Visit's type is different in current version, where it is (Array[xsbti.api.TypeParameter],xsbti.api.Type)Unit instead of (scala.collection.Seq,xsbti.api.Type)Unit
[error]    filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.Visit.visitParameters")
[error]  * method visitTypes(scala.collection.Seq)Unit in class xsbt.api.Visit's type is different in current version, where it is (Array[xsbti.api.Type])Unit instead of (scala.collection.Seq)Unit
[error] filter with: ProblemFilters.exclude[IncompatibleMethTypeProblem]("xsbt.api.Visit.visitTypes")

Yeah, I figured that wasn't really external API.
The PR is in a bit of messy state, I need to take some more time to rebase. I'd also like to try out your benchmarking rig to see which (if any) commits have a positive impact on runtimes. I drove these changes by collecting profiles with flight recorder.

Here's the report for -prof gc for the scala-library corpus.
The last column is the allocation in B/op attributable to Zinc itself. This PR reduces that by about a third.
num  desc                      gc.alloc.rate.norm   <value>-#1
1    baseline, zinc disabled<PHONE_NUMBER>.667
2    baseline  zinc enabled<PHONE_NUMBER>.000<PHONE_NUMBER>
3    patch, zinc enabled<PHONE_NUMBER>.667<PHONE_NUMBER>

I'm thinking of adding a mode to the benchmark rig that runs the compiler up to the ExtractAPI  phase in @Setup, and loops over the ExtractAPI work in the benchmarked method. That will make it much easier to targetted profiling and tuning of Zinc. Of course, we must also validate the results in the broader context of the normal compilation run, as the benchmarks currently do.

I'm thinking of adding a mode to the benchmark rig that runs the compiler up to the ExtractAPI  phase in @Setup, and loops over the ExtractAPI work in the benchmarked method.

It requires a few hacks, but seem to work: https://github.com/retronym/zinc/tree/topic/focus
WDYT?
[info] Benchmark                                                                       (_tempDir)  (zincEnabled)    Mode  Cnt           Score          Error   Units
[info] HotScalacMicroBenchmark.compile                                   /tmp/zinc-bench-baseline           true  sample   18        3888.819 ±      211.550   ms/op
[info] HotScalacMicroBenchmark.compile:compile·p0.00                     /tmp/zinc-bench-baseline           true  sample             3703.570                  ms/op
[info] HotScalacMicroBenchmark.compile:compile·p0.50                     /tmp/zinc-bench-baseline           true  sample             3839.885                  ms/op
[info] HotScalacMicroBenchmark.compile:compile·p0.90                     /tmp/zinc-bench-baseline           true  sample             4156.136                  ms/op
[info] HotScalacMicroBenchmark.compile:compile·p0.95                     /tmp/zinc-bench-baseline           true  sample             4680.843                  ms/op
[info] HotScalacMicroBenchmark.compile:compile·p0.99                     /tmp/zinc-bench-baseline           true  sample             4680.843                  ms/op
[info] HotScalacMicroBenchmark.compile:compile·p0.999                    /tmp/zinc-bench-baseline           true  sample             4680.843                  ms/op
[info] HotScalacMicroBenchmark.compile:compile·p0.9999                   /tmp/zinc-bench-baseline           true  sample             4680.843                  ms/op
[info] HotScalacMicroBenchmark.compile:compile·p1.00                     /tmp/zinc-bench-baseline           true  sample             4680.843                  ms/op
[info] HotScalacMicroBenchmark.compile:·gc.alloc.rate                    /tmp/zinc-bench-baseline           true  sample    6         281.356 ±       29.502  MB/sec
[info] HotScalacMicroBenchmark.compile:·gc.alloc.rate.norm               /tmp/zinc-bench-baseline           true  sample    6<PHONE_NUMBER>.556 ±   819406.113    B/op
[info] HotScalacMicroBenchmark.compile:·gc.churn.PS_Eden_Space           /tmp/zinc-bench-baseline           true  sample    6         281.810 ±       29.267  MB/sec
[info] HotScalacMicroBenchmark.compile:·gc.churn.PS_Eden_Space.norm      /tmp/zinc-bench-baseline           true  sample    6<PHONE_NUMBER>.889 ± 19759251.396    B/op
[info] HotScalacMicroBenchmark.compile:·gc.churn.PS_Old_Gen              /tmp/zinc-bench-baseline           true  sample    6          30.626 ±        4.740  MB/sec
[info] HotScalacMicroBenchmark.compile:·gc.churn.PS_Old_Gen.norm         /tmp/zinc-bench-baseline           true  sample    6   130446065.333 ±  9252509.827    B/op
[info] HotScalacMicroBenchmark.compile:·gc.churn.PS_Survivor_Space       /tmp/zinc-bench-baseline           true  sample    6          18.590 ±        6.947  MB/sec
[info] HotScalacMicroBenchmark.compile:·gc.churn.PS_Survivor_Space.norm  /tmp/zinc-bench-baseline           true  sample    6    79081034.667 ± 24937547.953    B/op
[info] HotScalacMicroBenchmark.compile:·gc.count                         /tmp/zinc-bench-baseline           true  sample    6         311.000                 counts
[info] HotScalacMicroBenchmark.compile:·gc.time                          /tmp/zinc-bench-baseline           true  sample    6       10263.000                     ms

does the on-the-fly compilation of the compiler interface enable the
optimiser? If not, hand inlining here is helpful.

@dwijnand Is there something here you'd like to see address before we merge?


Need to preserve changes to sequences in tenant mode

Create an API using a WSDL.

In the implement tab if we click the resources then the loaded WSDL will appear in the In-Flow section (not the In Flow section in the message mediation ). When we make changes in the In Flow section in the UI the changes are not saved in the UI in the tenant mode.

Fix : https://github.com/wso2/carbon-apimgt/pull/7823


[Android Studio 3.0 alpha7]OnClick doesn't get response

My Android Studio has been updated to 3.0 alpha7, when I use eventbus 3.0.0 on a OnClick Event, I find it can't work well(but it doesn't crash), the received Activity can't make any response!
But if I post message once the Activity onCreated, it can receive and make any response.
I think maybe the message hasn't been sent out !!!

Code or demo please.
we must keep in mind: Code has nothing to do with tools(android studio or eclipse).

I don't think so, maybe the gradle version don't match the code, because when I use Android Studio 2.3.3, it can be fine.

As @jp1017 said, we can not help without an example project so we can reproduce the issue. -ut

I made a project with AS 3.0.0 alpha7(and gradle version is 3.0.0-alpha7) ,you can run it to find the issue.
https://github.com/1130381752/MyApplication.git

You need to read up and understand the Android Activity lifecycle.
MainActivity will already have stopped (and unregistered it's EventListener) by the time Activity1 posts its event.

But if I post the Event once the MainActivity1 onCreate, MainActivity can make response(Toast) right now.

Are you aware that the new activity will go up to onResume() while the old activity remains in onPause()? Only after that the old activity will be stopped and destroyed. See Coordinating activities in the Android Activity Lifecycle documentation.
To pass data across activities you should save the data or you might try using sticky events.
-ut


startActivityForResult from onCreate() stack isn't tracked

From<EMAIL_ADDRESS>on May 05, 2011 19:53:34
What steps will reproduce the problem? 1. Create activity A
2. startActivityForResult for activity B (in same app)
3. Write Test case for A. In test, write:
solo.waitForActivity("B", 30);
ArrayList activities = solo.getAllOpenedActivities();
Activity a = solo.getCurrentActivity();
Phone shows activity B correctly, but the test case will return A as the current activity (and as the only opened activity), even though B is clearly on the screen and other methods (like getCurrentListViews()) will return the correct views from activity B. What version of the product are you using? On what operating system? Robotium 2.3, OSX 10.6, Testing using Android 1.6 and 2.2 devices.
Original issue: http://code.google.com/p/robotium/issues/detail?id=111

From<EMAIL_ADDRESS>on May 05, 2011 22:02:05
Try startActivitySync(Intent intent) instead.
Status: WontFix

From<EMAIL_ADDRESS>on May 05, 2011 22:02:28
Status: New

From<EMAIL_ADDRESS>on May 09, 2011 22:59:05
Status: Invalid

From<EMAIL_ADDRESS>on May 10, 2011 08:39:25
The point is that activity A needs to start B (which are both in the same app), and B will return a result. The test is not starting it, A is. The whole point of the test is that A starts B, and then gets back a result. I can use other methods to see the appropriate screen details synchronously, so that isn't the problem.
That said, I can deduce the activity is running, and I can deduce that it has returned. My report wasn't that I could not write the test, it was simply that stating assertions related to the "current activity" are useless if you don't actually track the current activity...so then why have such methods in your public interface?
This is not an invalid issue. It is a bug. The public facing API of you classes doesn't work.
The documentation of the activity related methods should at least contain this:
NOTE: These methods cannot track the current activity if your code uses startActivityForResult(). You should invent some other way of testing such activity flow (e.g. examine what is on the screen).

From<EMAIL_ADDRESS>on March 20, 2014 08:44:31
Please note: you need to implement tearDown methods for the tests, like this:
@Override
public void tearDown() throws Exception {
solo.finishOpenedActivities();
super.tearDown();
}
If you skip it, it may lead to the described behavior.
(I'm not saying the issue is valid or invalid)


global random date. isvalid function. some timezone tests.

Codecov Report

Merging #15 into master will decrease coverage by 5.05%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
- Coverage   92.37%   87.31%   -5.06%
==========================================
  Files          22       27       +5
  Lines         118      134      +16
==========================================
+ Hits          109      117       +8
- Misses          9       16       +7
- Partials        0        1       +1

Impacted Files
Coverage Δ

date/next.go
100% <100%> (ø)
:arrow_up:

date/last.go
100% <100%> (ø)
:arrow_up:

date/sample.go
100% <100%> (ø)
:arrow_up:

date/randomdate.go
100% <100%> (ø)
:arrow_up:

date/isvalid.go
50% <50%> (ø)

timezone/offset.go
100% <0%> (ø)

timezone/currtimezone.go
0% <0%> (ø)

timezone/curroffset.go
0% <0%> (ø)

timezone/timezone.go
100% <0%> (ø)

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 ef0fc50...35849a8. Read the comment docs.


Make sure layer config always has a name

this came up in: https://github.com/GeoNode/geonode-client/issues/100

Changes Unknown when pulling 8d6aeae7e4bd9607336952955b1d7020407ea2a5 on gxp-write-name into ** on master**.


Can i use this library inside my paid app?

I'm a indie developer and planning to use this library inside my paid app. But i'm not sure whether can i or not since it uses Apache 2 license. Can you help me things needs to be do? Is it enough to include Library name with link and license name in the about menu of application.  I'm new to license terms, i searched google for answer but i didn't get concrete answer. Thats why I'm posting here.

Yes.. enjoy. and always remember that All you need is love

You can see what you can do from this link.
https://choosealicense.com/licenses/apache-2.0/
Yes, you can use this in your project. 👍


Deprecate cip-mm

Hey @mrueg, thanks for filing this (and for using the tools here!)
First up, I want to point out kpromo pr, which includes much of the functionality of cip-mm and should be your go-to tool for creating image promotion PRs. You can read more about it here: https://github.com/kubernetes-sigs/promo-tools/blob/main/docs/promotion-pull-requests.md

it sorts the generated file by the checksum of the promoted container images. Ideally it would allow sorting the generated file by tag instead or have an option to provide that as a argument.

Now, onto this question...
It's actually something I asked when I started using the tool.
The manifest format is a map[string][]string https://github.com/kubernetes-sigs/promo-tools/blob/b245668212a77e73f0f862c9b3f740ea88f1502f/image/image.go#L47-L49
to support mapping a digest to multiple tags, which you can see an example of here: https://github.com/kubernetes/k8s.io/blob/48f96e52a326b0b7ec09ea29de18be9368533950/k8s.gcr.io/images/k8s-staging-artifact-promoter/images.yaml#L27
I agree that this is maybe not intuitive and I'm not saying that we couldn't change it, but it would:

affect the way the promoter reads in images
require us to update all manifests to support this

@kubernetes-sigs/release-engineering @listx -- curious to hear your thoughts here.
Originally posted by @justaugustus in https://github.com/kubernetes-sigs/promo-tools/issues/473#issuecomment-991167871

Ideally we humans shouldn't have to read the YAMLs directly --- sometimes the configurations can get very long and difficult to read directly. I.e., there should be a tool that can display things in a more sensible way.
If there is additional tooling available, it would make the map key ordering in YAML an obsolete discussion (because the ordering logic would reside in the tool, not in how we write out the YAML).


Improve experience of adding or editing attribution details

Is your feature request related to a problem? Please describe.
The current attribution wizard is hidden behind a context menu and not intuitive to use.
In addition, the individual input fields and the PURL input field are linked in such a way that one can disable the other as soon as certain data is entered by the user. This can lead to a frustrating user experience.
Describe the solution you'd like

Attribution wizard is replaced by autocomplete input fields in the attribution details.
Each autocomplete input should offer custom data entry as well as a list of likely values to choose from (collected from the resource's signal, if any exist). Unlike the attribution wizard, we omit signals that don't contain data. Each offered suggestion should also include the signal PURL so that it is possible to establish context between the suggestion and the its origin.
The PURL input field becomes read-only.

Additional context

Since the PURL is determined by the individual text inputs such as type, namespace, name, etc., we can generate it from the individual input fields which are more user friendly to fill and don't require the user to have PURL syntax knowledge. Thus, disabling individual inputs because of the presence of a PURL is exactly the wrong way around, from a UX/UI point-of-view.
A PURL may contain additional information as part of qualifiers such as OS, architecture, distro, subpaths. Is this important for users of OpossumUI, and if so: how do we offer the user to enter such information, again without requiring the user to understand PURL syntax?
The "Package Type" input field should offer a list of known package ecosystems rather than only show suggestions from the signals.
What option of package type, name, version should we give for first-party code?

See here for PURL syntax: https://github.com/package-url/purl-spec#purl

Not sure if that still accomplishes the goal to give an overview of the contained signals. The Attribution Wizard was build as a move to more package  oriented approach where directories are resolved. This proposal moves away from that again.

Let's have a discussion as I don't fully understand your comment. I think we can achieve a "package oriented approach" in an easier to understand and less hidden way.


Create deno.yml

Sorry i'm not familiar with Deno and can't accept this as of now. Will reopen with the proper explanations!


Renamed Measure fails to sync with visuals

Describe the bug
I was bulking editing measures in Tabular editor, Renamed quite a few measures in tabular editor and saved.  New names were reflected in Power BI but All the related visuals failed expecting for the previous measure name.
To Reproduce
Steps to reproduce the behaviour:

Rename a measure in tabular editor
Save and the changes are seen in Power BI tables i.e new name is applied at table level
all the visuals failed expecting previous measure name

Expected behaviour
New Names must have applied to the visuals as like we rename  a measure in Power BI and should not break the visuals
Observed behaviour
All the visuals are broken and shows error expecting for previous measure name.
Application specifics

Tabular Editor version: 2.11.7499
Semantic Engine used: Power BI Desktop
Model Compatibility Level: latest power bi model

This is not possible. Please see #455 and #672 for more details.


[Feature Request] New trigger: @Drink

There may be a need for a trigger that will fire when a character drinks potion. It may be necessary to replace the empty bottle returned by a potion, or you may want to adjust the time of drinking the next potion here, or you may want to turn off the loss of potion when the potion is drunk.
under void CChar::Use_Drink( CItem * pItem )
	const CItemBase *pItemDef = pItem->Item_GetDef();
	ITEMID_TYPE idbottle = (ITEMID_TYPE)pItemDef->m_ttDrink.m_ridEmpty.GetResIndex();

	int64 pDelay = 150;
	word pConsume = 1;

	TRIGRET_TYPE iRet = TRIGRET_RET_DEFAULT;
	if (IsTrigUsed(TRIGGER_DRINK))
	{
		CScriptTriggerArgs args;
		args.m_pO1 = pItem;
		args.m_VarsLocal.SetNumNew("IdBottle", idbottle);
		args.m_iN1 = pDelay;
		args.m_iN2 = pConsume;
		iRet = OnTrigger(CTRIG_Drink, this, &args);
		idbottle = (ITEMID_TYPE)args.m_VarsLocal.GetKeyNum("IdBottle");
		pDelay = args.m_iN1 ? args.m_iN1 : 150;
		pConsume = args.m_iN2 ? (word)(args.m_iN2) : 1;

		if (iRet == TRIGRET_RET_TRUE)
			idbottle = (ITEMID_TYPE)ITEMID_NOTHING;
	}

ON=@ drink
// return 1 = does not give empty potions
// argo =the potion she drank
// local.IdBottle = empty potion id
// src = drinking char
// argn1 = cooldown time
// argn2 = potion reduce amount
The codes here are purely examples. Although many have been tested, some may need to be rewritten.

SpellEffect do that with argo being the item used, but it will be nice to add the coooldown time for potions as currently is hardcoded

SpellEffect bunu argo kullanılan öğeyle yapıyor, ancak şu anda sabit kodlanmış olduğundan iksirlere bekleme süresi eklemek güzel olacak

It would also be nice if it gives an empty potion after using the potion or if it gives an empty potion with a different id.

I like this new trigger.  Could be use on alcool bottle too.

SpellEffect bunu argo kullanılan öğeyle yapıyor, ancak şu anda sabit kodlanmış olduğundan iksirlere bekleme süresi eklemek güzel olacak

It would also be nice if it gives an empty potion after using the potion or if it gives an empty potion with a different id.

U can modify data1 to retrieve a diferent empty bottle or whatever.
and LAYER_FLAG_PotionUsed should be able to be modified so u can set there the CoolDown by many ways.

SpellEffect do that with argo being the item used, but it will be nice to add the coooldown time for potions as currently is hardcoded

Should be nice to use tdata2 for it. so if tdata2 is defined it would be used to override potion's cd.

When the potion is made with the tdata value, this will be valid for all items. It seems like it would be nice to set the empty potion refund in a customized settings menu so that it can be turned on and off. I don't think it's shockingly effective to include too many triggers instead of controlling many things about the pot you drink with a single trigger.


[ADD]support for password protected redis cluster

replacement pull request for https://github.com/Grokzen/redis-py-cluster/pull/102

Remember to close the old one if this superseeds it.

@Grokzen all of my changes are committed now, can you do a code view when you are free?

@etng I will review it during the week and it should be merged either before or during the weekend.

@etng Reviwed this and it all looks good. I pulled the branch locally and i edited some of the commits to do some minor cleanup and i merged it manually so there is no need to merge this PR as is. You still get all the credit and all that even tho the first commit got changed to me O.o dunno why that happened. Still thank you alot for this fix :]
One other question, did you post a PR to add password capability to redis-trib.rb so that there is no need to have a patched copy in this repo? If so can you please post that PR so i can track it in another issue to remove it when the support is added.

@Grokzen my patch for redis-trib.rb is just for create cluster, modify and other operations are not supported now.I will implements these functions and try to send PR the redis project later :)

Awesome, please try to ping the issue i created about removing the trib file from this repo, so i can track the progress and remove it myself.

Any plan to make another release with this fix in it...?

+1

+1