Add ability to use native nodejs require resolve method

Feature request

What is the expected behavior?
I am using a 3rd party library which uses the nodeJs require.resolve method to get the path of a module at runtime. The specific piece of code in question is as follows
var sourceDir = path.join(path.dirname(require.resolve('dep')), 'dir', 'subdir');

When bundled with webpack, this results in the following
var sourceDir = path.join(path.dirname(/*require.resolve*/(124)), 'dir', 'subdir');

which results in a runtime failure, as path.dirname requires a string.
What is motivation or use case for adding/changing the behavior?
To support 3rd party packages which may use the built in NodeJs implementation of require.resolve
How should this be implemented in your opinion?
Through the use of a key _use_node_resolve_ in webpack config to indicate that webpack should leave the require.resolve implementation alone when bundling.
Are you willing to work on this yourself?
With some guidance and help, yes

Do you build project for web or node?

nodeJs

I apologize for intrusion, is there any progress on this?
I need for my NodeJS application to be able to call the native require.resolve() to resolve a path to a given module. I cannot substitute it with anything else.

@kettanaito can you create minimum reproducible test repo?

@evilebottnawi I've resolved it and will share the solution that worked for me below.

From my investigation, webpack replaces the native require module from NodeJS by their own implementation to allow certain webpack features. It seems it connects a module's require calls with the module IDs kept in webpack.

Webpack injects a native require module into your bundle through __non_webpack_require__  namespace. Thanks to @sokra for revealing this hidden gem.
const module = __non_webpack_require__('module-name')

I was looking for a way to use require.resolve(), so the proper way ended up to be __non_webpack_require__.resolve(modulePath). This is rather an edge case, but I wasn't able to find any mention of this global variable in webpack's documentation.

How would i go with this if I share my module between nodejs and client. In my nodejs run, I do not use webpack to bundle the code, I just git clone, npm ci, and npm start. That same file is also used inside of the client-side (React) that is build during npm ci process.
My goal is to get the folder where the package.json resides. Can I do that without the need to separate my code from server-side or webpack'ed client-side?
My code is:
const PROJECT_ROOT = path.dirname(require.resolve('./../../package.json'));

or
import packageJson from './../../package.json';

All this was working fine with webpack2. I'm am not sure how to convert this to work with webpack4. I've tried the fs.readFileSync() but on browser, I get the a.default.readFileSync is not a function error.

@quoininc-huudatran, I'm not sure if I understand your particular problem correctly, but if you just need a folder name/path, consider this:
const packageJsonPath = path.resolve('../../package.json')
const packageJsonDirname = path.dirname(packageJsonPath)

// Alternatively, you can parse the path and get more info
const parsedPath = path.parse(packageJsonPath)

path.dirname(path)
path.parse(path)

To manipulate paths you don't have to require a module. Let me know if that helps.
It's worth mentioning, that you shouldn't use built-in modules on the client, so if your goal is for the client to know the folder of package.json consider:

Figuring that out as a part of webpack build step and provigint the package json directory via webpack.EnvironmentPlugin():

// webpack.config.js
// The same functionality as from the snippet above
const PACKAGE_JSON_DIRNAME = path.dirname(path.resolve('../../package.json'))

module.exports = {
  // your webpack config,
  plugins: [
    new webpack.EnvironmentPlugin({
      PACKAGE_JSON_DIRNAME,
    })
  ]
}

Later, in the client, access that environmental variable as:
// src/app.js
process.env.PACKAGE_JSON_DIRNAME

Figuring that out on the server, only in case of more complicated scenarios.

@quoininc-huudatran, I'm not sure if I understand your particular problem correctly, but if you just need a folder name/path, consider this:
const packageJsonPath = path.resolve('../../package.json')
const packageJsonDirname = path.dirname(packageJsonPath)

// Alternatively, you can parse the path and get more info
const parsedPath = path.parse(packageJsonPath)

This wouldn't work for a package...
const otherPackageJson = require.resolve('@namespace/packageName/package.json');

I am requiring the file in order to be able to use values. In my example above, it would be something like:
const { name, version } = require('./../package.json');

Later, in the client, access that environmental variable as:
// src/app.js
process.env.PACKAGE_JSON_DIRNAME

Figuring that out on the server, only in case of more complicated scenarios.

Yes, my case is a shared code between client and server, so I cannot rely on webpack to do these things... and I rather not have my code polluted with
if (process.env.VARIABLE) {
   // use variable
} else {
    const { name, version } = require('./../package.json');
}

@quoininc-huudatran, thanks for the reply. I don't think the issue you describe is connected to the  problem OP describes.
The original issue is that webpack stubs the calls to require.resolve in order to inject additional info about the module imports. So, when calling require.resolve() your code is subjected to change once it compiles. Sometimes you may want to avoid that.
In your case you seem to import a package json file and grab some values from it. There is no need to require the package json just to know where it's located, so you might have gone with:
const PROJECT_ROOT =
  path.dirname(
-   require.resolve('./../../package.json')
+   path.resolve('./../../package.json')
  );

I'd still not recommend trying to perform that on the client, you shouldn't operate with file system as a client runtime (and client's code is what gets executed runtime). That's why I've suggested to resolve the package's directory as a part of build step, as one of potential solutions. I'm still not sure why you need to know the directory name, as you can import package json and grab values from it directly.

@kettanaito Above, I'm showing you the two use cases where the webpack4 breaks while it was working perfectly in webpack2. They are not directly related.
I'm required to use the require.resolve() because I need access to third party modules' path (I do not know in which node_modules they are installed in because it could be in any parent folder's node_modules). path.resolve() will not be able the handle this case.
So somehow, the webpack4 (maybe webpack3 too?) is breaking my code sharing between my backend and frontend shared code.
I believe it is therefore that it is related to the OP.


Cannot build with Carthage

I got this
*** xcodebuild output can be found in /var/folders/5y/fymdpwc907qd9sy1y4ncl4m80000gn/T/carthage-xcodebuild.WbKcew.log
*** Building scheme "PagingMenuController" in PagingMenuController.xcodeproj
** CLEAN FAILED **

The following build commands failed:
        Check dependencies
(1 failure)
** BUILD FAILED **

The following build commands failed:
        Check dependencies
(1 failure)
A shell task (/usr/bin/xcrun xcodebuild -project /Users/Minerva/src/scm.globalnet-ex.com/push7-ios/ios-native/Carthage/Checkouts/PagingMenuController/PagingMenuController.xcodeproj -scheme PagingMenuController -configuration Release -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build) failed with exit code 65:
** CLEAN FAILED **

The following build commands failed:
        Check dependencies
(1 failure)
** BUILD FAILED **

The following build commands failed:
        Check dependencies
(1 failure)

Swift version: 2.3
Xcode version: 8.1
PagingMenuController version: 1.2.0

Did you ru carthage update --toolchain com.apple.dt.toolchain.Swift_2_3 or can you download Xcode 8.2.1 and try again?

It works, thank you very much.

Good to know.


Error loading iOSInjection.bundle

Error loading /Applications/InjectionIII.app/Contents/Resources/iOSInjection.bundle/iOSInjection:  dlopen(/Applications/InjectionIII.app/Contents/Resources/iOSInjection.bundle/iOSInjection, 265): Library not loaded: @rpath/libswiftCore.dylib
Referenced from: /Applications/InjectionIII.app/Contents/Resources/iOSInjection.bundle/iOSInjection
Reason: image not found
xcode 11.3.1 (11C504)

HI, Is this the App Store version? Do you have your Xcode at the standard path /Applications/Xcode.app

HI, Is this the App Store version? Do you have your Xcode at the standard path /Applications/Xcode.app

Xcode Version 11.6 (11E708)  no problems.


CSUB-922: Improve automatic runtimeUpgrade debug capabilities

Description of proposed changes

Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (a8314df) 70.64% compared to head (3c6be94) 13.68%.

Additional details and impacted files
@@             Coverage Diff             @@
##              dev    #1431       +/-   ##
===========================================
- Coverage   70.64%   13.68%   -56.96%
===========================================
  Files         111       31       -80
  Lines       13009     1001    -12008
  Branches      128      128
===========================================
- Hits         9190      137     -9053
+ Misses       3819      864     -2955

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Bots] Add @all-contributors

Description
 Add all-contributors to the project for appreciating individuals who give time and efforts in making this project.
Reference
You may refer to this commit from houseofgeeks/hg

closing this as bot is already added


Out-of-memory exceptions

Moved here from https://github.com/http4s/blaze/issues/56
@bryce-anderson This behaviour appears when I use SimpleHttp1Client for the requests. According to the documentation, expect should close the connection, but without an explicit shutdownNow call, the threads do not get disposed of.

.expect will close the connection, but it won't shut down the thread pool that belongs to the client. The thread pool won't be shut down without explicitly calling shutdownNow. Just make one SimpleHttpClient or PooledHttpClient and reuse it, shutting it down when you're finished with that client.
If you're still having trouble, please feel free to reopen this issue and post a complete example.


Write project initialiser

It should be easy to start a new project and use these components.
Therefore we would write something similar to Create React App (CRA) that would allow people to generate a boilerplate project with a single command.

Required by #25.

Looks like we will need to publish before this will work.

This is now done, notwithstanding #86 and #87.

Minimal documentation is available here: https://www.npmjs.com/package/@not-govuk/create
More will be available with the merging of #77.


BehaviorSuperCircleJs

Recipe Name
BehaviorSuperCircleJs

Recipe Description
Port @i-am-tom's Super Circle game.
This will be a nice demonstration of the behavior library (and a contrast to our existing game recipes that use the signal library).
@i-am-tom, do we have your permission to copy and edit your work here under the MIT license?
@vladciobanu, I see you were looking for an open recipe request in your stream. Would you like to tackle this one?

Just a thought. If this shows off the behavior library, should that have its own prefix like Halogen and React?

Hey - I would absolutely be OK with this! I feel honoured 😳
If it helps, there's a talk to go with it https://www.youtube.com/watch?v=DWNnPh0o4NE

If this shows off the behavior library, should that have its own prefix

I assume you mean a reserved suffix. Let's see how many more of these recipes are created. If any are duplicated across libraries, then it makes more sense to switch to a suffix to keep them adjacent in the recipe list.

Yeah, I mean suffix :sweat_smile: Ok, sounds good!


Bump library-go to make external CCM default for OpenStack

THIS IS CURRENTLY INTENTIONALLY AN EMPTY COMMIT!
When https://github.com/openshift/library-go/pull/1359 merges I will update this PR with the resulting head of library-go.
This change needs to be committed against all of:

https://github.com/openshift/library-go
https://github.com/openshift/cluster-cloud-controller-manager-operator
https://github.com/openshift/machine-config-operator
https://github.com/openshift/cluster-kube-controller-manager-operator
https://github.com/openshift/cluster-kube-apiserver-operator

Unfortunately this will break OpenStack deployments during the period that it is only partially committed. To reduce the amount of time that OpenStack deployments are broken I am looking for pre-approvals in all repos before starting to merge any of them.

/hold


Uuuu

What does this PR do?
Which problem(s) does it fix and how? What does this PR add?
Where should the reviewer start?
Explain what should be set-up first in order to get the review started. Which page has to be viewed etc.
How should this be manually tested?

[x] Write down all
[x] the steps a person
[x] needs to take to test it.

Documents
Screenshots (if appropriate)
If this PR changes something that concerns UI changes, please post before and after screenshots here.
Other documents
If you have any documents that have anything to do with this PR.
Who should be notified?

[x] Write down the name/department this branch needs
[x] to be communicated to
[x] Check the box(es) to indicate that it has been
[x] communicated (add the label)

What should happen on deployment? (check all that apply)

[x] The usual steps.
[x] There are database changes, which should be run.
[x] There are files that should be manually uploaded.

Questions:

Does this require a blog post?
Does this require a knowledge base update?
Does support need training for this?
Does this has to be communicated to partners?

@


Get ceil value of the eviction count

Description:
$Subject

Closing this issue, Since we already merged the fix to master branch


 Followpath completes 100m within 17 secs

Expected Behavior

To slowly walk to the waypoint using the speed from walk_max and walk_min
Actual Behavior

Completed a 100m dash in 17 secs
Your FULL config.json (remove your username, password, gmapkey and any other private info)

> {

"// websocket_server": false,
"heartbeat_threshold": 10,
"enable_social": true,
"live_config_update": {
  "enabled": true,
  "tasks_only": false
},
"tasks": [
  {
    "type": "TelegramTask",
    "config": {
      "enabled": true,
      "master": ,
      "password": "",
      "alert_catch": {
        "all": {"operator": "or", "cp": 1200, "iv": 0.9}
        }
    }
  },
  {
    "type": "HandleSoftBan"
  },
  {
    "type": "RandomAlivePause",
    "config": {
      "enabled": true,
      "min_duration": "00:00:10",
      "max_duration": "00:20:00",
      "min_interval": "00:30:00",
      "max_interval": "01:00:00"
    }
  },
  {
     "type": "CollectLevelUpReward",

"config": {
"collect_reward": true,
"level_limit": -1
}
},
{
"type": "IncubateEggs",
"config": {
"enabled": true,
"infinite_longer_eggs_first": false,
"breakable_longer_eggs_first": true,
"min_interval": 120,
"infinite": [2,5,10],
"breakable": [5,10]
}
},
{
"type": "ShowBestPokemon",
"config": {
"enabled": true,
"min_interval": 60,
"amount": 5,
"order_by": "cp",
"info_to_show": ["cp", "ivcp", "dps", "hp"]
}
},
{
"type": "PokemonOptimizer",
"config": {
"enabled": true,
"transfer": true,
"transfer_wait_min": 3,
"transfer_wait_max": 5,
"evolve": true,
"evolve_time": 20,
"evolve_for_xp": true,
"evolve_only_with_lucky_egg": false,
"evolve_count_for_lucky_egg": 92,
"may_use_lucky_egg": false,
"min_slots_left": 10,
"upgrade_level": 60,
"groups": {
"trash" : ["Pidgey", "Rattata", "Caterpie", "Weedle", "Venonat"]
},
"keep": [
{
"mode": "by_pokemon",
"names": ["Eevee"],
"top": 1,
"evolve": false,
"sort": ["iv", "cp"],
"upgrade": false
},
{
"mode": "by_family",
"top": 1,
"evolve": true,
"sort": ["iv", "cp"],
"upgrade": false
},
{
"mode": "by_family",
"top": 1,
"evolve": true,
"sort": ["ncp", "iv"],
"upgrade": false
},
{
"mode": "by_family",
"top": 1,
"evolve": false,
"sort": ["cp"],
"upgrade": false
},
{
"mode": "by_family",
"names": ["trash"],
"top": 1,
"evolve": true,
"sort": ["iv","cp"],
"upgrade": false
}
]
}
},
{
"type": "NicknamePokemon",
"config": {
"enabled": true,
"dont_nickname_favorite": true,
"nickname_above_iv": 0.8,
"nickname_template": "{name:.9s}_{iv_pct2}",
"nickname_wait_min": 3,
"nickname_wait_max": 5
}
},
{
"type": "RecycleItems",
"config": {
"min_empty_space": 30,
"max_balls_keep": 200,
"max_potions_keep": 70,
"max_berries_keep": 30,
"max_revives_keep": 20,
"item_filter": {
"Pokeball":       { "keep" : 80 },
"Greatball":      { "keep" : 100 },
"Potion":         { "keep" : 0 },
"Super Potion":   { "keep" : 20 },
"Hyper Potion":   { "keep" : 30 },
"Revive":         { "keep" : 20 },
"Razz Berry":     { "keep" : 30 }
},
"recycle_wait_min": 3,
"recycle_wait_max": 5,
"recycle_force": true,
"recycle_force_min": "00:01:00",
"recycle_force_max": "00:10:00"
}
},
{
"type": "CatchPokemon",
"config": {
"catch_visible_pokemon": true,
"catch_lured_pokemon": true,
"min_ultraball_to_keep": 10,
"berry_threshold": 0.40,
"vip_berry_threshold": 0.9,
"treat_unseen_as_vip": true,
"daily_catch_limit": 300,
"vanish_settings": {
"consecutive_vanish_limit": 10,
"rest_duration_min": "02:00:00",
"rest_duration_max": "04:00:00"
},
"catch_throw_parameters": {
"excellent_rate": 0.1,
"great_rate": 0.2,
"nice_rate": 0.3,
"normal_rate": 0.4,
"spin_success_rate" : 0.55,
"hit_rate": 0.70
},
"catch_simulation": {
"flee_count": 3,
"flee_duration": 2,
"catch_wait_min": 2,
"catch_wait_max": 6,
"berry_wait_min": 2,
"berry_wait_max": 3,
"changeball_wait_min": 3,
"changeball_wait_max": 5,
"newtodex_wait_min": 20,
"newtodex_wait_max": 30
}
}
},
{
"type": "SpinFort",
"config": {
"enabled": true,
"spin_wait_min": 3,
"spin_wait_max": 6,
"daily_spin_limit": 1900
}
},
{ "type": "UpdateWebInventory",
"config": {
"enabled": true
}
},
{
"type": "FollowPath",
"config": {
"enabled": true,
"walker": "PolylineWalker",
"path_mode": "loop",
"path_start_mode": "closest",
"path_file": "configs/path.downtown.json",
"number_lap": 2,
"timer_restart_min": "00:10:00",
"timer_restart_max": "00:20:00"
}
},
{
"type": "CampFort",
"config": {
"enabled": true,
"max_distance": 400,
"min_forts_count": 2,
"min_lured_forts_count": 1,
"camping_time": 1800,
"moving_time": 600
}
},
{
"type": "MoveToMapPokemon",
"config": {
"enabled": false,
"address": "http://localhost:5000",
"//NOTE: Change the max_sniping_distance to adjust the max sniping range (m)": {},
"max_sniping_distance": 20000000,
"//NOTE: Change the max_walking_distance to adjust the max walking range when snipe is off (m)": {},
"max_walking_distance": 1000,
"min_ball": 20,
"prioritize_vips": true,
"snipe": true,
"snipe_high_prio_only": true,
"snipe_high_prio_threshold": 500,
"update_map": true,
"mode": "priority",
"map_path": "raw_data",
"walker": "StepWalker",
"max_extra_dist_fort": 10,
"skip_rounds": 50,
"update_map_min_distance_meters": 500,
"update_map_min_time_sec": 120,
"snipe_sleep_sec": 2,
"snipe_max_in_chain": 1,
"debug": false,
"catch": {
"==========Legendaries==========": 0,
"Aerodactyl": 1000,
"Snorlax": 1000,
"Articuno": 1000,
"Zapdos": 1000,
"Moltres": 1000,
"Dratini": 400,
"Dragonair": 900,
"Dragonite": 1000,
"Mewtwo": 1000,
"Mew": 1000,
        "==========Region Locked==========": 0,
        "Farfetch'd": 1000,
        "Kangaskhan": 1000,
        "Mr. Mime": 1000,
        "Tauros": 400,

        "==========Very Rare==========": 0,
        "Lapras": 900,
        "Electabuzz": 900,
        "Magmar": 600,
        "Ditto": 900,

        "==========Starters==========": 0,
        "Venusaur": 1000,

        "Charizard": 1000,

        "Blastoise": 1000,

        "Pikachu": 600,
        "Raichu": 1000,

        "==========Semi Rare==========": 0,
        "Porygon": 600,
        "Scyther": 600,
        "Jynx": 600,
        "Hitmonlee": 600,
        "Hitmonchan": 600,

        "==========Uncommon==========": 0,

        "Omanyte": 150,
        "Omastar": 500,

        "Seel": 300,
        "Dewgong": 500,

        "Grimer": 200,
        "Muk": 500,

        "Shellder": 200,
        "Cloyster": 500,

        "Haunter": 500,
        "Gengar": 1000,

        "Onix": 600,

        "Drowzee": 600,

        "Hypno": 600,

        "Vulpix": 200,
        "Ninetales": 600,

        "Growlithe": 200,
        "Arcanine": 700,

        "Mankey": 150,
        "Primeape": 500,

        "Clefairy": 150,
        "Clefable": 500,

        "Diglett": 200,
        "Dugtrio": 500,

        "Meowth": 250,
        "Persian": 500,

        "Psyduck": 150,
        "Golduck": 500,

        "Geodude": 100,
        "Graveler": 500,
        "Golem": 800,

        "Kabuto": 150,
        "Kabutops": 500,

        "Gyarados": 800,

        "Ponyta": 200,
        "Rapidash": 500,

        "Cubone": 300,
        "Marowak": 800,

        "Hitmonlee": 600,

        "Hitmonchan": 600,

        "Lickitung": 600,

        "Koffing": 200,
        "Weezing": 500,

        "Rhyhorn": 200,
        "Rhydon": 500,

        "Chansey": 800

      }
    }
  },
  {
    "type": "MoveToFort",
    "config": {
        "enabled": true,
        "lure_attraction": true,
        "lure_max_distance": 3000,
        "walker": "PolylineWalker",
        "log_interval": 5
    }
  },
  {
    "type": "FollowSpiral",
    "config": {
      "enabled": true,
      "diameter": 4,
      "step_size": 70
    }
  }
],
"map_object_cache_time":5,
"forts": {
  "avoid_circles": false,
  "max_circle_size": 10,
  "cache_recent_forts": true
},
  "pokemon_bag": {
  "// if 'show_at_start' is true, it will log all the pokemons in the bag (not eggs) at bot start": {},
  "show_at_start": true,
  "// if 'show_count' is true, it will show the amount of each pokemon (minimum 1)": {},
  "show_count": true,
  "// if 'show_candies' is true, it will show the amount of candies for each pokemon": {},
  "show_candies": true,
  "// 'pokemon_info' parameter define which info to show for each pokemon": {},
  "// the available options are": {},
  "// ['cp', 'iv_ads', 'iv_pct', 'ivcp', 'ncp', 'level', 'hp', 'moveset', 'dps']": {},
  "pokemon_info": ["cp", "iv_pct"]
},
"walk_max": 4.05,
"walk_min": 1.5,
"alt_min": 50,
"alt_max": 150,
"gps_default_altitude": 8.0,
"replicate_gps_xy_noise": true,
"replicate_gps_z_noise": true,
"gps_xy_noise_range": 0.000025,
"gps_z_noise_range": 12.5,
"debug": false,
"test": false,
"walker_limit_output": false,
"health_record": true,
"location_cache": true,
"distance_unit": "km",
"reconnecting_timeout": 15,
"logging": {
  "color": true,
  "show_datetime": true,
  "show_process_name": true,
  "show_log_level": true,
  "show_thread_name": false
},
"catch": {

"Pidgey": {"catch_above_cp": 200, "catch_above_iv": 0.8, "logic": "and"},
"Rattata": {"catch_above_cp": 100, "catch_above_iv": 0.8, "logic": "and"},
"Venonat": {"catch_above_cp": 100, "catch_above_iv": 0.8, "logic": "and"},
"Caterpie": {"catch_above_cp": 100, "catch_above_iv": 0.8, "logic": "and"},
"Magikarp": {"catch_above_cp": 100, "catch_above_iv": 0.8, "logic": "and"},
"any": {"catch_above_cp": 100, "catch_above_iv": 0.80, "logic": "or"}
},
"vips" : {
"Any pokemon put here directly force to use Berry & Best Ball to capture, to secure the capture rate!": {},
"any": {"catch_above_cp": 1200, "catch_above_iv": 0.9, "logic": "or" },
"Lapras": {},
"Moltres": {},
"Zapdos": {},
"Articuno": {},
    "// S-Tier pokemons (if pokemon can be evolved into tier, list the representative)": {},
    "Mewtwo": {},
    "Dragonite": {},
    "Snorlax": {},
    "// Mew evolves to Mewtwo": {},
    "Mew": {},
    "Arcanine": {},
    "Gyarados": {},
    "Muk": {},
    "Weezing": {},
    "Farfetch'd": {},
    "Kangaskhan": {},
    "Mr. Mime": {},
    "Tauros": {},
    "Chansey": {},
    "Hitmonlee": {},
    "Hitmonchan": {},
    "Lickitung": {}
},

"// websocket": {
"start_embedded_server": true,
"server_url": "<IP_ADDRESS>:4000"
}
}

Output when issue occurred

[2016-09-08 17:14:43] [FollowPath] [INFO] Walking from (1.2822329603267415,<PHONE_NUMBER>4464244, 6.9831008920896815) to (1.28159, 103.84954, 8.0), distance left: (0.13 km) ..
[2016-09-08 17:14:44] [FollowPath] [INFO] Walking from (1.2822173743405245,<PHONE_NUMBER>2724482, 7.019579344939509) to (1.28159, 103.84954, 8.0), distance left: (0.13 km) ..
[2016-09-08 17:14:44] [FollowPath] [INFO] Walking from (1.282207140150134,<PHONE_NUMBER>3027034, 6.870531895863424) to (1.28159, 103.84954, 8.0), distance left: (0.12 km) ..
[2016-09-08 17:14:46] [FollowPath] [INFO] Walking from (1.2821885064333336,<PHONE_NUMBER>0593056, 7.006849357343985) to (1.28159, 103.84954, 8.0), distance left: (0.12 km) ..
[2016-09-08 17:14:46] [FollowPath] [INFO] Walking from (1.2821764800511342,<PHONE_NUMBER>2210817, 6.81169709598659) to (1.28159, 103.84954, 8.0), distance left: (0.12 km) ..
[2016-09-08 17:14:46] [FollowPath] [INFO] Walking from (1.282158851833149,<PHONE_NUMBER>0232228, 6.5877677667145615) to (1.28159, 103.84954, 8.0), distance left: (0.11 km) ..
[2016-09-08 17:14:47] [FollowPath] [INFO] Walking from (1.2821531514554323,<PHONE_NUMBER>0136663, 6.737180797950861) to (1.28159, 103.84954, 8.0), distance left: (0.11 km) ..
[2016-09-08 17:14:47] [FollowPath] [INFO] Walking from (1.2821435645809875,<PHONE_NUMBER>8048802, 6.692980364469391) to (1.28159, 103.84954, 8.0), distance left: (0.11 km) ..
[2016-09-08 17:14:48] [FollowPath] [INFO] Walking from (1.2821249819883451,<PHONE_NUMBER>365683, 6.4307794807360725) to (1.28159, 103.84954, 8.0), distance left: (0.11 km) ..
[Errno 104] Connection reset by peer
[2016-09-08 17:14:51] [FollowPath] [INFO] Walking from (1.2821046031059775,<PHONE_NUMBER>0023392, 6.696229715587473) to (1.28159, 103.84954, 8.0), distance left: (0.10 km) ..
[2016-09-08 17:14:51] [FollowPath] [INFO] Walking from (1.2820895909344112,<PHONE_NUMBER>2769884, 6.39928771721838) to (1.28159, 103.84954, 8.0), distance left: (0.10 km) ..
[2016-09-08 17:14:52] [FollowPath] [INFO] Walking from (1.2820736494507539,<PHONE_NUMBER>1440362, 6.561910277071261) to (1.28159, 103.84954, 8.0), distance left: (0.10 km) ..
[2016-09-08 17:14:52] [FollowPath] [INFO] Walking from (1.2820625565007053,<PHONE_NUMBER>9184692, 6.1879122387896475) to (1.28159, 103.84954, 8.0), distance left: (0.09 km) ..
[2016-09-08 17:14:53] [FollowPath] [INFO] Walking from (1.282044204740045,<PHONE_NUMBER>4558099, 6.081337295838932) to (1.28159, 103.84954, 8.0), distance left: (0.09 km) ..
[2016-09-08 17:14:55] [FollowPath] [INFO] Walking from (1.2820277346917104,<PHONE_NUMBER>1962031, 6.149848154465416) to (1.28159, 103.84954, 8.0), distance left: (0.09 km) ..
[2016-09-08 17:14:57] [FollowPath] [INFO] Walking from (1.2820157630513938,<PHONE_NUMBER>1821017, 6.03107376132378) to (1.28159, 103.84954, 8.0), distance left: (0.08 km) ..
[2016-09-08 17:14:58] [FollowPath] [INFO] Walking from (1.282006488297446,<PHONE_NUMBER>1668609, 6.079000003988139) to (1.28159, 103.84954, 8.0), distance left: (0.08 km) ..
[2016-09-08 17:14:58] [FollowPath] [INFO] Walking from (1.2819965841229959,<PHONE_NUMBER>8651257, 6.239070676921683) to (1.28159, 103.84954, 8.0), distance left: (0.08 km) ..
[2016-09-08 17:14:58] [FollowPath] [INFO] Walking from (1.281983788201427,<PHONE_NUMBER>9415076, 6.160117770656144) to (1.28159, 103.84954, 8.0), distance left: (0.08 km) ..
[2016-09-08 17:14:58] [FollowPath] [INFO] Walking from (1.2819595265958836,<PHONE_NUMBER>1686333, 6.14419774650847) to (1.28159, 103.84954, 8.0), distance left: (0.07 km) ..
[2016-09-08 17:14:58] [FollowPath] [INFO] Walking from (1.2819530495092883,<PHONE_NUMBER>0081783, 5.809002317798816) to (1.28159, 103.84954, 8.0), distance left: (0.07 km) ..
[2016-09-08 17:14:58] [FollowPath] [INFO] Walking from (1.2819396025193648,<PHONE_NUMBER>7368704, 6.013795541508898) to (1.28159, 103.84954, 8.0), distance left: (0.07 km) ..
[2016-09-08 17:14:58] [ShowBestPokemon] [INFO] [Dragonite, CP 1903, IVCP 0.61, DPS 15.04, HP 110/110] | [Exeggutor, CP 1672, IVCP 0.93, DPS 12.63, HP 120/120] | [Snorlax, CP 1592, IVCP 0.96, DPS 14.76, HP 188/188] | [Slowbro, CP 1543, IVCP 0.62, DPS 11.1, HP 128/128] | [Poliwrath, CP 1412, IVCP 0.58, DPS 15.07, HP 112/112]
[2016-09-08 17:14:58] [FollowPath] [INFO] Walking from (1.2819212199911862,<PHONE_NUMBER>4571042, 5.9986907722255784) to (1.28159, 103.84954, 8.0), distance left: (0.07 km) ..
[2016-09-08 17:14:58] [FollowPath] [INFO] Walking from (1.2819021017387908,<PHONE_NUMBER>1182864, 5.884047698539518) to (1.28159, 103.84954, 8.0), distance left: (0.06 km) ..
[2016-09-08 17:14:58] [FollowPath] [INFO] Walking from (1.2818875268892536,<PHONE_NUMBER>0591895, 5.961126733794691) to (1.28159, 103.84954, 8.0), distance left: (0.06 km) ..
[2016-09-08 17:14:58] [FollowPath] [INFO] Walking from (1.281877693976794,<PHONE_NUMBER>7534087, 5.937811099180854) to (1.28159, 103.84954, 8.0), distance left: (0.06 km) ..
[2016-09-08 17:14:58] [FollowPath] [INFO] Walking from (1.281869464874571,<PHONE_NUMBER>4817698, 6.169356850129349) to (1.28159, 103.84954, 8.0), distance left: (0.06 km) ..
[2016-09-08 17:14:58] [FollowPath] [INFO] Walking from (1.2818524229388346,<PHONE_NUMBER>7287854, 5.8894334753407644) to (1.28159, 103.84954, 8.0), distance left: (0.05 km) ..
[2016-09-08 17:14:59] [FollowPath] [INFO] Walking from (1.2818366011298046,<PHONE_NUMBER>4290564, 6.07201137960963) to (1.28159, 103.84954, 8.0), distance left: (0.05 km) ..
[2016-09-08 17:14:59] [FollowPath] [INFO] Walking from (1.2818220605154116,<PHONE_NUMBER>4098141, 6.060498823247519) to (1.28159, 103.84954, 8.0), distance left: (0.05 km) ..
[2016-09-08 17:14:59] [FollowPath] [INFO] Walking from (1.2818127277038827,<PHONE_NUMBER>0901275, 5.8179675692190544) to (1.28159, 103.84954, 8.0), distance left: (0.04 km) ..
[2016-09-08 17:14:59] [FollowPath] [INFO] Walking from (1.2818015352885703,<PHONE_NUMBER>6929958, 6.019985316072789) to (1.28159, 103.84954, 8.0), distance left: (0.04 km) ..
[2016-09-08 17:14:59] [FollowPath] [INFO] Walking from (1.2817889197071597,<PHONE_NUMBER>9100651, 6.1629680883794205) to (1.28159, 103.84954, 8.0), distance left: (0.04 km) ..
[2016-09-08 17:14:59] [FollowPath] [INFO] Walking from (1.281779669264147,<PHONE_NUMBER>245992, 5.834310162945999) to (1.28159, 103.84954, 8.0), distance left: (0.04 km) ..
[2016-09-08 17:14:59] [FollowPath] [INFO] Walking from (1.2817753093145552,<PHONE_NUMBER>5217383, 6.039551124080895) to (1.28159, 103.84954, 8.0), distance left: (0.03 km) ..
[2016-09-08 17:14:59] [FollowPath] [INFO] Walking from (1.281767773236263,<PHONE_NUMBER>948893, 6.1285970751347785) to (1.28159, 103.84954, 8.0), distance left: (0.03 km) ..
[2016-09-08 17:14:59] [FollowPath] [INFO] Walking from (1.2817591905414398,<PHONE_NUMBER>770986, 5.964372475321875) to (1.28159, 103.84954, 8.0), distance left: (0.03 km) ..
[2016-09-08 17:14:59] [FollowPath] [INFO] Walking from (1.2817397574507825,<PHONE_NUMBER>1001428, 5.624440393289487) to (1.28159, 103.84954, 8.0), distance left: (0.03 km) ..
[2016-09-08 17:14:59] [FollowPath] [INFO] Walking from (1.2817210091065274,<PHONE_NUMBER>9366355, 5.558625536755718) to (1.28159, 103.84954, 8.0), distance left: (0.02 km) ..
[2016-09-08 17:14:59] [FollowPath] [INFO] Walking from (1.2817142106839563,<PHONE_NUMBER>7866356, 5.687042991253283) to (1.28159, 103.84954, 8.0), distance left: (0.02 km) ..
[2016-09-08 17:15:00] [FollowPath] [INFO] Walking from (1.2817010140379081,<PHONE_NUMBER>6796408, 5.7156884003350195) to (1.28159, 103.84954, 8.0), distance left: (0.02 km) ..
[2016-09-08 17:15:00] [FollowPath] [INFO] Walking from (1.2816940066543274,<PHONE_NUMBER>9971715, 5.635705808826364) to (1.28159, 103.84954, 8.0), distance left: (0.02 km) ..
[2016-09-08 17:15:00] [FollowPath] [INFO] Walking from (1.2816867237140754,<PHONE_NUMBER>7065167, 5.540045912976002) to (1.28159, 103.84954, 8.0), distance left: (0.01 km) ..
[2016-09-08 17:15:00] [FollowPath] [INFO] Walking from (1.2816701572800249,<PHONE_NUMBER>3373465, 5.3368082723085815) to (1.28159, 103.84954, 8.0), distance left: (0.01 km) ..
[2016-09-08 17:15:00] [FollowPath] [INFO] Walking from (1.281660355867361,<PHONE_NUMBER>6095435, 5.493707363433482) to (1.28159, 103.84954, 8.0), distance left: (0.01 km) ..
[2016-09-08 17:15:00] [FollowPath] [INFO] Walking from (1.2816425159886293,<PHONE_NUMBER>6226941, 5.474183746956065) to (1.28159, 103.84954, 8.0), distance left: (0.01 km) ..
[2016-09-08 17:15:00] [FollowPath] [INFO] Walking from (1.2816212333081076,<PHONE_NUMBER>6587411, 5.261470935109754) to (1.28159, 103.84954, 8.0), distance left: (0.00 km) ..
[2016-09-08 17:15:00] [FollowPath] [INFO] Walking from (1.281601577114721,<PHONE_NUMBER>8323577, 5.316136500049653) to (1.28159, 103.84954, 8.0), distance left: (0.00 km) ..

Steps to Reproduce

Task Bot to use followpath
Other Information
OS: Linux Mint

Branch: dev

Git Commit: 6aea15fc0a201d529de8c9d4cb3bf19cebc1cbb4

Python Version:

Any other relevant files/configs (eg: path files)

Yeah... After I've updated to the current commit, the bot suddenly walks faster than usual...

I'm seeing the same thing.
[2016-09-08 08:00:38] [MainThread] [MoveToFort] [INFO] Moving towards pokestop Mill Creek Tree Chair - 0.30mi [2016-09-08 08:00:43] [MainThread] [MoveToFort] [INFO] Moving towards pokestop Mill Creek Tree Chair - 0.24mi [2016-09-08 08:00:48] [MainThread] [MoveToFort] [INFO] Moving towards pokestop Mill Creek Tree Chair - 0.06mi [2016-09-08 08:00:50] [MainThread] [  SpinFort] [INFO] Found nothing in pokestop Mill Creek Tree Chair. [2016-09-08 08:00:50] [MainThread] [  SpinFort] [INFO] Possibly searching too often, take a rest. [2016-09-08 08:00:50] [MainThread] [  SpinFort] [INFO] Probably got softban.

Looks like the issue was introduced in either eb3861ea5e46df4c1b5f2e471ec85f01b0012cad or 6aea15fc0a201d529de8c9d4cb3bf19cebc1cbb4.
I'm on b66fc8854a5594370ecc6a52266251c1a7dc5e13 which seems fine so far.

Just tested it and I experienced the same problem.
Mine finish 0.07km (70m) in just about 4 seconds.

[2016-09-08 08:32:10] [FollowPath] [INFO] Walking from (34.00973713827172, -118.49610241898421, 8.0) to (34.0100744, -118.4954908, 8.0), distance left: (0.07 km) ..
[2016-09-08 08:32:11] [FollowPath] [INFO] Walking from (34.009717582701036, -118.49608553638684, 7.361054085061836) to (34.0100744, -118.4954908, 8.0), distance left: (0.07 km) ..
[2016-09-08 08:32:11] [FollowPath] [INFO] Walking from (34.009699966146044, -118.4960698050999, 7.349001020412185) to (34.0100744, -118.4954908, 8.0), distance left: (0.07 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.009716714658104, -118.4960504674608, 7.431829648480365) to (34.0100744, -118.4954908, 8.0), distance left: (0.07 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.00973556232697, -118.49602742195171, 7.303626722018598) to (34.0100744, -118.4954908, 8.0), distance left: (0.06 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.009749311972804, -118.49600504397996, 7.34844525301207) to (34.0100744, -118.4954908, 8.0), distance left: (0.06 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.009763601022215, -118.49598599092276, 7.327685278169569) to (34.0100744, -118.4954908, 8.0), distance left: (0.06 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.00978147150574, -118.49596226956969, 7.329699554330909) to (34.0100744, -118.4954908, 8.0), distance left: (0.05 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.009797326328986, -118.49594327693119, 7.27756024101799) to (34.0100744, -118.4954908, 8.0), distance left: (0.05 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.00981242357502, -118.49592942860367, 7.310429431196136) to (34.0100744, -118.4954908, 8.0), distance left: (0.05 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.00982521801954, -118.49590698806131, 7.286135374333353) to (34.0100744, -118.4954908, 8.0), distance left: (0.05 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.009833354379374, -118.49589504119785, 7.41730225787208) to (34.0100744, -118.4954908, 8.0), distance left: (0.05 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.00984933244021, -118.49587065811636, 7.322082957199905) to (34.0100744, -118.4954908, 8.0), distance left: (0.04 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.0098682600264, -118.4958489082574, 7.5491676555176985) to (34.0100744, -118.4954908, 8.0), distance left: (0.04 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.009879858136486, -118.49583961774368, 7.3879079177083655) to (34.0100744, -118.4954908, 8.0), distance left: (0.04 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.00986244657572, -118.49581903952864, 7.4375063114491935) to (34.0100744, -118.4954908, 8.0), distance left: (0.04 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.009845581861896, -118.49579766442642, 7.592689544147225) to (34.0100744, -118.4954908, 8.0), distance left: (0.04 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.00982864338317, -118.49577317984513, 7.5712772039089) to (34.0100744, -118.4954908, 8.0), distance left: (0.04 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.00981692248845, -118.49575547672237, 7.628669416993432) to (34.0100744, -118.4954908, 8.0), distance left: (0.04 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.00979916315484, -118.49573609874244, 7.423493339289682) to (34.0100744, -118.4954908, 8.0), distance left: (0.04 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.00978346770425, -118.49570375432353, 7.3375018174603275) to (34.0100744, -118.4954908, 8.0), distance left: (0.04 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.00981579350555, -118.49569111235644, 7.4742058101371525) to (34.0100744, -118.4954908, 8.0), distance left: (0.03 km) ..
[2016-09-08 08:32:12] [FollowPath] [INFO] Walking from (34.00984004967829, -118.49570597100663, 7.241467251093178) to (34.0100744, -118.4954908, 8.0), distance left: (0.03 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.00986022504286, -118.49572057629769, 7.026797404883632) to (34.0100744, -118.4954908, 8.0), distance left: (0.03 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.009886379031066, -118.49572993640055, 7.082003195771264) to (34.0100744, -118.4954908, 8.0), distance left: (0.03 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.009910859130635, -118.49573195028421, 7.054955329384899) to (34.0100744, -118.4954908, 8.0), distance left: (0.03 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.00992212490672, -118.49573454241805, 6.9040365353825175) to (34.0100744, -118.4954908, 8.0), distance left: (0.03 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.009946199072644, -118.49573680467859, 7.131225951901328) to (34.0100744, -118.4954908, 8.0), distance left: (0.03 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.00996708699412, -118.49574365512848, 6.949882182833634) to (34.0100744, -118.4954908, 8.0), distance left: (0.03 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.01000634963005, -118.49575244984325, 6.608531749544881) to (34.0100744, -118.4954908, 8.0), distance left: (0.03 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.01003215583815, -118.4957355214638, 6.209474923367359) to (34.0100744, -118.4954908, 8.0), distance left: (0.02 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.01003940053289, -118.49571506479609, 6.145888391895674) to (34.0100744, -118.4954908, 8.0), distance left: (0.02 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.010042252077724, -118.49569723516491, 6.171191987756688) to (34.0100744, -118.4954908, 8.0), distance left: (0.02 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.010031348638876, -118.49567191483246, 6.373713914390571) to (34.0100744, -118.4954908, 8.0), distance left: (0.02 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.01001287557762, -118.49564785982386, 6.17732433293735) to (34.0100744, -118.4954908, 8.0), distance left: (0.02 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.010001776080756, -118.49563108772404, 6.066993110617664) to (34.0100744, -118.4954908, 8.0), distance left: (0.02 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.009988742646115, -118.49560934276101, 5.707188202598376) to (34.0100744, -118.4954908, 8.0), distance left: (0.01 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.00998596189612, -118.49559354479422, 5.700597325917656) to (34.0100744, -118.4954908, 8.0), distance left: (0.01 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.00996870720967, -118.49556742507339, 5.359524931292165) to (34.0100744, -118.4954908, 8.0), distance left: (0.01 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.0099603974448, -118.4955387097374, 5.441801545126239) to (34.0100744, -118.4954908, 8.0), distance left: (0.01 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.00995434427022, -118.49551033089206, 5.305532849638319) to (34.0100744, -118.4954908, 8.0), distance left: (0.01 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.00995528962117, -118.49547685828583, 4.873745324123398) to (34.0100744, -118.4954908, 8.0), distance left: (0.01 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.00996623694503, -118.4954542335799, 4.826416007464941) to (34.0100744, -118.4954908, 8.0), distance left: (0.01 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.0099854618093, -118.49542963251727, 4.946029341286874) to (34.0100744, -118.4954908, 8.0), distance left: (0.01 km) ..
[2016-09-08 08:32:13] [FollowPath] [INFO] Walking from (34.00999869897922, -118.49541092688624, 4.782800505227292) to (34.0100744, -118.4954908, 8.0), distance left: (0.01 km) ..
[2016-09-08 08:32:14] [FollowPath] [INFO] Walking from (34.01000970825056, -118.49541686708336, 4.939300632282756) to (34.0100744, -118.4954908, 8.0), distance left: (0.01 km) ..
[2016-09-08 08:32:14] [FollowPath] [INFO] Walking from (34.01002198421127, -118.49542831132305, 4.753282301258652) to (34.0100744, -118.4954908, 8.0), distance left: (0.01 km) ..
[2016-09-08 08:32:14] [FollowPath] [INFO] Walking from (34.010036167494995, -118.49544418222095, 4.907296652057992) to (34.0100744, -118.4954908, 8.0), distance left: (0.01 km) ..
[2016-09-08 08:32:14] [FollowPath] [INFO] Walking from (34.01005690973815, -118.49546887068136, 4.89483204100976) to (34.0100744, -118.4954908, 8.0), distance left: (0.00 km) ..
[2016-09-08 08:32:14] [FollowPath] [INFO] Walking from (34.010068626649975, -118.49548389537996, 4.716216194321409) to (34.0100744, -118.4954908, 8.0), distance left: (0.00 km) ..

@ShiLingStar do you have the latest commit https://github.com/PokemonGoF/PokemonGo-Bot/commit/b0b1e0f5573d1047793f064f63c46450e2565d4a ?

@Anakin5 I think there are multiple Tasks spawning multiple StepWalkers!

My bad, I believe I just missed the latest commit b0b1e0f5573d1047793f064f63c46450e2565d4a when I was testing it.
I am now testing it again and it seems to fixed.

[2016-09-08 09:27:02] [FollowPath] [INFO] Walking from (34.01432723045102, -118.4971516610032,<PHONE_NUMBER>901429) to (34.0134672, -118.4973576, 8.0), distance left: (0.10 km) ..
[2016-09-08 09:27:06] [FollowPath] [INFO] Walking from (34.01431669169397, -118.49717051221839, 22.32382930825388) to (34.014899, -118.4970599, 8.0), distance left: (0.07 km) ..
[2016-09-08 09:27:07] [FollowPath] [INFO] Walking from (34.014309075122874, -118.49718543565926, 22.569457326799327) to (34.014899, -118.4970599, 8.0), distance left: (0.07 km) ..
[2016-09-08 09:27:08] [FollowPath] [INFO] Walking from (34.014293731070914, -118.49719912849183, 22.40757698222322) to (34.014899, -118.4970599, 8.0), distance left: (0.07 km) ..
[2016-09-08 09:27:09] [FollowPath] [INFO] Walking from (34.01427449371978, -118.49722516563074, 22.308576335334763) to (34.014899, -118.4970599, 8.0), distance left: (0.07 km) ..
[2016-09-08 09:27:10] [FollowPath] [INFO] Walking from (34.01427374779225, -118.49723762202734, 22.46397121392001) to (34.014899, -118.4970599, 8.0), distance left: (0.07 km) ..
[2016-09-08 09:27:11] [FollowPath] [INFO] Walking from (34.014287716366226, -118.49725308964477, 22.443054744943826) to (34.014899, -118.4970599, 8.0), distance left: (0.07 km) ..
[2016-09-08 09:27:11] [FollowPath] [INFO] Walking from (34.014298437972705, -118.49726514261437, 22.53335523529229) to (34.014899, -118.4970599, 8.0), distance left: (0.07 km) ..
[2016-09-08 09:27:12] [FollowPath] [INFO] Walking from (34.014306364419774, -118.49727633014243, 22.485021606089102) to (34.014899, -118.4970599, 8.0), distance left: (0.07 km) ..
[2016-09-08 09:27:14] [FollowPath] [INFO] Walking from (34.01431670616397, -118.4972882807502, 22.65911854170324) to (34.014899, -118.4970599, 8.0), distance left: (0.07 km) ..
[2016-09-08 09:27:14] [FollowPath] [INFO] Walking from (34.01432436365369, -118.49730110459988, 22.80200627402574) to (34.014899, -118.4970599, 8.0), distance left: (0.07 km) ..
[2016-09-08 09:27:15] [FollowPath] [INFO] Walking from (34.01433744927157, -118.49732077349017, 22.770993366421283) to (34.014899, -118.4970599, 8.0), distance left: (0.07 km) ..
[2016-09-08 09:27:16] [FollowPath] [INFO] Walking from (34.01435068955187, -118.49732981829482, 22.68035594144053) to (34.014899, -118.4970599, 8.0), distance left: (0.07 km) ..
[2016-09-08 09:27:17] [FollowPath] [INFO] Walking from (34.014368242945906, -118.49735197116527, 22.8772497624159) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:18] [FollowPath] [INFO] Walking from (34.01439004528275, -118.49737476273901, 22.77856303892145) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:19] [FollowPath] [INFO] Walking from (34.01440568920196, -118.49739045682571, 22.736437304298654) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:20] [FollowPath] [INFO] Walking from (34.01442027148222, -118.49740267842006, 22.597785304997803) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:21] [FollowPath] [INFO] Walking from (34.01443557741463, -118.49741953373783, 22.73887104320641) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:22] [FollowPath] [INFO] Walking from (34.0144458299424, -118.49743136971554, 22.864445128315243) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:23] [FollowPath] [INFO] Walking from (34.01446016132264, -118.49744671093052, 22.89015969974755) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:25] [FollowPath] [INFO] Walking from (34.01447301412575, -118.49745726753365, 22.46533408584239) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:25] [FollowPath] [INFO] Walking from (34.014484975328934, -118.49746910123173, 22.661452076018197) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:26] [FollowPath] [INFO] Walking from (34.014496131570944, -118.4974826955174, 22.470853522593334) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:29] [FollowPath] [INFO] Walking from (34.01450466353878, -118.49749515748141, 22.66140501351914) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:30] [FollowPath] [INFO] Walking from (34.01452519228614, -118.49750240236698, 22.74489983996071) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:31] [FollowPath] [INFO] Walking from (34.0145384827108, -118.49748584824039, 22.84743958518408) to (34.014899, -118.4970599, 8.0), distance left: (0.06 km) ..
[2016-09-08 09:27:32] [FollowPath] [INFO] Walking from (34.014551128721195, -118.49747806064829, 22.83362570212701) to (34.014899, -118.4970599, 8.0), distance left: (0.05 km) ..
[2016-09-08 09:27:33] [FollowPath] [INFO] Walking from (34.014568303755766, -118.49745378303464, 22.72830422934433) to (34.014899, -118.4970599, 8.0), distance left: (0.05 km) ..
[2016-09-08 09:27:35] [FollowPath] [INFO] Walking from (34.014576322140826, -118.49744353630088, 22.825841844017685) to (34.014899, -118.4970599, 8.0), distance left: (0.05 km) ..
[2016-09-08 09:27:36] [FollowPath] [INFO] Walking from (34.01459102793059, -118.497427467666, 22.766043427204362) to (34.014899, -118.4970599, 8.0), distance left: (0.05 km) ..
[2016-09-08 09:27:37] [FollowPath] [INFO] Walking from (34.0146017491849, -118.49741619498238, 22.625817628867612) to (34.014899, -118.4970599, 8.0), distance left: (0.05 km) ..
[2016-09-08 09:27:38] [FollowPath] [INFO] Walking from (34.01461958385336, -118.49739242569771, 22.867317447724467) to (34.014899, -118.4970599, 8.0), distance left: (0.04 km) ..
[2016-09-08 09:27:40] [FollowPath] [INFO] Walking from (34.014637860121425, -118.49736715959872, 22.82917904841144) to (34.014899, -118.4970599, 8.0), distance left: (0.04 km) ..
[2016-09-08 09:27:41] [FollowPath] [INFO] Walking from (34.01465207816462, -118.49734845257676, 22.627735377341995) to (34.014899, -118.4970599, 8.0), distance left: (0.04 km) ..
[2016-09-08 09:27:42] [FollowPath] [INFO] Walking from (34.014672473471784, -118.49732445137698, 22.90292875551955) to (34.014899, -118.4970599, 8.0), distance left: (0.04 km) ..
[2016-09-08 09:27:43] [FollowPath] [INFO] Walking from (34.01469199424649, -118.49730107673227, 22.677219064293908) to (34.014899, -118.4970599, 8.0), distance left: (0.03 km) ..
[2016-09-08 09:27:43] [FollowPath] [INFO] Walking from (34.0147091946876, -118.49727435820279, 22.975560087028484) to (34.014899, -118.4970599, 8.0), distance left: (0.03 km) ..
[2016-09-08 09:27:44] [FollowPath] [INFO] Walking from (34.014729935901016, -118.49724695360936, 22.94116753618541) to (34.014899, -118.4970599, 8.0), distance left: (0.03 km) ..
[2016-09-08 09:27:45] [FollowPath] [INFO] Walking from (34.01474223553737, -118.49723552076358, 22.83693830136357) to (34.014899, -118.4970599, 8.0), distance left: (0.02 km) ..
[2016-09-08 09:27:46] [FollowPath] [INFO] Walking from (34.01475682802363, -118.49721836221394, 22.79710990419932) to (34.014899, -118.4970599, 8.0), distance left: (0.02 km) ..
[2016-09-08 09:27:47] [  SpinFort] [INFO] Spun pokestop Frog Water Fountain. Experience awarded: 50. Items awarded: 1x Potion, 2x Pokeball
[2016-09-08 09:27:52] [FollowPath] [INFO] Walking from (34.01476691041013, -118.4972001700779, 22.707116363706227) to (34.014899, -118.4970599, 8.0), distance left: (0.02 km) ..
[2016-09-08 09:27:53] [FollowPath] [INFO] Walking from (34.01477718705274, -118.49719069373964, 23.02689514465456) to (34.014899, -118.4970599, 8.0), distance left: (0.02 km) ..
[2016-09-08 09:27:54] [FollowPath] [INFO] Walking from (34.014792197898764, -118.49717110223764, 22.954859871387363) to (34.014899, -118.4970599, 8.0), distance left: (0.02 km) ..
[2016-09-08 09:27:54] [FollowPath] [INFO] Walking from (34.01480929556075, -118.49715259755988, 23.03773163477581) to (34.014899, -118.4970599, 8.0), distance left: (0.01 km) ..
[2016-09-08 09:27:55] [FollowPath] [INFO] Walking from (34.01482969105404, -118.49713191870738, 23.074434700880342) to (34.014899, -118.4970599, 8.0), distance left: (0.01 km) ..
[2016-09-08 09:27:57] [FollowPath] [INFO] Walking from (34.0148467227525, -118.49711675995128, 22.73575791028264) to (34.014899, -118.4970599, 8.0), distance left: (0.01 km) ..
[2016-09-08 09:27:58] [FollowPath] [INFO] Walking from (34.01485746217624, -118.4970984002681, 22.95644239978567) to (34.014899, -118.4970599, 8.0), distance left: (0.01 km) ..
[2016-09-08 09:27:59] [FollowPath] [INFO] Walking from (34.014873915743955, -118.49707962386847, 23.00935499494301) to (34.014899, -118.4970599, 8.0), distance left: (0.00 km) ..
[2016-09-08 09:28:00] [FollowPath] [INFO] Walking from (34.014892715934025, -118.49706414736227, 23.114340896598048) to (34.014899, -118.4970599, 8.0), distance left: (0.00 km) ..
[2016-09-08 09:28:00] [FollowPath] [INFO] Loitering for 120 seconds...

@ShiLingStar cool 👍

Fixed


dataset question

why i got these messages:
Ground truth poses are not avaialble for sequence 11.
Ground truth poses are not avaialble for sequence 12.
Ground truth poses are not avaialble for sequence 13.
when i run test.py?
it seems that kitti dataset dosen't have ground truth poses of sequence 11-22?

You don't need to worry about this. It's just a moderate warning from pykitti module.
https://github.com/gitouni/CalibNet_pytorch/blob/25fdfa519ea0963d80ad76a0817af886cb144442/dataset.py#L116-L116
The ground-truth poses of sequence 11-20 are not provided by KITTI because these sequences are used for fair testing, and that is why the pykitti.odometry() threw that warning. However, it does not affect the calibration process, so do not worry about that.

how can i get the poses in the dataset?

how can i get the poses in the dataset?

We all have no access to the poses of sequences for testing. They're used for online evaluation of odometry performance.

How the poses is obtained in the figure below？
At 2023-09-13 17:46:03, "gitouni" @.***> wrote:
how can i get the poses in the dataset?
We all have no access to the poses of sequences for testing. They're used for online evaluation of odometry performance.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

How the poses is obtained in the figure below？ At 2023-09-13 17:46:03, "gitouni" @.> wrote: how can i get the poses in the dataset? We all have no access to the poses of sequences for testing. They're used for online evaluation of odometry performance. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.>

Sorry, I cannot see that figure that you want to display. However, the poses are not necessary for this calibration, as CalibNet works on a single-frame mode.

I have resulted! Thank you!
| |
@.***
|
|
@.***
|
---- Replied Message ----
| From | @.> |
| Date | 09/14/2023 09:34 |
| To | @.> |
| Cc |<EMAIL_ADDRESS>|
| Subject | Re: [gitouni/CalibNet_pytorch] dataset question (Issue #7) |
How the poses is obtained in the figure below？ At 2023-09-13 17:46:03, "gitouni" @.> wrote: how can i get the poses in the dataset? We all have no access to the poses of sequences for testing. They're used for online evaluation of odometry performance. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.>
Sorry, I cannot see that figure that you want to display. However, the poses are not necessary for this calibration, as CalibNet works on a single-frame mode.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


Very sad!

After @mxstbr leaves, RBP is developed little and little, i am very sad about this, how are you guys feeling?

@blling  Is there any formal announcement he is leaving RBP development?

Never left, I just founded a startup and am not using react-boilerplate at the moment, so I don't have any time to devote to it.

Thank you @mxstbr for the clarification.

yarn upgrade-interactive

Thanks @mxstbr

@mxstbr I am sorry , but there is no active maintenance on RBP, what is the long term goal ?

I agree with @gretzky . We are thanksful to RBP and @mxstbr for giving us the tools that let us start in the react ecosystem. I believe create-react-app is mature enough but I personally haven't used it yet. Could anybody experienced list what are the things we will need to implement ourself to get a RBP starting from create-react-app?

I think RBP needs more maintainers, because most are not active, who wants to be a volunteer...

I'll happily invite people to this organization to maintain the project/merge outstanding PRs/triage issues. See this comment for the direction the project should (imo) take: https://github.com/react-boilerplate/react-boilerplate/issues/1776#issuecomment-305529851
If you want to work on that vision, please be my guest, just tell me who to invite!

@mxstbr i'd love to take a crack at some work on it. i'm not sure if i'm in full agreement of migrating to create-react-app, but i can definitely handle some outstanding issues & PRs based on the contribution docs provided.

@blling you're not going to volunteer? you seem to have a lot of opinions on it.

I would love to help out as well.  ;)
My and my team has been working fulltime with the react-boilerplate for 4 months now and have 2-3 more in the current project we have, before we begin the next.
Out version uses a headless CMS where wordpress handles content management and react-boilerplate is a standalone frontend.
We have made some pretty good experience with this.
I can contribute with some project management, and make sure we get some PRs closed and we move forward. I won’t have time to do any development myself.
My current - and only - contribution so far has been to update the readme to show all our backers. 😂
So I would love to help out and hopefully remove some rocks on the road so the amazing developers who contribute can do what they do best. :)
LinkedIn link: http://linkedin.com/in/andersgerner

@gretzky no matter, even just closing all of these question issues and pointing people to StackOverflow would help a ton. (on top of merging PRs etc) Invited both you and @AndersGerner, check your notifications/email inbox!

@mxstbr no notif yet! not sure how long it takes

Could you add me too?

RBP's really the go-to starter project here in our company, and with my own personal projects as well. It'd be a shame to let it run out of volunteers like this.
I'd very much be willing to contribute (though I've only tried helping people in issues before, as well as discuss sagas!) but I'm still learning, and there are much better people than I am. But if it's okay, I'd still like to join.

I can agree about the question-issues, @mxstbr but then we should tell people to go to https://stackoverflow.com/questions/tagged/react-boilerplate for help and questions and leave the issues for bugs and feature requests.
I myself thought it was okay to ask in the heart of the project(the issues) as long as it was then marked somehow as a question.
I just think we should agree upon an approach on how to handle the issue so all maintainers mark them the same way and we can get a better overview of them as well as making sure people who have already just asked for help is given a hand to move on and don’t feel kicked out.
I also think we - the maintainers - should have a talk about the open PRs and feature requests and create some tupe of roadmap so people can see we are moving forward.
In between the lines, i’m trying to ask: where should we have such kind of talk? I can see its possible in the github organization- but do we prefer to have it somewhere else?
I would like to get in contact with all the active maintainers and try and find a time where we can all have a talk. :)

Personally, I find if questions are allowed in an issue tracker, it spirals out of control and is really hard to stay on top of. Some questions are great, discussion-provoking, and other are basic questions that are either answered A. in docs, or B. not related to the boilerplate and should be asked elsewhere. It's a hard line to toe, because you want to foster community. It's not nice to tell people to look elsewhere for an answer, but having questions like that here prevent maintainers from actually tracking issues.
I usually look at questions asked in issues and see if they're bug-related, or just a potential feature worded as a question, or a discussion starter. If they're just 'questions', or not directly related to the repo project itself, that's what StackOverflow is for. But this is all just my two cents, from experience.
Last night, I closed over 100 issues here that were either 1. Inactive / old / solved / merged with a PR or 2. Questions that were either inactive, not related to rbp, or just basic questions.

@gretzky Really a great work.
I love RBP very much, I was recently helping to finish #1969, but it seems to be blocked, I am very happy to work with all your guys. Maybe this issue should closed? Should we open a new RFC repo for discussion undetermined issues?
BTW:
Any more volunteers?  @anuraag?

Thank you so much @gretzky, and I agree with your stance on questions. Almost all of them could live on stackoverflow, with maybe the exception of react-boilerplate internals/contributing help.

@blling any anyone else interested, I'd be glad to start a a Discord server or Slack channel to discuss things, so we don't have to bog up any channel in the repo.

@gretzky thats exactly what I was looking for.
I think it would be great for us to find some time to talk and all get on the same page. I have some ideas for our PRs and roadmap, but I would like to run them by you and the other maintainers before I start doing any changes. :)
Slack would be great from my point of view. :)

I mean, the reason I can't work on react-boilerplate much anymore is because I'm building a Slack competitor for exactly these kinds of communities... 🙈 Maybe we should use that? https://spectrum.chat
See here for some more background: https://mxstbr.blog/2017/10/spectrum/

Oh I now see that @justingreenberg has already kicked off a community on there! Come join and let's discuss about react-boilerplate maintenance: https://spectrum.chat/react-boilerplate

Haha @mxstbr 😂 that Homer Simpson DOH moment 😂
Lets continue on Spectrum 😃

@mxstbr, shameless request for Github oauth into spectrum 😄
I'm gonna close this in favor of moving the convo to Spectrum

shameless request for Github oauth into spectrum

Yeah I know, we've thought about it—this might actually be a good reason to enable it! /cc @brianlovin

I mean...it is technically built already :P
I'll open an issue for it, we can prioritize it during the next triage

@gretzky @mxstbr im not a super dev yet but would love to help! I did a setup for my site and I enabled Prettier-Stylelint and global scss variable loader, would like to help/make a PR with these features. Also working on adding prettier-eslint but after im back from vacation

@csantiago132 contributions are always welcome! Feel free to join our spectrum community as well- link is in the top comment

Hi, @mxstbr. I love RBP! I'd love to contribute my time in response questions and do some fixes. What should I do?


Pass GO_TAGS to tools container

Type of change
New feature
Description
With this change, you can now build
the tools container with pkcs11.

@Mergifyio backport release-2.3

@Mergifyio backport release-2.3

@Mergifyio backport release-1.4

Command backport release-1.4: failure

No backport have been created

Backport to branch release-1.4 failed
Git reported the following error:

fatal: couldn't find remote ref master

Oh that sucks, the change from master to main breaks Mergify for old PRs 😢


Preview Monthly Emissions Data

Definition of Ready

[ ] Does this meet the INVEST criteria?
[ ] Does this have a clearly defined user?
[ ] Does this have an estimate?
[ ] Does this have acceptance criteria?
[ ] Does this have sufficient context (wireframes, business rules, etc.)?
[ ] Is this traceable to a feature, epic, or PI?

User Story
As a CAMPD custom data download user I want to preview my dataset so that I can confirm it contains my desired data
Acceptance Criteria
Given
When
Then
Context
(User journeys, design mockups, architectural diagrams, business rules, data element definitions)
Testing
Test Case:
Tester:
Definition of Done

[ ] Have all Acceptance Criteria been agreed to and validated by the scrum team?
[ ] Has the code been unit tested and peer reviewed?
[ ] Have the functional tests been executed?
[ ] Have all defects been reviewed and dispositioned, resolved, or deferred?
[ ] Has the user story been accepted by the Product Owner?
[ ] Is the user story ready to be deployed to the test/staging environments?

This ticket is no longer needed. The preview functionality will be built at the same time as the filter criteria


Implement BumpVer

In GitLab by @arisilon on May 19, 2023, 19:35
There's a sample implementation at https://realpython.com/pypi-publish-python-package/

In GitLab by @arisilon on May 22, 2023, 21:49
mentioned in commit e9e3381566c5a03733a8b21c0df51fec1750a106

In GitLab by @arisilon on May 30, 2023, 16:34
mentioned in commit 16f90cc441eeab6d83e3b6719c5ee253fd09af58


Keybase Pages prototype

This PR adds a prototype for Keybase Pages. It's now hardcoded to work with the staging Let's Encrypt environment, meaning the certs are not trusted by browsers, but we get higher rate limits.
To test it, you need configure two things on your domain name:

An A record that points to the EC2 public IP I'm running this on. For example: kbp-test2.song A 1m <IP_ADDRESS>
A TXT record to configure how content should be served. The TLF should be readable by kbpbot. For example: kbp-test2.song TXT 1m "kbp=/keybase/public/songgao/kbp-test2"

I vendored zap in for logging. It's a pretty nice alternative to logrus with way better performance and nicer interface, so I thought we could try it with Keybase Pages. But let me know if any of you have a strong opinion against it. The development logger looks like this:
2017-12-09T00:37:36.976Z        INFO    libpages/root.go:66     root.MakeFS     {"type": "kbfs", "tlf_type": "public", "tlf": "songgao", "path": "kbp-test2"}

while the prod logger will be fully json like on our server side.

I'm realizing this won't work for multi-instance deployments, as when ACME client (kbp) requests certificate, ACME server (Let's Encrypt) need to verify domain ownership, and there's no way to have the ELB route that traffic to the original instance that initiated the cert request.
I think we'll need to either:

aggregate HTTP-hosted well-known assets used by ACME client between all instances, or
deterministically delegate cert requesting and management to specific instances based on domain name, and proxy HTTP requests to the one that's responsible for the domain. HTTPS can still be served from any instance, and they don't have a cert, they'd just request it from the cert-owning instance.

I'm leaning towards second approach as we can use the same infrastructure for cert distribution and requests. Of course we always have the option to use ACM in our deployment, but keep the single-instance setup for "community" version. But that makes it hard for other people to deploy larger-scale kbp.
Let me know what you guys think!

Oh I was being inaccurate about autocert using HTTP (:80) for domain verification. It actually uses TLS SNI for verification. In other words, this only listens on :443. And that means the two approaches I suggested above are not applicable to autocert per se.


Set threshold value and color to the line graph and bar graph

The above example is what I want to achieve.
This was done using normal linear gradient class. But instead I want to be able to set the threshold value and color for a line graph

also would be nice if the same could be set for bar graph

You need to modify LinearGradient.stops to achieve your result.


Update tool improvements

Purpose

Fix done in the PR

Include update message only for build command
Remove self update command
Change dist list commands --remote flag to --local
Separate pull and dist pull help content

Codecov Report

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

@@            Coverage Diff             @@
##           master   #18704      +/-   ##
==========================================
+ Coverage   15.04%   15.53%   +0.49%
==========================================
  Files          48       47       -1
  Lines        1263     1223      -40
  Branches      199      185      -14
==========================================
  Hits          190      190
+ Misses       1059     1019      -40
  Partials       14       14

Impacted Files
Coverage Δ

...s/vscode/src/project-tree-view/project-overview.ts
0% <0%> (ø)
:arrow_up:

...ugins/vscode/src/project-tree-view/project-tree.ts

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 2d69fda...d759fba. Read the comment docs.


Improve readme installation for Windows

I struggle a bit for Windows installation, turns out I require higher permissions when installing a pip package since I've my Python on C:\ since not all of us are use to that, perhaps could be good to mention it.

Thanks for the PR!


fix: update crn and tags

Description
<!--- Replace this text with a summary of the changes in this PR. Include why the changes are needed and context about the changes. List required dependencies. If there is a Git issue for the change, please link to it. --->
https://github.com/terraform-ibm-modules/terraform-ibm-icd-elasticsearch/issues/127
Release required?

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

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

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

For mergers

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

/run pipeline

:tada: This PR is included in version 1.9.2 :tada:
The release is available on:

GitHub release
v1.9.2

Your semantic-release bot :package::rocket:


Plugin not compatible with IJ 2023.1 EAP

Would it be possible to publish the plugin compatible with
IntelliJ IDEA 2023.1 EAP (Ultimate Edition)
Build #IU-231.5920.14, built on January 27, 2023

?

v3.3.1 is listed in the changelog https://github.com/JetBrains/js-graphql-intellij-plugin/blob/master/CHANGELOG.md#331---2022-11-23
but for some reason it was never published to the marketplace https://plugins.jetbrains.com/plugin/8097-graphql

It should be available in the marketplace now 🎉.


[BUG] Nothing works in this course

🐞 Describe the bug:
Tests fail
UI Mode does not open
👻 To Reproduce:
Follow the setup steps from the course (there are lots of gaps. test the course on several newbies before posting it)
🌵 Expected behavior:
Tests run and pass
UI Mode opens
📸 Screenshots/GIFs/Videos:
....npx playwright test --ui
Error: Timed out 5000ms waiting for expect(locator).toHaveURL(expected)
Locator: locator(':root')
Expected pattern: /.*profile/
Received string:  "https://demoqa.com/login"
Call log:

locator._expect with timeout 5000ms
waiting for locator(':root')
locator resolved to …
unexpected value "https://demoqa.com/login"
locator resolved to …
unexpected value "https://demoqa.com/login"
locator resolved to …
unexpected value "https://demoqa.com/login"
locator resolved to …
unexpected value "https://demoqa.com/login"
locator resolved to …
unexpected value "https://demoqa.com/login"
locator resolved to …
unexpected value "https://demoqa.com/login"
locator resolved to …
unexpected value "https://demoqa.com/login"
locator resolved to …
unexpected value "https://demoqa.com/login"
locator resolved to …
unexpected value "https://demoqa.com/login"

at tests\ui\pages\login-page.ts:34
32 |
33 |   async checkLoggedIn() {

34 |     await expect(this.page).toHaveURL(/.*profile/);
|                             ^
35 |     await expect(this.page).toHaveTitle(/DEMOQA/);
36 |   }
37 |

at LoginPage.checkLoggedIn (C:\.......\tests\ui\pages\login-page.ts:34:29)
at globalSetup (C:\.......\tests\setup\global-setup.ts:15:19)

💈 Dependencies' Version (please complete the following information):

OS: Windows
Browser course default
Playwright Version 1.39
npm Version 10.2.0

🛝 Additional context:
I understand it's a free course but it's expected to teach student to use playwright, not to debug your course code.

Hi @CIALdev,
I understand your frustration and I'm sorry you feel this way. I prepared this training with only good intentions, and I did test with many people (in fact more than 500 people already completed it and it went well) but definitely it's not possible to map every single student's background.
I agree when you say "it's expected to teach student to use playwright, not to debug your course code" and I'll try to make the commands more explicit so you and other students don't have the feeling you need to debug the code to make it run successfully, thank you for the feedback. This is an advanced course and some background is necessary too, it's a 50%-50% work. Also, I always reply to the questions and try to point people in the right direction.
As I explained in your other comment the tests are not meant to run altogether, they are examples for each chapter tackled in the course.
To run the UI Mode, try the following steps:

Rename the playwright.config.ts file to playwright-full.config.ts
Rename the playwright-standard.config.ts file to playwright.config.ts
Go to your terminal and type npx playwright test --ui
Run the tests independently (1 spec at a time)
NOTE: The tests inside specs-auth will need the content inside the playwright-auth.config and as I mentioned in one of the chapters of the course, the application doesn't support one of the scenarios. I implemented it only to show you how to do it, so you can replicate it in your real application.

Let me know if you need more support, I'm happy to help.

One more note: In the readme file, I mentioned the versions the training was recorded. It's a good practice to use the same versions listed there, I cannot guarantee that the code will work with newer versions since breaking changes can be released at any moment and this training will not be upgraded.


Cache bust of partial URLs not working

I currently have the following task defined:
    cacheBust: {
        build: {
            options: {
                baseDir: 'build',
                assets: ['**'],
                queryString: true
            },
            files: [
                {expand: true, src: ['build/**/*'], filter: 'isFile'}
            ]
        }
    }

I also have the following file structure.
build
`-- desktop
    `-- css
        |-- estilos.css
        `-- images
            `-- sprite.png

on estilos.css, I have the following line of CSS: .sprite{background:url("images/sprite.png");}. To my understanding, this should be changed by the library to .sprite{background:url("images/sprite.png?SOMEQUERYSTRING");}but at the moment that is not working.
Is there anything wrong in my config, or it should be working but it isn't?
I have checked and in cachebust.json I can find that the sprite is indeed read, so I guess it's something to do with the fact that it's in a nested directory?

Have a read through the comments in #180 and #183

Facing the same issue. Went through #180 and #183 but still it doesn't help.

Ok i solved it. I was missing the baseDir parameter due to which the paths in my index.html did not change.


fix: use chainName from useStarknetWallet

Description of the Changes
Please add a detailed description of the change, whether it's an enhancement or a bugfix.
If the PR is related to an open issue please link to it.
Solves #INSERT_MONDAY_ID_HERE

Checklist

[ ] Manually tests of the main Application flows are done and passed.
[ ] New unit / functional tests have been added (whenever applicable).
[ ] Docs have been updated (whenever relevant).
[ ] PR title is follow the Conventional Commits convention: <type>[optional scope]: <description>, e.g: fix: prevent racing of requests

:tada: This PR is included in version 1.0.0-dev.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Reimplement Kolmogorov Smirnov query logic with sqlalchemy's Language Expression API

See linked issues for context.
Importantly, I have high hopes that the isolation and explicit testing of _cross_cdf_selection will now be useful for other kinds of Constraints, e.g. https://github.com/Quantco/datajudge/issues/45.

I find the SQLAlchemy code incredibly difficult to follow. Not saying that it is because you are writing complicated SQLAlchemy. Maybe it's just more difficult for me (with little SQLAlchemy experience) to follow than to follow SQL.

I definitely understand where you're coming from. A couple of hopefully related comments from my side:

Personally, I see multiple upsides of using the language expression API.

Firstly, it conveniently enables the use of abstractions such as ref.get_selection(engine). IIrc not being able to use this abstraction caused a lot of the development effort in the raw-sql version of this query logic. Moreover, it caused a bug in relation to Conditions.
Secondly, some raw sql queries might actually run just fine against multiple dialects. Yet, this is definitely not the case for all of our queries. When it is not possible, the language expression API actually allows us to 'write once, run everywhere™'. I'm not sure whether having a patchwork of raw sql and language expression api would be desirable in the long run.
Thirdly, I find it easier to share logic between different queries than with raw sql queries - see comment about reusing _cross_cdf_selection for another hypothesis test.

As you gently allude to, I think I have indeed seen a development on my end when it comes to reading language expression code. I believe to find it easier to read now than two years ago.

I still don't find it easy to read.

To me, this very example seems to be on one side of the query logic complexity spectrum, at least in how far datajudge is concerned.

Personally - even though I admire the rigid structure and invaluable comments introduced by @YYYasin19 - I didn't find the raw sql code easy to follow either. It took me some debugging and reimplementing to understand some of the intricacies.

Maybe it would help people like me if we had a simplified version of the query in SQL somewhere in a docstring to help get an overview of the code.

I'm definitely open to the idea.
I made a point out of mostly preserving @YYYasin19's structure of iterative steps - in contrast to recursion - to allow the curious developer to create, read and run these intermediate steps. What I often do is to set breakpoints and run str(intermediate_selection) or even engine.connect().execute(intermediate_selection) via pdb while executing the integration tests. Moreover, I hoped to have made the query building a little more clear with this[0] example as well as the dedicated test case[1].
Nevertheless, if you have a concrete suggestion I'm happy to follow your lead. :)
[0] https://github.com/Quantco/datajudge/pull/44/files#diff-74c4ccf9b9cba732c4562df6e1e05a5ecdee4e9c04f38276b54e85f850155660R943-R945
[1] https://github.com/Quantco/datajudge/pull/44/files#diff-294af7c1d98bcac87ae111bebc4c13a1b1d8155cce13ea48446397e950f9db32R7-R28

Maybe it would help people like me if we had a simplified version of the query in SQL somewhere in a docstring to help get an overview of the code.

I'm definitely open to the idea.

Why not put a link to the full version in Yasin's repository containing the SQL version?

Very nice (re-)implementation in the expression language API!
I agree with the fact that it is hard to parse without having experience with the API. I think we can split the query up as much as possible here, since the final compilation and optimization will still be done by the database engine(s), so our goal should be readability and maintainability -- though I don't see any obvious wins left here.


playing prop is not working in Safari

This is not working for me in Safari. Chrome starts video immediately. Safari not.
<ReactPlayer playing={true} url={videos} />

What is videos in your example?

import video_mp4_1280 from './1280.mp4';
import video_mp4_640 from './640.mp4';
import video_webm_1280 from './1280.webm';
import video_webm_640 from './640.webm';

const videos = [
	{
		src: video_webm_1280,
		type: 'video/webm',
		media: '(min-device-pixel-ratio:2), (-webkit-min-device-pixel-ratio:2)',
	},
	{
		src: video_webm_640,
		type: 'video/webm',
	},
	{
		src: video_mp4_1280,
		type: 'video/mp4',
		media: '(min-device-pixel-ratio:2), (-webkit-min-device-pixel-ratio:2)',
	},
	{
		src: video_mp4_640,
		type: 'video/mp4',
	},
];

This produces:
<video preload="auto" style="width: 100%; height: 100%;">
	<source src="/static/media/1280.9e882287.webm" type="video/webm" media="(min-device-pixel-ratio:2), (-webkit-min-device-pixel-ratio:2)">
	<source src="/static/media/640.a06678e3.webm" type="video/webm">
	<source src="/static/media/1280.23e52731.mp4" type="video/mp4" media="(min-device-pixel-ratio:2), (-webkit-min-device-pixel-ratio:2)">
	<source src="/static/media/640.c06decc4.mp4" type="video/mp4">
</video>

Video is displayed in Safari, but is not playing from the very beginning. If I add controls and hit play button it starts playing. But I need it to play on load. In Chrome, Firefox it plays. But not in Safari.

Oh! The solution is to add autoPlay prop to the component:
<ReactPlayer autoPlay playing={true} url={videos} />

Now everything works. Would be great to add this information in readme.

Oh! The solution is to add autoPlay prop to the component:
<ReactPlayer autoPlay playing={true} url={videos} />

I'm really confused as to why this has fixed it. Adding autoPlay to ReactPlayer will just add that attribute to the wrapper div, not the <video> itself. Unless Safari is also looking for autoPlay attributes on any parent element of a given <video>? I can't reproduce this issue myself.

I believe Safari stopped autoplaying videos that are not muted by default in Safari 11. If you add the muted prop to the ReactPlayer component, the video will start playing automatically.

I have the same problem with audio player. It doesn't play songs, if I use mute it does play, what would be a way to unmute the song immediately after it starts playing?


Improve Usage of disks.disks()

Since we're catching OSError inside of disks.disks() we shouldn't need the bare try/except clause anymore.  This PR also adds the tests for disks.disks() and provides a as_dict keyword so we can skip the extra for loop in service.py

@guidow, PTAL

Looks good to me.


Transition to jethro

@agherzan @floion

Reviewed 13 of 13 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io

Reviewed 13 of 13 files at r1.
Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from the review on Reviewable.io


Smiley text needs smooth draw

The text is not drawn smoothly.

It has been added in the new code. Have to release a major version update


Add ManagedClusterLabels to hub template context

The labels on the ManagedCluster where the policy is being propagated are now available for use in hub templates. And when the labels on the ManagedCluster change, the template will automatically be updated.
Refs:

https://issues.redhat.com/browse/ACM-4168

/hold

LGTM! There's a conflict to resolve here, though.

/unhold
Now ready for real review!


Does this plugin take some of the earnings from developer?

Is this plugin free or deducts some earning from developers for showing ads?

Yes, as he states in his readme:

You can also support this project by sharing 2% Ad traffic (it's not mandatory: if you are unwilling to share, please fork and remove the donation code).

You have to fork and to remove the donation code within the source.

Any idea where i can find donation code? Couldn't find anything, though i would love to share a beer with developer, but need to see how donation is working for him?

I think when you put your plugin calling code inside config.xml and you wrote source="npm". So whenever you build the phonegap, it automatically fetch the package of plugin from NPM server. So we can not edit or remove the code. This is my opinion only, but who knows the truth, may be plugin author.

@swapnilraja1212 if what you described above is true, then this plugin does smell fishy. Isn't it? @NightkingCH Did you get hold of how the donation code looks?

@DonZheng I didn't end up using admob. But if you have a look at https://github.com/appfeel/admob-google-cordova/blob/master/src/android/res/xml/admob.xml or search for the ids you see where they are used. https://github.com/appfeel/admob-google-cordova/search?q=rid. Within CDVAdMobAds.m you see that the ids are read out and it swaps randomly between the one you provided over the api or the one within the corresponding device configuration files. It seems to be the same mechanic for both iOS and Android.

@NightkingCH Thanks for your expertise, Thomas. Much appreciated.


What is the purpose of the change
fix #230
Related issues/PRs
Related issues: #230
Brief change log
Checklist

[x] I have read the Contributing Guidelines on pull requests.
[x] I have explained the need for this PR and the problem it solves
[x] I have explained the changes or the new features added to this PR
[x] I have added tests corresponding to this change
[x] I have updated the documentation to reflect this change
[x] I have verified that this change is backward compatible
[x] If this is a code change: I have written unit tests to fully verify the new behavior.

LGTM


Expose more stack level variables

some suggestions..

secret_manager_service_plan
existing_secrets_manager_crn
enable_platform_logs_metrics

Maybe others?

secret_manager_service_plan is now integrated in.
enable_platform is enabled by default.
I suggest having existing_secrets_manager_crn out until we get feedback.
We shouldn't put more features in until we get usage.

:tada: This issue has been resolved in version 0.1.0 :tada:
The release is available on:

GitHub release
v0.1.0

Your semantic-release bot :package::rocket:


Fix #161 - Get configuration for bolt protocol from URL

Did you check it with lorenzo? He had some concerns lately about distinguishing parameters, it might be that we have to prefix them with something like config:

It’s ok. The issue was related to the usage of comma as parameter separator and have the same character as value separator for list parameters, but we deprecated it in favour of the more compliant with URI syntax &.
Nevertheless, if we prefer to group parameters with the same meaning then prepending config: would be good. I’m just wondering if it’d not be to noisy for the user to add it because we have plenty of these config parameter.

Ok cool the let's keep it.


Right-to-left script not showing in TextInput widget

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
Thanks to #1830, regular Text widgets can handle complex scripts, including left-to-right (LTR), right-to-left (RTL), and mixed LTR/RTL. But this is only partially true for the TextInput widget, such that complex scripts will be displayed properly only if the content of the text input starts with an LTR (alphabet) character. In other words, the content of text input is only displayed when the content should be aligned LTR.
The screen capture below demonstrates the issue using the Todos example of the library, but this issue is reproducible with any TextInput instance. The video covers LTR, RTL, LTR->RTL, and RTL->LTR.
https://github.com/iced-rs/iced/assets/39179450/899d857a-61bb-43d7-ab0c-63dc7941c82c
What is the expected behavior?
Ultimately, if the user input starts with an RTL (alphabet) character, the entire content should be displayed RTL and be right-aligned. However, since TextInput does not yet have horizontal text alignment support, a first step would be to just make the text show up, even if left-aligned.
I don't have enough knowledge of text rendering or the internals of this library to pinpoint where the issue stems from and how to fix it. But I did try a couple of basic modifications to this function call:

Changed the hard-coded Alignment::Left to Alignment::Right
Changed bounds.x to a value expected by Alignment::Right

I also tried rendering with different values of offset with renderer.with_translation(...). None of my attempts so far has made the missing text appear.
I would be happy to look into fixing the issue if someone can point me to the potential location of the issue in the codebase.
Version
master
Operative System
macOS
Do you have any log output?
No response

@hecrj @mtkennerly I have dug deeper into this since posting the issue and identified the root cause. I think it is upstream in glyphon. FWIW, here's what I have found so far.
Original Issue
Cause
This happens because glyphon (I'm assuming that's where the text rendering happens) renders all right-to-left text as right-aligned, regardless of the horizontal_alignment value provided. That is the text is rendered from the rightmost end of the bounds (bounds.x + bounds.width) towards the left. Since TextInput has bounds.width = infinity, when you try to input RTL text into a TextInput, it tries to render the text at x = infinity which obviously will never show up on screen. What is different now compared to when I opened the issue is that performing this action simply leads to a crash in glyphon of "attempt to add with overflow" when trying to do math with infinity here.
Naive solution
Setting the bounds.width value here to f32::max(text_width, text_bounds.width) makes TextInput work with LTR scripts without problem (so far as I can tell), and RTL scripts display correctly too, although making the cursor work properly in this case requires some additional tweaking. I'm not making a PR on this because I think the issue needs to be handled on the rendering side, but I might be wrong.
https://github.com/iced-rs/iced/assets/39179450/ba417ae5-e173-4c25-bebf-87cee277718d
NOTE: the clipping at the end happens because renderer.measure_width returns a width of zero for RTL text having again to do with bounds.x = infinity.
A more fundamental issue
Cause
This is also causing an even more serious issue with the regular Text widget, because the bounds.x value of text is updated here assuming the renderer will respect the horizontal_alignment paramter. But because that doesn't happen for RTL text, the text is rendered completely out of bounds if any alignment other than Horizontal::Left is provided. As you can see below, RTL left-aligned acts like LTR right-aligned, and the other RTLs are out of the specified widget width, because their bounds.x is being moved to the right.

Naive solution
A downstream solution for this would be to update the bounds parameter differently for different cases of alignment when the text is RTL, for example:
bounds.width = text_width;
let x = match horizontal_alignment {
    alignment::Horizontal::Left => bounds.x,
    alignment::Horizontal::Center => bounds.center_x() - text_width / 2.0,
    alignment::Horizontal::Right => bounds.x + bounds.width - text_width,
};

Since I didn't find a function within iced or glyphon that returns the direction of a language, I couldn't test it out (without adding an explicit direction parameter to text widgets). The Horizontal::Left case works for both LTR and RTL however:

I'm not making a PR on this either because of the same reason as above: I think it needs a fix upstream.


71 feat db seeding

Implements/Fixes(DELETE THE WRONG ONE) #
If your PR is not WIP, Please check if your PR fulfills these requirements

[ ] The PR title follows the guidelines

Which part of the project does this PR belongs to ?
What is the current behavior ?
Does this PR introduce a breaking change ?
Other information

I created 2 user, 2 hashtag and 2 posts, basic stuff


New intent classifier for almost exactly match from training examples

Proposed changes:
Here I propose a new intent classifier: exact_intent_classifier.
exact_intent_classifier try to solve an embarrassing situation: some time model performance is so bad even you give an input text that exists in training examples but the model still give the wrong answer!
exact_intent_classifier remember the training examples almost exactly, when those example text come in again, exact_intent_classifier will output the right answer and confidence is 1.
exact_intent_classifier also have an config option: trailing_punctuation_marks that make classifier more powerful. classifier will make sure that without or with one of trailing_punctuation_marks will treat as same input. Such as trailing_punctuation_marks set to "?" means "where are you" and "where are you?" will treat as same thing.
exact_intent_classifier is designed to work with other classifiers, so it can always boost the performance more or less.
Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog

Although I agree this is a neat component and has its use cases, I am afraid we won't integrate it as
it delivers a false sense of predictive quality, e.g. if you test the bot with the utterances from your training it works - if you use slightly different examples it doesn't.


The release status for application insights event logs for custom policy doesn't match with the actual document

[Enter feedback here]

The section https://learn.microsoft.com/en-us/azure/active-directory-b2c/custom-policy-developer-notes#developer-interface is telling that referred articles are in Preview , but the actual pages do not mentioned it.
Application  Insights event logs | Preview | Used to monitor user flows in production.
-- | -- | --
 May I confirm what is release status of Track user behavior by using Application Insights - Azure AD B2C | Microsoft Learn? Thank you.

---
#### Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: a067ceb2-fe69-6b56-eafa-ffb7ebf1968e
Version Independent ID: 6fd66d79-08fa-b5ea-daf0-d92073269b64
Content: Developer notes for user flows and custom policies - Azure AD B2C
Content Source: articles/active-directory-b2c/custom-policy-developer-notes.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@jche0313
Thanks for your feedback! We will investigate and update as appropriate.

@jche0313
I'm going to assign this to the document author so they can take a look at it accordingly
@kengaderdus
Can you please check and add your comments on this doc update request as applicable.

@jche0313
Thanks for your feedback and patience.
It's in public preview. We'll update our docs #please-close


Project Setup

Hello,
Sorry for the silly question, but after cloning the project I'm getting error.
The type or namespace name 'Amazon' could not be found (are you missing a using directive or an assembly reference?)
I'm using Unity 2018.4.23f, Do I have import AWS SDK packages. Also, I'm trying to build for Android. Gamelift support Android builds?

Hello Rosank,
You should execute build.bat in the build folder to download the SDK, build it and put it in the Plugins folder. All should be good at that point. If you already did this, can you supply the output from this batch file, so that I can see what went wrong. Thank you!!!

Thank you It worked. I'm closing the issue


host: cross executable object serialization

Introduce a mechanism that lets you define an object that
holds the capacity to serialize itself in order to be reconstructed on
another python executable where its class is not defined.

While this is certainly technically very clever, it feels like we are abstracting too early. I would stick to the simple serialized dicts we currently have, and only when that becomes problematic try to generalize it.
Even if we do want to add some abstraction though, I'm not sure this concept is the right approach, for a few reasons:

This ties our wire protocol to implementation details of python. This is hopefully stable across python versions, but it would not work if we want some executables implemented in other languages down the line.
This requires the communicating processes to be in the same filesystem namespace and have access to each other's source files, that's not an assumption I think we should be making, especially as much of our communication happens across namespace boundaries.
It is not idiomatic python (afaik). Magically appearing classes defined in other executables would be surprising for someone used to writing python. I haven't tried, but I'm also suspicious if this would work well with IDEs.

Thanks @teg for this review. I understand your points. Ahhhh, I was so happy to have this for #961 it would have made things very nicely organized.
Well, I will come up with something different then. I'll manage with dicts only.