HOdlcoin generates wrong deposit addresses

HOdlcoin addresses start with H

This is caused by the HODL Komodo asset chain using the same ticker as Hodlcoin. We have HODLC as the ticker for Hodlcoin in our config, however it looks like at some point they changed to HODL: https://coinmarketcap.com/currencies/hodlcoin/
	{
		coin: 'HODL',
		asset: 'HODL',
		rpcport: 14431,
		electrumServers: [
			{
				host: 'electrum1.cipig.net',
				port: 10009,
			},
			{
				host: 'electrum2.cipig.net',
				port: 10009,
			},
		],
	},
	{
		coin: 'HODLC',
		name: 'Hodlcoin',
		rpcport: 11989,
		pubtype: 40,
		p2shtype: 5,
		wiftype: 168,
		txfee: 5000,
		electrumServers: [
			{
				host: 'hodl.amit.systems',
				port: 17989,
			},
			{
				host: 'hodl2.amit.systems',
				port: 17989,
			},
		],
	},

You can actually currently use both, HODLC will give you the correct address:

@sindresorhus I think the only reasonable solution here is to remove one. Ticker symbols should be unique. We shouldn't bend over backwards to support coins that don't check if the ticker symbol they want to use is free or not. Thoughts?

ah alright, thanks for explaining it.
also, HODLcoin (hodlc) is on the market since 2016, not sure what about the Komodo asset.

No problem, thanks for letting us know, good catch.
Are you aware if they recently changed their ticker to HODL?

I have no idea :/

A solution could be changing the Komodo asset one name to HODL instead of HOdlcoin, and keeping the ticket the same as it is now

Btw @sindresorhus if you tackle this for a new release. Can you check if users have trade history containing HODL or HODLC and then we completely remove the currencies if it breaks anything. I think it will, as we won't auto request the CMC prices for them anymore.

A solution could be changing the Komodo asset one name to HODL instead of HOdlcoin, and keeping the ticket the same as it is now

That's a nice solution visually, but under the hood all our code relies on the ticker symbols being unique to be able to differentiate between currencies. That's what's causing the current issues with duplicate name and USD price.
We will probably try to get some custom logic that handles cases like this to make it appear visually they are using the same ticker but still have different tickers under the hood.

Uh alright, understandable

Is the Komodo 'HODL' asset still live? If so where can I get more information?
If it is now defunct, I'd suggest removing it and using HODL as the ticker for HOdlcoin. HOdlcoin has always used this ticker, and is listed on CoinMarketCap, CoinExchange and Yobit(insolvent).

https://github.com/particle4dev/hyperdex/issues/13 HODLC coin removed


cmake: detect libc location at runtime

Description of changes
This PR updates the patch to Modules/Platform/UnixPaths.cmake to detect the libc location at runtime, based on the cc-wrapper specified in $NIX_CC. If $NIX_CC is not (or incorrectly) set, it falls back to the original behavior (ie.: use the libc that was used to build CMake itself).
This allows CMake to automatically pick up an alternate libc in package builds. The alternative would be to do something like -DCMAKE_SYSTEM_INCLUDE_PATH=${stdenv.cc.libc_dev}/include in every package build that wants a different libc.
This may sound niche, but I suspect may become a more common thing on Darwin as the option to use different macOS SDKs becomes available. #176661 was recently merged, making a second SDK available for x86_64-darwin by doing darwin.apple_sdk_11_0.callPackage ./my-package { }, which also swaps in a different stdenv with a different version of libSystem.
I'm specifically working on the Swift build on Darwin, which is picking up the wrong libSystem in a couple of places. A simple one is a call to find_package(Backtrace), which does a find_path(Backtrace_INCLUDE_DIR "execinfo.h"). Both calls can be easily tested in isolation.
Besides that, I also tested rebuilding fish on Linux with this change in place on master. Fish uses CMake, and apparently also pulls in a handful of CMake-using deps. That all worked fine and produced a working build.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I've now also successfully tested building and running fish on Darwin with this change on master, which includes the stdenv rebuild.

Caveat: I have very little understanding of how darwin packaging works.
Do I understand it correctly you are planning to use cmake (and a bucnh of other packages) built against one libc to build a few select packages against another libc? Is it typical on darwin to do such a thing? Or do people usually build the whole world with one SDK?

darwin.apple_sdk_11_0.callPackage ./my-package { }

What does it do? Does it only substitute stdenv (and a few darwin-specific packages) just for this package? Or does it apply the same for all it's dependencies? I suspect it's the former and cmake is only the first example of the breakage. AFAUY ideally you somehow need it to be propagated to all the packages who care. glibc/musl or libstdc/libc++ (to pick an extreme) do it via pkgs/pksMusl or pkgs/pkgsLLVM to ensure consistent environment.
Would something like that work for darwin?

Do I understand it correctly you are planning to use cmake (and a bucnh of other packages) built against one libc to build a few select packages against another libc? Is it typical on darwin to do such a thing? Or do people usually build the whole world with one SDK?

This is recent. It used to be Intel was built with the 10.12 SDK, and Apple Silicon was built with 11.0 SDK. The recent change is to opt-in per-package into the 11.0 SDK on Intel too.
What that means technically is also something I'm not an expert on. For example, libc on darwin is typically injected at run-time, so I imagine despite linking against different libcs, they use the same at run-time. I imagine that also applies to many frameworks provided by Apple (sans injection), but maybe there are some exceptions for the ones we have source. I'm really speculating here, because I don't know the specifics. 🙂
In practice this PR may not necessarily be darwin specific. It's about about using cmake to build with a different libc, without having to rebuild cmake itself.

darwin.apple_sdk_11_0.callPackage ./my-package { }

What does it do? Does it only substitute stdenv (and a few darwin-specific packages) just for this package? Or does it apply the same for all it's dependencies? I suspect it's the former and cmake is only the first example of the breakage. AFAUY ideally you somehow need it to be propagated to all the packages who care. glibc/musl or libstdc/libc++ (to pick an extreme) do it via pkgs/pksMusl or pkgs/pkgsLLVM to ensure consistent environment.
Would something like that work for darwin?

I do feel that a separate callPackage has limitations (and layer violations), but I'm not sure who is making those decisions.
The relevant part of that special callPackage for this PR is:
let
  clang = stdenv.cc.override {
    bintools = stdenv.cc.bintools.override { libc = packages.Libsystem; };
    libc = packages.Libsystem;
  };
in
  overrideCC stdenv clang;

But yes, it overrides specific packages (beyond stdenv), and all the Apple frameworks. See: pkgs/os-specific/darwin/apple-sdk-11.0/default.nix
I don't believe it recurses into dependencies.

Sorry, I rushed the last comment a bit, and made some small edits to it just now.
I think a relevant previous comment is https://github.com/NixOS/nixpkgs/pull/176661#issuecomment-1176864082, quoting:

I tried a PoC pkgsApple.sdk_<version>, but that didn’t work. It requires a lot of rebuilds, which broke in a few places (see my comments on Matrix). I also fear it would result in tons of extra packages built by Hydra that wouldn’t be used.

I can't easily find the Matrix discussion mentioned, unfortunately.
From what I can tell, a pkgsMusl or pkgsLLVM is there for the user to specifically request an alternate build of some package? Whereas what we want here is to simply have a working nix-env -iA go on Darwin (and the user shouldn't have to care what SDK is used.)
Whether we do apple_sdk_11_0.callPackages or pkgsApple.sdk_11_0, we need to have pkgs.go somehow annotated to use the newer SDK. When I said limitations / layer violations, what I meant is that the current callPackages solution does not combine, afaict. (ie.: hypothetically, if another platform needs a similar solution, I don't believe we can stack the two.)
For a pkgsApple-type solution, I guess we'd need some way to do similar annotation in all-packages.nix, but I'm not sure what that'd look like. (For example, a simple go = pkgsApple.sdk_11_0.go is recursive.)
Another difference is that a pkgsApple annotation probably only makes sense when applied to end-user applications, whereas callPackages allows building individual libraries with different SDKs. (I think that answers your question about mixing packages?)
So, there is I think good reason to at least prefer callPackages over pkgsApple. I wonder if we can slowly tackle all the breakages like this PR? (Another darwin-specific example I know of is xcbuild, which is currently also tied to whatever SDK it was built with. That's why it's also currently part of the set overridden by callPackages.)
I wonder if we can maybe even reduce the amount of overrides to just be limited to the darwin.* namespace, so we could potentially drop callPackages and replace it with a simple // optionalAttrs stdenv.isDarwin darwin.pkgs_11_0 (which does combine). But that's probably wishful thinking, as https://github.com/NixOS/nixpkgs/pull/180931 is currently set to expand the overrides.
P.S.: In an ideal world, I believe that we'd always use the latest SDK and set -mmacosx-version-min (the "deployment target") to the oldest version we want to support. But we don't, and I guess that's because it doesn't work well in practice?

Whether we do apple_sdk_11_0.callPackages or pkgsApple.sdk_11_0, we need to have pkgs.go somehow annotated to use the newer SDK. When I said limitations / layer violations, what I meant is that the current callPackages solution does not combine, afaict. (ie.: hypothetically, if another platform needs a similar solution, I don't believe we can stack the two.)
For a pkgsApple-type solution, I guess we'd need some way to do similar annotation in all-packages.nix, but I'm not sure what that'd look like. (For example, a simple go = pkgsApple.sdk_11_0.go is recursive.)

Yeah, pkgs* are more like cross-targets that assume pkgs already works. I agree pkgsApple would not make default case simpler. At beast it would help building parallel world with non-default SDK.

Another difference is that a pkgsApple annotation probably only makes sense when applied to end-user applications, whereas callPackages allows building individual libraries with different SDKs. (I think that answers your question about mixing packages?)

Yeah. That makes sense.

So, there is I think good reason to at least prefer callPackages over pkgsApple. I wonder if we can slowly tackle all the breakages like this PR? (Another darwin-specific example I know of is xcbuild, which is currently also tied to whatever SDK it was built with. That's why it's also currently part of the set overridden by callPackages.)

Would putting cmake override along with xcbuild also be ~ok? AFAIU it should Just Work without patching if built against stdenv with modified SDK (and everything else required). That would make me a bit less nervous.

P.S.: In an ideal world, I believe that we'd always use the latest SDK and set -mmacosx-version-min (the "deployment target") to the oldest version we want to support. But we don't, and I guess that's because it doesn't work well in practice?

Do @NixOS/darwin-maintainers have a vision how things should be laid out in multiple SDKs world? Reading https://github.com/NixOS/nixpkgs/issues/101229 AFAIU we normally expect only one default SDK. That is somewhat similar to linux stdenv that defaults to a single current compiler (and attempts to use something else frequently breaks when too old libstdc++ gets pulled in).

It was my understanding that Go 1.18 is already being built with the 11.0 SDK, and Go 1.18 is the default in unstable. Is there additional context I’m missing? (I’m aware some packages still have problems building, but I believe that’s due to https://github.com/golang/go/issues/51091).
Regarding cmake: I added cmake to callPackages in #180931, which is blocked due to needing updates to the bootstrap-tools on x86_64-darwin. The changes for that were in #181550, which has been merged, but stdenvBootstrapTools is not building on Hydra currently. I believe #182058 is attempting to fix that. After all that is done, and I go through the process of updating the bootstrap tools, then I can move #180931 forward.
Regarding the SDK: As I understand it, the default SDK on x86_64-darwin is 10.12. Making the 11.0 (and eventually newer) SDKs available was meant to be an escape hatch for when packages don’t build on the default SDK (my motivating example being MoltenVK, but Go and some other packages also wouldn’t build on the 10.12 SDK). Meaning, if packages can build with the 10.13 SDK once the SDK is bumped, those packages should be reverted to the default stdenv.

I don't know anything about cmake, so I can't review the code change, but I've been thinking about this exact issue in our build tooling more broadly, have started a discussion here: https://github.com/NixOS/nixpkgs/issues/185742.
I completely agree with the approach of detecting libc at runtime, though I would prefer if it was done with a mechanism that isn't nix specific.

Okay then!

This PR broke a build: https://hydra.nixos.org/build/187642932

That is probably a pkgsLLVM.llvmPackages.compiler-rt:
CMake Error at /nix/store/xjg2fzw513iig1cghd4mvcq5fh2cyv4y-cmake-3.24.0/share/cmake-3.24/Modules/Platform/UnixPaths.cmake:53 (file):
  file STRINGS file
  "/nix/store/4hiy0nfv99gsfc1hyss3rcl3sn6panmc-x86_64-unknown-linux-gnu-clang-wrapper-11.1.0/nix-support/orig-libc-dev"
  cannot be read.

Where we fail to read orig-libc-dev. /cc @stephank

orig-libc-dev is not yet there. My guess is that it's a bootstrap $CC without libc support and it can't yet produce executable binaries:
$ ls /nix/store/4hiy0nfv99gsfc1hyss3rcl3sn6panmc-x86_64-unknown-linux-gnu-clang-wrapper-11.1.0/nix-support/
add-flags.sh  add-hardening.sh  add-local-cc-cflags-before.sh  cc-cflags  cc-ldflags  orig-cc  propagated-build-inputs  setup-hook  utils.bash

$ nix develop -i /nix/store/73cdvx5gzdmbgva41b6my2hzzs3cnxvw-compiler-rt-x86_64-unknown-linux-gnu-11.1.0.drv
$$ dev>printf "int main(){}" | $CC -x c - -o a
x86_64-unknown-linux-gnu-ld: error: unable to find library -lgcc
x86_64-unknown-linux-gnu-ld: error: unable to find library -lgcc_s
x86_64-unknown-linux-gnu-ld: error: unable to find library -lc
x86_64-unknown-linux-gnu-ld: error: unable to find library -lgcc
x86_64-unknown-linux-gnu-ld: error: unable to find library -lgcc_s
clang-11: error: linker command failed with exit code 1 (use -v to see invocation)

Proposed possible fix by falling back to old mechanism if libc bits are not present in nix-support directory: https://github.com/NixOS/nixpkgs/pull/187773


Added accessibility support for all adaptive card elements

React-Native SDK Accessibility Support
Added accessibility support for all adaptive card elements such as image, media, actions, various input types, and containers. Please find below the property details.

Property name - altText
This text will be treated as a description of the particular element/container.

Microsoft Reviewers: Open in CodeFlow

LGTM

LGTM


feat: dhke

Signed-off-by: Berend Sliedrecht<EMAIL_ADDRESS>

Maybe we could add some form of testing for this?

Ill test it with the integration.


Item Frames incorrect placement

This looks like a job for me! Call in, the A Team!

Can't test this in newer verisons.

Can't test this in newer verisons.
w h a t

Item frames don't place.


Crashing Tick Loop

Mod Loader
forge-36.2.34
Mod version
Goety-1.36.1
Issue description
Whenever using an Arca to save myself either as human or lich, the server will crash instantly, when using a empty cage and a fire cage to make a spawner the server will crash just the same, While using the teleport focus to an Arca will only disconnect me and the server is fine.
I thought it could be a mod confliction so I tried recreating the events in a server with only Goety and it’s dependent mod curious. The crash happened again although unlike before I didn’t get a crash report.
So far I’ve had to disable arca from saving you just to use it and I hope there’s a way to fix it.
 For the fire cage I simply just right clicked a fire cage on a empty cage and it crashed.
Additional information
I am using aternos. Aswell for the fact this happens with no other mods but Goety, only difference being is that with my modpack I get a crash report while with Goety alone I don’t, I also don’t have this issue in single player

Should be fixed as of latest update!


Tap not working on Mobile (iOS)

Hi!
I'm having some trouble using react-typeahead-component on mobile devices namely iOS (iPhone 4S, iPad 2) devices with Chrome.
When I try to select the input, nothing happens. It seems that the input that gives the typeahead look is getting the focus event instead of the actual input where the user needs to write.
I was able to reproduce this using your Youtube example: http://ezequiel.github.io/react-typeahead-component/youtube/
Any ideas on how to fix this?
Cheers!

Hey @jpsfs, thanks for the feedback. I will try to fix this.

Hi @ezequiel, thank you for looking into to it.
I've done some more tests and it's definitely related with both inputs being on top of each other.
From what I've seen from other examples (ex: https://twitter.github.io/typeahead.js/) they put the hint input first and with position: absolute;. From what I've seen with your component, you go the other way around.
Changing this fixed this bug but the dropdown seems not to be working after these changes. I'm not familiar with all the source of react-typeahead-component, so probably after changing the order some other things need to be changed also.
I hope this gives you a little more insight about the issue. Please let me know if I can be of some assistance.
Best regards,

@jpsfs
Thanks for your investigation! I was able to use the idea you presented, and it indeed works. I've pushed the fix in release 0.6.0.
There's just one more issue I've found though: once the dropdown opens, touching one of the list items doesn't do anything... tricky. I may need some help with this one.

@jpsfs
This seems to be part of a bigger problem on mobile browsers (Safari, at least). Click events don't work as expected. React has acknowledged this, and recently merged a fix. See issue https://github.com/facebook/react/issues/1169 and pull https://github.com/facebook/react/pull/1536.
Apparently, adding cursor: pointer to the item fixes the clicking-on-item issue.


[Feature] Pretrained model?

分支
1.x 分支 (1.0.0rc2 或其他 1.x 版本)
描述该功能
I see that moblinetv3 only provides a pre-trained model of 1.0. Can you provide more pre-trained models with different scaling factors of 0.75 and 0.5?
是否希望自己实现该功能？

[ ] 我希望自己来实现这一功能，并向 MMClassification 贡献代码！

Sure, we will add more pretrains of 0.75 with priority, since official has only released 1.0 and 0.75.
0.5 needs to trained from scratch, hence will be considered in the future.

refers to https://github.com/open-mmlab/mmclassification/pull/1154, update with branch dev-1.x for more pretrains,


When logged out, user_info() doesn't have an email attribute

Is currently broken on production. Quick fix is to just do a hasattr
Full details inside
AttributeError:

AttributeError: 'TheUser' object has no attribute 'email'
In field index number 6

Traceback (most recent call last):
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 7978, in assemble
    exec_with_trap(question, user_dict)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 9329, in exec_with_trap
    exec(the_question.compute, the_dict)
  File "", line 1, in
NameError: name 'intro' is not defined

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 6090, in ask
    defaults[field.number] = eval(from_safeid(field.saveas), user_dict)
  File "", line 1, in
NameError: name 'panel_email' is not defined

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 6093, in ask
    defaults[field.number] = user_dict['_internal']['dirty'][substitute_vars(from_safeid(field.saveas), self.is_generic, the_x, iterators)]
KeyError: 'panel_email'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/flask/app.py", line 1523, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/flask/app.py", line 1509, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/webapp/server.py", line 8058, in index
    interview.assemble(user_dict, interview_status, old_user_dict, force_question=special_question)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 8259, in assemble
    raise the_error
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 8046, in assemble
    question_result = self.askfor(missingVariable, user_dict, old_user_dict, interview_status, seeking=interview_status.seeking, follow_mc=follow_mc, seeking_question=seeking_question)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 8744, in askfor
    return question.ask(user_dict, old_user_dict, the_x, iterators, missing_var, origMissingVariable)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 6097, in ask
    defaults[field.number] = field.default.text(user_dict).strip()
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 1503, in text
    return self.template.render(**the_user_dict)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/mako/template.py", line 451, in render
    return runtime._render(self, self.callable_, args, data)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/mako/runtime.py", line 828, in _render
    _render_context(template, callable_, context, *args,
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/mako/runtime.py", line 864, in _render_context
    _exec_template(inherit, lclcontext, args=args, kwargs=kwargs)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/mako/runtime.py", line 890, in _exec_template
    callable_(context, *args, **kwargs)
  File "memory:0x7fb6d11ce950", line 23, in render_body
AttributeError: 'TheUser' object has no attribute 'email'

The referer URL was https://apps.suffolklitlab.org/run/209a/

Traceback (most recent call last):
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 7978, in assemble
    exec_with_trap(question, user_dict)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 9329, in exec_with_trap
    exec(the_question.compute, the_dict)
  File "", line 1, in
NameError: name 'intro' is not defined

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 6090, in ask
    defaults[field.number] = eval(from_safeid(field.saveas), user_dict)
  File "", line 1, in
NameError: name 'panel_email' is not defined

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 6093, in ask
    defaults[field.number] = user_dict['_internal']['dirty'][substitute_vars(from_safeid(field.saveas), self.is_generic, the_x, iterators)]
KeyError: 'panel_email'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/flask/app.py", line 1523, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/flask/app.py", line 1509, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/webapp/server.py", line 8058, in index
    interview.assemble(user_dict, interview_status, old_user_dict, force_question=special_question)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 8259, in assemble
    raise the_error
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 8046, in assemble
    question_result = self.askfor(missingVariable, user_dict, old_user_dict, interview_status, seeking=interview_status.seeking, follow_mc=follow_mc, seeking_question=seeking_question)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 8744, in askfor
    return question.ask(user_dict, old_user_dict, the_x, iterators, missing_var, origMissingVariable)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 6097, in ask
    defaults[field.number] = field.default.text(user_dict).strip()
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 1503, in text
    return self.template.render(**the_user_dict)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/mako/template.py", line 451, in render
    return runtime._render(self, self.callable_, args, data)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/mako/runtime.py", line 828, in _render
    _render_context(template, callable_, context, *args,
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/mako/runtime.py", line 864, in _render_context
    _exec_template(inherit, lclcontext, args=args, kwargs=kwargs)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/mako/runtime.py", line 890, in _exec_template
    callable_(context, *args, **kwargs)
  File "memory:0x7fb6d11ce950", line 23, in render_body
AttributeError: 'TheUser' object has no attribute 'email'

The external hostname was apps.suffolklitlab.org

Unfortunately, this is happening even when the field itself asking for the email is turned off, I guess because DA evaluates the mako templating of the question before the code is evaluated. No other way to fix other than the hasattr


Does it support build for edge runtime?

Hello!
No, at this moment tramvai doesn't support Vercel edge runtime, or any other serverless environments.
Our framework setup fastify server, heavily integrated into the Dependency Injection system.
So, on the one hand, tramvai application lost the ability to be just a function like (request, response) => HTML.
But from the other hand, this approach has a lot benefits:

You don't need to care, how render React on server or client (compared to Remix, for example)
You have solid server metrics "out of the box", and can easily add custom metrics
server lifecycle are part of application lifecycle, and by using CommandLineRunner, you can for example run some other server for static assets or for requests mocking simultaneously with the application server (both of this cases already implemented in tramvai modules)
tramvai modules, thanks to DI, have full flexibility to work directly with the server instance, which allows us to implements modules where we have: cusom API endpoints, requests limits, http_proxy support, and many other specific and useful things.

The current solution has poor performance :(
For example, Cloudflare workers, the site is rendered and displayed to users around the world in about 50ms-65ms. At the moment, no framework provides a simple way to work in cloud functions or edge functions environments.

And the question is, if I want to use koa, what should I do in this case?

For example, Cloudflare workers, the site is rendered and displayed to users around the world in about 50ms-65ms

In our experience, two things significantly affect the response time of an SSR application:

server-side requests to any API's, because of that we have some timeouts, but still it can take a hundreds of milliseconds
server-side React rendering time for complex pages, can take from 25 to 100 ms, depends of page component complexity
Because of that, we haven't paid much attention to round-trip time.

But if we talk about cached content, no doubt RTT means a lot.
Also, we have a static HTML export feature, and these pages can be delivered to users via CDN.

And another question is, if I want to use koa, what should I do in this case?

No, we decided not to made abstractions over server framework, and use only specific framework, chosen by our team.
For now, we are in the process of completing the migration from express to fastify, for performance and some others reasons.
Supporting multiple server frameworks can be too expensive for us, at least it doubles our integration tests.

Supporting multiple server frameworks can be too expensive for us, at least it doubles our integration tests.

Is it possible to export an abstraction and connector functions for server frameworks ?
export handler = (req Request, res Response) {}

Don't think so, in server module internal implementation we have a lot specific framework connections.
E.g. list of internal tokens, any of this can be used in other core modules.


test: isolating test runs

kicking off new process for each test file
pulling out two problematic tests into separate files to run in isolation

Once accepted I'll add this commit right after @cxreg's fix so our nsolid adaptations come after this fix.
cc @cxreg @brycebaril

We should also think about lowering the timeout here otherwise our build servers get stuck instead of failing. Currently 600000 == 10mins so not a good idea IMO.
If we agree on say 10s timeout I'd add that onto this PR.


the css is not working properly

the slideshow image have a very small height and donot show properly

Very narrow (height of the icons). The parent div should have some height: 100% or something similar? I'm using bootstrap.css. Does it interfere?

@spidgorny thanks for reporting this bug. I'm guessing you're using background image. Can you follow this codesandbox [https://codesandbox.io/s/priceless-banach-sugm14?file=/src/slideshow.jsx](https://codesandbox.io/s/priceless-banach-sugm14?file=/src/slideshow.jsx]


docs: Document that uid is not unique across different kinds

Technically this is correct (frankly, I don't know that we check this even within a Kind - it's not really the primary key), but given UUID it is so diminishingly unlikely as to mostly negate this somewhat scare clause.
I'd rather file a bug that says we need a UUID index and be done with it.

As noted in #10610 ... when I saw the almost identical uids from service and endpoint I assumed they were identical ... as with similar paired objects in Openshift. Sorry for the noise.

Thanks, though. Appreciate the energy :)
On Jul 2, 2015 12:56 AM, "Stef Walter"<EMAIL_ADDRESS>wrote:

Closed #10660
https://github.com/GoogleCloudPlatform/kubernetes/pull/10660.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/10660#event-346186381
.


*nickserv should have identify command.

There should be a command in send the identify command to the server. It's not clear to everyone that the identify command is only requested by services after NickServ sends the message about nickname being registered. It would also help to see do the commads sent by *NickServ work.
There also seem to be commands for Ghost, Group, Recover and Release.
13:01:33 < *nickserv> +--------------+-----------------+-----------------------------------------------------------------------------------------------------------+
13:01:33 < *nickserv> | Command      | Arguments       | Description                                                                                |
13:01:33 < *nickserv> +--------------+-----------------+-----------------------------------------------------------------------------------------------------------+

13:01:33 < *nickserv> | Ghost        | nickname        | GHOST disconnects an old user session, or somebody attempting to use your nickname without authorization. |
13:01:33 < *nickserv> | Group        | nickname        |                                                                                |

13:01:33 < *nickserv> | Recover      | nickname        |                                                                                |
13:01:33 < *nickserv> | Release      | nickname        |                                                                                |

13:01:34 < *nickserv> +--------------+-----------------+-----------------------------------------------------------------------------------------------------------+

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/2535125-nickserv-should-have-identify-command?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

The whole module should be removed.


build: tslint rule to enforce html tags escaping in comments

The rule was built suposing that using backticks is enough to escape HTML tags in multiline code  comments. It should emit warnings when there is:
1 - Any HTML open tag (<) without a backtick (`)
/**
 * The using of <svg>` is very good because...
 */

2 - Any HTML close tag (>) without a backtick (`):
/**
 * The using of `<svg> is very good because...
 */

3 - Any HTML open or close tag without it's matching:
/**
 * The using of `<svg is very good because...
 */

4 - Any HTML open following an open tag and before a closing tag:
/**
 * The using of `<svg attr1="value1" < >` is very good because...
 */

Not sure whether look for unescaped html tags is better than look for "opening" backticks without the corresponding "closing" backticks.

Definitely this is not the way of escaping html tags in comment (based on the unsuccessful #7756 that didn't fix the issue)


Test features in ci

Introduces a new command test-features. It can be passed a list of port names or --all to specify for which ports the tests should be run.
The following tests are performed:

The core feature gets installed with default featured disabled (or --dont-test-feature-core)
Every feature gets installed with default featured disabled (or --dont-test-features-separately)
All features combined gets installed (or --dont-test-features-combined)

Feature which are unsupported or marked as cascade for the target triplet are skipped.
For every test only the necessary dependencies are installed (like vcpkg install in manifest mode).
The idea is to run the feature test for all ports that are changed by a PR.
Ports that cascade must be explicitly marked as cascade.
vcpkg format-feature-baseline scripts/ci.feature.baseline.txt is a command to format the feature baseline to enforce that all entries in a "block" are sorted alphabetically.
Docs: https://github.com/microsoft/vcpkg-docs/pull/131
Fixes https://github.com/microsoft/vcpkg/issues/13119
https://github.com/microsoft/vcpkg-tool/pull/908 reduce the needed ci time, this PR increases it again. So the actual change is not likely to be very large.

@vicroms @ras0219-msft Should this be extracted into an own command? The only interaction point between the current ci command and the feature test thing is that ports that failed to build in the feature test setting are not build again by the ci command (we build all packages) because they maybe will then suddenly work because dependencies are installed that are not listed in the port. The ports are then stored in the binary cache and the feature test will then also works because the package is already in the binary cache even through it would normally fail to build.
But this could also be solved by emitting a known-failures file by the new test-features command which is simply a list of abi's that are known to fail. This file is then passed to the ci command and the ci command then does not try to build these packages and we don't have the above mentioned problem.

Docs: https://github.com/microsoft/vcpkg-docs/pull/131

@AugP @BillyONeal @dan-shaw @ras0219-msft
Hi @autoantwort
We discussed this new feature and have the following asks:

Make it an experimental command: x-test-features
Option names in vcpkg use the --no-<toggle> pattern instead of --dont-<toggle>

We haven't made a review of the implementation yet, but will probably have some more comments later.

The commands removes all subdirs in buildtrees/<port>/src. Can this be avoided, or limited to .clean dirs? I would like to test ports without loosing temporary git repos, or editable dirs.

BTW could it test an unregistered modification, maybe via overlay ports?

So you want a flag like --editable?

I tested this PR while working locally on a vcpkg PR (zeroc-ice). It is quite helpful but at the moment,

I loose my git dirs for editing patches, without warning.
I hardly notice that it doesn't test the current state of my ports dir.

So you want a flag like --editable?

My comments were independent and shouldn't be mixed.
My first comment was about not touching unrelated source dirs in buildtrees (first problem).
My second comment was about the state of the ports dir (second problem).
With vcpkg install <port>; --editable has a different meaning: It is about not cleaning the actual source dir in buildtrees. This might be another option, but seems less important to me. I can transfer changes from editable state to proper patches before running test-features. And it is fragile: features may cause source dir modifications.
So I don't ask for a flag but for a general modification.

I hardly notice that it doesn't test the current state of my ports dir.

It does that.

I loose my git dirs for editing patches, without warning.

The behavior is the same as for x-set-installed, so --clean-buildtrees-after-build is on by default. I can change that. But I would personally prefer an inverted switch like --keep-buildtrees-after-build.

It does that.

Indeed, you are right.
I stumbled over another behaviour now: Post-build check errors of dependencies cause cascades which prevent the test of the port of interest. Understandable from a CI point of view, but less convenient for interactive testing. (In my case: readline-unix creates empty bin directories for x64-linux-dynamic. Good to have this covered by post-build checks, but I don't want to be stopped by this....)

Hm should I add a flag like --ignore-port-checks? As a workaround you could install the dependency outside of this command. Then it gets restored from the binary cache the next time, if you don't want to fix the check now :)

We haven't made a review of the implementation yet, but will probably have some more comments later.

@vicroms This PR is waiting for MS.


aarch64 release

aarch64 support is now in CI. Would be nice to see a new release for those targets.
PR: https://github.com/LukeMathWalker/bunyan/pull/11

0.1.8 is out 😁


Add ability to create connections on setUp thread group and disconnect on tearDown

When running load tests, one would prefer to create the connections on setUp thread group, run the load using these connection on the tests thread group/s (in loops and parallel users using different connections), and disconnect in the tearDown thread group section
At the moment connection is stored in JMeter vars, thus can only be used on the same thread group.

@leonpros,
Thanks for your suggestion.
We're considering to have the connection reused across thread groups in future, mark this as an enhancement.

any update on this issue?

@chongyuanyin This functionality would be great to have as I was looking for exactly similar.


about train

I meet a question for a long time,when I run python train.py, it will be as follows.

I try find this question,finally, I find this as follows

it is amazing!, I write the 'model_body = yolo_body(image_input, num_anchors, num_classes)' twice,it will be ok. but I don't know why. can you help me?

skip_mismatch=True is required because the output layers is not with the same shape.
Each Keras layer has its name, like 'Conv1', 'Conv2', 'Conv3'... When you call yolo_body the first time, the model layers may be from 'Conv1' to 'Conv50'. And 'Conv51' to 'Conv100' the second time. Then load_weights does nothing for the reason that by_name=True and the origin weights model begins at 'Conv1'.
Try upgrade Keras if there is a key error on skip_mismatch.

thank you,my keras is 2.1.2,I update the keras to 2.1.6 accordong to your suggestion,and solve this question .
thank you very much.


CPUParticles3D causes stutter if selected on the scene tree

Tested versions
-Reproducible in: 4.3.beta2
System information
Android 11 - Godot V.4.3.beta2- compatibility renderer
Issue description
when i add a CPUParticles3D and assigning a mesh for it , it works fine and first
.But if I expand the mesh drop-down for the particle it becomes so slow and laggy. If i deselect the CPUParticles3D in the scene tree everything works normally again
https://youtu.be/2dX27d-Arv0?si=QxO0TXgYS6zcYDmg
Steps to reproduce
create a project in compatibility renderer. add a CPUParticles3D,give it a mesh, expand the mesh drop-down.
Minimal reproduction project (MRP)
N/A
### Tasks

### Tasks

My guess is that the mesh inspector preview is re-rendering when it doesn't need to. It's interactive so it can't just use the Once update mode, but it should either use the When Changed update mode if it's not doing so already (it's the Viewport default), or it should switch to the Once update mode at startup and once the user stops interacting with it.

i think the stutter has been fixed in 4.3.beta3. CPU time seems ok. now only issue is camera view doesn't update which is most probably related to #93357. Thank you very much 😊


Determine how a transport declares that it supports binary

After https://github.com/aspnet/SignalR/pull/517 there's no longer a concept of text/binary messages but transports can declare themselves as supporting binary. We need to determine how this happens for http transports and how that manifests as transport metadata.

IMHO I'd like to follow the HTTP accept: header with an optional $format parameter similar to odata

Yeah, Accept headers are the best case, but unfortunately they don't work in all cases. WebSocket clients (the browser in particular) don't generally give you the ability to specify headers on the incoming request, and SSE requires a specific Accept header that doesn't distinguish between our sub-protocols (JSON and ProtoBuf).

We'll likely use the query string.

Proposal:
For http based transports, metadata can be passed through http requests via headers or query string:

Query string - ?sockets-{key}={value} e.g.  ?sockets-format=json&sockets-name=foo
Headers - X-Sockets-{key}={value} e.g. X-Sockets-format=json

These will manifest as keys in connection metadata with entries mapping to the key value pairs specified. There should be no conflict with reserved keys since we'll be using objects for those internally (even though we're not doing this today).

It's actually a bit more complicated than this. We need to go deeper and figure out how this maps to APIs on the client side as well.

Actually, the more I think about this, the more I think we need to negotiate based on a message rather than relying on the underlying transport. The problem is that TCP has nothing so we can't rely on this for those transport types. The HubEndPoint could look at the underlying transport metadata directly (e.g. like pull out the http context or specific features) in order to light up behavior based on the transport.

Something that's really important in this: We cannot allow internally-used metadata (like transport name, etc.) be overridden by this function for security reasons. For those, we should use Features anyway, in the new model.
In fact, I think "metadata" is the wrong term from this because we don't want customers putting things in here that could be overridden by client-provided parameters. Perhaps something like "Parameters"?

I think we can punt this. We added a negotiate message so there's no need to support flowing arbitrary data from the http request through the protocol. We offer access to the HttpContext directly so the user code can get at it.


Enable hibernate second level cache

related to #9

I have simplify the "when" condition in the prompt file to avoid too much complexity when we handle only a part on those conditions. We probably need to update this "when" condition when the blueprint will move forward.

Also I wonder if we should exclude test files from the Sonar quality gates

I'm in favor of excluding tests from Sonar duplication checks. Requiring low duplication in test classes often leads to tightly coupled/unreadable test code.

@avdev4j Can you take a look at the sonar failure on this one?

It comes from the server.spec.ts. I wonder If we should exclude test files from sonar analysis... anyway I know how to fix it.

LGTM


TOC does not work with group layers on version 100.1

TOC does not work with group layers on version 100.1
It only opens the parents level and not as a treeview for drill down

Use this webmap:
http://ess.maps.arcgis.com/home/webmap/viewer.html?webmap=f1ed0d220d6447a586203675ed5ac213
Expected (worked in v100):

Current (not working in v100.1):

I would like to understand better
Is this a problem that has to be fixed within the core or within the arcgis-toolkit-dotnet solution?

In my first round of looking at this, it seems that the problem is with this return statement.  If you remove it, the sub layers will populate:
https://github.com/Esri/arcgis-toolkit-dotnet/blob/687545da529fdf4bfb18aac4e1e683d58b92b206/src/Esri.ArcGISRuntime.Toolkit/WPF/UI/Controls/TableOfContents/LayerContentViewModel.cs#L115

Pushed a fix in to resolve this.

After I did the change I sometimes encounter with the following error:
System.InvalidOperationException: Collection was modified;
enumeration operation may not execute.
at
System.ThrowHelper.ThrowInvalidOperationException(ExceptionResour
ce resource)
at System.Collections.Generic.List‘1.Enumerator.MoveNextRareO
at
System.Linq.Enumerable.WhereSelectEnumerableIterator‘2.MoveNextO
at System.Collections.Generic.List‘1..ctor(IEnumerable‘1 collection)
at
med s.Map.UI.TableOfContent.LayerContentViewM od el. < BuildSublayerL
ist> d_16.MoveNextO in
c:\Users\tamarre\Source\Workspaces\SitaWare\Main\Source\meds.Ma
p\U1\TableOfContent\LayerContentViewModel.cs:line 116
End of stack trace from previous location where exception was
thrown
at
System.Runtime.CompilerServices.AsyncMethodBuilderCore.< > c. b_6_0(Obj ect state)
at
System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegat
e callback, Object args, Int32 numArgs)
at
System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object
source, Delegate callback, Object args, Int32 numArgs, Delegate
catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImplO
at System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.InvokeO
at System.Windows.Threading.Dispatcher.ProcessQueueO
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd,
Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr
wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object 0)
at
System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegat
e callback, Object args, Int32 numArgs)
at
System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object
source, Delegate callback, Object args, Int32 numArgs, Delegate
catchHandler)
at
System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPri
ority priority, TimeSpan timeout, Delegate method, Object args, Int32
numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg,
IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at
System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFram
e frame)
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at meds.Desktop.App.MainO in
c:\Users\tamarre\Source\Workspaces\SitaWare\Main\Source\meds.Des
ktop\obj\Debug\App.g.cs:Iine 0

@kerenco75 Could you try pulling the entire latest v100 branch? There was another commit shortly after that also cleaned up the indices in the collection.
If that doesn't help, could you share a sample and steps that reproduces this error?


JSON class not loading compliant file

@doutriaux1  Attached file (without the .txt) can't be read with
J = pcmdi_metrics.pcmdi.io.JSONs(inpath)
(pmp_cdat8) bash-4.1$ python -i portrait_test.py
Traceback (most recent call last):
File "portrait_test.py", line 12, in
J = pcmdi_metrics.pcmdi.io.JSONs(inpath)
File "/export/gleckler1/anaconda2/envs/pmp_cdat8/lib/python2.7/site-packages/pcmdi_metrics/pcmdi/io.py", line 57, in init
ignored_keys=ignored_keys,
File "/export/gleckler1/anaconda2/envs/pmp_cdat8/lib/python2.7/site-packages/pcmdi_metrics/io/base.py", line 491, in init
self.addJson(fnm)
File "/export/gleckler1/anaconda2/envs/pmp_cdat8/lib/python2.7/site-packages/pcmdi_metrics/pcmdi/io.py", line 61, in addJson
f = open(filename)
monsoon-wang_CMIP5_historical-regrid2_regrid2_2018-07-19-10-58-22.json.txt

@lee1043 Any ideas why this does not work after removing the ".txt" from the attached json file?

@gleckler1 could you please point where I can find the portrait_test.py?

@lee1043 This is it...
import glob
import json
import os, sys
import pcmdi_metrics
inpath = '/work/lee1043/cdat/pmp/pmp_results/tree_v0.3/pmp_v1.1.2/metrics_results/monsoon/monsoon_wang/cmip5/historical/test1/monsoon-wang_CMIP5_historical-regrid2_regrid2_2018-07-19-10-58-22.json'
J = pcmdi_metrics.pcmdi.io.JSONs(inpath)
print J.keys()

@gleckler1 could you please replace bottom two lines to below and give a try?
J = pcmdi_metrics.io.base.JSONs([inpath])
print(J.getAxisIds())

For me I see below as result.
['variable', 'model', 'domain', 'statistic']

@gleckler1,
@doutriaux1 recommended not to use pcmdi_metrics.pcmdi.io.JSONs as it returns something hard-coded axis IDs as below:
J = pcmdi_metrics.pcmdi.io.JSONs([inpath])
print(J.getAxisIds())

['variable', 'model', 'reference', 'rip', 'region', 'statistic', 'season']

which is not defined as json_structure in the JSON file. @doutriaux1 please correct me if I am wrong.

note: the inpath should be given as list, [inpath] to the json loading function

@lee1043 correct the method used by @gleckler1 is a convenience subclass used for pcmdi_metrics results.


Change package manager to yarn

This PR changes the package manager to yarn by generating lock files using yarn and changing npm commands to yarn.
Relates to https://github.com/cloudflare/cloudflare-docs/pull/2709

why the changes in workers-site/package-lock.json ?

@gganch The changes are from reverting from yarn install to npm install 'cos workers use npm to install dependencies. I will revert it


Rapid-fire sends regardless of interval.

I used the socket.io example to implement timesync using basic websockets (not a fan of socket.io's overhead and lack of binary buffers). Here is the gist of the implementation:
Server
socket.on('timesync', data  => socket.send('timesync', {
    id: data && data.id || null,
    result: Date.now()
}));

Client
const ts = require('timesync').create({server: socket});
ts.send = (socket, data) => socket.send('timesync', data); // Sends {jsonrpc: "2.0", id: null, result: <timestamp>}
socket.on('timesync', data => ts.receive(null, data)); // Receives {id: null, result: <timestamp>}

The issue is that hundreds of timesync requests are being sent per second, even though each is receiving a correct response. I have tried create({server: socket, interval: 5000}) as in the socket.io example, but am getting the same result. I'm not sure if I'm missing something, or if there's a bug. Any help would be appreciated.

I'm not sure what's going wrong in your case, but if the socket.io example works you should be able to figure out the differences between the working example and your code.
You're free to use another websocket solution instead of socket.io, timesync can work everywhere. The examples include the most commonly used solutions (http, express, socket.io), but you can use any web socket or http library.

I'm seeing the same thing on my web client.  Seems like it gets stuck in an infinite call / response loop.  It happens rarely and I'm not sure what scenarios lead to this issue.  I believe the issue is around this line:
else if (data && data.id !== undefined) {

        // this is a request from an other peer
        // reply with our current time
        timesync.send(from, {
          jsonrpc: '2.0',
          id: data.id,
          result: timesync.now()
        })
      }

It happens when somehow I get an id = 0:
{
    "id": 0,
    "result":<PHONE_NUMBER>374
}

This is my current client side code:
	var ts = timesync.create({
		server: '/timesync',
		interval: null,
		delay: 1000,
		repeat: 4,
	});
	ts.sync();

Thanks for the extra info @sean335 .
 In v0.3.1 an issue was fixed which could be related to this issue.
I can use some help figuring this out, will not have time for debugging this issue any time soon. Anyone interested in helping out just drop a message here.

I am also running into this issue whenever requests take longer than 10s. I think in my case it has to do with the implementation of timeouts. It seems that when the timeout is hit in the rpc function, the entry for id is deleted from _inProgress, and the promise is rejected with an error. But in the send function, the actual request ultimately returns successfully, so receive is being called, which falls into the else if block posted by @sean335 above. This results in a new request with the same id, and since the entry is still gone from _inProgress, it loops indefinitely.
If this is the case, maybe a way to fix it would be to have the XHR itself time out as well.

Thanks @dfeblowitz, that sounds like you've probably tracked down the issue. Would it be possible for you to turn your findings into a PR with a fix?

This issue should be closed now thanks to the fix of @dfeblowitz in #15.
Please let me know if this indeed resolves the reported issues.

Please reopen this. There was a subtlety that I missed in #15 that I didn't notice because of how I was testing, and I'm still seeing this issue when I include the new version in my application. It seems that the XHR timeout doesn't start counting until the request is sent, but timesync's internal timer starts counting before the XHR is created or opened. So if the XHR takes a long time in the "start" phase (which is happening for me), timesync may consider the request to have timed out, but the request still may complete successfully, triggering this behavior. (I'm looking at the Network > Details > Timings view in IE 11's devtools to figure this out, https://msdn.microsoft.com/en-us/library/dn255004(v=vs.85).aspx)
I didn't see this because I was testing by making the server take a long time to respond, which does make the XHR time out. I can work on addressing this.

Thanks for reporting back, that's trickier than I had expected! Would be great if you could find a solution!

This library does not deal with timeouts appropriately in the context of socket.io. Right now timesync assumes that a timeout indicates a permanently failed request, but this only the case half the time with socket.io:

If a timeout would occur because the server is temporarily inaccessible, then socket.io will wait until a connection is reestablished before pushing out all pending messages. In this situation, the request hasn't failed - it just hasn't happened yet.
If a timeout would occur because the server failed to respond to a request, then the request will never return.

So given the way the library is setup right now, I recommend against using the implementation supplied in the examples. I've found that this extremely minimal usage is much less error prone:
Server config:
socket.on('timesync', ({id} = {}) => socket.emit('timesync', {id, result: Date.now()}));

Client config:
const ts = timesync.create({server: true});
ts.send = async (_, data) => await socket.emit('timesync', data);
socket.on('timesync', ts.receive);
ts.on('change', console.log);

The one big pitfall with this implementation is that if the server fails to respond to any timesync message, then the entire process is permanently stalled. This doesn't cause any issues other than that the client will not acquire the proper offset from the server.

The library is based on the concept of sending a request, awaiting a reply, and then calculating the duration of the round trip. The library uses a simple RPC mechanism for that. The id is used to be able to relate the right reply to the right request.
Keeping timed out id's in memory sounds tricky since the amount of memory can grow infinitely.
If I understand you correctly, when a reply comes in with an id which was already timed out, it gives problems? If so, maybe we can properly handle these "orphaned" replies, by not crashing but neatly logging an error and continuing? Or is that already handled?

The library currently does not handle the case of when an ID returns which has already timed out. In that case the ID doesn't exist anymore, and so (as I remember) it interprets the request as though it's coming from another client.

In general it's a good idea to report errors like when receiving a reply with an unknown ID over silently ignoring it. I'm not sure by heart whether this breaks the application or just throws an error. In the latter case it would be nice if the error has a specific type or property so you can distinguish and decide to ignore this class of errors if you want.


Read hostnames from spec.tls.hosts on Ingress object

Fixes #610
Not sure about check for empty "host" value, if it's needed, just copied from rules handling.
Also updated docs, to reflect annotations support on ingress (see #545 ) and this new hostsnames from tls feature.

Signed that CLA

Thank you for your PR 🙂
/LGTM


Web component tester can not query element with v6.0.0.... used to be able to in 4.3.6

When upgrading web-component-tester from 4.3.6 to 6.0.0 my tests would break from not being able to query elements. The specific breakage here is when it tried to query spToast in  spToast = Polymer.dom(spApp.root).querySelector('sp-toast'); at line 56.
Example:
    <test-fixture id="sp-veteran">
      <template>

veteran

        <sp-app>
          <sp-toast></sp-toast>
          <sp-veteran></sp-veteran>
        </sp-app>
      </template>
    </test-fixture>


set completeopt+=popup?

Is your feature request related something that is currently hard to do? Please describe.
Now that there are popup windows, it should be possible to get completion information in a popup rather than the preview window.  This would be much more convenient than the preview window since it takes up less dedicated screen space.  Is this already planned?
Describe the solution you'd like
A popup which replaces the preview window for completion info.

The popup should be placed in the first possible space, depending on the size/aspect ratio of the popup, e.g.:

to the right
above
below
to the left

Describe alternatives you've considered
Plugins can already provide their own side-car popups today using the CompleteChanged event.  I assume they will do this in complex cases (e.g. using color).  But the simple case, display info in popup instead of preview, should be supported out of the box.
Additional context
I noticed that there is an unimplemented feature of popup windows, which I guess is blocking this:
flip		When TRUE (the default) and the position is relative
		to the cursor, flip to below or above the cursor to
		avoid overlap with the |popupmenu-completion| or
		another popup with a higher "zindex".
		{not implemented yet}

However, I argue that the overlap prevention should happen left/right as well.
I tried the very naïve implementation below.  It has issues, like positioning, and that multiple popups are spawned which don't go away until you close the pum (even though "moved" is set to "any").
diff --git a/src/option.c b/src/option.c
index 12a0816f3..98286b46f 100644
--- a/src/option.c
+++ b/src/option.c
@@ -3228,7 +3228,7 @@ static char *(p_fdm_values[]) = {"manual", "expr", "marker", "indent", "syntax",
 static char *(p_fcl_values[]) = {"all", NULL};
 #endif
 #ifdef FEAT_INS_EXPAND
-static char *(p_cot_values[]) = {"menu", "menuone", "longest", "preview", "noinsert", "noselect", NULL};
+static char *(p_cot_values[]) = {"menu", "menuone", "longest", "preview", "noinsert", "noselect", "popup", NULL};
 #endif
 #ifdef FEAT_SIGNS
 static char *(p_scl_values[]) = {"yes", "no", "auto", NULL};
diff --git a/src/popupmnu.c b/src/popupmnu.c
index 09faa69e8..3e5729748 100644
--- a/src/popupmnu.c
+++ b/src/popupmnu.c
@@ -702,7 +702,7 @@ pum_set_selected(int n, int repeat)
 	if (pum_array[pum_selected].pum_info != NULL
 		&& Rows > 10
 		&& repeat <= 1
-		&& vim_strchr(p_cot, 'p') != NULL)
+		&& strstr(p_cot, "preview") != NULL)
 	{
 	    win_T	*curwin_save = curwin;
 	    tabpage_T   *curtab_save = curtab;
@@ -845,6 +845,58 @@ pum_set_selected(int n, int repeat)
 		}
 	    }
 	}
+#endif
+#ifdef FEAT_TEXT_PROP
+# ifdef FEAT_QUICKFIX
+	else
+# endif
+	if (pum_array[pum_selected].pum_info != NULL
+		&& Rows > 10
+		&& repeat <= 1
+		&& strstr(p_cot, "popup") != NULL)
+	{
+	    char_u  *p, *e;
+	    list_T  *l;
+	    dict_T  *d;
+
+	    l = list_alloc();
+	    if (l == NULL)
+		return FALSE;
+	    for (p = pum_array[pum_selected].pum_info; *p != NUL; )
+	    {
+		e = vim_strchr(p, '\n');
+		if (e == NULL)
+		{
+		    list_append_string(l, p, 0);
+		    break;
+		}
+		else
+		{
+		    *e = NUL;
+		    list_append_string(l, p, (int)(e - p + 1));
+		    *e = '\n';
+		    p = e + 1;
+		}
+	    }
+
+	    d = dict_alloc();
+	    if (d == NULL)
+		return FALSE;
+	    dict_add_string(d, "pos", "botleft");
+	    dict_add_string(d, "line", "cursor-1");
+	    dict_add_string(d, "moved", "any");
+	    dict_add_number(d, "col", pum_col + pum_width + 3);
+
+	    typval_T argvars[3], rettv;
+	    argvars[0].v_type = VAR_LIST;
+	    argvars[0].vval.v_list = l;
+	    argvars[1].v_type = VAR_DICT;
+	    argvars[1].vval.v_dict = d;
+	    argvars[2].v_type = VAR_UNKNOWN;
+	    f_popup_create(argvars, &rettv);
+
+	    return FALSE;
+	}
 #endif
     }

As author of asyncomplete.vim and vim-lsp, I would be very happy if this was supported in vim so I don't have to duplicate this feature for asyncomplete and vim-lsp omni-func. For some LSP popup servers we need to send additional request to get the actual popup info so would be good to have a method something like this so we can call call set_complete_popup(completed_item, '...popup text') based off CompleteChanged event.

@prabirshrestha, what is the request/response and what do you do currently to populate the "info" field of completion menu?

Here is an example. Basically trying to set info for all completion items can be very expensive because server needs to do more work as well as some docs might be quite large which requires scrolling which currently vim8 doesn't support it yet since it can't focus in popup window.

To overcome this LSP supports completionItem/resolve. https://microsoft.github.io/language-server-protocol/specification#textDocument_completion. There is a bit more about perf on https://github.com/sourcegraph/javascript-typescript-langserver/issues/331
I personally don't think it should be just info as I would like to get more control over the popup. We already have enough information about row/height/size from CompleteChanged so would be ok to manually call popup_create. I was thinking if vim could do most of the complex work on positioning which may or may not make sense here.

vim8 doesn't support it yet since it can't focus in popup window.

Why can't you use the key callbacks?

I was thinking if vim could do most of the complex work on positioning

I do think vim should handle automatic positioning as a generic property of a popup because it is really tedious to do from plugins and should just need to be implemented once.

It should be possible to put the "info" from the complete menu in a popup instead of a preview window.
Positioning may be a bit tricky, especially on a small screen and when the cursor is near the top or bottom of the screen.
It should also be possible for a plugin to show a popup depending on what entry in the completion menu is selected.  The "info" is only plain text, a popup can do much more.

With
set previewpopup=height:10,width:60
set completeopt+=preview

the info field will be displayed in a popup window, but its position is wrong. Currently the popup window appears at the cursor position, consequently, always on top of the completion popup.
I wasn't sure whether I should open a new issue for that.

Sorry to bump an already closed issue, but I'm not sure if this one is completely implemented. Using macvim v8.1 (patches 1-2234) together with YouCompleteMe; the popup always appear on the sides of the completion menu, even in cases where it doesn't really fit:

I've been unable to find any way to position the popup above and/or below the menu as was described in this part of the original issue:

The popup should be placed in the first possible space, depending on the size/aspect ratio of the popup, e.g.:

to the right
above
below
to the left

Is the flip option for create_popup() a blocker for this? And if so is there anywhere I can track its implementation? I was unable to find any issue related to it on github.

I noticed that there is an unimplemented feature of popup windows, which I guess is blocking this:
flip		When TRUE (the default) and the position is relative
		to the cursor, flip to below or above the cursor to
		avoid overlap with the |popupmenu-completion| or
		another popup with a higher "zindex".
		{not implemented yet}

Related issue over at YouCompeteMe
Build used
VIM - Vi IMproved 8.1 (2018 May 18, compiled Oct 30 2019 23:05:13)
macOS version
Included patches: 1-2234

In the example you give, where should the info popup go then?  Perhaps below the menu?  But then it looses the connection with the selected entry (assuming there normally are several entries in the menu).  Or perhaps it can overlap the menu, making sure it doesn't obscure the selected entry?
We need several examples to see what works best in general, otherwise we are optimizing for one specific example and break it for others.

@brammool: If a minwidth option was added and there wasn't enough on the left nor the right of the completion menu it could be positioned above the line being edited, just like function signatures are rendered above the line after choosing a completion (with YCM at least). In this specific edge case it would mean the popup only had 2 lines available, but those two lines would be more readable. I agree that positioning it below the completions would sever the connection to the selected completion though.
Another solution would be for the plugin to simply only include the identifier (eg. exclude the signature) from the completion menu so that the popup has a better chance of fitting. I asked @puremourning about this in the referenced YCM issue.

just like function signatures are rendered above the line

For the record, positioning of the signature hint popup is completely YCM code and it’s already pretty complex (attempting to avoid overlapping the PUM). If the preview popup jumped around it would be even more hectic working out what takes priority.


Optimize serialization for chain-level multi-indexes

For smart-contract double serialization (object -> binary -> variant -> DB) is a necessity, because only simple types can be transferred.
In case of chain-level multi-indexes serialization from object to binary can be skipped, because on chain-level any object can be directly delivered to DB.

Closed in #45


Definition of AST should be placed at brack-parser

The brack-sdk-rs crate is a crate for use when developing plugins in rust, and therefore ASTs are defined there. However, it is unnatural for Parser to depend on brack-sdk-rs to use AST, so AST should be defined in brack-parser as well.

It has already resolved.


Merge policy.

Can we cobble together a policy for merging things? I didn’t want to start pulling in PRs in case @dissolve has a default way of handling commits on Inklings-io…

I haven't hit the issue yet as no one has had write access.  It's a small enough lib that I'm fine with it being community managed.  So go for it

Oops didn't mean to close it

the most important thing is a contributing.md file saying that contributors either give up all rights to their contributions or allow their contributions to be licensed under the same license as the project.

+1 I'm open to whatever if someone has something in mind

added a contributing.md and license information that i think all seems reasonable

After today, I'd say as a rule we should do everything in PRs reviewed by someone else 😝

:+1:

Make a new branch, commit changes to it, open PR with reviewers added.
After all reviewers green lit the PR, hit the big green merge button on GitHub.

That sound good to everyone?

Can set this in the repo configs to only allow merging after at least one
reviewer who is not the original commit creator
On Fri, Jun 30, 2017 at 11:27 AM, Martijn van der Ven <
<EMAIL_ADDRESS>wrote:

Make a new branch, commit changes to it, open PR with reviewers
added.
After all reviewers green lit the PR, hit the big green merge
button on GitHub.

That sound good to everyone?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Inklings-io/selfauth/issues/4#issuecomment-312298046,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACbZ4aeq7Lx2ZyqJ5T6fBpwy6k3GGEEYks5sJRPkgaJpZM4OC6bu
.

Can set this in the repo configs to only allow merging after at least one reviewer who is not the original commit creator

Go for it :+1:

I think that will do it... never set it up before


Pluggable scheduler API

Like to start the discussion around pluggable scheduler API, to make sure it doesn't become impossible to integrate with other schedulers.
I'm coming from the Mesos side, but I'm sure there are others too.

:+1:
The sooner we define an API the better – both so we don't become tied to our scheduler and so other providers (Kubernetes, Fleet, etc) can write their own drivers.

@vieux @aluzzardi how do we move forward with this? I think we should start implementing the default one under a interface at the very least.
Also it seems like the current scheduler class is only about the placement of a container, but there is also discovery and managing the state of a cluster.
I think all of this should be pluggable under interfaces.

@tnachen you're right, right now, scheduler and discovery are separated. Discovery already has it's own interface (consul, etcd, etc...), but not Scheduler.
You could look at this https://github.com/docker/swarm/pull/178 for an attempt at really basic version of the Scheduler interface.
Regarding mesos I feel like Scheduler and Discovery needs to be blended because swarm won't get a list of nodes, but a list of mesos master.
My dream would be swarm manage --discovery mesos://<zookeeper_url_with_the_mesos_masters>

Actually, after thinking about this more, I think we don't have to mix Scheduler and Discovery.
This will probably the main use case:
swarm manage --scheduler mesos --discovery zk://<zookeeper_url_with_the_mesos_masters>/path
But you should be able to use other discovery mechanism
swarm manage --scheduler mesos --discovery file://list_mesos_master
@tnachen what do you think ?

I think I need to understand more if discovery info is going to be used by some other commands or components of swarm.
Seems like discovery is simply listing all the swarm agents, does it also plan to list all the containers or find a particular container in the cluster?
But yes, I think discovery can stay as-is.
I'm thinking that the swarm framework can launch custom executors which launches the swarm agent that will be running on each host, and we can let the custom executor talk to the discovery backend out of band from Mesos if we want to utilize swarm discovery features in the future.
btw @vieux, if a swarm manager dies, how does it bootstrap again to get to know all the running containers?

discovery gives you a list of ip/port you need to talk to:
with the default scheduler, it's a list of docker daemon, with mesos I think it'll be a list of mesos master.
right now, when you restart it, it'll reconstruct the cluster cache by reaching all the nodes and asking for their containers.
soon we will have a local cache on disk.
later we will have shared state (probably with raft)

So if you want a list of all the available nodes that you can a docker container, then it's the whole list of slaves (which you can get from querying the JSON endpoint from master).
However just getting the slave nodes doesn't necessarily tell you the swarm endpoints, unless we assume swarm is running on the same port on all the nodes.
Also it's either an assumption that swarm agent is already preinstalled and running on all your cluster nodes, or the framework actually allows downloading swarm agent and running one per host itself.
I assume the former, where docker daemon is pre-installed.

@tnachen
Reading your last few comments, they don't make much sense to me. You speak of the swarm agent running on each node, but swarm only runs in one location. It talks to the docker daemon that runs on each node, but doesn't run there itself.

Just some of my thoughts on the whole scheduler thing. I think the scheduler interface will need to be a lot more advanced than just calling out to an external system and asking "what node should I place this container on?".
For example, if we use swarm for our system, we'll need it to be able to do things like handle when a new node comes up or goes down, so that it moves existing containers around to balance things out. Or rebalance containers if one of them starts consuming a lot of CPU.
Thus I think the interface should be more of swarm saying "I have this desired configuration", which would be what containers should be running and their configurations. The scheduler should then tell swarm what to do. If the configuration has a new container being started, the scheduler will tell swarm "start this container on node A". If the scheduler deems that some containers need to be moved around, it might also send "stop container X on node A. start container X on node B"
This scheme also allows the scheduler to move things without being prompted by swarm. Lets say a container starts using a lot of CPU, the scheduler might decide to move this container elsewhere. The move wasn't triggered by any configuration change.

I also don't think discovery should be tied into the scheduler. In my use case, discovery will be handled by swarm, and swarm will let the scheduler know a node just joined, or is leaving. If both scheduler and discovery happen to actually be the same service, thats fine, but swarm shouldn't know that.

@phemmer I'm looking at the example usage and also the discovery, and it seems to me that in order to be discovered you need to run the agent on each node in your cluster. Is this not true?

@tnachen Actually no. This is everyone's first thought when the see the swarm readme :-)
The swarm join --discovery token://FOO --addr=BAR action can actually be run from any node. All this does is publish the address of the docker daemon to the token based discovery service. It's a one-time registration operation. The swarm manager then reaches out to the discovery service to get a list of docker daemons that it needs to connect to.

@phemmer I see, the comments does it make it very confusing:
on each of your nodes, start the swarm agent

I'm not all familiar with the intentions and the code, but it seems like just looking at join.go alone, it seems to imply that it's meant to run on each node as it continues to callback register in a infinite loop with heartbeat timeout. If it's just a one time registration it seems unnecessary, and definitely doesn't make sense to run a bunch of loops in one node just giving ip addresses.

Actually it looks like I'm somewhat wrong. The agent does stay running. It pings the discovery service periodically to let it know the node is still there. It's been a few months since I played with it, so apparently I'm out of date. I appologize.

Implemented \o/

@aluzzardi - can you point me to the documentation on plugin API and how to create them?

@ppadala hello, there is no documentation really. You have to implement this interface: https://github.com/docker/swarm/blob/master/cluster/cluster.go

@ppadala I'm opening an issue to create documentation.

Thanks, @vieux. How do I install and register the plugin? If there's example code somewhere, please point me to it.

@ppadala you have to add a case to this switch https://github.com/docker/swarm/blob/master/cli/manage.go#L258

@vieux Is it expected that third party Swarm plugins live in docker tree and built together for now? Will there be a plugin architecture similar to volumes and libnetwork in the future?

@ppadala yes, we are thinking about a plugin architecture, for now they are to be checked in in the code.

Thanks for the quick responses @vieux.
Slight digression, but is there a way to find the Swarm ID from a container ID? It looks like currently Swarm master gets the container association by querying the Docker engines on each of the hosts. We are experimenting with sharing hosts across Swarm clusters and need a way to distinguish containers by Swarm IDs.
I see that labels are a way to distinguish containers, but they have to be set by the users.

Is there an issue open for the plugin architecture?


Automate testing of Using odo > Creating components docs in odo.dev

/kind user-story
/area-testing
User Story
As a QE I want to automate the test of Using odo > creating components documentation So that we can ensure that when following the documentation any steps/commands described in the documentation will complete successfully. Serves as acceptance tests, all test should pass.
Acceptance Criteria

[ ] Execute every command described in the documentation.
[ ] Report failing commands
[ ] Serves as acceptance testing, all commands should pass

Links

Related: #5195

/kind user-story

/close
in favor of https://github.com/redhat-developer/odo/issues/6192


jsonschema.Marshal

Is your feature request related to a problem? Please describe.
When exporting a config, I sometimes need the value of a field to equal the json-schema of another cue type. For example: LLM tool definitions.
Describe the solution you'd like
Similar to json.Marshal, I would like a jsonschema.Marshal that takes a cue definition and outputs json-schema.
Describe alternatives you've considered
Alternatively, I have to maintain json-schema by hand, or do a two-phase build process.

Do you mean generating jsonschema from CUE? If so, this would be https://github.com/cue-lang/cue/issues/929.

I want to generate jsonschema or openapi in cue via a function like json.Marshal.
For example:
test.cue
import "encoding/jsonschema"

#Thought: {
    name: string
    description: string
}

Component: {
    id: "LLMComponent"
    parameters: {
        model: string | *"gpt-4o"
        tools: {
            think_tool: jsonschema.Marshal(#Thought)
        }
    }
}

cue export test.cue
{
    "Component": {
        "id": "LLMInterface",
        "parameters": {
            "model": "gpt-4o",
            "tools": {
                "think_tool": "{\"openapi\":\"3.0.0\",\"info\":{\"title\":\"Generated by cue.\",\"version\":\"no version\"},\"paths\":{},\"components\":{\"schemas\":{\"Thought\":{\"type\":\"object\",\"required\":[\"name\",\"description\"],\"properties\":{\"name\":{\"type\":\"string\"},\"description\":{\"type\":\"string\"}}}}}}"
            }
        }
    }
}


Support setting KeyboardDismissMode

Adds the ability to set the TextView's KeyboardDismissMode

Looks good!

Looks good!


Tests Failing because of getPrefixLength

The previously depreciated function getPrefixLength is causing tests to fail in APL

Thank you - I will look into this issue for the next release.

This will be fixed in version 4.2
Thank you!


Auto-configure an async SNS client

:loudspeaker: Type of change

[ ] Bugfix
[ ] New feature
[x] Enhancement
[ ] Refactoring

:scroll: Description
Export the async-enabled subclass of the Amazon SNS client. Since this is built by a factory, this change is entirely declarative.
:bulb: Motivation and Context
fixes #564
:green_heart: How did you test it?
The automated tests were not working because of a Checkstyle error in Core.
:pencil: Checklist

[ ] I reviewed submitted code
[ ] I added tests to verify changes
[ ] I updated reference documentation to reflect the change
[ ] All tests passing
[ ] No breaking changes

:crystal_ball: Next steps

Ideally this change should be non-breaking - meaning  async client should be exposed as a bean in addition to already existing sync client.

Ideally this change should be non-breaking - meaning async client should be exposed as a bean in addition to already existing sync client.

The change is non-breaking as far as I can tell, but I wasn't sure whether the checklist was something I was supposed to do myself or was a code-review step.

The change is non-breaking as far as I can tell

My bad. Async one extends the Sync one.


Update package.json: Add repository url field

This is to make package homepage discoverable in npm index:

https://www.npmjs.com/package/json-server

Thank you!


Deprecate stash container

This really isn't popular so I'm going to reduce maintenance burden by removing it.

Done in https://github.com/onedr0p/containers/commit/c8637bde218bf9809a2e948eadd25621013fbc48


Select shows twice in a Bootstrap Modal

When using latest 1.10, in a modal view, 2 selects show. one formatted and one non-bootsratp-formatted
Any ideas?

See guidelines for contributing.

Bug reports
A bug is a demonstrable problem that is caused by the code in the repository.
Good bug reports are extremely helpful - thank you!
Guidelines for bug reports:

Use the GitHub issue search. Check if the issue has already been reported.

Check if the issue has been fixed. Try to reproduce it using the latest master or development branch in the repository.

Provide environment details. Provide your operating system, browser(s), jQuery version, Bootstrap version, and bootstrap-select version.

Create an isolated and reproducible test case. Create a reduced test case.

Include a live example. Make use of jsFiddle or jsBin to share your isolated test cases.

+1

Sorry about the reduced bug i submitted. I ended up just using a older version. But when i get some time, i will try and send over a demonstrable bug.

I have the same issue...

i'm getting the same  too, using the latest version

Make sure the CSS file is correctly imported. That fixed the issue for me.