Added support for XDG and .config configuration directories.

I prefer to have configuration files within ~/.config/, so I have written a small patch to add support for .config and $XDG_DATA_HOME.

Nice. Thanks!

Btw, this is now available from pypi.python.org from v0.1.10. Thanks again :)

Happy to help, thanks :)


Improve locations for external functions

For example:
type t = {
  foo : Foo.t option
} [@@deriving show]

The generated identifier Foo.to_string could be located either to the foo field or to the Foo.t type.
It would help with big records (No, I didn't wrote this monstrosity).

Good idea. This would be easy to fix using [@metaloc], I think.

I plan to do it, just posting bugs so I don't forget while debugging something else.

So, are you going to do it?

Apparently, I did forget ... I will try to make time, no guarantee. :(

Closing. Whoever needs this can implement this.

Oh, looks like this was fixed by @gasche  in 4fc257050.


video support possible?

Are you mixing the audio streams on the server and sending one mixed audio to each connected client?
If yes, would it also be possible to "tile" several incoming video streams into one?
Laurent

Hi, no plan in video yet.


Preprocessing for markdown lists

In Hugo, there must be a blank line before starting a list with * or numbers. This is not true in Jupyter. So we should find blocks of such lines and ensure they are preceded by a newline.

This should be fixed by enabling: noEmptyLineBeforeBlock
See https://gohugo.io/content-management/formats/#blackfriday-extensions
Leaving the issue open to update the readme

Closed in https://github.com/jbandlow/nb_hugo_exporter/pull/4


Create an Issue Template

To have a better organization with issues, an issue template is needed.
The template needs to have:

Description
Steps to Perform
Final Actions
Final Deadline

After the template is created, the related file will be in a directory in main branch.
Deadline :

13.00 - 23.02.2023

LGTM!


RTL support in translations

I made a Hebrew translation (here), but all the text is reversed. I've never done anything in Unity, though, so I have no idea how to fix that. Being a software developer, I guess I could google around and find a fix, but I was wondering if you have a quicker solution for me :)

Hi, thanks for working on a translation! I've added rtl support in the latest commit (you should just need to check the rtl checkbox on the _Hebrew.asset). Please let me know if it's not working correctly.


Ensure table name length is consistent across CPUs

Describe the contribution
To ensure consistency in the size of the CFE_TBL_FileHdr_t struct, this should be constrained to use only mission-scope definitions.
Also simplifies the structure definitions by NOT padding strings out to 32 bit multiples.  The default size of the strings are already 32 bit multiples so this is just unnecessary complexity.  There is also no major issue if not 32 bit aligned, as the compiler will add it automatically where needed.
Add a note in the related cfe_mission_cfg.h descriptions to affected values, that these should be kept as a multiple of 4 to maintain alignment.
Fixes #25
Testing performed
Built CFE using default/sample config
Verified no build issues, CFE and unit tests all run as expected (no change).
Expected behavior changes
No impact to behavior, but this may change the size of telemetry packets in some cases depending on the mission config.
System(s) tested on:
Ubuntu 18.04 (64 bit)
Contributor Info
Full name and company/organization of all contributors (required for acceptance)
Community contributors
You must attach a signed CLA (required for acceptance) or reference one already submitted

Switched base branch to rc-6.7.0 until it gets merged so all those changes don't clutter this change.

Commit 8fe60c3 contains the requested modifications


won't run with just scratch - needs base image.

Thanks for a nice project

I confirm that there is an issue with the current docker image, but the suggested solution is bad, it defeats the purpose of using multi-stage builds to reduce the final image size.
What's really causing the issue is the absence of CGO_ENABLED=0 environment variable, once I re-add it (it was recently removed), the image starts to work again.

Sorry about that. Should be fixed in 3a91baa.


RPC: Update hash to 32 byte value.

Update tests to new standard

Running the simple kvstore example, I am getting an error on parsing the result
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { code: ParseError, message: "Parse error. Invalid JSON", data: Some("expected 40-character hex string, got \"88D4266FD4E6338D13B845FCF289579D209C897823B9217DA3E161936F031589\" at line 9 column 3") }', src/libcore/result.rs:1084:5

It seems hashes have been update from 20 to 32 bytes. https://github.com/tendermint/tendermint/blob/master/CHANGELOG.md#v0260
This PR updates the hash and the tests

@ebuchman what are your thoughts on compatibility here? should we just target the latest Tendermint release only?

should we just target the latest Tendermint release only?

Yes, probably for now. We'll figure out a backwards compatibility story a bit later on ...

Any other fixes required?


fix: use single quote for values

fix #2

This will need to update the tests so they keep working. I'll create a PR with the necessary changes :)

This should be fixed now! Thanks for pointing this out. Fixed in v0.0.3 from #2


Use ktlint from different source

Ktlint has identation bug where it doesn't recognize
statement continuation or nesting.
DNM.

Ready to merge 👍


Allow plugins to override mediatypes registered by oteapi-core

Currently there is no semantics in how the strategies in oteapi-core stores information in the session. This is addressed by oteapi-dlite by  storing everything in a semantically well-defined collection accessible from the session. But oteapi-dlite is not able to e.g. register a json parser with mediatype application/json since that mediatype is already taken by oteapi-core.
The same is the case for accessService.
Current this issue blocks proper use of oteapi-dlite.
The easiest solution would be to move all current strategies in oteapi-core into a separate plugin.
But it might still be useful for the user to have a way to define the precedence between plugins and strategies in the case when two plugins provides a strategy for the same mediaType/accessService.

Have you tried to do this?
My idea to implement this was that I'd expect two values to appear for a single media type and then have always choose the one that isn't coming from the core, if this happens. But it might be that two values are not returned for the same entry point registration. So have you tried this?

Yes, I tried it and oteapi troughs an exception about conflicting mediatypes.
Splitting the dataresource datamodel into download and parse may solve my problem, since the new parseType would determine which parse strategy to use.
What happens if a plugin defines a download strategy with the same schema as oteapi-core?

This has been solved - closing it

How has this been solved? The last point was that an exception was thrown, has this been resolved by some PR?

Wrongly closed.


Revert "Async validation support for multiple fields"

Reverts erikras/redux-form#3134
I changed my mind. It shouldn't do this, as this means there is no good way to clear an async validation error.
The field-level async validation that #3134 was moving towards will require a separate action to set the errors.

Codecov Report

Merging #3171 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #3171   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          68      68
  Lines        1511    1507    -4
======================================
- Hits         1511    1507    -4

Impacted Files
Coverage Δ

src/createReducer.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[IRGen] Cast fixed-size opaque globals.

In https://github.com/apple/swift/pull/66560 , a bug in the lowering of global_addr was fixed.  Part of that fix was to postpone mapping the type of the global into context until getting the address of the global and projecting the buffer for the out-of-line value; at that point, the type is mapped into context and the address is cast.
It introduced an issue for fixed-size globals, however: the type of such globals was not mapped into context; the result was that the lowered value set for the corresponding SIL value would have the wrong type.
Fix that by extracting the code which mapped the type into context and cast the address to the appropriate lowered type into a lambda and call that lambda both in both the fixed-size (newly) and non-fixed-size (as before) cases.
rdar://114013709

@swift-ci please test


Canno't create c9 account without credit card.

As I see in tutorial, in the past you could create account free but now I can't create c9 account without credit card. Any suggestions?

Hi @cerushdope, FCC now recommends using https://glitch.com/ as a c9 alternative.

@huyenltnguyen  yeah, but how can I go on with the tutorial?

What tutorial are you referring to? Would you mind posting the link here?

Yes, we need to update the production challenges to recommend using glitch instead.
For example this:
https://www.freecodecamp.org/challenges/manage-packages-with-npm
We anticipate moving to the newer beta edition where this is already done. But for now, its alright if we can replace the links in the challenges, with a a guide to using glitch as an alternative.
Contributions needed:

Create a guide on using Glitch, at guides.freecodecamp.org
Replace the links on backup/master with the link to the guide, and update the instructions.

@QuincyLarson do you think this is Okay? Or should we just wait for launching beta and avoid this interim fix?

P.S: The original issue https://github.com/freeCodeCamp/freeCodeCamp/issues/9826

@raisedadead Thanks for the link. I was totally unaware of the challenge (I went straight to the beta after I finished the front-end cert).
If I may throw in my two cents on the matter,

Create a guide on using Glitch, at guides.freecodecamp.org

Agreed.
@QuincyLarson There is an idea just popped up in my head. What do you think about making a short youtube video on this, too? I think the visual would make it easier for users to follow, compared to having to read and mentally locate where a button is.

Replace the links on backup/master with the link to the guide, and update the instructions.

What if we just leave it as it is and add a note at the top of all back-end challenges? The note could say something like: "We recommend using Glitch for back-end challenges. Follow this [link] for the setup guide. If you wish to use C9, continue with the instructions below."

@cerushdope My recommendation, as a camper, is to learn back-end on the beta site (https://beta.freecodecamp.org/en/challenges/managing-packages-with-npm/introduction-to-the-managing-packages-with-npm-challenges). Please note that your progress on beta will be lost once it goes live, so remember to backup your solutions and save it somewhere else.

@huyenltnguyen  Alright. Guess everything is settled here. Thanks a lot.

@cerushdope You're welcome. Happy coding!


First example in Modal page is not working

Hello.
I can do a PR for that but i want to add the imports section so anyone can easily copy paste the example. What do you think?

Fixed the error with incorrect usage of state in the example on master. I'll consider making Ellie examples for the more complex examples.


(Unnecessary) README Changes

Emphasize - Incomplete Jailbreak -, convert partially to HTML for improved look and future updates to the README.
Also highlight kúp some more as he was a notably big factor for bringing this project to life.

@sukarodo i approve 🥵


[#3946] Support conversion of HttpMessage and HttpContent to HTTP/2 Frames

Motivation:
HttpToHttp2ConnectionHandler only converts FullHttpMessage to HTTP/2 Frames. This does not support other use cases such as adding a HttpContentCompressor to the pipeline, which writes HttpMessage and HttpContent.
Additionally HttpToHttp2ConnectionHandler ignores converting and sending HTTP trailing headers, which is a bug as the HTTP/2 spec states that they should be sent.
Modifications:
Update HttpToHttp2ConnectionHandler to support converting HttpMessage and HttpContent to HTTP/2 Frames.
Additionally, include an extra call to writeHeaders if the message includes trailing headers.
Result:
One can now write HttpMessage and HttpContent (http chunking) down the pipeline and they will be converted to HTTP/2 Frames.  If any trailing headers exist, they will be converted and sent as well.

AUTOMATED MESSAGE for ADMINS:Please verify and accept the pull request.To accept, say @netkins acceptTo build again, say @netkins buildTo whitelist the author, say @netkins whitelist

@nmittler @Scottmitch please take a look.

@netkins acept

@netkins accept

I don't know why the tests are failing... They pass on my local

@nmittler @Scottmitch ping

@blucas Just took a first pass.  Looks pretty good overall!

@blucas - Thanks for the PR!  Finished first pass...looks good so far. Ping me when rdy for another review.

@nmittler @Scottmitch @normanmaurer addressed your comments please have another look.
I have re-written the method as per Nathan's suggestion. There is a lot less going on now, so may make more sense.

@blucas - Looks like there is also a unit test failure on the build.

@nmittler @Scottmitch PTAL
I have simplified the code further as per Nathan's suggestion.
I hope I've fixed the unit test failure.  The tests have always passed on my machine, so I can only think it is a 'timing' issue.  I added a CountDownLatch for trailers, and increased the request countdown to 4 in my tests.
I have tried to test the trailers in both Firefox (38.0.5) and Chrome (Version 43.0.2357.134 (64-bit)). Firefox works as expected (the page is rendered properly).  Unfortunately it looks like Chrome does not expect to receive a HEADERS frame after a DATA frame.  I think this is a bug with Chrome.  Search for "Additional headers received for request/response stream" in the HTTP/2 Frame output below:
7167: HTTP2_SESSION
www.mysite.com:443 (DIRECT)
Start Time: 2015-07-18 12:17:32.052

t=888877 [st=    0] +HTTP2_SESSION  [dt=30104]
                     --> host = "www.mysite.com:443"
                     --> proxy = "DIRECT"
t=888877 [st=    0]    HTTP2_SESSION_INITIALIZED
                       --> protocol = "h2"
                       --> source_dependency = 7166 (SOCKET)
t=888877 [st=    0]    HTTP2_SESSION_SEND_SETTINGS
                       --> settings = ["[id:3 flags:0 value:1000]","[id:4 flags:0 value:10485760]"]
t=888877 [st=    0]    HTTP2_STREAM_UPDATE_RECV_WINDOW
                       --> delta = 10420225
                       --> window_size = 10485760
t=888877 [st=    0]    HTTP2_SESSION_SENT_WINDOW_UPDATE_FRAME
                       --> delta = 10420225
                       --> stream_id = 0
t=888878 [st=    1]    HTTP2_SESSION_SEND_HEADERS
                       --> fin = true
                       --> :authority: www.mysite.com
                           :method: GET
                           :path: /
                           :scheme: https
                           accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
                           accept-encoding: gzip, deflate, sdch
                           accept-language: en-US,en;q=0.8
                           cache-control: max-age=0
                           user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.134 Safari/537.36
                       --> priority = 0
                       --> stream_id = 1
                       --> unidirectional = false
t=888881 [st=    4]    HTTP2_SESSION_RECV_SETTINGS
                       --> clear_persisted = false
                       --> host = "www.mysite.com:443"
t=888881 [st=    4]    HTTP2_SESSION_RECV_SETTING
                       --> flags = 0
                       --> id = 1
                       --> value = 4096
t=888881 [st=    4]    HTTP2_SESSION_RECV_SETTING
                       --> flags = 0
                       --> id = 3
                       --> value =<PHONE_NUMBER>
t=888881 [st=    4]    HTTP2_SESSION_UPDATE_STREAMS_SEND_WINDOW_SIZE
                       --> delta_window_size = 0
t=888881 [st=    4]    HTTP2_SESSION_RECV_SETTING
                       --> flags = 0
                       --> id = 4
                       --> value = 65535
t=888881 [st=    4]    HTTP2_SESSION_RECV_SETTING
                       --> flags = 0
                       --> id = 5
                       --> value = 16384
t=888881 [st=    4]    HTTP2_SESSION_RECV_SETTING
                       --> flags = 0
                       --> id = 6
                       --> value =<PHONE_NUMBER>
t=888974 [st=   97]    HTTP2_SESSION_RECV_HEADERS
                       --> fin = false
                       --> :status: 403
                           content-length: 7
                           test: denied=YesMozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.134 Safari/537.36
                           trailer: testing
                       --> stream_id = 1
t=888975 [st=   98]    HTTP2_SESSION_RECV_DATA
                       --> fin = false
                       --> size = 7
                       --> stream_id = 1
t=888975 [st=   98]    HTTP2_SESSION_UPDATE_RECV_WINDOW
                       --> delta = -7
                       --> window_size = 10485753
t=888975 [st=   98]    HTTP2_SESSION_RECV_HEADERS
                       --> fin = true
                       --> testing: 123
                       --> stream_id = 1
t=888975 [st=   98]    HTTP2_SESSION_SEND_RST_STREAM
                       --> description = "Additional headers received for request/response stream"
                       --> status = 1
                       --> stream_id = 1
t=888975 [st=   98]    HTTP2_SESSION_RECV_DATA
                       --> fin = true
                       --> size = 0
                       --> stream_id = 1
t=888975 [st=   98]    HTTP2_STREAM_UPDATE_RECV_WINDOW
                       --> delta = 7
                       --> window_size = 10485760
t=918981 [st=30104]    HTTP2_SESSION_GOAWAY
                       --> active_streams = 0
                       --> last_accepted_stream_id = 1
                       --> status = 0
                       --> unclaimed_streams = 0
t=918981 [st=30104]    HTTP2_SESSION_CLOSE
                       --> description = "Finished going away"
                       --> net_error = 0 (?)
t=918981 [st=30104]    HTTP2_SESSION_POOL_REMOVE_SESSION
                       --> source_dependency = 7167 (HTTP2_SESSION)
t=918981 [st=30104] -HTTP2_SESSION

@blucas LGTM
@Scottmitch do you want to take another look?

@blucas looks good...  could you squash the commits ?
@Scottmitch please take a final look.

@blucas - Just 1 nit. Please squash your commits and we can cherry-pick.

@normanmaurer @Scottmitch All commits squashed :)

@blucas cool... let me take care

@blucas... thanks!
Cherry-picked into master (3ec02bf7460c3fda4d382bdf4c3b9ef4c67704e1) and 4.1 (57d28dd42178b35194037a4ded7f26e20e676c62)


Restarts every few minutes since 0.3.3

Hi.
Since i Upgraded to 0.3.3 the camera restarts every few Minutes. I cant access rtsp stream then and also Not the Web interface. After a reboot the camera clicks and is back online. Im Not sure if this only happens in night Mode. But at the Moment it is in night Mode.
I got exactly the Same camera two Times. The other camera works like a charm.
Is there any way to reflash the camera by ssh or so?
Edit: i disabled the rtsp stream, rebooted, enabled it and rebooted again. It seems that fixed the restarting but after around 30 minutes it restarted again...

As stated dis- and reenabling the rtsp stream seems to worked as a fix

My second cam (y25) has the same issue. It seems it was random, that it was online for 10 hours. I tried to reflash both cams "offline" now, but it wont succeed as the cams restart too often.
Both cams arent in Nightmode now. so that isnt an issue

Has you change it to offline at Yi app ?
The cam stayed like this after going offline in the app and I had to recover a previous Yi image from the SD

no, I use(d) those two cams for a long time (at least 2 years) with yi-hack. I updated every single update (beside 0.3.0 where i got an error and had to update through ssh) with the OTA update. everything worked fine until 0.3.3...
A (temporary?) fix:
I could reset one of the two cams easily with the reset button on the back. I paired it (like it would be new) with the yicam app. I deleted the cam afterwards in the app and "flashed" the 0.3.3 yi-hack.. Its online for around 6 hours now.
I could NOT pair the second cam with the app. Although the reset worked and the cam connected to WiFi (it said so) the pairing to the yicam app failed (timeout). Then I flashed (at least i think i did) the original yicam firmware. Afterwards I could pair the cam with the app. There it was shown as "offline sinc 2022". i deleted it and repaired it with another name. This worked. Then i deleted the cam again in app and flashed the 0.3.3 completely new. It seemed to work, but when i switched some options in the web interface and saved them, the cam crashed and rebooted... I will keep you up to date


    assert(isRuntimeMessage(message), 0x122 /* "Message to unpack is not proper runtime message" */);

I've hit this assert on a new doc. Looking at Kusto, there are not that many hits, but I worry when I see hits from just released 0.50 & 0.51 builds:
union Office_Fluid_FluidRuntime_Error
| where Data_error contains "0x122"
| summarize count() by Data_eventName, Data_docId, Data_loaderVersion
The doc I hit it with is this:
https://www.office.com/launch/fluid/content?auth=2&action=edit&drive=b!70_cNOFlWEyzRzEcCorMTZAND7s98E5GvCj7qsbvKwKg49qsUtgNRYr38F2hc1Tg&item=01CGOBCIFXGRNNC4I7TVALTGYILMXTBAOZ&file=https:%2F%2Fmicrosoft-my.sharepoint-df.com%2Fpersonal%2Fkening_microsoft_com&siteUrl=https:%2F%2Fmicrosoft-my.sharepoint-df.com%2Fpersonal%2Fkening_microsoft_com
Not sure if it's shared with everybody or just me, but if it's not shared widely, we can share it.
Also note that Ke reported that he can still open it with old version of local code, so it feels like there is some bug in latest release(s)?
Can you please take a look?

I also downloaded this file, so have op stream, can share if needed

If anyone needs me to share this file, please ping me. I will leave this file alone and won't touch it.
Right now I can NOT open this file on office.com, and I can NOT open it from fluidpreview.office.ne.  But I can open it from dev.fluidpreview.office.net.

I believe this change introduced it - https://github.com/microsoft/FluidFramework/pull/7811
A new ContainerMessageType type "Rejoin" was added. Older versions of runtime don't have this type so when they get this message which was generated by a newer runtime, they assert.
@wes-carlson Can you fix this. We should also add validation around this. This should have been caught by our tests.

Can you also enable full compat for these tests - https://github.com/microsoft/FluidFramework/blob/b086e1187d2af923d22882ba4b274822ddf67fc0/packages/test/test-end-to-end-tests/src/test/stashedOps.spec.ts

Shouldn't this prevent that from happening:
https://github.com/microsoft/FluidFramework/blob/8e451ad7cbb58029a5a1ea32c918e1acccdc3175/packages/runtime/container-runtime/src/containerRuntime.ts#L1438

If this is confirmed to be latest regression, I'd love to ask you to focus on quick mitigation first - I really do not want to see more documents being corrupted (even if it's temporarily before new code is deployed) - user experience sucks. Worth starting a thread on LiveSite channel? I assume that made it to prod, right?

Shouldn't this prevent that from happening:
https://github.com/microsoft/FluidFramework/blob/8e451ad7cbb58029a5a1ea32c918e1acccdc3175/packages/runtime/container-runtime/src/containerRuntime.ts#L1438

That check is done before unpacking the message to ContainerMessageType. So, there the type is MessageType.Operation.

Looks like it went in 0.51. We should release a patch with fix for 0.51 and 0.52.

Create an issue to add validation for this - https://github.com/microsoft/FluidFramework/issues/8409


Name in exported image partly missing

I have a json export file like this but when I export image it shows like this (The last word of each Name are missing)
On the browser:

On the file:

isoflow-export-2024-06-06T09 30 22.423Z.json
Am I missing something or this is just a bug.
Thank you so much for developing this beautiful diagram app !

@sakkarose thanks for flagging this.  There may be some issues with exporting depending on which browser you are using, could you let me the browser name (and version) you are using?  The recommendation is latest Chrome.

The one I used was Librewolf. I also have Chromium and Arc on my laptop. I will update with this being test on two other browsers.

I test on Arc. The description text on icon is now fine. But the text on arrow is getting a new line for the last word.

Here is the result on Chromium. Same result as Arc.

It's very weird, today I tried again on another machine with Librewolf and it's just like Arc and Chromium.


i18n(pt-BR): Update getting-started.mdx

Description (required)
Adds the updated PT-BR getting-started.mdx translation
Related issues & labels (optional)

Closes #
Suggested label:

The translation affects the spacing on the contributor grid, probably shouldn't happen:

Thanks, nice catch! Yeah, I guess that will happen for any language that needs a little more text than English (so most of them), I did some testing and it doesn't break anything in different viewports so we can tackle this on a later PR.

Thanks for the reviews, peeps!


MakerDAO TVL significantly higher than Defi Llama value

MakerDAO subgraph is showering that the total TVL is $9,110,531,585.

However, the TVL on Defi Llama is $7,897,615,105.

This has been fixed here: https://github.com/messari/subgraphs/pull/555
See https://subgraphs.messari.io/subgraph?endpoint=https://api.studio.thegraph.com/query/29379/makerdao-ethereum-v2/v0.0.2&tab=protocol


Reduce the overhead of multi-out layer

Currently, Multi-out layer is not included for the gradient sharing between layers. If the multi-out is not dominant, the overhead is not out-standing, but it is getting greater as it is used more frequently e.g., encoder and decoder in Transformer.
So for, NNTrainer adds the multi-out layer according to the network graph structure in realizer by multiout_realizer.cpp and it is possible to identify the derivatives of next multi-out layer can be added rather than overwrite. Therefore, we could change remmapper in multiout_realizer.cpp which takes the input with
std::string &id_, unsigned &idx_, boolean is_derivative_add

Of course, we need to add the RemapRealizer Constructor to have a kind of
private:
std::function<void(std::string&, unsigned &, bool )> remap_connection_with_derivative_add_fn;

and add relative function in layer_node.cpp, like,
void LayerNode::remapConnectionsWithAddDerivatives(std::function<void(std::string&, unsigned &, bool)> remap_fn);

:octocat: cibot: Thank you for posting issue #2056. The person in charge will reply soon.


Fix array shapes of AndroidConfig

The TTL has to be defined as "string" (Duration) instead of "int|double" as mentioned in referenced documentation https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages#androidconfig

Thanks Thorsten! The field is also referenced in the fromArray() method. FYI: I would have liked using PHPStan's type aliases, but PHPStorm doesn't support them (yet), that's why the shapes are duplicated so often 😅

Hey @jeromegamez :) yep missed that one 😄

Merged with https://github.com/kreait/firebase-php/commit/76c6dd381e44206cca97bec9f8abf39856365b5d, thanks again! 🌺


Use digest instead of tags in scorecard images

The use of tags breaks disconnected environments when using mirrored images.
Description of the change:
Reintroduces the use of Digest in the scorecard images instead of tags.
Motivation for the change:
Bring back default support to disconnected environments using scorecard.
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ x] Add or update relevant sections of the docs website in website/content/en/docs

Fixes: #6392

Thanks @everettraven I noticed the sanity test failed due to  a pair of typos fixed in the last commit, whenever you have time I appreciate your review

The docs sanity check is failing on an actually broken link but it will be fixed as part of #6394
Merging this


[BUG] Unable to setup fleet git repo in upstream cluster

Rancher Server Setup

Rancher version: v2.9-head (dcf32c221)
Installation option (Docker install/Helm Chart): docker
Proxy/Cert Details: n/a

Information about the Cluster

Kubernetes version: v1.29.3 +k3s1
Cluster Type (Local/Downstream): Upstream

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

Admin

Describe the bug

Fleet git repo gets stuck on Wait Applied (status.display.state WaitApplied)
cattle-fleet-local-system/fleet-agent-0 pod container fleet-agent-register log contains level=error msg="Failed to register agent: registration failed: cannot create clusterregistration on management cluster for cluster id

To Reproduce

Bring up v2.9-head in docker and wait for upstream pod creation to settle down
Navigate to Continuous Delivery --> change workspace to fleet-local --> Nav to Git Repos
Create git repo

repo https://github.com/rancher/fleet-examples
branch: master
path: simple

Result

Nav to upstream cluster --> Workloads --> Pods
View cattle-fleet-local-system/fleet-agent-0, init container never completes

Expected Result

fleet-agent-0 contains come up and fleet git repo reports as active

Screenshots

Additional context

This is currently blocking UI PR gates

Working as expected. Tests were setup using a localhost server-url so agent never came up. Tests were failing given change in fleet not reporting repo status.resources if the bundle fails to deploy (which was always the case in our ci)


Display CDP and LLDP from attached switches in Harvester

This is a REF for Harvester to display CDP (Cisco Discovery Protocol) and LLDP (Link Layer Discovery Protocol) information from attached switches within Harvester similar to VMware's showing of information within vSwitch.  Reference: https://www.provirtualzone.com/enable-link-layer-discovery-protocol-lldp-in-vswitch/

We're currently gathering this in a different way, but exposing this through the UI / labels would be awesome.


Continuing mapping to another cortical after created two different corticals

Add motion control
QC itself with projector
Add misc
Increase Misc's dimension to 4x1x1
Activate motion control once
Activate anything on MISC and it will qc projector on motion control itself.

https://github.com/feagi/brain-visualizer/assets/65916520/28545c52-c2bc-45dc-adef-c1fcac6cfff5
Before relaunch BV:

After relaunch BV:

Seems like this is FEAGI issue. It occurs on OPU only, not custom

I'm able to repo this easier:

Load Barebones (easiest genome)
Add Any OPU
Add another OPU
Check CB and see no map.
Reload BV and open the CB again, see that they are mapped

still able to repo this easily especially using API:

Load essential
Create OPU of servo
Create IPU of IR
Load it
See that IR mapped to Servo OPU automatically

Using API only:
endpoint: /v1/cortical_area/cortical_area

{
  "cortical_type": "OPU",
  "cortical_id": "o__ser",
  "coordinates_2d": [
    0,0
  ],
  "coordinates_3d": [
    40,0,0
  ],
  "channel_count": 1
}

{
  "cortical_type": "IPU",
  "cortical_id": "i__inf",
  "coordinates_2d": [
    0,0
  ],
  "coordinates_3d": [
    70,0,0
  ],
  "channel_count": 1
}

reload BV and see the issue

After restart everything and start FEAGI only.
Here is what I did:

Load essential genome thru api
Add Servo OPU thru API
Add IR thru API
Save genome
Load the saved genome
It is no longer there

I afraid something trigger that and we overlooked that

@Kakcalu13 any update on this?

@Kakcalu13 Was this ever fixed?

This is confirmed on feagi side

seems to be long fixed feagis side


Heroku push rejected

I am sorry this is the third time I am posting an issue here for you to help me, but after I tried many many 'solutions' i found around the web my problem wouldn't be fixed.
So I am trying to deploy the app with git push. Git respository is already commited and works just fine, but when I get to the git push heroku master I start getting an error about no Cedar-supported...
$ heroku buildpacks:set git://github.com/heroku/heroku-buildpack-python.git
Buildpack set. Next release on esouqbahrain will use git://github.com/heroku/heroku-buildpack-python.git.
Run `git push heroku master` to create a new release using this buildpack.

$ git push heroku master
Counting objects: 3849, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (3653/3653), done.
Writing objects: 100% (3849/3849), 12.73 MiB | 2.23 MiB/s, done.
Total 3849 (delta 1409), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Fetching custom git buildpack... done
remote:
remote:  !     Push rejected, no Cedar-supported app detected
remote: HINT: This occurs when Heroku cannot detect the buildpack
remote:       to use for this application automatically.
remote: See https://devcenter.heroku.com/articles/buildpacks
remote:
remote: Verifying deploy.....
remote:
remote: !       Push rejected to esouqbahrain.
remote:
To https://git.heroku.com/esouqbahrain.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/esouqbahrain.git'

Any idea for the fix? Thank you in advance

Okay, so I apologise. It was a silly mistake. I forgot to move the requirements.txt from the requirements folder to the root folder of the app.


pool.put()

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

$ go version
go1.16.3 windows/amd64

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GO111MODULE=on
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\86135\AppData\Local\go-build
set GOENV=C:\Users\86135\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=F:\gopath\pkg\mod
set GONOPROXY=git.addnewer.com
set GONOSUMDB=git.addnewer.com
set GOOS=windows
set GOPATH=F:\gopath;C:\Users\86135\go
set GOPRIVATE=git.addnewer.com
set GOPROXY=https://goproxy.cn,direct
set GOROOT=D:\LenovoSoftstore\Install\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=D:\LenovoSoftstore\Install\go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.16.3
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=F:\gopath\src\apiserver\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\Users\86135\AppData\Local\Temp\go-build1364965771=/tmp/go-build -gno-record-gcc-switches

What did you do?
why does not the method  pool.put()  epmty the object?

What did you expect to see?
i think pool.put() should empty the object such as bytebufferpool.put()，why not?
What did you see instead?

What pool?
Also, see https://golang.org/wiki/Questions.

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions


Mixed Reality Camera Manager settings not stored/retained

I tried to set near clip to 0.3 and quality to simple. Save scene, close Unity, Start Unity, settings are reverted again. At least in Unity 2017.1.2.f1, which is the recommended Unity version for a HoloLens app

This is a bug with MixedRealityCameraMangerEditor. Removing that fixes the issue.

Yeah it's not properly getting the serialized object.

Yeah I noticed. Unfortunately I don't know much about Editors. Giving the file a proper name is advisable too (there's an "a" missing

Halfway though a fix.  I'll post it shortly.

Well @keveleigh's fix works ;)


Support ParameterBlock arrays

In order to move the lighting system to ParameterBlock we need to be able to use the following syntax:
ParameterBlock<LightData> gLights[16].
On top of that, the current way in which Slang handle arrays-of-structs that contain textures make is hard to use pre-built parameter blocks. This is because it will convert the texture in LightData to
Texture2D some_slang_decore_gLights_texture[16].
For array of parameter blocks, we need each texture to use its own descriptor set.

Parameter blocks are not supposed to be used this way.
On Vulkan there is a limit on max parameter blocks you can use for a shader (it is 8), so an array of size 16 will likely not work.
It seems the right solution here is to either use ParameterBlock where LightDataArray is a struct of LightData[16], but as you have said it complicates working with textures.
The cleanest way to do so may be to use simulated bindless textures: instead of declaring Texture2D in LightData, we can simply define an int textureId. Then the engine passes all textures in a separate parameter block that is just an array of Texture2Ds. This requires the engine to manage such table of Texture2D resources but in general it makes handling texture resources much easier.

I had a discussion with Tim regarding ParameterBlock<LightDataArray>.
The main issue with that is that it prevents us from using a block per light, which is useful in case we want to stream light-data into the shader based on location (i.e. local point lights, light-probes, etc.)
It also means that for dynamic light sources (i.e. intensity changes with time) we will need to update the entire CB, even if most of the lights are static.
All of the above are solvable. Just want to make sure we're not missing something

Yeah, arrays of parameter blocks may not be a viable solution here due to API limits.
For light data streaming I'd put all LightData into a StructuredBuffer, and use a level of direction (light ids) to specifies which lights to use for a draw.
It shouldn't hurt that much to update small portions of the global light buffer per frame, especially when the engine partitions light data into static and persistently mapped dynamic buffers and use double buffering for dynamic data.

@nbenty I thought we’d had a Slack conversation about this and came to the conclusion that arrays of parameter blocks just flat out couldn’t be supported because there was no way to deal with dynamic indexing into the array (and ruling it out statically would be a big task for Slang).
@csyonghe I think the relevant point here is that Falcor wants to be able to wrap up each CPU-side light as a “thing” and then have a way to efficiently bind an array of such things. This is really strongly related to all the discussion we’ve been having lately about “sub-components” kinds of things.
My first thought (hastily typed on my phone, so take it with a grain of salt) is that the ideal answer for an application is to give each “shader component” style object a host accessible descriptor table (one or more) where binding get stored when set. Then allow the host-accessible tables to either be “flushed” to fresh GPU-accessible tables when you need to treat the component as a single top-level parameter block, or do a copy from those host-accessible tables into the backing storage of a larger “macro” parameter block. Either way the operation is just a single API call to copy descriptors from one table to another (for a contiguous range). There is a bit more work if the object wants to hold a CPU-side copy of any uniforms in the block.
This requires Slang to provide the layout information for the LightData type, even if it isn’t used directly as a parameter block. It also requires Slang to provide useful information that the app can use when binding a light into a larger block (e.g., for an array).

@tfoleyNV - correct, I'd like each C++ light object to hold a LightData parameter-block.
I don't mind copying the data. The problem is that Slang converts the array-of-structs (ParameterBlock<LightData> gLights[16]) into a struct-of-arrays (at least for the textures). This makes it hard to efficiently copy the descriptors for the block in the C++ object into the GPU descriptor table.
As a first (and potentially the only) solution, it would if all of the textures for a specific array-object will be contiguous.

Given that there is no (reasonable) way for us to support arrays of parameter blocks, I'm going to close this. The discussion was hopefully helpful in getting everybody on the same page.


samples: add quickstart publish sample

Quickstart publish sample will show up here.

Ping 6/11 FixIt Java folks for a review: @BenWhitehead @lesv


readonly & post issue

Fixed in https://github.com/yandex/ClickHouse/releases/tag/v1.1.54388-stable


Make the path to chown absolute

Otherwise, systemd rejects execution of these.
The upshot is that the files in said directories
remain owned by root:root, and therefore are
inaccessible to keylime. This in turn causes an
immediate attestation failure when measured boot
attestation is attempted.
Closes: #30

+1

I'm agree with this :)

@utkarsh2102 on systemd version 247.3-6 (Debian Bullseye) it works with the relative paths, but using the absolute path is a better idea.
Do you know on version it didn't work?


feat: activity 2 intro animation

animation for activity 2 intro

question:
are the images a bit blurry? i feel like they might be (my computer resolution isnt that high, does it make a difference on whoever is looking at this's computer?)
future:

add sound, and slow down animations to go with the sound
change intro lottie animations to be singular json with rasterized images

closes #43

@mattxwang
ty for the feedback, ill change them to vectorized and see how it turns out. unforutnatly its not svgs cuz AE doesnt support them, but i can just export as AI and hopefuly itll be good/same

makes sense! yea i agree, it'd also help with keeping the styling consistent. im currently working on a pr for making carousel and stuffs more consistent/other cleanup so maybe it'd be good to put in that pr? what do you think?


Add additional test for port and env flag

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind api-change
/kind bug
/kind cleanup
/kind deprecation
/kind design
/kind failing-test
/kind feature
/kind flake
/kind code-refactoring
Documentation changes: Please include [skip ci] in your commit message as well
/kind documentation
[skip ci]

What does does this PR do / why we need it:
Add additional test for env and port flag
Which issue(s) this PR fixes:
Fixes #?
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

[ ] I have read the test guidelines

How to test changes / Special notes to the reviewer:

@jichenjc We are currently trying to increase our unit tests and reduce our dependency on intg test so could please try to make this into a unit test if possible?

@girishramnani ok, I will close this one and add a new one if I can find some exapmle, thanks


Update to the latest version of the problem

Updated to the latest version, a lot of equipment in the final location contains invalid location information.
for example：The value of the positionId  in the device table valid is 0.

h02 protocol

Are you using official version without any modifications?

Basically no modification,And it was normal before the upgrade.

Basically? Are you sure you've updated config file?


Jupyter not working at /jupyter/

Jupyter index will redirect to /tree, which should be /jupyter/tree.

Fixed by #33


T page link

Here is a website link: https://www.facebook.com/trianglefoodbox/
I updated Airtable.

@GaneshT21 thanks for finding this!


Remove redundant fallback for app healthchecks

https://trello.com/c/fRihmgQ8/266-add-top-level-guidance-about-where-we-write-tests-on-govuk
This was added in ^1 without explanation.
I've checked and all apps have has_readiness_health_check set to
true wherever has_readiness_health_checkset is also set to true,
so this conditional branch is never used in practice.
I think it's clearer to have the alert work with just one type of
healthcheck and require someone adding an app to add both. This
means we can simplify the documentation for the alert.

In the comment you mention has_readiness_health_check twice - just to confirm you actually mean that everything with has_readiness_health_check also has has_liveness_health_check set, right?

Oops, thanks for spotting.
I've updated the commit and PR description.

Tested on Integration: leaving in place for 2 hours - enough time for Puppet state to update (1 hour) + reapply on monitoring (1 hour) - shows no change in the 135 total healthcheck alerts.


End of line

If parsed file is in DOS format, the end line is \r\n and not only \n
So parser will throw an exception

Hello, thanks for feedback. Could you provide a PR with the fix and add a test for this kind of files?

Sorry I don't have fix nor test for this
For now, I just apply $content = str_replace("\r\n", "\n", $content) before calling $reader->parse($content)
But I think it's should be done in FileParser::parse function ?

Yes it could be added there!

Another case with "end of line" problem is when all content is on single line.
that is take into consideration into FileParser::parse with
if (strlen($content) > $lineLength && !str_contains($content, "\n")) {
$content = chunk_split($content, $lineLength, "\n");
}
But sometimes, there is jsut one \n at the very end. Maybe the whole correction for 2 problem should be
$content = rtrim(str_replace("\r\n", "\n", $content), "\n");
at the begin of the function ?

It would be a way of improvement, if you could provide the file with these 2 differents cases and add it tests for it then we will be sure about the consistency of parsing

@guillaume-sainthillier see #275


Remove loginitems from configurations script

This error is causing the config script to break. It has been an issue since at least July 24:
https://github.com/pivotal/workstation-setup/issues/133
perhaps loginitems should be removed for now?

We would also need to remove https://github.com/pivotal/workstation-setup/blob/f584a0a26bd78afb4302bac2e85eda85ddba0ddf/scripts/configurations.sh#L14

Yes! I just removed that and another loginitems as well.


chore(main): release 0.1.2

:robot: I have created a release beep boop
0.1.2 (2024-11-23)
Bug Fixes

Use bookworm for build (9d0192e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/philipcristiano/owui-rag-sync/releases/tag/v0.1.2 :sunflower:


./byfn.sh up throws error

Error: Got unexpected status: SERVICE_UNAVAILABLE
Even after increasing CLI_TIMEOUT and CLI_DELAY to 100, the error occurs

Hey @anirudhkabi, thanks for raising the issue for it.
Not sure what's your OS? From my end it runs well under Ubuntu (16.04) and Travis CI (Ubuntu as well).
I will provide some steps to try to understand your local issue, hopefully you may follow it to provide valuable information.

Mark the code in byfn.sh by

function networkUp () {
......

#  sleep 12
#  docker exec cli scripts/script.sh $CHANNEL_NAME $CLI_DELAY $LANGUAGE $CLI_TIMEOUT
....

2.1 Run the following script in one new console (console1):
./byfn.sh up

You will see something in the end like:
Creating orderer.example.com ...
Creating orderer.example.com ... done
Creating cli ...
Creating cli ... done

Make sure you see orderer.example.com is done.
2.2 Open another console (console2) to run and see the log from orderer (If you have another tool like kitematic, you do not necessarily run by yourself)
docker logs -f orderer.example.com

BE NOTED: step2.1 and 2.2 should be run in parallel because you need to verify that the kafka self-checking log like this:
...
[sarama] 2018/03/04 05:54:48.198800 broker.go:146: Connected to broker at kafka2.example.com:9092 (unregistered)
[sarama] 2018/03/04 05:54:48.200471 client.go:397: client/brokers registered new broker #0 at 85ad5b5c61e9:9092
[sarama] 2018/03/04 05:54:48.200486 client.go:397: client/brokers registered new broker #1 at 66abc42c12b7:9092
[sarama] 2018/03/04 05:54:48.200493 client.go:397: client/brokers registered new broker #2 at 45f18a960094:9092
[sarama] 2018/03/04 05:54:48.200500 client.go:397: client/brokers registered new broker #3 at 41b8aba2be14:9092
...
2018-03-04 05:54:48.214 UTC [orderer/kafka] processMessagesToBlocks -> DEBU 108 [channel: testchainid] Successfully unmarshalled consumed message, offset is 0. Inspecting type...
2018-03-04 05:54:48.214 UTC [orderer/kafka] processConnect -> DEBU 109 [channel: testchainid] It's a connect message - ignoring

If all the steps above runs well, let's manually create the channel in the CLI :)
Open a third console (console3) to run

docker exec -it cli bash

Execute:
export CHANNEL_NAME=mychannel
peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

To see if it is successful?
If not running well, please copy more log from orderer (console2) here let me check it.
If it runs well, I don't know, you might need to trigger the cli by some other way, we may discuss it later after your test result on your local. Thanks.

2018-03-05 10:38:08.309 UTC [orderer/kafka] try -> DEBU 0f6 [channel: testchainid] Connecting to the Kafka cluster [sarama] 2018/03/05 10:38:08.309443 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.309537 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.309562 client.go:601: client/metadata fetching metadata for all topics from broker kafka1.example.com:9092 [sarama] 2018/03/05 10:38:08.314199 broker.go:96: Failed to connect to broker kafka1.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.314252 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.314269 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.314298 client.go:601: client/metadata fetching metadata for all topics from broker kafka0.example.com:9092 [sarama] 2018/03/05 10:38:08.315215 broker.go:96: Failed to connect to broker kafka0.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.315257 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.315273 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.315299 client.go:601: client/metadata fetching metadata for all topics from broker kafka2.example.com:9092 [sarama] 2018/03/05 10:38:08.316713 broker.go:96: Failed to connect to broker kafka2.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.316752 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.316768 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.316793 client.go:601: client/metadata fetching metadata for all topics from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:08.318071 broker.go:96: Failed to connect to broker kafka3.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.318103 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.318116 client.go:626: client/metadata no available broker to send metadata request to [sarama] 2018/03/05 10:38:08.318127 client.go:428: client/brokers resurrecting 4 dead seed brokers [sarama] 2018/03/05 10:38:08.318139 client.go:590: client/metadata retrying after 250ms... (3 attempts remaining) [sarama] 2018/03/05 10:38:08.568380 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.568483 client.go:601: client/metadata fetching metadata for all topics from broker kafka1.example.com:9092 [sarama] 2018/03/05 10:38:08.570440 broker.go:96: Failed to connect to broker kafka1.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.570567 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.570583 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.570625 client.go:601: client/metadata fetching metadata for all topics from broker kafka0.example.com:9092 [sarama] 2018/03/05 10:38:08.571908 broker.go:96: Failed to connect to broker kafka0.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.572014 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.572032 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.572073 client.go:601: client/metadata fetching metadata for all topics from broker kafka2.example.com:9092 [sarama] 2018/03/05 10:38:08.573380 broker.go:96: Failed to connect to broker kafka2.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.574321 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.574339 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.574427 client.go:601: client/metadata fetching metadata for all topics from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:08.576145 broker.go:96: Failed to connect to broker kafka3.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.576205 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.576219 client.go:626: client/metadata no available broker to send metadata request to [sarama] 2018/03/05 10:38:08.576277 client.go:428: client/brokers resurrecting 4 dead seed brokers [sarama] 2018/03/05 10:38:08.576291 client.go:590: client/metadata retrying after 250ms... (2 attempts remaining) [sarama] 2018/03/05 10:38:08.826636 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.826767 client.go:601: client/metadata fetching metadata for all topics from broker kafka1.example.com:9092 [sarama] 2018/03/05 10:38:08.833000 broker.go:96: Failed to connect to broker kafka1.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.833066 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.833110 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.833139 client.go:601: client/metadata fetching metadata for all topics from broker kafka0.example.com:9092 [sarama] 2018/03/05 10:38:08.846567 broker.go:96: Failed to connect to broker kafka0.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.846655 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.846671 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.846744 client.go:601: client/metadata fetching metadata for all topics from broker kafka2.example.com:9092 [sarama] 2018/03/05 10:38:08.871004 broker.go:96: Failed to connect to broker kafka2.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.871053 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.871069 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:08.871094 client.go:601: client/metadata fetching metadata for all topics from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:08.883073 broker.go:96: Failed to connect to broker kafka3.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.883127 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:08.883141 client.go:626: client/metadata no available broker to send metadata request to [sarama] 2018/03/05 10:38:08.883152 client.go:428: client/brokers resurrecting 4 dead seed brokers [sarama] 2018/03/05 10:38:08.883165 client.go:590: client/metadata retrying after 250ms... (1 attempts remaining) [sarama] 2018/03/05 10:38:09.133359 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:09.133427 client.go:601: client/metadata fetching metadata for all topics from broker kafka1.example.com:9092 [sarama] 2018/03/05 10:38:09.134798 broker.go:96: Failed to connect to broker kafka1.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:09.134833 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:09.134849 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:09.134872 client.go:601: client/metadata fetching metadata for all topics from broker kafka0.example.com:9092 [sarama] 2018/03/05 10:38:09.147221 broker.go:96: Failed to connect to broker kafka0.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:09.147282 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:09.147298 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:09.147321 client.go:601: client/metadata fetching metadata for all topics from broker kafka2.example.com:9092 [sarama] 2018/03/05 10:38:09.154653 broker.go:96: Failed to connect to broker kafka2.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:09.154702 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:09.154720 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:09.154768 client.go:601: client/metadata fetching metadata for all topics from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:09.178679 broker.go:96: Failed to connect to broker kafka3.example.com:9092: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:09.178775 client.go:620: client/metadata got error from broker while fetching metadata: dial tcp <IP_ADDRESS>:9092: getsockopt: connection refused [sarama] 2018/03/05 10:38:09.178793 client.go:626: client/metadata no available broker to send metadata request to [sarama] 2018/03/05 10:38:09.178805 client.go:428: client/brokers resurrecting 4 dead seed brokers [sarama] 2018/03/05 10:38:09.178821 client.go:187: Closing Client 2018-03-05 10:38:09.178 UTC [orderer/kafka] try -> DEBU 0f7 [channel: testchainid] Retrying every 1s for a total of 30s 2018-03-05 10:38:10.179 UTC [orderer/kafka] try -> DEBU 0f8 [channel: testchainid] Connecting to the Kafka cluster [sarama] 2018/03/05 10:38:10.179240 client.go:110: Initializing new client [sarama] 2018/03/05 10:38:10.179257 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:10.179391 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:10.179415 client.go:601: client/metadata fetching metadata for all topics from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:10.187163 broker.go:146: Connected to broker at kafka3.example.com:9092 (unregistered) [sarama] 2018/03/05 10:38:10.532725 client.go:154: Successfully initialized new client 2018-03-05 10:38:10.533 UTC [orderer/kafka] try -> DEBU 0f9 [channel: testchainid] Error is nil, breaking the retry loop 2018-03-05 10:38:10.538 UTC [orderer/kafka] startThread -> INFO 0fa [channel: testchainid] Producer set up successfully 2018-03-05 10:38:10.542 UTC [orderer/kafka] sendConnectMessage -> INFO 0fb [channel: testchainid] About to post the CONNECT message... 2018-03-05 10:38:10.542 UTC [orderer/kafka] try -> DEBU 0fc [channel: testchainid] Attempting to post the CONNECT message... [sarama] 2018/03/05 10:38:10.543030 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:11.100633 client.go:610: client/metadata found some partitions to be leaderless [sarama] 2018/03/05 10:38:11.100805 client.go:590: client/metadata retrying after 250ms... (3 attempts remaining) [sarama] 2018/03/05 10:38:11.351050 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:11.369408 client.go:610: client/metadata found some partitions to be leaderless [sarama] 2018/03/05 10:38:11.375028 client.go:590: client/metadata retrying after 250ms... (2 attempts remaining) [sarama] 2018/03/05 10:38:11.625323 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:11.661422 client.go:397: client/brokers registered new broker #0 at 8990d75b04fa:9092 [sarama] 2018/03/05 10:38:11.661805 client.go:397: client/brokers registered new broker #1 at 54aa5a50fc15:9092 [sarama] 2018/03/05 10:38:11.661955 client.go:397: client/brokers registered new broker #2 at c5af850cb064:9092 [sarama] 2018/03/05 10:38:11.662103 client.go:397: client/brokers registered new broker #3 at a201c9533fff:9092 [sarama] 2018/03/05 10:38:11.662266 client.go:610: client/metadata found some partitions to be leaderless [sarama] 2018/03/05 10:38:11.662417 client.go:590: client/metadata retrying after 250ms... (1 attempts remaining) [sarama] 2018/03/05 10:38:11.912843 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:11.929541 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:11.934371 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:38:11.934897 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:38:21.934927 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama] 2018/03/05 10:38:21.934980 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout [sarama] 2018/03/05 10:38:21.935036 async_producer.go:458: producer/leader/testchainid/0 state change to [retrying-1] [sarama] 2018/03/05 10:38:21.935049 async_producer.go:468: producer/leader/testchainid/0 abandoning broker 1 [sarama] 2018/03/05 10:38:21.935108 async_producer.go:663: producer/broker/1 shut down [sarama] 2018/03/05 10:38:22.035196 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:22.037657 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:22.038166 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:38:22.038189 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:38:22.038232 async_producer.go:446: producer/leader/testchainid/0 selected broker 1 [sarama] 2018/03/05 10:38:22.038256 async_producer.go:474: producer/leader/testchainid/0 state change to [flushing-1] [sarama] 2018/03/05 10:38:22.038266 async_producer.go:496: producer/leader/testchainid/0 state change to [normal] [sarama] 2018/03/05 10:38:32.037951 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama] 2018/03/05 10:38:32.038035 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout [sarama] 2018/03/05 10:38:32.038074 async_producer.go:458: producer/leader/testchainid/0 state change to [retrying-2] [sarama] 2018/03/05 10:38:32.038086 async_producer.go:468: producer/leader/testchainid/0 abandoning broker 1 [sarama] 2018/03/05 10:38:32.038170 async_producer.go:663: producer/broker/1 shut down [sarama] 2018/03/05 10:38:32.138460 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:32.142361 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:32.142821 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:38:32.143086 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:38:32.143246 async_producer.go:446: producer/leader/testchainid/0 selected broker 1 [sarama] 2018/03/05 10:38:32.143857 async_producer.go:474: producer/leader/testchainid/0 state change to [flushing-2] [sarama] 2018/03/05 10:38:32.144116 async_producer.go:496: producer/leader/testchainid/0 state change to [normal] [sarama] 2018/03/05 10:38:42.142937 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama] 2018/03/05 10:38:42.142990 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout [sarama] 2018/03/05 10:38:42.143069 async_producer.go:458: producer/leader/testchainid/0 state change to [retrying-3] [sarama] 2018/03/05 10:38:42.143143 async_producer.go:468: producer/leader/testchainid/0 abandoning broker 1 [sarama] 2018/03/05 10:38:42.143201 async_producer.go:663: producer/broker/1 shut down [sarama] 2018/03/05 10:38:42.243345 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:42.245854 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:42.246896 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:38:42.247145 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:38:42.247310 async_producer.go:446: producer/leader/testchainid/0 selected broker 1 [sarama] 2018/03/05 10:38:42.247472 async_producer.go:474: producer/leader/testchainid/0 state change to [flushing-3] [sarama] 2018/03/05 10:38:42.247609 async_producer.go:496: producer/leader/testchainid/0 state change to [normal] [sarama] 2018/03/05 10:38:52.246252 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama] 2018/03/05 10:38:52.246351 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout 2018-03-05 10:38:52.246 UTC [orderer/kafka] try -> DEBU 0fd [channel: testchainid] Retrying every 1s for a total of 30s 2018-03-05 10:38:53.246 UTC [orderer/kafka] try -> DEBU 0fe [channel: testchainid] Attempting to post the CONNECT message... [sarama] 2018/03/05 10:38:53.246687 async_producer.go:458: producer/leader/testchainid/0 state change to [retrying-1] [sarama] 2018/03/05 10:38:53.246704 async_producer.go:468: producer/leader/testchainid/0 abandoning broker 1 [sarama] 2018/03/05 10:38:53.246730 async_producer.go:663: producer/broker/1 shut down [sarama] 2018/03/05 10:38:53.346893 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:38:53.350037 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:38:53.350798 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:38:53.350928 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:38:53.350983 async_producer.go:446: producer/leader/testchainid/0 selected broker 1 [sarama] 2018/03/05 10:38:53.351175 async_producer.go:474: producer/leader/testchainid/0 state change to [flushing-1] [sarama] 2018/03/05 10:38:53.351241 async_producer.go:496: producer/leader/testchainid/0 state change to [normal] [sarama] 2018/03/05 10:39:03.350868 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama] 2018/03/05 10:39:03.350936 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout [sarama] 2018/03/05 10:39:03.351021 async_producer.go:458: producer/leader/testchainid/0 state change to [retrying-2] [sarama] 2018/03/05 10:39:03.351052 async_producer.go:468: producer/leader/testchainid/0 abandoning broker 1 [sarama] 2018/03/05 10:39:03.351084 async_producer.go:663: producer/broker/1 shut down [sarama] 2018/03/05 10:39:03.451204 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:39:03.453951 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:39:03.454319 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:39:03.454333 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:39:03.454354 async_producer.go:446: producer/leader/testchainid/0 selected broker 1 [sarama] 2018/03/05 10:39:03.454368 async_producer.go:474: producer/leader/testchainid/0 state change to [flushing-2] [sarama] 2018/03/05 10:39:03.454377 async_producer.go:496: producer/leader/testchainid/0 state change to [normal] [sarama] 2018/03/05 10:39:13.454186 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama] 2018/03/05 10:39:13.454248 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout [sarama] 2018/03/05 10:39:13.454300 async_producer.go:458: producer/leader/testchainid/0 state change to [retrying-3] [sarama] 2018/03/05 10:39:13.454314 async_producer.go:468: producer/leader/testchainid/0 abandoning broker 1 [sarama] 2018/03/05 10:39:13.454342 async_producer.go:663: producer/broker/1 shut down [sarama] 2018/03/05 10:39:13.554487 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:39:13.556593 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:39:13.556675 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:39:13.556697 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:39:13.556713 async_producer.go:446: producer/leader/testchainid/0 selected broker 1 [sarama] 2018/03/05 10:39:13.556751 async_producer.go:474: producer/leader/testchainid/0 state change to [flushing-3] [sarama] 2018/03/05 10:39:13.556761 async_producer.go:496: producer/leader/testchainid/0 state change to [normal] [sarama] 2018/03/05 10:39:23.556888 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout 2018-03-05 10:39:23.556 UTC [orderer/kafka] try -> DEBU 0ff [channel: testchainid] Attempting to post the CONNECT message... [sarama] 2018/03/05 10:39:23.556943 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout [sarama] 2018/03/05 10:39:23.557131 async_producer.go:458: producer/leader/testchainid/0 state change to [retrying-1] [sarama] 2018/03/05 10:39:23.557178 async_producer.go:468: producer/leader/testchainid/0 abandoning broker 1 [sarama] 2018/03/05 10:39:23.557228 async_producer.go:663: producer/broker/1 shut down [sarama] 2018/03/05 10:39:23.657405 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:39:23.659916 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:39:23.660375 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:39:23.660416 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:39:23.660442 async_producer.go:446: producer/leader/testchainid/0 selected broker 1 [sarama] 2018/03/05 10:39:23.660457 async_producer.go:474: producer/leader/testchainid/0 state change to [flushing-1] [sarama] 2018/03/05 10:39:23.660467 async_producer.go:496: producer/leader/testchainid/0 state change to [normal] [sarama] 2018/03/05 10:39:33.660446 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama] 2018/03/05 10:39:33.660505 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout [sarama] 2018/03/05 10:39:33.660557 async_producer.go:458: producer/leader/testchainid/0 state change to [retrying-2] [sarama] 2018/03/05 10:39:33.660570 async_producer.go:468: producer/leader/testchainid/0 abandoning broker 1 [sarama] 2018/03/05 10:39:33.660591 async_producer.go:663: producer/broker/1 shut down [sarama] 2018/03/05 10:39:33.760751 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:39:33.763114 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:39:33.764518 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:39:33.764774 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:39:33.764984 async_producer.go:446: producer/leader/testchainid/0 selected broker 1 [sarama] 2018/03/05 10:39:33.765122 async_producer.go:474: producer/leader/testchainid/0 state change to [flushing-2] [sarama] 2018/03/05 10:39:33.765248 async_producer.go:496: producer/leader/testchainid/0 state change to [normal] [sarama] 2018/03/05 10:39:43.763768 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama] 2018/03/05 10:39:43.763824 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout [sarama] 2018/03/05 10:39:43.763862 async_producer.go:458: producer/leader/testchainid/0 state change to [retrying-3] [sarama] 2018/03/05 10:39:43.763877 async_producer.go:468: producer/leader/testchainid/0 abandoning broker 1 [sarama] 2018/03/05 10:39:43.763919 async_producer.go:663: producer/broker/1 shut down [sarama] 2018/03/05 10:39:43.864064 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:39:43.866328 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:39:43.866809 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:39:43.867612 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:39:43.867758 async_producer.go:446: producer/leader/testchainid/0 selected broker 1 [sarama] 2018/03/05 10:39:43.867872 async_producer.go:474: producer/leader/testchainid/0 state change to [flushing-3] [sarama] 2018/03/05 10:39:43.867976 async_producer.go:496: producer/leader/testchainid/0 state change to [normal] [sarama] 2018/03/05 10:39:53.866588 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama] 2018/03/05 10:39:53.866658 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout 2018-03-05 10:39:53.866 UTC [orderer/kafka] retry -> DEBU 100 [channel: testchainid] Switching to the long retry interval 2018-03-05 10:39:53.866 UTC [orderer/kafka] try -> DEBU 101 [channel: testchainid] Attempting to post the CONNECT message... [sarama] 2018/03/05 10:39:53.866866 async_producer.go:458: producer/leader/testchainid/0 state change to [retrying-1] [sarama] 2018/03/05 10:39:53.866884 async_producer.go:468: producer/leader/testchainid/0 abandoning broker 1 [sarama] 2018/03/05 10:39:53.866913 async_producer.go:663: producer/broker/1 shut down [sarama] 2018/03/05 10:39:53.967075 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:39:53.969776 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:39:53.969935 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:39:53.969962 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:39:53.969982 async_producer.go:446: producer/leader/testchainid/0 selected broker 1 [sarama] 2018/03/05 10:39:53.969995 async_producer.go:474: producer/leader/testchainid/0 state change to [flushing-1] [sarama] 2018/03/05 10:39:53.970005 async_producer.go:496: producer/leader/testchainid/0 state change to [normal] [sarama] 2018/03/05 10:40:03.970046 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama] 2018/03/05 10:40:03.970240 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout [sarama] 2018/03/05 10:40:03.970345 async_producer.go:458: producer/leader/testchainid/0 state change to [retrying-2] [sarama] 2018/03/05 10:40:03.970364 async_producer.go:468: producer/leader/testchainid/0 abandoning broker 1 [sarama] 2018/03/05 10:40:03.970386 async_producer.go:663: producer/broker/1 shut down [sarama] 2018/03/05 10:40:04.070531 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:40:04.073103 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:40:04.073599 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:40:04.073629 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:40:04.073647 async_producer.go:446: producer/leader/testchainid/0 selected broker 1 [sarama] 2018/03/05 10:40:04.073902 async_producer.go:474: producer/leader/testchainid/0 state change to [flushing-2] [sarama] 2018/03/05 10:40:04.073913 async_producer.go:496: producer/leader/testchainid/0 state change to [normal] [sarama] 2018/03/05 10:40:14.073489 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama] 2018/03/05 10:40:14.073546 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout [sarama] 2018/03/05 10:40:14.073784 async_producer.go:458: producer/leader/testchainid/0 state change to [retrying-3] [sarama] 2018/03/05 10:40:14.073905 async_producer.go:468: producer/leader/testchainid/0 abandoning broker 1 [sarama] 2018/03/05 10:40:14.074050 async_producer.go:663: producer/broker/1 shut down [sarama] 2018/03/05 10:40:14.174239 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama] 2018/03/05 10:40:14.177434 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama] 2018/03/05 10:40:14.178324 async_producer.go:584: producer/broker/1 starting up [sarama] 2018/03/05 10:40:14.178353 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama] 2018/03/05 10:40:14.178377 async_producer.go:446: producer/leader/testchainid/0 selected broker 1 [sarama] 2018/03/05 10:40:14.178391 async_producer.go:474: producer/leader/testchainid/0 state change to [flushing-3] [sarama] 2018/03/05 10:40:14.178401 async_producer.go:496: producer/leader/testchainid/0 state change to [normal] [sarama] 2018/03/05 10:40:24.177739 broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama] 2018/03/05 10:40:24.177805 async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout 2018-03-05 10:40:24.177 UTC [orderer/kafka] try -> DEBU 102 [channel: testchainid] Retrying every 5m0s for a total of 12h0m0s

Thanks for your reply and sorry for such a huge log of orderer. What I can understand from the logs is that after lot of retries, the orderer is able to connect to kafka3 and fails to connect to other kafka containers. I am new to using kafka, cant interpret much when it says "not able to elect a leader".

021A0608AFC3F4D40522...C54F02703B9E94E190618E2F212DC4A3
2018-03-05 10:53:35.920 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: E45E8B3D4854364686069A8E4B25739524EC56E6DB499CB4F03F3C759175B413
2018-03-05 10:53:35.921 UTC [msp] GetLocalMSP -> DEBU 00a Returning existing local MSP
2018-03-05 10:53:35.921 UTC [msp] GetDefaultSigningIdentity -> DEBU 00b Obtaining default signing identity
2018-03-05 10:53:35.921 UTC [msp] GetLocalMSP -> DEBU 00c Returning existing local MSP
2018-03-05 10:53:35.921 UTC [msp] GetDefaultSigningIdentity -> DEBU 00d Obtaining default signing identity
2018-03-05 10:53:35.921 UTC [msp/identity] Sign -> DEBU 00e Sign: plaintext: 0A8C060A074F7267314D53501280062D...53616D706C65436F6E736F727469756D
2018-03-05 10:53:35.921 UTC [msp/identity] Sign -> DEBU 00f Sign: digest: E72D0E68A132F6E2538D037AE5462E628F898076E22ABB01E45B5CE1A3CEABA3
2018-03-05 10:53:35.921 UTC [msp] GetLocalMSP -> DEBU 010 Returning existing local MSP
2018-03-05 10:53:35.921 UTC [msp] GetDefaultSigningIdentity -> DEBU 011 Obtaining default signing identity
2018-03-05 10:53:35.921 UTC [msp] GetLocalMSP -> DEBU 012 Returning existing local MSP
2018-03-05 10:53:35.921 UTC [msp] GetDefaultSigningIdentity -> DEBU 013 Obtaining default signing identity
2018-03-05 10:53:35.921 UTC [msp/identity] Sign -> DEBU 014 Sign: plaintext: 0ABC060A0E08021A0608AFC3F4D40522...9A7AD73B6066BB3D7954691126FE4B6B
2018-03-05 10:53:35.921 UTC [msp/identity] Sign -> DEBU 015 Sign: digest: 0B2DE62DE33C12378F30B5236B1B599AB0114F2142F1AB80FC53E0DE399127A9
Error: Got unexpected status: BAD_REQUEST
Usage:
peer channel create [flags]
This is the logs for create channel

I compared my local log with yours, same with my local like
2018/03/05 10:38:11.661422 client.go:397: client/brokers registered new broker #0 at 8990d75b04fa:9092 [sarama]
2018/03/05 10:38:11.661805 client.go:397: client/brokers registered new broker #1 at 54aa5a50fc15:9092 [sarama]
2018/03/05 10:38:11.661955 client.go:397: client/brokers registered new broker #2 at c5af850cb064:9092 [sarama]
2018/03/05 10:38:11.662103 client.go:397: client/brokers registered new broker #3 at a201c9533fff:9092 [sarama]
2018/03/05 10:38:11.662266 client.go:610: client/metadata found some partitions to be leaderless [sarama]
2018/03/05 10:38:11.662417 client.go:590: client/metadata retrying after 250ms... (1 attempts remaining) [sarama]
2018/03/05 10:38:11.912843 client.go:599: client/metadata fetching metadata for [testchainid] from broker kafka3.example.com:9092 [sarama]
2018/03/05 10:38:11.929541 config.go:329: ClientID is the default of 'sarama', you should consider setting it to something application-specific. [sarama]
2018/03/05 10:38:11.934371 async_producer.go:584: producer/broker/1 starting up [sarama]
2018/03/05 10:38:11.934897 async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama]

Until the difference here:
async_producer.go:584: producer/broker/1 starting up [sarama]
async_producer.go:596: producer/broker/1 state change to [open] on testchainid/0 [sarama]
broker.go:96: Failed to connect to broker 54aa5a50fc15:9092: dial tcp: i/o timeout [sarama]
async_producer.go:762: producer/broker/1 state change to [closing] because dial tcp: i/o timeout [sarama]

you got the timeout stuff. Frankly I don't know..I just searched out from online see someone got the same  exception as yours: https://github.com/Shopify/sarama/issues/834


Handling invalid WriteToBigQuery use case

WriteToBigQuery with copy jobs doesn't support writing to a single table partition.
This PR is to throw an early error before beam starts up a copy job.
Also adding some documentation.

Run Python PreCommit

Run Python PreCommit

Run Python 3.8 PostCommit

Any updates ? If this change is not needed anymore, we should just close the PR.


Update usage of Spring boot

updated Spring boot version and removed the deprecated annotation.
replaced Field Injection with constructor and setter injection.
replaced the usage of @Value with a Properties bean.
This made it possible to replace the usage of ReflectionTestUtils with a mock of the Properties bean.

Thanks for your request! I already upgraded the Spring Boot version and adapted the tests. I'm not sure to adopt the constructor and setter injection approach as well as the properties beans. Have to think about it ...


Fix for using daily or hourly resolution market data for futures.

Open interest should use yyyyMMdd HH:mm in csv file when frequency is daily or hourly
Filename should be [baseticker]_[quote|openinterest|trade]_yyyyMM.csv

Thank you for the PR @smartquant; can you please add a few days of daily futures data in this format for testing of this PR? (ideally in ES or GC).

Hi Jared, I have uploaded an example data set for hourly and daily futures (GC and ES) as suggested converting the example minute data provided in the \Data folder. It took me a while to get my head around it, but I was able to use the consolidators for the job.
I am happy to write a test for loading the daily / hourly data, but I have not found an easy way to do this outside an algorithm, particularly when we want to load a whole future chain. Would need some guidance here.

@smartquant - When running the BasicTemplateFuturesAlgorithm with your changes (and the resolutions set to Daily)- I see that Slice.FuturesChain in OnData() has it's TradeBars and QuoteBars hydrated with the daily data.  I am also able to modify the filter and change the contracts selected. I think one way to test would be to add another futures example algorithm that uses the daily data and add a regression test for it.
There is also the LeanDataReader which could be helpful for writing unit tests.

Thanks @andrewhart098. Indeed the daily and hourly futures data was not correctly generated. I had to adapt the LeadDataReader to read the correct future within the zip file and re-generate the files. Code to generate the data is added as a unit test (but I have commented out the writing to the zip file).
As suggested I have added a regression test for daily futures data. Note the small bug fix in the Engine to make the history provider work correctly.


[ PROD-766] Fix issue with certain apps not rendering properly

App data returned from leo for certain apps seems to have changed, breaking some assumptions in the cloud environment page

googleProject is no longer returned from listApp API. This PR is to just make sure we're using cloudResource as fallback when saturnWorkspaceNamespace doesn't exist instead of googleProject
cloudContext.cloudResource will be the same as googleProject for google runtimes


Preview file in Recycle Bin

Provide a description of the new feature / enhancement
I want to preview the file in Recycle Bin as it is in the normal folder. Because I want to verify if I delete wrong or remember what it is.

Hello Clint Rutkas,I really don’t like Window Feedback Hub at all, it’s so difficult to use. ☹ I just think Power Toys can display the size of Folder in Recycle Bin, so I think you know exactly how to find it, so it's not hard to show it off. Sent from Mail for Windows 10 From: Clint RutkasSent: Saturday, May 1, 2021 1:24 AMTo: microsoft/PowerToysCc: Izumi; AuthorSubject: Re: [microsoft/PowerToys] Preview file in Recycle Bin (#11035) Honestly, a better spot for this is Windows Feedback Hub. This may not be something we have much control over—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.


Create nvd123stools.md

Can you help me create more links by deploying my repo here:
https://GitHub.com/interstellarforker/nvd123ishim
My Vercel links stopped working

damn how many checks lol

ok

also if u do make links give them to me

Did you do something to the code? Making a new vercel got the same error: https://nvd123ishim.vercel.app/

Did you do something to the code? Making a new vercel got the same error: https://nvd123ishim.vercel.app/

For some reason Vercel isn't supported anymore lol. I couldn't get my Vercel's to work either its odd

My Koyeb link works just fine lol. There are also other services u could probably use

you need a credit card for koyeb
netlify has the same error and i got suspended from render

wait a sec.
Try Glitch or Pages.Dev

Also I couldn't figure out FreeDNS but if you can than that.
Also are you in school? I am
And do you make all the PR0XY links? Just asking.
I think I got banned from Render too for legit no reason I didn't even use it

Also I couldn't figure out FreeDNS but if you can than that.
Also are you in school? I am
And do you make all the PR0XY links? Just asking.
I think I got banned from Render too for legit no reason I didn't even use it

free DNS requires the IP address
I'm on my half term break but i start school next week
i don't have proxies anymore since almost all the websites' owners hate people that have paid proxy links public because the links get banned easily and money is wasted. the owners try dmcaing and taking down people that leak the paid proxy links

How's glitch and pages.dev doing?
Also make link names unique but I'm scared if they have these things because my school will flag me and I got flagged like 2 weeks ago:
Cursewords
rizz
suck
ass
Make it family-friendly, I tend to make some links sports or TV related like ronaldo-farm (because he's farming in Saudi League) or homer-simpson (self-explainitory)
I also like links that are just random like maybe cookie-truck-crushers
U can disregard all of this I don't really care but I can't use it if it has anything slightly bad lol

Wait what nation are you in to where you have a break this late into the school year lol

Wait what nation are you in to where you have a break this late into the school year lol

the UK.
next week i have school until July 19th

I have 10 mi until my classes begin again then I'm done for pretty much the day

Author

i don't really care about football but i guess manchester city and arsenal are good

i couldn't host it on glitch, it auto suspended the project

i couldn't host it on glitch, it auto suspended the project

pages.dev?

i couldn't host it on glitch, it auto suspended the project

pages.dev?

paid since cloudflare

Bro are there any other services?

Bro are there any other services?

no :(
does github pages work

Re

I think there's Heroku but u could try GitHub Pages

I think there's Heroku but u could try GitHub Pages
koyeb might be  working for you if it hasn't updated to the latest version of your repo


[python] returning a list in c.s.field possibly causing the subsequent rules throw: MessageNotHandledException

Hi again,
While I was making my code more complex I've come across a weird issue which I can't tackle.
I'm using durable_rules in a way I described in #302
I'm calling a few rulesets on the same JSON/dict with post() in a sequence (looped).
Taking the same example:
with ruleset('is_color'):
    @when_all(m.source_object.Obj_color != None)
    def is_color(c):
        value = str(c.m.source_object.Obj_color)
        c.s.wrt = {'path': 'target_obj.sub_obj.target_field',
                       'value': value}

Will do what I expect
Rule: is_color
        value: Blue
        Done.
Rule: is_shape
        value: Cylindrical
        Done.
Rule: is_weight
        value: 0.1
        Done.
Rule: is_height
        value: 2.0
        Done.

But when changing the "return value" to be a list of objects
c.s.wrt = [{'path': 'target_obj.sub_obj.target_field',
                       'value': value}]

does break the subsequent rules and they won't execute anymore
Rule: is_color
        value: Blue
        Done.
Rule: is_shape
        Undefined rule in ruleset: is_shape  (MessageNotHandledException)
Rule: is_weight
        Undefined rule in ruleset: is_weight (MessageNotHandledException)
Rule: is_height
        Undefined rule in ruleset: is_height (MessageNotHandledException)

These messages are the product of my looped post() calls in a try/except block like
rule_set = ['is_shape', 'is_color', 'is_weight', 'is_height']

for rule_ in rule_set:
    print(f'Rule: {rule_}')
    meta = None
    try:
        answer = post(rule_, obj)
        if answer.get('wrt'):    # update m_json
            meta = answer.get('wrt')
            if isinstance(meta, dict):
                _set_do(m_json, meta['path'], meta['value'])
            else:
                for obj in meta:
                    _set_do(m_json, obj['path'], obj['value'])
        if answer.get('lap'):    # append to a list in the json
            meta = answer.get('lap')
            if isinstance(meta, dict):
                _append_do(m_json, meta['path'], meta['value'])
            else:
                for obj in meta:
                    _append_dot(m_json, obj['path'], obj['value'])
        if answer.get('msg'):   # message/log
            meta = answer.get('msg')
            print(f"{meta['type']}: while processing {meta['name']}; "
                  f"{meta['msg']} ({meta['field']}:{meta['value']})")

        print('\tDone.')
    except MessageNotHandledException:
        print(f'\tUndefined rule in ruleset: {rule_} (MessageNotHandledException)')
    except MessageObservedException:
        print(f'\tMessageObservedException in rule: {rule_}')
    except Exception as e:
        raise

The list of objects is essential to make multiple inject to the target JSON/dict based on one rule.
Do you have any suggestion/idea to solve this?
I'm sorry for the silly examples but I can't share any of the actual data.

Well, I've tried pretty much everything I could come up with to make durable_rules 2.0.19 accept a list() as dictionary value. No avail, it ends up messing up the subsequent rulesets.
Through, I have a workaround. Defining the list of objects as a nested object, like:
c.s.wrt = {
            1: {'path': 'path1', 'value': True},
            2: {'path': fpath2.{up}.flags', 'value': {}},
            3: {'path': f'path3.{down}.flags', 'value': {}},
            4: {'path': f'path4.{up}.state', 'value': {}},
            5: {'path': f'path5.{down}.state', 'value': {}}
        }

can be iterated - with some restrictions - like:
if answer.get('lap'):    # append to a list in the json
    meta = answer.get('lap')
    if isinstance(meta, dict) and 'path' in meta.keys():
        _append_do(... )
    else:
        for idx in meta.keys():
            _append_do(m_json, meta[idx]['path'], meta[idx]['value'])

the keys of the container-dict are completely arbitrary, could be anything, except
the keys of the container-dict must be different from the keys in the nested (repeated) dict
never use list()/[]as value

Hi, thanks for asking the question. Returning a list actually works fine:
For this code:
from durable.lang import *

with ruleset('is_color'):
    @when_all(m.source_object.Obj_color != None)
    def is_color(c):
        value = str(c.m.source_object.Obj_color)
        c.s.wrt = [{'path': 'target_obj.sub_obj.target_field',
                       'value': value}]

print(post('is_color', {'source_object': {'Obj_color': 1 }}))

The output is:
{'sid': '0', 'id': 'sid-0', '$s': 1, 'wrt': [{'path': 'target_obj.sub_obj.target_field', 'value': '1'}]}
Which is what I expected. Looking closely at the code you pasted:
# removed code for clarity
    try:
        answer = post(rule_, obj)

# removed code for clarity

             if isinstance(meta, dict):
                _set_do(m_json, meta['path'], meta['value'])
            else:
                for obj in meta:
                    _set_do(m_json, obj['path'], obj['value'])

It seems the value of obj changes each iteration when the value of wrt is not a dictionary.

You made me think. I wrote a long explanation of my code when I noticed what's the issue...
I think you point at the silly mistake calling two distinct things to obj in the same block.
It's embarrassing wasting your time with such a mistake.
Thanks a lot!