Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 15 14:07
    niemyjski commented #472
  • Dec 15 07:50
    alvin-su opened #472
  • Dec 15 01:35
    niemyjski synchronize #452
  • Dec 15 01:35

    niemyjski on elastic7

    Only put consumes attribute on … (compare)

  • Dec 14 16:39
    ejsmith synchronize #452
  • Dec 14 16:39

    ejsmith on elastic7

    Log the correct task id and cat… (compare)

  • Dec 14 06:25
    ejsmith synchronize #452
  • Dec 14 06:25

    ejsmith on elastic7

    Minor (compare)

  • Dec 14 06:00
    ejsmith synchronize #452
  • Dec 14 06:00

    ejsmith on elastic7

    Add missing task id (compare)

  • Dec 13 22:43
    ejsmith synchronize #452
  • Dec 13 22:43

    ejsmith on elastic7

    More reindex job changes (compare)

  • Dec 13 15:46
    ejsmith synchronize #452
  • Dec 13 15:46

    ejsmith on elastic7

    Just retry 3 times (compare)

  • Dec 13 15:44
    ejsmith synchronize #452
  • Dec 13 15:44

    ejsmith on elastic7

    More log message changes (compare)

  • Dec 13 14:25
    niemyjski synchronize #452
  • Dec 13 14:25

    niemyjski on elastic7

    Added retry reindex for disconn… (compare)

  • Dec 13 14:09
    niemyjski synchronize #452
  • Dec 13 14:09

    niemyjski on elastic7

    Updated migration to retry sock… (compare)

Frank Ebersoll
@frankebersoll
then add a breakpoint in the exceptionless-spec.js
Blake Niemyjski
@niemyjski
ok
trying now
Frank Ebersoll
@frankebersoll
then launch the "Test" debug configuration
Blake Niemyjski
@niemyjski
how did you do that
shortcut keys
when I press f5 it just does the launch node
Frank Ebersoll
@frankebersoll
Go to the debug area on the left. Select "Test" from the dropdown
Blake Niemyjski
@niemyjski
ok
looking
thinking we should default it to test
the other one for the node app could be in the express folder
thoughts?
pushed
break points don’t seem to be mapping properly
I’ve always had problems with that
Frank Ebersoll
@frankebersoll
pizza :)
Blake Niemyjski
@niemyjski
haha
eat up
I had summer sausage for lunch
Frank Ebersoll
@frankebersoll
thinking we should default it to test
not a problem. we just need to put this configuration to the top, i think
break points don’t seem to be mapping properly
i think that the paths in the .map files are incorrect
Blake Niemyjski
@niemyjski
well
Frank Ebersoll
@frankebersoll
i already got that working, just not yet in our project
Blake Niemyjski
@niemyjski
they would be pointing to dist/temp and our breakpoints are set in /
I think that’s the issue
Frank Ebersoll
@frankebersoll
they need to point back to the actual sources
ehm....
exceptionless-spec.js.map contains only source code, no mappings
not cool.
Blake Niemyjski
@niemyjski
{"version":3,"file":"submitSync.js","sourceRoot":"/source/","sources":["submitSync.ts"],
that sourceroot should be /src/ no?
Frank Ebersoll
@frankebersoll
right.
even more, it needs to be relative
or absolute to your workstation root
that's another problem that would be solved by an additional publish-build
Blake Niemyjski
@niemyjski
relative would be best
Frank Ebersoll
@frankebersoll
during debugging, we need source maps that support our local file structure
Blake Niemyjski
@niemyjski
yeah
Frank Ebersoll
@frankebersoll
after publishing, we need to support loading via the web
that might be two different things.
i'm back on master now, finishing stringily.
stringify*
Blake Niemyjski
@niemyjski
kk
Frank Ebersoll
@frankebersoll
ah, another thing!
the new npm seems to deduplicate modules into the root node_modules directory, wherever possible
Blake Niemyjski
@niemyjski
yeah
Frank Ebersoll
@frankebersoll
i guess it does this by downloading the "lowest common denominator" version of a module that is used by other modules