text:
Parselets should allow for *args and **nargs catchall

This issue takes the *args and **kwargs attempt from Python. Yeah, this would be nice to have :-D
func : @a, b=2, *args, **nargs {
    print(a)
    print(b)
    print(args)
    print(nargs)
}

>>> func(1)
1
2
()
()
>>> func(1,2,3)
1
2
(3,)
()
>>> func(a=3, b=5, c=10)
3
5
()
(c => 10)

#39 could only be resolved when this notation also becomes possible:
print : *args, newline=true { ... }

In this case, any args should be taken, no nargs are allowed but newline might be specified as narg after all.
More examples:
f : @a, b = 23, *args, x, y = 42, **kwargs {
    print(a, b, args, x, y, kwargs)
}

f()   # error: a required parameter
f(1)  # error: x required parameter
f(1, x=10)  # 1 23 () 10, 42, ()
f(1, 2, 3, x=4, y=5, z=6)  # 1 2 (3,) 4 5 (z => 6,)

repo: tokay-lang/tokay


text:
Update lib.rs

just a typo

Thank you

Thank you

source: gharchive/pull-request

authors: hagsteel quininer

repo: tokio-rs/io-uring

license_type: permissive

license_source: github-api


text:
How to load large file?

Use Message::decode need to load the whole file in memory.

The Buf abstraction allows you to customize how the buffer is passed in, you can then use a memory map for example to read from. Prost has nothing to do with where that read buffer comes from.

source: gharchive/issue

authors: LucioFranco leptonyu

repo: tokio-rs/prost


text:
[i18n / 翻訳待ち]  components/DataView.i18n.json の更新

📝 関連する issue / Related Issues

#1312

⛏ 変更内容 / Details of Changes

新･翻訳シートの反映
以下のキーを追加

"埋め込み用コード": "埋め込み用コード",
　　"埋め込み用コードをコピーしました": "埋め込み用コードをコピーしました"
残りの作業
新・翻訳シートの「Additional for Issue #1312 」で翻訳募集中
📸 スクリーンショット / Screenshots

翻訳完了後に貼ります。

@yuhkih 一部翻訳が終わってないかと思いますが、残りの翻訳作業はTransifexでやることになりました！
翻訳が終わってない部分は空文字列にしていただけると助かります

こちら、急きょ必要となりましたので、マージしたうえで

翻訳が終わってない部分は空文字列にしていただけると助かります

に関してはこちらで作業しておきます

@MaySoMusician  さん、ありがとうございます。
気づくの遅れて申し訳ございません・・・

@yuhkih いえいえお構いなく！ お手数おかけいたしました。
こちらも今度から出来る限り目安となる期限を明らかにしていく予定です

authors: MaySoMusician yuhkih

license: MIT


text:
Prevent falling back to a random card except in very rare circumstances

As pointed out in
https://github.com/tom-james-watson/wikitrivia/pull/121, it was previously possible for duplicate years or even duplicate cards to be drawn because we'd fall back to the random card choice too often. This was because the tooClose function could return true too easily for certain circumstances.
This makes it so tooClose is slightly less strict, but also only applies that function as a second pass, meaning we should fall back to a set of relevant cards instead of the whole deck.
Closes https://github.com/tom-james-watson/wikitrivia/issues/103, https://github.com/tom-james-watson/wikitrivia/pull/121

I came up with another solution which was to move the epoch from which you measure the third period for the first few rounds and then play as usual

This introduces a bit of an issue for early game failures, because you can draw a combination like 1990, 1900, 1820, for instance, and then the fourth card could be like 1901 and really mess your game up.
#123 would fix, but could also use this method and just change the last period to be 1700-2020, which would mean that no combination of early cards fails the tooClose check

What is 2020 - 2*dist * #cards supposed to represent? I don't quite follow what the table is meant to be showing.

Okay, much like my original code, I realised after writing it wasn't so well written after I walked far away from the computer lol
That column (which I've now changed) is simulating the worst case card draws.
If we start with 2020 as the end of the last period and the 55 - 5x function for distance, and our first card draw is 1970, we rule out 100 possible years because no card can be within 50 years of 1970, so 1920 through 2020 is ruled out.
And if we look at the state after 2 cards, we can rule out 180 years by supposing that the first two drawn were 1975 and 1885, and now everything from 1840 to 2020 is ruled out.
After 3 cards, rule out 240 years with 1980, 1900, 1820, each ruling out 80 years each.
And so on.

I also have a concern with changing the distance function in the current MR because 55 years feels way closer together in the 12th century than it does in the 20th century

I think probably we should just change the distance function to depend on the period we're looking at, actually.

repo: tom-james-watson/wikitrivia


text:
Connection Message not reading back

Hello - loving the framework so far. I'm having an issue with connection messages reading back properly. I get an error when getting parameters: "Message contains insufficient unread bytes (14) to read type 'string', result will be truncated!"
Here's an excerpt of what I'm doing on the client side:
private void StartClient()
{
client = new Client();
client.Connected += DidConnect;
client.ConnectionFailed += FailedToConnect;
client.Disconnected += ServerDidDisconnect;
var message = Message.Create(MessageSendMode.reliable, 5);
message.AddString("Test String");
Debug.Log($"Message {message.WrittenLength}");
client.Connect($"{ipAddress}:{messagePort}", 0, message );
clientRunning = true;

}
On the Server:
private void RemoteDidConnect(object sender, ServerClientConnectedEventArgs e)
{
Debug.Log("Remote Did Connect");
Debug.Log($"Unread: {e.ConnectMessage.UnreadLength}\n" +
$"{e.ConnectMessage.WrittenLength}");
var message = e.ConnectMessage;
Debug.Log($"Test string = {message.GetString()}");
}
Any ideas as to what I am doing incorrectly?
Thanks!

This line right here is the problem:
var message = Message.Create(MessageSendMode.reliable, 5);

because it creates a message with a header and ID, both of which are then included in the actual connect message and considered part of the payload. The receiving end will then interpret those extra bytes as the bytes containing the length of the string, but that's obviously not what they are, so it ends up being completely incorrect. Then it tries to retrieve the string itself, but because it's expecting there to be more bytes than there actually are, you get that error.
The client.Connect method expects a message with nothing in it other than the data you want to send, and you can get an empty message instance like so:
var message = Message.Create();

authors: CDCMacDaddy tom-weiland

repo: tom-weiland/RiptideNetworking


text:
Fluid Amounts

Using KubeJS because I couldn't get datapack code in #38 working.
How do I specify the amount of fluid to require, and what unit is being used? A default recipe calls for "500 unit" of lava; is that 500mb? Per what?

It's in milibuckets.


text:
URL Params do not work as expected for flag type params

get_param("reverse") does not return Some("") as expected for query string ?reverse
The expected behavior for URLParams is to treat params with no = in them as if the same as an empty value
localhost:80/api/users?reverse should be equivalent to localhost:80/api/users?reverse=
supporting documentation:
https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams#empty_value_vs._no_value

PR ready for review https://github.com/tomaka/rouille/pull/259

repo: tomaka/rouille

license_source: bigquery


text:
No primary_one_time_submit found

While running the examples, I get this error for each of them:
"error: no associated item named primary_one_time_submit found for type vulkano::command_buffer::AutoCommandBufferBuilder<_> in the current scope"
Can't seem to find anything on Google or in the docs.

This caused by the fact that this method has recently been added and is only available on the code on github.
But I published version 0.5.3. Just run cargo update and it should be available.

Works. What's the reason for the new method?

There are multiple kinds of command buffers, plus some flags that you can pass on creation. new was not precise enough.

authors: mattbullen tomaka

repo: tomaka/vulkano


text:
Do not fail in case of multipart/mixed requests.

The underlying jetty code does only support multipart/form-data. Any other multipart content like multipart/mixed can not be used with the MultipartValuePattern! (fixes #920)

Thanks!

authors: tekener tomakehurst

repo: tomakehurst/wiremock


text:
Enabling 'follow_set_cookies' with no set-cookie header

Having follow_set_cookies enabled while requesting a page that doesn't send a set-cookie header will cause needle to crash.
/root/node-osmosis/node_modules/needle/lib/cookies.js:72
  res = Object.keys(obj).map(function(key) {
               ^
TypeError: Object.keys called on non-object
    at Function.keys (native)
    at Object.exports.write (/root/node-osmosis/node_modules/needle/lib/cookies.js:72:16)
    at ClientRequest.<anonymous> (/root/node-osmosis/node_modules/needle/lib/needle.js:401:46)
    at ClientRequest.g (events.js:180:16)
    at ClientRequest.emit (events.js:95:17)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (http.js:1692:21)
    at HTTPParser.parserOnHeadersComplete [as onHeadersComplete] (http.js:121:23)
    at Socket.socketOnData [as ondata] (http.js:1587:20)
    at TCP.onread (net.js:527:27)

Seems like either cookies.read needs to always return an object or cookies.write needs to check that obj isn't undefined.

Good find. Will check tomorrow as part of #111 (which I meant to merge today, haha).

repo: tomas/needle

license: mit


text:
Error while generating SSL keys/cert

Hi,
I've been using your explanations to generate the certificates, with the docker container and the generate-ssl-certificate command. At the very end of the procedure I get:
Certificate is to be certified until Oct 21 13:34:19 2016 GMT (365 days)
Sign the certificate? [y/n]:y
failed to update database
TXT_DB error number 2

Most of my files has been generated, but the cert.pem file is empty:
drwxr-xr-x 6 root root 4096 oct.  22 15:33 demoCA/
-rw-r--r-- 1 root root    0 oct.  22 15:34 mail.mydomain.fr-cert.pem
-rw-r--r-- 1 root root 1708 oct.  22 15:34 mail.mydomain.fr-combined.pem
-rw-r--r-- 1 root root 1708 oct.  22 15:34 mail.mydomain.fr-key.pem
-rw-r--r-- 1 root root 1066 oct.  22 15:34 mail.mydomain.fr-req.pem

Do you have any idea where this comes from? What openssl command is perfomed by generate-ssl-certificate ? Thanks!
Jk.

I found in the sources the openssl command:
FQDN=mail.mydomain.fr
openssl ca -out /ssl/$FQDN-cert.pem -infiles /ssl/$FQDN-req.pem

But it's still showing up the same error in or out of the container...

Hi @jokesterfr, I reproduced your issue. I'll have a look.
Tell me if you find a lead.

Ok, found answer and tested.
failed to update database
TXT_DB error number 2
This is probably because you have generated your own signing certificate with the same Common Name (CN) information that the CA certificate that you've generated before.

I'm gonna update the README.

Hope this helps.

Thanks a lot for the quick response!
I've just done it by-hand using this tutorial it also works.
Thanks a lot for this docker project, you saved me 2 days of email server configuration...

You're welcome.

authors: jokesterfr tomav

repo: tomav/docker-mailserver


text:
Insert Timestamp

Insert Timestamp with shortcut   - useful functionality in previous  linux tomboy
can you add to new version ?

Yes, should be easy. Ctrl-T ?
What would you want stamped, that is what would you like the stamp to look like ?
Davo

Ctrl-D (Cmd-D for mac)  better for compatibility with old tomboy
you can try in previous linux tomboy version - looked good

I don't have Tomboy installed anymore, without Tomboy, I don't need the massive Mono libraries ....
If you can give me a sample, or something like -
[21 Aug, 2019 - 10:11]
I'd rather avoid getting into an argument with other sabout the right way to printing dates, the ISO standard,  20190821 is correct but ugly. My American cousins like 082119, incorrect and ugly :-)
What do you like ?
Davo

I'll represent the Americans, since they'll just give bad ideas otherwise.  How about this:
yyyy-MM-dd HH:MM:SS
e.g.
2019-12-29 21:59:03
It's easy for somebody to reformat, and in the future the formatting could pull locale settings, or let the user set the format themselves, and for now we'd have something that is great.

That, sir, is the ansi standard !  My preferred way but everyone I speak to hates it. Its good in the  most significant terms are always to the left and because the year is obviously at the start, we know its not one of the other ambiguous possibilities. And easily generated in code.

Yes, I agree with everything you wrote, though most people I talk do don't hate it, they just have to look at it a second time to figure it out.  Without it, though, we're stuck with the backwards europeans (day before month before year, so literally backwards) and the messed-up Americans (month-day-year), and that's before we get into a squabble about two-digit vs. four-digit years, or twelve-hour vs. twenty-four-hour clocks, or spelled out month names (argh no!), or "time" before "date", or the level of precision in the timestamp.  ANSI gives a good default, and then as people chime in, or volunteer to help (or maybe from the start if you are up to it) a setting can be added for them to select common options, or specify their own.
In summary, as a default ANSI makes the most sense (to me) to complete the feature request, but by all means let people make it different (wrong) however they like if time permits, or if they want to code that feature themselves.  ;-)

The ANSI standard is the only one that makes sense. Are you going to waste code, possible providing a sort on the underlying ANSI format while "translating" the visual into the other formats based on interface language or something else?

authors: aguador dajoker davidbannon shtalinberg

repo: tomboy-notes/tomboy-ng


text:
Font functions change the text selection

When using the highlight or any font related function (except fixed width) on marked text, the new settings is applied, but it expands the mark by 1 character on each click, which should not happen.

Yeah, I had not noticed that but must have seen it a hundred times !
Trivial fix, done.

authors: davidbannon traumschule


text:
TabPage navigation

Here's the related routing for the current issue.
// A tab page , as my main page
'/ei/:eiId': (route) {
 return TabPage(..., paths: [..., 'list'])
}
// Nested page from tab page
'/ei/:eiId/list': (route) {
 return MaterialPage(...)
}
// A full page
'/ei/:eiId/sub/sub/:anotherId': (route) {
 return MaterialPage(...)
}

Route '/ei/:eiId/sub/sub/:anotherId' pushes '/ei/:eiId/list'.
When Landing directly on '/ei/:eiId/sub/sub/:anotherId', route '/ei/:eiId' is not build "completely" before this page, I can see it with inherited theme not applied.
When route '/ei/:eiId/list' is pushed, the URL is fine but the TabPage is broken, the listing tab doesn't show and tab navigation does not work.
If I refresh the page, the navigation gets back to normal and I get the listing page.
I just tried to wrap TabPage with StackPage in 0.10, but this does not change the behaviour.
For now, I must manually push '/ei/:eiId', wait few milliseconds, and replace with the listing page.

Hello, can you clarify what you mean by the route not being "completely" built? Really not understanding that, sorry.
I've tried to reproduce a problem using the same route map but haven't been able to.

Here's an unperfect reproducer for the issue:
tab_routing.zip
You must ensure to land directly on http://localhost:/#/ei/1/eq/1 to reproduce it (refresh page if necessary).
From there, go to list from the button.
=> You should get the HLR tab selected, the correct URL in bar address but the tab content is 'news'.
Out of interest, this is an unperfect reproducer since the tab page can be recovered by tapping on hlr bottom menu button.
In my project, I replace the navigation each time I tap on bottom menu item to reset query parameters, I cannot navigate anymore in this situation without refreshing the page. (which is not doable on other platforms).

Thanks, I've reproduced it, will get to this as soon as I can

Thanks for the feedback!

Apologises for not getting to this yet, have been very busy.
This issue is my top priority to fix, but in doing so I found another bug in Routemaster and another two bugs in Flutter itself 🤦

Ahah! No worries, I've some workarounds.
Take your time to do it right. Routing is crucial in apps, for the feature it provides and also because it's like a "ghost" in the source code. We must trust the package at all costs.
I choose you mainly because of serious testing! Your comment resonates like an additional insurance to me!

Thank you, that means a lot 😁
I filed the first Flutter bug on this - this could also affect you given your app's structure: https://github.com/flutter/flutter/issues/86222

Hi @llfbandit, in fact... I think it is that Flutter bug that you're seeing here.
Do you see this in Chrome's Console when running your app?
Error: Unexpected null value.
    at Object.throw_ [as throw] (errors.dart:236)
    at Object.nullCheck (operations.dart:518)
    at page_view._PagePosition.new.get viewportDimension [as viewportDimension] (scroll_position.dart:172)
    at page_view._PagePosition.new.getPixelsFromPage (page_view.dart:382)
    at page_view.PageController.new.animateToPage (page_view.dart:197)
    at tabs$._TabBarViewState.new._warpToCurrentIndex (tabs.dart:1417)

Hmm, I don't remember this trace. I'm now on vacation and won't be able to confirm this until end of July

Cool, have a lovely vacation! 🌴
Almost certain this is an upstream Flutter bug, sadly.
I'll have a think if I can come up with any workaround in Routemaster, but I doubt it. For now the easiest fix is probably copying TabBarView and doing a local fix.

Here's a dirty hack you can try that might fix the issue.
Check TickerMode.of(context) and if it's false, don't return TabBarView:
Widget build(BuildContext context) {
  if (!TickerMode.of(context)) {
    return SizedBox();
  }

  return TabBarView(
    controller: TabPage.of(context).controller,
    children: [
      Scaffold(body: Text('One')),
      Scaffold(body: Text('Two')),
    ],
  );
}

This stops the TabBarView being rendered until the page is actually shown.

Closing this for now as I'm 99% sure it's caused by https://github.com/flutter/flutter/issues/86222
Please comment and I'll be happy to reopen if it isn't.

authors: bdremynoel llfbandit tomgilder

repo: tomgilder/routemaster


text:
Support Kitty themes

Description
Kitty is capable of defining multiple colors themes and switching between them.
Add multiple color schemes to the Kitty config
Component or tool

Kitty

Not using Kitty anymore, this issue became obsolete.

repo: tomijaroli/dotfiles


text:
Per toml #1016, year-zero values are invalid

This adds invalid tests for the three cases in which date-time and date values use zero for a year.

With the change of direction on TOML PR #1016, these invalid tests are no longer required, as some parser projects may be able to work with year-zero values without technical or philosophical problems.
In about 12 hours, I will close this PR, unless I am persuaded to keep the restrictions by commentors on either project.

repo: toml-lang/toml-test


text:
File dialog boxes does not display texts clearly

Bug

Describe the bug

Ok so when trying to open a file or folder, inside the file dialog box, the folder and filenames are not visible. I thought it was a tkinter issue but when i tested it seperately, the filedialog works fine.
System Information

OS: Ubuntu 22.04
Python Version: 3.10.12

Issue is caused by the sv-ttk package used, the bug is yet to be fixed
https://github.com/rdbende/Sun-Valley-ttk-theme/issues/104


text:
(Request) Could we have the option for 2 lines text too?

I kinda like how the event text is written in 2 line like before - makes it more readable for longer event title.
Can we have the option to toggle for either 1 or 2 lines?

I think that it would not maintain the widget style.

authors: hilmihisham tommasoberlose

repo: tommasoberlose/another-widget


text:
Fixing the KTX modules URL in Third-party tab

Currently the URL for KTX modules are prefixed with ktx-:
Ex: https://github.com/libktx/ktx/tree/master/ktx-app
This update removes the ktx- prefix which fixes KTX modules URL:
Ex: https://github.com/libktx/ktx/tree/master/app

Looks good, thanks for finding this! Merging.

authors: mariorez tommyettinger

repo: tommyettinger/gdx-liftoff


text:
wrong slashed node number

In epoch detail page (e.g 5625):

149 MN
2 slashed node

Expectation: 1 slashed node

We will calculate slash node at last block of epoch and update slashed status in 5 next epoch
https://github.com/tomochain/tomoscan/commit/01558989daf85925db94887ee32a8db8eeb9ebfd

repo: tomochain/tomoscan


text:
Defer to merge_chunks in special cases of rechunk

#221 introduced merge_chunks, a special-case of rechunk that can be implemented using blockwise. I noticed that whilst reduction calls merge_chunks directly, inside ops.rechunk the primitive rechunk is always called. Shouldn't it be possible for ops.rechunk to check if the user is asking them to perform that special case, and internally dispatch to merge_chunks?
This also makes me wonder whether there are any other special cases of rechunk that could be written using blockwise.

This should be possible, but I'm not sure how much this occurs in practice. The only calls to rechunk in Cubed are in reshape and from_array (for some cases).

It will also happen if an xarray user calls .rechunk, because it dispatches to cubed's rechunk method.
I agree it's not a very common case (though I expect it to come up in the full pangeo vorticity example where we pad then rechunk to merge the padded values back in).

there are any other special cases of rechunk that could be written using blockwise.
It will also happen if an xarray user calls .chunk on an already-chunked array

This is very confusing to me.
Isn't a rechunk without a on-disk intermediate not "blockwise" by definition (you are communicating across chunks)? I thought the optimization was effectively optimizing chunking when reading from an intermediate store by looking at the chunks needed for the succeeding operation. But perhaps I'm misunderstanding something.

merge_chunks is implemented using map_direct, which

works by creating an empty array that has the same shape and chunk structure as the output, and calling map_blocks on this empty array, passing in the input arrays as side inputs to the function, which may access them in whatever way is needed.

That might resolve it for you @dcherian ?
Alternatively, the way I have been thinking about this merge_chunks operation is as just one-half of what rechunker does. In Tom A's original suggestion that led for rechunker, he breaks general rechunking into a split pass and a merge pass. If you can accomplish the specific rechunk only doing the merge pass you don't need the intermediate store.

authors: TomNicholas dcherian tomwhite

repo: tomwhite/cubed


text:
horizontal to vertical

CSV Transpose horizontal to vertical

@tonirilix maybe it's more like an option to make it grow vertically instead of horizontally
For example:
{
    "user":{
        "name":"Lucas",
        "age":10
    },
    "address":{
        "street":"eqwewqewqewqewq",
        "number":"10",
        "zip":"99163"
    }
}

so instead of having all columns side by side, I wish we could have
user.name | user.age
Lucas | 10

address.street | address.number | address.zip
eqwewqewqewqewq | 10 | 99163

in my case I have a huge JSON file, so having to scroll a lot to the right is not a good experience XD it would be better if we could just scroll down

repo: tonirilix/nested-json-flattener


text:
Error REQUEST_NOT_SUCCESSFUL when Download Failed from getintopc.com

URL Downloading-> http://51.83.136.12/Getintopc.com/BluffTitler_Ultimate_15.0.0.1_Multilingual.rar?md5=_jQwKLaEW30Wk-ArOgA6sg&expires=1600940204
throwable -> String -> com.tonyodev.fetch2.exception.FetchException: request_not_successful
throwable -> StackTrace ->
com.tonyodev.fetch2.downloader.ParallelFileDownloaderImpl.run(ParallelFileDownloaderImpl.kt:160)
com.tonyodev.fetch2.downloader.DownloadManagerImpl$start$$inlined$synchronized$lambda$1.run(DownloadManagerImpl.kt:103)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
java.lang.Thread.run(Thread.java:919)
httpResponse -> 404 Not Found, Nginx
on the other hand, downloading from the same URL using chrome browser works?

@abhishekhugetech Have you tried the download on a different device or emulator?. Does the download work in a browser on the device. I noticed the the url uses the ip address instead if host name eg: google.com. What if you tried the host name instead does it work??

I got the solution for this issue. You'll have to add header Referrer and value will be getintopc

authors: abhishekhugetech nikzdevz tonyofrancis

repo: tonyofrancis/Fetch


text:
"Redo" shortcut label under Edit is wrong

Describe the bug
under Edit, it says the shortcut for Redo is CTRL+Y, it should be CTRL+SHIFT+Z
To Reproduce
Steps to reproduce the behavior:

Go to 'Edit'
Look at 'Redo'
See wrong label

Expected behavior
Redo shortcut label should say "CTRL+SHIFT+Z"
Screenshots

fixed in #408 , thank you for the report 😺

Thanks!

authors: BlobbishTheArtist pixtur ylmrx


text:
Enable Sourcegraph

I want to use Sourcegraph code search and code review with godep. A project maintainer needs to enable it to set up a webhook so the code is up-to-date there.
Could you please enable godep on @Sourcegraph by going to https://sourcegraph.com/github.com/tools/godep and clicking on Settings? (It should only take 15 seconds.)
Thank you!

Done. Thanks for the report!

authors: hoffoo kr

repo: tools/godep


text:
Avoid vcs check error in current package and sub packages.

fixes #116

So this fixes godep: unable to detect version control system for code.google.com/ path errors?
That is great! :+1:


text:
Pass golint

This branch makes the code pass golint:

Comment all exported structs, constants and functions.
Remove an unnecessary blank identifier from an iteration.

All tests passing.

Thanks!

authors: buddhamagnet freeformz


text:
github.com/thebotguys/signalr: does not exist anymore

Try it: https://github.com/thebotguys/signalr.
This means this library will fail to compile.

@steenzout This seems to have sorted itself out.

authors: dataBaseError steenzout

repo: toorop/go-bittrex


text:
un-removed required loading watcher

I goofed when testing some cleanup for the fix for the “no data” message bug and removed a watcher that I thought was unnecessary but was actually needed. This re-adds the watcher.

What is going wrong? Why is it necessary?

repo: topcoat-data/topcoat-public


text:
2623 | Base styles and typography

Link to Ticket
Description of Changes Made

Adds typography setup based on the values added in the style guide.
Adds link styles for link, link with arrow and button.
Adds drop cap for first letter for heading 1, 1-b and 2. Does not include the blended colours that appear in this letter.
Adds a styleguide dir for the pattern lib where i've added an example typography page.

Notes:

I noticed that the body text on desktop was 20px and on mobile was 16px however there was no example for this scale in the style guide (or there was a typo on mobile where it said the text remained at 20px).

TODO:

[x] Implement a hover/focus state for buttons when viewing in high contrast mode - currently the background-color does is not enough

How to Test
Typography can be seen in the pattern library on the example page: styleguide/typography/typography.html
MR Checklist

[x] Add a description of your pull request and instructions for the reviewer to verify your work.
[x] If your pull request is for a specific ticket, link to it in the description.
[x] Stay on point and keep it small so the merge request can be easily reviewed.
[x] Tests and linting passes.

Unit tests

[ ] Added
[x] Not required

Documentation

[ ] Updated build docs
[ ] Updated editor guidelines (https://docs.google.com/document/d/1PAWccdQ4tfaZsrEWmpDhvP3GH5RRmBOARFVp4b-kje8/edit?usp=sharing)
[x] Not required

Browser testing

[x] I have tested in the following browsers and environments (edit the list as required)

Latest version of Chrome on mac
Latest version of Firefox on mac
Latest version of Safari on mac
Safari on last two versions of iOS
Chrome on last two versions of Android

[ ] Not required

Data protection

[ ] Not relevant
[ ] This adds new sources of PII and documents it and modifies Birdbath processors accordingly

Accessibility

[x] Automated WCAG 2.1 tests pass
[ ] Manual WCAG 2.1 tests completed
[ ] I have tested in a screen reader
[x] I have tested in high-contrast mode
[ ] Any animations removed for prefers-reduced-motion
[ ] Not required

Sustainability

[ ] Images are optimised and lazy-loading used where appropriate
[x] SVGs have been optimised
[ ] Perfomance and transfer of data considered
[ ] If JavaScript is needed alternatives have been considered
[x] New font variants have not been added
[x] Not required

Thanks for the review @helenb!


text:
[dependencies] Allow use with Wagtail 5.x

I just did a quick test on the project I'm currently working on, and it seems that nothing prevents wagtail-footnotes from doing its job on a Wagtail 5.0 instance, so this should be rather safe to merge? :slightly_smiling_face:
Whether it's in the Wagtail Admin or the frontend, everything seems to be working correctly.
(I would attach screenshots if I could, but it seems to be disabled on this GitHub repo?)

Note that we already have https://github.com/torchbox/wagtail-footnotes/pull/49 doing the same thing; but that other PR is much bigger (41 files changed), as it has a much wider scope - so merging it will likely take some time as it involves some chat to happen before an agreement is made with everything it covers.
On the other hand, this PR is on the contrary very minimalist, only relaxing the constraint as for the version of Wagtail that can be used, so the goal would just be to be able to use the wagtail-footnotes package with Wagtail 5.x setups in the short term :slightly_smiling_face:

@olivierphi we'll get #49 tidied up and merged today. Will cut a release.
Thank you for this, nonetheless

authors: olivierphi zerolab

repo: torchbox/wagtail-footnotes


text:
Exporter status

Hi,
I wanted to know what is the best method to check exporter availability.
Many Prometheus exporters have a metric called:

exporter_name_up

An example can be found with the Unbound exporter here:

https://github.com/letsencrypt/unbound_exporter/blob/main/unbound_exporter.go#L42

Can I make the relevant PR?
Regards,

Hi @avachette , thank you for your message.
This is first time I can hear about such availability check. Yes, I saw similar metrics within some other apps. I think it is not bad idea and having one more metrics wouldn't harm this exporter. Feel free to prepare PR.
thanks, Laura

authors: avachette torilabs

repo: torilabs/ipsec-prometheus-exporter


text:
Local run command no longer works

https://github.com/tortellini-tools/action/blob/main/README.dev.md#on-the-current-repository describes how to run check locally however this gives error:
ode dist/index.js
::error::no such file or directory:

Probably because the default value from action.yml is not used. The core.getInput(name) only reads INPUT_NAME env variable.
To be able to run locally we could

Add INPUT_<config>=<default config url> env vars to README.dev.md
Replace core.getInput(name) with core.getInput(name) || '<default config url>'
Use another method to get defaults from action.yml when running locally
Run workflow locally using act

What is the best solution?

Option 1 could look like
INPUT_RULES=https://github.com/NLeSC/tortellini-on-rsd/raw/main/config/rules.kts \
INPUT_CLASSIFICATIONS=https://github.com/NLeSC/tortellini-on-rsd/raw/main/config/license-classifications.yml \
node dist/index.js

Fixed in #129

repo: tortellini-tools/action


text:
[Feature]: add doc for shouldCatch prop

Package Scope
@suspensive/react
Description
add doc for shouldCatch prop
Possible Solution
No response
etc.
No response

@jgjgill Could you make this doc please? I think you understood this shouldCatch prop

Oh, there was a related issue.
If I can help, I'd be happy to take it from there.
Thanks. 🙇♂

authors: jgjgill manudeli

repo: toss/suspensive


text:
🛑 MSP-Trust is down

In c134995, MSP-Trust (https://www.hanatrust.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MSP-Trust is back up in 1732024 after 8 minutes.

repo: touguy/uptime


text:
🛑 MSP-Trust is down

In 4a1864a, MSP-Trust (https://www.hanatrust.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MSP-Trust is back up in a8209a6 after 25 minutes.


text:
customize meta data on Missing Members page

(Since we often link to it and promote it on social)
"Town Hall Project Missing Members Report: See which members of Congress haven't held a town hall in 2017."

Merging with #161

authors: meganrm nathanmwilliams

repo: townhallproject/townHallProject


text:
Problem with /run/user folder in VS Code dev containers with user_runtime_path

In VS Code dev containers, there is no /run/user folder in the default Python container.
This means using user_runtime_path and trying to put anything there (or using the ensure_exists argument) will result in a crash, with PermissionError: [Errno 13] Permission denied: '/run/user'.
I'm not certain what the best route forwards is here, and this is not my area of expertise! Some tentative thoughts:

A good solution might be to fall back to a different user runtime directory location if /run/user doesn't exist.
An alternative would be to push this back to users of this package, warning them in the docs that the directory might not exist and they should check it beforehand (although this seems unideal).
Or maybe the default Python dev container should be updated so it does have a runtime dir.

Based on https://specifications.freedesktop.org/basedir-spec/latest/index.html:

If $XDG_RUNTIME_DIR is not set applications should fall back to a replacement directory with similar capabilities and print a warning message. Applications should use this directory for communication and synchronization purposes and should not place larger files in it, since it might reside in runtime memory and cannot necessarily be swapped out to disk.

I think we should provide a different location if it doesn't exist.

https://serverfault.com/questions/388840/good-default-for-xdg-runtime-dir has some decent suggested fallbacks - in particular, creating a folder named after the service/application and logged in user in the system tmp directory.
Since user_runtime_dir takes appname and appauthor parameters, a decent tmp dir fallback folder name would be f"{appauthor}-{appname}-{username}".
When ensure_exists is used, the fallback folder should be explicitly created with 700 permissions when it's outside the user's home directory (and hence won't get user-only permissions by default).

authors: domdomegg ncoghlan ofek

repo: tox-dev/platformdirs


text:
Implement range_color

Add support for range_color
For example, if a color range of [100, 200] is used with the ["blue", "green", "red"] color scale, then any instance with a color value of 100 or less will be blue, and 200 or more will be red. Anything in between will be interpolated as usual.
Ref: https://plotly.com/python/colorscales/#explicitly-setting-a-color-range

@CaioSilvaUT boas! Sure, I'd be happy to guide you :)
Let me know if you need help getting started.
And please take a quick look at our contributing guide to ensure you get a working development environment from the start 🚀

@tpvasconcelos Sorry to bother you, but I have some questions about completing this issue. If possible, I would like to get in touch via email or something like that, even a Google Meet call if necessary.
I've already made a draft of the range_color function using plotly example, but I'm having trouble figuring out where to place it in this repository. I’ve never worked with such a large repository before.

That's understandable. From the issue's description it is not clear exactly how this feature should be implemented. Here are my thoughts on it at first glance.

Maybe we should narrow this down to only apply to colormode='fillgradient' for now, since it doesn't make sense in the context on index-based colormodes and it's not very obvious that this would be useful in the mean-based colormodes either.

If we do this, it should be clearly documented in the ridgeplot() docstring!

range_color should be added as a new parameter to the ridgeplot() function, and then passed through to create_ridgeplot() and finally to ColoringContext()
For the area trace (AreaTrace), the values will likely have to be passed to the Fillgradient's start and stop parameters. I'm not sure about this tho... Can you investigate?
For the bar trace (BarTrace), the p should be set to 0 for x values smaller than the lower range and 1 for x values larger than the upper range

Let me know if something is not clear or if you get stuck somewhere!

authors: CaioSilvaUT tpvasconcelos

repo: tpvasconcelos/ridgeplot


text:
[ Issue, Forge ] Crash on startup

[ Issue, Forge ]  Crash on startup
LINE-45: [main/FATAL]: Mixin apply failed firstpersonmod.forge.mixins.json
I believe this is the issue, not too sure though.

MC : 1.16.5
Forge : 36.2.8
OptiFine : HD_U_G8
Mod Name : FirstPersonMod-2.0.2.jar

Crash Report : N/A
Latest.log : https://gist.github.com/zndrmn/2377e1c4d9f795d4ee4173c3bab328e3#file-latest-log-L45

Uhh I'll look into it tomorrow, worst case use the previous build on curse for now and check rather that works.

Yeah I tested both versions, version 2.02 was crashing.
I didn't check to see if the previous version had the same mixin error though

So 2.0.2 and 2.0.1 are crashing?

No just 2.0.2

Thats odd cause 2.0.2 doesn't change any mixin, and just adds a few null checks. Will have to check that tomorrow because its 2am...

Exte code 0 on 2.0.2 while 2.0.1 works fine

Here's the Crash Report:
crash-2021-11-12_01.31.09-client.txt

I marked 2.0.2 an alpha on curse, please use 2.0.1 again!

Not able to create 1.16 updates anymore(and it's now a really outdated version anyway). Going to close this, since it doesn't seem to cause more issues.

authors: Red-EyedFairace ekiplier tr7zw zndrmn


text:
Update trace4cats-core, trace4cats-kernel, ... to 0.14.1

Updates

io.janstenpickle:trace4cats-core
io.janstenpickle:trace4cats-kernel
io.janstenpickle:trace4cats-testkit

from 0.14.0 to 0.14.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (0.14.0).
You might want to review and update them manually.
README.md

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.janstenpickle" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "io.janstenpickle" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, old-version-remains, commit-count:1

Superseded by #189.


text:
Update google-cloud-trace to 2.37.0

About this PR
📦 Updates com.google.cloud:google-cloud-trace from 2.3.7 to 2.37.0
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.cloud", artifactId = "google-cloud-trace" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.cloud", artifactId = "google-cloud-trace" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #352.


text:
Update grpc-api, grpc-okhttp, grpc-stub to 1.68.0

About this PR
📦 Updates

io.grpc:grpc-api
io.grpc:grpc-okhttp
io.grpc:grpc-stub

from 1.49.2 to 1.68.0
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.grpc" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.grpc" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #423.


text:
Render leisure=bleachers

Render leisure=bleachers
OSM Carto doesn't render them; they have a discussion about it, but nobody made a PR yet.

Icon: https://www.flaticon.com/free-icon/bleachers_5029773?term=bleachers&page=1&position=1&origin=search&related_id=5029773

Background will be like lighter park fill.

https://www.openstreetmap.org/#map=19/49.62459/8.36702&layers=P

authors: Hufkratzer quinncnl

repo: tracestrack/tracestrack-maps


text:
HOTT-805: On first accessing quota search, please hide the error message

On first accessing quota search, please hide the error message "Sorry, there is a problem with the search query. Please specify one or more search criteria"
Jira link
https://transformuk.atlassian.net/browse/HOTT-805
What?
I have added/removed/altered:

[ ] Add a guard in the presenter, so that the following line won't try reject! on nil, and the search result will be an array in any case

Why?
I am doing this because when a search is not provided, the app tries to run a reject! on a nil object, and errors.
Have you? (optional)

[ ] Reviewed view changes with stake holders
[ ] Validated mobile responsive behaviour of view changes

repo: trade-tariff/trade-tariff-frontend


text:
[DRAFT] WIP Enable pane support

Type of PR: enhancement
PR checklist:

[ ] Addresses an existing issue: fixes #50
[ ] Includes tests
[ ] Documentation update

Overview of change:
Based on community implementation https://github.com/tradingview/lightweight-charts/pull/824

Also take a look at horizontal crosshair line visibility, it should be painted on the active pane only. The same logic should be applied for crosshair price label as well.

And for some reason vertical line is not painted on the first pane

Also take a look at horizontal crosshair line visibility, it should be painted on the active pane only. The same logic should be applied for crosshair price label as well.

And for some reason vertical line is not painted on the first pane

thanks for spotting this one, fixed crosshair in https://github.com/tradingview/lightweight-charts/pull/1557/commits/5fc37ee4450b9db08174c048ed61b045e0d63677

It's something wrong here 🙂

It's something wrong here 🙂

'QA' testing coming soon. 😅 Been focused on the API design review first.
Agree that we should only have a single TV attribution logo (on the bottom pane).

It's something wrong here 🙂

'QA' testing coming soon. 😅 Been focused on the API design review first.
Agree that we should only have a single TV attribution logo (on the bottom pane). Also the price label is different. Is it the exact same data? or is it randomised a bit?

fixed logo duplication in https://github.com/tradingview/lightweight-charts/pull/1557/commits/c391ec18accda43087f4bf3a345fe69a7b167f8e

After an error of using moveToPane(-1) then you can no longer move the pane.

// ...create a normal chart above...
volumeSeries = chart.addHistogramSeries(
    {
        priceFormat: {
            type: 'volume',
        },
    },
    1 // Pane index
);

volumeSeries.setData(generateLineData())

volumeSeries.moveToPane(2); // okay
volumeSeries.moveToPane(5); // okay
volumeSeries.moveToPane(-1); // error, but expected

volumeSeries.moveToPane(2); // error, but should work

Moving a series to a different price scale seems to also move the series to pane 0

// ...create a normal chart above...
volumeSeries = chart.addHistogramSeries(
    {
        priceFormat: {
            type: 'volume',
        },
    },
    1 // Pane index
);

volumeSeries.setData(generateLineData())

// make left price scale visible
chart.applyOptions({leftPriceScale: {visible: true}})

// move volume series to left price scale
volumeSeries.applyOptions({priceScaleId: 'left'})

// !! now appears in pane 0

volumeSeries.moveToPane(1) // does nothing since it thinks it is in pane 1

volumeSeries.moveToPane(0) // hides empty pane 1
volumeSeries.moveToPane(1) // now the volume is back into the correct position

Using the above bug, it is possible to get an empty pane within the middle of the chart

// ...create a normal chart above...
volumeSeries = chart.addHistogramSeries(
    {
        priceFormat: {
            type: 'volume',
        },
    },
    1 // Pane index
);

volumeSeries.setData(generateLineData())

// make left price scale visible
chart.applyOptions({leftPriceScale: {visible: true}})

// move volume series to left price scale
volumeSeries.applyOptions({priceScaleId: 'left'})

// !! now appears in pane 0

volumeSeries.moveToPane(2) // There is now an empty pane 1. Showing 3 panes

[Minor] When dragging the pane separator, the time scale width can change. Maybe we would want to 'fix' the time scale width while dragging?
Let's only do this if it is easy, and lightweight to implement.
https://github.com/tradingview/lightweight-charts/assets/3482679/39e30ada-f9eb-4c0e-8339-68ef59572bbd

After an error of using moveToPane(-1) then you can no longer move the pane.

// ...create a normal chart above...
volumeSeries = chart.addHistogramSeries(
    {
        priceFormat: {
            type: 'volume',
        },
    },
    1 // Pane index
);

volumeSeries.setData(generateLineData())

volumeSeries.moveToPane(2); // okay
volumeSeries.moveToPane(5); // okay
volumeSeries.moveToPane(-1); // error, but expected

volumeSeries.moveToPane(2); // error, but should work

Moving a series to a different price scale seems to also move the series to pane 0

// ...create a normal chart above...
volumeSeries = chart.addHistogramSeries(
    {
        priceFormat: {
            type: 'volume',
        },
    },
    1 // Pane index
);

volumeSeries.setData(generateLineData())

// make left price scale visible
chart.applyOptions({leftPriceScale: {visible: true}})

// move volume series to left price scale
volumeSeries.applyOptions({priceScaleId: 'left'})

// !! now appears in pane 0

volumeSeries.moveToPane(1) // does nothing since it thinks it is in pane 1

volumeSeries.moveToPane(0) // hides empty pane 1
volumeSeries.moveToPane(1) // now the volume is back into the correct position

Using the above bug, it is possible to get an empty pane within the middle of the chart

// ...create a normal chart above...
volumeSeries = chart.addHistogramSeries(
    {
        priceFormat: {
            type: 'volume',
        },
    },
    1 // Pane index
);

volumeSeries.setData(generateLineData())

// make left price scale visible
chart.applyOptions({leftPriceScale: {visible: true}})

// move volume series to left price scale
volumeSeries.applyOptions({priceScaleId: 'left'})

// !! now appears in pane 0

volumeSeries.moveToPane(2) // There is now an empty pane 1. Showing 3 panes

we are throwing an error and a developer who uses the library should handle the error
and 3 fixed in https://github.com/tradingview/lightweight-charts/pull/1557/commits/745e4bfac02cf29d62fa9bff43f962a4c79b954d

[Minor] When dragging the pane separator, the time scale width can change. Maybe we would want to 'fix' the time scale width while dragging?
Let's only do this if it is easy, and lightweight to implement.
time-scale-width-changing.mov

@SlicedSilver could we move this to future improvements

can't express how much I am waiting for this feature, guys! So grateful for everyones work ❤

I am excited for this feature , love you guys for this work :)

authors: SigmaU SlicedSilver illetid kirchet vishnuc

repo: tradingview/lightweight-charts


text:
IngressClass not working on AWS EKS 1.18 Cluster - no matches for kind "IngressClass" in version "networking.k8s.io/v1"

The way this Helm chart tries to evaluate the API version for IngressClass doesn't work for AWS EKS 1.18 cluster.
  {{- if .Capabilities.APIVersions.Has "networking.k8s.io/v1" }}
apiVersion: networking.k8s.io/v1
  {{- else if .Capabilities.APIVersions.Has "networking.k8s.io/v1beta1" }}
apiVersion: networking.k8s.io/v1beta1

You will get...
error: unable to recognize "ingressclass.yaml": no matches for kind "IngressClass" in version "networking.k8s.io/v1"

...because IngressClass runs with networking.k8s.io/v1beta1.
$ k explain IngressClass
KIND:     IngressClass
VERSION:  networking.k8s.io/v1beta1

Because NetworkPolicy runs with networking.k8s.io/v1 as an API version .Capabilities.APIVersions.Has "networking.k8s.io/v1" will IMHO evaluate to true.
$ for kind in `kubectl api-resources | tail +2 | awk '{ print $1 }'`; do kubectl explain $kind; done | grep -e "KIND:" -e "VERSION:"
...
KIND:     IngressClass
VERSION:  networking.k8s.io/v1beta1
KIND:     Ingress
VERSION:  extensions/v1beta1
KIND:     NetworkPolicy
VERSION:  networking.k8s.io/v1

Just ran into this issue as well when upgrading to latest chart version.
Cluster version 1.18.9.

According to the docs @ https://helm.sh/docs/chart_template_guide/builtin_objects/
Capabilities.APIVersions.Has $version indicates whether a version (e.g., batch/v1) or resource (e.g., apps/v1/Deployment) is available on the cluster.
If I'm reading that correctly, that should mean the template could be changed to:
  {{- if .Capabilities.APIVersions.Has "networking.k8s.io/v1/IngressClass" }} apiVersion: networking.k8s.io/v1   {{- else if .Capabilities.APIVersions.Has "networking.k8s.io/v1beta1/IngressClass" }} apiVersion: networking.k8s.io/v1beta1
Will try it out.

repo: traefik/traefik-helm-chart


text:
[HTTP/1] httputil: ReverseProxy read error during body copy - use of closed network connection

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
Using Traefik v2.10.7 on top of Warp 10 lead to this issue:

2024/01/23 09:53:40 reverseproxy.go:666: httputil: ReverseProxy read error during body copy: read tcp 10.0.2.215:35006->10.0.2.215:8080: use of closed network connection

Seems the fix is in golang 1.21 with the usage of http.ResponseController.EnableFullDuplex()
More context on this:

https://github.com/golang/go/issues/40747#issuecomment-1382404132
https://github.com/golang/go/issues/57786
https://github.com/golang/go/issues/15527

What did you see instead?
2024/01/23 09:53:40 reverseproxy.go:666: httputil: ReverseProxy read error during body copy: read tcp 10.0.2.215:35006->10.0.2.215:8080: use of closed network connection

What version of Traefik are you using?
2.10.7
What is your environment & configuration?
Add more configuration information here.

file provider
debian 11 VM

If applicable, please paste the log output in DEBUG level
No response

Hello,
I've noted the concerns you raised, and I'd like to address two points regarding this matter.
Firstly, there is a consideration to introduce the new EnableFullDuplex but it might be prudent to hold off for now. We are uncertain about its potential impact on the reverse proxy. While we could implement it with an option, there's a chance it could become obsolete if it turns out to be necessary all the time. Therefore, I suggest waiting for feedback on Go issues before proceeding.
Secondly, I attempted to replicate the issue with Warp10, but unfortunately, I couldn't. To further investigate and verify if the proposed solution resolves the problem, could you provide a reproducible case?

Hi @juliens
Sorry for the delay, I forgot to answer.
My deployment is as follow:

traefik binary deployed on host (no container)
Warp 10 deployed on host (no container) and accessed via localhost or via the private ip on the machine

# /etc/traefik/traefik.yml
api:
  dashboard: true
certificatesResolvers:
  le:
    acme:
      email: me@company.com
      storage: /etc/traefik/acme.json
      tlsChallenge: {}
entryPoints:
  api:
    address: 127.0.0.1:9999
  metric:
    address: xxx.xxx.xxx.xxx:80
    http:
      redirections:
        entryPoint:
          scheme: https
          to: matricsecure
  metricsecure:
    address: xxx.xxx.xxx.xxx:443
  web:
    address: yyy.yyy.yyy.yyy:80
    http:
      redirections:
        entryPoint:
          permanent: true
          scheme: https
          to: websecure
  websecure:
    address: yyy.yyy.yyy.yyy:443
global:
  checkNewVersion: true
  sendAnonymousUsage: true
log:
  filePath: /var/log/traefik.log
  format: json
providers:
  file:
    fileName: /etc/traefik/file.yml

# /etc/traefik/file.yml
http:
  middlewares:
    apiAuth:
      basicAuth:
        users:
        -xxx:yyy
    redirectToHttps:
      redirectScheme:
        permanent: true
        scheme: https
  routers:
    warp10:
      entryPoints:
      - metricsecure
      middlewares:
      - redirectToHttps
      rule: Host(`warp10.company.com`)
      service: warp10@file
      tls:
        certResolver: le
    warp10-http:
      entryPoints:
      - metric
      middlewares:
      - redirectToHttps
      rule: Host(`warp10.company.com`)
      service: warp10@file
  services:
    warp10:
      loadBalancer:
        servers:
        - url: http://10.0.2.215:8080/ (or http://127.0.0.1:8080/

On my IoT project, I have http calls to Warp10 every 100ms max but not with a lot of data within (a few data points each)
Hope it helps

Hi,
For your information, I notice the same behaviour with Caddy as an alternative to Traefik.

Ok, adding the header Connection: close to our HTTP/1.1 request calls fixed the issue.
=> closing as the bug was elsewhere.

authors: juliens nsteinmetz

repo: traefik/traefik


text:
[ECS Provider] - SSM managed instances causes discovery to fail

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
Run traefik on an ECS Anywhere ECS instance which the instance ID is not i-[a-z0-9]+ but mi-[a-z0-9]+
I tracked it down as far as
https://github.com/traefik/traefik/blob/25725e9b2fbd8f383b45c5fb2e3943e1591ab9c1/pkg/provider/ecs/ecs.go#L375
and https://github.com/traefik/traefik/blob/25725e9b2fbd8f383b45c5fb2e3943e1591ab9c1/pkg/provider/ecs/ecs.go#L408
After it found the ECS Instances it goes about describing the EC2 instance without checking that it is in fact an EC2 instance.
so after that, when trying to build the instance and describe it doesn't work.
The call for ec2-describe-instances is what returns the error. With CLI, for example
aws ec2 describe-instances --instance-ids mi-08593f2320b5826a3

An error occurred (InvalidInstanceID.Malformed) when calling the DescribeInstances operation: Invalid id: "mi-08593f2320b5826a3"

instead we can get some information from SSM
aws ssm describe-instance-information --instance-information-filter-list key=InstanceIds,valueSet=mi-08593f2320b5826a3

See API Docs
One way to catch whether the instance might be external, in addition not having a different instance ID format, is to check for attributes in the ECS Instance.
      "attributes": [
        {
          "name": "ecs.capability.external"
        }
]

This might not be the best way to detect it, but that can be used in combination of the instance ID format.
I don't know go well enough to open a PR myself for this, sorry about that.
Suggested recommendation: implement to do describe ecs instances and support managed instances
or
ignore that specific error if the instance id does not match the regex i-[a-z0-9]+
What did you see instead?
Results into

time="2022-03-15T17:38:21Z" level=error msg="Provider connection error failed to get ECS configuration: InvalidInstanceID.Malformed: Invalid id: \"mi-08593f2320b5826a3\"\n\tstatus code: 400, request id: 75eabde6-192c-4406-b5a3-50fcfd816c6e, retrying in 621.405684ms" providerName=ecs

What version of Traefik are you using?

docker run --rm traefik version
Version:      2.6.1
Codename:     rocamadour
Go version:   go1.17.7
Built:        2022-02-14T16:50:25Z
OS/Arch:      linux/arm64

What is your environment & configuration?
---
# Docker compose with overrides and config to run in AWS ECS

version: "3.8"
services:
  traefik:
    ports:
       - 8000:80/tcp
    expose:
      - 8080/tcp
    labels:
      container_name: traefik
    environment:
      AWS_DEFAULT_REGION: ${AWS_DEFAULT_REGION:-eu-west-1}
    command:
      #- "--log.level=DEBUG"
      - "--api.insecure=true"
      - "--providers.ecs.autoDiscoverClusters=true"
      - "--providers.ecs.exposedByDefault=true"
      - "--providers.ecs.refreshSeconds=15"
      - "--providers.ecs.clusters=${CLUSTER_NAME}"
      - "--entrypoints.web.address=:80"
      - "--metrics"
      - '--metrics.prometheus=true'
      - "--metrics.prometheus.addServicesLabels=true"
      - "--metrics.prometheus.addrouterslabels=true"
      - "--entryPoints.web.address=:80"
      - "--entryPoints.web.proxyProtocol.trustedIPs=192.168.103.0/24"

It is a modified version of the instructions on https://labs.compose-x.io/apps/traefik_ecs_part1.html which works the same but uses ECS Anywhere instances instead of EC2/Fargate.
If applicable, please paste the log output in DEBUG level
time="2022-03-15T17:38:21Z" level=error msg="Provider connection error failed to get ECS configuration: InvalidInstanceID.Malformed: Invalid id: \"mi-08593f2320b5826a3\"\n\tstatus code: 400, request id: 75eabde6-192c-4406-b5a3-50fcfd816c6e, retrying in 621.405684ms" providerName=ecs

@JohnPreston Did you actually mean to open two issues, or is this one here a duplicate of #8795 as far as you're concerned?

Opened a PR #8845
First try at go

@JohnPreston Did you actually mean to open two issues, or is this one here a duplicate of #8795 as far as you're concerned?

Yes I meant to create a different issue.
A. #8795 is more of a statement than anything else IMHO, i.e. "there is no documentation saying it works for ECS Anywhere".
I am very glad that someone pointed it out though. I'd be glad to come up with documentation on how to run in ECS Anywhere but (see below) it should not make any difference given the control plane (ECS) is the same and technically running on on-prem instances is "the same" as in EC2 mode. The only difference would be the no-support of AWSVPC networking mode on prem which from the aspect of figuring out, which IP address to send the traffic to, would be the difference.
B. This issue goes into the why it is not working.
Otherwise, ECS Anywhere discovery as per my use of traefik in ECS so far (and now from attempting to fix by reading the code) does not need to know about the ECS instance (and where applicable, EC2 instance) to allow the services and tasks discovery. Therefore I'd expect that the discovery for these services "as-if" they were running in AWS Fargate, and be able to send the traffic to the tasks of the service based on that discovery.
If however the discovery to send traffic to that instance (on-prem that is) requires to find out the IP address of said instance to send the traffic to it, then my PR needs a big function added to do the discovery of the SSM instance to retrieve the property

Closed by #8973

authors: JohnPreston kevinpollet mpl


text:
Lowering of do-while.

Includes some code quality improvements in the -vast-hl-to-ll-cf pass and some test refactors.

Add the most trivial test case do {} while (0);

authors: lkorenc xlauko

repo: trailofbits/vast


text:
🛑 ABB Restore is down

In 80c2711, ABB Restore (https://backup.$DOMAIN1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ABB Restore is back up in 917cda4 after 10 minutes.

repo: traktuner/status


text:
Restyle section headers (CSS)

Leaving this for you @hongkonggong hehehe

Have fixed all the easy things already, will pass for now until a larger revamp is required.

authors: hongkonggong shenchingtou


text:
🛑 TechinAsia is down

In a8500c5, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 954 ms

Resolved: TechinAsia is back up in f235aad after 7 minutes.

repo: traqy/upptime


text:
🛑 TechinAsia_Laravel_API is down

In 6fe26ce, TechinAsia_Laravel_API (https://www.techinasia.com/api/2.0/companies) was down:

HTTP code: 403
Response time: 233 ms

Resolved: TechinAsia_Laravel_API is back up in 5ee50a6 after 7 minutes.


text:
🛑 TechinAsia is down

In d029420, TechinAsia (https://www.techinasia.com) was down:

HTTP code: 403
Response time: 773 ms

Resolved: TechinAsia is back up in 3b8d8dc after 7 minutes.


text:
🛑 TechinAsia_WordPress_API is down

In 1e9c3a2, TechinAsia_WordPress_API (https://www.techinasia.com/wp-json/techinasia/2.0/posts) was down:

HTTP code: 403
Response time: 227 ms

Resolved: TechinAsia_WordPress_API is back up in 388c947 after 7 minutes.


text:
🛑 TechinAsia_Laravel_API is down

In fbc4a1f, TechinAsia_Laravel_API (https://www.techinasia.com/api/2.0/companies) was down:

HTTP code: 403
Response time: 227 ms

Resolved: TechinAsia_Laravel_API is back up in 80307f5 after 14 minutes.


text:
add simonbyrne to Julia maintainer list

cc: @tkelman @staticfloat @ninjin

also L34

done.

authors: simonbyrne tkelman

repo: travis-ci/travis-build


text:
Tweaks to error messages and Sentry config

add bits to some log messages about what's happening next
log the JSON when there are parsing errors
reduce Sentry hook to panic and fatal levels by default, with option to include error level

The JSON payload often (always?) contains some credentials, so I'm not sure if logging it is a good thing.

@henrikhodne :facepalm: of course.  Hmm.  My intent here is to get more information about the error.  Maybe I could do something a tiny bit clever and replace all strings with "fafafaf".

I wonder if we can have scheduler put some kind of identifier in the headers of the message and then print that?

That'd be cool.  I'll back out the JSON logging for now.

:sparkles: Looks good :+1: :blue_heart:

authors: henrikhodne meatballhat

repo: travis-ci/worker


text:
go test github.com/travisjeffery/jocko/server deletes $TMPDIR

https://github.com/travisjeffery/jocko/blob/master/server/server_test.go#L189
https://github.com/travisjeffery/jocko/blob/master/server/server_test.go#L222

You probably want https://golang.org/pkg/io/ioutil/#TempDir instead.

Woh, thanks. Yeah I use ioutil.TempDir to create the dir that's actually used (dataDir). Just a stupid couple of lines there. At least I can tell people I've been shamed by Dave Cheney in an issue in the Go repo.

authors: davecheney dgryski travisjeffery

repo: travisjeffery/jocko


text:
🛑 Consus is down

In dcde628, Consus (https://api.treant.io/health/consus) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Consus is back up in 93e3f51.

repo: treant-io/status


text:
KOGITO-5702: t is not possible to use interface as field with XmlAdapter

It is needed to use some generic types in some cases and replace it by real values in XmlAdapter.
If I am doing it I am getting this error:
[ERROR] /Volumes/Workspace/treblereel/mapper-xml/tests/jre/target/generated-test-sources/test-annotations/org/treblereel/gwt/xml/mapper/client/tests/annotations/xmladapter/generic/BeanBeanXMLSerializerImpl.java:[33,101] cannot find symbol
  symbol:   class ValueInterfaceBeanXMLSerializerImpl
  location: package org.treblereel.gwt.xml.mapper.client.tests.annotations.xmladapter.generic
[ERROR] /Volumes/Workspace/treblereel/mapper-xml/tests/jre/target/generated-test-sources/test-annotations/org/treblereel/gwt/xml/mapper/client/tests/annotations/xmladapter/generic/BeanBeanXMLDeserializerImpl.java:[36,101] cannot find symbol
  symbol:   class ValueInterfaceBeanXMLDeserializerImpl
  location: package org.treblereel.gwt.xml.mapper.client.tests.annotations.xmladapter.generic

This PR contains full reproducer.

@hasys thak you, good catch!

authors: hasys treblereel

repo: treblereel/mapper-xml


text:
Publish lakeFS Hadoop FileSystem to Maven Central and to S3

Artifact coordinates: io.lakefs:hadoop-lakefs, similar to org.apache.hadoop:hadoop-aws.
Publish a stripped JAR to Maven Central (to be used as a dependency when building libraries) and an assembled JAR to S3 (to be loaded into Spark).

Everything done, including published snapshots.  Closing -- no point in leaving this open until "The Right Version" is published, that's a release not an issue.

Now published, too.

repo: treeverse/lakeFS


text:
Present technical conclusions from failed OC project

Please add more in review!
Closes #4810.

Pulling by force: this is a docs PR and functional tests are not blockers to pulling it.


text:
Is it shit?

`
#include <stdio.h>
#include <stdlib.h>
#include <time.h>
int main() {
int ililillililililililili = 7355608;
char llillilililillilililillii = 'ilililillililililililili';
float iillilililiiililililllllillili = 3.14159f;
srand(time(NULL));

ililillililililililili = ililillililililililili + llillilililillilililillii;
ililillililililililili = ililillililililililili + (int)llillilililillilililillii;
iillilililiiililililllllillili = iillilililiiililililllllillili * ililillililililililili;

printf("ililillililililililili = %d, llillilililillilililillii = %c, iillilililiiililililllllillili = %.2f\n", ililillililililililili, llillilililillilililillii, iillilililiiililililllllillili);

return ililillililililililili;

}
`
ez code

int main() { int ililillililililililili = 7355608; char llillilililillilililillii = 'ilililillililililililili'; float iillilililiiililililllllillili = 3.14159f;

srand(time(NULL));

ililillililililililili = ililillililililililili + llillilililillilililillii;
ililillililililililili = ililillililililililili + (int)llillilililillilililillii;
iillilililiiililililllllillili = iillilililiiililililllllillili * ililillililililililili;

printf("ililillililililililili = %d, llillilililillilililillii = %c, iillilililiiililililllllillili = %.2f\n", ililillililililililili, llillilililillilililillii, iillilililiiililililllllillili);

return ililillililililililili;

}
` ez code

repo: trekhleb/state-of-the-art-shitcode


text:
Feature/cofss 260 add gis feedback

For an easy-to-read copy of this readme, see https://github.com/trendmicro/cloudone-filestorage-plugins/tree/feature/COFSS-260_Add_GIS_feedback/post-scan-actions/aws-python-promote-or-quarantine

Hi @ChristinaSmith123 ,
I'm okay with the content. But the our case ID cannot be shown on anywhere per company policy. Please squash and remove the case ID from commits. Once you force push to this branch, close the PR and delete the branch. Don't close the PR before you force push the commit or I'm afraid the commit history will remain. Finally, push to another branch without case ID for another PR.

repo: trendmicro/cloudone-filestorage-plugins


text:
The search function is not effective

raise error
data, entries, cursor = await self.backoff(lambda: self.get(client, params), **kwargs)
TypeError: cannot unpack non-iterable NoneType object
search = Search(email, username, password, save=True, debug=1, proxies=proxies)
res = search.run(
limit=37,
retries=1,
latest=True,
queries=[
{
'category': 'Latest',
'query': 'test'
}
],
)

It looks like if there was any error during tweet search iteration (maybe lost internet connection, rate limit exceeding etc.), TypeError: cannot unpack non-iterable NoneType object exception is raised, effectively discarding all tweets that have been retrieved until that moment. It would be great if successfully retrieved tweets are returned, maybe with some indication of error details.
  File "/app/./twitter/search.py", line 50, in run
    return asyncio.run(self.process(queries, limit, out, **kwargs))

  File "/usr/local/lib/python3.10/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)

  File "uvloop/loop.pyx", line 1517, in uvloop.loop.Loop.run_until_complete

  File "/app/./twitter/search.py", line 54, in process
    return await asyncio.gather(*(self.paginate(s, q, limit, out, **kwargs) for q in queries))

  File "/app/./twitter/search.py", line 74, in paginate
    data, entries, cursor = await self.backoff(lambda: self.get(client, params), **kwargs)

TypeError: cannot unpack non-iterable NoneType object

authors: godusoppp msvprogs

repo: trevorhobenshield/twitter-api-client


text:
Update spectral.yaml

Added rule to require the description field within tags

Will handle this by adding the recommended flag to the OAS rule import. More information found here: https://docs.stoplight.io/docs/spectral/0a73453054745-recommended-or-all

authors: CarrieRaglan jbend

repo: trimble-oss/openapi-spectral-rules


text:
Change slack channel for build notifications

Scope of changes
This PR changes the build notification channel from gds-github to gds-containers
Type of change

[ ] bug fix
[ ] new feature
[ ] documentation
[ ] other (describe)

Acceptance criteria
Describe how reviewers can test this change to be sure that it works correctly. Add a checklist if possible
Author checklist

[ ] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[ ]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[ ]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

@rebeccabilbro I hope it's ok - I'm going to merge this to try to fix the builds in #792 -- the container builds are failing with Slack errors.

authors: bbengfort rebeccabilbro

repo: trisacrypto/directory


text:
Open Demo03.xlsx with Excel2019, it prompts file needs to be recovered

When opening the "Demo3.xlsx" file with Excel 2019, Excel prompts.

This is exactly the same as the previous feedback from  bytehammer2 (Issue #105).
After clicking "Yes", the file is repaired and can be opened normally.
After carefully comparing the repaired xml file changes, I finally determined that some of the element in docProps/app.xml was incorrect, which caused the Excel repair prompt.
Here is the content of the "docProps/app.xml" file extracted from the Excel file before the recovery, you can see that the value of the vt:i4 element in HeadingPairs node is 1.
<?xml version="1.0" encoding="UTF-8"?>
<Properties xmlns="http://schemas.openxmlformats.org/officeDocument/2006/extended-properties" xmlns:vt="http://schemas.openxmlformats.org/officeDocument/2006/docPropsVTypes">
   <Application>Microsoft Macintosh Excel</Application>
   <DocSecurity>0</DocSecurity>
   <ScaleCrop>false</ScaleCrop>
   <HeadingPairs>
      <vt:vector size="2" baseType="variant">
         <vt:variant>
            <vt:lpstr>Worksheets</vt:lpstr>
         </vt:variant>
         <vt:variant>
            <vt:i4>1</vt:i4>
         </vt:variant>
      </vt:vector>
   </HeadingPairs>
   <TitlesOfParts>
      <vt:vector size="4" baseType="lpstr">
         <vt:lpstr>Sheet2</vt:lpstr>
         <vt:lpstr>Sheet3</vt:lpstr>
         <vt:lpstr>Sheet4</vt:lpstr>
         <vt:lpstr>Sheet5</vt:lpstr>
      </vt:vector>
   </TitlesOfParts>
   <Company />
   <LinksUpToDate>false</LinksUpToDate>
   <SharedDoc>false</SharedDoc>
   <HyperlinksChanged>false</HyperlinksChanged>
   <AppVersion>16.0300</AppVersion>
</Properties>

However, in the "docProps/app.xml" file extracted from the repaired Excel file, we can see that the value of the vt:i4 element of the HeadingPairs node is 4.
<?xml version="1.0" encoding="UTF-8"?>
<Properties xmlns="http://schemas.openxmlformats.org/officeDocument/2006/extended-properties" xmlns:vt="http://schemas.openxmlformats.org/officeDocument/2006/docPropsVTypes">
   <Application>Microsoft Macintosh Excel</Application>
   <DocSecurity>0</DocSecurity>
   <ScaleCrop>false</ScaleCrop>
   <HeadingPairs>
      <vt:vector size="2" baseType="variant">
         <vt:variant>
            <vt:lpstr>Worksheets</vt:lpstr>
         </vt:variant>
         <vt:variant>
            <vt:i4>4</vt:i4>
         </vt:variant>
      </vt:vector>
   </HeadingPairs>
   <TitlesOfParts>
      <vt:vector size="4" baseType="lpstr">
         <vt:lpstr>Sheet2</vt:lpstr>
         <vt:lpstr>Sheet3</vt:lpstr>
         <vt:lpstr>Sheet4</vt:lpstr>
         <vt:lpstr>Sheet5</vt:lpstr>
      </vt:vector>
   </TitlesOfParts>
   <Company />
   <LinksUpToDate>false</LinksUpToDate>
   <SharedDoc>false</SharedDoc>
   <HyperlinksChanged>false</HyperlinksChanged>
   <AppVersion>16.0300</AppVersion>
</Properties>

So it can be inferred that the value of vt:i4 of HeadingPairs node should be same with the sheets count.
Apply the following patch code to the addSheetName/deleteSheetName/appendSheetName/prependSheetName/insertSheetName functions in XLProperties.cpp. The value of vt:i4 element in HeadingPairs will be equal to the sheetCount and then this bug is fixed.
void XLAppProperties::appendSheetName(const std::string& sheetName)
{
    if (!m_xmlData) return;
    auto theNode = sheetNames(xmlDocument().document_element()).append_child("vt:lpstr");
    theNode.text().set(sheetName.c_str());
    int sheetCnt = sheetCount(xmlDocument().document_element()).as_uint();
    sheetCnt++;
    sheetCount(xmlDocument().document_element()).set_value(sheetCnt);
    headingPairsCounts(xmlDocument().document_element()).first_child().text().set(sheetCnt);
}

Interesting - this is still saved as <vt:i4>1</vt:i4> - maybe I should have read the issue list a few months ago :)
I'll try to find the specification of this field & whether it is indeed intended to hold the count of worksheets (which seems logical).

Okay, development branch is merged into main - this should be resolved.

authors: aral-matrix clerktz

repo: troldal/OpenXLSX


text:
🛑 Bazarr is down

In 7e93fc6, Bazarr (https://tronflix.app/bazarr/system/status) was down:

HTTP code: 521
Response time: 98 ms

Resolved: Bazarr is back up in cde05b1.

repo: tronyx/upptime


text:
Strange "hook" error

Any idea what the problem is, or how I debug?
: truffle test
Using network 'development'.

Compiling ./contracts/Adoption.sol...
Compiling ./test/TestAdoption.sol...

  TestAdoption
    1) "before all" hook: prepare suite

  0 passing (20s)
  1 failing

  1) TestAdoption
       "before all" hook: prepare suite:
     Error: while migrating TestAdoption: Returned error: VM Exception while processing transaction: revert
      at /usr/local/lib/node_modules/truffle/build/webpack:/packages/truffle-deployer/src/deployment.js:364:1
      at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:189:7)

This is the Ganache log, it says "revert" but no reason why:
[17:24:46]   Transaction: 0xd4f8e47ef6f02036d3880512ffe64545ce08b5e85cc28f2408242efaee272add
[17:24:46]   Contract created: 0x4e96714cc6c51e9b673ec09701e12ac3e27fb9b2
[17:24:46]   Gas usage: 190068
[17:24:46]   Block Number: 16
[17:24:46]   Block Time: Wed Jan 30 2019 17:24:44 GMT+0000 (GMT)
[17:24:46] eth_getTransactionReceipt
[17:24:46] eth_getCode
[17:24:46] eth_getBlockByNumber
[17:24:46] eth_getBlockByNumber
[17:24:46] eth_getBlockByNumber
[17:24:46] eth_estimateGas
[17:24:46] eth_getBlockByNumber
[17:24:46] eth_blockNumber
[17:24:46] eth_sendTransaction
[17:24:46]   Transaction: 0x2995d64ec8cff5018e91e99cf9fb850a4fb3153575e539de2b31998835907c1c
[17:24:46]   Contract created: 0xc43cc30198cf91e1f791bb1d29582e12ada1ceb7
[17:24:46]   Gas usage: 189480
[17:24:46]   Block Number: 17
[17:24:46]   Block Time: Wed Jan 30 2019 17:24:45 GMT+0000 (GMT)
[17:24:46]   Runtime Error: revert
[17:24:46] eth_call
[17:24:46] eth_getBlockByNumber

You can refer to this link....
https://ethereum.stackexchange.com/questions/47115/truffle-error-vm-exception-while-processing-transaction-revert

repo: truffle-box/pet-shop-box


text:
colegislator, bowess

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,c]

/trunk merge

repo: trunk-io/mergequeue-staging


text:
anakinetomer, firmarius

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,f]

/trunk merge


text:
fumaroles, granjeno

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[f,g]

/trunk merge


text:
bradypodidae, absey

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,b]

/trunk merge


text:
cantharidized

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c]

/trunk merge


text:
cloisonn, gimcracks

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,g]

/trunk merge


text:
downfalling, fosterlings

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,f]

/trunk merge


text:
enc, fining

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[e,f]

/trunk merge


text:
furls, genistein

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[f,g]

/trunk merge


text:
cocash, autosuggestible

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,c]

/trunk merge


text:
americana, endogamy

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,e]

/trunk merge


text:
captivatrix, buccina

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,c]

/trunk merge


text:
entoloma, dormitory

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,e]

/trunk merge


text:
curlylocks

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c]

/trunk merge


text:
femalely, bucrania

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,f]

/trunk merge


text:
ebulliometer

This pull request was generated by the 'mq' tool

/trunk merge


text:
baptisias, chetif

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[b,c]

/trunk merge


text:
gondoliers

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[g]

/trunk merge


text:
drawbar, brothy

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,d]

/trunk merge


text:
encyclics, fishpotter

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[e,f]

/trunk merge


text:
candace, dealates

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,d]

/trunk merge

repo: trunk-io/mergequeue


text:
gastrolater, bonaveria

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,g]

/trunk merge


text:
gewgawry, achtelthaler

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,g]

/trunk merge


text:
boskage, disquisitory

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,d]

/trunk merge


text:
dissimilarly, agamis

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,d]

/trunk merge


text:
graptolitoidea, ciminite

This pull request was generated by the 'mq' tool

/trunk merge


text:
adenocellulitis, enjoyably

This pull request was generated by the 'mq' tool

/trunk merge


text:
gonadectomies, eutaxite

This pull request was generated by the 'mq' tool

/trunk merge


text:
bundling, didymium

This pull request was generated by the 'mq' tool

/trunk merge


text:
comprovincial, estonia

This pull request was generated by the 'mq' tool

/trunk merge


text:
gangliest, breading

This pull request was generated by the 'mq' tool

/trunk merge


text:
coenurus, gigglers

This pull request was generated by the 'mq' tool

/trunk merge


text:
cenatory, fathoms

This pull request was generated by the 'mq' tool

/trunk merge


text:
auricyanide

This pull request was generated by the 'mq' tool

/trunk merge


text:
brailler, gossipmongering

This pull request was generated by the 'mq' tool

/trunk merge


text:
adonic, forementioned

This pull request was generated by the 'mq' tool

/trunk merge


text:
apologia, copaljocote

This pull request was generated by the 'mq' tool

/trunk merge


text:
dielectrical

This pull request was generated by the 'mq' tool

/trunk merge


text:
eremite, canstick

This pull request was generated by the 'mq' tool

/trunk merge


text:
festooneries, enough

This pull request was generated by the 'mq' tool

/trunk merge


text:
grinned, bullswool

This pull request was generated by the 'mq' tool

/trunk merge


text:
disprovement, foreworn

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[d,f]

/trunk merge


text:
coattailed, enlighteningly

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[c,e]

/trunk merge


text:
corser

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[c]

/trunk merge


text:
clablaria, flocked

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[c,f]

/trunk merge


text:
fructiferousness, benzotetrazine

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[b,f]

/trunk merge


text:
discophorous, gherkin

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[d,g]

/trunk merge


text:
erythrogenesis, appallingly

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,e]

/trunk merge


text:
doffers, berengarian

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[b,d]

/trunk merge


text:
abaka, clinologic

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,c]

/trunk merge


text:
chresards, fishtailed

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[c,f]

/trunk merge


text:
aluminish, gringolee

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,g]

/trunk merge


text:
enamellers, cryophilic

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[c,e]

/trunk merge


text:
bumpoff, fogmen

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[b,f]

/trunk merge


text:
enow, falseness

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[e,f]

/trunk merge


text:
gossipingly, euhemerized

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[e,g]

/trunk merge


text:
blizzardy, forebitt

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,f]

/trunk merge


text:
bracingness, cactales

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,c]

/trunk merge


text:
acarophilous, grimacers

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,g]

/trunk merge


text:
glaver, antislavery

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,g]

/trunk merge


text:
classless, freespac

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,f]

/trunk merge


text:
andrewsite, disquantity

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,d]

/trunk merge


text:
apneic

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a]

/trunk merge


text:
bowet, forepoled

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,f]

/trunk merge


text:
elflock, beetleheaded

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,e]

/trunk merge


text:
geotactically, drily

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[d,g]

/trunk merge


text:
🛑 pnt is down

In dfea6e0, pnt (https://portainer.pnt.truongsinh.pro) was down:

HTTP code: 0
Response time: 0 ms

Resolved: pnt is back up in 4ba87bb after 1 hour, 4 minutes.


text:
Update README

It's a bit outdated.

[x] new examples using new API instead of the old stuff made with Famous.
[x] Replace gitter badge with link to site and forums.

Finished in 7e55dc166775ff9dcd4e7239716e6377d828e38d

repo: trusktr/infamous


text:
chore(deps): update various dependencies

Summary
This PR fixes a typo in the CODEOWNERS file and upgrades various deps listed below

Storybook releated deps
Danger
Happo.io
Husky
webpack-cli

How To Test
Ensure build works yarn
Ensure tests run yarn test
Run storybook yarn storybook

lgtm 🌈
Approving this to help prevent blocking. But I have a question around peer-dependencies.
Also since most of these were minor releases, what do we think about relaxing the ^ dependency versioning to have the last value be a 0 so that we don't have to update the dependencies at such a granular level?
We could replace some of our dependencies with a ~ rather than a ^ which would allow us to have minor updates with ease.
=> SO answer around clarity about carat versus tilde in package.json
Right now because our dependency versions don't include a left-most zero digit, we might as well be hard-coding the version and not use the ^ nor the ~ in our dependencies.
Thanks for getting to this work @gidjin 🏆

If I understand correctly from the link using ~ would make it only update patch versions vs minor and patch versions like ^. So that feels more strict to me, so I'm not sure I am following your suggestion. Or are you saying only allowing patch versions would be easier to manage since minor upgrades would take manual intervention vs be caught by dependabot?

repo: trussworks/react-uswds


text:
Add option of enforcing TLS-only requests via the S3 bucket policy

This change allows an extra statement to be added to the log S3 bucket
policy that denies requests unless they're made via TLS.
This additional policy statement is necessary to be able to enforce
encryption-in-transit requirements alongside the encryption-at-rest
that's already handled by the
apply_server_side_encryption_by_default block on the S3 bucket
resource.
This policy is required for buckets managed by this module to pass the
AWS Config s3-bucket-ssl-requests-only[1] managed rule and
Prowler's[2] extra764 check, which although not part of the CIS
benchmark seems like a sensible thing to satisfy.
Note that Trussworks' AWS Config module[3] enables the
s3-bucket-ssl-requests-only check by default, so before this change,
the two modules together result in failing Config checks.
By default insecure requests are permitted, in line with S3 defaults
and the historical behaviour of this module.
Note that this change does not appear to be implementable in a safe
manner following the pattern of other statements of flipping the
effect. My reading of explicitly allowing aws:SecureTransport requests
would have the effect of permitting all anonymous HTTP requests, which
is definitely not the opposite of denying any HTTP requests.
[1] https://docs.aws.amazon.com/config/latest/developerguide/s3-bucket-ssl-requests-only.html
[2] https://github.com/toniblyx/prowler
[3] https://github.com/trussworks/terraform-aws-config

Thanks for the very detailed PR. I plan to take a look at it today, but just wanted to say I appreciate you adding tests!

Closing in favour of #62 which - as per feedback on this PR - makes TLS-only requests the default.

authors: bazbremner dynamike

repo: trussworks/terraform-aws-logs


text:
fix(app): Update the handle vp logic to support selective disclosure

Selective disclosure flow and other flows works as expected now

Codecov Report
Patch and project coverage have no change.

Comparison is base (3e9d6fc) 89.79% compared to head (e89464b) 89.79%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #441   +/-   ##
=======================================
  Coverage   89.79%   89.79%
=======================================
  Files          79       79
  Lines        2950     2950
=======================================
  Hits         2649     2649
  Misses        199      199
  Partials      102      102

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

repo: trustbloc/wallet-sdk


text:
[CI] Error in Publish Image workflow

After recent upgrade to Go 1.17 we started seeing this error in our publish workflow:
Error: buildx failed with: error: failed to solve: golang:1.17-alpine3.12: docker.io/library/golang:1.17-alpine3.12: not found

@rolsonquadras could you take a look at this, please?

repo: trustbloc/wallet


text:
OpenARC crashes when only a single c= canonicalization is present in the ARC Message Signature

Summary
If the ARC-Seal c= field only contains one value, arc_parse_canon_t passes a NULL to arc_name_to_code, causing a crash in strcasecmp
Detail
RFC-6376 (DKIM) (section 3.5) :
If only one algorithm is named, that algorithm is used for the header and "simple" is used for the body.
For example, "c=relaxed" is treated the same as "c=relaxed/simple".
RFC-8617 (ARC) states the canonicalization uses RFC-6376 definitions for fields.
If further states that only "relaxed" canonicalization is allowed, so if missing, set to "relaxed" instead
This means that a value of c=relaxed is permitted in the ARC Message Signature.
Sample data:
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed; d=xxxx.com; s=securemail; t=1615885933;	bh=9DhmaIwA6aWZhCUaFaOFDUoIZxR3
The bug
There is no check for NULL (no token found) on the second call to strtok_r in arc_parse_canon_t, causing a crash when the NULL token is passed to arc_name_to_code

Apologies, I see this fix is in the develop branch already

repo: trusteddomainproject/OpenARC


text:
Send Binance getting invalid hex

    let privateKey = wallet.getKeyForCoin(coin: .binance)
    let publicKey = privateKey.getPublicKeySecp256k1(compressed: true)

    print("BNBPrivateKey", privateKey.data.hexString)
    print("BNBPublivKey", privateKey.getPublicKeySecp256k1(compressed: true))
    print("BNBAddress", wallet.getAddressForCoin(coin: .binance))

    let token = BinanceSendOrder.Token.with {
        $0.denom = "BNB" // BNB or BEP2 token symbol
        $0.amount = Int64(0.001)   // Amount, 1 BNB
    }

    let orderInput = BinanceSendOrder.Input.with {
        $0.address = AnyAddress(publicKey: publicKey, coin: .binance).data
        $0.coins = [token]
    }

    let orderOutput = BinanceSendOrder.Output.with {
        $0.address = AnyAddress(string: "bnb1vczjtps08p3uquvvw9mnwc6r08urwz6yzu4aym", coin: .binance)!.data
        $0.coins = [token]
    }

    let input = BinanceSigningInput.with {
        $0.chainID = "Binance-Chain-Tigris" // Chain id (network id),                 from /v1/node-info api
        $0.accountNumber = 576590              // On chain account / address number,     from /v1/account/<address> api
        $0.sequence = 1                  // Sequence number, plus 1 for new order, from /v1/account/<address> api
        $0.source = 0                     // BEP10 source id
        $0.privateKey = privateKey.data
        $0.memo = ""
        $0.sendOrder = BinanceSendOrder.with {
            $0.inputs = [orderInput]
            $0.outputs = [orderOutput]
        }
    }

    let output: BinanceSigningOutput = AnySigner.sign(input: input, coin: .binance)
    print("output", output.encoded.hexString)

   Above is my code..I need to send bnb from one address to another..Folowing exactly same as your document. But am getting invalid hexString.

   Please help to sort out this issue.

can you share your address? $0.amount = Int64(0.001) is 0?

Hi.. My address: bnb10mfhwu4ktjvzlgyqmkrtdulc303wv2dx34mve7

I need to send 0.001 BNB

BNB decimals is 8, you need to pass 100000 for 0.001 BNB

Ok..Now am getting a hexString..
When I try to send that hexString for a broadcast API..am receiving error:
{
code = 400;
"failed_tx_index" = 0;
message = "encoding/hex: invalid byte: U+007B '{'";
"success_tx_results" =     (
);
}
API: https://dex.binance.org/api/v1/broadcast
Post parameters: let param = ["sync": false, "body": output.encoded.hexString] as [String: Any]
Don't know what am doing wrong here??

hmm, try sequence = 0?

Still same error response

from: https://docs.binance.org/api-reference/dex-api/paths.html#apiv1broadcast, sync is located in url query, and body should be your raw tx

Can refer some example or any other document??

sorry, can you join https://t.me/BinanceDEXchange and ask them?

ok

close now because rpc part is not related with wallet core

repo: trustwallet/wallet-core