haskell: default name to "" when root isn't a path in developPackage

See https://github.com/NixOS/nixpkgs/issues/103062
I don't think the documentation on developPackage really needs updating, at the risk of making it too verbose.
Motivation for this change
This allows derivation outputs to be used as the root attribute in developPackage
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This allows one to set root to store paths, for instance the output of
gitignoreSource.
On Sat, Nov 7, 2020, 7:24 PM Dennis Gosnell<EMAIL_ADDRESS>wrote:

@cdepillabout commented on this pull request.
In pkgs/development/haskell-modules/make-package-set.nix
https://github.com/NixOS/nixpkgs/pull/103063#discussion_r519167183:

@@ -230,7 +230,7 @@ in package-set { inherit pkgs stdenv callPackage; } self // {
# build that package.
developPackage =
{ root

 , name ? builtins.baseNameOf root

 , name ? if builtins.typeOf root == "path" then builtins.baseNameOf root else ""

When would you want this? root gets passed to callCabal2nix, so it looks
like it has to be a path?
What bug are you trying to fix here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/103063#pullrequestreview-525646500,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGRJXABMHX7KQCYKMBUOJDSOUU5PANCNFSM4TNQP45A
.

Is there a nice way to get the name of a store path (i.e. everything after the hash), perhaps that would be better than "". Either way that string is just cosmetic.

rebased

Is it possible to merge or reject this please?

rebased


⚠ Processors has degraded performance

In 40a3c39, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 86 ms

Resolved: Processors performance has improved in 57ac1fc.


x/tools/cmd/godoc: identifier links in comments

What version of Go are you using (go version)?

$ go version
go version go1.12.4 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN="/Users/cafxx/go/bin"
GOCACHE="/Users/cafxx/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/cafxx/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.12.4/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.12.4/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/ql/lydqwymx3kz23j27p_dr5kz00000gp/T/go-build764495944=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
I wanted to have identifiers in comments turn into links, for ease of navigation. I have comments like the following in my repos:
// SomeFunction does something.
// SomeFunction can not be called concurrently; you can use OtherFunction
// if your code must be able to perform this operation concurrently.
func SomeFunction() {
  // ...
}

// OtherFunction is the same as SomeFunction but it can be called concurrently.
func OtherFunction() {
}

Note that this would not need to apply only to functions. Ideally it should happen for any (public?) identifier in the same package, as well as for public identifiers in other packages (if they are properly prefixed with the package name).
Examples of places where this could be useful (cursory check on a single package in the stdlib):

https://golang.org/pkg/bytes/#Buffer.Next (Buffer.Read)
https://golang.org/pkg/bytes/#Buffer.Read (io.EOF)
https://golang.org/pkg/bytes/#Buffer.String (strings.Builder)
https://golang.org/pkg/bytes/#Buffer.Write (ErrTooLarge)
https://golang.org/pkg/bytes/#Buffer.WriteTo (io.WriterTo)

What did you expect to see?
I would expect the SomeOtherFunction in the comment be rendered as a link to SomeOtherFunction in the HTML output of godoc.
What did you see instead?
No links. 😭

Duplicate of https://github.com/golang/go/issues/25444. See https://static-hotlinks.digitalstatic.net/bytes/#Buffer


Macro pollution (Is it called like this) on windows

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
windows 10 x64
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
binary
TensorFlow version:
2.1
Python version:
3.7
Installed using virtualenv? pip? conda?:
Bazel version (if compiling from source):
0.27.1
GCC/Compiler version (if compiling from source):
visual studio 2019
CUDA/cuDNN version:
10.2/7
GPU model and memory:
Turing

Describe the problem
Use compiled tensorflow to compile an empty project like this:
`#include <tensorflow/core/framework/tensor.h>
int main(int argc, char const* argv[])
{
return 0;
}I got some errors like this: warning C4003: not enough arguments for function-like macro invocation 'min' error C2589: '(': illegal token on right side of '::' error C2062: type 'unknown-type' unexpected error C3805: 'type': unexpected token, expected either '}' or a ','. Then I write#undef max
#undef min`  on third_party\eigen3\unsupported\Eigen\CXX11\Tensor,it passed compile.
Provide the exact sequence of commands / steps that you executed before running into the problem
Compile tensorflow to get .dll .lib and header files.
Create an empty vs project,config and use those files.
Write "#include <tensorflow/core/framework/tensor.h>" and compile it.
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@yonghenghuanmie Can you please provide more details on your issue? If this is not a bug, then please post this question in stackoverflow where there is a large community to support. If this is more of a bug, then please provide more details. Thanks!

I solved a similar problem.
I got some errors like this: warning C4003: not enough arguments for function-like macro invocation 'min'.
This is because the macro definition of min in windows.h requires two parameters, so there may be no problem with Linux. This is a namespace conflict, you can use
#undef min
#undef max
to close the macro definition in window.h.
May be useful

@jvishnuvardhan This is a bug. The simplest possible project linking to tensorflow won't build without a manual workaround. @yonghenghuanmie provided sufficient details to replicate the issue, what more do you need?


Issue with type casting of integers

EdgeDB Version: 4.4+9974f3c
EdgeDB CLI Version: 4.0.2+b26c502
OS Version: Windows11

Steps to Reproduce:

ok as expected.

tt:edgedb> insert MyNumber {number:= <int16>1234 };
{default::MyNumber {id: 1f0c2598-b2b5-11ee-bf5d-079f11515058}}

failed as expected.

tt:edgedb> insert MyNumber {number:= <int32>1234 };
edgedb error: InvalidPropertyTargetError: invalid target for property 'number' of object type 'default::MyNumber': 'std::int32' (expecting 'std::int16')

I expected to get an InvalidPropertyTargetError but successfully created a MyNumber.

tt:edgedb> insert MyNumber {number:= <int64>1234 };
{default::MyNumber {id: 22807242-b2b5-11ee-bf5d-d7154f6739e4}}

tt:edgedb> insert MyNumber {number:= 1234 };
{default::MyNumber {id: 257cc7f2-b2b5-11ee-bf5d-3f87384dd245}}

Schema:
module default {
    type MyNumber {
        number: int16;
    }
}

I'm seeing the same behavior with floats too. If I create a MyFloat type with a number: float64 or a number: float32 it will accept a cast into the other float type without issues.
And one might think that this is an implicit cast if not for the insert MyNumber {number:= <int32>1234 }; query you bring up that does fail.

@vpetrovykh Could you look into this and see if there's anything that can be untangled?
Either both should work or both shouldn't.
Honestly probably both shouldn't work, but we might need to make both work instead.

There are a few things interacting here, in the casting system (see casting table)
We have some general rules:

The operations should be "safe" or at least as safe as possible. Which means that things that can cause errors should not happen implicitly. This means that we generally don't want to allow mixing up types if they are "too different". So it's OK to write 1 + 2.3, but not 1 + "2.3" even though you could cast that string explicitly 1 + <float64>"2.3". This means that typically you can mix numerical types to some extent, but usually not any of the other types.
We generally want to allow mixing numerical types if we can cast them to whichever type has more precision. So it's always safe to upcast in this direction int16 => int32 => int64, but we can't assume that going in reverse direction is safe, so it needs an explicit cast. Similarly, we assume that you can go from float32 to float64, but not in reverse without losing data. For the same reason we don't implicitly cast from "unlimited precision" numbers like decimal or bigint to any of the other numerical types. If you want that, you need an explicit cast.
Assignments are special, they often happen when a user is providing the values in a query directly as literals and not as typed parameters. So we wanted to make it more convenient to write insert Foo{bar := 23, baz := "GREEN"} even when the properties bar and baz are not int64 and str, respectively, but int16 and some custom enum (that has GREEN as a valid value). This means that because when you write a number without any type information you get either int64 or float64 and these types will appear all the time in assignments to any of the numerical properties. So in order to make inserts less annoying for 99% of common cases we treat these two types as valid during assignment (such as insert or update) for all numerical types and we will cast them implicitly.

All of this means that in an insert you can assign 1234 to an int16 property, but not <int32>1234 to the same property.
On the other hand since we only have two float types and one of them is the default literal type you can assign that default literal to a float32 property as well.


<EMAIL_ADDRESS>decompress error

PS C:\Users\rfks\Downloads> scoop install twilio
Installing '7zip' (22.01) [64bit] from main bucket
7z2201-x64.msi (1,8 MB) [=====================================================================================] 100%
Checking hash of 7z2201-x64.msi ... ok.
Extracting 7z2201-x64.msi ... done.
Linking ~\scoop\apps\7zip\current => ~\scoop\apps\7zip\22.01
Creating shim for '7z'.
Creating shortcut for 7-Zip (7zFM.exe)
Persisting Codecs
Persisting Formats
Running post_install script...
'7zip' (22.01) was installed successfully!
Notes
Add 7-Zip as a context menu option by running: "C:\Users\rfks\scoop\apps\7zip\current\install-context.reg"
Installing 'twilio' (4.0.1) [64bit] from twilio-scoop bucket
twilio-win32-x64.tar.xz (32,3 MB) [===========================================================================] 100%
Checking hash of twilio-win32-x64.tar.xz ... ok.
Extracting twilio-win32-x64.tar.xz ... ERROR Exit code was 2!
Failed to extract files from C:\Users\rfks\scoop\apps\twilio\4.0.1\twilio-win32-x64.tar.
Log file:
~\scoop\apps\twilio\4.0.1\7zip.log
Please try again or create a new issue by using the following link and paste your console output:
https://github.com/twilio/scoop-twilio-cli/issues/new?title=twilio%404.0.1%3A+decompress+error

Hi @rfks , Thanks for reaching out. We've identified this issue internally and are working on it. Meanwhile, to unblock you can download the updated cli version from releases executables present here.

cheers @shrutiburman !

Hi @rfks ,
This has been fixed in our latest release 🚀.
Closing this issue, feel free to re-open if you're still facing this.


Register a key multiple times on the same environment with different scopes

Hi there,
I would propose to enhance the library to support the use case of registering a key twice with different scopes.
Our specific use case would be to be able to inject the same storage class with a read/write or read-only database connection depending on the scope of the injector used.
Example adjusted from the docs:
provider = Provider()

@provider.provides('database_connenction', scope='app')
def make_database():
    ....

@provider.provides('database_connenction_ro', scope='app')
def make_database_ro():
    ....

@provider.provides(ITodoItemStorage, scope='action')
def make_sqlite_todo_storage(injector):
    connection = injector.inject('database_connenction')  # (2)
    try:
        yield SQLiteTodoStorage(connection)  # (3)
    except Exception:
        connection.close()
    else:
        connection.commit()

@provider.provides(ITodoItemStorage, scope='action_ro')
def make_sqlite_todo_storage_ro(injector):
    connection = injector.inject('database_connenction_ro')  # (2)
    try:
        yield SQLiteTodoStorage(connection)  # (3)
    except Exception:
        connection.close()

Do you think this is feasible and a good enhancement?

Hi,
This is not what the scopes are meant to be used for. Scopes are just used to limit lifetime of injected objects (so f.e. cleanup actions can be executed when API call is done, not when entire server is shut down).
Instead, I suggest to split interfaces into smaller ones by following interface segregation principle. With smaller interfaces you will end up with distinct provider keys, and you will be able to inject implementation depending on interface type, like so far.
For example, you can change from this:
class IDatabaseConnection(abc.ABC):
   ...

to this:
class IDatabaseConnectionReadOnly(abc.ABC):
   ...

class IDatabaseConnection(IDatabaseConnectionReadOnly):
   ...

And now you should be able to do different things based on interface type:
@provider.provides(IDatabaseConnection, scope='app')
def make_database():
    ....

@provider.provides(IDatabaseConnectionReadOnly, scope='app')
def make_database_ro():
    ....

This is how I do this in my projects.
Alternatively, you could also try variants:
https://pydio.readthedocs.io/en/stable/api/keys.html#pydio.keys.Variant
And if my answer does not satisfy your needs, we can continue discussing your proposal here. I'm open for new ideas and will be thankful for any contributions to this tool.
BR,
Maciej

Thanks for the answer!
I see your point that my proposal contradicts the purpose of the scopes to limit the lifetime of an object.
I did not want to go for the variant injection keys as this would mean that within the same scope of an injector, we would introduce a pitfall of opening up two database connections if not being mindful.
E.g.
async with injector.scoped("action") as scoped_injector:
      storage_items = scoped_injector.inject(ITodoItemStorageRO) # creates a RO connection
      storage_actions = scoped_injector.inject(IActionStorage)  # created a second non RO connection. Not good!

I also thought about introducing a new environment flag while adding a scope but this is also not permitted. I think I will go the route of separate injection keys with variants bundled in a child injector so that everybody specifically either requests a RO db connection or a non-restricted connection.

Just one more thing that came to my mind...
I've once had a problem of delivering command line global params to injectors when using Click to create CLI app, and came out with following solution:
In providers I've declared something similar to this:
@provider.provides('params')
def make_params():
    return {}  # empty dict

@provider.provides(ISomeCommand, scope='action')
def make_command(injector):
    params = injector.inject('params')
    return SomeCommand(**params)

And command execution looked like this:
@click.group()
@click.option('--dry-run', ...)
def app(**kw):
    params = injector.inject('params')
    params.update(kw)

@app.command()
@click.option('--some-command-option', ...)
def some_command(**kw):
    return injector.inject(ISomeCommand).invoke(**kw)

I needed this to control dependency injectors depending on global flags like --dry-run, so I could detect (inside injector) that the command was run with that option, and based on that change the implementation of interface being injected. In other words, from the use case PoV it was completely transparent, but I could still modify the behavior of injectors without affecting business logic of the app.
Maybe this is what you are looking for? :-)

Thanks for that example and the help, this is also a good option! I will tinker with this a bit.
I think it is safe to say that this issue can be closed 👍


Support authenticating against an Escape inventory using Basic Auth

Support for basic authentication has now been added to the inventory (see: https://github.com/ankyra/escape-inventory/issues/12), which should make this easier to setup and test.

Added support for servers protected with Basic Auth to escape run login --url URL. Logging in using this method will validate the credentials and store them in the current profile if correct and then use those for all subsequent requests.
To enable programmatic access: the BASIC_AUTH_USERNAME and BASIC_AUTH_PASSWORD are now also supported on the client side (but only get used for new config profiles); as are the basic_auth_username and basic_auth_password configuration variables for config files and profiles.


We have no more pull requests to adopt

We’ve cleared the backlog of pull requests needing adoption and closed the old ones out, so it seems best to remove this from the contributing guidelines.

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS


Add HTTP Status Code constants

Migrate hardcoded numerals for status codes to constants from NPM library

Pull Request Test Coverage Report for Build 1742

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 88.103%

Totals

Change from base Build 1728:
0.02%

Covered Lines:
8126

Relevant Lines:
8941

💛  - Coveralls


Examination scheduling

When i solve using basic parameter, i got the result that some very first day in the available time for examinations have a lot of exams while the last few days in the available time literally don't have any exam, and more over some constraints like direct conflict or more than 2 A day conflicts have a big number, the easier way I can see that I can move some examination into the last few day which don't have much exam even no exam, so how can i do that with out do it manual by myself, is there any way to setup constraint to solve this problems?

for more specified, i have 14 days for examinations, the examination timetable i got for first 4 days is 931 over 1140 exam i already have(over 80% exam)

Quick question: Is the solver able to assign all exams? That is, on the Examination Timetabling Solver page, it shows 100% assigned variables? Most of the optimization happens only after the solver is able to place all exams.
If the solver is able to assign all exams, could you please share your data with me (using the Export XML button on the Examination Timetabling Solver page)?
If the solver is NOT able to assign all exams, you need to check the Not-assigned Exams (and/or the Conflicts Statistics) pages and fix the inconsistencies in the problem.

All exam have been assigned this is the result in XML(I cannot upload XML, so I zipped it)
exam-solution (3).xml.zip

Your problem is shaped by the Same Period distribution preferences. They are all required, and 1151 of your 1154 exams are present in at least one required Same Period preference. Besides generating a lot of direct conflicts that cannot be avoided, they also make it extremely hard for the solver to make local changes as each exam is, on average, required to be at the same period as 7 - 8 other exams. When I make all the Same Period preferences soft (preferred instead of required), the solver can quickly come up with a solution that has no student conflicts (no directs, no more than two exams on a day, no back-to-backs). But some of the Same Period preferences will remain not satisfied.
Also, by default, the solver tries to put each exam as early as possible in the examination week (it will pick the earliest possible period from those that are otherwise equal, e.g., have the same student conflicts). This can be avoided by setting the following two solver configuration parameters to zero:
Exam rotation weight (defaults to 0.001)
Examination period index weight (defaults to 0.0000001)

Closing the issue as no additional questions were provided.

FYI: In the most recent UniTime release (4.8.159), handling of soft distribution preferences has been significantly improved. Previously, a distribution was considered violated if any of the two exams in the constraint were in violation. In the new implementation, the penalization is based on how many examination pairs are violated. This helps the solver gradually decrease the number of violations during the search.
So, looking at your problem back from June, if all the Same Period distributions are made preferred instead of required, the solver is able to ensure that over 96% of examination pairs that are preferred to be in the same period are placed in the same period.


Revert "Reimplement hipMemGetInfo (#1447)"

This reverts commit 3d661e47068685abf0ba7723d562eca6d70794d7.

Closing this since there is no current plans to revert this on master branch.


One-off bug?

Using openfst 1.7.5, and pynini 2.0.9.post2, if I do:
words='you say potato'.split()

word_table = ni.SymbolTable()
word_table.add_symbol('<ε>')  # empty symbol at index 0
print(word_table.num_symbols())

for sym in words:
    word_table.add_symbol(sym)
    print(word_table.num_symbols())

I see output:
1
2
2
3

Thanks for very clear report; looks suspicious. Will investigate: would
probably be an issue with OpenFst itself. There has been some recent churn
in the symbol table object.
On Tue, Dec 17, 2019 at 5:21 PM Alexander Kain<EMAIL_ADDRESS>wrote:

Using openfst 1.7.5, and pynini 2.0.9.post2, if I do:
words='you say potato'.split()
word_table = ni.SymbolTable()
word_table.add_symbol('<ε>')  # empty symbol at index 0
print(word_table.num_symbols())
for sym in words:
word_table.add_symbol(sym)

print(word_table.num_symbols())

I see output:
1
2
2
3
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/pynini/issues/18?email_source=notifications&email_token=AABG4OIKOGFX6IT56DOJ53LQZFGGXA5CNFSM4J4CLG4KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IBFWTUQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABG4OLTNDSHW53J6BHZVVDQZFGGXANCNFSM4J4CLG4A
.

Should I try with openfst 1.7.4?

You could but I’m not sure it’d help track this down.
Unrelatedly almost all of this stuff is on Conda-Forge as of yesterday.
On Tue, Dec 17, 2019 at 5:32 PM Alexander Kain<EMAIL_ADDRESS>wrote:

Should I try with openfst 1.7.4?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/pynini/issues/18?email_source=notifications&email_token=AABG4ONIESW5ELUBXEDI2G3QZFHODA5CNFSM4J4CLG4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHEFZOI#issuecomment-566779065,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABG4OOO424BTIJLKOPJQS3QZFHODANCNFSM4J4CLG4A
.

I tried installing from conda-forge on a brand-new anaconda python 3.7 install. After about one hour I hit CTRL-C :(

Good news, this doesn't replicate at (internal) HEAD for me so we must have fixed it or, IDK, something else is going on. Will put out another version bump before too long.

This bug persists in version 2.1.0 :(
Incidentally, the conda-forge install works now!

Would you be willing to take a look? I absolutely cannot reproduce this as
I do not own any Macs and it doesn't seem to occur anywhere else.
On Mon, Feb 24, 2020 at 10:16 PM Alexander Kain<EMAIL_ADDRESS>wrote:

This bug persists in version 2.1.0 :(
Incidentally, the conda-forge install works now!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/pynini/issues/18?email_source=notifications&email_token=AABG4OMFI26ZK73FVWXAOJTRESEQ5A5CNFSM4J4CLG4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM2MQNY#issuecomment-590661687,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABG4OLEHNHVSTQGZX67P4DRESEQ5ANCNFSM4J4CLG4A
.

I ran this in an ubuntu VM and indeed it works fine! Very puzzling. I'm not sure if I will have the time to debug this, and I can use Linux as a work-around for the time being.

CFLAGS="-stdlib=libc++ -mmacosx-version-min=10.7" python setup.py install
fixes this


python3.pkgs.ambee: don't re-distribute package

Closes https://github.com/NixOS/nixpkgs/issues/126677

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 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

[ ] Fits CONTRIBUTING.md.

This incorrectly marks fixing #126677.
#126677 requests removal.

This incorrectly marks fixing #126677.
#126677 requests removal.

I disagree, you requested nixpkgs not to re-distribute the package. This change makes the package build only on the end-user machine.

I disagree, you requested nixpkgs not to re-distribute the package.

That was before you just ignored future communication and merged (even worse: an incompatible version).
Please remove it as requested. I don't want anything of myself to be associated with this project as of now.

Locked for now. Please see https://github.com/NixOS/nixpkgs/issues/126677#issuecomment-860071285. Please don't merge this until everyone's had a chance to cool off.


Something went wrong reported directly after windows login

Microsoft PowerToys version
"<IP_ADDRESS>"
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce

Install PowerToys
Have no problems for years.
One day boot a computer with PowerToys installed.

Bug report log attached.
PowerToysReport_2022-06-17-18-56-03.zip
✔ Expected Behavior
Silence
❌ Actual Behavior
3 windows headed with "Something went wrong."
Other Software
None I am aware of. This seems to be an error confined to PowerToys

Likely #18275
Did it occur only once? /needinfo


Random fixes

That's it, random fixes. I was to lazy to make commits explaining each one.

I didn't see anything in there that is really a fix, but still they are nice improvements. Thanks.


Fix aes cfb1 so that it can operate in bit mode.

The code to handle the cipher operation was already in the provider.
It just needed a OSSL_PARAM in order to set this into the algorithm.
EVP_CIPHER_CTX_set_flags() has been modified to pass the OSSL_PARAM.
Issue reported by Mark Powers from Acumen.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Made this a draft because documentation is still needed for the new parameter, but this should be only done after the cipher documentation PR has been merged.

NOTE: There is now a bit of a problem using the EVP_CIPHER_CTX_set_flags() in that it has to be done AFTER the cipher has been attached to the cipher_ctx. Before it just set ctx->flags but now it needs access to ctx->cipher->set_ctx_params()..

This pull request is ready to merge

It depends on the documentation.  If it's going to be part of this, it isn't ready to merge.  If it will be a separate PR, this is ready.

Updated documentation now that the "Update cipher documentation" PR has been merged. Changes are in the last 2 commits.

ping

This pull request is ready to merge

Merged to master.
Feel free to add another PR that changes the name if required.


"Error: BacnetError - Class:5 - Code:67"

Node Version:12.16.1
Node BACstack Version: 0.0.1-beta.22
Hey together,
I am running the bacstack with a Siemens DXR2 Room Automation Device and I can greatly read all my data.
But I can not write data. With the bacstack V0.0.1-beta.14 I always got the result "undefined" and I couldn't figure out what is the problem.
Now I receive "Error: BacnetError - Class:5 - Code:67" which is probably because of better error handling. Based on the handbook it is a "reject unrecognized Service" but no clue what to do with this message or where to search.
Also already had a look in here:
https://github.com/fh1ch/node-bacstack-browser/issues/2
But no help for me yet.
Anybody has Ideas on this?
Greets
Tom

@tstockner I had the same problem. It worked very well in early version and than it was broken. A very first quick read inside the code it looked like there is now a routing inside which is not finished for all or not working well for every request type.


Error signal arrived during external code execution on Windows 10

What OS are you using (uname -a, or Windows version)?
Windows 10 Enteprise 64bit
What programming language are you using (C/C++/Go/Rust)?
go version go1.14.3 windows/amd64
TDM-GCC-64
What did you expect to see and what you saw instead?
The library works well on MacOS and Linux (Ubuntu). But when I tried to run this example code on Windows 10
package main

import "github.com/zserge/webview"

func main() {
	debug := true
	w := webview.New(debug)
	defer w.Destroy()
	w.SetTitle("Minimal webview example")
	w.SetSize(800, 600, webview.HintNone)
	w.Navigate("https://en.m.wikipedia.org/wiki/Main_Page")
	w.Run()
}

It crashes like this
API server listening at: <IP_ADDRESS>:39131
Exception 0xe06d7363 0x19930520 0xa8f690 0x7ffa653a3c58
PC=0x7ffa653a3c58
signal arrived during external code execution
github.com/zserge/webview._Cfunc_webview_create(0x1, 0x0, 0x0)
	_cgo_gotypes.go:121 +0x55
github.com/zserge/webview.NewWindow.func1(0x57bb01, 0x0, 0x0)
	D:/Work/SoftwareDefinedPerimeter/Projects/src/github.com/zserge/webview/webview.go:162 +0x88
github.com/zserge/webview.NewWindow(0x40ed01, 0x0, 0x0, 0x0)
	D:/Work/SoftwareDefinedPerimeter/Projects/src/github.com/zserge/webview/webview.go:162 +0x7f
github.com/zserge/webview.New(0xc00013c301, 0x0, 0x0)
	D:/Work/SoftwareDefinedPerimeter/Projects/src/github.com/zserge/webview/webview.go:152 +0x42
main.main()
	D:/Work/SoftwareDefinedPerimeter/Projects/src/my-example-project/main.go:11 +0x44
rax     0x0
rbx     0x7ffa458a9328
rcx     0x0
rdi     0x19930520
rsi     0xa8f690
rbp     0xa8fd70
rsp     0xa8f3c0
r8      0x0
r9      0x0
r10     0x0
r11     0x0
r12     0x2030000
r13     0x0
r14     0x30
r15     0x0
rip     0x7ffa653a3c58
rflags  0x204
cs      0x33
fs      0x53
gs      0x2b
Process exiting with code: 0

I have no idea now :( Can you help me to fix this. Thanks!

Are you still experiencing this error?

Not OP, but still seeing this issue today, right after installing the Webview2 runtime. I built webview.dll from source using the script, and edgeHTML was working before installing webview2. In my case, I want to require Edge Chrome.
Would be grateful if anyone can confirm they got this to work against the current webview2 runtime (not just the insider build). Thanks.

Debugged this, and the current crash at least was caused by using multi-threaded mode, which isn't supported by webview2. They added a check for this, which is why the previous 0.9 dll worked. Submitted a PR to fix this here.

@chenilim or @tunggiga Is this issue fixed for you? I am not experiencing it. I will reopen if it is still a problem.


The performance of flask-sqlalchemy

Hei guys:
I write  a model which has a foreign key,but it's query speed is very slow!
The code is:
class StationLine(db.Model, BaseMixin):
id         = db.Column(db.Integer, primary_key=True)
station_id = db.Column(db.Integer, db.ForeignKey('station.id'))
station    = db.relationship("Station", foreign_keys=[station_id], backref="lines")
start_date = db.Column(db.DATETIME, default=datetime.datetime.utcnow())
end_date   = db.Column(db.DATETIME, default=datetime.datetime.utcnow())
reads = StationLine.query.all()
print reads
The StationLine table only got 900 records(mysql).
When i remove the station_id,it's being very fast!
Is it normal?Or is there some solutions to improve the speed?...
Sorry for my poor english...

Hei


Add correlation_id field to file_event_log

Add the RabbitMQ message correlation ID header as a field in the file_event_log. This is useful for keeping track of which file is being processed when cancel and re-ingest messages are sent from central EGA.
AC:

[x] Add correlation ID field to file_event_log
[ ] Create migration for update

Hey team! Please add your planning poker estimate with Zenhub @aaperis @dbampalikis @jbygdell @kostas-kou @viklund


Link delegate

https://github.com/vuejs/vue-router/issues/140
v-link has delegate feature now.
I can't implement the test case correctly.

gr8


Fetch error: 404 Instantiating https://.../public/plugins/grafana-bigquery-datasource/module.js

grafana used : grafanaoss:9.1.0 running in GCP Kubernetes.
we are seeing below error when trying to install bigquery datasource from the UI as a server admin.
Error :
"Fetch error: 404 Instantiating https://.../public/plugins/grafana-bigquery-datasource/module.js Loading plugins/grafana-bigquery-datasource/module"

Hi @pxn83q5,
Thanks for opening this issue. Can you please check if you can install any other plugin through the ui?

I'm going to close this issue as there was no response.


[NOT A BUG BUT I NEED HELP] Resource pack conversion

I am attempting to convert the resource pack for geyser following your steps through java2bedrock but it keeps failing. Is there any way you can provide help with this? It has to do with the structure of the resource pack when generated by polymer. Thank you in advance!

Should probably made it more clear that geyser doesn't support the way polymer makes these item models work on 1.21.2+.

Should work if you are using 1.21.1.

I gotcha, I'm using 1.21.4 so it won't work yet


feat: AdjustIndex preserves existing filter

Closes #710

:tada: This PR is included in version 6.12.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Support embedded anonymous property structs

Allow property structs to contain anonymous embedded structs and
interfaces.  Properties in an anonymous embedded struct or interface are
treated as if they were properties in the embedding struct.

LGTM

Added one more patch to prevent errors when the docs generator came across anonymous embedded structs.

LGTM


Setting min script chunk time to 15 seconds

Currently, chunks of scripts can run up to 4 minutes, but there is no hard minimum duration. These changes now require that the minimum be at least 15 seconds.

Almost forgot to ask for test updates to reflect these code...  Would appreciate those, thank you! :D

Awesome!  Thank you very much!  LGTM here, asking for a second approval from @gwsii

Thanks for the contribution @glee2244 !

Uh oh. @erikerikson I just realized that this creates some technical debt.
@glee2244 can you please submit a PR to add yourself to the list of contributors in the package.json?
Thanks! :+1:

Indeed!  Haha.  That field in the package.json is almost never updated...  Don't let it hold up any plans if you don't have capacity @glee2244 !  :D


Added various games to COMPAT.md

Added entries for Blood: Fresh Supply, Geometry Dash, Getting Over It with Bennet Foddy, Katamari Damacy Reroll, Quake 2, Terraria, and Transformice.

Thanks!

Transformice is flash player so it's only x86 iirc.
The architect is the application architecture not the app arch. The app arch doesn't matter as x64 injects both while x86 can only inject x86.


FOGL-2513 wiringpi apt package added into control file

sudo apt install /var/cache/apt/archives/foglamp-south-ina219-1.5.0-armhf.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'foglamp-south-ina219' instead of '/var/cache/apt/archives/foglamp-south-ina219-1.5.0-armhf.deb'
The following additional packages will be installed:
  wiringpi
The following NEW packages will be installed:
  foglamp-south-ina219 wiringpi
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 47.1 kB/55.3 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://archive.raspberrypi.org/debian stretch/main armhf wiringpi armhf 2.46 [47.1 kB]
Fetched 47.1 kB in 1s (36.9 kB/s)
Selecting previously unselected package wiringpi.
(Reading database ... 49837 files and directories currently installed.)
Preparing to unpack .../wiringpi_2.46_armhf.deb ...
Unpacking wiringpi (2.46) ...
Selecting previously unselected package foglamp-south-ina219.
Preparing to unpack .../foglamp-south-ina219-1.5.0-armhf.deb ...
Unpacking foglamp-south-ina219 (1.5.0) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Processing triggers for man-db (<IP_ADDRESS>-2) ...
Setting up wiringpi (2.46) ...
Setting up foglamp-south-ina219 (1.5.0) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...

As per discussion; we do not need this in 1.5.0 release. So changed base branch to develop


Slick Slider cloned slide images not loading properly in production (AWS)

In my production environment  i'm getting an error where the images in my slides with the '.cloned' class aren't loading. In their place is an empty .svg. In my staging environment this issue isn't happening at all.

More Details

Which browsers/versions does it happen on?

This is only happening in Chrome and Firefox

Which jQuery/Slick version are you using?

Running 1.8.1

Did this work before?

Yes it works in the dev and staging environments

changing my "src" attribute to "data-lazy" fixed this


Only increase unread counter for whitelisted actions

Fixes #271. Only three actions whitelisted because only these actions increase the unread counter on the server, and we must follow the exact same rules.

👍
Note: this is the mentionned only place where it is incremented: https://github.com/thelounge/lounge/blob/master/src/plugins/irc-events/message.js#L67-L73

👍 and merging, nice catch!


Could you release the finetuned checkpoints and retrieved results (i.e. the input file for evaluation)?

Hi, I am trying to re-implement this project according to README. Unfortunately, the final results are slightly worse (spice -0.01) than provided results (t5.test in this repo). Could you release the fine-tuned checkpoints and the input file (with retrieved auxiliary results) for evaluation?

Thanks for your interest in our work! Since this work was done during my internship at Microsoft, I don't have checkpoints right now. In addition, I think the error of 0.01 is acceptable.


Add support for aws_grafana_workspace_service_account* resources

Is your request related to a new offering from AWS?
Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

Yes ✅: introduced in AWS provider v5.59.0

Is your request related to a problem? Please describe.
I would like to be able to create service accounts using Terraform
Describe the solution you'd like.
A similar method to the existing API token configuration would likely make most sense
Describe alternatives you've considered.

Additional context
These resources are available from aws provider version 5.59.0
New Resource: aws_grafana_workspace_service_account (https://github.com/hashicorp/terraform-provider-aws/issues/38101)
New Resource: aws_grafana_workspace_service_account_token (https://github.com/hashicorp/terraform-provider-aws/issues/38101)

This issue has been resolved in version 2.2.0 :tada:


Add OpenTelemetry banner to the OpenTracing website

Just making sure folks can find what they need.

https://github.com/opentracing/opentracing.io/pull/433

Done


Fix set episode(s)

Motivation and Context
Makes things like env.current_episode = ... and env.episodes = ... actually work!
How Has This Been Tested
Via the test
Types of changes

Bug fix (non-breaking change which fixes an issue)

Looks good to me. Let's merge.


Adds check for blank password

https://github.com/rancher/rancher/issues/5973

@yasker FYI

@cjellick ?


[jvm-packages] Early stopping incorrectly splits data for ranking tasks

The new early stopping code in jvm-packages splits the dataset into test/train groups on a per-row basis. Because we have to provide the group data in a separate Seq[Seq[Int]] the group data is no longer correct after the test/train split. This prevents the usage of early stopping for ranking tasks.
Something like issue #2748 may provide a good way to support this in the future, although i still think users might want to make the choice between a completely arbitrary split (breaking up groups between test/train) and keeping whole groups in either test or train side of the split.

Good catch! I agree that a good first step to address this is to get rid of the Seq[Seq[Int]] hack. As for groupwise sampling, this should be possible afterwards, because we would be able to repartition with groups in mind and then either accept or reject the whole group.


Execute E2E on dev.plermaplant.net

Yes they get performed only on pr.permaplant.net.
Maybe we would want to run them on dev.permaplant.net when merged to master?

Originally posted by @4ydan in https://github.com/ElektraInitiative/PermaplanT/pull/846#discussion_r1302986695

Yes, this is a good idea as there are no other tests before the release.
Such errors are unlikely, though, so I don't think this is high-prior.

Shouldnt we remove the two stages Deploy PR and E2E tests for PR in the master branch?

Maybe it would be best to write a separate Jenkinsfile for the master pipeline.

Shouldnt we remove the two stages Deploy PR and E2E tests for PR in the master branch?

Yes, once we have proper dev E2E test, it does not make sense that way.

Maybe it would be best to write a separate Jenkinsfile for the master pipeline.

As it is best for you.


dependency not installable with yarn without git

Currently, react-trello can't be installed through yarn if git is not available (which could easily happen in a CI environment or when running your dev environment in a docker container). The reason is probably the https dependency on the fork of smooth-dnd here: https://github.com/rcdexta/react-trello/blob/master/package.json#L49
Which leads to
# yarn add -D -E<EMAIL_ADDRESS>yarn add v1.10.1
[1/4] Resolving packages...
error Couldn't find the binary git
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

I'm not sure if this was intentional?

Any update on this?

I have the same problem. @dapi will you do smth with that?
I want to use your library, but this bug. A lot of people used yarn with docker. I guess it should be changed.

Add this line in your Docker file
RUN apk add --no-cache git
before your yarn commands

Mentioned package is replaced


Update version from 0.0.0 to 0.0.10

Looks fine, but where did we get the version 0.0.10?

I had asked @bricerisingalgorand about that, and he said that we've been bumping the patch number until we get to the 1.0.0 release.


Android crashs on start. No static method zzic

I've updated react-native "react-native": "^0.29.2" and also added the maps react-native-maps:0.7.1. Now the Android-App does not start anymore.
"Unfortunately, MyApp has stopped."
pidcat:

I have no clue what this stacktrace wants to tell me.

I'm getting the same error.
It might be working with another play-services version, as suggested here: https://github.com/googlemaps/android-maps-utils/issues/258

@dbanck That's it! I made sure all play-services-* in all packages were the same version and it worked.

Same error, changed my app/build.gradle to :
    compile 'com.google.android.gms:play-services-auth:9.4.0' // should be at least 9.0.0
    compile 'com.google.android.gms:play-services-maps:9.4.0'

fix the issue

In my case it helped to set the version in my app/build.gradle like that, which forces to use this version.
compile ('com.google.android.gms:play-services-gcm:8.4.0') {  force = true;  }

Just in case you are not able or don't want to upgrade.

I write whole article about this problem:
<EMAIL_ADDRESS>Hope I helped you :)


include  patchelf.rb and its deps in Gemfile.lock

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

Includes patchelf.rb and its deps in Gemfile.lock .
Request @
https://github.com/Homebrew/brew/pull/7996#issuecomment-657922970
cc @jonchang @MikeMcQuaid @sjackman @woodruffw

1 of the test is failing.

anyone actually using the functionality will have the right gems installed on demand.
This seems to be the case according to the test on my host,

reporting back soon after tests on docker ...

Gemfile needs to be updated to remove the conditional dependency based on HOMEBREW_PATCHELF_RB, as I laid out in the other issue.

This will result in the same Gemfile.lock issue people are seeing with HOMEBREW_DEVELOPER happening for all non-HOMEBREW_DEVELOPERs. That doesn't seem to be a solution as it will affect/annoy more people.

sorry, can you expand on this ?

Gemfile needs to be updated to remove the conditional dependency based on HOMEBREW_PATCHELF_RB, as I laid out in the other issue.

@jonchang .
Why is that a requirement?
we only wish on devs.

We still wish only to force it on devs

We can't really do that without the current problems. Let's remove the conditional Gemfile``if ENV["HOMEBREW_PATCHELF_RB"] and install it unconditionally in Gemfile.lock.

 If you change the Gemfile.lock without also changing the Gemfile to remove the conditional, you’ll get a dirty Gemfile.lock when you do not have HOMEBREW_DEVELOPER=1 set, that is, for all non-developer users. We want to update the Gemfile.lock as your PR 8034 does but also remove the conditional from Gemfile. I believe we also want to vendor the patchelf.rb gem and its dependencies, and remove the logic to install this gem.
The feature would continue to be enabled only when HOMEBREW_DEVELOPER=1 is set, but the gem would be installed for everyone.

@MikeMcQuaid At what point is patchelf.rb vendored into Homebrew/brew? In this PR, or in a subsequent PR?

@MikeMcQuaid At what point is patchelf.rb vendored into Homebrew/brew? In this PR, or in a subsequent PR?

@sjackman I'd think when we're at the point that patchelf.rb is enabled for everyone and we remove the HOMEBREW_PATCHELF_RB variable.


misleading error message: must not be a relative path

Regarding
https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/src/Batch/FileConventions/Src/AzureBatchFileConventions/StoragePath.cs#L64
            if (Path.IsPathRooted(relativePath))             {                 throw new ArgumentException($"{nameof(relativePath)} must not be a relative path", nameof(relativePath));             }
Shouldn't this say "must be a relative path"?

see PR #2540

@peter172sp Yes, I believe that it should.

@matthchr it looks like this didn't make it through. Do we want to make this change?

Discussed with Matt in person and he informed me that these changes were made locally and should be in the next release.

This is fixed in the 3.2 drop of Microsoft.Azure.Batch.Conventions.Files - @shahabhijeet can you close?


use JWK Algorithm instead of config Alg

Hi,
I have a situation, which there are different JWKs with different algorithms. I sign my tokens with them in random style for more security, but in KrakenD for validating them I must declare the Alg attribute in the config, which can be replaced by the JWK algorithm as the default value.
So applying this change adds a lot of flexibility for validating the tokens.

Actually I found that the issue is related to auth0-go package so I am closing it.


Fix L<EVP_KDF-derive> to L<EVP_KDF_derive>

This could actually something for find-doc-nits, to only allow normal symbols for (3), i.e. for any link that anything that matches /L<(?:.*?|)(.+?)\(3\)(?:/.*)?>/, $1 must match /^[_[:alpha:]][_[:alnum:]]*$/
I think those regexps are correct, but haven't test.  Feel free to play with them.

Merged to master, thanks!

86913ef711 Fix L<EVP_KDF-derive> to L<EVP_DEF_derive>


Export

Purpose
Add the possibility to export the system to MoorDyn (MoorDyn-C actually)
Type of change
What types of change is it?

[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (non-backwards-compatible fix or feature)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Documentation update
[ ] Maintenance update
[ ] Other (please describe)

Testing
Just go to the MoorDyn associated PR, and on the tests/Mooring folder execute the tool moorpy_ic.py
Checklist

[X] I have run existing tests which pass locally with my changes
[ ] I have added new tests or examples that prove my fix is effective or that my feature works
[ ] I have added necessary documentation

Apparently you prefer to keep this out from MoorPy, but implement it on MoorDyn. We have done that:
https://github.com/FloatingArrayDesign/MoorDyn/pull/244
Anyway, please cherry-pick https://github.com/NREL/MoorPy/pull/30/commits/5c6e3c9267872a7f1819d7062bf1f07f48c16787

I am closing this in favor of #31


Correctly return newly persisted Schema ID - Fixes #340

Tests are failing, have converted to Draft PR

Please, squash and force push

Merged.
Thanks for your contribution !


Any way to select branch of repo?

Hey, according to docs, New deployments will be triggered automatically on code changes to the default branch of the repo.
However my target code is in the staging branch of the repository. Any way I can tell Cyclic to use that for deploys?
Thanks

Once deployed goto the dashboard, select your app and then: Environments > Auto-Deployments > Branch Name


Update node-sass

Update node-sass to latest version ^9.0.0. Node-sass has archived and this is the latest version for this package.


Box Alignment no centered on bootstrap 4

Sorry for the late response,
I've not tested this on bootstrap 4, i will get it done asap

fc4bab4 Added Bootstrap v4 support


Some columns do not show in View - Redshift

View columns do not show when expanding columns - however they do show on query result

@ARod001 could you provide a table and view DDLs that will help to reproduce an issue?
also, which dbeaver version do you use?
Is the issue reproducible for all the views or only with some special?

Thanks Dziyana

I don’t think so – I can provide a screenshot though (below).
Version <IP_ADDRESS>104042040
All views

It seems like the columns missing are DATE data types.
@.***D73765.6FF4AE90]
Alberto Rodriguez
Business Analyst
Commercial Services - USNG
desk:<PHONE_NUMBER>  mobile:<PHONE_NUMBER>
TC Energy.comhttps://www.tcenergy.com/
From: Dziyana @.>
Sent: Thursday, April 22, 2021 3:51 AM
To: dbeaver/dbeaver @.>
Cc: Alberto Rodriguez @.>; Mention @.>
Subject: [EXTERNAL] Re: [dbeaver/dbeaver] Some columns do not show in View - Redshift (#12204)
@ARod001https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ARod001&d=DwMCaQ&c=Q5SXlsxPryShfyrkNJViwkWBHuTWASXd1LyNpDogBFY&r=5FaM3O5EoFL10otWsbciM-wmUiowDpzvuuWxuZ8JLsQ&m=vToe7LV98xbIH0JFVkXH1nekexVuFAaIrpv70E5cMxg&s=Nluep_SCZVV7f3n01Soc_iLGcwm_6jJ65KspCQNBNp8&e= could you provide a table and view DDLs that will help to reproduce an issue?
also, which dbeaver version do you use?
Is the issue reproducible for all the views or only with some special?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_dbeaver_dbeaver_issues_12204-23issuecomment-2D824662886&d=DwMCaQ&c=Q5SXlsxPryShfyrkNJViwkWBHuTWASXd1LyNpDogBFY&r=5FaM3O5EoFL10otWsbciM-wmUiowDpzvuuWxuZ8JLsQ&m=vToe7LV98xbIH0JFVkXH1nekexVuFAaIrpv70E5cMxg&s=DmbNFsvdYbbEOPsyQ4sYO6kZaVPE08bjBck2_WmUUZI&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ATZCYCJIV3ZA3HJZ5TNUUE3TJ7PP3ANCNFSM43LGF7OA&d=DwMCaQ&c=Q5SXlsxPryShfyrkNJViwkWBHuTWASXd1LyNpDogBFY&r=5FaM3O5EoFL10otWsbciM-wmUiowDpzvuuWxuZ8JLsQ&m=vToe7LV98xbIH0JFVkXH1nekexVuFAaIrpv70E5cMxg&s=zu5vgX5PCjYWc4Zd1azt02c_Zair2_yQw0cv2bgh1kc&e=.

We respect your right to choose which electronic messages you receive. To stop receiving this and similar communications from TC Energy please Click here to unsubscribe.
If you are unable to click the request link, please reply to this email and change subject line to "UNSUBSCRIBE".
This electronic message and any attached documents are intended only for the named addressee(s). This communication from TC Energy may contain information that is privileged, confidential or otherwise protected from disclosure and it must not be disclosed, copied, forwarded or distributed without authorization. If you have received this message in error, please notify the sender immediately and delete the original message.
Thank you

May be some connection is with this ticket https://github.com/dbeaver/dbeaver/issues/10703

I saw that but it was closed and resolved and it did not seem to apply.  Issue is still happening as described
Alberto Rodriguez
Business Analyst
Commercial Services - USNG
desk:<PHONE_NUMBER>  mobile:<PHONE_NUMBER>
TC Energy.comhttps://www.tcenergy.com/
From: Anastasiya @.>
Sent: Friday, April 23, 2021 9:27 AM
To: dbeaver/dbeaver @.>
Cc: Alberto Rodriguez @.>; Mention @.>
Subject: [EXTERNAL] Re: [dbeaver/dbeaver] Some columns do not show in View - Redshift (#12204)
May be some connection is with this ticket #10703https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_dbeaver_dbeaver_issues_10703&d=DwMCaQ&c=Q5SXlsxPryShfyrkNJViwkWBHuTWASXd1LyNpDogBFY&r=5FaM3O5EoFL10otWsbciM-wmUiowDpzvuuWxuZ8JLsQ&m=CcVOapXctABc3xf7moX35oy0cGbf-OBXLsfjFsQNElQ&s=Yy7OosAzLrRBtWhU_o_LwAXUGk8oaaH4MwXaLNVVeGc&e=
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_dbeaver_dbeaver_issues_12204-23issuecomment-2D825696625&d=DwMCaQ&c=Q5SXlsxPryShfyrkNJViwkWBHuTWASXd1LyNpDogBFY&r=5FaM3O5EoFL10otWsbciM-wmUiowDpzvuuWxuZ8JLsQ&m=CcVOapXctABc3xf7moX35oy0cGbf-OBXLsfjFsQNElQ&s=6o9N22ZdtSbgZXcwY9XlKDTlg6F2CaFLOsoNl9F4pN4&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ATZCYCIK3JIIHRV2NNCFR33TKF7SXANCNFSM43LGF7OA&d=DwMCaQ&c=Q5SXlsxPryShfyrkNJViwkWBHuTWASXd1LyNpDogBFY&r=5FaM3O5EoFL10otWsbciM-wmUiowDpzvuuWxuZ8JLsQ&m=CcVOapXctABc3xf7moX35oy0cGbf-OBXLsfjFsQNElQ&s=lCOcgz-1zQrDl_FrE0QnypW2OA053RMJZLhFLl19hu0&e=.

We respect your right to choose which electronic messages you receive. To stop receiving this and similar communications from TC Energy please Click here to unsubscribe.
If you are unable to click the request link, please reply to this email and change subject line to "UNSUBSCRIBE".
This electronic message and any attached documents are intended only for the named addressee(s). This communication from TC Energy may contain information that is privileged, confidential or otherwise protected from disclosure and it must not be disclosed, copied, forwarded or distributed without authorization. If you have received this message in error, please notify the sender immediately and delete the original message.
Thank you

Can't reproduce with date type column.

Can you attach here (in Github) your screenshot manually please? I can't see it in your email-version answer.

there is no update on an issue for a long time.
If it is still actual for you, feel free to reopen an issue


[libunwind] update to 1.8.1

Solved https://github.com/microsoft/vcpkg/pull/37268

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[ ] The "supports" clause reflects platforms that may be fixed by this new version.
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Thanks for the update and removing the unneeded vcpkg-cmake dependency :)


Update Issue - 70192905

default description
URL tested: http://ci.bsstag.com/welcome
Open URL on Browserstack

Property
Value

Browser
Chrome 78.0

Operating System
Windows 8.1

Resolution
1200x710

Screenshot Attached
Screenshot URL

Click here to reproduce the issue on Browserstack

Updated Screenshot Attached


How to use a cusom datepicker with it?

How to use a custom datepicker for set a startDate field value?

You have to create a custom Trait


How to get client remote ip address?

How to get client ip address?

are you looking for req.serverRequest.conn.remoteAddr ??

Yes thanks!


🐛 [Bug]: id is not binding

Environment
edge
Version
latest
Version
latest
Link to minimal reproduction
id is not binding
Step to reproduce

What is expected
No response
What is actually happening
No response
Any additional comments (optional)
No response

非bug，这两个id是不同的含义。一个是设计器自己对每个shema设定的内部id，一个是前端含义上元素的id。不是同个东西


xferfcn_test test_pole_mimo fails on arm and powerpc

As a continuation of my efforts to provide packages of python-control and slycot for OpenSUSE ( see python-control/Slycot#82 and python-control/Slycot#83), python-control now starts to build (because python-slycot is avaialble now) but fails on test_pole_mimo in xferfcn_test.py:
[  269s] ======================================================================
[  269s] FAIL: Test for correct MIMO poles.
[  269s] ----------------------------------------------------------------------
[  269s] Traceback (most recent call last):
[  269s]   File "/home/abuild/rpmbuild/BUILD/control-0.8.2/control/tests/xferfcn_test.py", line 415, in test_pole_mimo
[  269s]     np.testing.assert_array_almost_equal(p, [-2., -2., -7., -3., -2.])
[  269s]   File "/usr/lib64/python2.7/site-packages/numpy/testing/_private/utils.py", line 1017, in assert_array_almost_equal
[  269s]     precision=decimal)
[  269s]   File "/usr/lib64/python2.7/site-packages/numpy/testing/_private/utils.py", line 754, in assert_array_compare
[  269s]     raise AssertionError(msg)
[  269s] AssertionError:
[  269s] Arrays are not almost equal to 6 decimals
[  269s]
[  269s] (shapes (6,), (5,) mismatch)
[  269s]  x: array([-1.999985+0.000000e+00j, -2.000007+1.271532e-05j,
[  269s]        -2.000007-1.271532e-05j, -7.      +0.000000e+00j,
[  269s]        -3.      +0.000000e+00j, -2.      +0.000000e+00j])
[  269s]  y: array([-2., -2., -7., -3., -2.])

_common_den() strikes again (#194, #206). I see it has the optional argument imag_tol, but it is never used within the function except where it is set to 1e-8 by default.
Any ideas how to fix this? Is the resulting machine precision on theses arches really worse than the x86 build, where this tests fine? Or is there maybe a problem with the slycot / lapack / (open)blas / numpy environment on those build machines?

Ignore my last question about slycot. It is not even used in _common_den().
Only  numpy.roots() involved in returning complex poles...

Assuming that the problem comes down to a difference in precision between architectures, what is the best way to fix this?  One possibility would be to introduce a configuration variable for the error tolerance that get used as a default and then this could be set in the test scripts for different architectures (?).

numpy.finfo().eps as used in _common_den()  should be enough to derive the necessary information.
Have look at this one:
    def test_pole_mimo(self):
        """Test for correct MIMO poles."""

        sys = TransferFunction([[[1.], [1.]], [[1.], [1.]]],
                               [[[1., 2.], [1., 3.]], [[1., 4., 4.], [1., 9., 14.]]])
        p = sys.pole()

        try:
            np.testing.assert_array_almost_equal(p, [-2., -2., -7., -3., -2.])
        except AssertionError as e:
            print("EPS: {}".format(np.finfo(float).eps))
            for i in [0, 1]:
                for j in [0, 1]:
                    print("Roots of sys.den[{}][{}]:".format(i, j))
                    print(np.roots(sys.den[i][j]))
            numc, denc, denorderc = sys._common_den()
            print("Common Den:")
            print(denc)
            raise e

[   78s] ...................F..........
[   78s] ======================================================================
[   78s] FAIL: Test for correct MIMO poles.
[   78s] ----------------------------------------------------------------------
[   78s] Traceback (most recent call last):
[   78s]   File "/home/abuild/rpmbuild/BUILD/control-0.8.2/control/tests/xferfcn_test.py", line 426, in test_pole_mimo
[   78s]     raise e
[   78s] AssertionError:
[   78s] Arrays are not almost equal to 6 decimals
[   78s]
[   78s] (shapes (6,), (5,) mismatch)
[   78s]  x: array([-1.999985+0.000000e+00j, -2.000007+1.271532e-05j,
[   78s]        -2.000007-1.271532e-05j, -7.      +0.000000e+00j,
[   78s]        -3.      +0.000000e+00j, -2.      +0.000000e+00j])
[   78s]  y: array([-2., -2., -7., -3., -2.])
[   78s] -------------------- >> begin captured stdout << ---------------------
[   78s] EPS: 2.22044604925e-16
[   78s] Roots of sys.den[0][0]:
[   78s] [-2.]
[   78s] Roots of sys.den[0][1]:
[   78s] [-3.]
[   78s] Roots of sys.den[1][0]:
[   78s] [-1.99999999 -2.00000001]
[   78s] Roots of sys.den[1][1]:
[   78s] [-7. -2.]
[   78s] Common Den:
[   78s] [[ 1.  6. 12.  8.]
[   78s]  [ 1. 12. 41. 42.]]
[   78s]
[   78s] --------------------- >> end captured stdout << ----------------------

Maybe sqrt(eps)  (or precision/2) would do the trick?
But I still not fully understand that _common_den algorithm. How would it have to be modified to recognize den[1][0]  as a polynomial with a double root?

I'm not an expert on this, but my sense is that computing common denominators for MIMO transfer functions is often ill-conditioned.  @repagh and @roryyorke are have more expertise here.

Ok, @repagh, @roryyorke,  please have a look at my take in #345. Changing threshold whether we already have the root or not to sqrt(eps) fixes the test failure.
I also changed the logic to actually do something with imag_tol. That last warning in the function never would have triggered because den is only assigned polyfromroots().real further above.

Fixed in PR #345


Using Custom Layout - No JavaScript on the footer to Populate the Read table

First of all, great project!
Tried to extend the one of my own layouts using the command below
php artisan make:crud all --master-layout=layouts.mylayout
Seems to work great overall, adding records works, however, it's missing the JavaScript in the footer that populates from ajax request and fills the records list table.
Is there a particular section I need in my master layout file for this to work other than @yield('content')?

OK, so it does seem to need @yield('scripts') in addition, but it still doesn't generate dataTables javascript includes, so it needs to be added to the layout manually.
It might be a better idea to include this in a separate file as an include to add in the layout I guess, but then it may interfere with other bootsrap includes above.

I'm glad you resolved, yeah probably at least I need to put some documentation to let know this. Sorry for the delay to answer :)


sanityinc/consult-ripgrep-at-point can't work with C-u

Dear @purcell ,
When i use C-u M-? to call sanityinc/consult-ripgrep-at-point, the variable prefix-arg in the function is nil. I'm not sure if this is just an error specific to my environment or if we should be using the current-prefix-arg variable here.
emacs version: GNU Emacs 28.1 (build 1, x86_64-apple-darwin20.4.0, Carbon Version 164 AppKit 2022.44)
Best regards.

Good catch, fixed now, thanks!


az group create issue

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az group create
Errors:
invalid syntax (custom.py, line 805)
Traceback (most recent call last):
python3.6/site-packages/knack/cli.py, ln 215, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 553, in execute
    self.commands_loader.load_arguments(command)
azure/cli/core/__init__.py, ln 476, in load_arguments
    self.command_table[command].load_arguments()  # this loads the arguments via reflection
...
<frozen importlib._bootstrap_external>, ln 759, in source_to_code
<frozen importlib._bootstrap>, ln 222, in _call_with_frames_removed
cli/command_modules/resource/custom.py, ln 805
    err_messages = [f'{preflight_error.code} - {preflight_error.message}']
                                                                        ^
SyntaxError: invalid syntax

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az group create -l {} -n {} --subscription {}

Expected Behavior
Environment Summary
Linux-4.14.47-56.37.amzn1.x86_64-x86_64-with-glibc2.3.4
Python 3.6.11
Installer:

azure-cli 2.11.1

Additional Context

ARM

@yonzhan

@rdhruval The CLI version and Python version you used are too old. Could you upgrade the Python version to 3.8+ and CLI version to the latest version (2.37.0)?


Gateways Widget backport to RELENG_2_3_3

This is the same code cherry-picked as in #3661 but now applied to RELENG_2_3_3. It makes the Gateways widget have the same checkbox show/hide behavior as the other widgets, as released in 2.3.3.
I don't know what the policy is about backporting into 2.3.3 - this is not strictly a fix, but it does "fix" a UI inconsistency, and I think it would be useful to have [if|when] a 2.3.3-p2 is needed.

As we get closer to 2.4, I am being more strict about "bug fixes only" for 2.3, but this one is worth sneaking in :)


Error with ConstantObfuscation, only obfuscates strings in methods not outside (not for all classes I dont think) "due to low method capacity"

Describe the bug
When I try constant obfuscation, it seems to only obfuscate constants that are inside of a method and wont obfuscate the ones outside it
To Reproduce
Turn on Constant Obfuscation, have strings outside of a method, The class must be slightly big ish, I cant give you access to the jar here on github because it contains private things but I can give you one if you have discord
Expected behaviour
I wanted all strings to be obfuscated but it forgot some strings outside of methods and gave an error
Screenshots

Bozar version
1.7.0 built from master
Additional context
Problem happened when I was trying to obfuscate an important joke java program with special strings, It fails at those strings with a "due to low method capacity" error

Maybe not as much as a "bug" as someone told me such constants need to have stuff asigned by a method to to be string obfed, but most obfuscators should make a method and do this default? Superblaubeere27 (opensource Obfuscator does this I am pretty sure

I should add [WARN] prefix to that message :/
I explained the meaning of that warning in #11
About your question, we can assign String values to fields directly. But our goal is to scramble that logic using bytecode instructions. We can't add bytecode instructions to field nodes (afaik). We have to create a method to do that.
We can also assign obfuscated String value first, then decrypt on all references (so it's possible but there are things like reflection, and finding references of that is hard).
 If it still gives that warning for most classes, then it means I should make a new lighter constant obfuscation 😀
You can also try moving some of your fields to an inner class as a workaround

I should add [WARN] prefix to that message :/ I explained the meaning of that warning in #11
About your question, we can assign String values to fields directly. But our goal is to scramble that logic using bytecode instructions. We can't add bytecode instructions to field nodes (afaik). We have to create a method to do that. We can also assign obfuscated String value first, then decrypt on all references (so it's possible but there are things like reflection, and finding references of that is hard).
 If it still gives that warning for most classes, then it means I should make a new lighter constant obfuscation 😀 You can also try moving some of your fields to an inner class as a workaround

now my program is not working

Can you provide more details about the issue you're experiencing? Did the obfuscation process complete successfully?

I should add [WARN] prefix to that message :/ I explained the meaning of that warning in #11
About your question, we can assign String values to fields directly. But our goal is to scramble that logic using bytecode instructions. We can't add bytecode instructions to field nodes (afaik). We have to create a method to do that. We can also assign obfuscated String value first, then decrypt on all references (so it's possible but there are things like reflection, and finding references of that is hard).
 If it still gives that warning for most classes, then it means I should make a new lighter constant obfuscation 😀 You can also try moving some of your fields to an inner class as a workaround

now my program is not working

@Wenaly can you provide more details about the issue you're experiencing? Did the obfuscation process complete successfully?

Thanks a lot, it's not necessary


Move horovod and sok init functions to user code

Goals :soccer:

Remove hvd.init() and sok.init() and have the users run them.
Introduce singlegpu and multigpu markers.

Implementation Details :construction:
In some cases when horovod is not built correctly or not configured correctly with MPI, hvd.init() or sok.init() will throw an MPI_LIB errors on the C-level, which we cannot catch from Python. This happened in https://github.com/NVIDIA-Merlin/models/pull/1134 for example.
Following @oliverholworthy's proposal, this PR leaves hvd.init() and/or sok.init() up to the user.
We still need to initialize them to run unit tests but incorrect installation in the ci-runner will still block the CI, so this PR also introduces singlegpu and multigpu pytest markers to skip the horovod tests in the single-gpu case, similarly to https://github.com/NVIDIA-Merlin/Merlin/pull/999.

Ci is unblocked for now in https://github.com/NVIDIA-Merlin/models/pull/1136. Will close this PR and revisit if necessary.


made the name of blog authors clickable, created CTA to the linkedIn …

resolves #238
resolves #248

I'm not sure if we should hardcode those profile image URLs. Is it possible to dynamically get the latest image at build time? Maybe it's in the  tags of an LI profile. Not a blocking thing though.
LGTM.


Cannot import PrismaInstrumentation within tsx process

Bug description
import { PrismaInstrumentation } from "@prisma/instrumentation";
         ^

SyntaxError: The requested module '@prisma/instrumentation' does not provide an export named 'PrismaInstrumentation'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:180:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:263:5)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:547:26)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:116:5)```

    getting this error on import

### How to reproduce

1. define a worker file with the import
2. attempt to run the file with tsx

### Expected behavior

import is successful and can be used in otel sdk

### Prisma information

N/A

### Environment & setup

- OS: macOS
- Database: PG
- Node.js version: 23.3.0

### Prisma Version

5.21.1

Hi @PrathamSoni
Can you please upgrade your Prisma version to 6.1.0 as tracing is now in GA? Use version 6.1.0 or later of the prisma, @prisma/client, and @prisma/instrumentation npm packages. You will also need to install the @opentelemetry/api package as it's a peer dependency.
https://www.prisma.io/docs/orm/prisma-client/observability-and-logging/opentelemetry-tracing#step-1-install-up-to-date-prisma-orm-dependencies


fix: use path.join to support Windows

Description of changes
changes template string ${somePath}/${somePath2} to path.join(somePath, somePath2). This does not fix the constant import issue where the constant is undefined

Issue #, if available
fixes #767

Description of how you validated changes
Checklist

[x] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@josefaidt could you rebase this to resolve conflicts when you're able

Closing this as the issue appears to have been fixed upstream.


CircuitBreaker + Predicate + Failure interaction.

Hi @jhalterman! I've been pushing failsafe at Rally Health as a superior replacement to our lesser in-house version. I'm a big fan of this project and grateful that it exists.
@KyohoSatsumi and I encountered some surprising behavior involving CircuitBreaker.failIf(Predicate) when an operation fails (with a Throwable) and the Predicate is still invoked with a null argument. In the worst case, the operation is never completed!
I've created a couple minimal failing test cases illustrating my expectations and some comments around the parts of the implementation that I think might be problematic. Hoping to get your feedback around the original intent and possible solutions.
Fix is up.

Coverage remained the same at 84.075% when pulling 51d67b5c99a411b41a975c4ec0f01ea988487b3d on htmldoug:circuit-breaker-predicate-failure into e8d2a7f68d90d0a0e5f919c9423521575509bfab on jhalterman:master.

I went ahead and added fixes.
If they look good to you, I'll strip out the uncertainty in the comments and summarize.

I've removed the temporary discussion javadoc and summarized. This should be ready to merge now as is.
@jhalterman please review when you get a sec and let me know if you'd like for me to make any changes.

Would love to be able to start using this in our projects! Attention appreciated. :)

Thanks for this PR.
Ignoring user-land exceptions inside of predicates is a good idea to me. We actually have 2 more places where predicates are used, in RetryPolicies. Care to ignore them there as well?
https://github.com/jhalterman/failsafe/blob/master/src/main/java/net/jodah/failsafe/RetryPolicy.java#L223
https://github.com/jhalterman/failsafe/blob/master/src/main/java/net/jodah/failsafe/RetryPolicy.java#L241
Other than that, the PR looks good. 👍

You bet. Done.

Nice - thanks for this!

@jhalterman, any plans to cut a release with this fix?

@laflechejonathan Sure - apologies. I've had some work pending for a while that I was waiting on, but no need to wait just for this fix.
Just cut 1.1.1 release. Should be in central shortly.


{CI} test core for onboarding pytest on CI

Description
core is modified, it will run all tests
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

test core

/azp run


Add a --check flag

I'm working on a CI setup where I want to be able to run both cargo clippy and cargo build. Without the --check flag, we need to rebuild the dependencies for checking each time. With this addition, cargo clippy is able to leverage the cache.
Thanks for the wonderful tool, it's really sped up our CI!

Hi @snoyberg!
Can you tell me a bit more about your usecase?
I am a bit surprised to hear you are using cargo-chef for your CI pipeline - wouldn't sccache or just plain-old incremental compilation (by caching the right folders) be a better match?

Sure, happy to share. I regularly perform builds within Docker containers in our CI setups. We could use CI caching to speed this up, and do that in plenty of other cases. But performing the build within a Docker image can provide us with a more reliable CI "caching" strategy, by pinning down exactly which tag of the base build image we're using. Specifically in this case, I'm performing a statically linked MUSL-based build, and knowing that we have all of the base system and Rust dependencies fully configured is nice.
I'd be happy to extract the relevant files from our project setup if you'd like to see. I know not everyone is in favor of the concept of performing builds this way. But I actually had thought that this was one of the primary use cases of cargo-chef. If our Docker registry had better --cache-from support, it would have been a simple multistage Docker use case.

That's enough for me to move forward 😁 Although, if you want to share a minimal example of your setup, I am sure others will benefit! (And I am curious as well, of course)

Awesome, thanks for the merge and release! I've put together a GitLab repository demonstrating the workflow I'm using on some projects, together with a README explaining it:
https://gitlab.com/snoyberg/docker-chef-ci-example


the lights on my roomba 896 stay on

Hello, I just integrated my roomba 896 into homebridge, it works great!
I just have a small problem, the robot lights are constantly on since integration with homebridge.

Hi someone had this issue, go here to see his solution

@Cyrille556 I hope the above helper with your problem. If not I'd be interested to hear your results with the latest beta version of the plugin.


Updated to not allow processing of worker commands embedded in git co…

…mment
https://dev.azure.com/mseng/AzureDevOps/_workitems/edit/1645065

The updates to dotnet* files were because the tests were failing since they did not match the Internet versions

Tommy and I talked about it briefly. There's not really a good way to inject a message. Since there's not much of a use case for this to work anyhow, I think it's alright.


Segmentation faults when using SwiftyJSON as a subproject

If you add SwiftyJSON by dragging in the SwiftyJSON.xcodeproj then linking the framework and add a class like the following:
import SwiftyJSON

class Object {
func method(json: JSON) {
}
}

You'll get a segmentation fault

@konstantinkoval thanks,
Your hack did the trick. With unit tests where main app goes as target decency importing SwiftyJSON as a file in main app won't help

Hi all,
I dug into this and have submitted a minimal repro case in PR to /practicalswift/swift-compiler-crashes. It seems the compiler crashes when it hits the default arguments (opt: NSJSONReadingOptions = .AllowFragments) in the JSON initialiser. When a initialization like that is optimised out, the compiler segfaults. It's definitely a bug in swiftc.
It only happens when SwiftyJSON is imported as a module, so you can use the .swift file directly in the meantime.
Another workaround is to make sure the call isn't optimised out (e.g. the .cancel() and println(".") workarounds above.
For SwiftyJSON library code, see if you can omit the default arguments for opt: and errorPointer: somehow. Sucks, but swiftc is still, um, a little wonky and this won't probably be fixed for some time.

Hi all,
just a small note to say I use SwiftyJSON.swift directly in a Framework, and it builds fine, but it crashes when I run unit tests (seg fault 11 too). I guess it's because doing that Swifty gets in a module (even if it's not his own) and it is the same bug in swiftc.

I have a segfault 11 too when I just include SwiftyJSON.swift in my project. It occurred suddenly after a small refactoring. Before everything was finde. So I think it has nothing to do with the subproject but with some strange swift compiler behaviour.

Same issue here. I'm having a new surprise at each attempt to compile this.
When registering Alamofire request callbacks, that's the compiler error I was receiving:
Command failed due to signal: Segmentation fault: 11

After tried what @yuhua-chen suggested, the problem changed, in a very surprising way:
Undefined symbols for architecture x86_64:
  "__TMdV10SwiftyJSON4JSON", referenced from:
      __TFFC7example14ViewController11viewDidLoadFS0_FT_T_U0_FV10SwiftyJSON4JSONT_ in ViewController.o
ld: symbol(s) not found for architecture x86_64

After removing the Alamofire callback, the program do compile, which doesn't help.

@endel: would you be able to share a gist of your crashing/non-crashing code? That sounds like a different segfault that I'd like to minimise and report against swiftc asap. Thanks.

@rustedivan sure, here it is: https://gist.github.com/endel/6e2f9ac7279a6ee42b90
I've written 3 examples to demonstrate what is happening for me:

Runs fine
Segmentation fault
Linker error

I'm using a custom Request class for this.

Excellent, thanks for putting in the effort with the different cases. Swift compiler crashes are collecting over at practicalswift/swift-compiler-crashes so these reports are golden.

For me the following caused a segfault:
switch type {
	case .aType:
		// Do Something
	default:
		break
}

and this solved it:
switch type {
	case .Some(.aType):
		// Do Something
	default:
		break
}

@kostiakoval's workaround solved it for me. I pushed a copy of the changes to  https://github.com/sman591/SwiftyJSON/tree/compiler-segfault-workaround in case anyone else wants to try it.

Same here :-(
If you remove "options" parameter from init() and pass "AllowFragments" as default value to NSJSONSerialization (cannot be modified as removed as input parameter)... It works.
It's a shame that Apple had relased this faulty compiler (this is one of the many bugs it has)

I just had this issue! It was hard to track down but essentially once I removed a function that included JSON object from SwiftyJSON class, it crashed my code with the segmentation fault.
So basically if I removed code from the project it crashed.
When I imported SwiftyJSON.swift into my project it started to work.
Here was the stack overflow I posted: http://stackoverflow.com/questions/28623405/why-can-i-not-remove-an-unused-function-from-my-swift-class

We got feedback from apple, they request to test it with Xcode 6.3 and the news swift 1.2 compiler. We still have to migrate our project, so we can't yet test it, so if someone else that has the problem could try it with Xcode 6.3 that would be great

@broglep-koubachi  I had the exact same pb combining Alamofire and SwiftyJSON doing something like this
Alamofire.request(.GET, APIClientConstants.kApiBaseUrl + "/vls/v1/stations", parameters: params).responseJSON { (req, response, json, error) in
if (error != nil) {
completionHandler(APIResponseState.Error(error!))
}
else {
var json = JSON(json!)
completionHandler(APIResponseState.Correct(json))
}
}
It wouldn't compile under Xcode 6.1.1 and swift 1.1 but it works with swift 1.2 and Xcode 6.3 after manually updating Alamofire and SwiftyJSON to Swift 1.2 of course

+1 Removing the options parameter from init(data:options:error:) worked for me as well.

This seems to be fixed in Xcode 6.3.


Relay and Host connectivity tests failing in the first run of WebRTC troubleshooter tests on chrome devices

Browsers and versions affected
Chrome: 63.0.3239.37/ 10032.29.0 dev
Chrome devices : Wolf, Sanppy
Steps to reproduce

Browse to https://test.webrtc.org/
Click Allow in the getUserMedia prompt
Click Start

Expected results
All tests should pass
Some failures may be expected, such as:
-if your camera can't support higher resolutions
-if you're currently on a network that doesn't supply an IPv6 address
Actual results

Host connectivity tests fails with "[Failed] Timed out" error
Throughput test stops after "data throughput"
No errors in javascript console

testrtc-2017-11-06T21_57_44.391Z.log

Note: This issue is not observed after refreshing https://test.webrtc.org/  page and rerunning the tests

@KaptenJansson
@rantonysamy

Will check and get back to you.

Network related I believe. Closing.


The script to copy information from duplicate bugs to the bugs they have been duplicated to should not revert signature changes

Jens removed a signature, because it is invalid (I'll file a separate issue about that): https://bugzilla.mozilla.org/show_bug.cgi?id=1435343#c90
Then right after, bugbug added the same signature right back. It would be better if it didn't just flip the signatures right back after somebody changed them.

Moved to the autonag repository as the problem is not in bugbug.

I'm unsure whether we should actually do this, or if we should keep the same information across bugs in the same "duplicate group".

@marco-c should we do this as part of #1760? If we merge copy_duplicate_info into duplicate_copy_metadata, this will be automatically solved.

Sounds good!

This is very rare though, so let's only do it if it's super quick.


PYI-531: create form for user input

Proposed changes
What changed
This adds a basic html form to be able to enter JSON data along with GPG45 values
Validation and storing of inputs in follow up stories
Why did it change
So we can test different and more types of data
Issue tracking

PYI-531

Checklists
Environment variables or secrets

[x] No environment variables or secrets were added or changed


chore: Add context-centric based API for noir_wasm

Description
Currently this PR is not breaking
This adds an API that maps closer to the API we'd have in the CLI or atleast one that differs less with the native version. One can imagine a shared Context object and in nargo_cli the main difference is the PathToSourceMap struct that gets passed in for example.
Problem*
Resolves
Summary*
Additional Context
Documentation*
Check one:

[ ] No documentation needed.
[ ] Documentation included in this PR.
[ ] [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist*

[ ] I have tested the changes locally.
[ ] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Need to add js tests

Added tests and also a new method called compile_ which exposes the same API as compile, but internally uses the context based API -- (this still non-breaking)


Add Optic to list

By submitting this pull request, I promise I have read the contribution guidelines twice and ensured my submission follows it. I realize not doing so wastes the maintainers' time that they could have spent making the world better. 🖖
⬆⬆⬆⬆⬆⬆⬆⬆⬆⬆

This is not an Awesome list.

Sorry, I don't understand? Optic is a node module you'd download  (either by doing npm i -g @useoptic/cli or the dev depdency (npm i -D @useoptic/cli) - why isn't this valid for this list?


Update DTDL documentation to include JSON-LD details

Every DTDL document is a JSON-LD document. The language spec alludes to this but does not contain information about how the terms used in the documentation map to JSON-LD (such as how the term "Interface" maps to a JSON-LD IRI). The suggestion is to add a section that focuses on DTDL and JSON-LD for readers interested in those details.

We have updated the language docs with a better description of JSON-LD usage. I believe this issue can be closed.


Automated cherry pick of #5052: fix: progressively update image size while uploading

Cherry pick of #5052 on release/3.1.
#5052: fix: progressively update image size while uploading

/lgtm
/approve


WIP: Opt runtime bench

diff between the old test-linux-stable cargo test --all --release --verbose --locked
and new cargo +nightly test --all --release --verbose --locked -Z package-features --features runtime-benchmarks jobs:
benchmarking::tests::add_slashing_spans_works: test             benchmarking::tests::add_slashing_spans_works: test
                                                              > benchmarking::tests::close_approved: test
                                                              > benchmarking::tests::close_disapproved: test
                                                              > benchmarking::tests::close_early_approved: test
                                                              > benchmarking::tests::close_early_disapproved: test
benchmarking::tests::create_validators_with_nominators_for_er   benchmarking::tests::create_validators_with_nominators_for_er
benchmarking::tests::create_validator_with_nominators_works:    benchmarking::tests::create_validator_with_nominators_works:
                                                              > benchmarking::tests::execute: test
                                                              > benchmarking::tests::propose_execute: test
                                                              > benchmarking::tests::propose_proposed: test
                                                              > benchmarking::tests::set_members: test
                                                              > benchmarking::tests::test_benchmarks_elections_phragmen: test
benchmarking::tests::test_benchmarks_offchain: test             benchmarking::tests::test_benchmarks_offchain: test
benchmarking::tests::test_benchmarks: test                      benchmarking::tests::test_benchmarks: test
                                                              > benchmarking::tests::test_benchmarks: test
                                                              > benchmarking::tests::test_benchmarks: test
                                                              > benchmarking::tests::test_benchmarks: test
                                                              > benchmarking::tests::test_benchmarks: test
                                                              > benchmarking::tests::test_benchmarks: test
                                                              > benchmarking::tests::test_benchmarks: test
                                                              > benchmarking::tests::test_benchmarks: test
                                                              > benchmarking::tests::test_benchmarks: test
                                                              > benchmarking::tests::test_benchmarks: test
                                                              > benchmarking::tests::test_benchmarks: test
                                                              > benchmarking::tests::test_benchmarks: test
                                                              > benchmarking::tests::test_benchmarks: test
benchmarking::tests::test_payout_all: test                      benchmarking::tests::test_payout_all: test
                                                              > benchmarking::tests::transfer_best_case: test
                                                              > benchmarking::tests::transfer_keep_alive: test
                                                              > benchmarking::tests::transfer_set_balance_killing: test
                                                              > benchmarking::tests::transfer_set_balance: test
                                                              > benchmarking::tests::transfer: test
                                                              > benchmarking::tests::vote: test

closing because of inactivity.


CouchApp 'push' don't work on Couchbase Server 2.0

This problem, imho, alike http://groups.google.com/group/couchbase/browse_thread/thread/1c12708323b68616
Error after run command in Ubuntu terminal
couchapp -v push db http://<IP_ADDRESS>:5984/db
2011-10-17 14:39:38 [DEBUG] Resource uri: http://<IP_ADDRESS>:5984/db
2011-10-17 14:39:38 [DEBUG] Request: HEAD None
2011-10-17 14:39:38 [DEBUG] Headers: {'Accept': 'application/json', 'User-Agent': 'couchapp/0.6.0'}
2011-10-17 14:39:38 [DEBUG] Params: {}
2011-10-17 14:39:38 [DEBUG] Start to perform request: <IP_ADDRESS>:5984 HEAD /db
2011-10-17 14:39:38 [DEBUG] create new connection
2011-10-17 14:39:38 [DEBUG] Send headers: ['HEAD /db HTTP/1.1\r\n', 'Host: <IP_ADDRESS>:5984\r\n', 'User-Agent: restkit/3.2.3\r\n', 'Accept-Encoding: identity\r\n', 'Accept: application/json\r\n', 'Authorization: Basic ZGFsaW9uOnZpc29yODg4\r\n']
2011-10-17 14:39:38 [DEBUG] Start to parse response
2011-10-17 14:39:38 [DEBUG] Got response: 500 Internal Server Error
2011-10-17 14:39:38 [DEBUG] headers: [MultiDict([('Server', 'CouchDB/1.2.0a-00596f2-git (Erlang OTP/R14B03)'), ('Date', 'Mon, 17 Oct 2011 11:39:38 GMT'), ('Content-Type', 'application/json'), ('Content-Length', '579'), ('Cache-Control', 'must-revalidate')])]
2011-10-17 14:39:38 [DEBUG] release connection
2011-10-17 14:39:38 [DEBUG] return response class
2011-10-17 14:39:38 [DEBUG] release connection
2011-10-17 14:39:38 [CRITICAL] {'msg': '', 'status_int': 500, 'response': couchapp.client.CouchdbResponse object at 0x1bd9a50}
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.7/couchapp/dispatch.py", line 48, in dispatch
return _dispatch(args)
File "/usr/lib/pymodules/python2.7/couchapp/dispatch.py", line 92, in _dispatch
return fun(conf, conf.app_dir, *args, **opts)
File "/usr/lib/pymodules/python2.7/couchapp/commands.py", line 75, in push
dbs = conf.get_dbs(dest)
File "/usr/lib/pymodules/python2.7/couchapp/config.py", line 152, in get_dbs
return [Database(dburl) for dburl in dburls]
File "/usr/lib/pymodules/python2.7/couchapp/client.py", line 220, in init
self.res.head()
File "/usr/lib/pymodules/python2.7/couchapp/restkit/resource.py", line 121, in head
params_dict=params_dict, **params)
File "/usr/lib/pymodules/python2.7/couchapp/client.py", line 138, in request
raise RequestFailed(str(e))
RequestFailed: {'msg': '', 'status_int': 500, 'response': couchapp.client.CouchdbResponse object at 0x1bd9a50}

Couchbase Server 2.0 > http://couchbase.com/downloads

what does curl -I http://localhost:5984/nonexisistingdb return?

~$ curl -I http://localhost:5984/nonexisistingdb
HTTP/1.1 404 Object Not Found
Server: CouchDB/1.1.2 (Erlang OTP/R14B)
Date: Mon, 17 Oct 2011 13:10:19 GMT
Content-Type: text/plain;charset=utf-8
Content-Length: 44
Cache-Control: must-revalidate

~$ curl -I http://localhost:5984/exisistingdb
HTTP/1.1 200 OK
Server: CouchDB/1.1.2 (Erlang OTP/R14B)
Date: Mon, 17 Oct 2011 13:10:30 GMT
Content-Type: text/plain;charset=utf-8
Content-Length: 217
Cache-Control: must-revalidate

~$ curl -I http://localhost:5984/nonexisistingdb
HTTP/1.1 500 Internal Server Error
Server: CouchDB/1.2.0a-00596f2-git (Erlang OTP/R14B03)
Date: Mon, 17 Oct 2011 13:20:00 GMT
Content-Type: text/plain;charset=utf-8
Content-Length: 448
Cache-Control: must-revalidate

~$ curl -I http://localhost:5984/exisistingdb
HTTP/1.1 500 Internal Server Error
Server: CouchDB/1.2.0a-00596f2-git (Erlang OTP/R14B03)
Date: Mon, 17 Oct 2011 13:20:09 GMT
Content-Type: text/plain;charset=utf-8
Content-Length: 438
Cache-Control: must-revalidate

curl -X POST http://<IP_ADDRESS>:5984/exixtingdb -d '{ "demo": true }' -H "Content-Type: application/json"
{"ok":true,"id":"6a68fcc6c504806658188a72de0013ec","rev":"1-9d0420a0506b9c5adeb9804b6a5c4eda"}

CouchApp on Couchbase Server 1.1.2 is going normal (CouchDB 1.1).

So, it seems like a couchbase error for me. HEAD should return a 404, or 200 . I suggest you open a ticket on couchbase tracker for that.

Couchbase Server 2.0 does not have a CouchDB API.
Couchbase Single Server (any version) does and should work as advertised.

thanks @janl for the explanation. Closing this issue as a none issue then.

Couchbase Server 2.0 does not have a CouchDB API.

@jan, slide below is wrong?
Source > http://couchbase.com/on-demand/webinar/couchbase-server-2.0-overview

@benoitc, standard curl-command is work on any Couchbase Server without errors:
curl -X POST http://<IP_ADDRESS>:5984/exixtingdb -d '{ "demo": true }' -H "Content-Type: application/json"
I see what method 'get_db_info' not implement for Couchbase Server 2.0.
The point in hand is just this: "Why CouchApp can't work on Couchbase Server 2.0?"
Thanks!

I guess it can if _design/docid/... api is supported. Let me know.

We do expose an API to access View results and manage design docs for deploying views. This isn't intended for anything else beside our Web UI and client SDKs, (or you custom SDK if you have one). It is not a full fledged CouchDB API, we only ported a few things we need to support views for the 2.0 release. The 3.0 release will have the full CouchDB API. You can spot (very tiny) that the 5984 API endpoint is for views only. Please do not try and expect it to behave like a regular CouchDB.

Thanks for the explanation, @janl.
I use CouchApp and find it as excellent solution for synchronize local and couchdb data of complex project (many thanks, @benoitc!). On this weekend attempt to try Couchbase Server 2.0... I await 3.0... or update CouchApp: my current CouchDB project consist of many templates, attachments and some static docs. Therefore, Couchbase Server 2.0 - "views only" today :(

@savdalion We have Couchbase Single Server for you today :)