zulip: Change remove_subscriptions to update_subscriptions.

The underlying endpoint that remove_subscriptions called was
zerver.streams.view.update_subscriptions_backend, which is more
for bulk removing and adding subscriptions. Also there is a
separate endpoint for removing subscriptions that gives more
control than this one. So this method should be more aptly
called update_subscriptions and should allow one to add
subscriptions as well.
Note that once we make the next PyPI release and update the main
repo to use it, ./zulip/tools/test-api should fail, and would
need to be updated in the PR that updates the main repo to use
the latest release of the packages.
@roberthoenig, @showell: Could I please get a quick review? Thanks! :)

Just a random bit of commentary since I saw this: There are some use cases for bulk-removing subscriptions via the API, but I don't expect them to be common.

@timabbott: From what I remember, in either case, bulk-removing shouldn't be a problem. But just from a general perspective, advertising update_subscriptions as remove_subscriptions just didn't seem right, since there was already remove_subscriptions that gave users a little bit more control (for example, removing someone else from a stream, which update_subscriptions couldn't do because it didn't take in the principals argument). So there are definitely some use cases yes, but the changes that were done as part of this shouldn't affect those! :) Thanks!

Yep, makes sense.


GL backend shading_language parsing fails

https://github.com/gfx-rs/gfx/blob/master/src/backend/gl/src/info.rs line 193 fails on some systems, gl.GetString returns a null pointer. Can I quickfix this? It prevents my application from working on most systems since it panics.
EDIT: This only happens on Win10, not on a linux virtualbox

Could you print the returned version information from the GL (before parse)?

For some reason Visual Studio Code and Visual Studio 2017 are unable to debug the executable anymore, I don't know what's wrong. I will try to clone and edit gfx's source.

I can't use my edited dependency, see my reddit post: https://www.reddit.com/r/rust/comments/7dci9i/dependency_patching_error/

Have you used the 0.16 or pre-ll branch?
Nonetheless, locally cloning and running the triangle example (of one of the mentioned branches) should work also.

How do I run that? Following the instructions does not work

@msiglreith Maybe you can build a test for me?

@PvdBerg1998
I setup a branch here: https://github.com/msiglreith/gfx/tree/gl-version
Running cargo run --example triangle in the root directory should work. The console will print out two strings, GL version and GLSL version.
Example output from my system:
"4.5.13492 Compatibility Profile/Debug Context 22.19.677.257"
"4.50"

@msiglreith Runs on my Win10 desktop (the machine where the bug does not occur). Output:
"4.5.0 NVIDIA 384.94"
"4.50 NVIDIA"

Also runs on the laptop where the crash occurs:
"4.4.0 - Build <IP_ADDRESS>74"
"4.40 - Build <IP_ADDRESS>74"

So the get_version function does not return null here?

Ok, thanks for the output. If I understand it correctly, the triangle example works fine even on the laptop, but it crashes in your application? Could you provide a minimal example for reproducing or give us access to the source? Might be an error on context creation earlier.

Yes, I have been trying to patch the dependency to use your branch just now. Having some trouble though.
The error occurs when using the Piston library. You can use their hello world example: https://github.com/PistonDevelopers/piston_window

I had also created an issue for piston: https://github.com/PistonDevelopers/piston/issues/1214

I'm experiencing the same issue after updating rust and only when running cargo run --release
Version: rustc 1.23.0-nightly (63739ab7b 2017-11-21)

@McGittyHub Thanks for the report, I'm able to reproduce it locally but not sure what's causing the issue, might be a nightly regression. It also fails when running our triangle example in release mode.
It seems to fail loading the GL1.1 functions correctly for me, which includes gl.GetString.

Looks like a nightly regression: https://github.com/rust-lang/rust/issues/46182

Update: The issue is due to the PROC definition in gl-rs, which is marked as non-null by the compiler in release due to the "system" ABI, boiling down to missing kernel32::GetProcAddress call and getting null-ptrs for the OpenGL 1.1 functions.
The mentioned typedef must be fixed in gl-rs, glutin needs to be updated to the new gl-rs version and gfx-rs must also update to the new glutin version then, yay.

@msiglreith I'm curious about your post in the rust repos issue, I did not quite get the explanation. Did the null check get optimized away in release mode?
if !p.is_null() {
    panic!("{:?}", p);
    return p;
}

Or was something else?

It's been a while. I checked out the linked glrs issue and it seems to be fixed. This issue is probably unblocked?

yes, thanks!


Added ignore option

The flatten function is very useful and low-weight to be used in various use-cases. Although in our case we needed the option to ignore some objects. For example we wanted to flatten an object with some nested instances of moment (...). Those needed to be preserved.
Therefore I added the option to ignore every occurence of given fields. The feature is kept very simple to keep it clear.

Did this never get merged in? I think this would be a great feature to add...


True xDS version in admin interface

While we added config hash for versioning of xDS in https://github.com/envoyproxy/envoy/pull/1805, it would be useful for integration testing to have the actual version info as understood by the management server and xDS exposed on an admin interface handler. This won't be available via stats, since version info is an arbitrary length string which we can't represent as a gauge, so just an admin handler.

@rfaulk @mattklein123 I'm thinking of adding for ADS a JSON/proto handler for this that returns some message defined in data-plane-api describing each of the muxed protocols. For non-ADS, it's a bit more complicated for RDS/EDS, since each of these xDS might actually have multiple versions, as resources may fan out to multiple servers individually. This is in aid of Google integration testing, I think others will find it helpful.
LMK if the above proposal makes sense and I can implement.

SGTM. Should this be the first admin API that we define a proto response for instead of hand rolling JSON output? Incrementally more work but would be cool.

For posterity: right now we have the version info string of different xDS APIs surfaced in a couple places:

RDS: in the /routes admin endpoint, for each route configuration. You are right that it would be a little bit more complicated to do so centrally for RDS. Which is why I did the handler work in the scope of the router.
CDS: in the /clusters admin endpoint, for the cluster manager.

@htuch what do you think about removing these from their separate places and unifying them under the one /xds(?) admin endpoint? I would love to see the admin endpoint output converted into proto messages, as I have already been burned by bad JSON in the /routes output.

@junr03 Yep, I think moving to a single handler would be great. Let's make this happen, hopefully I get cycles this year unless someone is interested in this before Q1.


Added support for getting job build details, job build output, and qu…

…eued item details.
Fixes #98.

This change is

Awesome stuff @corydwood - I'll get onto the review this week. Can you add some details into the CHANGELOG.MD mentioning the new additions (this will go into the release notes section on PS Gallery).

Still keen on getting this one in @corydwood - any chance you'll have time to make the changes? Otherwise I can finish it up.

Would love to get this functionality going, but @corydwood seems to have disappeared.  What can we do?

Sorry I haven't been able to work on this more. I added this PR after adding this functionality for a project I was working on for my company and haven't had time to add the additional tests and documentation requested.
I'm unsure when I'm going to have time to make these changes so it may be best if @PlagueHO can finish it up as he stated above.


Angular 11_ Dist folder includes duplicate module files

Command
build
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
I am working on angular 11 project, where I have observed on ng build in dist folder duplicate chunks are generated. Please find more details below:

In above screen shot on highlighted dist folder's area indicates duplicate files for same module type. With 'default/~' annotation. I am not getting why these files are getting generated and those are getting added on site's module tree map which is impacting performance of my project.

Can any one help me to avoid these duplicate modules issue?
Thankyou in Advance..!
Minimal Reproduction
Using below command to generate dist folder:
ng build  --aot true --build-optimizer true --common-chunk true --cross-origin none --delete-output-path true --extract-css false --extract-licenses false --fork-type-checker true --named-chunks true --output-hashing none --preserve-symlinks false --prod true --service-worker true --source-map false --stats-json false --subresource-integrity false --vendor-chunk true

Exception or Error
No response
Your Environment
Angular CLI: 11.2.14
Node: 12.22.12
OS: win32 x64

Angular: 11.0.2
animations, common, compiler, compiler-cli, core, forms
language-service, platform-browser, platform-browser-dynamic
router, service-worker
Ivy Workspace: Yes

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.1100.7
@angular-devkit/build-angular      0.1100.7
@angular-devkit/core               11.0.7
@angular-devkit/schematics         11.2.14
@angular/cdk                       11.2.13
@angular/cli                       11.2.14
@angular/localize                  11.2.14
@angular/material                  11.2.13
@angular/material-moment-adapter   11.2.13
@schematics/angular                11.2.14
@schematics/update                 0.1102.14
rxjs                               6.6.7
typescript                         4.0.5

Anything else relevant?
No response

This is working as intended due to differential loading.
Please be aware that Angular 11 is no longer supported. For more information about or support policy please see https://angular.io/guide/releases#support-policy-and-schedule.


Stream heap snapshots

Takes advantage of https://github.com/JuliaLang/julia/pull/51518.

Codecov Report

Merging #27 (f054d9f) into main (62d1303) will decrease coverage by 29.70%.
Report is 2 commits behind head on main.
The diff coverage is 0.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@             Coverage Diff             @@
##             main      #27       +/-   ##
===========================================
- Coverage   92.85%   63.15%   -29.70%
===========================================
  Files           1        1
  Lines         154      133       -21
===========================================
- Hits          143       84       -59
- Misses         11       49       +38

Files
Coverage Δ

src/ProfileEndpoints.jl
63.15% <0.00%> (-29.70%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Logged-in users should be able to pledge items

Part of #77
Here is an example user flow for this feature. Basically, clicking the button opens a new tab/window to the Amazon product and redirects the original tab to the "Thanks for donating"/pledge page (note the Amazon page is a newly opened tab; clicking the button simulates closing the tab):

We've made some changes to the last page since I made the gif (notably, + pledge quantity), but feel free to play around with the UI:

If the "Not Yet Received" functionality isn't built yet, let's not worry about it here.

"Named pledge" pages should probably be private to the pledging user, admins, and site managers for the related wishlists. Does that make sense?


Frontend: create a base home page

First thing we need to do is create a debug home page so people can start working on backend + connecting to gcp etc. There's no need to actually add anything to the sections, when people start working on this they'll add the content to the sections.
All it needs is a couple different categories:

Internal API calls
GCP connection
External API calls

This is for anyone, so just pick it up. ( add yourself as an assignee )

I can do this one (i don't have perms to assign myself)

try assigning yourself now, i think i fixed it


throwable does not cause test to fail

Example:
class MyException() : Throwable()

class Playground : FlatSpec() { init {
    "it" should "do something" {
        throw MyException()
    }

    "it" should "do something else" {
    }
}
}

In Intellij/gradle this gives an incorrect picture like if the first test suceeded correctly.

If a class MyRunException() : RuntimeException() instance is thrown instead, the test is tagged as failed as expected. Why don't Throwables cause tests to fail but require RuntimeException as base class?
I thought it may be a junit feature/problem after all but it does not seem to be the case:

public class Dummy {

    @Test
    public void runTest() throws Throwable {
        throw new Throwable();
    }

    @Test
    public void runAnotherTest() throws Throwable {
    }
}

Here runTest fails as expected:

:+1: Sounds like I just need to change Exception to Throwable.


Added a Blog website

Related Issue
This PR looks forward to resolving the issue where the blog was directing to an empty site. It has also resolved the bug of blog being not directable to anywhere.
Description
The changes added are a blogging folder where all content related to a blogging site is present.  Users can read blogs in there in this site.
Type of PR

[x] Bug fix
[x] Feature enhancement

Screenshots

Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:
This is a blog reading and search available site. Kindly review this PR and label it under GSSoC @Durgesh-Vaigandla

@Varsha010101 What's your issue number.?

Issue number 280


import messages — prepare for review

Docs Build status updates of commit 9549a61:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 9e32b5e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/graph-api/import-messages/import-external-messages-to-teams.md
:bulb:Suggestion
View
Details

msteams-platform/graph-api/import-messages/import-external-messages-to-teams.md

Line 46, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /graph/api/team-post?view=graph-rest-beta&tabs=http NOTE: This Suggestion will become a Warning on 1/29/21.
Line 96, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /graph/api/channel-post?view=graph-rest-beta&tabs=http NOTE: This Suggestion will become a Warning on 1/29/21.
Line 319, Column 0: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /graph/api/group-post-members?view=graph-rest-beta&tabs=http NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a4b041d:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 73acdfe:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/graph-api/import-messages/import-external-messages-to-teams.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit faf6015:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/graph-api/import-messages/import-external-messages-to-teams.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Request (create channel in migration state)
{
<EMAIL_ADDRESS>"migration",
"displayName": "Architecture Discussion",
"description": "This channel is where we debate all future architecture plans",
"createdDateTime": "2020-03-14T11:22:17.047Z"
}
Response Body
{
<EMAIL_ADDRESS>"https://canary.graph.microsoft.com/testprodbetateamsgraphsvcncus/$metadata#teams('9cc6d6ab-07d8-4d14-bc2b-7db8995d6d23')/channels/$entity",
"id"<EMAIL_ADDRESS>"createdDateTime": null,
"displayName": "Architecture Discussion",
"description": "This channel is where we debate all future architecture plans",
"isFavoriteByDefault": null,
"email": null,
"webUrl": null,
"membershipType": null,
"moderationSettings": null
}
Note response headers do not contain the following for creating channels
Location: /teams/{teamId}/channels/{channelId}/operations/{operationId}
Content-Location: /teams/{teamId}/channels/{channelId}

Could we trim down the request for importing messages to the bare essentials ?
POST https://graph.microsoft.com/beta/teams/teamId/channels/channelId/messages
{
"replyToId": null,
"messageType": "message",
"createdDateTime": "2019-02-04T19:58:15.511Z",
"lastModifiedDateTime": null,
"deleted": false,
"subject": null,
"summary": null,
"importance": "normal",
"locale": "en-us",
"policyViolation": null,
"from": {
"application": null,
"device": null,
"conversation": null,
"user": {
"id": "id-value",
"displayName": "Joh Doe",
"userIdentityType": "aadUser"
}
},
"body": {
"contentType": "html",
"content": "Hello World"
},
"attachments": [],
"mentions": [],
"reactions": []
}
can be shortened to
POST https://graph.microsoft.com/beta/teams/teamId/channels/channelId/messages
{
"createdDateTime": "2019-02-04T19:58:15.511Z",
"from": {
"user": {
"id": "id-value",
"displayName": "Joh Doe",
"userIdentityType": "aadUser"
}
},
"body": {
"contentType": "html",
"content": "Hello World"
}
}

Response code for end team migration and end channel migration are 200 and 204

Response code for add team members is 201 Created not 204

We need to move the errors from this overview doc to individual api docs

Docs Build status updates of commit 655c6f5:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/graph-api/import-messages/import-external-messages-to-teams.md
:warning:Warning
View
Details

msteams-platform/graph-api/import-messages/import-external-messages-to-teams.md

Line 220, Column 13: [Warning-bookmark-not-found] Cannot find bookmark '#http-400-client-request-errors' in 'graph-api/import-messages/import-external-messages-to-teams.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3518166:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/graph-api/import-messages/import-external-messages-to-teams.md
:warning:Warning
View
Details

msteams-platform/graph-api/import-messages/import-external-messages-to-teams.md

Line 220, Column 13: [Warning-bookmark-not-found] Cannot find bookmark '#http-400-client-request-errors' in 'graph-api/import-messages/import-external-messages-to-teams.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit e58ac28:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit d6a28c4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/graph-api/import-messages/import-external-messages-to-teams.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[driver] utility for extracting and saving timeline summary

lgtm. This looks great! I am slightly concerned that the trace label names are not guaranteed to be stable. Maybe we can audit the codebase together to ensure we somehow tag certain traces are being used by external tools and must not be changed.

Buildbot is mad though.


Update Deploy-Policies.ps1

Adding required scope permissions for graph access. While testing on a new tenant was unable to deploy without these additional permissions.

Interesting, I thought so too and was testing with less permission and it did work for me - Merged for now and I will double check again - thanks for the contribution!


error logline when sendq is exceeded

This was considered and rejected in #1293. However, it's actually quite likely to occur in a context where fakelag is disabled and bots are in use.

I misremembered what I did previously: there is a logline for the sendq, but it's not always being triggered as expected.


Improper Handling of Exceptional Conditions in Newtonsoft.Json

Describe the bug
The following message has been reported by GitHub:
We found potential security vulnerabilities in your dependencies.
Scope

[x] AP Review dependency and Update
[x] CP Update
[x] DP Update
[x] ExDM Update

Done


Project website URL on GitHub project doesn't work

http://francescou.github.io/docker-compose-ui is 404

Any feedback @francescou?

http://francescou.github.io/docker-compose-ui
↓
https://github.com/francescou/docker-compose-ui

@francescou
It doesn't seem to be fixed with my current permissions. Please correct it when you have time.


Data dictionary for indicators

We need to provide a data dictionary that describes the indicators.

[x] Physical Exposure
[x] Social Vulnerability
[ ] Multi-hazard Risk
[x] PSRA
[x] DSRA

PSRA indicators completed sent to translation on Dec 23, 2021.

Closing as Multi Hazard risk dataset is being re-scoped.


Should have option to gracefully handle existing A record for CNAME create

When doing a CNAME create action on a record with an existing A record, the following error is returned:
Excon::Errors::BadRequest: Expected(201) <=> Actual(400 Bad Request)

CNAME must be the only record on a subdomain

Obviously we can't expect Chef to continue, as that might throw off expectations, but an extra option force would allow us to remove any existing A records on that subdomain if set to true, or continue the current behaviour (default) if set to false.
Use case that runs into this:
our nodes can be created on both EC2 or other external hosts. If on EC2, we create a CNAME record for the by amazon provided DNS record (like ec2-53-214-183-212.eu-west-1.compute.amazonaws.com). However, when using a non-ec2 instance, we use the public_ip with an A record.
Switching between ec2 and non-ec2, you'd have to manually remove the records before continuing.

hi @JeanMertz
I realize this issue has had no activity for a little while. Can you let us know if this issue is now resolved for you?

I'll close this issue @martinisoft, I am no longer actively working on Chef projects, so have no idea if this is still an issue, but at least it's not for me.
Thank you for your time and involvement :+1: :smile:


add python 3.12 compatibility

Nose is deprecated, and so this migrates to pytest and fixes all broken assertions. All previously passing tests pass, so no changes to test logic were needed. Pytest works with Python 3.8+, so I've updated the versions in setup.py to reflect that. Finally, there was an unused import in the test_release.py file, that I removed.

@pyrox0 thanks. Merged.


Converting float64 values to datetime64[ns] format using pd.to_datetime results in NaT if errors='coerce'

Code Sample, a copy-pastable example if possible
A Pandas dataframe contains a date variable that is formatted as float64 as follows:
tempDF = pd.DataFrame({'group': ['a','b'],
                       'date': [1.434692e+18,1.432766e+18]})

print(tempDF)

Which appears as:
           date group
0  1.434692e+18     a
1  1.432766e+18     b

The date variables can be formatted to datetime64[ns] as follows:
tempDF['date'] = pd.to_datetime(tempDF['date'],format=None)
print(tempDF)

Which works as expected:
                 date group
0 2015-06-19 05:33:20     a
1 2015-05-27 22:33:20     b

However, if errors='coerce' is included in the do_datetime() function, the dates are returned as NaT.
tempDF['date'] = pd.to_datetime(tempDF['date'],format=None,errors='coerce')
print(tempDF)

Which produces the following:
  date group
0  NaT     a
1  NaT     b

This issue was identified as a result of a reported bug (#12821 ) where datetime64[ns] columns are returned as float64 following agg() function where all dates in a group are NaT. Converting columns back to datetime64[ns] format is necessary. However, identifying valid numeric values as errors when errors='coerce' and returning NaT values results in unnecessary data-loss.
 But I also removed the default unit to None from ns (IOW it would only trigger if passed). So this was an oversite.
thanks for the report.

Thanks for the rapid response!


Suggestion: enable auto completion in docker container

I suggest to enable auto completion in docker container.
+ RUN rm /etc/apt/apt.conf.d/docker-clean

Reference

https://github.com/tianon/docker-brew-ubuntu-core/issues/75#issuecomment-386444576
https://penguin-coffeebreak.com/archives/242

Thanks! I'll merge it after fixing CI 👍

Added in https://github.com/Tiryoh/docker-ros2-desktop-vnc/pull/79.
Thanks @atinfinity  :+1:


Angular2spa bundling improvements

These are significant changes, so I'm calling them out as a pull request, (even though I'm just about to merge it). If you have feedback/questions/etc, please do post here even though it will probably be merged by the time you see this - we can still change things.
The main differences are:

We now select between 'dev' and 'prod' builds based on the presence of a --env.prod flag, and not based on the ASPNETCORE_ENVIRONMENT env var. This is much better, because it means build and publish scripts can reliably trigger the correct dev/prod build in a natural way. See how project.json's prepublish scripts can now easily guarantee the correct build format. Relying on the ASPNETCORE_ENVIRONMENT var before made no sense really, given that the current value just reflects what else you're doing on your machine, and you might not remember to change it before publishing your app.

Calling the flag --env.prod is not arbitrary - this is the flag format that Webpack 2 uses, so when we later update to Webpack 2, people won't have to change their build scripts.

Server-side prerendering now uses a prebuilt bundle (ClientApp/dist/main-server.js) - it no longer compiles your TypeScript at runtime. This is a big improvement - it means that:

App startup is much faster (no need to wait for an extra round of compilation)
Deployment is much simpler (no need to deploy your .ts source code or take runtime dependencies on any part of Webpack - you just deploy the ClientApp/dist/main-server.js file that comes out of the build process)
Deployed apps have fewer ways to fail (you can no longer have issues with TypeScript compilation in production, because that no longer happens on your prod servers)
Compatiblity with obscure webpack plugins is now basically 100%, because we're no longer doing anything weird (previously we used aspnet-webpack's LoadViaWebpack feature to compile to an in-memory filesystem, and in some edge cases, this confused some webpack plugins, but now we're just running a plain regular Webpack build system at build time and putting the results on disk, just like every other Webpack build system out there).
Developers will be more able to debug any issues they encounter in server-side prerendering, because the server-side builds are no longer created using a hidden webpack config, and the output is no longer hidden in an in-memory filesystem. Now it's just a regular webpack config you can see and edit yourself, and the files go onto disk where you can see them yourself. Any build errors will now happen at build-time, not run time. You can even execute the prerendering bundle directly under node.exe (completely independently of ASP.NET) if that helps you track down anything unexpected.

Soon I'll be applying the equivalent changes to all the other templates (React, etc.).

I was going to recommend the naming change as well! Always nice to align with naming conventions :+1:


Pytest tests need updating for the new test discovery model

Tests in src/test/unittests/pytest/pytest.testMessageService.test.ts require a set of input text to send to the parser to complete the tests there. The input text is the output text from the pythonFiles/testing_tools module.
However, the test layout that we need to replicate is not successfully handled by the testing_tools adapter for Pytest yet. The foreign tests brought into a class via the inheritance model is causing the adapter to throw NotImplementedError here. (The file being processed at that point in the code does not match the file where test exists.)
Once we get testing_tools updated to handle inheritance in Pytest then we should be able to generate the correct ouput JSON to replace the contents of the *.output files in src\test\pythonFiles\testFiles\pytestFiles\results\ to get these tests working again.

This is also causing problems in the tests found in file src/test/unittests/pytest/pytest.discovery.test.ts.

This must be a P0, we cannot leave this as is, else this will get pushed into the queue with other issues/bugs, when in fact it could result in a regression.
I.e. we could end up making changes that break existing code and there's absolutely no way this will get caught, until a user reports this.
Also, this is a new feature that was introduced in a recent release.

Removing P1 and adding to milestone


add noise and reverberance version for BinauralWSJ0Mix

Hi there,
I have created a noise and reverberance version of BinauralWSJ0Mix datasets and trained with convtasnet-parallel structure. Here are the recipes and not conflicted with the clean version of datasets.
Also, I have trained convtasnet-parallel.yaml again and got a better results which I could share you with the Google Driver.
Thanks.

Hi @ycemsubakan , do you have time for checking this PR please?

Hi @huangzj421 , sorry for the delay. I will try to do it soon.

@huangzj421 , Could you add in the README the instructions on how to run the model with these noisy conditions? As before, the script should automatically download and create the corresponding dataset.

For convtasnet-parallel-noisy.yaml I am getting this error. You can see the command I used also here.

And, I am observing the following error for convtasnet-parallel-reverb.yaml:

For convtasnet-parallel-noisy.yaml I am getting this error. You can see the command I used also here.

I have corrected the data generation scripts and now these should work fine.

@huangzj421 , Could you add in the README the instructions on how to run the model with these noisy conditions? As before, the script should automatically download and create the corresponding dataset. I would like to try myself if everything works correctly.

The usage is the same as the previous PR which you should only set wsj_root and output_root and it will download and generate data into output_root.

And, I am observing the following error for convtasnet-parallel-reverb.yaml:

Please note that I tried convtasnet-parallel.yaml, and that seems to work fine. Correction: Actually, I am also observing that the is stuck at 80, and it doesn't go down for `convtasnet-parallel.yaml'. In the previous PR, I tried and it the error was going down as expected.. I am not sure what's happening here..

I am sorry that I don't understand the "Correction" part you said. Also the test check failed but I don't know why.

Actually, if the dataset is already created, we should not require wsj_root again, right?

What I mean with the 'correction' part is that, when I run the script, (with convtasnet_parallel.yaml, the error does not go down. It is stuck at 80.

Actually, if the dataset is already created, we should not require wsj_root again, right?

Yes, if the dataset is done and dynamic mixing don't need it in the hparams["base_folder_dm"].

OK, let me check it.

Yes, but we would also not need wsj_root if the dataset is already created.

For convtasnet-parallel-noisy.yaml I am getting this error. You can see the command I used also here.

I have corrected the data generation scripts and now these should work fine.

Ok, can you push your code after this correction in the data generation script?

For convtasnet-parallel-noisy.yaml I am getting this error. You can see the command I used also here.

I have corrected the data generation scripts and now these should work fine.

Ok, can you push your code after this correction in the data generation script?

Oh, it doesn't need to push cause I just corrected in my repo.

For convtasnet-parallel-noisy.yaml I am getting this error. You can see the command I used also here.

I have corrected the data generation scripts and now these should work fine.

Ok, can you push your code after this correction in the data generation script?

Oh, it doesn't need to push cause I just corrected in my repo.

I am now getting this error:

For convtasnet-parallel-noisy.yaml I am getting this error. You can see the command I used also here.

I have corrected the data generation scripts and now these should work fine.

Ok, can you push your code after this correction in the data generation script?

Oh, it doesn't need to push cause I just corrected in my repo.

I am now getting this error:

It seems that the download link is invalid. I am trying to search another one.

What I mean with the 'correction' part is that, when I run the script, (with convtasnet_parallel.yaml, the error does not go down. It is stuck at 80.

What is the unit of 80? 80%?

Hi @ycemsubakan , I have fixes some errors in train.py and the data generation scripts in my repo. After you remove the previous BinauralWSJ0Mix folder and run train.py again, it will download automatically and train smoothly.
But I still don't know the 80 stuck you said and pytest check failure. Thanks.

The noisy version seems to work after your last push. (the data generation)
But the loss is still kind of stuck:

The noisy version seems to work after your last push. (the data generation)
But the loss is still kind of stuck:

It was weired cause I just trained and the loss goes down well:

My command was:
CUDA_VISIBLE_DEVICES=3,5,6,7 python -m torch.distributed.launch --nproc_per_node=4 train.py hparams/convtasnet-parallel.yaml --data_folder /mnt/test/ --wsj_root /mnt/wsj/ --distributed_launch --distributed_backend='nccl'
Your loss was too big, did you use the dynamic mixing?

The noisy version seems to work after your last push. (the data generation)
But the loss is still kind of stuck:

It was weired cause I just trained and the loss went down well:  My command was: CUDA_VISIBLE_DEVICES=3,5,6,7 python -m torch.distributed.launch --nproc_per_node=4 train.py hparams/convtasnet-parallel.yaml --data_folder /mnt/test/ --wsj_root /mnt/wsj/ --distributed_launch --distributed_backend='nccl' Your loss was too big, did you use the dynamic mixing?

No, I am not using dynamic mixing. I am training on a single gpu. Can you try training on a single gpu?

The noisy version seems to work after your last push. (the data generation)
But the loss is still kind of stuck:

It was weired cause I just trained and the loss went down well:  My command was: CUDA_VISIBLE_DEVICES=3,5,6,7 python -m torch.distributed.launch --nproc_per_node=4 train.py hparams/convtasnet-parallel.yaml --data_folder /mnt/test/ --wsj_root /mnt/wsj/ --distributed_launch --distributed_backend='nccl' Your loss was too big, did you use the dynamic mixing?

No, I am not using dynamic mixing. I am training on a single gpu. Can you try training on a single gpu?

It was not so big as well:

The noisy version seems to work after your last push. (the data generation)
But the loss is still kind of stuck:

It was weired cause I just trained and the loss went down well:  My command was: CUDA_VISIBLE_DEVICES=3,5,6,7 python -m torch.distributed.launch --nproc_per_node=4 train.py hparams/convtasnet-parallel.yaml --data_folder /mnt/test/ --wsj_root /mnt/wsj/ --distributed_launch --distributed_backend='nccl' Your loss was too big, did you use the dynamic mixing?

No, I am not using dynamic mixing. I am training on a single gpu. Can you try training on a single gpu?

It was not so big as well:

Hm.. weird.. I am not sure why this is happening when I try. This doesn't happen with other recipes. I'll try to understand what's happening.

The noisy version seems to work after your last push. (the data generation)
But the loss is still kind of stuck:

It was weired cause I just trained and the loss went down well:  My command was: CUDA_VISIBLE_DEVICES=3,5,6,7 python -m torch.distributed.launch --nproc_per_node=4 train.py hparams/convtasnet-parallel.yaml --data_folder /mnt/test/ --wsj_root /mnt/wsj/ --distributed_launch --distributed_backend='nccl' Your loss was too big, did you use the dynamic mixing?

No, I am not using dynamic mixing. I am training on a single gpu. Can you try training on a single gpu?

It was not so big as well:

Hm.. weird.. I am not sure why this is happening when I try. This doesn't happen with other recipes. I'll try to understand what's happening.

Maybe you could remove all the dataset and train it again?

Yes, I already tried that. I generated the dataset from scratch.

Hi @ycemsubakan, do you have any updates?

@huangzj421 No, I will try to get to it this week.

@huangzj421 No, I will try to get to it this week.

Okay, thanks!

With convtasnet-parallel-noise.yaml, I observed the following error. Do you see it also?

With convtasnet-parallel-noise.yaml, I observed the following error. Do you see it also?

No, I guess you should update the automatic downloaded data generation scripts from https://github.com/huangzj421/Binaural-WSJ0Mix or you can remove the old version in your data_folder.

With convtasnet-parallel-noise.yaml, I observed the following error. Do you see it also?

No, I guess you should update the automatic downloaded data generation scripts from https://github.com/huangzj421/Binaural-WSJ0Mix or you can remove the old version in your data_folder.

I see.. It was working earlier. But, this could be an issue for people who use this recipe in the future. Can you automatically check if the folders are correct, and then if not, you can either automatically fix, or at least you need to give an error message so that people know that they should delete the folder, and create a new one.

@huangzj421 , all of the .yaml files for me now work. For some reason when I tried with my conda environment, as I mentioned the training was not going down. But with a standard virtual environment it works fine.
I think you can do the version check for the dataset in a separate PR, and if everything is fine with @mravanelli, we can merge.

@huangzj421 , all of the .yaml files for me now work. For some reason when I tried with my conda environment, as I mentioned the training was not going down. But with a standard virtual environment it works fine.
I think you can do the version check for the dataset in a separate PR, and if everything is fine with @mravanelli, we can merge.

That's great, thanks! 'Separate PR' means opening a new PR?

@huangzj421 , all of the .yaml files for me now work. For some reason when I tried with my conda environment, as I mentioned the training was not going down. But with a standard virtual environment it works fine.
I think you can do the version check for the dataset in a separate PR, and if everything is fine with @mravanelli, we can merge.

That's great, thanks! 'Separate PR' means opening a new PR?

Yes. If you already have a solution for dataset versioning, feel free to push it here. If you think it's going to take time, we can open a new PR, after we merge this one.

@huangzj421 , all of the .yaml files for me now work. For some reason when I tried with my conda environment, as I mentioned the training was not going down. But with a standard virtual environment it works fine.
I think you can do the version check for the dataset in a separate PR, and if everything is fine with @mravanelli, we can merge.

That's great, thanks! 'Separate PR' means opening a new PR?

Yes. If you already have a solution for dataset versioning, feel free to push it here. If you think it's going to take time, we can open a new PR, after we merge this one.

Okay, got it. But some checks of PR failed, how can we merge it?

@huangzj421 , all of the .yaml files for me now work. For some reason when I tried with my conda environment, as I mentioned the training was not going down. But with a standard virtual environment it works fine.
I think you can do the version check for the dataset in a separate PR, and if everything is fine with @mravanelli, we can merge.

That's great, thanks! 'Separate PR' means opening a new PR?

Yes. If you already have a solution for dataset versioning, feel free to push it here. If you think it's going to take time, we can open a new PR, after we merge this one.

Okay, got it. But some checks of PR failed, how can we merge it?

The checks are failing because of a general problem. It will be fixed soon.

@huangzj421 , all of the .yaml files for me now work. For some reason when I tried with my conda environment, as I mentioned the training was not going down. But with a standard virtual environment it works fine.
I think you can do the version check for the dataset in a separate PR, and if everything is fine with @mravanelli, we can merge.

That's great, thanks! 'Separate PR' means opening a new PR?

Yes. If you already have a solution for dataset versioning, feel free to push it here. If you think it's going to take time, we can open a new PR, after we merge this one.

Okay, got it. But some checks of PR failed, how can we merge it?

The checks are failing because of a general problem. It will be fixed soon.

Okay, thank you!

Hi @mravanelli , do you have time to check this PR? Cem has reviewed it and everything is fine. Thanks.

Everything seems fine to me. I ran the code one other time. I did some updates to README. I will merge once the tests pass.


Archive command

@droserasprout this

@droserasprout
I added a new command for CLI: add a new label.


This page blog/_posts/2022-02-17-updated-dockershim-faq.md has no Chinese version

This is a Bug Report
This page blog/_posts/2022-02-17-updated-dockershim-faq.md has no Chinese version
Problem:
This page blog/_posts/2022-02-17-updated-dockershim-faq.md has no Chinese version
Proposed Solution:
Translate Chinese version for blog/_posts/2022-02-17-updated-dockershim-faq.md
Page to Update:
https://kubernetes.io/blog/2022/02/17/dockershim-faq/
Comments
/language zh
/assign

/assign


Run lots of commands in parallel?

Is there a forum or mailing list for asking usage questions?
I'm new to toil and am trying to work out how to do some simple initial things, like run the same command on thousands of different inputs, in parallel.
Based on the docs I tried this:
from toil.job import Job

def echo(job, message, memory="10M", cores=1, disk="10M"):
    job.fileStore.logToMaster("%s" % message)

j1 = Job.wrapJobFn(echo, "echo 1")
j2 = j1.addChildJobFn(echo, "echo 2")
j3 = j1.addChildJobFn(echo, "echo 3")
j4 = j1.addChildJobFn(echo, "echo 4")
...
j9997 = j1.addChildJobFn(echo, "echo 9997")
j9998 = j1.addChildJobFn(echo, "echo 9998")
j9999 = j1.addChildJobFn(echo, "echo 9999")
j10000 = j1.addChildJobFn(echo, "echo 10000")

if __name__=="__main__":
    options = Job.Runner.getDefaultOptions("./jobstore")
    options.logLevel = "INFO"
    Job.Runner.startToil(j1, options)

But this was very slow. How are inputs normally provided to toil scripts so that you have just 1 job definition (and no children), but have the system run the job on each of your inputs?

Hi Sendu, thank you for your interest in Toil.
Toil supports dynamic job creation through the use of job.addChildJobFn.
So to adjust your example:
from toil.job import Job

def start(job):
    for i in range(10,000):
        message = 'echo ' + str(i + 1)
	job.addChildJobFn(message)

def echo(job, message, memory="10M", cores=1, disk="10M"):
    job.fileStore.logToMaster("%s" % message)

if __name__=="__main__":
    options = Job.Runner.getDefaultOptions("./jobstore")
    options.logLevel = "INFO"
    Job.Runner.startToil(start, options)

I recommend taking a look at the toil-scripts repository for some non-trivial use cases which will show you how our group implements Toil in pipelines.
https://gitter.im/bd2k-genomics-toil/Lobby is our channel for discussing Toil.
Please re-open this issue if you feel your question was not addressed.

Hi, thanks for the suggestion, but I couldn't get your code to run without error 'assert self._batchSystem is not None'.
I tried this:
from toil.job import Job

def start(job):
    for i in range(10,000):
        message = 'echo ' + str(i + 1)
        job.addChildJobFn(echo, message)

def echo(job, message, memory="10M", cores=1, disk="10M"):
    job.fileStore.logToMaster("%s" % message)

if __name__=="__main__":
    parser = Job.Runner.getDefaultArgumentParser()
    options = parser.parse_args()
    Job.Runner.startToil(Job.wrapJobFn(start), options)

And while it runs to completion, it doesn't actually do the work (1 job, no echos).
Beyond the specifics of this example though, my question was if this was generally the right approach for running lots of commands? Is the optimal thing to do to end up calling addChildJobFn() lots of times in your script, one way or another?
And how long would you expect a script like this to take on a 24core machine? I think I'm doing something wrong, because it is taking >7hrs on my initial version of the script and still hasn't finished.


InternVL-Chat-V1.5 support

pleaseeeeee, InternVL-Chat-V1.5 surpasses many proprietary multi-modal models, very powerful, pleaseeeee.

Hi, Is InternVL-Chat-V1.5 suported now?

Hi, Is InternVL-Chat-V1.5 suported now?

Hi @AdamzNV @ncomly-nvidia  @juney-nvidia , would please add some comments here?

We don't support this model yet. According to download statistics from Hugging Face, its popularity has been declining for the past half month.

mark

mark

mark

We don't support this model yet. According to download statistics from Hugging Face, its popularity has been declining for the past half month.
@AdamzNV
Please take a look at this ranking list. The score of the InternVL model is in the top 2.
https://rank.opencompass.org.cn/leaderboard-multimodal/?m=REALTIME

Can try: https://github.com/NetEase-Media/grps_trtllm

Hi @AmazDeng    we just enabled internvl2 supporting. do u still have further issue or question now? If not, we'll close it soon.

@nv-guomingz Wow, that looks great

Hi @AmazDeng we just enabled internvl2 supporting. do u still have further issue or question now? If not, we'll close it soon.

Thank you for your work. Could you please provide the link to the relevant documentation?

Hi @AmazDeng we just enabled internvl2 supporting. do u still have further issue or question now? If not, we'll close it soon.

@nv-guomingz Thank you for your work. Could you please provide the link to the relevant documentation?

https://github.com/NVIDIA/TensorRT-LLM/tree/main/examples/multimodal#internvl2

Hi @AmazDeng we just enabled internvl2 supporting. do u still have further issue or question now? If not, we'll close it soon.

@nv-guomingz Thank you for your work. Could you please provide the link to the relevant documentation?

https://github.com/NVIDIA/TensorRT-LLM/tree/main/examples/multimodal#internvl2

@nv-guomingz
I checked the documentation, and tensorrt-llm only supports InternVL2-1B to InternVL2-26B. So, does tensorrt-llm support InternVL2-40B?

https://github.com/NVIDIA/TensorRT-LLM/tree/main/examples/multimodal#internvl2

@nv-guomingz I checked the documentation, and tensorrt-llm only supports InternVL2-1B to InternVL2-26B. So, does tensorrt-llm support InternVL2-40B?

I'm not the owner of this model but I think 40B should be supported if it's just a large varaint of InternVL2.


Cannot Delete World

I accidentally created a new survival world with multiverse and now it seems there is no way to get rid of it.
I have tried unloading it with mv unload worldname and got the error.
"Error trying to unload world 'worldname'"
Then I tried mv remove worldname and got:
Hmm Multiverse does not know about this world but it's loaded in memory.
To unload it using multiverse, use:
/mv import worldname NORMAL
Error trying to unload world from config!
Trying mv import worldname NORMAL resulted in:
Multiverse already knows about 'worldname'!
Then I tried mv delete worldname and then mvconfirm and got:
World 'worldname' could not be unloaded.  Is it a default world?
World could NOT be deleted.
So I'm at a loss, what should I try next?

How do you turn off default?

This was a long time ago but iirc the default world is listed in server.proporties and you need to change it to another world so that multiverse can delete it.

What if you dont have access to server.properties or the world file?

i also have the same problem. Multiverse keeps regenerating the map. it is not set to default. i deleted the world files, removed the data block from world.yml and restarting the server. no progress.


[Suggestion] Use the cpp command (C Pre Processor)

I recently wanted to get rid of the cruft from my config.h removing all the conditional lines. I instinctively used cpp feeding it patches.h for the macros and telling it to retain comments to get the desired result.
I ran something like this:
cpp config.h.old -imacros patches.h -C -o config.h
I then realized I couldve used this script and out of curiosity I checked the implementation.
IDK if this project is actively developed, but perhaps the ginormous awk program can be shortened with cpp?

Thanks for the suggestion, and the tip. Yes I think the whole script can be simplified with this so I shall have a closer look at my earliest convenience.
I was actually looking for something like this back when I wrote the finalizer but didn't come across cpp in my searches, hence the rather complicated awk script.
At first glance I don't foresee any complications using cpp for the bulk work.

I have had a closer look and using cpp is not that straightforward as I first thought.
The key is that we will want to preprocess only the directives that are present in patches.h and leave everything else as-is. Using cpp I end up with a dwm.c that has more than 24K lines including everything from /usr/include/X11/Xft/Xft.h and all related libraries.
From the man page:

The cpp command expects two file names as arguments, infile and outfile. The preprocessor reads infile together with any other file s it specifies with #include.  All the output generated by the combined input files is written in outfile.

I didn't see any way around this based on the command line options. Possibly it might be possible with another preprocessor tool. I tried m4 but that is not designed for this.


Unable to pip install rerun-sdk on Amazon Linux 2

There are no built distributions available to install on Amazon Linux 2. I'm currently using conda-provided Python, but using yum-provided Python yields the same results.
I  don't understand this very well, but I think the crux of the issue is that rerun-sdk only offers builds for manylinux-2.31 and the latest version available on Amazon Linux 2 is manylinux 2.26.
Excerpt from pip debug --verbose
  cp38-abi3-manylinux_2_26_x86_64
  cp38-abi3-manylinux_2_25_x86_64
  cp38-abi3-manylinux_2_24_x86_64
  cp38-abi3-manylinux_2_23_x86_64
  cp38-abi3-manylinux_2_22_x86_64
  cp38-abi3-manylinux_2_21_x86_64
  cp38-abi3-manylinux_2_20_x86_64
  cp38-abi3-manylinux_2_19_x86_64
  cp38-abi3-manylinux_2_18_x86_64
  cp38-abi3-manylinux_2_17_x86_64
  cp38-abi3-manylinux2014_x86_64
  cp38-abi3-manylinux_2_16_x86_64
  cp38-abi3-manylinux_2_15_x86_64
  cp38-abi3-manylinux_2_14_x86_64
  cp38-abi3-manylinux_2_13_x86_64
  cp38-abi3-manylinux_2_12_x86_64
  cp38-abi3-manylinux2010_x86_64
  cp38-abi3-manylinux_2_11_x86_64
  cp38-abi3-manylinux_2_10_x86_64
  cp38-abi3-manylinux_2_9_x86_64
  cp38-abi3-manylinux_2_8_x86_64
  cp38-abi3-manylinux_2_7_x86_64
  cp38-abi3-manylinux_2_6_x86_64
  cp38-abi3-manylinux_2_5_x86_64
  cp38-abi3-manylinux1_x86_64

Linux Distro
$ cat /etc/os-release
NAME="Amazon Linux"
VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora"
VERSION_ID="2"
PRETTY_NAME="Amazon Linux 2"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
HOME_URL="https://amazonlinux.com/"
SUPPORT_END="2025-06-30"

Pip Install
$ pip install -vv rerun-sdk
Using pip 24.0 from /opt/conda/lib/python3.10/site-packages/pip (python 3.10)
Defaulting to user installation because normal site-packages is not writeable
Created temporary directory: /tmp/pip-build-tracker-hi6vyt8x
Initialized build tracking at /tmp/pip-build-tracker-hi6vyt8x
Created build tracker: /tmp/pip-build-tracker-hi6vyt8x
Entered build tracker: /tmp/pip-build-tracker-hi6vyt8x
Created temporary directory: /tmp/pip-install-geq6iv0b
Created temporary directory: /tmp/pip-ephem-wheel-cache-srl7omw3
1 location(s) to search for versions of rerun-sdk:
* https://pypi.org/simple/rerun-sdk/
Fetching project page and analyzing links: https://pypi.org/simple/rerun-sdk/
Getting page https://pypi.org/simple/rerun-sdk/
Found index url https://pypi.org/simple/
Looking up "https://pypi.org/simple/rerun-sdk/" in the cache
Request header has "max_age" as 0, cache bypassed
Starting new HTTPS connection (1): pypi.org:443
https://pypi.org:443 "GET /simple/rerun-sdk/ HTTP/1.1" 304 0
Fetched page https://pypi.org/simple/rerun-sdk/ as application/vnd.pypi.simple.v1+json
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_10_12_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/f0/a3/e25cf3fe609ede853794206c668997948d7b3ceb6371675fb39bcceea022/rerun_sdk-0.17.0a4-cp38-abi3-macosx_10_12_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_11_0_arm64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/07/9c/bab535affb0bb44bb20c111bd92abc4c8a1f8a2c08a681f2464e394b1b41/rerun_sdk-0.17.0a4-cp38-abi3-macosx_11_0_arm64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_aarch64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/95/46/e8f3ae3caf1eb35db9720481deb2ea8e839723a97969cde4d4fa84c4a57e/rerun_sdk-0.17.0a4-cp38-abi3-manylinux_2_31_aarch64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/06/23/f74fdaaefa401cf5c4b8b7a740ccca61c9976752ce2db7cff2daa10a5ee6/rerun_sdk-0.17.0a4-cp38-abi3-manylinux_2_31_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/eb/7e/3ab317e966717dd2d2171371c8bc5e94266e6c8d3bf126e2bba3c60af458/rerun_sdk-0.17.0a4-cp38-abi3-win_amd64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_10_12_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/4d/c7/00fee180b02a06388f209c3370ac3ab3f061b7713e15cddac5b5b0b26fbe/rerun_sdk-0.17.0a6-cp38-abi3-macosx_10_12_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_11_0_arm64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/b0/df/3c3753be7f5f8c2dc5912f7887977a1bbca2ab500ee227aad28b47a8b97b/rerun_sdk-0.17.0a6-cp38-abi3-macosx_11_0_arm64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_aarch64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/00/a5/a41e426d5e75070a6e652bc5aa26408334cdcaa31e1fe21d26c76260064c/rerun_sdk-0.17.0a6-cp38-abi3-manylinux_2_31_aarch64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/da/47/39be8a1370ab5ecb8aa0ed68ff18620f0ccbd3c2e895bdee7130b52e80ce/rerun_sdk-0.17.0a6-cp38-abi3-manylinux_2_31_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/ad/0f/7e7c8631cd283d362db70d124e32a55d9a2f63e68f45710b6ee975ce524f/rerun_sdk-0.17.0a6-cp38-abi3-win_amd64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_10_12_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/22/3c/a622d5288bd9cb23be5eac00fd2315325e0114227257c5b1c7df74cf8964/rerun_sdk-0.17.0a8-cp38-abi3-macosx_10_12_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_11_0_arm64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/48/16/87ec7132c060dd7bd55b984b9fc5946610d21de49877f9dd260ce8972ffb/rerun_sdk-0.17.0a8-cp38-abi3-macosx_11_0_arm64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_aarch64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/91/f3/499d7eb28c6689ae3cd483d9d7c080dfc18cd5505e93a470d761d117d27a/rerun_sdk-0.17.0a8-cp38-abi3-manylinux_2_31_aarch64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/02/8c/7aa354fefd9227494ae9d8ddc54770dedd4399d08eeba1b06bba92b73769/rerun_sdk-0.17.0a8-cp38-abi3-manylinux_2_31_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/b3/63/18af31ae323b6bfb73d84916da7a1c1e37cb2f7df3c7933b32ec49f93506/rerun_sdk-0.17.0a8-cp38-abi3-win_amd64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_10_12_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/14/e6/835e7ecce6d52fdf956f916852eeaf149cc5bf92dbd341046d8edc17d2f0/rerun_sdk-0.17.0a9-cp38-abi3-macosx_10_12_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_11_0_arm64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/a1/7e/00f97b8ab1ed447e47de52b980bee10254a1e4d13cac16e9995bc26d0a58/rerun_sdk-0.17.0a9-cp38-abi3-macosx_11_0_arm64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_aarch64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/f7/ad/0a82e791f53009000b4ebfc14989ce9b818443a0d9f3767134977cc5ee74/rerun_sdk-0.17.0a9-cp38-abi3-manylinux_2_31_aarch64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/b1/df/5da1a5786f3478fb5709bb6ad64e0a8582fb223da3a2d9474d22a29d96cf/rerun_sdk-0.17.0a9-cp38-abi3-manylinux_2_31_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/c5/5c/2ca4abafefa7df8a47d04a9b04b46641fdef31ac7bc4ccbdd38889fbad5c/rerun_sdk-0.17.0a9-cp38-abi3-win_amd64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_10_12_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/ac/91/036d9b087fc49aeb4882d50f6b1ffd46ef6df35ed9a5b42801ce98d2f4ae/rerun_sdk-0.17.0rc1-cp38-abi3-macosx_10_12_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_11_0_arm64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/be/c9/0725a9958d0a6d2cab54b1cf8750dd4561f81d382872842ed7b93d9d80d8/rerun_sdk-0.17.0rc1-cp38-abi3-macosx_11_0_arm64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_aarch64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/6d/03/b9f85addbc081ac6d7d2571e3a67803e4287652df71385a8bb2aa6f3d8fb/rerun_sdk-0.17.0rc1-cp38-abi3-manylinux_2_31_aarch64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/bf/17/f55ca234897cd2f34afb345ee5db9c294b72c9b1f03392869ff94f3ffbc7/rerun_sdk-0.17.0rc1-cp38-abi3-manylinux_2_31_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/01/b3/c2b39a69652c5733fc9a8e1d6c3057c989124613e689cede52de1226456d/rerun_sdk-0.17.0rc1-cp38-abi3-win_amd64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_10_12_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/08/c6/898ea78c4b8acec3beeb82a22cc03f396f9ec851765ab3d4e9200ce4b8b2/rerun_sdk-0.17.0rc2-cp38-abi3-macosx_10_12_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_11_0_arm64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/4a/80/214469d707e9fc11f8d1a7abd98974d3dbbcfd00fbd3c8b41ae017ad6853/rerun_sdk-0.17.0rc2-cp38-abi3-macosx_11_0_arm64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_aarch64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/1d/3d/070cf8b5df104b66a49ba8365f19d9b7f84cfe8791b66ad16339f9fffb92/rerun_sdk-0.17.0rc2-cp38-abi3-manylinux_2_31_aarch64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/3a/7a/ce7fc1c23edd0a2710eff192825a664201321831d7a8d903cb6358ed6327/rerun_sdk-0.17.0rc2-cp38-abi3-manylinux_2_31_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/81/b0/1fd1d5cb00a595342ed06ea00b68150ef8a26a56622ffe7916baf928ac14/rerun_sdk-0.17.0rc2-cp38-abi3-win_amd64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_10_12_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/d6/17/42d0d7ff24c009f7a3c7a95570ceea4f4784a5ff69e116e06a74a906d099/rerun_sdk-0.17.0rc3-cp38-abi3-macosx_10_12_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_11_0_arm64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/36/79/4c5bbc0b7aad687477c865c139a5d2b5952e432a9ca30c7f6e135ea5c745/rerun_sdk-0.17.0rc3-cp38-abi3-macosx_11_0_arm64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_aarch64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/41/db/47c9a6079f86cc9499e69ed87e57f18e790ca0b0a3064ab1c2d18f91bda3/rerun_sdk-0.17.0rc3-cp38-abi3-manylinux_2_31_aarch64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/5a/ae/7cbf5d776df480e0c1d03670aa99856f735cbe82a0e217623327bcb5a17a/rerun_sdk-0.17.0rc3-cp38-abi3-manylinux_2_31_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/b7/8c/951738b660a5efc92d626c3b5cf88712ec0cb12d3641f57b74e936fc1960/rerun_sdk-0.17.0rc3-cp38-abi3-win_amd64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_10_12_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/30/5f/ce02381b9d7e1e14f60c421c76dce12b7d823690181784780b30266017b1/rerun_sdk-0.17.0-cp38-abi3-macosx_10_12_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-macosx_11_0_arm64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/b7/c5/d47ba7b774bc563aa3c07ba500dd304ea24b31fe438e10ea9ad5e10ffe17/rerun_sdk-0.17.0-cp38-abi3-macosx_11_0_arm64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_aarch64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/87/0a/b5fe1ffea700eeaa8d28817a92ad3cb4a7d56dc4af45de76ea412cfc5cd5/rerun_sdk-0.17.0-cp38-abi3-manylinux_2_31_aarch64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-manylinux_2_31_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/d9/74/6c1ff0c8dbe6da09ceb5ea838a72382fa3131ef6bb9377a30003299743fa/rerun_sdk-0.17.0-cp38-abi3-manylinux_2_31_x86_64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
  Skipping link: none of the wheel's tags (cp38-abi3-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/8c/28/92423fe9673b738c180fb5b6b8ea4203fe4b02c1d20b06b7fae79d11cc24/rerun_sdk-0.17.0-cp38-abi3-win_amd64.whl (from https://pypi.org/simple/rerun-sdk/) (requires-python:<3.13,>=3.8)
Skipping link: not a file: https://pypi.org/simple/rerun-sdk/
Given no hashes to check 0 links for project 'rerun-sdk': discarding no candidates
ERROR: Could not find a version that satisfies the requirement rerun-sdk (from versions: none)
ERROR: No matching distribution found for rerun-sdk
Exception information:
Traceback (most recent call last):
  File "/opt/conda/lib/python3.10/site-packages/pip/_vendor/resolvelib/resolvers.py", line 397, in resolve
    self._add_to_criteria(self.state.criteria, r, parent=None)
  File "/opt/conda/lib/python3.10/site-packages/pip/_vendor/resolvelib/resolvers.py", line 174, in _add_to_criteria
    raise RequirementsConflicted(criterion)
pip._vendor.resolvelib.resolvers.RequirementsConflicted: Requirements conflict: SpecifierRequirement('rerun-sdk')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/conda/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 95, in resolve
    result = self._result = resolver.resolve(
  File "/opt/conda/lib/python3.10/site-packages/pip/_vendor/resolvelib/resolvers.py", line 546, in resolve
    state = resolution.resolve(requirements, max_rounds=max_rounds)
  File "/opt/conda/lib/python3.10/site-packages/pip/_vendor/resolvelib/resolvers.py", line 399, in resolve
    raise ResolutionImpossible(e.criterion.information)
pip._vendor.resolvelib.resolvers.ResolutionImpossible: [RequirementInformation(requirement=SpecifierRequirement('rerun-sdk'), parent=None)]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/conda/lib/python3.10/site-packages/pip/_internal/cli/base_command.py", line 180, in exc_logging_wrapper
    status = run_func(*args)
  File "/opt/conda/lib/python3.10/site-packages/pip/_internal/cli/req_command.py", line 245, in wrapper
    return func(self, options, args)
  File "/opt/conda/lib/python3.10/site-packages/pip/_internal/commands/install.py", line 377, in run
    requirement_set = resolver.resolve(
  File "/opt/conda/lib/python3.10/site-packages/pip/_internal/resolution/resolvelib/resolver.py", line 104, in resolve
    raise error from e
pip._internal.exceptions.DistributionNotFound: No matching distribution found for rerun-sdk
Remote version of pip: 24.2
Local version of pip:  24.0
Was pip installed by pip? False
Removed build tracker: '/tmp/pip-build-tracker-hi6vyt8x'

pip debug.txt

Since you're using conda-provided python, is it an option to also use conda-provided rerun? Our conda packages are generally more portable due to how the conda build tooling works.

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Yes, I've used the conda installation successfully, but the goal is to remove dependence on conda from our deployment because we have a weird mixture of conda and pip right now that is becoming pain to sustain.

same issue here but on rocky linux
NAME="Rocky Linux"
VERSION="8.9 (Green Obsidian)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="8.9"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Rocky Linux 8.9 (Green Obsidian)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:8:GA"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
SUPPORT_END="2029-05-31"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-8"
ROCKY_SUPPORT_PRODUCT_VERSION="8.9"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.9"

using UV for dependency resolution - ideally wouldn't need conda just for rerun


How to pass 'vector<vector>' parameter?

// values is a Uint8Array[] type
this.txb.pure.vector('vector<u8>', [].slice.call(values))

Does not work.  And how to pass 'vector<vector<u8>>' parameter to MoveCall?

I assume you're using TypeScript SDK: https://sdk.mystenlabs.com/typescript/transaction-building/basics#pure-values


Zoom out and set this page to 90 percent using transform in css

Hey @Anu27n please assign this to me I would like to work on this task

@Buddha-11 Assigned please star the repo.


python310Packages.openapi-core: 0.16.2 -> 0.16.3

Description of changes
https://github.com/p1c2u/openapi-core/releases/tag/0.16.3

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 207009 run on x86_64-linux 1

2 packages built:

python310Packages.openapi-core
python39Packages.openapi-core


thumbnail_*_with_opts with default options cause error

Hi @augustocdias ,
here is the code of thumbnail_buffer_with_opts:
    let buffer = std::fs::read("any.jpeg").expect("hello world");
    let buffer_options = ops::ThumbnailBufferOptions::default();
    let resized = ops::thumbnail_buffer_with_opts(&buffer.as_slice(), 100, &buffer_options).expect(app.error_buffer().unwrap());

thumbnail_with_opts
let options = ops::ThumbnailOptions::default();
let resized = ops::thumbnail_with_opts("any.jpeg", 100, &options).expect(app.error_buffer().unwrap());

thread 'main' panicked at 'vips__file_read: error reading from file ""
profile_load: unable to load profile ""

vips-8.10.2-Mon Oct 12 16:43:59 UTC 2020
Could it be caused by the import_profile and export_profile?
Thanks

oh, it's duplicated as #5
and the import_profile: "sRGB", export_profile: "sRGB" works


tsc includes previous output in result when allowJs is enabled and "exclude" is non-empty

TypeScript Version: 2.7.0-dev.20171222
Code
For easy access, clone this gist: https://gist.github.com/WasabiFan/6922d6eb6224945ac809c216fdc37089
test.ts:
// Source code here

tsconfig.json:
{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "outDir": "out",
    "allowJs": true
  },
  "exclude": [
    "node_modules"
  ]
}

Removing the exclude block or disabling allowJs avoids the issue.
Note that this is an easy state to get into: in my case, I generated a VSCode extension with their official templates and then enabled allowJs. I didn't realize what was going on until my PC ran out of RAM, as it automatically ran the watch task and the depth grew every time I saved.
Expected behavior:
I can compile the project with tsc as many times as I'd like.
Actual behavior:
PS D:\...> git clone https://gist.github.com/WasabiFan/6922d6eb6224945ac809c216fdc37089 tsc-recursion-demo-gist
Cloning into 'tsc-recursion-demo-gist'...
remote: Counting objects: 7, done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 7 (delta 1), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (7/7), done.
PS D:\...> cd .\tsc-recursion-demo-gist\
PS D:\...\tsc-recursion-demo-gist> tsc -p .
PS D:\...\tsc-recursion-demo-gist> tsc -p .
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/test.js' because it would overwrite input file.
PS D:\...\tsc-recursion-demo-gist> tsc -p .
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/out/test.js' because it would overwrite input file.
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/test.js' because it would overwrite input file.
PS D:\...\tsc-recursion-demo-gist> tsc -p .
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/out/out/test.js' because it would overwrite input file.
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/out/test.js' because it would overwrite input file.
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/test.js' because it would overwrite input file.
PS D:\...\tsc-recursion-demo-gist> tsc -p .
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/out/out/out/test.js' because it would overwrite input file.
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/out/out/test.js' because it would overwrite input file.
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/out/test.js' because it would overwrite input file.
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/test.js' because it would overwrite input file.
PS D:\...\tsc-recursion-demo-gist> tsc -p .
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/out/out/out/out/test.js' because it would overwrite input file.
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/out/out/out/test.js' because it would overwrite input file.
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/out/out/test.js' because it would overwrite input file.
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/out/test.js' because it would overwrite input file.
error TS5055: Cannot write file 'D:/.../tsc-recursion-demo-gist/out/test.js' because it would overwrite input file.

The fix (and the best option) is to exclude the output directory. But given that existing templates don't do that, I think this is a significant issue. I don't understand why this doesn't happen when the exclude block is removed; I assume there's an internal safety to prevent this problem that's overridden.

We automatically exclude the outDir as well as node_modules, but given an explicit list of exclude files, I'm not sure what we can do to opt out of that behavior.

Is there something that prevents you from always excluding the outDir (appending it to the exclude list)? I can't think of a scenario where including the output directory would be the "right" behavior, but I don't have visibility into the whole product so I could be missing something.

I'll need to chat with @mhegazy to recall the full context on this topic.


Added Unit Type and Unit Term

Added both the Unit type () and the Unit term (). I wasn't sure which one I needed so I made both just in case.
Testable via:
*Main> runTest "Tests/UnitTest.hs"
Output:
---------------------------- Type Checked Program ---------------------------
data Number = Succ Number | Zero
/\t_uC.
  \(i_u4 :: t_uC).
    let f_u3 : () -> Number -> Number
             = \(x_u5 :: ()).
                 \(y_u6 :: Number).
                   y_u6
    in f_u3 () Zero
---------------------------- Elaborated Program ---------------------------
data Number = Succ Number | Zero
/\t_uC.
  \(i_u4 :: t_uC).
    let f_u3 : () -> Number -> Number
             = \(x_u5 :: ()).
                 \(y_u6 :: Number).
                   y_u6
    in f_u3 () Zero
Size: 125
------------------------------- Program Type ------------------------------
forall (t_uC : *). t_uC -> Number
------------------------------ Program Theory -----------------------------
{theory_super : [],
 theory_inst : [],
 theory_local : []}
-------------------------- System F Program Type --------------------------
forall t_uC. t_uC -> Number

Added both the Unit type () and the Unit term (). I wasn't sure which one I needed so I made both just in case.

Well, you either need neither or both, so you did the right thing :slightly_smiling_face:


Switch website to use Docsy theme

This is a Feature Request
What would you like to be added
Change the website from its existing home-grown(?) theme to use a new theme derived from Docsy.
Why is this needed
Adopting the Docsy theme provides:

better, automatically generated navigation (including when JavaScript is disabled)
a user experience tuned for technical documentation
improved switching between different Kubernetes versions

Comments
See PR #20874
/kind feature
/priority important-longterm

PR #20874 introduced a snag for the list of tasks: #21789


@svgr/webpack: make @babel/env an optional peer dependency

🚀 Feature Proposal
Move @babel/env from dependencies to peerDependencies with peerDependenciesMeta specifying that it is optional.
Motivation
@babel/env is a very heavy dependency, but isn't even used if babel: false is specified in the config. For projects which wish to manage their own babel config, being able to omit this would reduce the package installation time quite considerably.
Since the only place which uses it is already async, it would be easy to import the dependency using a dynamic import only once it is known that babel: false has not been specified.

Personally I would prefer to go even a step further and remove the automatic babel config entirely, instead specifying that users should include the loader as use: ['babel-loader', '@svgr/webpack'] (or whatever they are using), since this will match the rest of their config and is a familiar pattern (e.g. for css transpilers).

I agree, today Babel is not the only choice. I am OK to move out Babel and make it optional, we can release a major for that, it makes sens.


ExecuteMenuItem failed because there is no menu named 'Window/Hierarchy'

happens every time when i search for gameobject and press enter
Unity3d 2018.3.12f1
ExecuteMenuItem failed because there is no menu named 'Window/Hierarchy'
UnityEditor.EditorApplication:ExecuteMenuItem(String)
Haste.HasteWindow:OnReturn(Event) (at Assets/Haste/Editor/HasteWindow.cs:188)
Haste.HasteWindow:OnKeyDown(Event) (at Assets/Haste/Editor/HasteWindow.cs:321)
Haste.HasteWindow:OnEvent(Event) (at Assets/Haste/Editor/HasteWindow.cs:353)
Haste.HasteWindow:OnGUI() (at Assets/Haste/Editor/HasteWindow.cs:476)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Haste activates the hierarchy tab (in case it's hidden). The menu path must have changed. The string "Window/Hierarchy" should be replaced with whichever menu path opens the hierarchy. The code for that is here: Assets/Haste/Editor/Results/HasteHierarchyResult.cs#L119

ah right its moved here


Sort the Games in alphabetical order.

Can we have the games in the site sorted by alphabetical order or by platform (i.e., WINE/Proton & Linux Native) and then sort them alphabetically under the platform group?

The current sorting order of the games is actually very intentional and strategic. By putting very popular games at the top, it's almost guaranteed they will be looked at first, applying pressure on these studios to add support.
I'm open to having other sorting options that are non-default. If anyone would like to open a PR for that, feel free.

Wow! Thank you allowing various sorting methods and for the new look for the Web Site. It looks absolutely gorgeous and is very easily readable.


Can't turn off the line highlighting

I'd like the line number in the gutter to be highlighted, but not the text of the line itself.
I tried this, but it had no effect:
atom-text-editor::shadow {
  // The cursor line important to use rgba for opacity, also requires !important
  // to override any theme.
  .line.highlight-line {
    background: none !important;
  }
}

What did I miss?

This package doesn't actually highlight the gutter.

So, highlight-line doesn't highlight lines? Do you know what does?

It does highlight lines; but not the gutter. This package only deals with the line part in the picture below; and does nothing with the gutter.

Good! So why doesn't the example code turn off line highlighting?

It does (well the code in the screenshot uncommented).
But your theme might have styling on .cursor-line which gives a primitive highlight line. (Out at the moment and can't remember the exact class).

On 15 Nov 2015, at 12:37, Bob Rockefeller<EMAIL_ADDRESS>wrote:
Good! So why doesn't the example code turn off line highlighting?
—
Reply to this email directly or view it on GitHub.

OK! I see where it is. Thanks for the clue.


removed the 'plugins' direction from the plugins page.

removed the "plugins" direction from the plug-ins page.

Please remember to sign-off your commits


See if I can add suffic to generate api

Cuz I dont want to use domain Suffix in all my self written services

{
"$schema"<EMAIL_ADDRESS>"spaces": 2,
"generator-cli": {
"version": "7.1.0",
"generators": {
"v1": {
"generatorName": "typescript-angular",
"output": "#{cwd}/src/app/openapi-services/#{ext}/#{name}",
"inputSpec": "http://localhost:5126/Swagger/v1/swagger.json",
"removeOperationIdPrefix": true
}
}
}
}
since this is not working anyways, I might as well put a compile error in here, until they fixed it:
https://github.com/OpenAPITools/openapi-generator-cli/issues/690
(╯°□°）╯︵ ┻━┻

closed, because the project seems not maintained for it.


Installed Cyphondock in a aws Ubuntu instance, But still i am not able to load the cyphon graphical user interface.

Duplicate of https://github.com/dunbarcyber/cyphondock/issues/38.


Error 404: When request Azure resource at PublishContent, zipDeploy : Failed to use /home/runner/work/temp/temp_web_package...zip as ZipDeploy content

These github workflows have worked 2 years for us to deploy various python functions hundreds of times to azure and now are suddenly no longer reliable:
      - name: Publish Azure Function
        uses: Azure/functions-action@v1
        id: fa
        with:
          app-name: ${{ env.AZURE_FUNCTIONAPP_NAME }}
          package: ${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }}
          publish-profile: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }}

While debugging now we also tried v1.5.1, but no success with it either. Some more or less random restart/delete/disable may or may not help to resolve it (as described here https://github.com/microsoft/azure-pipelines-tasks/issues/18739#issuecomment-1905856749) but the issue comes back and then one can start the deployment over and over again and see the same error.
Here is how the github job log starts with debug logging:
Current runner version: '2.311.0'
Operating System
Runner Image
  Image: ubuntu-22.04
  Version: 20240116.3.0
  Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240116.3/images/ubuntu/Ubuntu2204-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240116.3
Runner Image Provisioner
  2.0.324.1

And this is how it fails:
##[debug]Deployment status: 0 'Building and Deploying '***-4e62-871a-d8bdc4ef87f0'.'. retry after 5 seconds
##[debug]setting affinity cookie ["ARRAffinity=****a443cf3f6c7c2e4daaee92c2062af1b69e3649bf26d43fe66fe700a7de;Path=/;HttpOnly;Secure;Domain=***.scm.azurewebsites.net","ARRAffinitySameSite=****443cf3f6c7c2e4daaee92c2062af1b69e3649bf26d43fe66fe700a7de;Path=/;HttpOnly;SameSite=None;Secure;Domain=***.scm.azurewebsites.net"]
##[debug][GET] [https://***.scm.azurewebsites.net:443/api/deployments/latest?deployer=GITHUB_ZIP_DEPLOY_FUNCTIONS_V1&time=2024-01-23_11-20-47Z](https://***.scm.azurewebsites.net/api/deployments/latest?deployer=GITHUB_ZIP_DEPLOY_FUNCTIONS_V1&time=2024-01-23_11-20-47Z)
##[debug]Could not parse response body.
##[debug]{}
Error: Failed to deploy web package to App Service.
Error: Execution Exception (state: PublishContent) (step: Invocation)
Error:   When request Azure resource at PublishContent, zipDeploy : Failed to use /home/runner/work/_temp/temp_web_package_8472975363497814.zip as ZipDeploy content
Error:     Failed to deploy web package to App Service.
Not Found (CODE: 404)
Error:       Error: Failed to deploy web package to App Service.
Not Found (CODE: 404)
    at Kudu.<anonymous> (/home/runner/work/_actions/Azure/functions-action/v1/lib/appservice-rest/Kudu/azure-app-kudu-service.js:235:41)
    at Generator.throw (<anonymous>)
    at rejected (/home/runner/work/_actions/Azure/functions-action/v1/lib/appservice-rest/Kudu/azure-app-kudu-service.js:6:65)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
Error: Deployment Failed!
##[debug]Node Action run completed with exit code 1

It does seem to finish the publishing though (as our version tag shows the new version) but it does not start the remaining steps of the deployment as it considers this step as failed.

This issue keeps occurring randomly for our deployments. :(

same here too. Microsoft fix this please!

@patelchandni @Hazhzeng any ideas how to solve this problem?

Same here

Same here, I have error but it's deploy

Any solutions inbound? Having the same issue with v1.5.0 and 1.5.1

Same thing here - the builds suddenly started failing after 2 years.
My workaround for now is use to https://github.com/Azure/webapps-deploy instead. Found the workaround in another related issue: https://github.com/Azure/functions-action/issues/213.
  - name: Deploy
    uses: azure/webapps-deploy@v2
    id: fa
    with:
      app-name: ${{ env.AZURE_FUNCTIONAPP_NAME }}
      package: '${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }}/build'
      publish-profile: ${{ secrets.AZURE_API_PUBLISH_PROFILE }}

Same issue here as well...

same issue here

same issue here!

Same issue here!

Any alternative solutions to propose ?

+1

Hello Allo,
I fixed the issue by resetting my

Redeploy my Azure Function
Generate the Github Action Worflow file from the portal

Hope this can help you !

+1

+1

Same issue here.

Hey this issue is still existing for me. The re-deploy mentioned previously is not working, is there any attention on this?

I got a similar error message in my workflow and have been trying to solve it for several days. I'm using RBAC instead of publish-profile, but maybe this still applies and helps someone:
I disconnected the leftover configuration in the functions Deployment center (menu in Azure portal), even though I was NOT deploying through it, but through GitHub runner with RBAC credentials.
No actual changes to the workflow itself or environment variables (I do have the WEBSITE_RUN_FROM_PACKAGE=1 there since the beginning though.)

Hi.
I noticed, from the portal, that my function was not able to locate the workflow file in /.github/workflows/.
The file was there, but had been converted to lower-case letters, and Azure expected some camel-case version of the filename. I changed the filename in the repository, and this solved the issue for me.

Hi,
I'm having the same issue. Sometimes works other not without make any changes.
Using version 1.5.2 and RBAC for auth.
Nothing yet?

Any updates on this?

These are app specific issues, so please open a support ticket from Azure Portal if the issue still exists.


Change ruby version for Kernel#trust, #untrust and #untrusted

#1016
Feature #16131

The following deprecated methods are removed.
[ ] Kernel#trust, Kernel#untrust, Kernel#untrusted?

I broke my #1024 branch so I created new one

Could you please follow the @eregorn's suggestion and also check that respond_to? returns false in Ruby 3.2?
I've found several similar cases in the existing specs when some deprecated method is removed:

https://github.com/ruby/spec/blob/master/core/kernel/match_spec.rb#L25-L28
https://github.com/ruby/spec/blob/master/core/encoding/replicate_spec.rb#L70-L74

Thank you for the specs!