Bump cm-promql to v0.15.0

upgrade codemirror-promql to v0.15.0
inject the metricNames coming from the MetricExplorer in the PromQLExtension (fix #8686)
update the import paths accordingly to the changes provided by this new release.

:+1: Nice, thanks! (waiting for CI to pass)

Is there a change for the end users?

yes @roidelapluie  but it's quite minor :

With this PR, the metricNames is injected into the PromQL editor. So when you will start to type, you won't have to wait a couple of times before it returns the list of the possible metrics since it's already provided.
And also, like that, the list of the metrics is not retrieved two times by two different tools.
And another light improvement is when you have an empty editor and you want to trigger the autocompletion using ctrl + space then it will display the list of metrics/ functions / aggregations available. Before this PR, if you are trying, nothing is happening.

Finally in the previous release (v0.14.1, #8700), it fixed the autocompletation of the label after a coma. The list wasn't displayed immediatly like it is the case for the first label to autocomplete.
Hope it's clearer, let me know if it's not. At this time, I'm not sure what I'm saying is clear ^ ^.

Thanks!


docs: fix typo

recalulate -> recalculate

Hello @tannerlinsley !
Please let me know if this PR doesn't meet your standards so I can improve it
TIA
~Amnon ^_^

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Collection.find doesn't call map when result is empty

I'm experiencing currently an issue when trying to map over an empty result set.
For example, when I try to do:
Collection.find(condition).map(x => ....)

the map callback will not be called if the result of find is empty.
Is that behaviour according to the design?

If there is no data in the Mongo.Collection, then the changes events won't fire, and the next callback of the Observable won't fire.
You can use RxJS startWith operator in order to solve it:
Collection.find(condition).startWith([]).map(x => ....)

I personally expected it to return an empty array when nothing was in the collection or at least a null. Is there a reason why it doesn't do this by default?

I agree with @jerradpatch Otherwise, there is no way to distinguish between the two cases (data isn't loaded yet vs data is loaded but empty)
It is needed to avoid showing users the empty placeholders in lists, which is confusing (user sees a notice saying that her list is empty, and then the list populates with data)
There is a pull request fixing it https://github.com/Urigo/meteor-rxjs/pull/103


Do not install the diagnostics .gitkeep file

We don't want to install random empty files with the compiler.
This could also be handled in swift_install_in_component which would prevent the issue in the future, but I wasn't sure if we wanted to make that change.

There's a better fix here, so I'm going to close this.


Add Release Notes for Component 0.1.76

Closes https://github.com/brave/brave-browser/issues/11720

@srirambv in a PR earlier today, @bbondy moved CHANGELOG.md to the project root: https://github.com/brave/ethereum-remote-client/blob/master/CHANGELOG.md - if you could place your diff there. Thanks!

@ryanml done


Why does wasm files loading in app manager not use wasm_runtime_load?

In modue_wasm_app.c, wasm file(bitcode or aot) is loaded by wasm_runtime_load_from_sections. By doing this, some sections destruction is involved.
https://github.com/bytecodealliance/wasm-micro-runtime/blob/049760b84966d119b2f95a3d9be6e17d638e2d9b/core/app-mgr/app-manager/module_wasm_app.c#L646-L659
In the project-mini, wasm_runtime_load is used, which seems much simpler.

And it seems that when app manager exits, all installed app will be gone.

I think the app manager code assumes the aot file was streamed from remote sources, and during the stream process, it generates sections on the fly. So by the time the app is ready to be installed, there is no reason to call wasm_runtime_load again (which generates sections again).
Personally I feel like app manager should not have assumption around how the app was received, hence it should always do wasm_runtime_load.

@AfflatusX As the issue #352 you filed, this assumption restricts app manager's extension ability.

Yeah I agree - I replaced that with wasm_runtime_load in my fork actually. However, I think it would be better to handle section generation in this routine instead of making the assumption around how the data was received :)

The app-manager is designed to be run on many different platforms.
On some constrained devices such as MCUs, the memory consumption, especially the peak memory usage is a key factor. We use wasm_runtime_load_from_sections to create the module and then we can free some useless sections by destroy_part_wasm_sections to reduce the memory consumption and peak memory usage.

@xujuntwt95329 Could destroy_part_wasm_sections be import for wasm_runtime_load to make all platforms benefited from it? or make wasm_runtime_load_from_sections  and wasm_runtime_load same?

Could destroy_part_wasm_sections be import for wasm_runtime_load to make all platforms benefited from it?

I‘m afraid not. On some platforms like Linux, we read the whole file into memory and call wasm_runtime_load, in this case, we can't destroy the section body as they don't have their own memory block.

or make wasm_runtime_load_from_sections and wasm_runtime_load same?

Developers are free to decide which API to use. They can simply read the whole file and use wasm_runtime_load (just like the product-mini), or they can also resolve every section from the file, and then use wasm_runtime_load_from_sections to load the module, which may be a little more complicated.

wasm_runtime_load codes show that it also destroy loaded sections after loading sections.
https://github.com/bytecodealliance/wasm-micro-runtime/blob/034606b0a986a43f6063368e1ac28587472710bd/core/iwasm/aot/aot_loader.c#L1894-L1909

The destroy_sections only destroy the memory space of AOTSection or WASMSection structure, section_body is not freed.


add build.zig.zon file

Allows using the built-in package manager

This would be quite nice

Idk how I missed this PR, but I did. Anyways, I decided to just do this myself, leaving out all the template comments :)
https://github.com/Hejsil/mecha/commit/d5a642ca8aca75dbd60859df8d3a45421d371faa


The type or namespace name 'ApplicationInsights' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)

Just added Template10 to my installation of VS2015. Tried to build an empty project based off the Minimal template.
First error was complaining about System but that just requires a build and a refresh.
After that, however, I get the error in the title, complaining about ApplicationInsights missing.
As far as I can tell, this is an optional service running off Azure. Should we be forcing developers to use this?
Even if we are making it an optional feature of Template10, shouldn't there be some "getting started" documentation for developers so that they know the initial steps required to get going? I found http://dailydotnettips.com/2015/08/12/adding-application-insights-to-a-windows-10-universal-app/, for example, but all it starts with is "First, login to Azure Portal". Not very helpful if, as a developer, I've never done that before. Is there a cost for this?

Commenting out the calls to ApplicationInsights in App.xaml.xs/App() clears the build error, so it doesn't look like there are any other references to ApplicationInsights in the template.

@JerryNixon  This issue still exists in the library v1.12 for the Blank template. The same bunch of errors described above appear after creating a new app based on Blank. The issue does not happen with the Hamburger and Minimal templates because they reference the ApplicationInsights NuGet packages.


Addresses singleton variable warnings in tests.pl

Addressing warnings for singleton variables

This makes sense, thanks a lot!
In testing this, however, I found out that I can't use the library anymore:
?- use_module(constrained).
   true.
?- length_c(A, 1).
   error(type_error(evaluable,constrained/0),(is)/2).
?- functor_c(A, a, 1).
   error(type_error(evaluable,constrained/0),(is)/2).

This means that I can't even run the tests. Can you reproduce this? I remember this working fine last time I touched this.
I haven't been able to isolate this, and it seems like a very elusive heinsenbug in Scryer Prolog's compilation becuse if I change the definition of length/2 in unrelated ways it gets fixed.

number_c/1 works for me also, but functor_c/3 and length_c/2 give that error (at least with those arguments).

Ah, interesting. I see the same failure behaviors you do---those particular queries break, but other interactions with those same constraints seem to work just fine.

Ok, so it's not just me. I'll investigate this deeper another time.


Improve HTTP API

We should probably keep close to or directly embed http.Server. The problem there is net.Listener, which only works for TCP.

Also see the discussion happening at https://github.com/mholt/caddy/issues/47.

We now have an API very similar to http.Server. We still need to think about graceful shutdowns though, as we cannot simply Close() the net.Listener, or wrap the TCP connections as some libraries do.

Does QUIC really need graceful shutdowns / restarts?

Well…
There's obviously state in a connection (crypto keys, streams, …), that cannot easily be migrated to e.g. a new process. So, if a server goes away, it cannot simply pass the connection to another server, but has to close it first. Now, QUIC has two ways of shutting down a connection. The first one is a CONNECTION_CLOSE, which immediately terminates the connection (~ TCP RST). The second, a GOAWAY frame is different, and basically allows current requests to finish, but does not allow new requests, similar to H2's GOAWAY frame. By graceful shutdown, I mean that we should have an API that sends GOAWAYs, possibly with some timeout, and makes the server stop responding to new connections. I will implement this behavior soon, see #153.
However, since the kernel doesn't do as much work for UDP, I'm not sure how a 0-downtime restart would be done. In particular, there's only one socket in total, not one per connection. That means there has to be some instant where all incoming packets are passed to the new server, and the old one doesn't receive any packets anymore. Right now, I don't see how a 0-downtime restart is possible in this setup.

You're probably right, but if it helps give clarity to the graceful restart process, let me share how Caddy does it:
file, err := old.listener.File()
if err != nil {
	return err
}
ln, err = net.FileListener(file)
if err != nil {
	return err
}
file.Close()

We then use ln and pass it into the call to Serve(). Good news, *UDPConn has a File() method. Granted, we're using a net.Listener which is what Caddy uses, but if you scroll up in that file a bit, you'll see a comment where I am considering a pattern for supporting UDP with net.Listener:
type UDPListener struct {
	*net.UDPConn
}
func (u UDPListener) Accept() (net.Conn, error) {
	return u.UDPConn, nil
}
func (u UDPListener) Close() error {
	return u.UDPConn.Close()
}
func (u UDPListener) Addr() net.Addr {
	return u.UDPConn.LocalAddr()
}
var _ net.Listener = UDPListener{}

I haven't worked with UDP in ~10 years (!) so I am not fresh on the technicalities here, so you should tell me if this is ludicrous (if not a little unusual) or if maybe it's something that can work. :sweat_smile:

I have to admit, I haven't worked with 0-downtime restarts yet, but this is my understanding:
With TCP, you get a listener socket, and a new socket (with its own FD) for each connection. That way, you can pass the listener socket to a new server instance and have new connections served there, but continue to handle (and possibly shutdown) old connections in the old process. Only when they are all closed, the old process terminates.
With UDP, the situation is different. You only get a single socket (FD), where you handle the packets for both new and known connections. Therefore, as soon as you pass the socket to the new process, the old one stops being able to receive packets, and therefore practically stops working. Since the graceful shutdown possibly takes time to allow for large downloads to complete, there either is downtime when switching to the new process, or old connections are not gracefully terminated.
One thing to note, this is not a problem when using a load balancer that is aware of QUIC (which Google is probably doing). There, you can of course simply stop forwarding new connections to the stale server, and wait until it properly stops.
It is quite possible that I'm missing something; it might make sense to ask this on the QUIC mailing list.

Okay, that makes sense. Do you have a link to said mailing list?
FWIW, I'm not married to the idea of having Caddy support graceful restarts with QUIC, at least not right away. I'd be happy to ship Caddy 0.9 with optional, experimental QUIC support using this library!

I've asked the question on the mailing list: https://groups.google.com/a/chromium.org/forum/#!topic/proto-quic/w4tL3AuZkww
I also agree that 0-downtime restarts are not important for experimental QUIC support in 0.9, I was just curious ;)

I think that with the new CloseGracefully function (which exists, but currently does nothing, see #153) we've got everything we need for now. Closing this issue.

Cool. It looks like, from the response on the mailing list, a graceful UDP restart will be a little tricky (connection IDs and all that) -- again, not something I as a user of the library would need right away, but I guess you can add it to the long-term list of things to consider. :+1: Nice work!


fix: center align text

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/7636
Tests

Create a "New Room" via the floating "+" icon
If already created go to the room
Click the room header to access the Details right hand pane
Verify that the room name is aligned to center

[x] Verify that no errors appear in the JS console

QA Steps

Same as tests

[x] Verify that no errors appear in the JS console

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @tgolen in version: 1.1.40-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @yuwenmemon in version: 1.1.40-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Issue 1 -
Title - [High]: Chrome+Jaws : Screen reader: Role and label not defined for "back" control.
Actual - Role is not defined for the "back (<)"control. This made it difficult for screen reader users to access the functionality associated with it. Additionally, the label is not defined for the mentioned interactive element in the source code of the page.
Expected - When a role is defined appropriately for the interactive element, the screen reader user will interact with the element effectively.
WCAG failure - 4.1.2, 2.5.3
Reproducible in staging? - Yes
Version Number: - v1.1.40-2
Platforms - Web, Desktop, Mobile-web, iOS
Suggested Fix - Ensure that all the page functionality is available for all users irrespective of the device being used.
Apply the following changes:

Specify role="button" for the 'div' element containing the "back (<)" control.
Provide aria-label value such as "back" for the 'div' element containing the "back (<)" control.

Note - Due to installation of build not able to check on 'Android'.

Issue 2 -
Title- [High]: Chrome+Jaws: Screen reader: Role is not defined for controls.
Actual - Role is not defined for the "Members", "Settings", "Invite" and "Leave room" controls. This made it difficult for screen reader users to access the functionality associated with it.
Expected - Role should be defined as a 'button' for the "Members", "Settings", "Invite" and "Leave room" controls.
WCAG failure - 4.1.2
Reproducible in staging?: - Yes
Version Number: - v1.1.40-2
Platforms - Web, Desktop, Mobile-web, iOS
Suggested Fix - Ensure that all the page functionality is available for all users irrespective of the device being used.
Apply the following changes:

Specify role="button" for the 'div' element containing the "Members", "Settings", "Invite" and "Leave room" controls.

Note - Due to installation of build not able to check on 'Android'.

Issue 3 -
Title - [Medium]: Chrome+Jaws : Missing list markup for controls.
Actual - The list mark-up, is not used to present related information on the screen. For instance, the related information such as "Members", "Settings", "Invite" and "Leave room" controls are not marked as list items that visually look like a list. As a result, screen reader users might find it difficult to navigate to the lists and different list items quickly.
Expected - When list mark-up is provided for the mentioned content, screen reader users will identify a number of list items.
WCAG failure - 1.3.1
Reproducible in staging? - Yes
Version Number: - v1.1.40-2
Platforms - Web, Desktop, Mobile-web, iOS
Suggested Fix - Use appropriate list mark-up, such as 'li' and 'ul' to identify related information. In addition, if required apply styles to maintain the visual presentation of the web page.
Note - Due to installation of build not able to check on 'Android'.


Enhancement: Implicitly enable no_unused_imports fixer

This PR

[x] implicitly enables the no_unused_imports fixer
[x] runs composer style-fix

Thank you, @bighappyface and @erayd!


GUI: have a color scheme

Instead of the current black and white theme.

Pushing this to v2!

Note this issue is about updating the font, icons and colors. Not the layout of the elements from the new design.
Let's post the colors here once we have them.

@edouardparis i think this is addressed?

Yes, Icons needs to be updated still

I think this is done. Feel free to reopen if i'm mistaken.


Issue with Open AI Function Calling

Issue:
For a use case, I have data in multiple sources PDFs, excel files, 3rd party APIs. I have uploaded PDF data to AI Search and configured it in the bot app, it works fine with PDF data. Now when I try to add more data sources like 3rd party APIs using function calling feature, application throws error - "400 - Functions are not supported for this API version or this model version." while enabling function calling feature. Functions are working fine with 4/4o GPT versions when tried separately.
In code, I am trying to add tools & tool_call parameters:
tools = [
{
"type": "function",
"function": {
"name": "get_current_weather",
"description": "Get the current weather in a given location",
"parameters": {
"type": "object",
"properties": {
"location": {
"type": "string",
"description": "The city and state, e.g. San Francisco, CA",
},
"unit": {"type": "string", "enum": ["celsius", "fahrenheit"]},
},
"required": ["location"],
},
},
}
]
model_args['tools'] = tools
model_args['tool_choice'] = 'auto'
Configuration:
Tried with GPT 4 & 40
version: 2024-05-01-preview
Can anyone please suggest the right way to do it.

Hi @codedash07, we recently (last 24 hours) updated the model support for data sources + functions. Can you give it another try? If it's still not working, can you share the exact model names & versions you're using, and which region your AOAI resource is in?

@sarah-widder The newer codebase does not throws error  "400 - Functions are not supported for this API version or this model version", . Any specific change was made in latest codebase?
For streamed responses with this bot, can you please share a sample usage with function calls. It would be really helpful.
Thanks in advance.

@codedash07 there was a change on the service side to update the supported model list for function calling with data. For more information on function calling, please reference the documentation here. Currently, only one data source can be used at a time.

@sarah-widder Thanks for this information.
Is function calling only supported with Assistants API currently? Unable to find any documentation around async chat completion calls with function calling.
For non-stream chat completion calls its works fine.

@codedash07 function calling is supported with chat completions, both streaming and non-streaming. For an SDK example, it may help to look at posts in the openai discussion forums - like this one or similar - https://community.openai.com/t/streaming-function-calls-does-not-return-an-id-with-tool-calls/608510/3
If the SDK is not working, calling the chat completions API directly is also always an option.

@sarah-widder  It seems like streaming has stopped working in the latest codebase. Is there ongoing any issue in frontend code?


Remove JSON marshalling of gaugeIDs

We use JSON marshalling for gaugeIDs in several locations. We should remove this, and replace it with a more efficient serialization format. This will need a state migration.
I just noticed it being used here: https://github.com/osmosis-labs/osmosis/blob/d3e00da98551cc77db54ea4de0f974703f298de2/x/incentives/keeper/store.go#L80 and in a couple iterators. We should change all of these to no longer be using json.

I'm closing this issue noticing that it isn't getting mistakenly getting JSON marshalled to the state machine, but only a process of unmarshalling.


Build fails on macOS Sierra

The minizip link stage fails because it can't find libz or isn't actually linking with libz. But because this libkml fork is using CMake, I can't tell what it is doing. The original Google project also fails to build, but there I can see exactly what Google is doing wrong and fix it.
If anyone wants to give me a crash course in debugging CMake, I will give it another shot. I'm no fan of automake and Google's automake in libkml is really broken. But at least I can fork Google's project and fix the code. CMake is a complete mystery.

could you able to see the cmake messages when building ?

I can see CMake's standard progress messages, but they aren't helpful when something goes wrong. Here is the output:
`
[ 70%] Building C object CMakeFiles/minizip.dir/aes/sha1.c.o
[ 76%] Linking C shared library libminizip.dylib
Undefined symbols for architecture i386:
"_crc32", referenced from:
_unzReadCurrentFile in unzip.c.o
_zipWriteInFileInZip in zip.c.o
"_deflate", referenced from:
_zipWriteInFileInZip in zip.c.o
_zipCloseFileInZipRaw64 in zip.c.o
"_deflateEnd", referenced from:
_zipCloseFileInZipRaw64 in zip.c.o
"deflateInit2", referenced from:
_zipOpenNewFileInZip4_64 in zip.c.o
"_get_crc_table", referenced from:
_unzOpenCurrentFile3 in unzip.c.o
_zipOpenNewFileInZip4_64 in zip.c.o
"_inflate", referenced from:
_unzReadCurrentFile in unzip.c.o
"_inflateEnd", referenced from:
_unzCloseCurrentFile in unzip.c.o
"inflateInit2", referenced from:
_unzOpenCurrentFile3 in unzip.c.o
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[5]: *** [libminizip.1.2.8.dylib] Error 1
make[4]: *** [CMakeFiles/minizip.dir/all] Error 2
make[3]: *** [all] Error 2
make[2]: *** [/tmp/cmake-build/third-party/Stamp/MiniZip/MiniZip-build] Error 2
make[1]: *** [CMakeFiles/MiniZip.dir/all] Error 2
make: *** [all] Error 2
`

you can do make VERBOSE=1 and additionally there is CMAKE_VERBOSE_MAKEFILE option. The latter must be passed when configuring using cmake.

I just found that myself.
`
[  5%] Linking C shared library libminizip.dylib
/Applications/CMake.app/Contents/bin/cmake -E cmake_link_script CMakeFiles/minizip.dir/link.txt --verbose=1
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -arch i386 -arch x86_64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk -mmacosx-version-min=10.12 -O3 -DNDEBUG -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk -mmacosx-version-min=10.12 -dynamiclib -Wl,-headerpad_max_install_names -headerpad_max_install_names -compatibility_version 1.2.8 -o libminizip.1.2.8.dylib -install_name /tmp/cmake-build/third-party/Build/MiniZip/libminizip.1.2.8.dylib CMakeFiles/minizip.dir/ioapi.c.o CMakeFiles/minizip.dir/unzip.c.o CMakeFiles/minizip.dir/zip.c.o CMakeFiles/minizip.dir/aes/aescrypt.c.o CMakeFiles/minizip.dir/aes/aeskey.c.o CMakeFiles/minizip.dir/aes/aestab.c.o CMakeFiles/minizip.dir/aes/entropy.c.o CMakeFiles/minizip.dir/aes/fileenc.c.o CMakeFiles/minizip.dir/aes/hmac.c.o CMakeFiles/minizip.dir/aes/prng.c.o CMakeFiles/minizip.dir/aes/pwd2key.c.o CMakeFiles/minizip.dir/aes/sha1.c.o
`
It isn't linking with libz.

i will try to fix a push for this. there are some changes regarding the whole build of zlib, I made sometime ago. i don't have access to that system now. but I will push it after work.
I will let you know tonight.

can you test this branch. I had fixed many build issues here.
https://github.com/libkml/libkml/tree/synced_upstream

I had to add boost to the third party directory. But now CMake is confused by my private frameworks. I am wrapping a bunch of open-source projects into frameworks so I can bundle and distribute them. CMake finds the following:
-- Found EXPAT: /Users/jdaniel/Library/Frameworks/expat.framework (found version "2.2.0")
However, that path doesn't exist. If Expat is a dependency, either pkg-config would return the include and libraries or I would specify them manually via environment variables. None of the project's I'm working with know (or are supposed to know) anything about frameworks.
Eventually, the build fails on /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -arch i386 -arch x86_64 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk -mmacosx-version-min=10.12 -O3 -DNDEBUG -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk -mmacosx-version-min=10.12 -dynamiclib -Wl,-headerpad_max_install_names -headerpad_max_install_names -compatibility_version 1.0.0 -current_version 1.3.1 -o ../../../lib/libkmlbase.1.3.1.dylib -install_name /tmp/libkml-synced_upstream/lib/libkmlbase.1.dylib CMakeFiles/kmlbase.dir/attributes.cc.o CMakeFiles/kmlbase.dir/csv_splitter.cc.o CMakeFiles/kmlbase.dir/date_time.cc.o CMakeFiles/kmlbase.dir/expat_handler_ns.cc.o CMakeFiles/kmlbase.dir/expat_parser.cc.o CMakeFiles/kmlbase.dir/file.cc.o CMakeFiles/kmlbase.dir/file_posix.cc.o CMakeFiles/kmlbase.dir/localec.cc.o CMakeFiles/kmlbase.dir/math_util.cc.o CMakeFiles/kmlbase.dir/mimetypes.cc.o CMakeFiles/kmlbase.dir/referent.cc.o CMakeFiles/kmlbase.dir/string_util.cc.o CMakeFiles/kmlbase.dir/time_util.cc.o CMakeFiles/kmlbase.dir/uri_parser.cc.o CMakeFiles/kmlbase.dir/version.cc.o CMakeFiles/kmlbase.dir/xml_namespaces.cc.o CMakeFiles/kmlbase.dir/zip_file.cc.o CMakeFiles/kmlbase.dir/contrib/minizip/unzip.c.o CMakeFiles/kmlbase.dir/contrib/minizip/iomem_simple.c.o ../../../third_party/CMakeFiles/MINIZIP.dir/zlib/contrib/minizip/unzip.c.o ../../../third_party/CMakeFiles/MINIZIP.dir/zlib/contrib/minizip/zip.c.o ../../../third_party/CMakeFiles/MINIZIP.dir/zlib/contrib/minizip/mztools.c.o ../../../third_party/CMakeFiles/MINIZIP.dir/zlib/contrib/minizip/ioapi.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriCommon.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriCompare.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriEscape.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriFile.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriIp4.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriIp4Base.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriNormalize.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriNormalizeBase.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriParse.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriParseBase.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriQuery.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriRecompose.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriResolve.c.o ../../../third_party/CMakeFiles/URIPARSER.dir/uriparser/src/UriShorten.c.o /usr/lib/libz.dylib /Users/jdaniel/Library/Frameworks/expat.framework  ld: can't map file, errno=22 file '/Users/jdaniel/Library/Frameworks/expat.framework' for architecture i386 clang: error: linker command failed with exit code 1 (use -v to see invocation)
If that last item would have been the correct path /Users/jdaniel/Library/Frameworks/Expat.framework/Versions/Current/unix/lib/libexpat.dylib, then it would have worked.
I might need to take another look at my framework scripts and do a better job providing a real framework with a valid umbrella header and keep it separate from the POSIX side. I guess you can go ahead and close this issue.  I've removed the "-Werror -pedantic" from Google's original project and it builds correctly now.

This is really close. cmake is searching for frameworks. you can disable it easily.  can you add below lines into root CMakeLists.txt
if(APPLE)
set(CMAKE_SYSTEM_FRAMEWORK_PATH "" CACHE PATH "" FORCE)
endif()
you can aslo set  set(CMAKE_FIND_FRAMEWORK NEVER)
https://cmake.org/cmake/help/v3.0/command/find_library.html

I'm trying another approach. I swapped the synced_upstream branch back in and it seems to work. I haven't built GDAL or run any tests yet, but it builds and GDAL appears to accept it.

IIUC, synced_upstream works for your case right?
If that is the case, i will merge it to master?

I have to check again. I had stopped using it because it was building the libraries incorrectly. They didn't have the appropriate ids or paths. But I just ran another build of just libkml and it looks OK now. I will have to run another full build.

OK. I have narrowed it down to something about the installation. It seems to build fine. But then when it installs, it strips the path off the dylib id and all internally referenced kml dylibs. This makes them unusable.

See https://cmake.org/Wiki/CMake_RPATH_handling
Supposedly, "CMake gives the user complete control over the RPATH of executables and libraries created using CMake". I find the opposite to be true.

I encountered the same build error mentioned at the beginning of this thread on MacOS 12.1 (21C52).  Fortunately this version mentioned  above by rashadkm completed the build.
https://github.com/libkml/libkml/tree/synced_upstream

This issue is almost 5 years old. If you review what I said back in 2017, it was building correctly for me too. But the installation step corrupts the binaries.
I long ago stopped using this project. I ported it all to an Xcode project and never looked back. I am currently going through my other libraries that were in better shape than this one. There are so many benefits to a native Xcode build that I'm porting them all. All credit goes to the GDAL project for switching to cmake so that I literally have no choice anymore.


yt support argument concatenating

before
yt 'brown eyed soul gone'
after
yt brown eyed soul gone

a9352a2c99808cd3a8effc81b3c85f44f660a48d


How to Manage the Large Hypersim Dataset for Reproduction?

Thank you for your outstanding contribution to the community!
I am trying to reproduce this work, but the Hypersim Dataset(~1.9TB) exceeds my local and cloud storage capabilities. What strategies or tools do you recommend for handling such a large dataset, especially for efficient access and training?

I noticed that you mentioned using 54K samples for training. To better understand and reference your experimental setup, could you kindly provide some information on the approximate memory usage of this dataset during training?
Your insights would be greatly helpful for my research.I sincerely appreciate it.(感谢大佬！)

The processed Hypersim dataset is much smaller. You can download and process it part-by-part (need some modifications to the preprocessing script though).

Can you tell me how many Gs there are in the processed Hypersim dataset, and can you provide a modified preprocessing script? I am a beginner in this area and I would appreciate it if you could provide it

The processed training set would be around 95GB.


add sledgehammer sprite - #126

The sledgehammer is pink to match the majority of the metal weapons, if a non-pink version is desired I can change it.

No, this is perfect. Thank you so much! :confetti_ball:


Can we make it so the test continues on screenshot failure and reports the failures at the end of the test?

I have a test that as multiple screenshots. If the first screenshot happens to fail it does not continue on with the rest of the test like it would if you used the built-in “cy.screenshot” option. Is there away to have it continue with the test even if it has a screenshot fails and report the failures at the end.

@danferk it's implemented already
let me know if it suits your needs


Refactoring compose function

Thanks for refactoring @shubho, this looks great!

Feel free to land the refactor..(I assume tests are passing?) Also might be good to run the timing benchmarks just to be sure nothing changed there. Relevant ones are:
./benchmarks/benchmark_functions
and
./benchmarks/benchmark_ctc

It seems I don't have land permission - can any of the folks with write access land? I want to add a CPU only data parallel implementation on top - so want to land this one first


Peer authentication failed for user "postgres" on initial chef run (reboot + 2nd run works fine)

I am trying to setup a fairly simple Vagrantfile that boots a VM with postgresql and creates a couple of users and databases using hw-cookbooks/database. In the end I need access to the database from the host machine, so I change the pg_hba.conf by setting a couple of attributes in the Vagrantfile:
chef.json = {
  "postgresql" => {
    "version" => "9.3",
    "password" => {
      "postgres" => "postgres",
    },
    "config" => {
      "listen_addresses" => "*"
    },
    "pg_hba" => [
      { "type" => 'host', "db" => 'all', "user" => 'all', "addr" => '<IP_ADDRESS>/16', "method" => 'md5' },
      { "type" => 'local', "db" => 'all', "user" => 'all', "addr" => '', "method" => 'trust' }
    ]
  }
}

Now, when I boot the VM for the first time I get FATAL:  Peer authentication failed for user "postgres". When I reboot the VM and run chef again everything works as it should, but I destroy and reprovision the VM a couple of times per month and it's just cumbersome.
I also see this in my log:
INFO: template[/etc/postgresql/9.3/main/pg_hba.conf] not queuing delayed action restart on service[postgresql] (delayed), as it's already been queued

So my guess is this has to do with the service notification having been changed from :immediately to :delayed and therefore when I try to create the users and databases during the initial convergence run the default pg_hba.conf is still in effect.
Am I doing something wrong? Help would be appreciated.

I'm having a similar issue - Creating databases in the same Chef run as configuring postgresql seems to me like a regular usecase.
Was there a particular reason the action was changed to :delayed?
+1

I experienced this on 3.4.14 but can not reproduce this on 3.4.20. So it seems to be fixed.


Problems with customizing pydantic error messages[QUESTION]

First check

[ ] I used the GitHub search to find a similar issue and didn't find it.
[ ] I searched the FastAPI documentation, with the integrated search.
[ ] I already searched in Google "How to X in FastAPI" and didn't find any information.

Description
I want to customize the wrong version of pydantic, but it doesn't work。
I would like to ask what I should do。

from pydantic import BaseModel, ValidationError
class Model(BaseModel):
v: str
# def __init__(self,v =None):
#     print('被调用了 外部类')
class Config:
    max_anystr_length = 1
    error_msg_templates = {
        'value_error.any_str.max_length': 'max_length:{limit_value}',
    }

@app.post("/items/")
async def create_item(item: Model):
return item

error_msg_templates definition does not work！
Thank you very much
How can I [...]?
Is it possible to [...]?
Additional context
Add any other context or screenshots about the feature request here.

This one is actually interesting. Looks like pydantic's internal error_dict() function is overriding the previous custom error message and falls back to default because it did not get a valid model from FastAPI. It's being used publicly but it's mostly a pydantic internal function, and I would not blame pydantic here. I am not sure if FastAPI can use pydantic's internal more wisely somehow.
https://github.com/samuelcolvin/pydantic/blob/d495710303c7716f0a54281b86a7c1c81930c223/pydantic/error_wrappers.py#L109-L111
A more self-contained testcase:
from pydantic import BaseModel, ValidationError
from fastapi import FastAPI
from fastapi.exception_handlers import request_validation_exception_handler
from fastapi.exceptions import RequestValidationError
from starlette.requests import Request
from starlette.responses import Response

class Model(BaseModel):
    v: str
    class Config:
        max_anystr_length = 1
        error_msg_templates = {
            'value_error.any_str.max_length': 'max_length:{limit_value}',
        }

app = FastAPI()

@app.exception_handler(RequestValidationError)
async def http_exception_accept_handler(request: Request, exc: RequestValidationError) -> Response:
    print(exc.raw_errors)
    print(exc)
    return await request_validation_exception_handler(request, exc)

@app.post("/")
async def create_item(item: Model):
    return item

try:
    Model.validate({'v':'x' * 20})
except ValidationError as e:
    print(e)

So, to override defaults one should use explicit @validator decorator to every property?

I got the same Problem also!
I tested the same code in pydantic, it's OK, but in the environment of fastAPI, it returned the default error msg.
from pydantic import BaseModel, ValidationError

class UserModel(BaseModel):
    name: str
    age: int
    class Config:
        error_msg_templates = {"type_error.integer":"The param must be an integer!"}

try:
    d = {"name":'aaa', "age":"ee"}
    u = UserModel(**d)
    print(u)
except ValidationError as e:
    print(e)

# age
#  The param must be an integer! (type=type_error.integer)

this is the code with fastAPI
from fastapi import FastAPI
from pydantic import BaseModel

app = FastAPI()

class User(BaseModel):
    name: str
    age: int
    class Config:
        error_msg_templates = {"type_error.integer":"The param must be an integer!"}

@app.post('/')
def index(u:User):
    return u

And the error msg is:
{
    "detail": [
        {
            "loc": [
                "body",
                "u",
                "age"
            ],
            "msg": "value is not a valid integer",
            "type": "type_error.integer"
        }
    ]
}

I think this issue must be considered as a bug. We are a lot of people that override Pydantic error messages using the standard way, so I guess it should work out of the box like everything in FastAPI :)

@elrik75 As I mentionner in another comment, you can override the default schema for ValidationError, so it appears in OpenAPI: https://github.com/tiangolo/fastapi/issues/1376#issuecomment-756276509
Not ideal, but tested on a projet and it does the job.

@elrik75 As I mentionner in another comment, you can override the default schema for ValidationError, so it appears in OpenAPI: https://github.com/tiangolo/fastapi/issues/1376#issuecomment-756276509
Not ideal, but tested on a projet and it does the job.

Figured out some workaround:
@app.exception_handler(RequestValidationError)
async def http_exception_accept_handler(request: Request, exc: RequestValidationError) -> Response:
    raw_errors = exc.raw_errors
    error_wrapper: ErrorWrapper = raw_errors[0]
    validation_error: ValidationError = error_wrapper.exc
    overwritten_errors = validation_error.errors()
    return JSONResponse(status_code=status.HTTP_422_UNPROCESSABLE_ENTITY,
                        content={"detail": jsonable_encoder(overwritten_errors)},
                        )

Now output will be as expected

Well done, It do works.


HDFS-14260: Synchronized Method in BlockReceiver Can Be Replaced with…

… Atomic Value

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
0
Docker mode activated.

-1
patch
12
https://github.com/apache/hadoop/pull/483 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/483

JIRA Issue
HDFS-14260

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-483/1/console

versions
git=2.7.4

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
0
Docker mode activated.

-1
patch
8
https://github.com/apache/hadoop/pull/483 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/483

JIRA Issue
HDFS-14260

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-483/2/console

versions
git=2.17.1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
0
Docker mode activated.

-1
patch
10
https://github.com/apache/hadoop/pull/483 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/483

JIRA Issue
HDFS-14260

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-483/3/console

versions
git=2.17.1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
0
Docker mode activated.

-1
patch
9
https://github.com/apache/hadoop/pull/483 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hadoop/pull/483

JIRA Issue
HDFS-14260

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-483/4/console

versions
git=2.17.1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Close the PR because the code was committed via the patch attached to the jira.


KYLIN-4684 Fix web ui bug when create streamig table

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to Kylin?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have create an issue on Kylin's jira, and have described the bug/feature there in detail
[x] Commit messages in my PR start with the related jira ID, like "KYLIN-0000 Make Kylin project open-source"
[ ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If this change need a document change, I will prepare another pr against the document branch
[ ] Any dependent changes have been merged

Further comments
If this is a relatively large or complex change, kick off the discussion at user@kylin or dev@kylin by explaining why you chose the solution you did and what alternatives you considered, etc...

Pull Request Test Coverage Report for Build 6224

0 of 0   changed or added relevant lines in 0 files are covered.
6 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.002%) to 28.029%

Files with Coverage Reduction
New Missed Lines
%

core-job/src/main/java/org/apache/kylin/job/impl/threadpool/DefaultScheduler.java
2
80.23%

core-metrics/src/main/java/org/apache/kylin/metrics/lib/impl/MetricsSystem.java
4
68.33%

Totals

Change from base Build 6212:
-0.002%

Covered Lines:
26226

Relevant Lines:
93568

💛  - Coveralls

@zhangayqian  Do you have do a test/verify for this patch ?

Test
Reproduce in kylin3.1.0

Before this issue be fixed, set TS Partten to S when load streamingV2 table and save this table

Then check table schema of this table, found that the TS Partten is saved as MS actually.

Test in Fixed version

Set TS Partten to S when load streamingV2 table and save this table

Then check table schema of this table,  the TS Partten is saved as S.

Test Result

Issue be fixed by this PR.

Thank you @zhangayqian .


Airspeed preflight checks update

Some updates to the airspeed preflight checks.
Describe problem solved by this pull request

airspeed validity information given by the airspeed selector/validator is checked for preflight checks
user can set maximal allowed airspeed during arming (new parameter ASPD_MAX_ARM)

Describe your solution

listen to airspeed_validated instead of airspeed in the airspeed preflight checks
don't allow arming if airspeed_selector is down (as we then have no airspeed_validated data)
add confidence value to the airspeed_validated message, such that this can be checked at instant of arming (later we can also think about how to include it in the general airspeed validation checks)
add new parameter ASPD_MAX_ARM to set maximal allowed airspeed during arming (instead of hard-coded 4 m/s like now)
rename subsystem DIFFERENTIALPRESSURE to AIRSPEED as airspeed source doesn't need to be a differential pressure sensor

Test data / coverage
SITL and bench tested.
Else
The confidence indicator doesn't seem to work for the SDP3X sensors, I always get a confidence of 1.0000 when it's plugged in, 0 otherwise.

@RomanBapst thanks for the review, I've addressed your comments.
Do you have an opinion about using the airspeed confidence metric for the preflight checks, resp. of the confidence value of the airspeed overall? @dagar and me discussed it quickly last week, and came to the conclusion that it is probably not worth to keep on dragging that with us, firstly because we don't know of any case where it was detecting a stuck sensor and secondly because it would need a lot of tuning for different sensors (eg for the SDP3X sensors).

Just posting here to offer my support for this PR.  Looks like a good improvement for those of us who use airspeed.  thanks!

@Antiheavy do you by chance have any experience with the airspeed confidence indicator? Ever used it/saw it indicating an actual failure?

do you by chance have any experience with the airspeed confidence indicator? Ever used it/saw it indicating an actual failure?

Unfortunately I don't think we don't have much experience with "airspeed confidence indicator" yet.  The version of the airspeed failsafe we are using is a pre-v1.9 that we worked with @priseborough  to develop (very similar to what existed in v1.9 with a few minor differences).  I don't think the "confidence indicator" was part of that (was it?).  We have lots of flight data with the airspeed failsafe system using the "load factor ratio" and EKF Innovation test ratio criteria for failure detection.

do you by chance have any experience with the airspeed confidence indicator? Ever used it/saw it indicating an actual failure?

Unfortunately I don't think we don't have much experience with "airspeed confidence indicator" yet. The version of the airspeed failsafe we are using is a pre-v1.9 that we worked with @priseborough to develop (very similar to what existed in v1.9 with a few minor differences). I don't think the "confidence indicator" was part of that (was it?). We have lots of flight data with the airspeed failsafe system using the "load factor ratio" and EKF Innovation test ratio criteria for failure detection.

@Antiheavy no the airspeed confidence was always (as far as I know) only used to during the preflight checks, not in the in-air airspeed validity check.

@sfuhrer This is good to go from my side but would be good to get some testing on it.
If other people are going to test it then a test plan might be useful.

@sfuhrer Format check failed - do you have the pre-commit hook for format check installed? Run make check_format once to get it installed.

@LorenzMeier yeah I do, but the hook probably doesn't catch formatting issues during a rebase (which is where the format check slipped in I think). I've fixed it now, thanks for pointing it out!

@RomanBapst I've tested this on my own setups now, both with and without airspeed sensor. No problems seen, so from my point of view we could bring this in.
The only thing I'm still not entirely sure is if we should keep the airspeed confidence metric, as I never yet encountered a situation where it correctly detected a malfunctioning airspeed sensor.

@dagar as discussed on the devcall this week I removed any dependency of the preflight checks to the airspeed confidence level. As we then don't have any other consumer (beside HIL, see below), I don't see any reason to keep the airspeed confidence calculation and removed that as well from sensors. Do you agree?

@dagar I've revered the last commit, where I had removed the airspeed confidence completely. Not it's still there, but no longer used inside the preflight checks. Is this now good to go in from your perspective?


⚠ Bofrost.de has degraded performance

In c83514a, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1088 ms

Resolved: Bofrost.de performance has improved in 1f041c5 after 8 minutes.


Modifier keys in key config must be specified in the correct order.

The key definitions have a fixed order for modifier keys. User key config should be normalized to that order, to avoid confusion about unworking bindings.
We should probably have the following order: shift + ctrl + alt + meta + key
Example:
ctrl+shift+up will work because that's the order defined in key_mappings.py
shift+ctrl+up won't work (even though it should) since it's not defined anywhere.

Done in release v0.1.56


Explicit metadata manager classes.

This is intended as an alternative to #4227
At present, each metadata 'manager' object is created in its own unique class by the iris.common.metadata.metadata_manager_factory factory function.
But in practice, there is only one such class definition for each type of metadata class (aka BaseMetadata subclass),
( actually, only 5 of these ).  All the manager types are identical re--creations of those.
#4227 notes this as performance problem, and adds caching to avoid re-creating a manager class each time.
So, effectively, this just creates 5 reference classes + re-uses them.
Quite apart from performance issues, I think that the way managers all have unique types is already pretty odd, and also the code is rather unusual and hard to follow.
As I think @bsherratt also suggests there
The reason for the code complexity is the effort to avoid boilerplate repetition in the BaseMetadata class definitions and the related manager classes.
So, I feel that maybe a problem with #4277 is that the caching adds yet another "layer" to the code.
However, the basic performance problem it solves just goes back to defining each of the 5 manager classes once, instead of creating them dynamically.
Seeing that, and carefully considering the code + @bsherratt comments, I came to the conclusion that we can replace the factory approach with a more conventional class definition for each of the "manager classes".
So that's what this attempts to do.
I'm keen to see if we can do that in a more explicit and easy-to-follow way, without re-introducing too much repetition or boilerplate.
N.B. the appropriate manager class is then referenced directly by containing objects, instead of calling the factory function.
( see the small changes in cube.py / coords.py / aux_factory.py )

Turning out to be quite a tricky bit of code isn't it...
Just to clarify, my comment wasn't against using type to create a class. It's certainly unconventional so it does add to the complexity, but not necessarily the first thing I'd think to change. After all, a class block is literally syntactic sugar for type(name, bases, namespace) (well, plus some magic to avoid creating a closure over the class body).
I was just observing that we only need one Manager class per Metadata class, but the current code creates many more than that (one manager class per required manager instance). And furthermore that we could easily enumerate all the Managers and expose those in the module namespace instead of the factory. (Hence the code snippet of what that could look like)

we can replace the factory approach with a more conventional class definition for each of the "manager classes"
I'm keen to see if we can do that in a more explicit and easy-to-follow way, without re-introducing too much repetition or boilerplate.

I think these are mutually exclusive. If there isn't a factory function that takes a Metadata class and returns a Manager class, then the only alternative is that every new metadata class requires a corresponding incantation
@manager_class
class SomeNewMetadataManager(MetadataManager):
    metadata_class = SomeNewMetdata

It's not much boilerplate, but if it's valuable to easily be able to add new metadata classes, then surely it's already too much?

@bsherratt If there isn't a factory function ...  every new metadata class requires a corresponding incantation
... It's not much boilerplate ...

Of course you're right.  My feeling was, it looks a bit clunky but there is virtually nothing there to get wrong.
( Given that, when creating + using a new metadata type, you are not very likely to miss the fact that you need a new manager type, as the container boilerplate for that is now pretty obvious )
My first commit here did retain the factory approach, and the manager classes creation there is notably simpler.
It's a plain choice.
But after consideration, I think this (later) way is less clever, less pretty, but just that much simpler to understand (and therefore maintain).

Another point worth noting : we removed the need for the setstate/getstate/reduce to make picking work, which is a definite win.
That works whether or not you use the original
manager_class = factory_class(metadata_class) approach,
or the `@decorator: class MyManager(MetadataManager): metadata_class=MyMeta" one.
FWIW
I did try to replace the factory/decorator approach with an embedded class definition
(i.e. a "class ..." within the factory call, replacing the 'type' usage)
But that re-introduces the pickling difficulty (it doesn't associate the generated class directly with the module).
I'd love to get rid of that, I expect there's a way, but I couldn't work out how.

Alright, I'll admit you intrigued me with the pickling issue
So it turns out that pickling custom objects requires that its type's __qualname__ resolves to the type object.
It also turns out that there's another little bit of magic that a class block has over type: it sets that __qualname__ by appending __name__ to the qualname of the current scope. type just leaves it the same as __name__. But each function call has its own scope, called eg funcname.<locals>, so the class qualname is nothing useful and it can't be (automatically) pickled.
I suppose messing with __qualname__ could open up any other wacky combination we wanted (MyMetadata.Manager anyone?) but that's clearly even more of a maintenance headache.

I didn't have much else to add by the way, I'm happy with "clunky but obvious" if everyone else is. Or indeed #4227, but for me I think this wins (sorry!)


Release on pypi

Hey there !
Could you by any chance upload the last version on pypi ? :) I'd like that before going the transformer route ! Thanks !
Cheers !

Done


Need requests, but missing from requirements

I tried to run fuel-download in a virtual environment, but it gave me this error:
Traceback (most recent call last):
  File "/Users/lahwran/blocks/ve/bin/fuel-download", line 5, in <module>
    from fuel import downloaders
  File "/Users/lahwran/blocks/ve/lib/python2.7/site-packages/fuel/downloaders/__init__.py", line 9, in <module>
    from fuel.downloaders import binarized_mnist
  File "/Users/lahwran/blocks/ve/lib/python2.7/site-packages/fuel/downloaders/binarized_mnist.py", line 1, in <module>
    from fuel.downloaders.base import default_downloader
  File "/Users/lahwran/blocks/ve/lib/python2.7/site-packages/fuel/downloaders/base.py", line 5, in <module>
    import requests
ImportError: No module named requests

I checked requirements.txt and setup.py, neither mention requests. Probably would be good to add that.

Thanks for the report. I made a PR.
I think the reason Travis didn't catch this is that it's getting pulled in as a dependency of another package only required for running the tests, possibly mock.


Deprection of Enforce ints for events?

This relates to https://github.com/mne-tools/mne-python/pull/2415
@Eric89GXL @agramfort I think we should add a deprecation warning to indicate that from now on mne won't accept non integers in the events array, and, in the meantime, try to convert it. I personally have several scripts that now crash because of a float array passed to EpochsArray(). I'm of course fine with correcting my scripts, but I suppose that I won't be the only one facing this issue.

This is difficult. There is nothing we deprecated in the strict sense. You normally deprecate a function or a parameter. A deprecation warning would require us to still provide the functionality.
It almost feels like a bug that we accepted float values in the first place.

I agree with you conceptually. I just think that in practice users may be annoyed.

I also don't think it quite applies as a deprecation, but rather as a bug fix. In other words, floating point values were never meant to be supported, and it was an error on our part not to type-check them previously. In this sense, that they worked at all in previous versions can be considered a matter of unfortunate happenstance. For example, you can't read and write such things to disk (here on 0.9):
>>> import numpy as np
>>> import mne
>>> events = np.zeros((1, 3))
>>> events[:, 2] = 1.5
>>> event_id = dict(foo=1.5)
>>> mne.EpochsArray(np.zeros((1, 1, 2)), mne.create_info(1, 1.), events,
                    event_id=event_id).save('temp-epo.fif')
>>> mne.read_epochs('temp-epo.fif')
...
  File "/home/larsoner/custombuilds/mne-python/mne/event.py", line 185, in _read_events_fif
    mappings = dict((k, int(v)) for v, k in m_)
  File "/home/larsoner/custombuilds/mne-python/mne/event.py", line 185, in <genexpr>
    mappings = dict((k, int(v)) for v, k in m_)
ValueError: invalid literal for int() with base 10: '1.5'
>>> Traceback (most recent call last):
  File "/home/larsoner/Desktop/untitled0.py", line 15, in <module>
    print(mne.read_epochs('temp-epo.fif').events)
  File "<string>", line 2, in read_epochs

Beyond such clearly failing cases, perhaps more concerning is that floats might also fail to work properly in other cases in some silent or in unexpected way that doesn't throw an exception. For example, there could be places we make use of isinstance(..., int) which won't do what it's supposed to with a float input, but will instead proceed into a branch that does not raise an error but instead does something silently bad.
If by "convert" you mean convert to integers on input, unfortunately we have no guarantee that previous behavior without such conversion would be maintained. We can't guarantee that such users didn't have events like 1.0, 1.01, 1.02, etc. that would all convert to the same event using a simple round; we can't know if they were doing arithmetic on event values so we can't e.g. convert the float64 bytes to int64 (which would otherwise preserve uniqueness), and so forth. Unfortunately a warning saying we are doing some simple conversion probably won't be sufficient to prevent users who were using floats from mistakenly proceeding with analyses. Warnings are a lot easier to ignore than errors, especially if a script has a lot of logging output.

Ok, I'm convinced, thanks for this detailed response.


Compiler status & tasks

Hello friends! I just merged in what I have so far for Swift code generation. Here's a status update on code generation overall:
Status
The new ReasonML compiler is significantly easier to work with than the original JavaScript one (and the small proof-of-concept TypeScript one I made), so I'm very happy with ReasonML and plan to continue in this direction.
I've made pretty good progress toward correct, performant Swift component code. There's still a lot left to do though. JS code is also close to working, but definitely needs a lot of tweaks. You can browse the current generated output for a test workspace I made here: https://github.com/airbnb/Lona/tree/master/examples/generated/test
I'll categorize what's left into a few categories below. The tasks vary a lot in size, but I think some will be pretty easy for others to pick up and can be done in parallel. Let me know if you see something you want to try!
Language-agnostic

[x] The code is pretty messy. Most Swift generation code is in one 1000 line file. I couldn't decide what would work better: organizing code by target (e.g. js, swift) or by purpose (e.g. outputting colors) so there's a mix of both right now. I think now that there's a decent amount of code, it might make sense to figure out what's working and what isn't and decide on the best organization. [Update: I organized code by target and started using subdirectories. I think future refactoring can be more incremental]
[x] Test cases. One day I think we'll want automated screenshots per target to catch visual regressions. I think for now we can just commit the generated code for the test workspace, and compare the diff when we change the compiler. It would be good to figure out a set of test cases that cover most of the core flexbox use cases. The code to generate constraints is complicated and I suspect it'll be easy to cause regressions without a comprehensive set of test cases.
[ ] The Logic language is designed around the current UI of Lona Studio, which I think will be limiting going forward. We should use a more standard AST format that the compiler and future tools can read and write more easily. Lona Studio will translate from the internal data structure to the new Logic AST we define.
[ ] Logic AST optimizations. After we've improved the Logic AST, there are some optimizations that can be performed on the Logic AST instead of being duplicated in the Swift/JS AST.
[x] There will probably eventually be multiple targets per language. E.g. JS => React, React Native, Vue, Angular. Swift => UIKit, ComponentKit. Might make sense to update the code to use the framework names instead.
[ ] Configurability. There are lots of ways people will want to customize the generated code. I have a few ideas here.

[x] I think we should have CLI options for extremely most common stuff.
[x] I think we should allow a config file (likely using cosmiconfig) akin to webpack/babel/eslint where more details options can be specified. If this config file can run JS code (e.g. config.js) then we can also support hooks for more detailed customization.
[ ] Eventually, separate the various targets of the compiler into different repos. Allow easy forking of individual targets. Code generation will likely need to be customized in an infinite number of ways that we can't support through a config-based approach.

Swift

[x] [@dabbott] Flexbox. I've handled some of the core layout properties, but there are many more to cover. E.g. alignment. Also, the current implementation has some issues even in the test files I've committed.
[x] Style properties. Properties like background color, border, etc, all need to be generated.
[x] [@dabbott] TextStyles. I think we should start by including something similar to the AttributedFont class in Lona Studio (this is similar to what we do in the Airbnb app), and then generating an instance of AttributedFont for each text style.
[x] Images. People will likely want to use their own image fetching/caches classes, so at some point we'll want to make this configurable. We'll also need to figure out how to bundle image assets from desk. I think to start, we can do something pretty simple to fetch remote images via URL, and not think about images on disk (Lona Studio doesn't handle these very well yet -- absolute file paths aren't very useful).
[x] [@dabbott] Custom components. I think the main challenge here will be that we need to figure out how to constrain the custom component to its parent. So far I've "solved" this in JS by assuming all custom components are within a parent with flexDirection: 'column'. This makes components entirely self-contained, which I think is an acceptable tradeoff. I'm not sure if the same technique will work in Swift though.
[x] Optional parameters. Lona Studio will likely need to make nullability more clear in a lot of places before this makes sense.
[x] View visibility. Currently the visible style is correctly applied to the isHidden property of views, but when a view is hidden, we need to update constraints so that other children within the same parent rearrange themselves. Otherwise, there may be a gap between components when a view is hidden.

JS
I haven't touched the JS code generation in a bit. The original compiler still works better than this new one. But it's mainly a matter of adding more features and fixing bugs.

[ ] Refactoring. This was the first code I wrote in ReasonML and some of it isn't very good. I'd probably have to look through the code more to find all the specifics, but e.g. the Swift AST uses objects which works very well, so the JS AST should do this too. The idea of converting all ASTs to a generic tree structure (tree.re) probably isn't a very good idea, since each AST node likely needs custom rules.
[x] Fixing bugs. There are lots of buggy things currently - e.g. we need to normalize layer names before using them as keys in the styles object.
[x] Imports. We don't import anything at the top of the file yet. We need this before the generated code is functional.
[x] Color generation - the format for this already exists in the original compiler -- we just need to regenerate it using the JS AST in Reason
[x] Text style generation - like colors, the format for this already exists

Kotlin/Java

[ ] Find somebody with Kotlin/Java knowledge?

FYI @ryngonzalez @NghiaTranUIT @GuillaumeSalles @jasonzurita

Most specific tasks here are done. Closing


Added missing Brazillian Portuguese translations

Added the following translations:

Credits button;
Difficulty settings buttons;
Renderer settings buttons;
Death message;
Dynamic sky button;
Cycle Item Type, Attack / Break, Pick Block and Use / Place Buttons;
Mouse Buttons
Changed the "Tip15" to support $keybind_pickBlock

I also added the $schema, I don't know if it is necessary. I did this so the pt-br file is closer to how the en-us file is written.

Thank you! Had to double check you were in the CREDITS.txt. May I ask why the Portuguese fallback entry was removed in metadata?

Other languages didn't have it, so I though it wouldn't matter if I removed it. May I ask what it is used for? And, should I add it back?
Also, I think schemas are used only if the language is uses other alphabet, if im correct, then I will remove the $schema entry since it's not necessary.

I'll merge it in now and add back the fallback, thank you


[objc] Move hash support to the processor

One of many cases to cover. The move helps in many ways, including
making sure the hash method addition is done before dupe names are
processed (e.g. a .net method/property could be named Hash)

Build and tests passed.


World.GetAllProps() doesn't work

As the title suggests, the World.GetAllProps() method doesn't work. For example, when I'm around a lot of props, it only returns about two out of them. There's obviously something wrong.

This has been known for a long time(ever since the feature got added) The method actually only returns Props in the script pool, not the game object pool. A fix will arrive once alexander updates scripthookv. You may aswell close this issue

What is the point of having the method if it doesn't do what it says?

Wasnt fully tested when it was first made, and considering its going to get fixed, there is no point removing it now. the issue also exists with World.GetAllPeds, GetAllVehicles and GetAllEntities

It's kind of bad, because I had planned to use the feature in a mod, and now it doesn't work properly. It's just a little bit frustrating.

This has been fixed, just waiting for the sdk to be updated on here before pushing it

pinging @crosire :)

Updated in<PHONE_NUMBER>012e3b5f10023e2521f2ad513d8761.

Should be fixed in abcc5c3ca10c4eee9bc17a97d32aa408788cec95.

How come I only get the player, and not rest of all the entities in the world?

This has been fixed


autobahn.cpp:79: error: C2664: 'Poco::Net::Context::Context(const Poco::Net::Context &)': cannot convert argument 5 from 'bool' to 'const std::string &'

Thanks for your work! I' ve tested this library with master head on linux and it compiles and works after removing #include "util/make_unique.h". But on windows 10 with vs 2015, I get the following error:
autobahn.cpp:79: error: C2664: 'Poco::Net::Context::Context(const Poco::Net::Context &)': cannot convert argument 5 from 'bool' to 'const std::string &'

When I open the Poco/Net/Context.h file ( I installed Poco with $ conan install Poco/1.7.5@lasote/stable). I found the constructor of this really doesn' t exist. I don' t know how to fix this. Any clues?

This library has been tested with POCO versions 1.5.4, 1.6.1 and 1.7.2. Version 1.7.5 also contains the constructor I'm using:
https://github.com/pocoproject/poco/blob/poco-1.7.5/NetSSL_OpenSSL/include/Poco/Net/Context.h#L190
On master it's still there.
Maybe an issue with that package manager? Cannot help you with that sorry.

Thanks. It works with poco compiled by myself.


Create Hub feature

Create a Hub feature so stores can be broken up in larger apps for scalability.

Created an extendStore prop option for the createStore function. This allows you to break up your stores to make them easier to maintain and create an index store.  Can also be used by 3rd party extensions to add state to the store.


does not always seem to work with multiple tags.

it seems to fail to tag to tag on multiple files with multiple tags and only tag the first one

Thanks for bringing this to my attention. The plugin automatically reduces the number of notes after a tag is selected if the selected notes already have the tag on them. Thereby, if you select five notes and four of them are already tagged with #mySelectedTag, only the note lacking #mySelectedTag will be changed.
If you're experiencing this in a different scenario, please let me know more precise steps I can take to repeat this issue and I'll do my best to troubleshoot what's going wrong.

Hi Gorky, thanks for getting back.
It seems to fail to do so. sometimes i get the tag on all notes, sometimes only on the first one. would it recognize a tag like tags: [tagA, tagB]?

Yes, it will recognize all frontmatter tags that Obsidian considers valid:
tag: [tag1, tag2]

tags: tag1 tag2

Tags: tag1, tag2

Tag:
  - tag1
  - tag2

Note that the quick-tagger plugin consolidates these all into a single tags list. The plugin should solve this, not cause it, but if your note has a combination of tag, tags, Tag, and Tags in the frontmatter, only one will show in reading mode.
Please keep searching for a way to repeat the error you're seeing. Once you have a way to consistently repeat the bug, let me know and I can dig into it and identify the cause.

I just realized the side panel buttins are only for single tagging. right click menue works fine, lol.

Aha, thanks for the update! I see how that could be confusing.
I'll see if there are any improvements I can make with the ribbon icons, either by clarifying they only act on the current note or making it work with multiple notes selected. Unfortunately, I'm under the impression that the latter option will be too tricky and fragile.


persist mongo data between system restarts (don't use /tmp)

fixes #1730

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1731   +/-   ##
=======================================
  Coverage   98.58%   98.58%
=======================================
  Files          59       59
  Lines        2896     2896
=======================================
  Hits         2855     2855
  Misses         41       41

Hi @carchrae
Sorry I didn't take a look at this pull request earlier. I was away on vacation. I see that you already agreed to the BigchainDB CLA. I will send you the CLA follow-up email now.

Looks good.
Thanks, @carchrae !

This is to confirm that I agreed to and accepted the BigchainDB Entity (Organization) Contributor Agreement at https://www.bigchaindb.com/cla/ and to represent and warrant that I have authority to do so.
X9bqaKlBUhRq7YmmaR8AkgATBfeoA5U1atuVmNW7pJsl93mSKiSQMSpUfDcTWCe

Thanks @carchrae . That completes the CLA agreement process.
@krish7919 You can accept the requested changes and merge this pull request.

happy to help @ttmc - we are just starting to use bigchaindb so will try to contribute where we can.


"expires_at" not working properly

In LocalStorage,
Calculation of "expires_at" based on the "expires_in" is not calculating properly.
In oidc-client.min.js
line no 7999
this.expires_in == 7074
o.expires_in == 7199
Line no 1417
e.expires_in == 6795
and, here they are fixing "this.expires_at == wrong time"

This appears to be related to oidc-client. Please contact oidc-client if you need assistance.


A computer layout view should not allowing absolute assignment.

In UICatalog open Buttons and click on one of both buttons at the bottom. An exception will be firing because those buttons have Width anchored with type DimCombine. So, generics controls should not change that behavior unless in user control specific.
I also fixed the PositionCursor which should be positioned over the hotkey.
The radio button is not rendering the initial selection. So, I created a Refresh method that call OnSelectionChanged.

In cases that have to assign an absolute value this may be possible with like this:
			try {
				Width = w;
			} catch (Exception) {
				LayoutStyle = LayoutStyle.Absolute;
				Width = w;
			}


feat: Split words of query and send 1 query per word

This PR tries to improve the search times when there are several words.
Instead of considering the full query, we send several query for each word, ignoring very small words that are not capitalized.

feat: Split words of query and send 1 query per word
feat: Default debug search uses drafts
fix: Ignore search terms that are not capitalized and under 2 letters of length

This is related to https://github.com/visualize-admin/visualization-tool/issues/683

@l00mi When you have further information on whether the stardog full text search or our queries can be improved, could you post it here ? Thanks 🙇

Yes will do. Thank you for this inputs.


Add prerelease information to the new version

Feature Request
As an extension to generating a standard semver compatible version number, it would be handy to be able to append prerelease information. e.g.
nextVersion(prerelease: 'alpha')

would generate something like:
1.0.0-alpha

Can I try to work on this ?


Rancher issue with Remote mysql

Rancher versions:
rancher/server: 1.6.5
rancher/agent:
Infrastructure Stack versions:
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
Docker version: (docker version,docker info preferred) 1.13.1
Operating system and kernel: (cat /etc/os-release, uname -r preferred) Ubuntu 16.04
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Environment Template: (Cattle/Kubernetes/Swarm/Mesos) Cattle
Steps to Reproduce:
Results:
I am having issues making the rancher server work with remote mysql. I have verified that all db parameters are set correctly, getting following exception while creating/starting the rancher server(1.6.5). Anyways, it doesnt affect the working of the rancher server as all services appears to be running fine inside the rancher. Even deployment of custom catalog is fine. When I tried using multicontainer catalog with higher number of containers , its failing with same proxy error. Please check
2017-12-27 10:07:38,724 INFO    [main] [ConsoleStatus] Starting [89/90]: WebhookServiceLauncher
2017-12-27 10:07:38,724 INFO    [main] [ConsoleStatus] Starting [90/90]: project.template.reload
2017-12-27 10:07:38,793 INFO    [main] [ConsoleStatus] [DONE ] [138400ms] Startup Succeeded, Listening on port 8081
2017-12-27 10:07:48,112 ERROR [:] [] [] [] [ecutorService-2] [o.a.c.m.context.NoExceptionRunnable ] Uncaught exception io.cattle.platform.lock.ex
ception.FailedToAcquireLockException: Failed to acquire lock [SERVICE.ACCOUNT.CREATE.machineServiceAccount]
at io.cattle.platform.lock.provider.impl.StandardLock.lock(StandardLock.java:56) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl$1.withLock(AbstractLockManagerImpl.java:17) ~[cattle-framework-lock-0.5.0-SNAPSHO
T.jar:na]
at io.cattle.platform.lock.impl.LockManagerImpl.doLock(LockManagerImpl.java:30) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:13) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:
na]
at io.cattle.platform.lock.impl.AbstractLockManagerImpl.lock(AbstractLockManagerImpl.java:37) ~[cattle-framework-lock-0.5.0-SNAPSHOT.jar:
na]
at io.cattle.platform.service.launcher.GenericServiceLauncher.getCredential(GenericServiceLauncher.java:116) ~[cattle-iaas-logic-common-0
.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.docker.machine.launch.ComposeExecutorLauncher.setEnvironment(ComposeExecutorLauncher.java:40) ~[cattle-docker-machi
ne-0.5.0-SNAPSHOT.jar:na]
at io.cattle.platform.service.launcher.GenericServiceLauncher.doRun(GenericServiceLauncher.java:200) ~[cattle-iaas-logic-common-0.5.0-SNA
PSHOT.jar:na]
at org.apache.cloudstack.managed.context.NoExceptionRunnable.runInContext(NoExceptionRunnable.java:15) ~[cattle-framework-managed-context
-0.5.0-SNAPSHOT.jar:na]
at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) [cattle-framework-managed-context-0
.5.0-SNAPSHOT.jar:na]
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55) [cattle-framework-managed-conte
xt-0.5.0-SNAPSHOT.jar:na]
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:108) [cattle-framework-man
aged-context-0.5.0-SNAPSHOT.jar:na]
at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52) [cattle-framework-manag
ed-context-0.5.0-SNAPSHOT.jar:na]
at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) [cattle-framework-managed-context-0.5
.0-SNAPSHOT.jar:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_72]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_72]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_72]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_72]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_72]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_72]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_72]
time="2017-12-27T10:08:13Z" level=fatal msg="Failed to configure cattle client: Get http://localhost:8080/v2-beta: net/http: request canceled (Cl
ient.Timeout exceeded while awaiting headers)"
2017/12/27 10:08:13 http: proxy error: net/http: request canceled
time="2017-12-27T10:08:14Z" level=fatal msg="Exiting go-machine-service: Timed out waiting for transtion." service=gms
2017/12/27 10:08:14 http: proxy error: net/http: request canceled
time="2017-12-27T10:08:15Z" level=info msg="Starting go-machine-service..." gitcommit=v0.39.0 service=gms
time="2017-12-27T10:08:15Z" level=info msg="Waiting for handler registration (1/2)" service=gms
time="2017-12-27T10:08:15Z" level=info msg="Starting Rancher Auth service"
time="2017-12-27T10:08:15Z" level=info msg="Listening on :8090"
time="2017-12-27T10:08:15Z" level=info msg="Initializing event router" workerCount=5
time="2017-12-27T10:08:16Z" level=info msg="Connection established"
time="2017-12-27T10:08:16Z" level=info msg="Waiting for handler registration (2/2)" service=gms
time="2017-12-27T10:08:16Z" level=info msg="Starting websocket pings"
time="2017-12-27T10:08:16Z" level=info msg="Initializing event router" workerCount=250
time="2017-12-27T10:08:16Z" level=info msg="Connection established"
time="2017-12-27T10:08:16Z" level=info msg="Starting websocket pings"
time="2017-12-27T10:08:17Z" level=info msg="Installing builtin drivers" service=gms
time="2017-12-27T10:08:17Z" level=info msg="Downloading all drivers" service=gms
time="2017-12-27T10:08:17Z" level=info msg="Done downloading all drivers" service=gms
time="2017-12-27T10:08:24Z" level=info msg="Starting Catalog Service (port 8088, refresh interval 300 seconds)"
Sometimes I am getting following error too, in addition to the above one
time="2017-12-27T11:27:26Z" level=fatal msg="Failed to configure cattle client: Get http://localhost:8080/v2-beta/schemas: net/http: request canc
eled (Client.Timeout exceeded while awaiting headers)"
time="2017-12-27T12:09:08Z" level=error msg="Error reading the setting api.auth.provider.configured , error: Get http://localhost:8080/v2-beta/se
ttings/api.auth.provider.configured: net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
time="2017-12-27T12:09:08Z" level=error msg="UpgradeSettings: Error reading existing DB settings Get http://localhost:8080/v2-beta/settings/api.a
uth.provider.configured: net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
time="2017-12-27T12:09:08Z" level=fatal msg="Failed to upgrade the existing auth settings in db to new: Get http://localhost:8080/v2-beta/setting
s/api.auth.provider.configured: net/http: request canceled (Client.Timeout exceeded while awaiting headers)"

@vsknov is your remote db a clustered/ha setup?

We have tested with Mysql Version 5.5 and worked fine.
But when we testing with Mysql Version 5.7, facing above mentioned issue.
Can you please let me know, is there any setting changes required for V 5.7 other than one specified in the Rancher document.
Kindly help on the same.

@vsknov Can you please specify what exactly you are running?

Exact MySQL version or used packages/Docker images (Pure MySQL/MariaDB)
Standalone or clustered (Galera/Percona)?
Anything in front of the database servers (HAProxy, MaxScale)?

Please reply so we can help on this.


Discord.Net should be a metapackage, not an empty package with deps

Fixed in https://github.com/RogueException/Discord.Net/commit/34139c9b59e06fcfb497304def96b66554135bdc


Throwing :end_client_run_early during the recipe compile phase should not error.

Describe the Enhancement:
Implement a Chef Client run "blackout window" with no (or absolutely minimal) host impact during the period specified by an attribute.  An "Exit with success" during the compile phase would be ideal because the exit code could be placed at the very beginning of the run
Describe the Need:

Any host with heavy resource usage and/or time/thread-sensitive code ($ traders, lunch rush, ...)
Any installation with a periodic business-mandated "code-freeze"

Current Alternative

"Exit with success" from a Chef run during the converge phase by calling "throw :end_client_run_early".  This is not useful for CPU/disk-intensive hosts that are sensitive to the activity a normal Chef compile/converge puts on the system.
Schedule Chef using crond (much more complex if a blackout window is defined in an attribute)

Can We Help You Implement This?:
This should be a very simple implementation, since a "throw :end_client_run_early" during the compile phase already works - only returns an error/exception; either

change the behavior to match the converge phase exit (success) or
add a ":end_client_run_with_success" that behaves the same in compile and converge phases

My existing workaround (exit during converge phase) attached.
pb_freeze2.zip

% cat  /Users/lamont/zero/local-mode-cache/cache/chef-stacktrace.out
Generated at 2018-12-04 10:54:57 -0800
UncaughtThrowError: uncaught throw :end_client_run_early
/Users/lamont/zero/local-mode-cache/cache/cookbooks/test/recipes/default.rb:2:in `throw'
/Users/lamont/zero/local-mode-cache/cache/cookbooks/test/recipes/default.rb:2:in `from_file'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/mixin/from_file.rb:34:in `instance_eval'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/mixin/from_file.rb:34:in `from_file'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/cookbook_version.rb:199:in `load_recipe'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/run_context.rb:350:in `load_recipe'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/run_context/cookbook_compiler.rb:166:in `block in compile_recipes'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/run_context/cookbook_compiler.rb:163:in `each'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/run_context/cookbook_compiler.rb:163:in `compile_recipes'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/run_context/cookbook_compiler.rb:79:in `compile'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/run_context.rb:199:in `load'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/policy_builder/expand_node_object.rb:97:in `setup_run_context'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/client.rb:515:in `setup_run_context'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/client.rb:281:in `run'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/application.rb:303:in `run_with_graceful_exit_option'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/application.rb:279:in `block in run_chef_client'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/local_mode.rb:44:in `with_server_connectivity'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/application.rb:261:in `run_chef_client'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/application/client.rb:440:in `run_application'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/lib/chef/application.rb:66:in `run'
/Users/lamont/.rvm/gems/ruby-2.5.1/gems/chef-14.7.17/bin/chef-client:25:in `<top (required)>'
/Users/lamont/.rvm/gems/ruby-2.5.1/bin/chef-client:23:in `load'
/Users/lamont/.rvm/gems/ruby-2.5.1/bin/chef-client:23:in `<main>'
/Users/lamont/.rvm/gems/ruby-2.5.1/bin/ruby_executable_hooks:15:in `eval'
/Users/lamont/.rvm/gems/ruby-2.5.1/bin/ruby_executable_hooks:15:in `<main>'%

delaying to converge phase succeeds correctly:
ruby_block "whatever" do
  block do
    throw :end_client_run_early
  end
end

results in:
% chef-client -z -j dna.json
Starting Chef Client, version 15.0.96
resolving cookbooks for run list: ["test"]
Synchronizing Cookbooks:
  - test (0.0.1)
Installing Cookbook Gems:
Compiling Cookbooks...
Converging 1 resources
Recipe: test::default
  * ruby_block[whatever] action run

    Running handlers:
    Running handlers complete
    Chef Client finished, 0/0 resources updated in 03 seconds

It would be nice to be able to throw :end_client_run_early during compile to ensure that resources which run actions during compile don't get run. For example:
# cookbook_a/metadata.rb

depends 'cookbook_b'

# cookbook_a/recipes/default.rb

file '/tmp/test' do
  owner 'root'
  group 'root'
  action :nothing
end.run_action(:create)

# cookbook_b/attributes/default.rb
throw :end_client_run_early if condition_is_met

This feature request is currently being tracked at https://chef-software.ideas.aha.io/ideas/EFF-I-1. If anyone would like this kind of functionality please vote on that issue and comment. It's something we'd like to build.


Add TrustId parameter to swift driver

github/ncw/swift has added support for trust [1], so let's add it.
[1]https://github.com/ncw/swift/commit/8f232e4782787aee6ab31050e4aa75eb970b277c

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:humble00/distribution.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Will Docker distribution CI get the newest github.com/ncw/swift lib? I have add trust support to github.com/ncw/swift. But CI reports it is not supported.

Hi @humble00 According to the error message of circleci, you need to:

update the value of "Rev" at https://github.com/docker/distribution/blob/master/Godeps/Godeps.json#L99 for using the latest version of ncw/swift with additional "trustID" property

update the documentation about openstack v3 auth url in https://github.com/docker/distribution/blob/master/docs/configuration.md as I've found you got the v3 auth url updated in ncw/swift

go fmt your changed code

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:humble00/distribution.git somewhere
$ cd somewhere
$ git rebase -i HEAD~3
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

@nevermosby , I update the value of "Rev", but it doesn't work. How can I update the dependencies?

@humble00 I think u r good now for  jenkins and circleci since your code changes for ncw/swift have been included into your pull request.

LGTM

@RichardScothern ,I need this feature in our openstack project magnum. And the milestone is coming. Please have a look at this pr if you have time. Thank you.

LGTM


Update qtox to 1.10.2

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as ab966beb112015ffd909922982ad9258b2df001c. Your contribution is still credited to you.


chore: update qdrant examples

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

Project coverage is 0.00%. Comparing base (2e44434) to head (6d8550a).

Additional details and impacted files
@@          Coverage Diff          @@
##            main   #1321   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files         69      69
  Lines       6685    6685
=====================================
  Misses      6685    6685

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

/cherry-pick release-1.0-beta


how to add options like a different pot to agouti.Selenium()

Can you give an example in how this should work?
I did try to figure out fro the documentation, but get lost every time :-(
I see that I can use agouti.Selenium(options)
but unclear to me is how those options are,
and I think a more complete example would be nice

Hi @marcelloh,
Are you asking how to run Selenium on a custom port, or are you asking how to connect to an already running instance of Selenium?

I have no idea what agouti.Selenium(options) does.
If it connects to an already running Selenium, then explain what the options can do.
If it starts a selenium instance somehow, then... explain what the options can do.
If both is possible, then... explain what the options can do.

Agouti is documented here and at agouti.org.
agouti.Selenium() starts an instance of Selenium WebDriver automatically. Options are listed here, but do not include an option for changing the randomized port.
If you want to configure Agouti to start Selenium on a custom port automatically, you can use agouti.NewWebDriver, documented in detail here. See the implementation for agouti.Selenium as an additional example.
If you already have an instance of Selenium running, you can use agouti.NewPage() to connect to it. Just provide a URL to the webdriver.

I found out that with the following:
'''
var agoutiDriver *agouti.WebDriver
//agoutiDriver = agouti.PhantomJS()
//agoutiDriver = agouti.Selenium()
agoutiDriver = agouti.ChromeDriver()
if err := agoutiDriver.Start(); err != nil {
panic(err)
//t.Fatal("Failed to start Chrome:", err)
}
'''
I could actually see what was wrong.
panic: failed to start service: failed to run command: exec: "chromedriver.exe": executable file not found in %PATH%
where the
t.Fatal("Failed to start Chrome:", err)
gives me:
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x7495ae]
which makes the error handling a bit useless for a human :-(

This is the expected behavior of the standard library testing.T.Fatal() method -- you can't pass it a nil interface value. The behavior is not related to Agouti.
It appears that you're running Windows and don't have ChromeDriver installed. Is this the case?

yes, a panic(err) did tell me this :-(


fix consider the large_block_len is 0

Proposed changes
If the large_block_len is 0, should not continue reading the block_len.

run buildall

run buildall

run buildall


Can a simple function be added?

Is it possible to add the option to add a delay in seconds between each SMS?

If I have a minute someday, I'll take a look

When do you expect it to release? I think I can create a delay timer and some other features.

Feel free to open a pull request if you do have time, I'll be happy to check it out !
M.
Le 7 d?c. 2015 ? 01:18, OpenSourceIsCool <notifications<EMAIL_ADDRESS>a ?crit :
When do you expect it to release? I think I can create a delay timer and some other features.

Reply to this email directly or view it on GitHubhttps://github.com/tiphedor/SMS-Spammer-Android/issues/6#issuecomment-162379431.

Cool, thanks!
https://www.avast.com/?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
This
email has been sent from a virus-free computer protected by Avast.
www.avast.com
https://www.avast.com/?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Mon, Dec 7, 2015 at 12:47 AM, Martin STEFFEN<EMAIL_ADDRESS>wrote:

Feel free to open a pull request if you do have time, I'll be happy to
check it out !
M.
Le 7 d?c. 2015 ? 01:18, OpenSourceIsCool<EMAIL_ADDRESS><EMAIL_ADDRESS>a ?crit :
When do you expect it to release? I think I can create a delay timer and
some other features.

Reply to this email directly or view it on GitHub<
https://github.com/tiphedor/SMS-Spammer-Android/issues/6#issuecomment-162379431

.

—
Reply to this email directly or view it on GitHub
https://github.com/tiphedor/SMS-Spammer-Android/issues/6#issuecomment-162417352
.


Created a minified version of the code

Created a minified versio if the code using https://mothereff.in/lua-minifier. Review requested

@all-contributors please add @Seniru for  code, doc, design, maintainance