cargo-risczero fails to build after new cargo-generate / bstr update

The following nightly workflow fails while building cargo-generate:
https://github.com/risc0/risc0/actions/runs/5040495627/jobs/9039330965#step:6:195
Upstream tracking issue:
https://github.com/cargo-generate/cargo-generate/issues/942
This currently blocks cargo install cargo-risczero installs
Reproduction locally:
cd risc0
cargo install --path risc0/cargo-risczero

I am seeing this issue locally on a fresh install, agreed that the cargo-generate upstream is broken

cargo-generate pushed a fix in the following commit to handle bstr 1.5: https://github.com/cargo-generate/cargo-generate/commit/7aa00177681596f2aa430c7f4f1000d038162f13

Should be fixed as of 0.15.1 (this PR specifically: https://github.com/risc0/risc0/pull/580)


GLEW could not be initialized: Missing GL version

Hello, i've met a problem in running demo.py
2022-04-04 14:55:26.887 (  15.100s) [        F0A55E80]vtkOpenGLRenderWindow.c:493    ERR| vtkEGLRenderWindow (0x561980223bb0): GLEW could not be initialized: Missing GL version
run-demo.sh: line 19:  7579 Segmentation fault      (core dumped)
I've tried several approaches but all of them failed. Do you have any idea about this bug?

Haven't seen this issue myself, but maybe this thread can help: https://github.com/openai/mujoco-py/issues/268. I use mayavi==4.7.2 in my environment.


Forward # comments

Is your feature request related to a problem? Please describe.
My source m3u playlist looks like this
#EXTM3U
#EXTINF:-1 provider="Magio GO" group-title="Všeobecné" tvg-id="4099" tvg-logo="https://files.cdn.magio.tv/tv_logos/jednotka-hd.png" catchup="append" catchup-source="?utc={utc}&utcend={utcend}",Jednotka
#KODIPROP:inputstream=inputstream.adaptive
#KODIPROP:inputstream.adaptive.manifest_type=mpd
#KODIPROP:inputstream.adaptive.internal_cookies=true
#KODIPROP:mimetype=application/dash+xml

Threadfin ignores the #KODIPROP comments and outputs this:
#EXTM3U url-tvg="http://URL/xmltv/threadfin.xml" x-tvg-url="http://URL/xmltv/threadfin.xml"
#EXTINF:0 channelID="x-ID.0" tvg-chno="1000" tvg-name="Jednotka" tvg-id="1000" tvg-logo="https://files.cdn.magio.tv/tv_logos/jednotka-hd.png" group-title="Všeobecné",Jednotka
http://URL/stream/63e3332acd506ff069b97741c35ef2b2

This makes the playlist unable to be played in Kodi, as it requires those tags. Threadfin could have an option to simply copy all adjacent comments to the output.
I see that this is a relevant issue to #73

I will not be adding this support. Sorry but no more new features will be built


Switch from docker to podman for running tests

Summary: Switch from docker to podman for running bpf tests.
The outer run_docker script still uses docker, but the tests themselves run containers with podman.
Type of change: /kind cleanup
Test Plan: All bpf tests pass under podman.

It might be nice to include more detail in the diff summary of why we are switching to podman.


Meaninful Args

Maybe prepare a set of args that can be used when defining a producer or a view that has a specific meaning in that context.
Example:
// This shows the view if the shouldMount prop is truthy
// else it will return null
const a = view((
   foo = Get.foo.value,
   shouldMount = Arg.foo > 10
) =>
{foo}
)

// This is equivalent to having that logic inside the component:
const a = view((
   foo = Get.foo.value
) => {
  if (foo < 10) {
    return null
  }
  return
{foo}

})

Another interesting arg is isInViewport which works very well if it's paired to a producer:
const a = view((...) => {...})
const b = producer((
  isInViewport
) => { // change classes, or trigger something that updates the view })
a.producers = [b]

Other meaningful args could include:

uniqueId: allows views or producers to store something in a personal location
any lifecycle hooks: mounting, unmounting, bootstraping

This breaks way too many concerns and complicates the API.


[B03679] Add an openseadragon content viewer

Coverage remained the same at 27.497% when pulling d12a81f35fd457bfa2d045dba376134cd2de553f on dame-sprint-oct-b03679-dragon into 82758fd247e3eab7bd5d8ebe38b1d822af1ac0c5 on dame-sprint-oct-staging.


[zero] revert PR #3166, it disabled grad clip for bf16

#3166 inadvertently disabled gradient clipping when using bf16. The original intention was to remove grad scaling when using bf16, however when using bf16 the loss scale is forced to 1.0 which will result in no grad scaling occurring.

thanks, good catch, yes, this is the grad clip to avoid exploding, no matter which format is used. It is independent with loss scale of fp16.


Error running on Ubuntu

(I originally thought it's related to another repo - https://github.com/lbarasti/twitch-url-checker/issues/1)
crystal src/url-checker.cr
/usr/bin/ld: cannot find -lgpm (this usually means you need to install the development package for libgpm)
collect2: error: ld returned 1 exit status
Error: execution of command failed with code: 1: `cc "${@}" -o '/home/oren/.cache/crystal/crystal-run-url-checker.tmp'  -rdynamic  -lz `command -v pkg-config > /dev/null && pkg-config --libs --silence-errors libssl || printf %s '-lssl -lcrypto'` `command -v pkg-config > /dev/null && pkg-config --libs --silence-errors libcrypto || printf %s '-lcrypto'` -lyaml -lpcre -lm /usr/bin/../lib/crystal/lib/libgc.a -lpthread /usr/share/crystal/src/ext/libcrystal.a -levent -lrt -lncursesw -ltinfo -lgpm -ldl -L/usr/bin/../lib/crystal/lib -L/usr/lib -L/usr/local/lib`

I tried installing the following but I already had them installed (:
sudo apt-get install libgmp3-dev
sudo apt-get install -y libgmp-dev

Any ideas?

Installing this solved my issue
apt-get install libgpm-dev        # needs only for static link

but the only example that works is color.cr. hello.cr prints nothing and border.cr shows:

In /home/oren/p/crystal/crt.cr/src/crt/window.cr:6:20

 6 | def initialize(@row = -1, @col = -1, y = 0, x = 0)
                    ^---
Error: instance variable '@row' of Crt::Window must be Int32, not Float64
~/p/crystal/crt.cr/examples crystal color.cr
~/p/crystal/crt.cr/examples crystal hello.cr
~/p/crystal/crt.cr/examples crystal border.cr
Showing last frame. Use --error-trace for full trace.

In /home/oren/p/crystal/crt.cr/src/crt/window.cr:6:20

 6 | def initialize(@row = -1, @col = -1, y = 0, x = 0)
                    ^---
Error: instance variable '@row' of Crt::Window must be Int32, not Float64

Hi @oren
Updated for crystal-0.32.1. Could you try 0.4.1? 🙏

I see an improvement! the borer.cr seems to work (i see two rectangles). So now hello.cr and the code from the README don't work. BTW, I see similar issue in other ncurses libraries - https://github.com/agatan/ncurses.cr/issues/10


No error validation on container name

Rancher Versions: 4/10
Steps to Reproduce:

Create a container with the name "e.g. myapp"

Results: Creates container.  Probably should follow same rules as service name currently does, especially since container is going to be more prominent.

Version - 6/12 (2.0 Alpha)
This is not fixed


HTTP Error 404: not found

I installed youtube-dl by the following instruction in README.md
sudo curl -L https://yt-dl.org/downloads/latest/youtube-dl -o /usr/local/bin/youtube-dl
sudo chmod a+rx /usr/local/bin/youtube-dl

with the latest version 2019.01.17 and when I tried to find out the resolution to download the video from youtube by following command youtube-dl -F 'https://www.youtube.com/watch?v=ehtUb55Rmmg' I got this error.
WARNING: unable to download video info webpage: HTTP Error 404: Not Found
WARNING: unable to download video info webpage: HTTP Error 404: Not Found
WARNING: unable to download video info webpage: HTTP Error 404: Not Found
WARNING: unable to download video info webpage: HTTP Error 404: Not Found
WARNING: unable to download video info webpage: HTTP Error 404: Not Found
Traceback (most recent call last):
  File "/usr/bin/youtube-dl", line 11, in <module>
    load_entry_point('youtube-dl==2019.1.17', 'console_scripts', 'youtube-dl')()
  File "/usr/lib/python3/dist-packages/youtube_dl/__init__.py", line 477, in main
    _real_main(argv)
  File "/usr/lib/python3/dist-packages/youtube_dl/__init__.py", line 467, in _real_main
    retcode = ydl.download(all_urls)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line 2002, in download
    url, force_generic_extractor=self.params.get('force_generic_extractor', False))
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line 793, in extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 508, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1672, in _real_extract
    token = video_info.get('token') or video_info.get('account_playback_token')
AttributeError: 'NoneType' object has no attribute 'get'

Try updating to the latest version with youtube-dl --update

Try updating to the latest version with youtube-dl --update

I don't quite have the same error as the original threadstarter, but all
age-gate restricted videos at youtube, since some days, no longer
work, even with the current git checkout of youtube-dl. It seems to me
as if Google changed a few things to make it harder to download
videos directly.

Try updating to the latest version with youtube-dl --update

youtube-dl --update
Usage: youtube-dl [OPTIONS] URL [URL...]

youtube-dl: error: youtube-dl's self-update mechanism is disabled on Debian.
Please update youtube-dl using apt(8).
See https://packages.debian.org/sid/youtube-dl for the latest packaged version.

youtube-dl: error: youtube-dl's self-update mechanism is disabled on Debian.

you have multiple versions installed in the system.

no, i have installed i have just installed through apt-get command

youtube-dl is already the newest version (2019.01.17-1.1).
...
youtube-dl --version
2021.05.16

obviously you have two versions installed(2019.01.17 and 2021.05.16), remove the old version.

youtube-dl is already the newest version (2019.01.17-1.1).
...
youtube-dl --version
2021.05.16

obviously you have two versions installed(2019.01.17 and 2021.05.16), remove the old version.

thank you I have removed and installed it again and my problem is been solved


Overhaul internal representation, replacing NS… with …Box types

This PR removes any remaining use of NS…Array/NS…Dictionary/NSNumber/NSDecimalNumber/NSNull/… (as storage) from the code-base.
It introduces an internal type …
internal enum Box {
    case null(NullBox)
    case bool(BoolBox)
    case decimal(DecimalBox)
    case signedInteger(SignedIntegerBox)
    case unsignedInteger(UnsignedIntegerBox)
    case floatingPoint(FloatingPointBox)
    case string(StringBox)
    case array(ArrayBox)
    case dictionary(DictionaryBox)
}

… as well as accompanying variant box types, replacing use of Any/NS….
👷🏻♀It improves type-safety by reducing use of Any (from 60 down to 19 occurrences) as well as NSObject (from 37 down to 1 occurrence).
🏗It further more levels the field for improvements/additions such as support for order-preserving elements & attributes.
💡Thanks to encapsulation we can now safely change the inner logic of DictionaryBox to retain insertion order.

The problems I see with turning Box into a protocol are these:
The protocol(s) would have to look something like this to work:
protocol AnyBoxProtocol: Equatable {
    var xmlString: String { get }
}

protocol BoxProtocol: AnyBoxProtocol {
    associatedtype Unboxed

    init(_ unboxed: Unboxed)

    func unbox() -> Unboxed
}

But in the case of SignedIntegerBox/UnsignedIntegerBox/FloatingPointBox the BoxProtocol couldn't even be implemented properly as their init(_:) and func unbox differ significantly due to covering whole type families, not just a single wrapped type.
If Swift allowed for multiple protocol conformances we'd be fine. Alas it doesn't.
Another benefit of using a enum is that we get a guarantee for exhaustive switches.
Adding a new box type some time in the future is far less brittle that way, than it is with type erasure (be it Any or protocol Box).

Also could Apple please get rid of the plague that is . xcodeproj already?
Those merge conflicts are the worst. It's almost 2019, damnit! 😩

Great point, I think we should consider moving all custom settings to Package.xcconfig like I've done in CoreXLSX and get rid of .xcodeproj altogether in the repository encouraging users to run swift package generate-xcodeproj --xcconfig-overrides Package.xcconfig on their side when needed. The only problem is baselines which are stored within .xcodeproj and I'm not sure how useful benchmarks are without baselines... 🤔

Commit 7fe7984 just removed enum Box in favor of protocol Box. 🙂

Rebased onto master.

Phew, this PR ended up quite bigger than anticipated, but it's worth it, I think.
The separation and encapsulation, as well as addition of finely-grained unit tests should give us a good and solid foundation for future improvements and bug fixes.
Thanks for your comments, @MaxDesiatov!


fix: gizmo filtering

This PR is an alternative for #39

this is not really clean, you are still accessing the blender_object by name , what happen if you have two object with the same name?
and is not better in term of performance , the cost of accessing the context surely increase with the size of the scene


Update directives to add manifest-src to Chrome/Firefox

Closes #338.

Adds the manifest-src CSP directive to Chrome/Firefox
Removes reflected-xss

I also took the opportunity to bump the ruby version to the latest. I did not update the Changelog, let me know if that's necessary and I will.
If you have any questions/considerations, let me know, thanks!

Yay! Thanks @carlosantoniodasilva. I can update the changelog.
Since master represents the (unreleased) 4.x line, I'll cherry-pick these into 3.x and push a new gem next week.

(leaving this open so I remember to do this next week)

@oreoshake thanks! I totally missed the 3.x branch vs master being 4x. Let me know if you'd prefer a separate PR targeting 3.x or if I can help with anything else!

Don't worry about it! It's not obvious and I'm seriously lagging on
releasing 4.x so this gives me more motivation to do so. Unfortunately, a
kitchen accident 🔪 has made coding temporarily more difficult 😆.
On Thu, Jul 13, 2017 at 17:02 Carlos Antonio da Silva <
<EMAIL_ADDRESS>wrote:

@oreoshake https://github.com/oreoshake thanks! I totally missed the
3.x branch vs master being 4x. Let me know if you'd prefer a separate PR
targeting 3.x or if I can help with anything else!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/twitter/secureheaders/pull/339#issuecomment-315233712,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAbYBB5o55bn0WQYYFDZX7THM1mwNmguks5sNq_ugaJpZM4OVwLk
.

Released in 3.6.7! Thanks again.

:tada: thanks so much @oreoshake! And sorry to hear about the 🔪  accident!


WL-5304 Update the declaration of Authorship

This is ready for the remote exams deployment.

Merged as this needs to get into the build soon.


Update version: lode.lode version 0.34.0

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115103&drop=dogfoodAlpha

@wingetbot run


Algolia search isn't working in v4.4.0 documentation

Operating system [macOS] and version [iMac (21.5-inch, Mid 2011)]
Browser and version [Chrome, Firefox, Safari, Brave]

It's fixed now.


Add support for unsigned data types

Could you add support for unsigned data types and builder data types:

sbyte
ushort
uint
ulong
StringBuilder
UriBuilder

These types are included in v1.2.6. Can we have TimeZone and StringReader types added as well?
Is there a way for users to register types?


Incomplete Docs: What should be the error response for adaptive card actions?

https://github.com/MicrosoftDocs/AdaptiveCards/blob/a5d7403042d00acb58c0260d7a77156b89b5cc05/AdaptiveCards/authoring-cards/universal-action-model.md?plain=1#L217-L225
The docs for the error type are just a "todo".
Could you give me an example what i should return for the following types:

application/vnd.microsoft.error (400)
application/vnd.microsoft.activity.loginRequest (401)
application/vnd.microsoft.error.preconditionFailed (412)
application/vnd.microsoft.error (500)

Update, I ended up discovering theres a factory for these types:
using Microsoft.TeamsFx.Conversation;

var invokeRes = InvokeResponseFactory.ErrorResponse(InvokeResponseErrorCode.BadRequest, "Invalid Data");

return (AdaptiveCardInvokeResponse)res.Body;


Why is the author's best run not good?

I downloaded the author’s best run from wandb, and after experimentation, the results are as follows:

Did I download the wrong model?

Thank you for your reply!

Sorry to disappoint you, but even the best run has 17% character error rate :(
But it seems like the model works better if you resize the image to something closer to those in the training dataset.

Also, this was meant to be a student project, so I stopped working on it after a month. I hope you can find a way to improve it.

Dear sir, I met the same problem when converting polynomials, so what size should we convert the input to when using your best run model? @kingyiusuen


Rounding of e5m2 inconsistent with OCP spec.

The OCP spec pdf declares that rounding for E5M2 (and analogously for E4M3) should round all values larger than FLOAT_MAX to infinity in non-saturation mode.
In contrast, ml_dtypes implements the IEEE-like behaviour that values between FLOAT_MAX + SPACE round to FLOAT_MAX, where SPACE is the value half way between FLOAT_MAX and nextUp(FLOAT_MAX), if the latter were finite.
dtype = ml_dtypes.float8_e5m2
convert = lambda v: np.array([v]).astype(dtype).astype(float).item()

print(f'{convert(57344.0)=}')
print(f'{convert(57344.1)=} <-- should be inf')
print(f'{convert(61439.9)=} <-- should be inf')
print(f'{convert(61440.0)=}')

prints
convert(57344.0)=57344.0
convert(57344.1)=57344.0 <-- should be inf
convert(61439.9)=57344.0 <-- should be inf
convert(61440.0)=inf

More detailed workings at colab

Relevant table from the spec:


Cannot Watch Movies with plexdrive and plex

I have mounted the plexdrive and plex can see all of the files just fine.  But every time I go to watch something it throws in plex an s1001 error.  I've researched this to the moon and back about permissions and this and that and I have everything as far as I can tell setup correctly.  I'm hoping that someone might have some insight into something that maybe they've experienced this before.  The folders I'm trying to watch from were shared with me by someone else in my gdrive I don't know if that plays into this or not.  Thanks.

Is this still an issue?

Yeah I'm still having issues with it.  This is what I"m seeing in my logs
Jun 22, 2018 10:13:09.287 [0x7f5b1abf6700] ERROR - MDE: video has neither a video stream nor an audio stream Jun 22, 2018 10:13:09.287 [0x7f5b1abf6700] ERROR - Streaming Resource: Cannot make a decision because either the file is unplayable or the client provided bad data
I've attempted to have plex analyze everything in the libraries in order to find the audio/video stream.  Someday's it works just fine but its a lot of miss before a hit.

I think it was mentioned in another issue, that Google applies much more aggressive rate limiting on shared files.


Add support to multiple process groups by syncing across ranks

Summary
Add support to multiple process groups by syncing across ranks.
Test Plan
$ comm_replay --trace-type et --trace-path /home/sanshang/021_debug/000_code/param/trace/traces_megatronlm_gpt_43B_32ranks_pytnightly0703/execution_trace

@GSSBMW, I converted the dictionary (loaded from json) between "str" to "str" to a dictionary between "int" to "str", keep the sort code. Please review it. Thanks


enhance: complete hypergraph rule.

Proposed changes
Issue Number: close #xxx
Problem summary
Describe your changes.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

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

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.5 seconds
load time: 447 seconds
storage size:<PHONE_NUMBER>0 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221108151614_clickbench_pr_42220.html


Obj-C support?

Can we please have @objc support for this library?

Sure. Give me like a day or two. The only annoying this is that ChronoParsedResult can’t be represented in Objective-C, since it’s a struct. Would you be cool with parsedResultsFrom(naturalLanguageString: String, referenceDate: Date?) returning an NSDictionary instead of a ChronoParsedResult?

Or I suppose I could create a ChronoParsedResultReference that’s just a class representation of ChronoParsedResult.


Redirect Manager - Import is not working on aem-sdk-quickstart-2021.12.6151.20211217T120950Z-211100

Required Information

[ ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: aem-sdk-quickstart-2021.12.6151.20211217T120950Z-211100
[ ] ACS AEM Commons Version: 5.1.0
[ ] Reproducible on Latest? yes

Expected Behavior
I am able to import redirects from Excel file on Redirect Manager page (Import tab)
Actual Behavior
There is 400 Bad Request as a response to form's request.
RequestProgressTracker Info for this request points out that wrong servlet has been chosen:

0 TIMER_START{Request Processing}
0 COMMENT timer_end format is {,}
4 LOG Method=POST, PathInfo=null
5 TIMER_START{handleSecurity}
1285 TIMER_END{1278,handleSecurity} authenticator org.apache.sling.auth.core.impl.SlingAuthenticator@46ec975d returns true
1858 TIMER_START{ResourceResolution}
1936 TIMER_END{77,ResourceResolution} URI=/apps/acs-commons/content/redirect-manager/jcr:content.import.html resolves to Resource=JcrNodeResource, type=acs-commons/components/utilities/manage-redirects, superType=null, path=/apps/acs-commons/content/redirect-manager/jcr:content
1941 LOG Resource Path Info: SlingRequestPathInfo: path='/apps/acs-commons/content/redirect-manager/jcr:content', selectorString='import', extension='html', suffix='null'
1941 TIMER_START{ServletResolution}
1943 TIMER_START{resolveServlet(/apps/acs-commons/content/redirect-manager/jcr:content)}
2604 TIMER_END{660,resolveServlet(/apps/acs-commons/content/redirect-manager/jcr:content)} Using servlet com.adobe.aem.wcm.site.manager.internal.servlets.ImportSiteTemplateServlet
2606 TIMER_END{665,ServletResolution} URI=/apps/acs-commons/content/redirect-manager/jcr:content.import.html handled by Servlet=com.adobe.aem.wcm.site.manager.internal.servlets.ImportSiteTemplateServlet

Steps to Reproduce
Just choose Excel file to upload and try to submit the form. Then check this request in Recent Request page http://localhost:4502/system/console/requests

@myslinskipawel There is currently a product issue which is preventing the upload for the Redirect Manager. It will be fixed with the next public SDK.

Hi @bpauli,  Do you happen to know if this will be fixed with the 5.2.1 SDK or some kind of ETA?

The upload is working fine in the latest 2022.3.6698.20220318T233218Z-220400 and AEM 6.5.12.
I believe this ticket can be closed.

Agreed.  This can be closed


Persistent custom icon set (like the core ones)

Can anybody tell me, if there is a description on how to store a custom icon font pack persistent (on a selfhosted environment)?
Just as the core fonts like fontawesome, fontelico etc, so that the font is always present and can be downloaded/chosen from.
So basically, which steps do I need to do the same as the fontello team does, after receiving a font recommendation to add the font to the fontello installation.

https://github.com/fontello/fontello/blob/master/Makefile#L35 start from this point

Clone one of existing font repo and modify it for your needs. See Makefile in it.
Add front to support/src folder
Update font list
run make rebuild

In short - there are no easy way to change persistent fonts without programming skills.


LineSeries onMouseOver not responding.

OnMouseOver not triggered (: while hovering)when used inside LineSeries However, it is triggered as part of onClick event.
 <LineSeries
                key={entry.title}
                data={entry.data}
                color={entry.color}
                onSeriesMouseOver={(event) => {
                  console.log('onSeriesMouseOver called')
                }}
              />

Also facing issues populating Hint value.

@deepakrocks there a number of issues that might be at play here, but maybe take a look here #919?

I'm closing this as I think the above referenced PR addresses this? Feel free to reopen or ask more questions under the fold


The SSL connection could not be established (RevocationStatusUnknown or altered verification) when download symbols from HTTPS source

I always got the following errors when I try to download symbols  from our https server under windows 11 enterprise OS, and this https server link is directly accessible from browser:
error 1:
Error: The SSL connection could not be established, see inner exception.
Authentication failed, see inner exception.
The message or signature supplied for verification has been altered

error2:
Error: The SSL connection could not be established, see inner exception.
The remote certificate is invalid because of errors in the certificate chain: RevocationStatusUnknown

The error is sometimes like error1, sometimes like error2. I checked the license for this https server link is under TLS1.2, and I also changed the regedit value to disable protocol SSL 3.0, TLS 1.0 and TLS 1.1, and only keep TLS 1.2 enabled. But it's still not working, I also checked the issue #7618 and #3274, which might be related to this issue, but there is no clue with my scenario, still no option to turn CRL validation off, and I am not able to change any config in the BC server side.
Could anyone can help me with it? Appreciate a lot in advance!
Versions:

AL Extension: 12.0.875970
VS Code: 1.88.1
OS: win 11 enterprise 22H2

Hi, this issue is out of scope of for this repository. You should do one of the following:

Open a support request to CSS through the PartnerSource portal
Open a bug in Collaborate
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

As a reminder, this repository only handles issues to do with the compiler or VSCode development experience for AL.


non-visible GUIs still capture input

I'm looking into this as it becomes extra problematic with collapsed folders.
I'm in the process of checking in a change that I believe is correct in fixing the bug, although at present it means extra work is done to generate a list of visible hitscan objects and I don't (yet) do any caching of that.  The extra expense may or may not be trivial, I suspect there could be some implications to garbage generated, which is not what anyone wants in a VR application.
Should be fairly easy to add the caching, but I'd rather do it in a way that avoided too much extra responsibility on the part of individual controllers.

I did notice this got fixed during testing. Great work!


sfsu crashes when there are files in the scoop buckets folder

Describe the bug
scoop search panics when there are files in scoop/buckets/ which are not in a sub-folder
To Reproduce
Steps to reproduce the behavior:

install scoop and set up sfsu
update scoop buckets
create a file in %USERPROFILE%/scoop/buckets/
run sfsu search test

Expected behavior
sfsu skips over files not in subfolders or provides a clearer error message
Full Output
thread '<unnamed>thread '' panicked at '<unnamed>called `Result::unwrap()` on an `Err` value: Os { code: 267, kind: NotADirectory, message: "The directory name is invalid." }' panicked at '', called `Result::unwrap()` on an `Err` value: Os { code: 267, kind: NotADirectory, message: "The directory name is invalid." }src\commands\search.rs', :src\commands\search.rs133::13322:

Version [e.g. 1.4.0]
sfsu 1.4.13

Why would you want to have loose files in the buckets directory?
It isn't part of the official scoop spec, so I never added support for it.

I created them by accident and it took me a bit to figure out what was happening because the error message are a bit generic, no file path or anything

I'll add a nicer error message when I get the chance.
Thanks for the issue


[contracts] feat: Implement Merkle Airdrop Support for Initial Token Distribution

Issue: Implement Merkle Airdrop Support for Initial Token Distribution
Description
This issue aims to implement Merkle airdrop support for the initial distribution of tokens in the Unruggable Memecoin project. This feature will enable users to claim their allocated tokens by submitting a Merkle proof, verifying their inclusion in the eligibility Merkle tree. The Merkle root for the airdrop eligibility will be provided during the deployment of the token.
Requirements

Merkle Root Integration: Include a parameter for the Merkle root in the token deployment process, representing the root of the airdrop eligibility tree.
Claim Function: Develop a smart contract function that allows users to claim their tokens by submitting a valid Merkle proof.
Verification Process: Implement a verification mechanism in the contract to check the submitted Merkle proof against the stored Merkle root.
Efficient Claiming Process: Optimize the claiming process to be gas-efficient and user-friendly.

Implementation Notes

Ensure the accuracy and security of the Merkle proof verification process.
The Merkle root should be immutable post-deployment to maintain the integrity of the airdrop.
Provide clear documentation and examples on how users can generate and submit their Merkle proofs.
Thoroughly test the claim functionality to handle various cases, including invalid proofs or attempts to claim more than once.

Hey @abdelhamidbakhta I would like to take this issue could you assign this to me.
Thanks

Hey @abdelhamidbakhta I would like to take this issue could you assign this to me. Thanks

great, assigned to you

Hey @abdelhamidbakhta I would like to take this issue could you assign this to me. Thanks

great, assigned to you

Thank you

Hey, Is it closed? Otherwise I can work on it

Also curious if this issue is still open, can tackle it if so.


Dataset Viewer issue for allenai/scirepeval

Link
https://huggingface.co/datasets/allenai/scirepeval
Description
The dataset viewer is not working for dataset allenai/scirepeval.
Error details:
Error code:   ResponseNotReady

Thanks for your patience. The jobs queue was under pressure; the dataset viewer is now working.


New package: ItuRjl v0.1.1

Registering package: ItuRjl
Repository: https://github.com/HillaryKchao/ItuRjl.jl
Created by: @HillaryKchao
Version: v0.1.1
Commit: 01f3535f16f8d42e4dfa1b6fd89a68f5d37787e5
Git reference: master
Description: A Julia implementation of the ITU-Recommendations for space links covering cloud, gaseous, rain, and scintillation attenuations.
Release notes:

v0.1.1 for studying impact due to climate change.

I received this message when trying to merge my commit to general:

I was not able to load the package (i.e. import ItuRjl failed). See the CI logs for details.

My initial thought was that my package name did not match my main module name, so I changed that, but the same test still did not pass. Any insight to what I would need to do to fix this would be much appreciated. Thank you!

Can you import the package yourself locally? This is what I get:
(@v1.7) pkg> activate --temp
  Activating new project at `/tmp/jl_waNdg2`

(jl_waNdg2) pkg> add https://github.com/HillaryKchao/ItuRjl.jl.git
     Cloning git-repo `https://github.com/HillaryKchao/ItuRjl.jl.git`
    Updating git-repo `https://github.com/HillaryKchao/ItuRjl.jl.git`
    Updating registry at `/tmp/foo29/registries/General.toml`
   Resolving package versions...
    Updating `/tmp/jl_waNdg2/Project.toml`
  [ec3d9ab2] + ItuRjl v0.1.1 `https://github.com/HillaryKchao/ItuRjl.jl.git#master`
    Updating `/tmp/jl_waNdg2/Manifest.toml`
  [ec3d9ab2] + ItuRjl v0.1.1 `https://github.com/HillaryKchao/ItuRjl.jl.git#master`
Precompiling project...
  ✗ ItuRjl
  0 dependencies successfully precompiled in 1 seconds
  1 dependency errored.
Stacktrace:
 [1] error(s::String)
   @ Base ./error.jl:33
 [2] compilecache(pkg::Base.PkgId, path::String, internal_stderr::IO, internal_stdout::IO, ignore_loaded_modules::Bool)
   @ Base ./loading.jl:1466
 [3] compilecache(pkg::Base.PkgId, path::String)
   @ Base ./loading.jl:1410
 [4] _require(pkg::Base.PkgId)
   @ Base ./loading.jl:1120
 [5] require(uuidkey::Base.PkgId)
   @ Base ./loading.jl:1013
 [6] require(into::Module, mod::Symbol)
   @ Base ./loading.jl:997

From the backtrace it seems like something goes bad with the read! at iturP840.jl:24. A size mismatch?
Regarding the package name, as an outsider ITURecommendations would make a lot more sense to me than ItuRjl.

Thank you! I'm going to remake the package with a new name and clean up some small errors then reupload it; hopefully, that will fix the issue.


2021-03-26T22:58:55.1280777Z
2021-03-26T22:58:55.1281126Z             # test that "machines" is actually respected by creating a socket that uses
2021-03-26T22:58:55.1281560Z             # one of the ports mentioned in "machines"
2021-03-26T22:58:55.1281955Z             error_msg = "Binding port %s failed" % open_ports[0]
2021-03-26T22:58:55.1282409Z             with pytest.raises(lgb.basic.LightGBMError, match=error_msg):
2021-03-26T22:58:55.1282897Z                 with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s:
2021-03-26T22:58:55.1283522Z                     s.bind(('<IP_ADDRESS>', open_ports[0]))
2021-03-26T22:58:55.1283930Z >                   dask_model.fit(dX, dy, group=dg)
2021-03-26T22:58:55.1284535Z E                   Failed: DID NOT RAISE <class 'lightgbm.basic.LightGBMError'>
2021-03-26T22:58:55.1284881Z
2021-03-26T22:58:55.1285208Z ../tests/python_package_test/test_dask.py:1098: Failed
2021-03-26T22:58:55.1285799Z ----------------------------- Captured stdout call -----------------------------
2021-03-26T22:58:55.1286458Z Using passed-in 'machines' parameter
2021-03-26T22:58:55.1286873Z [LightGBM] [Info] Local rank: 0, total number of machines: 1
2021-03-26T22:58:55.1287324Z [LightGBM] [Info] Local rank: 0, total number of machines: 1
2021-03-26T22:58:55.1288005Z [LightGBM] [Warning] num_threads is set=2, n_jobs=-1 will be ignored. Current value: num_threads=2
2021-03-26T22:58:55.1288778Z [LightGBM] [Warning] num_threads is set=2, n_jobs=-1 will be ignored. Current value: num_threads=2
2021-03-26T22:58:55.1289309Z =============================== warnings summary ===============================
2021-03-26T22:58:55.1289734Z tests/python_package_test/test_basic.py::test_basic
2021-03-26T22:58:55.1290141Z tests/python_package_test/test_engine.py::test_reference_chain
2021-03-26T22:58:55.1290555Z tests/python_package_test/test_engine.py::test_init_with_subset
2021-03-26T22:58:55.1290967Z tests/python_package_test/test_engine.py::test_fpreproc
2021-03-26T22:58:55.1291394Z tests/python_package_test/test_engine.py::test_dataset_params_with_reference
2021-03-26T22:58:55.1292182Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:1433: UserWarning: Overriding the parameters from Reference Dataset.
2021-03-26T22:58:55.1292900Z     _log_warning('Overriding the parameters from Reference Dataset.')
2021-03-26T22:58:55.1293171Z
2021-03-26T22:58:55.1293540Z tests/python_package_test/test_basic.py::test_add_features_equal_data_on_alternating_used_unused
2021-03-26T22:58:55.1294039Z tests/python_package_test/test_basic.py::test_add_features_same_booster_behaviour
2021-03-26T22:58:55.1294484Z tests/python_package_test/test_engine.py::test_sliced_data
2021-03-26T22:58:55.1294911Z tests/python_package_test/test_engine.py::test_monotone_penalty_max
2021-03-26T22:58:55.1295325Z tests/python_package_test/test_engine.py::test_forced_bins
2021-03-26T22:58:55.1296216Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:448: UserWarning: Usage of np.ndarray subset (sliced data) is not recommended due to it will double the peak memory cost in LightGBM.
2021-03-26T22:58:55.1296907Z     _log_warning("Usage of np.ndarray subset (sliced data) is not recommended "
2021-03-26T22:58:55.1297185Z
2021-03-26T22:58:55.1297547Z tests/python_package_test/test_basic.py::test_add_features_equal_data_on_alternating_used_unused
2021-03-26T22:58:55.1298047Z tests/python_package_test/test_basic.py::test_add_features_same_booster_behaviour
2021-03-26T22:58:55.1298521Z tests/python_package_test/test_basic.py::test_add_features_from_different_sources
2021-03-26T22:58:55.1299384Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:2129: UserWarning: Cannot add features from NoneType type of raw data to NoneType type of raw data.
2021-03-26T22:58:55.1299987Z   Set free_raw_data=False when construct Dataset to avoid this
2021-03-26T22:58:55.1300337Z     _log_warning(err_msg)
2021-03-26T22:58:55.1300531Z
2021-03-26T22:58:55.1300888Z tests/python_package_test/test_basic.py::test_add_features_equal_data_on_alternating_used_unused
2021-03-26T22:58:55.1301449Z tests/python_package_test/test_basic.py::test_add_features_same_booster_behaviour
2021-03-26T22:58:55.1301925Z tests/python_package_test/test_basic.py::test_add_features_from_different_sources
2021-03-26T22:58:55.1302872Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:2131: UserWarning: Reseting categorical features.
2021-03-26T22:58:55.1303457Z   You can set new categorical features via ``set_categorical_feature`` method
2021-03-26T22:58:55.1303865Z     _log_warning("Reseting categorical features.\n"
2021-03-26T22:58:55.1304099Z
2021-03-26T22:58:55.1304433Z tests/python_package_test/test_basic.py::test_add_features_from_different_sources
2021-03-26T22:58:55.1305402Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:2129: UserWarning: Cannot add features from list type of raw data to ndarray type of raw data.
2021-03-26T22:58:55.1305949Z   Freeing raw data
2021-03-26T22:58:55.1306253Z     _log_warning(err_msg)
2021-03-26T22:58:55.1306434Z
2021-03-26T22:58:55.1306793Z tests/python_package_test/test_basic.py::test_add_features_from_different_sources
2021-03-26T22:58:55.1307725Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:2129: UserWarning: Cannot add features from list type of raw data to csr_matrix type of raw data.
2021-03-26T22:58:55.1308280Z   Freeing raw data
2021-03-26T22:58:55.1308580Z     _log_warning(err_msg)
2021-03-26T22:58:55.1308756Z
2021-03-26T22:58:55.1309105Z tests/python_package_test/test_basic.py::test_add_features_from_different_sources
2021-03-26T22:58:55.1309949Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:2129: UserWarning: Cannot add features from list type of raw data to DataFrame type of raw data.
2021-03-26T22:58:55.1310487Z   Freeing raw data
2021-03-26T22:58:55.1310772Z     _log_warning(err_msg)
2021-03-26T22:58:55.1310961Z
2021-03-26T22:58:55.1311279Z tests/python_package_test/test_consistency.py: 10 warnings
2021-03-26T22:58:55.1312067Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/engine.py:148: UserWarning: Found `num_trees` in params. Will use it instead of argument
2021-03-26T22:58:55.1312677Z     _log_warning("Found `{}` in params. Will use it instead of argument".format(alias))
2021-03-26T22:58:55.1312943Z
2021-03-26T22:58:55.1313269Z tests/python_package_test/test_consistency.py: 10 warnings
2021-03-26T22:58:55.1314058Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:1222: UserWarning: data keyword has been found in `params` and will be ignored.
2021-03-26T22:58:55.1314658Z   Please use data argument of the Dataset constructor to pass this parameter.
2021-03-26T22:58:55.1315279Z     _log_warning('{0} keyword has been found in `params` and will be ignored.\n'
2021-03-26T22:58:55.1315562Z
2021-03-26T22:58:55.1315878Z tests/python_package_test/test_dask.py: 173 warnings
2021-03-26T22:58:55.1316588Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/dask.py:285: UserWarning: Parameter n_jobs will be ignored.
2021-03-26T22:58:55.1317122Z     _log_warning(f"Parameter {param_alias} will be ignored.")
2021-03-26T22:58:55.1317360Z
2021-03-26T22:58:55.1317705Z tests/python_package_test/test_dask.py::test_training_does_not_fail_on_port_conflicts
2021-03-26T22:58:55.1318185Z tests/python_package_test/test_dask.py::test_training_does_not_fail_on_port_conflicts
2021-03-26T22:58:55.1318657Z tests/python_package_test/test_dask.py::test_training_does_not_fail_on_port_conflicts
2021-03-26T22:58:55.1319131Z tests/python_package_test/test_dask.py::test_training_does_not_fail_on_port_conflicts
2021-03-26T22:58:55.1319895Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/dask.py:285: UserWarning: Parameter num_threads will be ignored.
2021-03-26T22:58:55.1320430Z     _log_warning(f"Parameter {param_alias} will be ignored.")
2021-03-26T22:58:55.1320735Z
2021-03-26T22:58:55.1321399Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[True-binary-classification-pickle]
2021-03-26T22:58:55.1322312Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1322843Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1323212Z   Hosting the HTTP server on port 37203 instead
2021-03-26T22:58:55.1323534Z     warnings.warn(
2021-03-26T22:58:55.1323716Z
2021-03-26T22:58:55.1324375Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[True-binary-classification-joblib]
2021-03-26T22:58:55.1325345Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1325878Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1326247Z   Hosting the HTTP server on port 33305 instead
2021-03-26T22:58:55.1326566Z     warnings.warn(
2021-03-26T22:58:55.1326749Z
2021-03-26T22:58:55.1327438Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[True-binary-classification-cloudpickle]
2021-03-26T22:58:55.1328332Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1328866Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1329234Z   Hosting the HTTP server on port 43253 instead
2021-03-26T22:58:55.1329566Z     warnings.warn(
2021-03-26T22:58:55.1329738Z
2021-03-26T22:58:55.1330426Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[True-multiclass-classification-pickle]
2021-03-26T22:58:55.1331333Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1331851Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1332218Z   Hosting the HTTP server on port 44841 instead
2021-03-26T22:58:55.1332549Z     warnings.warn(
2021-03-26T22:58:55.1332719Z
2021-03-26T22:58:55.1333394Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[True-multiclass-classification-joblib]
2021-03-26T22:58:55.1334303Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1334836Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1335193Z   Hosting the HTTP server on port 32785 instead
2021-03-26T22:58:55.1335527Z     warnings.warn(
2021-03-26T22:58:55.1335694Z
2021-03-26T22:58:55.1336377Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[True-multiclass-classification-cloudpickle]
2021-03-26T22:58:55.1337296Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1337855Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1338216Z   Hosting the HTTP server on port 34245 instead
2021-03-26T22:58:55.1338544Z     warnings.warn(
2021-03-26T22:58:55.1338723Z
2021-03-26T22:58:55.1339364Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[True-regression-pickle]
2021-03-26T22:58:55.1340252Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1340783Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1341148Z   Hosting the HTTP server on port 45953 instead
2021-03-26T22:58:55.1341547Z     warnings.warn(
2021-03-26T22:58:55.1341731Z
2021-03-26T22:58:55.1342375Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[True-regression-joblib]
2021-03-26T22:58:55.1343482Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1344011Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1344377Z   Hosting the HTTP server on port 45391 instead
2021-03-26T22:58:55.1344690Z     warnings.warn(
2021-03-26T22:58:55.1344874Z
2021-03-26T22:58:55.1345539Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[True-regression-cloudpickle]
2021-03-26T22:58:55.1346502Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1347042Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1347434Z   Hosting the HTTP server on port 42285 instead
2021-03-26T22:58:55.1347772Z     warnings.warn(
2021-03-26T22:58:55.1347941Z
2021-03-26T22:58:55.1348590Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[True-ranking-pickle]
2021-03-26T22:58:55.1349452Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1349982Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1350393Z   Hosting the HTTP server on port 37475 instead
2021-03-26T22:58:55.1350731Z     warnings.warn(
2021-03-26T22:58:55.1350897Z
2021-03-26T22:58:55.1351542Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[True-ranking-joblib]
2021-03-26T22:58:55.1352420Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1352934Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1353298Z   Hosting the HTTP server on port 37689 instead
2021-03-26T22:58:55.1353623Z     warnings.warn(
2021-03-26T22:58:55.1353794Z
2021-03-26T22:58:55.1354445Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[True-ranking-cloudpickle]
2021-03-26T22:58:55.1355331Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1355862Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1356214Z   Hosting the HTTP server on port 33847 instead
2021-03-26T22:58:55.1356542Z     warnings.warn(
2021-03-26T22:58:55.1356740Z
2021-03-26T22:58:55.1357411Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[False-binary-classification-pickle]
2021-03-26T22:58:55.1358316Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1358840Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1359206Z   Hosting the HTTP server on port 36535 instead
2021-03-26T22:58:55.1359520Z     warnings.warn(
2021-03-26T22:58:55.1359702Z
2021-03-26T22:58:55.1360365Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[False-binary-classification-joblib]
2021-03-26T22:58:55.1361268Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1361804Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1362169Z   Hosting the HTTP server on port 36923 instead
2021-03-26T22:58:55.1362593Z     warnings.warn(
2021-03-26T22:58:55.1362834Z
2021-03-26T22:58:55.1363509Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[False-binary-classification-cloudpickle]
2021-03-26T22:58:55.1364417Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1364942Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1365303Z   Hosting the HTTP server on port 45309 instead
2021-03-26T22:58:55.1365634Z     warnings.warn(
2021-03-26T22:58:55.1365802Z
2021-03-26T22:58:55.1366462Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[False-multiclass-classification-pickle]
2021-03-26T22:58:55.1367415Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1367950Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1368319Z   Hosting the HTTP server on port 41641 instead
2021-03-26T22:58:55.1368651Z     warnings.warn(
2021-03-26T22:58:55.1368825Z
2021-03-26T22:58:55.1369509Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[False-multiclass-classification-joblib]
2021-03-26T22:58:55.1370414Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1370918Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1371276Z   Hosting the HTTP server on port 44095 instead
2021-03-26T22:58:55.1371603Z     warnings.warn(
2021-03-26T22:58:55.1371763Z
2021-03-26T22:58:55.1372439Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[False-multiclass-classification-cloudpickle]
2021-03-26T22:58:55.1373322Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1373851Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1374203Z   Hosting the HTTP server on port 45179 instead
2021-03-26T22:58:55.1374533Z     warnings.warn(
2021-03-26T22:58:55.1374702Z
2021-03-26T22:58:55.1375361Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[False-regression-pickle]
2021-03-26T22:58:55.1376241Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1376772Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1377121Z   Hosting the HTTP server on port 41487 instead
2021-03-26T22:58:55.1377450Z     warnings.warn(
2021-03-26T22:58:55.1377630Z
2021-03-26T22:58:55.1378284Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[False-regression-joblib]
2021-03-26T22:58:55.1379209Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1379735Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1380100Z   Hosting the HTTP server on port 37289 instead
2021-03-26T22:58:55.1380417Z     warnings.warn(
2021-03-26T22:58:55.1380599Z
2021-03-26T22:58:55.1381247Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[False-regression-cloudpickle]
2021-03-26T22:58:55.1382137Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1382809Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1383195Z   Hosting the HTTP server on port 38679 instead
2021-03-26T22:58:55.1383623Z     warnings.warn(
2021-03-26T22:58:55.1383793Z
2021-03-26T22:58:55.1384462Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[False-ranking-pickle]
2021-03-26T22:58:55.1385328Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1385855Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1386219Z   Hosting the HTTP server on port 34439 instead
2021-03-26T22:58:55.1386545Z     warnings.warn(
2021-03-26T22:58:55.1386714Z
2021-03-26T22:58:55.1387360Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[False-ranking-joblib]
2021-03-26T22:58:55.1388317Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1388837Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1389200Z   Hosting the HTTP server on port 40549 instead
2021-03-26T22:58:55.1389531Z     warnings.warn(
2021-03-26T22:58:55.1389697Z
2021-03-26T22:58:55.1390344Z tests/python_package_test/test_dask.py::test_model_and_local_version_are_picklable_whether_or_not_client_set_explicitly[False-ranking-cloudpickle]
2021-03-26T22:58:55.1391231Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/node.py:151: UserWarning: Port 8787 is already in use.
2021-03-26T22:58:55.1391754Z   Perhaps you already have a cluster running?
2021-03-26T22:58:55.1392102Z   Hosting the HTTP server on port 40215 instead
2021-03-26T22:58:55.1392433Z     warnings.warn(
2021-03-26T22:58:55.1392601Z
2021-03-26T22:58:55.1392915Z tests/python_package_test/test_dask.py::test_errors
2021-03-26T22:58:55.1393648Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/dask.py:312: RuntimeWarning: coroutine '_wait' was never awaited
2021-03-26T22:58:55.1394129Z     wait(parts)
2021-03-26T22:58:55.1394296Z
2021-03-26T22:58:55.1394611Z tests/python_package_test/test_dask.py::test_errors
2021-03-26T22:58:55.1395485Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/distributed/utils_test.py:939: RuntimeWarning: coroutine 'PooledRPCCall.__getattr__.<locals>.send_recv_from_rpc' was never awaited
2021-03-26T22:58:55.1396065Z     gc.collect()
2021-03-26T22:58:55.1396244Z
2021-03-26T22:58:55.1396548Z tests/python_package_test/test_engine.py::test_binary
2021-03-26T22:58:55.1397343Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/engine.py:148: UserWarning: Found `num_iteration` in params. Will use it instead of argument
2021-03-26T22:58:55.1397957Z     _log_warning("Found `{}` in params. Will use it instead of argument".format(alias))
2021-03-26T22:58:55.1398224Z
2021-03-26T22:58:55.1398556Z tests/python_package_test/test_engine.py::test_pandas_categorical
2021-03-26T22:58:55.1398978Z tests/python_package_test/test_engine.py::test_linear_trees
2021-03-26T22:58:55.1399392Z tests/python_package_test/test_engine.py::test_save_and_load_linear
2021-03-26T22:58:55.1400168Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:1705: UserWarning: categorical_feature in Dataset is overridden.
2021-03-26T22:58:55.1400676Z   New categorical_feature is [0]
2021-03-26T22:58:55.1401212Z     _log_warning('categorical_feature in Dataset is overridden.\n'
2021-03-26T22:58:55.1401463Z
2021-03-26T22:58:55.1401797Z tests/python_package_test/test_engine.py::test_pandas_categorical
2021-03-26T22:58:55.1402554Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:1705: UserWarning: categorical_feature in Dataset is overridden.
2021-03-26T22:58:55.1403174Z   New categorical_feature is ['A']
2021-03-26T22:58:55.1403715Z     _log_warning('categorical_feature in Dataset is overridden.\n'
2021-03-26T22:58:55.1404054Z
2021-03-26T22:58:55.1404368Z tests/python_package_test/test_engine.py::test_pandas_categorical
2021-03-26T22:58:55.1405113Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:1705: UserWarning: categorical_feature in Dataset is overridden.
2021-03-26T22:58:55.1405775Z   New categorical_feature is ['A', 'B', 'C', 'D']
2021-03-26T22:58:55.1406329Z     _log_warning('categorical_feature in Dataset is overridden.\n'
2021-03-26T22:58:55.1406566Z
2021-03-26T22:58:55.1406889Z tests/python_package_test/test_engine.py::test_pandas_categorical
2021-03-26T22:58:55.1407610Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:1705: UserWarning: categorical_feature in Dataset is overridden.
2021-03-26T22:58:55.1408345Z   New categorical_feature is ['A', 'B', 'C', 'D', 'E']
2021-03-26T22:58:55.1408908Z     _log_warning('categorical_feature in Dataset is overridden.\n'
2021-03-26T22:58:55.1409145Z
2021-03-26T22:58:55.1409469Z tests/python_package_test/test_engine.py::test_pandas_categorical
2021-03-26T22:58:55.1410203Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:1705: UserWarning: categorical_feature in Dataset is overridden.
2021-03-26T22:58:55.1410683Z   New categorical_feature is []
2021-03-26T22:58:55.1411188Z     _log_warning('categorical_feature in Dataset is overridden.\n'
2021-03-26T22:58:55.1411440Z
2021-03-26T22:58:55.1411745Z tests/python_package_test/test_engine.py::test_pandas_sparse
2021-03-26T22:58:55.1412147Z tests/python_package_test/test_sklearn.py::test_pandas_sparse
2021-03-26T22:58:55.1413093Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/pandas/core/generic.py:5673: PerformanceWarning: Concatenating sparse arrays with multiple fill values: '[0, nan, False]'. Picking the first and converting the rest.
2021-03-26T22:58:55.1413789Z     return self._mgr.as_array(transpose=self._AXIS_REVERSED)
2021-03-26T22:58:55.1414015Z
2021-03-26T22:58:55.1414356Z tests/python_package_test/test_engine.py::test_int32_max_sparse_contribs
2021-03-26T22:58:55.1415278Z   /home/AzDevOps_azpcontainer/miniconda/envs/test-env/lib/python3.8/site-packages/scipy/sparse/_index.py:82: SparseEfficiencyWarning: Changing the sparsity structure of a csr_matrix is expensive. lil_matrix is more efficient.
2021-03-26T22:58:55.1415883Z     self._set_intXint(row, col, x.flat[0])
2021-03-26T22:58:55.1416079Z
2021-03-26T22:58:55.1416377Z tests/python_package_test/test_engine.py::test_init_with_subset
2021-03-26T22:58:55.1417098Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:1959: UserWarning: Cannot subset str type of raw data.
2021-03-26T22:58:55.1417552Z   Returning original raw data
2021-03-26T22:58:55.1417892Z     _log_warning("Cannot subset {} type of raw data.\n"
2021-03-26T22:58:55.1418117Z
2021-03-26T22:58:55.1418424Z tests/python_package_test/test_engine.py::test_monotone_constraints
2021-03-26T22:58:55.1418834Z tests/python_package_test/test_engine.py::test_monotone_penalty
2021-03-26T22:58:55.1419308Z tests/python_package_test/test_engine.py::test_monotone_penalty_max
2021-03-26T22:58:55.1419721Z tests/python_package_test/test_engine.py::test_get_split_value_histogram
2021-03-26T22:58:55.1420144Z tests/python_package_test/test_sklearn.py::test_pandas_categorical
2021-03-26T22:58:55.1420561Z tests/python_package_test/test_sklearn.py::test_pandas_categorical
2021-03-26T22:58:55.1420976Z tests/python_package_test/test_sklearn.py::test_pandas_categorical
2021-03-26T22:58:55.1421373Z tests/python_package_test/test_sklearn.py::test_pandas_categorical
2021-03-26T22:58:55.1421781Z tests/python_package_test/test_sklearn.py::test_pandas_categorical
2021-03-26T22:58:55.1422524Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:1702: UserWarning: Using categorical_feature in Dataset.
2021-03-26T22:58:55.1423406Z     _log_warning('Using categorical_feature in Dataset.')
2021-03-26T22:58:55.1423637Z
2021-03-26T22:58:55.1423968Z tests/python_package_test/test_engine.py::test_dataset_update_params
2021-03-26T22:58:55.1424899Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:1222: UserWarning: categorical_feature keyword has been found in `params` and will be ignored.
2021-03-26T22:58:55.1425520Z   Please use categorical_feature argument of the Dataset constructor to pass this parameter.
2021-03-26T22:58:55.1426173Z     _log_warning('{0} keyword has been found in `params` and will be ignored.\n'
2021-03-26T22:58:55.1426453Z
2021-03-26T22:58:55.1426773Z tests/python_package_test/test_plotting.py::test_plot_metrics
2021-03-26T22:58:55.1427558Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/plotting.py:328: UserWarning: More than one metric available, picking one to plot.
2021-03-26T22:58:55.1428202Z     _log_warning("More than one metric available, picking one to plot.")
2021-03-26T22:58:55.1428447Z
2021-03-26T22:58:55.1428817Z tests/python_package_test/test_sklearn.py::test_binary_classification_with_custom_objective
2021-03-26T22:58:55.1429741Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/sklearn.py:922: UserWarning: Cannot compute class probabilities or labels due to the usage of customized objective function.
2021-03-26T22:58:55.1430322Z   Returning raw scores instead.
2021-03-26T22:58:55.1430677Z     _log_warning("Cannot compute class probabilities or labels "
2021-03-26T22:58:55.1430922Z
2021-03-26T22:58:55.1431227Z tests/python_package_test/test_sklearn.py: 12 warnings
2021-03-26T22:58:55.1431967Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/basic.py:739: UserWarning: Converting data to scipy sparse matrix.
2021-03-26T22:58:55.1432656Z     _log_warning('Converting data to scipy sparse matrix.')
2021-03-26T22:58:55.1432897Z
2021-03-26T22:58:55.1433235Z tests/python_package_test/test_utilities.py::test_register_logger
2021-03-26T22:58:55.1434135Z   /home/AzDevOps_azpcontainer/.local/lib/python3.8/site-packages/lightgbm/plotting.py:357: UserWarning: Attempting to set identical bottom == top == 1.0 results in singular transformations; automatically expanding.
2021-03-26T22:58:55.1434720Z     ax.set_ylim(ylim)
2021-03-26T22:58:55.1434898Z
2021-03-26T22:58:55.1435376Z -- Docs: https://docs.pytest.org/en/stable/warnings.html
2021-03-26T22:58:55.1435822Z =========================== short test summary info ============================
2021-03-26T22:58:55.1436513Z FAILED ../tests/python_package_test/test_dask.py::test_classifier[binary-classification-dataframe-with-categorical]
2021-03-26T22:58:55.1437294Z FAILED ../tests/python_package_test/test_dask.py::test_classifier[multiclass-classification-dataframe-with-categorical]
2021-03-26T22:58:55.1437831Z FAILED ../tests/python_package_test/test_dask.py::test_regressor[scipy_csr_matrix]
2021-03-26T22:58:55.1438502Z FAILED ../tests/python_package_test/test_dask.py::test_regressor[dataframe-with-categorical]
2021-03-26T22:58:55.1439237Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[array-binary-classification]
2021-03-26T22:58:55.1440037Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[array-multiclass-classification]
2021-03-26T22:58:55.1440817Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[array-regression]
2021-03-26T22:58:55.1441557Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[array-ranking]
2021-03-26T22:58:55.1442339Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[scipy_csr_matrix-binary-classification]
2021-03-26T22:58:55.1443149Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[scipy_csr_matrix-multiclass-classification]
2021-03-26T22:58:55.1443951Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[scipy_csr_matrix-regression]
2021-03-26T22:58:55.1444743Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[dataframe-binary-classification]
2021-03-26T22:58:55.1445636Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[dataframe-multiclass-classification]
2021-03-26T22:58:55.1446417Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[dataframe-regression]
2021-03-26T22:58:55.1447157Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[dataframe-ranking]
2021-03-26T22:58:55.1447998Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[dataframe-with-categorical-binary-classification]
2021-03-26T22:58:55.1448857Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[dataframe-with-categorical-multiclass-classification]
2021-03-26T22:58:55.1449765Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[dataframe-with-categorical-regression]
2021-03-26T22:58:55.1450578Z FAILED ../tests/python_package_test/test_dask.py::test_machines_should_be_used_if_provided[dataframe-with-categorical-ranking]
2021-03-26T22:58:55.1451151Z = 19 failed, 367 passed, 7 skipped, 2 xfailed, 279 warnings in 665.52s (0:11:05) =
2021-03-26T22:58:55.6498638Z ##[error]Bash exited with code '255'.
2021-03-26T22:58:55.6555869Z ##[section]Finishing: Test

I guess that first 4 failures are quite easy to "fix" by slightly relaxing the asserting accuracy, e.g.
a = 0.998, b = 1.0, check_shape = True, check_graph = True, check_meta = True
check_chunks = True, kwargs = {}, a_original = 0.998, b_original = 1.0
adt = dtype('float64'), a_meta = None, a_computed = None, bdt = dtype('float64')
b_meta = None

or

a = 0.9631152654080015, b = 0.9769588528806643, check_shape = True
check_graph = True, check_meta = True, check_chunks = True
kwargs = {'atol': 0.01}, a_original = 0.9631152654080015
b_original = 0.9769588528806643, adt = dtype('float64'), a_meta = None
a_computed = None, bdt = dtype('float64'), b_meta = None

Also, sometimes test_dask.py::test_regressor[array] is failing for the same reason.
All other failures (all parametrized variants of test_machines_should_be_used_if_provided) are expected I believe due to socket vs MPI underlying differences.

Hi, I am looking for the lightgbm.dask support for the MPI version for the following reasons:

Application: hyperparameter optimization, where multiple lgbm.fit() calls are submitted, either sequentially/parallel

Sockets don't work for two reasons: 1) Currently, for each trial the socket version starts looking for random ports for each worker, however due to security concerns, a node cannot open any random port; 2) the amount of open ports on my system is limited, so I need to limit the number of ports used, I tried by specifying the machines parameter to use a fixed set of ports for each trial while doing multiple trials sequentially, that did not work. https://github.com/microsoft/LightGBM/issues/4960#issue-1107667816


Feature/v2 upgrade & Grouping support

Upgrade to support Serilog v2 and added custom grouping support.

@tony-haupt I've forked and modified this Sink to support v2 of Serilog and I've also added the custom group key support that you added to Raygun.Diagnostics. Can you review this implementation for comparison?

Implementation looks good.  You're binding the custom event to the RayGunClient prior to sending the message and in the event itself you're using the proper CustomGroupingKey property of the event arguments.

@tony-haupt any thoughts? I've made some changes based on my testing and the raygun samples.. I think we may want to make similar changes to Raygun.Diagnostics as well. With that said. I still can't get this to work.. no matter what I try, all of the errors are not getting grouped on Raygun. I've verified that the group is coming through, however I've not been able to debug to verify the event is actually firing. I would assume it is though. Here is my sample code... it is posting the the Adapt Bot raygun application
Log.Logger = new LoggerConfiguration()
    .MinimumLevel.Verbose()
    .WriteTo.Raygun("ht//yCo7AwRdQnVj5zjkog==", tags: new[] { "chicken", "beef", "misc"})
    .WriteTo.Console()
    .CreateLogger();

  var transaction = new { TransactionId = Guid.NewGuid()};
  var myLog = Log.ForContext("Transaction", transaction, true).ForContext("GroupKey", "mycustomkey");

  myLog.Information("This is highlevel trace information");
  myLog.Debug("This is low level diagnostic information");
  myLog.Error(new Exception("unexpected error"), "This is unexpected error information");
  myLog.Error(new Exception("expected error"), "This is expected error information");
  myLog.Error(new Exception("random error"), "This is random error information");

@tony-haupt ok, got rid of all of the event code and added new custom tags per log event. All have tested well and the code is much simpler. Here is new sample:
Log.Logger = new LoggerConfiguration()
    .MinimumLevel.Verbose()
    .WriteTo.Raygun("ht//yCo7AwRdQnVj5zjkog==", tags: new[] { "chicken", "beef"})
    .WriteTo.Console()
    .CreateLogger();

  var transaction = new { TransactionId = Guid.NewGuid()};
  var myLog = Log.ForContext("Transaction", transaction, true).ForContext("GroupKey", "mycustomkey");

  myLog.Information("This is highlevel trace information");
  myLog.Debug("This is low level diagnostic information");
  myLog.ForContext("Tags", new[] {"tag1", "tag2"}).Error(new Exception("unexpected error"), "This is unexpected error information");
  myLog.Error(new Exception("expected error"), "This is expected error information {@Tags}", new[] {"tag3", "tag4"});
  myLog.Error(new Exception("random error"), "This is random error information");


Silent Death for Windows Binaries on PyPi

I'm seeing silent death for certain scripts running windows binaries recently uploaded to PyPi (version 0.4.0 and 0.5.0). Binaries compiled from source locally on windows have no issues and neither do any linux binaries hosted on PyPi.

Unfortunately, I've narrowed it down to a recent update to the MSVC build tools that ship with visual studio and are used in the GitHub actions runners. I was able to reproduce the bad binaries when building locally with the latest version of visual studio (v10.). I don't currently think that it is anything to do with our code base, but I will investigate. In the mean-time  people building from source on windows should not update their MSVC build tools or update visual studio if everything is working right now.

Some progress on workaround. Downgrading the MSVC++ platform toolset from 14.40 to 14.29 in Github Actions results in working binaries. Also looks like this toolset can be installed side by side 14.40 locally in  visual studio by installing the extension below.

Visual studio wont use it by default, so its not a fix for local builds yet. I'll figure out how to set that up and add it to the build tutorial.

Offending windows wheels for version 0.4 and 0.5 have been removed from PyPi. Linux ones are still available. We will do a new windows release soon.

No need to downgrade tools. Looks like this issue is caused by a specific update to std::mutex in the latest version of msvcp140.dll. See link for details.
The bad builds would work fine if they were running with the latest msvcp140.dll. However anaconda and other python distros ship with older incompatible versions, hence the crashes. I can confirm that compiling our binaries with _DISABLE_CONSTEXPR_MUTEX_CONSTRUCTOR as  suggested by msft fixes the issue even when running against old dlls. That is what we will do for now.


[FLINK-19238] Arena block size sanity

This PR replaces the PR https://github.com/apache/flink/pull/13393. I'm the author of that PR, but have lost access to the GitHub account owning the branch for the PR.
Logs a WARN if the case arena block size is too high.
What is the purpose of the change
This change adds a WARN message in the case RocksDB will very likely (100% sure?) perform very poorly because of the way the managed memory is configured.
There's an associated JIRA ticket FLINK-19238.
Brief change log
RocksDBMemoryControllerUtils has new methods to calculate different values as RocksDB calculates those.
The actual logging is in RocksDBOperationUtils.sanityCheckArenaBlockSize. The arena block size is not known before this. Most of the code changes is caused by the need to pass writeBufferManagerCapacity to the check.
Verifying this change
If you run any properly performing Flink application (on a RocksDB state backend), there won't be any change caused by this PR.
If you setup a simple Flink app and run it with StreamExecutionEnvironment.createLocalEnvironment and high parallelism (let's say 16), you should see the new WARN messages
This change added tests and can be verified as follows:

RocksDBOperationsUtilsTest.testSanityCheckArenaBlockSize

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): / no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? yes/no. The only user visible change is a new WARN message. Not really a feature...
If yes, how is the feature documented? JavaDocs

Logs a WARN if the case arena block size is too high.
What is the purpose of the change
This change adds a WARN message in the case RocksDB will very likely (100% sure?) perform very poorly because of the way the managed memory is configured.
There's an associated JIRA ticket FLINK-19238.
Brief change log
RocksDBMemoryControllerUtils has new methods to calculate different values as RocksDB calculates those.
The actual logging is in RocksDBOperationUtils.sanityCheckArenaBlockSize. The arena block size is not known before this. Most of the code changes is caused by the need to pass writeBufferManagerCapacity to the check.
Verifying this change
If you run any properly performing Flink application (on a RocksDB state backend), there won't be any change caused by this PR.
If you setup a simple Flink app and run it with StreamExecutionEnvironment.createLocalEnvironment and high parallelism (let's say 16), you should see the new WARN messages
This change added tests and can be verified as follows:
RocksDBOperationsUtilsTest.testSanityCheckArenaBlockSize
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): / no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? yes/no. The only user visible change is a new WARN message. Not really a feature...
If yes, how is the feature documented? JavaDocs

Thanks for continue working on this one @anonymouscodeholic . Checking the Azure test failure it's caused by FLINK-19619 and not related to changes here. I will review the latest commits asap.
Just a heads up, that the feature freeze of 1.12.0 is approaching and let's try to get this one in before that. Thanks.

Some quick comments:
It seems the comments on the javadoc of RocksDBMemoryControllerUtils (fix on the link style) were neglected, could you double check it @anonymouscodeholic ?
And maybe also the comment on RocksDBOperationsUtilsTest, which I think could make the test case more readable.
Thanks.

Some quick comments:
It seems the comments on the javadoc of RocksDBMemoryControllerUtils (fix on the link style) were neglected, could you double check it @anonymouscodeholic ?
And maybe also the comment on RocksDBOperationsUtilsTest, which I think could make the test case more readable.
Thanks.

Hey, things got complicated, because I couldn't approve the changes in the original PR and had to hand-pick them in this PR. I think I just missed those few comments.
Just pushed the latest.

Merged master to this branch and still having strange test failures....

mvn verify
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.169 s <<< FAILURE! - in org.apache.flink.runtime.execution.librarycache.BlobLibraryCacheRecoveryITCase
[ERROR] testRecoveryRegisterAndDownload(org.apache.flink.runtime.execution.librarycache.BlobLibraryCacheRecoveryITCase)  Time elapsed: 0.169 s  <<< ERROR!
java.lang.NoSuchMethodError: 'java.lang.ClassLoader org.apache.flink.runtime.execution.librarycache.LibraryCacheManager$ClassLoaderLease.getOrResolveClassLoader(java.util.Collection, java.util.Collection)'
	at org.apache.flink.runtime.execution.librarycache.BlobLibraryCacheRecoveryITCase.testRecoveryRegisterAndDownload(BlobLibraryCacheRecoveryITCase.java:113)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at org.junit.runners.Suite.runChild(Suite.java:27)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
	at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
	at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)

Trying with mvn clean verify.... Though mvn should be clever enough to compile all that has changed.

Hey, things got complicated, because I couldn't approve the changes in the original PR and had to hand-pick them in this PR. I think I just missed those few comments.
Just pushed the latest.

No problem, thanks for the follow up actions.

Merged master to this branch and still having strange test failures....

From the CI report on Azure all tests passed with 5fed292, so I guess there might be some environment issues during your local test which is irrelative to the changes of this PR.

From the CI report on Azure all tests passed with 5fed292, so I guess there might be some environment issues during your local test which is irrelative to the changes of this PR.

Yes, I have all kinds of trouble running tests locally. Those issues seem to be unrelated to this PR.
Is there still something missing?

@Myasuka Can you have a look at this?

Sorry for late reply, I'll take a look tonight @anonymouscodeholic

Thanks for the review @Myasuka , I will resolve these minor issues when merging this PR, if no objections.

@Myasuka could you take a look at c700e3a and let me know whether it addresses your comments well? Thanks.


Introducing a --host option to allow using (n) subdomains

Fixes #31
Example usage:
$ node bin/server --port 1234 --host multi.levels.deep.mydomain.com
Client:
$ lt --port 80 --host http://multi.levels.deep.mydomain.com:1234
your url is: http://ypxwyyefij.multi.levels.deep.mydomain.com:1234

Also allows usage of sub-sub[-sub[...]] domains:
$ node bin/server --port 1234 --host levels.deep.mydomain.com
Client:
$ lt --port 80 --host http://levels.deep.mydomain.com --subdomain one.two
your url is: http://one.two.levels.deep.mydomain.com:1234

Possible usecase (my particular case): debugging of "customer specific subdomain webapps" on a developer machine running localtunnel (exampleproject.manuel.tunnelserver.company.org). tunnelserver.company.org would be the tunnel server's url and exampleproject.manuel a custom subdomain pointing to a very specific project on my machine.
Imagine you needed access to a specific team on Slack (teamname.slack.com) on a developer's local machine (teamname.manuelsmachine.slack.com) from outside via localtunnel on a company's dev domain (teamname.manuelsmachine.localtunnel.slack.com). It would be as simple as node bin/server --host localtunnel.slack.com and lt --port 80 --host http://localtunnel.slack.com --subdomain teamname.manuelsmachine
(I'm not working for Slack, just using it as example since everybody knows the pattern behind Slack's URLs)

i made docker file for this pr.
https://hub.docker.com/r/ohwhos/localtunnel-server/

im testings and works +1

is anyone still working on this PR ?

the PR works!

Looks like we're having a conflict here.

@defunctzombie will you merge an publish new version with docker image please?

@manuelbieh, please, resolve so simple conflict on empty lines, otherwise this PR will stuck for another year :man_facepalming:

@manuelbieh, you are :rocket:. Resolved in 5 minutes :+1:
@defunctzombie, now it's your turn. Please, merge this PR. One year of waiting.. It can close at least 4 issues #31, #51, #13, #40

I usually respond within 5 minutes or never 😁 😉

BTW I've made alternative implementation of this feature, some may check if needed https://github.com/localtunnel/server/pull/65

When is this feature going to be integrated?

Using this PR. I now have a new error when trying to get a tunnel
  localtunnel server listening on port: 3000 +0ms
  localtunnel:server request /?new +1m
[error]	bookrc.js:10 Assignment to constant variable.
TypeError: Assignment to constant variable.
    at maybe_bounce (server.js:59:9)
    at Server.<anonymous> (server.js:330:52)
    at emitTwo (events.js:106:13)
    at Server.emit (events.js:191:7)
    at HTTPParser.parserOnIncoming [as onIncoming] (_http_server.js:546:12)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)
TypeError: Assignment to constant variable.
    at maybe_bounce (server.js:59:9)
    at Server.<anonymous> (server.js:330:52)
    at emitTwo (events.js:106:13)
    at Server.emit (events.js:191:7)
    at HTTPParser.parserOnIncoming [as onIncoming] (_http_server.js:546:12)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:99:23)

node version : 6.9.1

@taniki try this one https://github.com/localtunnel/server/pull/65

Closing in favor of #65. Will evaluate that PR as a potential enhancement.


Exposing native overlay property from iOS picker

Changes Proposed in this pull request:
-Exposing native overlay property from iOS picker

Can you remove the DS_STORE and adjust the tab spacing and then it will be good to go.

Done. If you need me to change anything else just let me know.

Looks good, could you add in some documentation and some tests in the tests folder?


Button in readme that adds the Working Group meeting to your calendar

It would be great if a recurring meeting could be added to someone's calendar who's interested in attending the working group with just a click of a button on the readme page! Just an idea :-)

This is a great idea! I can look into this.

Implemented by  https://github.com/paketo-buildpacks/.github/pull/22


Outstanding PowerPC64 testcase failures

With powerpc64 fully bootstrapped, I was able to go back and build the libc tests. It shows a number of things we need to move into the arch specific files. Note: I also had to make a couple of changes to struct ipc_perm to get the tests to build (some fields are different sizes), so it needs to be moved too.
bad MCL_CURRENT value at byte 0: rust: 1 (0x1) != c 0 (0x0)
bad MCL_CURRENT value at byte 1: rust: 0 (0x0) != c 32 (0x20)
bad MCL_FUTURE value at byte 0: rust: 2 (0x2) != c 0 (0x0)
bad MCL_FUTURE value at byte 1: rust: 0 (0x0) != c 64 (0x40)
bad SIGSTKSZ value at byte 1: rust: 32 (0x20) != c 64 (0x40)
bad CBAUD value at byte 0: rust: 15 (0xf) != c 255 (0xff)
bad CBAUD value at byte 1: rust: 16 (0x10) != c 0 (0x0)
bad TAB1 value at byte 1: rust: 8 (0x8) != c 4 (0x4)
bad TAB2 value at byte 1: rust: 16 (0x10) != c 8 (0x8)
bad TAB3 value at byte 1: rust: 24 (0x18) != c 12 (0xc)
bad CR1 value at byte 1: rust: 2 (0x2) != c 16 (0x10)
bad CR2 value at byte 1: rust: 4 (0x4) != c 32 (0x20)
bad CR3 value at byte 1: rust: 6 (0x6) != c 48 (0x30)
bad FF1 value at byte 1: rust: 128 (0x80) != c 64 (0x40)
bad BS1 value at byte 1: rust: 32 (0x20) != c 128 (0x80)
bad VT1 value at byte 1: rust: 64 (0x40) != c 0 (0x0)
bad VT1 value at byte 2: rust: 0 (0x0) != c 1 (0x1)
bad VWERASE value at byte 0: rust: 14 (0xe) != c 10 (0xa)
bad VREPRINT value at byte 0: rust: 12 (0xc) != c 11 (0xb)
bad VSUSP value at byte 0: rust: 10 (0xa) != c 12 (0xc)
bad VSTART value at byte 0: rust: 8 (0x8) != c 13 (0xd)
bad VSTOP value at byte 0: rust: 9 (0x9) != c 14 (0xe)
bad VDISCARD value at byte 0: rust: 13 (0xd) != c 16 (0x10)
bad VTIME value at byte 0: rust: 5 (0x5) != c 7 (0x7)
bad IXON value at byte 1: rust: 4 (0x4) != c 2 (0x2)
bad IXOFF value at byte 1: rust: 16 (0x10) != c 4 (0x4)
bad ONLCR value at byte 0: rust: 4 (0x4) != c 2 (0x2)
bad CSIZE value at byte 0: rust: 48 (0x30) != c 0 (0x0)
bad CSIZE value at byte 1: rust: 0 (0x0) != c 3 (0x3)
bad CS6 value at byte 0: rust: 16 (0x10) != c 0 (0x0)
bad CS6 value at byte 1: rust: 0 (0x0) != c 1 (0x1)
bad CS7 value at byte 0: rust: 32 (0x20) != c 0 (0x0)
bad CS7 value at byte 1: rust: 0 (0x0) != c 2 (0x2)
bad CS8 value at byte 0: rust: 48 (0x30) != c 0 (0x0)
bad CS8 value at byte 1: rust: 0 (0x0) != c 3 (0x3)
bad CSTOPB value at byte 0: rust: 64 (0x40) != c 0 (0x0)
bad CSTOPB value at byte 1: rust: 0 (0x0) != c 4 (0x4)
bad CREAD value at byte 0: rust: 128 (0x80) != c 0 (0x0)
bad CREAD value at byte 1: rust: 0 (0x0) != c 8 (0x8)
bad PARENB value at byte 1: rust: 1 (0x1) != c 16 (0x10)
bad PARODD value at byte 1: rust: 2 (0x2) != c 32 (0x20)
bad HUPCL value at byte 1: rust: 4 (0x4) != c 64 (0x40)
bad CLOCAL value at byte 1: rust: 8 (0x8) != c 128 (0x80)
bad ECHOKE value at byte 0: rust: 0 (0x0) != c 1 (0x1)
bad ECHOKE value at byte 1: rust: 8 (0x8) != c 0 (0x0)
bad ECHOE value at byte 0: rust: 16 (0x10) != c 2 (0x2)
bad ECHOK value at byte 0: rust: 32 (0x20) != c 4 (0x4)
bad ECHONL value at byte 0: rust: 64 (0x40) != c 16 (0x10)
bad ECHOPRT value at byte 0: rust: 0 (0x0) != c 32 (0x20)
bad ECHOPRT value at byte 1: rust: 4 (0x4) != c 0 (0x0)
bad ECHOCTL value at byte 0: rust: 0 (0x0) != c 64 (0x40)
bad ECHOCTL value at byte 1: rust: 2 (0x2) != c 0 (0x0)
bad ISIG value at byte 0: rust: 1 (0x1) != c 128 (0x80)
bad ICANON value at byte 0: rust: 2 (0x2) != c 0 (0x0)
bad ICANON value at byte 1: rust: 0 (0x0) != c 1 (0x1)
bad PENDIN value at byte 1: rust: 64 (0x40) != c 0 (0x0)
bad PENDIN value at byte 3: rust: 0 (0x0) != c 32 (0x20)
bad NOFLSH value at byte 0: rust: 128 (0x80) != c 0 (0x0)
bad NOFLSH value at byte 3: rust: 0 (0x0) != c 128 (0x80)
bad VEOL value at byte 0: rust: 11 (0xb) != c 6 (0x6)
bad VEOL2 value at byte 0: rust: 16 (0x10) != c 8 (0x8)
bad VMIN value at byte 0: rust: 6 (0x6) != c 5 (0x5)
bad IEXTEN value at byte 1: rust: 128 (0x80) != c 4 (0x4)
bad TOSTOP value at byte 1: rust: 1 (0x1) != c 0 (0x0)
bad TOSTOP value at byte 2: rust: 0 (0x0) != c 64 (0x40)
bad FLUSHO value at byte 1: rust: 16 (0x10) != c 0 (0x0)
bad FLUSHO value at byte 2: rust: 0 (0x0) != c 128 (0x80)
bad EXTPROC value at byte 2: rust: 1 (0x1) != c 0 (0x0)
bad EXTPROC value at byte 3: rust: 0 (0x0) != c 16 (0x10)
bad TCGETS value at byte 0: rust: 1 (0x1) != c 19 (0x13)
bad TCGETS value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TCGETS value at byte 2: rust: 0 (0x0) != c 60 (0x3c)
bad TCGETS value at byte 3: rust: 0 (0x0) != c 64 (0x40)
bad TCSETS value at byte 0: rust: 2 (0x2) != c 20 (0x14)
bad TCSETS value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TCSETS value at byte 2: rust: 0 (0x0) != c 60 (0x3c)
bad TCSETS value at byte 3: rust: 0 (0x0) != c 128 (0x80)
bad TCSETSW value at byte 0: rust: 3 (0x3) != c 21 (0x15)
bad TCSETSW value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TCSETSW value at byte 2: rust: 0 (0x0) != c 60 (0x3c)
bad TCSETSW value at byte 3: rust: 0 (0x0) != c 128 (0x80)
bad TCSETSF value at byte 0: rust: 4 (0x4) != c 22 (0x16)
bad TCSETSF value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TCSETSF value at byte 2: rust: 0 (0x0) != c 60 (0x3c)
bad TCSETSF value at byte 3: rust: 0 (0x0) != c 128 (0x80)
bad TCGETA value at byte 0: rust: 5 (0x5) != c 23 (0x17)
bad TCGETA value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TCGETA value at byte 2: rust: 0 (0x0) != c 20 (0x14)
bad TCGETA value at byte 3: rust: 0 (0x0) != c 64 (0x40)
bad TCSETA value at byte 0: rust: 6 (0x6) != c 24 (0x18)
bad TCSETA value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TCSETA value at byte 2: rust: 0 (0x0) != c 20 (0x14)
bad TCSETA value at byte 3: rust: 0 (0x0) != c 128 (0x80)
bad TCSETAW value at byte 0: rust: 7 (0x7) != c 25 (0x19)
bad TCSETAW value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TCSETAW value at byte 2: rust: 0 (0x0) != c 20 (0x14)
bad TCSETAW value at byte 3: rust: 0 (0x0) != c 128 (0x80)
bad TCSETAF value at byte 0: rust: 8 (0x8) != c 28 (0x1c)
bad TCSETAF value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TCSETAF value at byte 2: rust: 0 (0x0) != c 20 (0x14)
bad TCSETAF value at byte 3: rust: 0 (0x0) != c 128 (0x80)
bad TCSBRK value at byte 0: rust: 9 (0x9) != c 29 (0x1d)
bad TCSBRK value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TCSBRK value at byte 3: rust: 0 (0x0) != c 32 (0x20)
bad TCXONC value at byte 0: rust: 10 (0xa) != c 30 (0x1e)
bad TCXONC value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TCXONC value at byte 3: rust: 0 (0x0) != c 32 (0x20)
bad TCFLSH value at byte 0: rust: 11 (0xb) != c 31 (0x1f)
bad TCFLSH value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TCFLSH value at byte 3: rust: 0 (0x0) != c 32 (0x20)
bad TIOCINQ value at byte 0: rust: 27 (0x1b) != c 127 (0x7f)
bad TIOCINQ value at byte 1: rust: 84 (0x54) != c 102 (0x66)
bad TIOCINQ value at byte 2: rust: 0 (0x0) != c 4 (0x4)
bad TIOCINQ value at byte 3: rust: 0 (0x0) != c 64 (0x40)
bad TIOCGPGRP value at byte 0: rust: 15 (0xf) != c 119 (0x77)
bad TIOCGPGRP value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TIOCGPGRP value at byte 2: rust: 0 (0x0) != c 4 (0x4)
bad TIOCGPGRP value at byte 3: rust: 0 (0x0) != c 64 (0x40)
bad TIOCSPGRP value at byte 0: rust: 16 (0x10) != c 118 (0x76)
bad TIOCSPGRP value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TIOCSPGRP value at byte 2: rust: 0 (0x0) != c 4 (0x4)
bad TIOCSPGRP value at byte 3: rust: 0 (0x0) != c 128 (0x80)
bad TIOCOUTQ value at byte 0: rust: 17 (0x11) != c 115 (0x73)
bad TIOCOUTQ value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TIOCOUTQ value at byte 2: rust: 0 (0x0) != c 4 (0x4)
bad TIOCOUTQ value at byte 3: rust: 0 (0x0) != c 64 (0x40)
bad TIOCGWINSZ value at byte 0: rust: 19 (0x13) != c 104 (0x68)
bad TIOCGWINSZ value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TIOCGWINSZ value at byte 2: rust: 0 (0x0) != c 8 (0x8)
bad TIOCGWINSZ value at byte 3: rust: 0 (0x0) != c 64 (0x40)
bad TIOCSWINSZ value at byte 0: rust: 20 (0x14) != c 103 (0x67)
bad TIOCSWINSZ value at byte 1: rust: 84 (0x54) != c 116 (0x74)
bad TIOCSWINSZ value at byte 2: rust: 0 (0x0) != c 8 (0x8)
bad TIOCSWINSZ value at byte 3: rust: 0 (0x0) != c 128 (0x80)
bad FIONREAD value at byte 0: rust: 27 (0x1b) != c 127 (0x7f)
bad FIONREAD value at byte 1: rust: 84 (0x54) != c 102 (0x66)
bad FIONREAD value at byte 2: rust: 0 (0x0) != c 4 (0x4)
bad FIONREAD value at byte 3: rust: 0 (0x0) != c 64 (0x40)
bad ipc_perm size: rust: 56 (0x38) != c 48 (0x30)
bad field offset __seq of ipc_perm: rust: 28 (0x1c) != c 24 (0x18)
bad field type __seq of ipc_perm: rust: 0x1c != c 0x18
bad shmid_ds size: rust: 120 (0x78) != c 112 (0x70)
bad field size shm_perm of shmid_ds: rust: 56 (0x38) != c 48 (0x30)
bad field offset shm_segsz of shmid_ds: rust: 56 (0x38) != c 72 (0x48)
bad field type shm_segsz of shmid_ds: rust: 0x38 != c 0x48
bad field offset shm_atime of shmid_ds: rust: 64 (0x40) != c 48 (0x30)
bad field type shm_atime of shmid_ds: rust: 0x40 != c 0x30
bad field offset shm_dtime of shmid_ds: rust: 72 (0x48) != c 56 (0x38)
bad field type shm_dtime of shmid_ds: rust: 0x48 != c 0x38
bad field offset shm_ctime of shmid_ds: rust: 80 (0x50) != c 64 (0x40)
bad field type shm_ctime of shmid_ds: rust: 0x50 != c 0x40
bad field offset shm_cpid of shmid_ds: rust: 88 (0x58) != c 80 (0x50)
bad field type shm_cpid of shmid_ds: rust: 0x58 != c 0x50
bad field offset shm_lpid of shmid_ds: rust: 92 (0x5c) != c 84 (0x54)
bad field type shm_lpid of shmid_ds: rust: 0x5c != c 0x54
bad field offset shm_nattch of shmid_ds: rust: 96 (0x60) != c 88 (0x58)
bad field type shm_nattch of shmid_ds: rust: 0x60 != c 0x58

Nice work! If you want to set up a CI builder for powerpc64 you're more than welcome to, it should be relatively simple to the other triples like aarch64-unknown-linux-gnu.
You'll probably just need to give me a build of the standard library for powerpc64 linux as well as the nightly date it corresponds to, but other than that it should be easy to add! (and prevent regressions)

Thanks Alex, it would be great to get powerpc64 into the CI builder. I'll work on it when we get the above issues fixed.

[triage-attempt] Hello @antonblanchard, can you share your work about making a CI builder for PowerPC64 here? No problem if you didn't find a way or moved to an other project.
If you don't mind I would try to make it working like the way we test OpenBSD and consort.
Thank you very much. :)

We're now currently testing powerpc64, so I believe these have all been fixed.


fix(cli): allow overrides reporter via cli option

fix: #2537

The CI is always down on ubuntu, I am trying to solve it, please wait some time :)


Solc package (solc-select)

For now, what we have here is ability to use solc-select to switch the current used version of solc.
Using and activating python virtual environment from now on should be essential. Otherwise, if you have python already in use on production, well good luck!
Will see in the future to check and disable solc-select (trigger error) if python environment is not set!
Update: I've added the check for virtual environment. No need to know which environment as long as it's set. If it's not set, it will raise error and instructions on how to set the environment.

Added environment variable TEST_SOLGO_SOLC_SELECT_DISABLED. If it's set to true it will not run these tests. This is a safety measure that can be taken into account.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

117 of 149 (78.52%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 81.881%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

solc/command_mock.go
19
22
86.36%

solc/select.go
25
35
71.43%

solc/command_real.go
73
92
79.35%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
9255

Relevant Lines:
11303

💛  - Coveralls