Import error with w3lib.encoding (from requests-html)

This may be related to #443 (?) but given how far the compilation process is progressing I suspect #443 has been resolved and can be closed?
I am using the requests-html package to scrape data from other pages (with JS content) to be inserted into a section of my page.
Test code is:
from requests_html import AsyncHTMLSession

asession = AsyncHTMLSession()

async def get_page1():
    r = await asession.get('https://python.org/')
    await r.html.arender()
    return r

async def get_page2():
    r = await asession.get('https://reddit.com/')
    await r.html.arender()
    return r

pages = asession.run(get_page1, get_page2)

and gives the following output/error:
(webdev) C:\Users\ustauss\Anaconda3Projects\ts_test>transcrypt -a -b -m -v rqhtstest.py

Transcrypt (TM) Python to JavaScript Small Sane Subset Transpiler Version 3.7.16
Copyright (C) Geatec Engineering. License: Apache 2.0

Parsing module: c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/transcrypt/modules/org/transcrypt/__runtime__.py
Generating code for module: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/org.transcrypt.__runtime__.js
Saving source map in: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/org.transcrypt.__runtime__.map
Saving target code in: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/org.transcrypt.__runtime__.js
Saving minified target code in: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/org.transcrypt.__runtime__.js
Saving multi-level sourcemap in: {}
Parsing module: C:/Users/ustauss/Anaconda3Projects/ts_test/rqhtstest.py
Generating code for module: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/rqhtstest.js
Parsing module: c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/requests_html.py
Generating code for module: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/requests_html.js
Parsing module: c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/w3lib/encoding.py
Generating code for module: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/w3lib.encoding.js
Parsing module: c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/transcrypt/modules/sys/__init__.py
Generating code for module: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/sys.js
Saving source map in: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/sys.map
Saving target code in: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/sys.js
Saving minified target code in: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/sys.js
Saving multi-level sourcemap in: {}
Parsing module: c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/transcrypt/modules/re/__init__.py
Generating code for module: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/re.js
Parsing module: c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/transcrypt/modules/re/translate.py
Generating code for module: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/re.translate.js
Saving source map in: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/re.translate.map
Saving target code in: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/re.translate.js
Saving minified target code in: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/re.translate.js
Saving multi-level sourcemap in: {}
Saving source map in: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/re.map
Saving target code in: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/re.js
Saving minified target code in: C:/Users/ustauss/Anaconda3Projects/ts_test/__target__/re.js
Saving multi-level sourcemap in: {}

Error while compiling (offending file last):
        File 'C:/Users/ustauss/Anaconda3Projects/ts_test/rqhtstest.py', line 1, at import of:
        File 'c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/requests_html.py', line 22, at import of:
        File 'w3lib.encoding', line 5, namely:

        Import error, can't find any of:
                C:/Users/ustauss/Anaconda3Projects/ts_test/re/translate/translate.py
                C:/Users/ustauss/Anaconda3Projects/ts_test/re/translate/translate.js
                c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/transcrypt/modules/re/translate/translate.py
                c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/transcrypt/modules/re/translate/translate.js
                C:/Users/ustauss/Anaconda3/envs/webdev/Scripts/transcrypt.exe/re/translate/translate.py
                C:/Users/ustauss/Anaconda3/envs/webdev/Scripts/transcrypt.exe/re/translate/translate.js
                c:/users/ustauss/anaconda3/envs/webdev/re/translate/translate.py
                c:/users/ustauss/anaconda3/envs/webdev/re/translate/translate.js
                c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/re/translate/translate.py
                c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/re/translate/translate.js
                C:/Users/ustauss/Anaconda3Projects/ts_test/re/translate.py
                C:/Users/ustauss/Anaconda3Projects/ts_test/re/translate.js
                C:/Users/ustauss/Anaconda3Projects/ts_test/codecs.py
                C:/Users/ustauss/Anaconda3Projects/ts_test/codecs.js
                c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/transcrypt/modules/codecs.py
                c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/transcrypt/modules/codecs.js
                C:/Users/ustauss/Anaconda3/envs/webdev/Scripts/transcrypt.exe/codecs.py
                C:/Users/ustauss/Anaconda3/envs/webdev/Scripts/transcrypt.exe/codecs.js
                c:/users/ustauss/anaconda3/envs/webdev/codecs.py
                c:/users/ustauss/anaconda3/envs/webdev/codecs.js
                c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/codecs.py
                c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/codecs.js

Aborted

The __target__ subdirectory contains the following files:
org.transcrypt.__runtime__.js
org.transcrypt.__runtime__.map
org.transcrypt.__runtime__.pretty.map
org.transcrypt.__runtime__.py
re.js
re.map
re.pretty.map
re.py
re.translate.js
re.translate.map
re.translate.pretty.map
re.translate.py
sys.js
sys.map
sys.pretty.map
sys.py

Is Transcypt forgetting somewhere that it put those files (except codecs.*) into __target__?
What is going on?
Happy to provide any of the files in __target__ if necessary.

Transcrypt doesn't support 3rd party packages and only part of the standard library modules.
Generaly, compatibility goes like this:

Syntax and built-ins works (there are some edge cases).
Specific features, such as kwargs and magic methods, may need pre-compiler switches.
Standard library modules support is limited.
3rd party modules are not supported unless they conform with the previous restriction, using 3rd
party javascript library is prefered.

To see a list of supported standard library features see section 4 at https://transcrypt.org/docs/html/index.html.

In this specific case encoding.py from w3lib imports codecs, which is not supported
File 'w3lib.encoding', line 5, namely:

        Import error, can't find any of:
                ...
                C:/Users/ustauss/Anaconda3Projects/ts_test/codecs.py
                C:/Users/ustauss/Anaconda3Projects/ts_test/codecs.js
                ...

Not sure what the deal is with that mention of translate.py, maybe it's been imported in a special way? But in any case, the codecs.py import is a problem.

translate comes from transcrypt's own re module implementation.
codecs.py is part of the standard library.
So I tried the following:
tstst.py:
# import re, codecs, encodings
import re
import codecs
# import encodings

re seems to compile fine (with only re imported there is a tstest.js). But with the test as shown the error is now:
        Import error, can't find any of:
                C:/Users/ustauss/Anaconda3Projects/ts_test/codecs.py
                C:/Users/ustauss/Anaconda3Projects/ts_test/codecs.js
                c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/transcrypt/modules/codecs.py
                c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/transcrypt/modules/codecs.js
                C:/Users/ustauss/Anaconda3/envs/webdev/Scripts/transcrypt.exe/codecs.py
                C:/Users/ustauss/Anaconda3/envs/webdev/Scripts/transcrypt.exe/codecs.js
                c:/users/ustauss/anaconda3/envs/webdev/codecs.py
                c:/users/ustauss/anaconda3/envs/webdev/codecs.js
                c:/users/ustauss/anaconda3/envs/webdev/lib/site-packages/codecs.py

(The same respectively with only encodings being imported. With both only the search for last one is listed.)
Both are actually in c:/users/ustauss/anaconda3/envs/webdev/lib/ which is not on the search path - because line 47, transcript/__main__.py removes it:
lowerSkipExtensions = ('.zip', '/dlls', '/lib', '/python37')
(What is the rationale for excluding /lib?)
Deleting '/lib', obviously helps but now I'm stuck with:
Error while compiling (offending file last):
        File 'C:/Users/ustauss/Anaconda3Projects/ts_test/tstest.py', line 9, at import of:
        File 'codecs', line 44, namely:

        Can't import module 'codecs'

codecs.py from line 10 to the offending line 44:
...
import builtins
import sys

### Registry and builtin stateless codec functions

try:
    from _codecs import *
except ImportError as why:
    raise SystemError('Failed to load the builtin codecs: %s' % why)

__all__ = ["register", "lookup", "open", "EncodedFile", "BOM", "BOM_BE",
           "BOM_LE", "BOM32_BE", "BOM32_LE", "BOM64_BE", "BOM64_LE",
           "BOM_UTF8", "BOM_UTF16", "BOM_UTF16_LE", "BOM_UTF16_BE",
           "BOM_UTF32", "BOM_UTF32_LE", "BOM_UTF32_BE",
           "CodecInfo", "Codec", "IncrementalEncoder", "IncrementalDecoder",
           "StreamReader", "StreamWriter",
           "StreamReaderWriter", "StreamRecoder",
           "getencoder", "getdecoder", "getincrementalencoder",
           "getincrementaldecoder", "getreader", "getwriter",
           "encode", "decode", "iterencode", "iterdecode",
           "strict_errors", "ignore_errors", "replace_errors",
           "xmlcharrefreplace_errors",
           "backslashreplace_errors", "namereplace_errors",
           "register_error", "lookup_error"]

### Constants

#
# Byte Order Mark (BOM = ZERO WIDTH NO-BREAK SPACE = U+FEFF)
# and its possible byte string values
# for UTF8/UTF16/UTF32 output and little/big endian machines
#

# UTF-8
BOM_UTF8 = b'\xef\xbb\xbf'

…
Any ideas why this would cause an error?

codecs.py is part of the standard library

And is not supported, so there's a good chance it wouldn't pass compilation.

(What is the rationale for excluding /lib?)

My guess would be that since they are not supported might as well exclude them, and in my case trying to add them caused a clash between the std re module and the transcrypt implemented one.
I tried including BOM_UTF8 = b'\xef\xbb\xbf' in a .py and compiling it with transcrypt caused the error you have. test_byte = b'00000001' and test_string = '\xef\xbb\xbf' works fine, so maybe an encoding problem with hex numbers in a byte? Maybe someone working on the compiler could help with that.

Did a few more tests:
any hex bytes \x80 and greater fail with the same error, \7f and less is ok. Looks like the compiler is getting a range check wrong somewhere but haven't been able to find that yet.

Hi @ustauss
/lib is excluded indeed because of nameclashes, and because what's there can't be used in the browser for the larger part since machine language (compiled C++) code isn't supported in the browser. Webassembly is a workaround but results in overly large pageload times (typically minutes).
The decoding issue will be looked into, thanks for the detective work done there...
About activity of TS development. Sometimes some very proficient developers get involved, even over a longer time, which gives great progress.
But other times they're all busy and development slows down until they're available once more, or until new persons participate.
So development speed is not constant, but I try to keep up a minimum pace. A regular, somewhat formalized organisation could make development speed more predictable. It's on my mind, but I have not yet found a practical solution. Moving to California would help, but I am too deeply rooted in the Netherlands for that...

Thanks for the reply @JdeH.
The joys of volunteer open source.
I've been trying to add some very useful screen scraped content into a volunteer web page that I've been running for over a decade. Transcrypt would be absolutely perfect because with requests-html it would only be a few more lines of Python and  done. Brython etc is just not quite as nice in this case and I'd probably run into similar issues(?).
Doing it in JavaScript now, which I'm only learning for this, it's way more effort. Maybe there are good JS packages/libraries that could make it similarly simple and easy but I just don't have the broader knowledge yet.
Transcrypt was worth a try though...


Info button on webUI not working

Expected Behavior
Bot details is shown when pressing INFO button in WebUI
Actual Behavior
if webpage have just been reloaded only a small box with the word "SUBMENU" is shown, if any other button have been pressed (ITEMS, POKEMON, POKEDEX) then its the last shown box that will be reopened when pressing the INFO button
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": false,
"tasks_only": false

},
"tasks": [
{
    "type": "TelegramTask",
    "config": {
      "enabled": false,
      "master": null,
      "alert_catch": ["all"]
    }
  },

{
"type": "TransferPokemon",
"config": {
"min_free_slot": 5,
"transfer_wait_min": 1,
"transfer_wait_max": 4
}
},
{
"type": "UpdateLiveStats",
"config": {
"enabled": false,
"min_interval": 10,
"stats": ["username", "uptime", "stardust_earned", "xp_earned", "xp_per_hour", "stops_visited"],
"terminal_log": true,
"terminal_title": true
}
},
{
  "type": "HandleSoftBan"
},

{ "type": "UpdateWebInventory",
  "config": {
    "enabled": true
  }
},

   {
    "type": "RandomPause",
    "config": {
      "enabled": false,
      "min_duration": "00:00:10",
      "max_duration": "00:10:00",
      "min_interval": "00:10:00",
      "max_interval": "02:00:00"
    }
  },
  {
    "type": "CompleteTutorial",
    "config": {
      "enabled": true,
      "// set a name": "",
      "nickname": "SugarBison2"
    }
  },

{
  "type": "CollectLevelUpReward"
},
  {
    "type": "IncubateEggs",
    "config": {
      "longer_eggs_first": true,
      "min_interval": 120,
	  "infinite": [2,5,10],
	  "breakable": [2,5,10]
    }
  },

{
    "type": "RecycleItems",
    "config": {
      "min_empty_space": 15,
      "max_balls_keep": 150,
      "max_potions_keep": 50,
      "max_berries_keep": 70,
      "max_revives_keep": 70,
      "item_filter": {
        "Pokeball":       { "keep" : 100 },
        "Potion":         { "keep" : 10 },
        "Super Potion":   { "keep" : 20 },
        "Hyper Potion":   { "keep" : 30 },
        "Revive":         { "keep" : 30 },
        "Razz Berry":     { "keep" : 100 }
      },
      "recycle_wait_min": 1,
      "recycle_wait_max": 4
    }
  },
    {
      "type": "CatchPokemon",
      "config": {
        "catch_visible_pokemon": true,
        "catch_lured_pokemon": true,
     "daily_catch_limit": 800,
      "min_ultraball_to_keep": 5,
        "catch_throw_parameters": {
          "excellent_rate": 0.1,
          "great_rate": 0.5,
          "nice_rate": 0.3,
          "normal_rate": 0.1,
          "spin_success_rate" : 0.6
        },
			  "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": 2,
			    "changeball_wait_max": 3
			  }
      }
    },
{
    "type": "SpinFort",
    "config": {
      "spin_wait_min": 2,
      "spin_wait_max": 3
    }
  },

    {
        "type": "PokemonOptimizer",
        "config": {
            "enabled": true,
                "// the 'transfer' parameter activate or deactivate the transfer of pokemons": {},
                "// at false, no pokemon is going to be transfered, ever": {},
                "// at false, you will still get the log information of what the optimizer": {},
                "// would have transfered if the parameter was true": {},
            "transfer": true,
                "// 'transfer_wait_min' and 'transfer_wait_max' are the minimum and maximum": {},
                "// time to wait when transferring a pokemon": {},
            "transfer_wait_min": 2,
            "transfer_wait_max": 4,
                "// the 'evolve' parameter activate or deactivate the evolution of pokemons": {},
                "// at false, no pokemon is going to be evolved, ever": {},
                "// at false, you will still get the log information of what the": {},
                "// optimizer would have evolved if the parameter was true": {},
            "evolve": true,
                "// Time in seconds to wait between two evolve": {},
            "evolve_time": 20,
                "// the 'evolve_for_xp' parameter let you choose if you want the optimizer": {},
                "// to use your candies to evolve low quality pokemons in order to maximize your xp": {},
                "// at false, the optimizer will still use candies to evolve your best Pokemons": {},
            "evolve_for_xp": true,
                "// the 'evolve_only_with_lucky_egg' parameter let you choose if you want the optimizer": {},
                "// to only Evolve Pokemons when a lucky egg is available": {},
            "evolve_only_with_lucky_egg": false,
                "// the 'evolve_count_for_lucky_egg' parameter let you define the minimum": {},
                "// number of Pokemons that must evolve before using a lucky egg": {},
                "// If that number is not reached, and evolve_only_with_lucky_egg is true, evolution will be skipped": {},
                "// If that number is not reached, and evolve_only_with_lucky_egg is false,": {},
                "// evolution will be performed without using a lucky egg": {},
            "evolve_count_for_lucky_egg": 92,
                "// the 'may_use_lucky_egg' parameter let you choose if you want the optimizer": {},
                "// to use a lucky egg right before evolving Pokemons. At false; the optimizer": {},
                "// is free to evolve Pokemons even if you do not have any lucky egg.": {},
            "may_use_lucky_egg": true,
                "// the 'keep' parameter let you define what pokemons you consider are the 'best'. These Pokemons": {},
                "// will be keep and evolved. Note that Pokemons are evaluated inside their whole family": {},
                "// Multiple way of ranking can be defined. Following configuration let you keep the best iv,": {},
                "// the best ncp and the best cp": {},
            "keep": [
                {
                        "// Following setting let you keep the best iv of the family": {},
                        "// the 'top' parameter allow you to define how many Pokemons you want to keep": {},
                        "// at the top of your ranking. If several Pokemons get the same score, they are": {},
                        "// considered equal. Thus, top=1 might result in keeping more than 1 Pokemon.": {},
                    "top": 1,
                        "// the 'evolve' parameter let you choose if you want to evolve the Pokemons you keep": {},
                    "evolve": true,
                        "// the 'sort' parameter define how you want to rank your pokemons": {},
                        "// Critera are sorted fro, the most important to the least important.": {},
                        "// Available criteria are:": {},
                        "// 'iv' = individual value": {},
                        "// 'ivcp' = iv weigted so that for equal iv, attack > defense > stamina": {},
                        "// 'cp' = combat power (can be increased with candies)": {},
                        "// 'cp_exact' = combar power (not rounded)": {},
                        "// 'ncp' (normalized cp) or 'cp_percent' = ratio cp / max_cp": {},
                        "// 'iv_attack' = attach component of iv": {},
                        "// 'iv_defense' = defense component of iv": {},
                        "// 'iv_stamina' = stamina component of iv": {},
                        "// 'dps' = raw dps based on the moves of the pokemon": {},
                        "// 'dps_attack' = average dps when attacking": {},
                        "// 'attack_perfection' = ratio dps_attack / best_dps_attack. Return same order as 'dps_attack'": {},
                        "// 'dps_defense' = average dps when defending": {},
                        "// 'defense_perfection' = ratio dps_defense / best_dps_defense. Return same order as 'dps_defense'": {},
                        "// 'hp' = current health points": {},
                        "// 'hp_max' = max health points": {},
                        "// Note that the more criteria you add to this list, the less likely Pokemons": {},
                        "// will be equals": {},
                    "sort": ["iv"]
                },
                {
                    "// Following setting let you keep keep the best normalized cp of the family": {},
                    "// That is the Pokemon with higher CP once fully evolved": {},
                    "top": 1,
                    "evolve": true,
                    "sort": ["ncp"]
                },
                {
                    "// Following setting let you keep keep the best cp of the family.": {},
                    "// But will not evolve it further (in favor of the best ncp)": {},
                    "// It will only applies to the family of 'Dragonite', 'Arcanine' and 'Muk'": {},
                    "// Other families are not following this setting": {},
                    "names": ["Dragonite", "Arcanine", "Muk"],
                    "top": 1,
                    "evolve": false,
                    "sort": ["cp"]
                }
            ]
        }
  },

{
  "type": "MoveToMapPokemon",
    "config": {
      "address": "http://<IP_ADDRESS>:5000",
      "max_distance": 500,
      "min_ball": 50,
      "prioritize_vips": true,
      "snipe": true,
      "snipe_high_prio_only": true,
      "snipe_high_prio_threshold": 400,
      "update_map": true,
      "mode": "priority",
      "map_path": "raw_data",
      "catch": {
      "==========Legendaries==========": 0,
      "Aerodactyl": 1000,
      "Snorlax": 1000,
      "Articuno": 1000,
      "Zapdos": 1000,
      "Moltres": 1000,
      "Dratini": 1000,
      "Dragonair": 1000,
      "Dragonite": 1000,
      "Mewtwo": 1500,
      "Mew": 1500,

      "==========Region Locked==========": 0,
      "Farfetch'd": 1500,
      "Kangaskhan": 1000,
      "Mr. Mime": 1000,
      "Tauros": 1000,

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

      "==========Starters==========": 0,

      "Ivysaur": 600,
      "Venusaur": 1000,

      "Charmeleon": 600,
      "Charizard": 1000,

      "Wartortle": 600,
      "Blastoise": 1000,

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

      "==========Semi Rare==========": 0,

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

      "Omastar": 500,

      "Dewgong": 500,

      "Muk": 500,

      "Cloyster": 500,

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

      "Hypno": 600,

      "Ninetales": 600,

      "Wigglytuff": 500,

      "Dugtrio": 500,

      "Vaporeon": 800,
      "Jolteon": 800,
      "Flareon": 800,

      "Kabutops": 500,

      "Gyarados": 800,

      "Rapidash": 500,

      "Slowbro": 500,

      "Magneton": 500,

      "Kingler": 500,

      "Electrode": 500,

      "Exeggcutor": 500,

      "Lickitung": 500,

      "Weezing": 500,

      "Rhydon": 500,

      "Chansey": 800,

      "Seadra": 600,

      "Seaking": 500,

      "Starmie": 800,

      "==========T1 Evolvers==========": 0,
      "Butterfree": 500,

      "Beedrill": 500,

      "==========T2 Evolvers==========": 0,

      "Vileplume": 600,

      "Poliwrath": 800,

      "Kadabra": 600,
      "Alakazam": 800,

      "Machamp": 800,

      "Victreebel": 800
    }
  }
},
  {
    "type": "MoveToFort",
    "config": {
      "lure_attraction": true,
      "lure_max_distance": 2000,
      "walker": "StepWalker"
    }
  },
  {
    "type": "FollowSpiral",
    "config": {
      "diameter": 4,
      "step_size": 70
    }
  }

],
"map_object_cache_time": 5,
"forts": {
"avoid_circles": true,
"max_circle_size": 50,
"cache_recent_forts": true
},
"walk_min": 13,
"walk_max": 23,
"sleep_schedule": [
{
"time": "22:53",
"duration": "7:39",
"time_random_offset": "00:30",
"duration_random_offset": "00:30",
"wake_up_at_location": ""
}
],
"alt_min": 500,
"alt_max": 1000,
"gps_default_altitude": 8.0,
"replicate_gps_xy_noise": false,
"replicate_gps_z_noise": false,
"gps_xy_noise_range": 0.000125,
"gps_z_noise_range": 12.5,
"action_wait_min": 1,
"action_wait_max": 5,
"debug": false,
"test": false,
"health_record": false,
"location_cache": true,
"distance_unit": "km",
"reconnecting_timeout": 1,
"logging": {
"color": true,
"show_datetime": true,
"show_process_name": false,
"show_log_level": false
},
"catch_randomize_reticle_factor": 1.0,
"catch_randomize_spin_factor": 1.0,
"catch_throw_parameters": {
"excellent_rate": 0.7,
"great_rate": 0.5,
"nice_rate": 0.3,
"normal_rate": 0.1,
"spin_success_rate" : 0.8
},
"catch": {
"any": {"catch_above_cp": 0, "catch_above_iv": 0, "logic": "or" },
"// Pokemons with example": { "always_catch": true },
"// Gets filtered with release parameters": {},

"// Legendary pokemons (Goes under S-Tier)": {},
"Lapras": { "always_catch": true },
"Moltres": { "always_catch": true },
"Zapdos": { "always_catch": true },
"Articuno": { "always_catch": true },

"// S-Tier pokemons (if pokemon can be evolved into tier, list the representative)": {},
"Mewtwo": { "always_catch": true },
"Dragonite": { "always_catch": true },
"Snorlax": { "always_catch": true },
"// Mew evolves to Mewtwo": {},
"Mew": { "always_catch": true },
"Arcanine": { "always_catch": true },
"Vaporeon": { "always_catch": true },
"Gyarados": { "always_catch": true },
"Exeggutor": { "always_catch": true },
"Muk": { "always_catch": true },
"Weezing": { "always_catch": true },
"Flareon": { "always_catch": true },

"// Growlithe evolves to Arcanine": {},
"Growlithe": { "always_catch": true },
"// Dragonair evolves to Dragonite": {},
"Dragonair": { "always_catch": true },
"// Grimer evolves to Muk": {},
"Grimer": { "always_catch": true },

"// Magikarp evolves to Gyarados": {},
"Magikarp": { "always_catch": true },
"// Exeggcute evolves to Exeggutor": {},
"Exeggcute": { "always_catch": true },
"// Eevee evolves to many versions, like Vaporeon, Flareon": {},
"Eevee": { "always_catch": true },

"// A-Tier pokemons": {},
"Slowbro": { "always_catch": true },
"Victreebel": { "always_catch": true },
"Machamp": { "always_catch": true },
"Poliwrath": { "always_catch": true },
"Clefable": { "always_catch": true },
"Nidoking": { "always_catch": true },
"Venusaur": { "always_catch": true },
"Charizard": { "always_catch": true },
"Golduck": { "always_catch": true },
"Nidoqueen": { "always_catch": true },
"Vileplume": { "always_catch": true },
"Blastoise": { "always_catch": true },
"Omastar":  { "always_catch": true },
"Aerodactyl": { "always_catch": true },
"Golem": { "always_catch": true },
"Wigglytuff": { "always_catch": true },
"Dewgong": { "always_catch": true },
"Ninetales": { "always_catch": true },
"Magmar": { "always_catch": true },
"Kabutops": { "always_catch": true },
"Electabuzz": { "always_catch": true },
"Starmie": { "always_catch": true },
"Jolteon": { "always_catch": true },
"Rapidash": { "always_catch": true },
"Pinsir": { "always_catch": true },
"Scyther": { "always_catch": true },
"Tentacruel": { "always_catch": true },
"Gengar": { "always_catch": true },
"Hypno": { "always_catch": true },
"Pidgeot": { "always_catch": true },
"Rhydon": { "always_catch": true },
"Seaking": { "always_catch": true },
"Kangaskhan": { "always_catch": true }

},
"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": {},
"Vaporeon": {},
"Gyarados": {},
"Exeggutor": {},
"Muk": {},
"Weezing": {},
"Flareon": {}

}
}
Output when issue occurred
there's no output - bot is running as expected but just not updating its stats to the web ui
Steps to Reproduce
go into Web UI - click INFO button
Other Information
OS:
Ubuntui 14.04 LTS
Branch:
Latest DEV

We're using a very old (and dirty) commit of the WebUI. Issue is caused by location-xxx.json no longer having the user_id/player_stats data.
I'm not sure if it worth to keep everything in place to not break web. I think it's better to move to a websockets web.

after i've set the "UpdateLiveStats", to true the info button is working again

Then it's not being initialised when UpdateLiveStats is set to false.

@Jasperrr91 and is there any? 'cause i see the websocket_server option in the config, but it's not documented at all. can't even specify a port for it to use...

@r3pek yes: https://github.com/PokemonGoF/PokemonGo-Web/tree/rewrite
I believe this websocket_server documentation is severely outdated. I'll update it later today.

This issue was fixed a few days ago. Closing.


GUI Issue - Timeline view

Is this a BUG REPORT or FEATURE REQUEST?:
Bug
What happened:
http://argo.applatix.net/workflows/default/argo-ci-lmf7w?tab=timeline&nodeId=null
The workflow timeline show from 1:05 to 1:04 - how is that possible
Also when i click on one step and close the summary window, it leave gray image to the right which goes after resizing the browser

Fixed


Color Swatch emojis

Note: This is a more focused spinoff or subset of the discussion about colored/material hearts #222.
The human eye and brain can distinguish thousands if not millions of colors, but in language, we regularly only refer to a very small and thus crude subset, which depends on the domain, of course. There is only a handful of canonical color names that are used in common parlance and several dozen color designations that one would roughly understand in a special setting.
Text is predominantly monochrome, i.e. a single foreground or ink color and a single background or canvas color. Colorful characters – like emojis usually are – has been used throughout history if and where possible, though. There are some (compatibility) emojis that could be reused as color swatches, but no shape (heart, square, diamond, circle, book) already has enough variations. Some of them also do not have good monochromatic fallback. There are some existing characters, however, that are not yet emojis, but could work as conventional representations of colors in B&W text: hatching squares.
There are various conventions to match colors (or surface materials) with hatching patterns, but the one originating from European heraldry is probably best known and most suitable. There are existing characters for, at least, blue, red, green, purple, black and white swatches, which would just require an emoji presentation variation selector U+FE0F (VS-16) appended. This would be recorded in emoji-variation-sequences.txt and could be done without waiting for an update to the Unicode Standard, since such emoji data is governed by UTS51. There was already a proposal to Unicode to add additional pattern squares, which would be introduced in a future release of the Unicode Standard (i.e. 11.0 in June 2018 or later).

Color
Tincture
Pattern
Sample
Description

black
ink
■ U+25A0

filled, solid, opaque, foreground

white = silver
argent
□ U+25A1?

white
canvas
▢ U+25A2?

none, blank, empty, transparent, background

?
?
▣ U+25A3

(filled square inside empty square)

blue
azure
▤ U+25A4

-- horizontal stripes

red
gules
▥ U+25A5

|| vertical stripes

black
sable
▦ U+25A6

++ square pattern, orthogonal crosshatch

(lime) green
vert
▧ U+25A7

\\ forward diagonals

purple
purpure
▨ U+25A8

// backward diagonals

reddish purple
murrey
▩ U+25A9

/\ diagonal crosshatch

dark-gray = iron, steel
—
▩ U+25A9 (X+2BxE)

XX diamond pattern (German)

yellow = gold
or
X+2Bx0

.. dotted

dark red (maroon/pink)
sanguine
X+2Bx1

-\ horizontal-forward crosshatch

orange-tawny
tenné
X+2Bx2

-/ horizontal-backward crosshatch

brown
brunâtre
X+2Bx3

|\ vertical-forward crosshatch

grey
fey
X+2Bx4

|/ vertical-backward crosshatch (English)

(alternate) blood red (pink)
(sanguine)
X+2Bx4

|/ vertical-backward crosshatch (German)

flesh, skin
carnation
X+2Bx7

|  vertical dashed

ash-gray
cendrée
X+2Bx8

|- alternating dashed

sky-blue
bleu-céleste
X+2Bx9

-. horizontal dash-dotted (Spanish: green)

orange
—
X+2BxA

! vertical dash-dotted

(alternate) green
(vert)
X+2BxB

.-. dotted horizontal stripes (Spanish)

(alternate) orange-tawny
(tenné)
X+2By1

.|. dotted vertical stripes (English)

Michael Everson's proposal from April 2011 had new Square With ... Fill characters at U+2B60..2B71. These codepoints have since been delegated to some arrows. The block Miscellaneous Symbols and Arrows U+2Bxy still has some other unassigned slots that could be used instead, e.g. U+2BD2..2BEB or U+2BF0..2BFF.

 This could be a hair color, car paint, nail polish, blossom color, nib ink, symbol tint etc. Any frequent combination would be documented in emoji-zwj-sequences.txt. (Skin complexion is already dealt with by dedicated combining Emoji Modifier characters U+1F3FA..F that are based upon the Fitzpatrick scale, but combine its first two values into one. If added, X+2Bx7 carnation might need to become an Emoji Modifier Base.)
For UTC150 in November 2016, @pauldhunt (unsuccessfully) proposed 10 new characters for color swatches in L2/16-318, which map to U+25A5 ▥, U+2BxA, U+2Bx0, U+25A7 ▧, U+25A4 ▤, U+25A8 ▨, U+25A1 □, U+25A6 ▦, U+25A9 ▩/2BxE/2Bx8 and U+2Bx3 above:

RED
ORANGE
YELLOW
GREEN
BLUE
PURPLE
WHITE (may potentially use WHITE LARGE SQUARE, U+2B1C)
BLACK (may potentially use BLACK LARGE SQUARE, U+2B1B)
GREY
BROWN

Proposals

L2/11-094
L2/16-318

Standard References

Unicode Technical Standard 51 “Unicode Emoji”
How to propose emojis to Unicode
Unicode document submission form

DIN 30601:1971 offered a more systematic approach for additive colors with lines for red, dashes for green and dots for blue. Hatchings of composite colors would use combinations of these basic patterns. They intentionally deviate from heraldic customs to ensure independence of drawing orientation. Black and White would be fully and not filled, respectively.

Henrik Theiling made an artificial writing system for the constructed language Toki Pona by Sonja Elen Kisa, which uses some of the patterned squares for different colors:

Char
Codepoint
Color

■
U+25A0
black

▤
U+25A4
red

▥
U+25A5
yellow, light green

▦
U+25A6
blue-green, cyan

▧
U+25A7
colorful

☐
U+2610
white

David P. Kendal and for 12 emoji color modifiers in L2/17-355.

red
orange
yellow
green
dark blue
light blue
pink
purple
brown
black
grey
white

This set was apparently identified by Berlin and Kay in linguistic study.
Evo


Idea: Clicking on activity icon in detail panel pans to activity point

This will be discussed in #56

This is only relevant for certain activities in a fraction of locations.
Desktop: with zoom/pan guidelines in place, activity locations should be apparent and further zooming/panning may not be desirable or meet user expectations.
Mobile: implementation could be difficult zoom/pan + hide panel. May not meet user expectations.


Why doesn't my project appear?

http://godoc.org/?q=toc
Doesn't show https://github.com/kaihendry/toc
Is it because I am missing inline documentation? Any pointers please?

It is there. I'm guessing this is a new repo. I guess gddo didn't update this repo in time. You can manually let gddo fetch a repo by go to http://godoc.org/github.com/kaihendry/toc


Fix building on Windows.

This fixes building on Windows. We disable reordering and fix iridium to link correctly on Chromium 55. We still download syzygy for now until we decide if we want to keep it. icu_use_data_file has to be enabled on Windows for now to get it to at least build. Patches are not read into memory and piped over stdin anymore.
We can just kill syzygy building/downloading all together if you like, but I think it may be worth looking into at some point if performance or linking problems come up.
Should fix both #137 #118

I do apologize for the terribly formatted git message. I was in a rush to get this pull request created before I went to bed to avoid another 24 hour wait.
I'll check 64bit build tomorrow.

The commit message is fine. Good implementation of the changes. We should probably disable downloading syzygy for now by commenting out the lines in extra_deps.ini so there won't be extra downloading.
Also what is the problem with the original code for patching? What kind of errors (or any output) do you get? The GNU patch utility I instructed users to use in BUILDING works on Windows 10.

The patch function outputs patching but it doesn't patch anything. I can look further into it.
I'll disable the download when I test 64bit
Sent from my android device.

The patch function outputs patching but it doesn't patch anything. I can look further into it.

That's really weird. I have no idea what can be causing that if the patch utility hasn't changed and buildlib's invocation of it hasn't changed. Maybe it's some weird Windows silent failure?

I think it might be due to how python is interacting with the shell, but stdin might have been acting strangely in my setup. I'm not using ActivePython, but the official release. It might work if I updated python 3 I just noticed I'm on a REALLY old version.
C:\Users\nopjmp>C:\Python34\python.exe
Python 3.4.3 (v3.4.3:9b73f1c3e601, Feb 24 2015, 22:44:40) [MSC v.1600 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>

@nopjmp Ah yeah Python 3.5 changed some stuff with the subprocess module. You should upgrade since I haven't tested the behavior with Python 3.4 on Windows (someone has on Debian Jessie though, but it's different from Windows).

@Eloston 64bit builds, but I need to fix GN bootstrap.py to compile for 64bit. Otherwise, it works just fine. I'll try to clean it up today if I have time; otherwise, it will be done tomorrow. I'll test Python3.5 also.

@nopjmp Alright sounds good. Glad to hear that we're almost there.

Windows 64bit is fixed and I reverted the hacked up patch function.

Perfect. Even all of the patches and code are consistent in style with everything else. Thanks for the great work!


[Rocketmq 350] Add multiple Network Interface Cards support

What is the purpose of the change
It is becoming commonplace to have more than one Network Interface Card (NIC), usually one for local network communication, another for remote communication.
Supporting multiple Network Interface Cards support for “Broker Machine” could be very useful.
Brief changelog
1 Broker will report multiple addresses to Name Server, the format is like the multiple nameServer addr: ip1;ip2;ip3:port
2 After consumer/producer get the route info from Name Server, there is a test or detect process, then store one accessible address for each broker.
3 All the changes are backward compatible. But if using the changed broker and old version client, the consumer/producer will get exception because fetched broker’s addr is not “ip:port”, it could be “ip1;ip2:port”.
4 add a configure Parameter in the broker to disable the new feature
Verifying this change
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x ] Format the pull request title like [ROCKETMQ-XXX] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[ x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x ] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.2%) to 40.055% when pulling 5af660c65c4000dbcc9f88beae9df3c46a6b240b on mark800:ROCKETMQ-350 into 2d43e75eb3789b02dd4f65865ac34ad10652f6ce on apache:master.

@zhouxinyu could you please help to review this pr?

But if using the changed broker and old version client.....

We must operate with that, it's a very common deployment structure.

@zhouxinyu Added “isEnableMultipleNICSupport” option in brokerConfig

@mark800 Could you resolve the conflicts, I will help to review your pr.

@mark800 Could you modify your code to make travis check pass?

@vongosling travis check passed, could you please review the pr?

Could you tell us your real use case for your Multi Network Interface Cards, how do you choose if we have many ips?


Paste very slow

Copy/paste one node works fine, but pasting trees is extremely slow, with larger trees often taking minutes

some work has been done on that, I can now paste all of Hamlet.xml anywhere inside Hamlet.xml very quickly.


SAK-50053 permissionswc Make permissions component responsive

https://sakaiproject.atlassian.net/browse/SAK-50053


Added Android Studio version <IP_ADDRESS>.

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Have you tested your manifest locally with winget install -m ?

Finally!  #3680 can be closed now that winget manifests can contain alternative success codes.
Microsoft Reviewers: Open in CodeFlow

/azp run


Add a way to display only one error for a field

Describe the bug
Currently we return field.state.meta.touchedErrors ValidationError[] as a string by concataining the different errors of a field with commas.
It would be great to be able to display only one error.
e.g:
         validators={{
            onChange: v.string([
              v.minLength(1, t(i18n)`This field is mandatory`),
              v.custom(isDateStringValid, t(i18n)`The birth date format is incorrect`),
              v.custom(isDateStringOver18, t(i18n)`You have to be at least 18 years`),
            ]),
          }}

These valibot validators will end up on showing all three errors just by typing a letter and deleting it.
Imo, this is not a good UX.
I would expect some kind of priority in the error messages, thus only displaying the first validation to return an error.
Your minimal, reproducible example
https://github.com/TanStack/form/
Steps to reproduce
     validators={{
        onChange: v.string([
          v.minLength(1, t(i18n)`This field is mandatory`),
          v.custom(isDateStringValid, t(i18n)`The birth date format is incorrect`),
          v.custom(isDateStringOver18, t(i18n)`You have to be at least 18 years`),
        ]),
      }}

Expected behavior
More control over the errors display
How often does this bug happen?
None
Screenshots or Videos
No response
Platform
macOS
TanStack Form adapter
react-form
TanStack Form version
0.19.0
TypeScript version
No response
Additional context
No response

This should be done at the validator level where you can pass transformErrors to transformErrors: errors => errors[0] rather than   transformErrors: errors => errors.join(', ')
Will mark this as "Good first issue" and a feature request

Hello, can I work on this issue? If possible, please assign it to me.

@crutchcorn Hello, can I work on this issue? If possible, please assign it to me. 😊

Not sure if this is relevant to this issue or if I should create a separate one but being able to return an array from
validators={{
    onChange: ["err1", "err2"] // string | string[]
}}

would be a very nice addition.

@jessekelly881 let's open a different issue on it :)
@seobbang PRs welcome! No need to assign it out, but do feel free to tackle the issue :)

Would love this fixed @seobbang did you manage to work on this?

@TheKnightCoder I'm going to try again 🤗

It would be nice to accept ValidatonError[] as return value for FieldValidateOrFn since there could be some cases when we want all errors to be shown from a single validation.
For example, when setting password we may want to show multiple errors under the input like 'length should be longer than 8', 'should contain special characters', ...

I quickly passed by here and was seeing something like this, it probably doesn't work and I don't have time to test/research in depth but maybe it will help:
import { safeParse, safeParseAsync } from 'valibot'
import type { BaseIssue, BaseSchema, BaseSchemaAsync } from 'valibot'
import type { Validator } from '@tanstack/form-core'

type Params = {
  errorMap?: (
    errors: [BaseIssue<unknown>, ...BaseIssue<unknown>[]],
  ) => BaseIssue<unknown>
}

export const valibotValidator = (params: Params) =>
  (() => {
    return {
      validate({ value }, fn) {
        if (fn.async) return
        const result = safeParse(fn, value)
        if (result.success) return
        if (params.errorMap) {
          return params.errorMap(result.issues)
        }
        return result.issues.map((i) => i.message).join(', ')
      },
      async validateAsync({ value }, fn) {
        const result = await safeParseAsync(fn, value)
        if (result.success) return
        if (params.errorMap) {
          return params.errorMap(result.issues)
        }
        return result.issues.map((i) => i.message).join(', ')
      },
    }
  }) as Validator<
    unknown,
    | BaseSchema<unknown, unknown, BaseIssue<unknown>>
    | BaseSchemaAsync<unknown, unknown, BaseIssue<unknown>>
  >

@t-rosa @crutchcorn
I have a question.
According to what you(@t-rosa ) suggested, when valibotValidator is used in useForm it can be used like:
validatorAdapter: valibotValidator({errorMap: errors => errors[0]}),

But the problem is that even if I want to use the default value, I have to use it with function call:
validatorAdapter: valibotValidator(),

But because we've been used like:
validatorAdapter: valibotValidator,

it's going to be a problem for people who are already using this validator.
So, should I make another validator, for example, valibotValidatorWithOption`?
Please tell me if I'm wrong or if there's any other way.
Thank you for your help

I wonder if it does the job?
import { safeParse, safeParseAsync } from 'valibot'
import type { BaseIssue, BaseSchema, BaseSchemaAsync } from 'valibot'
import type { Validator } from '@tanstack/form-core'

type Params = {
  errorMap?: (
    errors: [BaseIssue<unknown>, ...BaseIssue<unknown>[]],
  ) => BaseIssue<unknown>
}

export const valibotValidator = ((params: Params) => {
  return {
    validate(
      { value }: { value: unknown },
      fn: BaseSchema<unknown, unknown, BaseIssue<unknown>>,
    ) {
      if ((fn as any).async) return
      const result = safeParse(fn, value)
      if (result.success) return
      if (params.errorMap) {
        return params.errorMap(result.issues)
      }
      return result.issues.map((i) => i.message).join(', ')
    },
    async validateAsync(
      { value }: { value: unknown },
      fn: BaseSchemaAsync<unknown, unknown, BaseIssue<unknown>>,
    ) {
      const result = await safeParseAsync(fn, value)
      if (result.success) return
      if (params.errorMap) {
        return params.errorMap(result.issues)
      }
      return result.issues.map((i) => i.message).join(', ')
    },
  }
}) as Validator<
  unknown,
  | BaseSchema<unknown, unknown, BaseIssue<unknown>>
  | BaseSchemaAsync<unknown, unknown, BaseIssue<unknown>>
>

Maaaybe this? (Sorry it's not very clean I guess :'()
import { safeParse, safeParseAsync } from 'valibot'
import type { BaseIssue, BaseSchema, BaseSchemaAsync } from 'valibot'
import type { Validator } from '@tanstack/form-core'

type Params = {
  errorMap?: (
    errors: [BaseIssue<unknown>, ...BaseIssue<unknown>[]],
  ) => BaseIssue<unknown>
}
type validateValue = { value: unknown }
type validateFn =
  | BaseSchema<unknown, unknown, BaseIssue<unknown>>
  | BaseSchemaAsync<unknown, unknown, BaseIssue<unknown>>

export const valibotValidator = ((params: Params = {}) => {
  return {
    validate({ value }: validateValue, fn: validateFn) {
      if (fn.async) return
      const result = safeParse(fn, value)
      if (result.success) return
      if (params.errorMap) {
        return params.errorMap(result.issues)
      }
      return result.issues.map((i) => i.message).join(', ')
    },
    async validateAsync({ value }: validateValue, fn: validateFn) {
      const result = await safeParseAsync(fn, value)
      if (result.success) return
      if (params.errorMap) {
        return params.errorMap(result.issues)
      }
      return result.issues.map((i) => i.message).join(', ')
    },
  }
}) as Validator<
  unknown,
  | BaseSchema<unknown, unknown, BaseIssue<unknown>>
  | BaseSchemaAsync<unknown, unknown, BaseIssue<unknown>>
> &
  ((
    params: Params,
  ) => Validator<
    unknown,
    | BaseSchema<unknown, unknown, BaseIssue<unknown>>
    | BaseSchemaAsync<unknown, unknown, BaseIssue<unknown>>
  >)

@t-rosa this looks awesome! Let's move forward with it in a PR :)
@seobbang this WILL be a breaking change, but a very minor one. We're prior to 1.0 so that shouldn't be a problem

I'm sorry for my slow understanding.
The current type of validatorAdapter:
export type Validator<Type, Fn = unknown> = () => {
    validate(options: {
        value: Type;
    }, fn: Fn): ValidationError;
    validateAsync(options: {
        value: Type;
    }, fn: Fn): Promise<ValidationError>;
};

But if i use valibotValidator like this with @t-rosa 's code
 validatorAdapter: valibotValidator({ errorMap: (errors) => errors[0] }),

valibotValidator return just
 {
    validate({ value }: validateValue, fn: validateFn) {
      if (fn.async) return
      const result = safeParse(fn, value)
      if (result.success) return
      if (params.errorMap) {
        return params.errorMap(result.issues)
      }
      return result.issues.map((i) => i.message).join(', ')
    },
    async validateAsync({ value }: validateValue, fn: validateFn) {
      const result = await safeParseAsync(fn, value)
      if (result.success) return
      if (params.errorMap) {
        return params.errorMap(result.issues)
      }
      return result.issues.map((i) => i.message).join(', ')
    },
  }

Not function, just object.
So the types don't match.
How can this be solved?

I'm sorry for my slow understanding.
The current type of validatorAdapter:
export type Validator<Type, Fn = unknown> = () => {
    validate(options: {
        value: Type;
    }, fn: Fn): ValidationError;
    validateAsync(options: {
        value: Type;
    }, fn: Fn): Promise<ValidationError>;
};

But if i use valibotValidator like this with @t-rosa 's code
 validatorAdapter: valibotValidator({ errorMap: (errors) => errors[0] }),

valibotValidator return just
 {
    validate({ value }: validateValue, fn: validateFn) {
      if (fn.async) return
      const result = safeParse(fn, value)
      if (result.success) return
      if (params.errorMap) {
        return params.errorMap(result.issues)
      }
      return result.issues.map((i) => i.message).join(', ')
    },
    async validateAsync({ value }: validateValue, fn: validateFn) {
      const result = await safeParseAsync(fn, value)
      if (result.success) return
      if (params.errorMap) {
        return params.errorMap(result.issues)
      }
      return result.issues.map((i) => i.message).join(', ')
    },
  }

Not function, just object.
So the types don't match. How can this be solved?

Yes, you're right.
I think we should use the first version, even if it's a mini breaking change. as crutchcorn said it shouldn't be a problem :)
So this one maybe the best option:
import { safeParse, safeParseAsync } from 'valibot'
import type { BaseIssue, BaseSchema, BaseSchemaAsync } from 'valibot'
import type { Validator } from '@tanstack/form-core'

type Params = {
  errorMap?: (
    errors: [BaseIssue<unknown>, ...BaseIssue<unknown>[]],
  ) => BaseIssue<unknown>
}

export const valibotValidator = (params: Params = {}) =>
  (() => {
    return {
      validate({ value }, fn) {
        if (fn.async) return
        const result = safeParse(fn, value)
        if (result.success) return
        if (params.errorMap) {
          return params.errorMap(result.issues)
        }
        return result.issues.map((i) => i.message).join(', ')
      },
      async validateAsync({ value }, fn) {
        const result = await safeParseAsync(fn, value)
        if (result.success) return
        if (params.errorMap) {
          return params.errorMap(result.issues)
        }
        return result.issues.map((i) => i.message).join(', ')
      },
    }
  }) as Validator<
    unknown,
    | BaseSchema<unknown, unknown, BaseIssue<unknown>>
    | BaseSchemaAsync<unknown, unknown, BaseIssue<unknown>>
  >

It should be ok for valibot, the PR is open, we should be able to do the same for the other validators

I just submitted a PR to be able to pass a config to the valibot adaptator: https://github.com/TanStack/form/pull/980
Using the abortPipeEarly option of valibot seem felt cleaner for me, and would fix this issue too...


Add logic to simplify Avro decoding and field access

Event payloads looks like this after being decoded by Avro:
{
    Name: { string : "My name" },
    LastModifiedDate: { long:<PHONE_NUMBER>000 }
}

It would be nice to strip the intermediate type properties and produce something like this:
{
    Name: "My name",
    LastModifiedDate:<PHONE_NUMBER>000
}

This was an issue for us, and I came up with this solution. I'm curious what others are doing. This worked for Platform Events, haven't tested change data capture since we don't use it.
Object.entries(payload).forEach(([key, value]) => {
    if (value && typeof value === 'object') {
        payload[key] = value[Object.keys(value)[0])
    }

Thanks for the lead @soileaud. The implementation turned out to be a bit more complex because of compound types but it's now part of v3.0.0.


Fix incorrect method name header in api docs

Noticed an incorrect method name in the documentation related to registerRemoteNotificationsRegistrationDenied.

Do we know if there is a 4.2.5 release planned within the next week?  I was super excited to see registerRemoteNotificationsDenied pop up in the documentation as it resolves a blocking bug for us.  If there's a way I can help, please let me know.

Thanks! nice catch. releasing today, sorry for the late response

release is 4.3.0


People are more than users

Fixes #275  Use people instead of user. In our department, we have 2 Patrick Browns. So, we would need to differentiate them by name (Patrick J Brown and Patrick M Brown), then use the person, not user name to get them listed correctly in history.

Not totally sold on this being the solution to non-repudiation. Won't they both have different user ids?

Yes, but we don't display the userID in the text of the history description. Database will always know they are different, but folks reading the text won't.

What's to prevent Person.Name being the same for two people?

We have an open issue to allow teams to edit the person's name (only for that team). Haven't implemented, but that's how teams will be able to differentiate.

Yeah, but shouldn't the user be capable of editing their own User.DisplayName? You can update the history descriptions to be "DisplayName (kerberos)" to differentiate, which will show the user's preferred display name but still offer the feature you need.

In the design committee meetings, they were very insistent that team admins be able to update the name for that team, but no change that person's name in another team. That's why we created the person.firstname and .lastname instead of just using the user name that is pulled from IAM. That's why I updated to pull from person instead of user.

Okay. Given that requirement, yeah, use Person. But I still think you should a "(kerberos)" entry instead of mandating Team Unique.


fix(textfield): height improvements

Hello!
In this PR i've removed the fixed height on textifelds. With this improvement we can easliy reuse the component in other projects where we need to adjust the height.
Please let me know if i missed something.

Hi, thanks a lot for taking the time to do this! We will have a closer look at this one soon (I am in the office and Storybook is not accessible from the scania network).
A couple of things before having a look though:
In a couple of days we are going to release a Small variant for our textfield component, that hopefully will make it possible to use it in more compact spaces.
The reason why we don't leave full freedom on the height of this component, is to avoid stretching its use, just for the sake of fitting things in small spaces, disregarding usability or UX considerations. Also, by only having 3 size variants, we can achieve higher consistency across different apps/pages within an app.
Would you say that you need considerably smaller textfields? Our large one is 56px high, our medium one 48px high and the new small variant will be 40px tall.

Thanks for replying!
Sounds good that you will be making another size for the textfield. I understand your thoughts and ideas why you want fixed heights. However though, it will only work when you're using your library from scatch in a new project. If you're migrating from an already existing project you need to make bigger adjustments and it will affect the application on greater matter. I'm looking for a textfield with a height of 30px-35px. We could indeed use your textfield as it is today but in our case we need to rebuild the hole header just to make it work. What do you think about a prop for the height? We could use 50px as default and perhaps a minimum of 30px? @alexlioliopoulos

We are still a bit hesitant about opening up the component in this way, for the reasons I explained in my previous comment. If including such a prop, hence making it super easy for consumers of our packages to go super-small in the input elements, we expect many of them to go that way for most of the cases (not only specific cases like the header one that you are mentioning, which makes sense). Using smaller things seems to be appealing, since you can gather more things in a small real estate. However, it usually brings worse UX.
So, regarding your specific issue, I would suggest creating a new component that would resemble the styling of the SDDS textfield one, and make it as tall as you need it to be. Or of course, use the SDDS header as well, which could work fine with the textfield too. What do you think?

Yes you've got a point. We will build our own component instead as you suggested. We can use your textfield-component in the future when we're ready for your header as well. We can close this PR. @alexlioliopoulos


Possible problems with sparkey files with two dots in file names.

Say you have a Sparkey index file and log file that is in the following form:
a-b-c.sparkey.spi, a-b-c.sparkey.spl. Assuming the "base file" here is "a-b-c.sparkey", the getIndexFile method will return "a-b-c.spi" and the getLogFile method will return "a-b-c.spl"

Good catch, that should be easy to fix!

This would hopefully fix your issue: #22

Yes. Should I close the issue?


Free space to show negatiove values

Free space should show negative values
Fixes https://github.com/project-koku/koku-ui/issues/1214
Fixes https://github.com/project-koku/koku-ui/issues/1214

Codecov Report

Merging #1225 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1225   +/-   ##
=======================================
  Coverage   75.69%   75.69%
=======================================
  Files         231      231
  Lines        4485     4485
  Branches      872      872
=======================================
  Hits         3395     3395
  Misses        956      956
  Partials      134      134

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 bf44a8c...68d9b52. Read the comment docs.


[LandingHeader.jsx] - add responsive landing page header

Task Description
Briefly describe the task or project.
Details
(Please Provide Key Details, if required)

Goals and objectives
Deliverables
Dependencies

Branch Name
PR Should be made in feature/LandingPage Branch.
For more information, please read our Contributing Guidelines.
Deadline
Specify the task deadline.
Priority
Set the priority: [High/Medium/Low]
Additional Details
Add any other context about the task here.
Instructions
Stay you can start working on it by taking latest pull from main branch

[ ] Please read the contributors guidelines Contributing Guidelines.
[ ] Please follow the code of conduct Code Of Conduct
[ ] Don't Forget to join onboarding group for knowledge flow and direct conversation and support from admins
[ ] Link Curious Developers Community - Curious Connect
[ ] Please attach the screenshots and video of the development work once it is done
[ ] Contributions more than 3 will be awarded a certificate of appreciation from curious ecosystem
[ ] please mail to<EMAIL_ADDRESS>for claiming certificate and please attach your issue number

Respect Co Developers And Please Reach-out to admins if any issues
Additional Details
Add any other context about the task here.

Can I work on this issue ?

👋 Hello! I'd be happy to help with this issue. Could you please assign it to me? Additionally, could you please label it for the appropriate level? Thank you! 🚀

Instructions
You can start working on it by taking latest pull from main branch

[ ] Please read the contributors guidelines Contributing Guidelines.
[ ] Please follow the code of conduct Code Of Conduct
[ ] Don't Forget to join onboarding group for knowledge flow and direct conversation and support from admins
[ ] Link Curious Developers Community - Curious Connect
[ ] Please attach the screenshots and video of the development work once it is done
[ ] Contributions more than 3 will be awarded a certificate of appreciation from curious ecosystem
[ ] please mail to<EMAIL_ADDRESS>for claiming certificate and please attach your issue number

Respect Co Developers And Please Reach-out to admins if any issues

👋 Hello! I'd be happy to help with this issue. Could you please assign it to me? Additionally, could you please label it for the appropriate level? Thank you! 🚀

Instructions
You can start working on it by taking latest pull from main branch

[ ] Please read the contributors guidelines Contributing Guidelines.
[ ] Please follow the code of conduct Code Of Conduct
[ ] Don't Forget to join onboarding group for knowledge flow and direct conversation and support from admins
[ ] Link Curious Developers Community - Curious Connect
[ ] Please attach the screenshots and video of the development work once it is done
[ ] Contributions more than 3 will be awarded a certificate of appreciation from curious ecosystem
[ ] please mail to<EMAIL_ADDRESS>for claiming certificate and please attach your issue number

Respect Co Developers And Please Reach-out to admins if any issues

Can I work on this issue ? And why are the labels for gssoc not added in the issues

Instructions
You can start working on it by taking latest pull from main branch

[ ] Please read the contributors guidelines Contributing Guidelines.
[ ] Please follow the code of conduct Code Of Conduct
[ ] Don't Forget to join onboarding group for knowledge flow and direct conversation and support from admins
[ ] Link Curious Developers Community - Curious Connect
[ ] Please attach the screenshots and video of the development work once it is done
[ ] Contributions more than 3 will be awarded a certificate of appreciation from curious ecosystem
[ ] please mail to<EMAIL_ADDRESS>for claiming certificate and please attach your issue number

Respect Co Developers And Please Reach-out to admins if any issues

@thecuriousteam I would like to take on this task and create a responsive header for the website. I will ensure that the header looks good on all screen sizes and devices. Please assign this issue to me. under GSSOC'24

Yes @paulkrishanu4 you can start working on it

@thecuriousteam can I start working on that issue

@thecuriousteam can I start working on that issue

Instructions
You can start working on it by taking latest pull from main branch

[ ] Please raise pull request to feature/InitialUIDesign
[ ] Please read the contributors guidelines Contributing Guidelines.
[ ] Please follow the code of conduct Code Of Conduct
[ ] Don't Forget to join onboarding group for knowledge flow and direct conversation and support from admins
[ ] Link Curious Developers Community - Curious Connect
[ ] Please attach the screenshots and video of the development work once it is done
[ ] Contributions more than 3 will be awarded a certificate of appreciation from curious ecosystem
[ ] please mail to<EMAIL_ADDRESS>for claiming certificate and please attach your issue number

if any help required reach-out to admins or mentors in the onboarding group default meeting link and approach to admins - [https://meet.google.com/bwp-aasw-xbk]
Respect Co Developers And Please Reach-out to admins if any issues

Is landing header means normal header of any website with responsiveness


Allow use with jquery 2.0 (bower)

Is there some reason that the bower definition restricts usage of jquery 2.0?

hi @aaronchi the plugin is not yet tested with jQuery 2.0, which does not support IE8 anymore

Now compatible


Set min identifier to 1

To support code like this:
public enum ECLevel: String, CaseIterable {
   case l = "L"
   case m = "M"
   case q = "Q"
   case h = "H"
}

or this
for i in (0..<5) {
   print(\(i))
}

Change .yml to:
identifier_name:
  max_length:
    warning: 100
    error: 100
  min_length:
    warning: 1  // 👈 was 2
    error: 1 // 👈 was 2

The rule is intentional. Single-character variable names reduce readability.
The above should be:
public enum ErrorCorrectionLevel: String, CaseIterable {
	case low = "Low"
	case medium = "Medium"
	case quality = "Quality"
	case high = "High"
}

So just out of professional curiosity.
Would you write:
let x = 2 👉 let xVal = 2
for i in (0..<5){ print(i) } 👉 for index in (0..<5){ print(index) }

let x = 2 👉 let xVal = 2

x and y are fine if they're actually referring to coordinates.
https://github.com/sindresorhus/swiftlint-sindre/blob/471f96b56cdc3ad34e059dc0ca3dc46fae72b7be/.swiftlint.yml#L148-L149

for i in (0..<5){ print(i) } 👉 for index in (0..<5){ print(index) }

Yes, I prefer spelling it out, but I know this one is contentious.


mnemonic phrase not visible

hey guys, i'm having trouble generating the mnemonic, everthing works fine but after i type it my password and confirm it the powershell window shrinks and says press any key after you have written down your mnemonic, but there's no words showing. it is blank. any thoughts?

Re-run the key generation code. There is a way to delete the old and create new.  I had the same problem when i first did it.


Dog Website Urban Collar

Description
Dog Website

Code of Conduct

[X] I follow Contributing Guidelines of this project.

/assign


Change URLs getAssemblyByChromsome... endpoints

I've been also thinking a lot about moving the /refseq/ part to a query param ?authority=refseq as suggested in the last refget call, and I think it makes sense, but let's do that in another PR.
Originally posted by @jmmut in https://github.com/EBIvariation/contig-alias/pull/41

v1/assemblies/{assemblyAccession}/chromosomes would be used for either genbank or refseq,but
v1/assemblies/{assemblyAccession}/chromosomes?authority=genbank or
v1/assemblies/{assemblyAccession}/chromosomes?authority=refseq would be used if the user knows which naming are they using


Walr2

Previously, the implementation of the "feature label dot product" only supported 1-bit features. We need to support more precision than that. This PR is intended to migrate to a multi-bit representation that's intended to be used to represent numbers between 0 and 1. For example, if using 8-bit values, they would represent the values 0/256 through 255/256.

I'm not sure I understand your intent for GenericArray and M. Is there some reason GenericArray makes sense here, but not for the main protocol?


Ms create test readme

I created a small script to generate a readme file within the graph_test_set folder that lists the descriptions of each test currently in the folder.
There is probably a smart way to get it to run each time we add or edit a test?
But for now we can just merge if we think it looks ok.

Btw marion - Really love the idea, it shouldn't be hard to implement that - We can create a githook so that everytime someone creates a PR the script auto-generates the readme (We already have that for the metadata-schema repo with the self-generation of human-readable schemas)

@ESapenaVentura sorry I have added the script properly now, I think that git doesn't add things in hidden folders i.e. .readme was being ignored when I git add *ed

The li


added rounded social buttons

Issue:

can u help me with this branch conflict?

@shahednasser

Please merge the newest changes from the master, as there are some conflicts that can't be resolved.

should i create another pull-request and close this one or can i just discard this conflicting file and create another commit
?

You can discard the conflicting file

creating this pull request again don't know what's happening

i just sae that the file which was conflicting had been removed from original sbuttons repository

so can u tell me if if need to do it all over again or will this request be merged as i had deleted the conflicting files.

You don't need to do it all over again. I'll look into your work and merge it if I find everything is ok!

ok do update me if there are issues you can discard this and i will do it again

It seems that you deleted the branch and unfortunately I can't see how the changes you made look like. Can you show me a screenshot of how it should be at least?

https://drive.google.com/file/d/17f-U46BcNgXi0kuxy7kZyCIsU8OestwK/view?usp=drivesdk
https://drive.google.com/file/d/17b0ZjAUGQwXiXkvAHoF4VBYm3OCwbG2O/view?usp=drivesdk

I will push these changes again and then you can check also the conflict was due to the file sbutton.min.css was deleted from main repository and i made a pull request before that

I meant a screenshot of how the buttons should look like. I can see the changes you made in code but since there's no repository, I can't clone it to see it in action

my code is deleted just give me some time maybe an hour or half i wil update them and then send you screenshots and then if you think about about changes you can tell me

You had removed that sbutton.min.css where should i put that code into?

Make sure your repo is up to date with this one, then just make changes in the less files and run "npm run compile". We don't need "sbuttons.min.css" anymore.

Here it is

Please  check these then after your approval i will push these changes

Looks great, but I think the font shouldn't change (should remain as it is now).
Please push the changes.


'make deb' and 'make rpm' are broken

to fix #59 they were moved. I can't fix them right now, but it would be great if someone did.

Hi ,
I'm still seeing the same issue while installing rtslib package.Is there any workaround or patch to resolve the error in building the rpm package?
make rpm
Exporting the repository files...
Cleaning up the target tree...
Fixing version string...
Generating rpm specfile from template...
Generating rpm changelog...
Generating debian changelog...
Generated release tarball:
dist/rtslib-fb-2.1.fb59.12.g845606a.tar.gz
Building rpm packages...
error: File /root/new/rtslib-fb/dist/rtslib-2.1.fb59.12.g845606a.tar.gz: No such file or directory
make: *** [build/rpm-stamp] Error 1

Thanks,
Ravindar

ok, I pushed a fix for make rpm. make deb is still broken until somebody wants to fix it.

Thanks Andy for your quick fix. We also see the similar error in compiling "configshell-fb".
make rpm
Exporting the repository files...
Cleaning up the target tree...
Fixing version string...
Generating rpm specfile from template...
Generating rpm changelog...
Generating debian changelog...
Generated release tarball:
dist/configshell-fb-1.1.fb19.1.g773dcad.tar.gz
Building rpm packages...
error: File /root/new/configshell-fb/dist/configshell-1.1.fb19.1.g773dcad.tar.gz: No such file or directory
make: *** [build/rpm-stamp] Error 1
[root@Ravindar configshell-fb]#

Hi Andy,
I have opened one new ticket to track the issue mentioned in my latest comment. If possible, Could you please review the configshell-fb code changes  attached in https://github.com/agrover/configshell-fb/issues/22 and let me know your inputs?
Thanks for your help in Advance!!
Thanks,
Ravindar


getResourceOwner parameter type

Hello,
Doesn't would be better to set the type of the $token parameter here to AccessTokenInterface instead of AccessToken?
https://github.com/thephpleague/oauth2-client/blob/8c7498c14959b98d4143a8ef91e895f353381628/src/Provider/AbstractProvider.php#L765
what do you think?
Thanks

While you are absolutely correct: it would be better to expect Interfaces and not specific implementations, it is to consider that this small change would require a new major release because it would break bacward compatibility, as it happened in the past (ref #753 and #752 for example).
And I highly doubt a new major release will be created only for this alone.


Optimize StyleBoxFlat.draw()

I'm not great at optimizing, but I needed this... I don't know which changes contributed most to the speedup, but resizing beforehand and the unfolding of the last nested loop seem like the primary two.
# Example of how I tested this
func _ready() -> void:
	var sbf := StyleBoxFlat.new()
	sbf.border_color = Color.RED
	sbf.set_corner_radius_all(4)
	var t := Time.get_ticks_msec()
	for i in 1000:
		sbf.draw(get_canvas_item(), Rect2(10, 10, 60, 20))
	print(Time.get_ticks_msec() - t)

Benchmarks:

Rounded stylebox: 205ms on master, 110ms in my PR (1.9x faster)
Stylebox with sharp corners: 75ms on master, 65ms in my PR (1.2x faster)

On production builds, on 4.3.beta2 I get 58ms on average, on this artifact I got 39ms on average.
This speedup should make stylebox drawing faster, for example if you draw hundreds of styleboxes in the same frame. It won't affect stylebox rendering after they have been drawn.

cc @davthedev

I'd suggest using ptrw to improve iteration if we're resizing

I'd suggest using ptrw to improve iteration if we're resizing

Not too familiar with pointers, but I think I got it? I got slightly better measures, but I don't think they are statistically-significant

Changing title as I discovered a notable speedup in drawing styleboxes in general.

I expected that some recent optimizations, like the Vector.insert() optimization, might change the benchmark. But I still measure the same 1.9x speedup for rounded styleboxes and 1.2x for all others.

Belated thanks! And oops I merged by mistake, I intended to wait for style fixes first. Can be done in a follow-up :)


pino cli discards not properly formatted log lines

When piping pino in the console, pino discards the lines that are not formatted exactly as it expects. Bunyan instead simply prints those line not formatted.
pull request: #95

Duplicate of #94


Occasionally: Screen dims and screen locks a little later

Steps to reproduce
Playback of a live stream, no user interaction, sometimes sleep mode is activated.
Expected behaviour
The screen does not dim down. Screen lock is prevented when the app is running in the foreground.
Actual behaviour
Screen dims and screen locks a little later.
Device: Samsung Galaxy A13 5G (SM-A136B/DSN)
Operating System: Android 14, One UI-Version 6.1
ZAPP: 8.5.2 (72)

The cause could be in a library used or in Android itself. I also observed the phenomenon under Zattoo.


React on 'return' key for dialogs

e.g.

Add database -> enter name -> hit enter
Options dialog (database connection) should react on hitting enter as well

Is there an issue for F5 to perform the "Refresh" in the Argon DB Connection view?

#7 was meant for things like F5 on the TreeView. Should add this by Swing API or should we hook into some Oxygen API?

You can use the swing way of adding key bindings using the tree component's action and input map.

:+1: noticed also the "Rename" dialog does not close on ENTER pressed

hope I got them all where it applies...


Nesting message redirection

Andrew Stacey at TeX.sx wishes to suppress xparse log messages locally.  The package can indeed be quite verbose at times, and packages built upon it may want to redefine some commands locally for whatever purpose, without shouting it at every juncture.  For instance, tikz could redefine a bunch of commands at each picture but we would not want to get one message per redefined command per picture.  Such a temporary redirection can be done easily by calling \msg_redirect_name:nnn within a TeX group.  However, in the context of defining commands, introducing a group may be troublesome, especially given that all xparse assignments are local.
The correct approach, I believe, would be to tie the global setting of which redirections are in place at any time to the LDB.  But this is not a short-term solution.
Short-term, I wish to add to l3candidates, with no prospect of moving to l3kernel, functions such as follows:
\msg_get_name_redirection:nnN { <module> } { <msg name> } \l_tmpa_tl
\msg_get_module_redirection:nnN { <module> } { <msg class> } \l_tmpa_tl
\msg_get_class_redirection:nN { <msg class> } \l_tmpa_tl

Alternatively, a less versatile, but probably more practical option all around would be to introduce
\msg_save_redirections:
\msg_restore_redirections:

Links to https://github.com/latex3/svn-mirror/issues/28


[$500] Routing number field is not auto focused.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.41-1
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: applause internal team
Slack conversation:
Action Performed:

go to workspace setting
Click on connect manually

Expected Result:
Routing number is autofocussed
Actual Result:
Not autofocussed
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/43996225/61cc5edf-5053-40a2-b842-d4f9bc9309da

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01c2f2f4d15d74aa10
Upwork Job ID:<PHONE_NUMBER>003891712
Last Price Increase: 2024-02-13

I think this is not a blocker, @MrMuzyk @barttom can address this as a follow up to the PR @akinwale @shubham1206agra

PR was CPed


Mulltiple exports

Hi there, thank you for your work
i just have a question is it possible to use mulltiple exports in a same tread?
like
Citizen.CreateThread(function()

    Ammunations = exports['bob74_ipl']:GetAmmunationsObject()
    BahamaMamas = exports['bob74_ipl']:GetBahamaMamasObject()

    -- add the details etc for both here
end)

Hi
Yes it shouldn't be a problem :)


Test CLI functions

Module cxflow.cli is tested only partially. Additional tests are required, especially for predict, resume etc.

Closing in favor of #101


version <IP_ADDRESS> not found in repo

[x] I have verified there are no duplicate active or recent bugs, questions, or requests
[x] I have verified that I am using the latest version of Material Dialogs.
[x] I have given my issue a non-generic title.
[x] I have read over the documentation (before asking questions on how to do something).

Include the following:

Material Dialogs version: <IP_ADDRESS>
Device OS version: 7.0.0
Device Manufacturer: ASUS
Device Name: Zenfone 3

Reproduction Steps
integration version <IP_ADDRESS>
not found in repo ?
Only <IP_ADDRESS> works

https://bintray.com/drummer-aidan/maven/material-dialogs%3Acore/<IP_ADDRESS>
https://bintray.com/drummer-aidan/maven/material-dialogs%3Acommons/<IP_ADDRESS>


Incorrect behaviour when used within admin

Currently, when used within the admin site, the upload behaviour does not display the percentage upload UI element correctly (it just displays a black bar), does not remove the percentage bar on error and cannot be used after an error occurs. One of the causes of these issues is that the native file selection button is still shown and is the means to trigger the upload behaviour.

looks like this is using the custom template from platform, have the custom scripts been ported across as well?


Readthedocs setup

Hi, here is the guide you need to follow to publish the Sphinx docs: https://docs.readthedocs.io/en/stable/tutorial/
EDIT: Just installing the webhook should be enough, I'll take care of the rest.
then the link in the readme needs to be adjusted.

@tristanlatr  Thanks for your instructions in the email. Now the webhook  has been created

I now close this issue but will  give regular attention to the readdocs work.  Thanks for the great help!


Font changes

Increased font sizes to take up more space, changed colors (of links)to be more noticeable, and boldened section headers

Looks good, I like the new colors for the links


Node projects with --lib es6: cannot find name 'console'

TypeScript Version: nightly (2.0.0-dev.20160706)
Code
// Before compiling: npm install @types/node
// Compile options: { "lib": ["es6"], "types": ["node"] }
process.cwd();          // OK
console.log('testing'); // ERROR: Cannot find name 'console'

Expected behavior:
Compiles without errors
Actual behavior:
console is not defined
More Info:
node.d.ts does not contain a definition for the global console instance or for the Console class. References to console are resolved against the definitions from lib.dom.d.ts. But now with the --lib option, Node projects can opt out of the ambient DOM typings. That brings up the problem that console is not defined.
It's not as simple as just copying the ambient console and Console definitions from lib.dom.d.ts into node.d.ts, because in browsers the Console constructor is globally available but in Node it is not. 'Hiding' Console under the NodeJS namepace in node.d.ts wont work either because then projects that don't use the --lib option will get conflicting DOM and Node definitions and will see the error TS2403: Subsequent variable declarations must have the same type.  Variable 'console' must be of type 'Console', but here has type 'Console'.
I'm testing out changes to node.d.ts that will work both with and without --lib, and will submit a PR to DefinitelyTyped if I can get it working.

Looks like a definition bug in nose.d.ts

PR on DefinitelyTyped: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/9998

How to resolve this problem?

@frogcjn if you get your node typings using npm install @types/node, you'll have the updated node.d.ts that includes the Console definitions.

thanks @yortus

This seems to have caused this bug:
https://github.com/Microsoft/TypeScript/issues/13204

tsconfig , lib property add "dom"

thanks @gatspy

thanks @gatspy ,it works!

@gatspy thanks


mdbx_cursor_set: do not pass exact where not necessary

Thanks for contribution and pointing me to this.
However, I decided to fix it differently.


Overlappograms should be in DN

When mapping photons from the spectral cube to the detector plane through Poisson sampling, the photons should first be converted to DN. That is, the weights of the resulting histogram should add in DN space while the sampling should continue to be done in photon space.

This will involve fixing the step in mapping the sampled photons to the detector plane.

The project_spectral_cube now includes a flag for converting to DN before projecting down.


add stride to patch embed3d

Codecov Report

Merging #1228 (bfd1527) into main (d7f4ae8) will decrease coverage by 0.05%.
The diff coverage is 28.57%.

@@            Coverage Diff             @@
##             main    #1228      +/-   ##
==========================================
- Coverage   68.50%   68.45%   -0.06%
==========================================
  Files         252      252
  Lines       12228    12232       +4
  Branches     2030     2033       +3
==========================================
- Hits         8377     8373       -4
- Misses       3319     3325       +6
- Partials      532      534       +2

Impacted Files
Coverage Δ

...s/video_swin_transformer/video_swin_transformer.py
44.54% <ø> (ø)

towhee/models/layers/patch_embed3d.py
60.46% <28.57%> (-6.21%)
:arrow_down:

towhee/dataframe/dataframe.py
73.10% <0.00%> (-1.05%)
:arrow_down:

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 d7f4ae8...bfd1527. Read the comment docs.


Py311 upgrade

Description of proposed changes
Remove support for deprecated versions of Python (3.6, 3.7, 3.8) and add support for Python 3.11.
Related issue(s)
Fixes # (issue)
Test plan
Update automated tests to run with new Python version
Checklist
Need help on these? Just ask!

[x] I have read the CONTRIBUTING document.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] I have run tox -e complex and/or tox -e spark if appropriate.
[x] All new and existing tests passed.

@bhancock8 super thrilled with the realease :)


fluentbit is not catching an logs with docker (even with the example on the docker hub page)

I went throught the official docker_hub page and tried the example to test fluentbit with an ubuntu docker image here: https://hub.docker.com/r/fluent/fluent-bit/
unfortunatly, I see nothing here catched by fluentbit.
running:
docker run -p <IP_ADDRESS>:24224:24224 fluent/fluent-bit:latest
followed by:
docker run --log-driver=fluentd -t ubuntu echo "Testing a log message"
displays nothing on the fluentbit output in the console.
am I missing something here, or is the page outdated ?
I was trying fluentbit with an nginx container in a docker-compose file to catch nginx logs and it did not work, so I started from 0 with the official documentation on the docker_hub web page.
Here is my docker-compose.yml
version: '3.2'
services:
  nginx:
    container_name: nginx
    image: nginx:1.15.0
    ports:
      - 7070:80
    links:
      - fluentbit
    logging:
      driver: "fluentd"
      options:
        fluentd-address: <IP_ADDRESS>:24224
        tag: nginx.access

  fluentbit:
    container_name: fluentbit
    image: fluent/fluent-bit:1.3
    ports:
      - "24224:24224"
      - "24224:24224/udp"

@Fettah Solution in https://github.com/fluent/fluent-bit-docker-image/issues/11 seems to work.


Major changes for new Teams 1.0 release

Pull Request (PR) description
Update resources to support Teams 1.0.0 cmdlet release
This Pull Request (PR) fixes the following issues
- Fixes #96

-->

Codecov Report

Merging #100 into Dev will decrease coverage by 0.46%.
The diff coverage is 97.43%.

@@            Coverage Diff             @@
##              Dev     #100      +/-   ##
==========================================
- Coverage   89.95%   89.48%   -0.47%
==========================================
  Files          40       36       -4
  Lines        3007     2806     -201
==========================================
- Hits         2705     2511     -194
+ Misses        302      295       -7

Impacted Files
Coverage Δ

...SC/DSCResources/MSFT_TeamsTeam/MSFT_TeamsTeam.psm1
98.07% <97.43%> (+3.63%)
:arrow_up:

Continue to review full report at Codecov.

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


ART-2134: add prepare-release job

This job will perform an assortment of weekly release tasks for creating a release from scratch. The job needs to know:

the expected release name (e.g. 4.6.42)
expected release date
proposed nightlies for each arch

The tasks for preparing a release are:

create advisories for a release (notify docs team to create live ids)
record advisory numbers to ocp-build-data.
freeze automation
create a release JIRA
sweep bugs and builds into the advisories
verify the swept builds match the nightlies (verify-payload)
notify QE teams (mainline and multiarch) about the proposed nightlies, advisories, and Jira

Notes for reviewers

The pipeline is implemented in Python (rather than calling existing Jenkins jobs), and the Jenkinsfile just takes job parameters, execute the python script, and save artifacts in the workspace.
To make the JIRA automation easier, I've updated the templates https://issues.redhat.com/browse/OCPPLAN-4756 and https://issues.redhat.com/browse/OCPPLAN-1373 to follow Jinja2 format.
Job parameters are minimum. Options rarely changing are stored in config/artcd.toml.
This is my test build: https://saml.buildvm.openshift.eng.bos.redhat.com:8888/job/hack/job/yuxzhu/job/aos-cd-jobs/job/build%252Fprepare-release/19/console (it failed at the second last step because the complained images was removed from ocp-build-data but still exists in image streams, otherwise it would pass)
Example command for running manually (add --dry-run if you don't really want to prepare a release):

# set credentials
$ kinit
$ oc login api.ci.openshift.org
$ oc registry login
$ docker login quay.io
$ bugzilla login --api-key
$ export JIRA_USERNAME=<your-jboss-jira-username> JIRA_PASSWORD=<your-jboss-jira-password>

# run the pipeline
$ pyartcd/prepare_release.py -vv --working-dir=./pyartcd_working --config=./config/artcd.toml 4.2.42 --package-owner<EMAIL_ADDRESS>--date 2020-Dec-09 --package-owner<EMAIL_ADDRESS>--nightly 4.2.0-0.nightly-2020-11-05-133907 --nightly 4.2.0-0.nightly-s390x-2020-11-05-133855

I reordered some steps comparing with the existing jobs. Please take a look and see if the order is reasonable.

docs https://github.com/openshift/aos-cd-jobs/pull/2438


Handling multiple He3 cells?

@astellhorn mentioned that He3 cells may be switched out during an experiment. However, in the basics workflow defined in #3 we have assumed that we have a single set of parameters such as He3Pressure and He3FillingTime.
If my understanding is correct then we need to generalize this, adding e.g., a cell identifier to compute, e.g., a cell-dependent He3Opacity. This would however imply that we need to perform independent fits, i.e., we also get a cell-dependent He3Transmission. For the full run we would then have to concatenate multiple such time-dependent decay functions (or handle the entire data reduction independently when switching to a new cell).

I try to also catch this in an over view slide with the other DB background measurements

We should use filling time, cell pressure, and cell length (recorded in NeXus) file to identify if the same cell is used for a run (ideally also cell ID).
Given a collection of runs and based on above params (read from each run) we can categorize the runs into runs for different cells.
For each cell, we can then, e.g., load all direct-beam runs (or run sections) and perform a fit to obtain the time-decay of the transmission.
Finally, we can correct the sample data. Merging of runs for different cells can be performed after or before the correction. If before the correction, we also merge the transsmission time decays obtain from the separate fits.


SRS Review #9

@karolserkis
Please correct this sentence "Nevertheless, the intended reader is expected
to have a basic knowledge in mathematics (calculus, dierentials/ODEs) and physics (kinematics, energy potential, Lagrangian, Poincare mapping) is recommended to get a deeper
understanding of the document.".
My guess is that you should remove "is recommended" alone to make it right.

@Malavika-Srinivasan @smiths
Thanks!


make usable from Objective-C code

Allow using the logger in Objective-C code:
@import AlamofireNetworkActivityLogger;

// ...
    [[NetworkActivityLogger shared] startLogging];
    [NetworkActivityLogger shared].level = NetworkActivityLoggerLevelDebug;

@yonat I think this is not a good idea to make it Objective-C compatible, since Alamofire is Swift only. It seems that you'll have to keep that compatibility in some kind of wrapper in your code. That's what people do when they want to use Alamofire in Objective-C.

I have a mixed project, and don't need to call Alamofire from Objective-C. But the global inits (and test/debug flags) are in Objective-C, and so i need to access AlamofireNetworkActivityLogger from Objective-C.
Don't know if this is a common use case, but that what I'm facing.


Issues on uploaded windows-binaries for v0.3.0

When trying to build the Docker Windows container from the binaries in the release, there seems to be communication issues between the client library and the service. Using the service in standalone mode also reports issues.
This does not happen with the Linux binaries. It only affects the Windows binaries.
Workflow showing the problema can be found here:
https://github.com/ansys/pyansys-geometry/actions/runs/6123669671

Issue seems to be solved - for now

Will require a new release

Problem solved. Pipelines will now verify prior to doing the release that the binaries are working fine. Closed by #709


Use http 1.1, server has misconfigured http 2 setup

Error message when not specifying protocol version (=> will use http 2):
07:51:23 curl: (92) HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)
07:51:23 sentinel-254488> exit code: 92
07:51:23
07:51:23 ERROR: Command 'curl -L -o img_emb_0000.npy  https://the-eye.eu/public/AI/cah/laion5b/embeddings/laion2B-en/img_emb/img_emb_0000.npy' returned code 92
07:51:23

@jobergum or @kkraune please take a look

Wow, thanks!


Can I use this tool to migrate content from on-prem Sharepoint 2013 to on-prem Sharepoint 2013 ?

Hi, i need to migrate one on-prem SP 2013 site collection few content (about 1TB) to another new site.  Can i use this tool to perform the migration?

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

ID: 36d01d11-eea9-7f49-693d-25c3fecc6253
Version Independent ID: 6749a619-2b75-1561-81e9-b45888c58c4b
Content: How to use the SharePoint Migration Tool
Content Source: migration/how-to-use-the-sharepoint-migration-tool.md
Product: sharepoint-server-itpro
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

@raymondhahs Thank you for submitting feedback. We are currently investigating this.

@officedocsbot assign @scanum

@raymondhahs thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products: https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

@officedocsbot close


Is there a way to do a PATCH of an entity?

Hello,
I was trying to update a single attribute of an entity but I just see update or save and they send all the attributes of the object in the payload. For example it would be nice to have something like:
remult.repo(MyEntity).patch(id, {isActive: true});
Thank you

I think that update will do exactly that:
remult.repo(MyEnity).update(id, {isActive:true})

Another option is change a member and send the update:
let myEntity = remult.repo(MyEntity).findFirst()
myEntity.isActive=true
remult.repo(MyEntity).save(myEntity)

I tried and it works, just the HTTP method is a PUT instead of a PATCH, but it does the job.

@noam-honig Is update supposed to keep all fields that are not specified intact? It seems to me that in some circumstances other fields get overwritten (perhaps primitive types and/or allowNull?). Indeed, in the PUT network request some other fields (not specified in the second parameter of update) are specified with null values.

@groszdaniel yes - unspecified fields shoud stay intact. If not, it's a bug and I would like to fix it.
Can you give me some information on how to reproduce it?

@noam-honig I made a simple example based on the React starter project: https://github.com/groszdaniel/remult-update-bug
One entity, two integer fields, each button is supposed to increment one without touching the other. Instead, when one is incremented, the other becomes 0. In the network request, you can see that a 0 is sent for the unspecified field. (Not in the example, but strings are set to an empty string, for instance.) The allowNull option doesn't actually matter.
If you fix this, I suggest also updating the documentation to make it clear that it's allowed to only specify some fields. Currently, all examples specify unchanged fields like this:
repo.update(id, { ...foo, field: value })
That's why it wasn't clear to me if it was a bug that other fields are zeroed, or intended behavior. The ...foo is currently necessary, but it should be superfluous if the bug is fixed.

Thanks. I'm out of town, will look at it tomorrow

Sorry about that, this issue was already fixed in version:
https://github.com/remult/remult/releases/tag/v0.22.4
My bad for not updating the starter kit - will do that now


Plugin must provide a way to distinguish between graphic and movieclip.

A parameter "loop" will be set to true/false for movie-clip and graphic respectively. This parameter will be along with the "Place" command.