Dockerfile to create base image.

What changes were proposed in this pull request?
Just adding a Dockerfile.
How was this patch tested?
docker build . in my local.
Please review http://spark.apache.org/contributing.html before opening a pull request.

I had initially copied all the poms in separately, but it (a) there are a lot of POMs in this file, each necessitating its own COPY command and layer, and (b), frankly, asset resolution is not the longest part of this build we're going to be building this so infrequently, I don't feel the minor cacheablility validates the larger image, increased Dockerfile management, etc.


CSV import float precision

I have the following csv file:
Rom;80;95;0.1;2019-07-02
Paris;75;90;0.2;2019-07-02
Madrid;90;120;0;2019-07-02
When I copy it to my weather table, floating point numbers are not identical to the input:
query = "CREATE TABLE weather (city VARCHAR, temp_lo INTEGER, temp_hi INTEGER, prcp REAL, date DATE);"
cursor.execute(query)
cursor.execute("COPY weather FROM 'C:\\Users\\multmeierj\\weather.csv' DELIMITER ';';")
cursor.execute("SELECT * FROM weather").fetchall()
[['Rom', 80, 95, 0.10000000149011612, 737607], ['Paris', 75, 90, 0.20000000298023224, 737607], ['Madrid', 90, 120, 0.0, 737607]]
The csv imports correctly in R and pandas, is this related to numpy in the background?
EDIT: I guess this is no really a bug, but depends on python's handling of floating numbers
`

I think its a printing issue. But we will double check.

Hey it works on windows ^^

This is likely just related to floating point precision, as "REAL" is a 4-byte float which cannot represent numbers like 0.2 accurately. Switching to DOUBLE might reduce the issue, but we need DECIMAL support to fix this properly.


fix: update redeem spec

there is no longer a punishment fee that goes to the fee pool - it all goes to the user now
renamed some vars

Can you also reference the events in the function specifications?


Decide on Figma file I.A.

[ ] Document decision record
[ ] Discuss options at dev/design sync

@dylanzheng94 could you add the link of the doc for decision record please ? Thank you


Load functionality for v0.2.4 release

@shirubana :  I'm making a pull request to finalize this load functionality.  The first thing I did was to rebase your commits based on v0.2.4, so everything should  look the same as load_functionality_silvana except it's a bit neater.
Here are a couple things that I would like to do:

can we either remove the groupbycell example files into a private fork of yours, or move them to the docs folder?
I think that some of these load and analysis functions might work best in a separate .py file in the \bifacial_radiance\ directory.  We can keep analysis a bit separate from the core simulation functions.  If you're ok with that, I can get started on the new file and linking back to our routine.
We should include some tests and examples for the save, load and cleaning functions.  That way we can confirm that any changes we make don't break the basic functionality.

Let me know if you want to take a stab at any of these things, or if you'd prefer that I start on them first.  Thanks!

Ah! I was wondering where I had left that file....thanks for finding it 💃 ... I'll copy it and take care of it. I need to continue working on it.
I had thought about this, because it's similar to what we did with bifacial_vf and I think it's a great idea.
Agreed. I think it should be implemented into the main workflow though, because again if someone runs 2-UP with gap they will get a wrong result spit out at the end. I had a journal with an example but it must be outdated by now.

I can tackle this !
(I can send some other code your way if you're idle on rotating around the torque tube hahahahaha like that ever happens).

Load and clean functions are in a separate .py file now. Not sure what else I need to do for the review? However all checks have failed since late last week on this branch. I have clicked on them but I can't figure out what's going on or how to go about it.

@shirubana - go ahead and merge your load functionality unit tests for read1Result and deepcleanResult into this branch and I'll take a look at them.

Various things Im' struggling with with the branch off of this version ~

the import of load.py is not working for me. I had to hard code it to
from load import loadRadianceObj, read1Result, loadtrackerdict, _loadTrackerDict, deepcleanResult

Running the TorqueTube Journal example, I am getting wrong values in the sensor positions. I am very confused because yesterday it was working well. I'll go back in a bit to my branch of the Module Agnostic Orientationand check that journal again. 😠

This pytest branch that I'm trying to merge doesn't have the new py-test modifications needed for the Module Agnostic Orientation branch. This isj ust for the read and clean functionality.

Also this version's pytest (and my pytest branch) both are crying wolf when running for me...... One issue is that test\materials\ground is not bing created or something. I haven't figured that out yet.

Solved 1-3,
for 4, my pytest worked for a while until I merged the new load_functionality changes from today.  The issue I'm finding is that

'materials\ground.rad'  does not get created...
And since the way that you "load" load.py in bifacial_radiance is not working for me, then test_load.py fails.

I'll try to investigate how to solve it.

I'm merging this load functionality - checks are passing and we have new unit tests for the new features. Thanks @shirubana !

@cdeline we can close this branch, load_functionality silvana branch and v_0_2_4 branch now?

Yes, these can be removed.
On Feb 28, 2019, at 4:47 PM, Silvana Ayala <notifications<EMAIL_ADDRESS>wrote:
@cdelinehttps://github.com/cdeline we can close this branch, load_functionality silvana branch and v_0_2_4 branch now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/NREL/bifacial_radiance/pull/51#issuecomment-468485686, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWKtOFYMFrIEG1t80Shg-vwXcxPvfFoZks5vSGqhgaJpZM4a-nHl.


Feature Request [Elasticache-Auto-Discovery]

Hi, I was wondering if it's possible to add autodiscovery to pymemcache.
If it makes sense to add, I would love to contribute.

Hi @Nerdyvedi, we would be happy to accept that contribution

@jogo Kindly take a look at the PR I've created to add this feature.

@jogo Can you please take a look at the PR I've created , I would like to know what should be the next steps ? This feature is actually kind of useful and would help discover nodes from the configuration endpoint.


Add example showing dynamic key selection at runtime

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.701%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2683

Relevant Lines:
2896

💛  - Coveralls


Support PostgreSQL empty & inf range and OffsetDateTime for Guava ranges

After the PostgreSQLGuavaRangeType is now aware of its element type
through the DynamicParameterizedType (since #215), the bounds do not
have to be deduced from the provided range anymore. As a result
unbounded ranges like the empty range or the infinite range can be
properly mapped. As a fallback we still use the old behaviour, deducing
the element type from the bound.
For the infinite range nothing special happens. PostgreSQL's (,) now
maps to Range.all() if the element type is known.
Guava is somewhat opinionated about "empty" ranges. While ranges are
allowed to be empty (there even exists Range#isEmpty), a Guava range
is defined by its bounds so for the empty range bounds are still
mandatory (https://github.com/google/guava/issues/2400). PostgreSQL on the other hand normalizes any empty range to an
"empty" literal. As a result bounds will always be lost when persisting
empty ranges in PostgreSQL. I.e. in the previous implementation [0,0)
would be persisted fine, but then fail upon a consecutive fetch because
the bounds would have been lost in normalization.
In order to work around this limitation, empty ranges are now mapped to
the empty range with the minimal element value as placeholder bound. At
least always an empty range is returned, but users should note that the
actual bounds are lost during this normalization.
As a second improvement, tstzrange now maps to an OffsetDateTime by
default, unless a ZonedDateTime element is specified through the
DynamicParameterizedType. OffsetDateTime is more appropiate than
ZonedDateTime here, because PostgreSQL only stores the offset and not the
actual timezone. This is also analog to JPA 2.2 which also does
support only OffsetDateTime and not ZonedDateTime.
When a ZonedDateTime is requested, we fall back
to the old behaviour (guessing the timezone based on the offset).

@jwgmeligmeyling Thanks. I'll review it when I have some time.

Applied upstream, thanks for your contribution.

Applied upstream, thanks for your contribution.

Fixes https://github.com/vladmihalcea/hibernate-types/issues/287

Fixes https://github.com/vladmihalcea/hibernate-types/issues/287


(Build) Adds static analysis reports

Issue #, if available:
Fixes #172
Description of changes:
Adds static analysis reports

Findbugs
PMD -- coding rules
CPD -- duplicate code detection
Xref -- linked HTML version of the code used by the preceding reports

Sample output from my forked ion-java
https://therapon.github.io/ion-java/project-reports.html
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

You only need to check the last commit--sorry for the noise.

Already merged from the previous PR. Closing this one


Throttle running multiple queries after login

Hello,
I wonder if it's normal that after a user is logged in, I can see that the following query is ran 4 times:
select * from `throttle` where `user_id` = '1' limit 1

I understand a throttle check, on login, but not after a user is already logged in.
(of course when disabling the throttling in the configuration those don't run anymore)
I'm using latest version of laravel 5, the feature/laravel-5 branch.
Thanks

Throttling is on our radar.

Cool. :)
Checked on Sentinel, and no issue there. 1 query get ran select * from throttlewheretype= 'ip' andip= '<IP_ADDRESS>' andcreated_at > '2015-04-09 06:09:35' after login

uh oh, thought this was the sentinel branch. :( If we have time we'll take a look but more then likely it will be some time.


Do not allocate to negative ratio

No allocations allowed to negative values. When having a negative amount, allocation should be reversed. Fixes #258.

I am not sure about allocation of negative amount. It's question about domain.
Previous behavior may be correct. If we do allocation of debt (represented as negative amount) for example.
(new Money(-5, new Currency('USD')))->allocate([3, 7]); // => [-1, -4]

@Sharom Hmm. Now I am doubting too.

Negative amounts are all right, but mixed sign ratios surely shouldn't be allowed - anyway, all of the allocated money should have the same sign. Negative ratios aren't as bad as mixed ones, but IMO it's the feature we don't need just for clarity.

I reverted to the old behaviour. Let's leave as it is. We could always add another constant to the Money class, as with rounding.
So negative ratios are not allowed. And when there is a negative amount (debt), the one with largest share gets most of the debt.


Backup wallet refactor

UI Backup menu item now pops up for user to selection location for both wallet and config.
execute backupwallet is removed
backupwallet rpc now backs up both wallet and config to walletbackups directory.
backup.cpp/h is where backup related items are stored now except portions that could not.
removed walletmodel->backupWallet
put backup.h header only where needed for calls
fixed bug to allow user when menu ui backup wallet is called to allow it to save to where they want it.
now users can set an argument for backup location with backupdir=

Deals with #655


URLSessionProxyDelegate.enableAutomaticRegistration swizzling troubles with Instabug SDK

Hi !
I hope you're doing well 👍
I'm using your great library with the new macOS app that is very useful to us to monitor network calls and speed troubles of our app across the world.
Unfortunately, I'm experimenting conflicts between Pulse lib and Instabug lib... Instabug bugs reporter seems to be swizzled by Pulse... As we're using both in our project this is very sad because we've to choose between user feature bugs reporting and network log monitoring...
I'll let guys from Instabug come to you with more details but I think this is the function at the origin of this issue :
public extension URLSessionProxyDelegate {
    /// Enables automatic registration of `URLSessionProxyDelegate`. After calling this method, every time
    /// you initialize a `URLSession` using `init(configuration:delegate:delegateQueue:))` method, the
    /// delegate will automatically get replaced with a `URLSessionProxyDelegate` that logs all the
    /// needed events and forwards the methods to your original delegate.
    static func enableAutomaticRegistration(logger: NetworkLogger = .init()) {
        sharedLogger = logger
        if let lhs = class_getClassMethod(URLSession.self, #selector(URLSession.init(configuration:delegate:delegateQueue:))),
           let rhs = class_getClassMethod(URLSession.self, #selector(URLSession.pulse_init(configuration:delegate:delegateQueue:))) {
            method_exchangeImplementations(lhs, rhs)
        }
    }
}

I hope a solution will be found because these two tools are so great !
Best wishes
Jeremie

There are multiple ways to integrate Pulse, ranging from some to no swizzling required. Please consider using a different approach.


Add multiple filters of the same type for Insights

Describe the feature or enhancement
I've been wondering for a while, why it wasn't possible to add multiple filters of the same type to Insights reports.

Why isn't it possible to just add a second filter for URL and exclude more?

You should be able to choose the same filter type with multiple conditions. Will get this fixed. Thanks for reporting

Was this fixed in the latest release? as I am still experiencing the issue after upgrading

v2.12.1 (docker), the problem exists. Will it be fixed?


Taxonomic Trail

Feature or enhancement
We need a tool/button that would show the entire taxonomic trail of a name and its descendants, and allow us to select from amongst them and execute a command (such as changing the parent/removal from synonymy)
Location
on the Edit Taxon Name screen (?)
Screenshot, napkin sketch of interface, or conceptual description
No response
Your role
Curator of small insect orders, SFG

See also #2794


Get Tweet for specific URL using Twitter API

Hi everyone ,
I need help for get count of tweet for specific URL using Twitter API. Any one have sample code to achieve that functionality for my website. I need total share tweet count for my each post.
Please help if any one have idea for that.
Thanks,
Crish

@cristopher-christ This is more of a general Twitter API question than a twitter-api-php library question, but can you be more specific?
Have a look through https://dev.twitter.com/rest/public and see if there's a Twitter API call there for your need.


Obtain Device Status

Problem/Motivation
Looking to receive the status of the devices.
Expected behavior
devices[id].status returns up or down
Actual behavior
There is no status property
Steps to reproduce
devices = await tailscale.devices()
    for device in devices:
        device_status = devices[device].status

Proposed changes
Return if the device is online/offline

Looks like this may not yet be possible:
https://github.com/tailscale/tailscale/issues/7004
Can you think of any clever workarounds other than ping? Something that could be embedded in this package?

Can you think of any clever workarounds other than ping?

That is not in scope for this package. If you want to ping a device, I suggest to look for a package that can ping an address.
../Frenck


Interval support

Summary of the changes / Why this improves CrateDB
Checklist

[X] User relevant changes are recorded in CHANGES.txt
[X] Touched code is covered by tests
[X] Documentation has been updated if necessary
[X] CLA is signed
[X] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Documentation is not fully finished yet, still need to describe the format better.

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please


The specified bucket does not exist

Please help me. I try to deploy serverless but this error appear when try to excecute
serverless --stage=production deploy

into npm run deploy:api step
here is the cli output
Serverless Error ---------------------------------------

     The specified bucket does not exist

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues

  Your Environment Information -----------------------------
     OS:                 darwin
     Node Version:       6.2.0
     Serverless Version: 1.4.0

This can happen if you manually delete the S3 bucket rather than deleting it via Serverless/CloudFormation. See: https://github.com/serverless/serverless/issues/1877

thanks for jumping in here and helping out @kmjennison 🙇

Not now :( I'm try again form zero but nothing happens. Thanks guys!

@Danjavia what do you mean by nothing happens?

I have the same issue. And checking in s3 the bucket exists correctly. I don't know.

hey @Danjavia - sorry for getting back so late. Did you eventually resolve the issue?

Try deleting the stack from CloudFormation and redeploying - that got me over this hump.

Something is definitely off here. Using the same serverless.yml, and as a test, I was able to create the deployment, then used serverless remove successfully. Then, I ran deploy again and got failures. There is definitely a clean up issue.

Deleting the cloudformation template might not be a good solution. The next deployment will create a new api-gateway deployment with different id, which will change the url(might not matter if you are using cnames).
The better solution which worked for me was:
go to cloudtrail and select s3 resource to check the deleted bucket name. You don't need this if you have some other way of knowing the bucket name.
create a bucket with same name.
retrigger deployment
Looks like serverless use the bucket just for backup. It worked for me.

This is just a general comment but when you deliver back error messages to the user, please try to include the proper name of what doesn't exist. That is, if a bucket doesn't exist you should say WHAT THE BUCKET NAME IS.
Also, passing --verbose does nothing. A command line tool is supposed to be a user interface, not a hurdle.

Try deleting the stack from CloudFormation and redeploying
This worked for me, too. Thanks.

I would like to reopen this issue. It is fairly easy to arrive at this situation and this has happened to me numerous times over the past few months. I've never been able to identify exactly how to fix it. The error message Serverless yields is useless. At the very minimum, the bucket name needs to be included in the error.

I agree the error messages are poor. When it has happened to me it has usually been when I have been using plugins to simplify the removal of the stack. It is rare though.
Best approach was above - look at Cloudtrail. It seems to be the removal of the serverless bucket itself that causes the problem. As its not named in the yaml file your attention is not directed to it.

It would be really valuable that the bucket name is included in the error message.

I had deleted the s3 bucket long ago and was getting Unhandled rejection ServerlessError: The specified bucket does not exist. The cloudtrail was too old to show the bucket name.
I did sls info -v -s prod and found the ServerlessDeploymentBucketName ... 👍


language issue

this appears randomly most of the time

seems like other languages other than the default one , takes around 2 minutes to be displayed


Difference between colmap and blender

Nice work! Thanks for your work.  I found that you rearranged the rows of the pose matrix of colmap. nerf_matrix_to_ngp
Is it because the reference coordinate system is different about COLMAP and NeRF? And what is the difference?  Thks~

Thank you very much. It's very useful !


fix: Update AWS provider version to support AL2023_* AMI types; ensure AL2023 user data receives cluster service CIDR

Description

Update AWS provider version to support AL2023_* AMI types

Provider https://github.com/hashicorp/terraform-provider-aws/pull/36046
SDK<EMAIL_ADDRESS>

Ensure AL2023 user data receives cluster service CIDR
Fix a bug where setting create = false on a managed nodegroup would return an error when looking up the instance type used for EFA

Motivation and Context

Resolves #2954
Relates https://github.com/awslabs/amazon-eks-ami/issues/1597#issuecomment-1973512095
On AL2 AMI, the service CIDR was optional but starting with the AL2023 AMI, its now required

Breaking Changes

No

How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects
[x] I have executed pre-commit run -a on my pull request

This PR is included in version 20.5.3 :tada:


Parallel Extrapolation Methods Benchmarks

Testing Parallel Extrapolation Methods on Stiff ODEs.
TODO:

[ ] Alter with order ranges for best performance (Comment: min_order = 3 gives better performance in some cases rather than the default of 2)
[ ] Play with sequences (I think they are alright default for the best)
[ ] Threading options (Polyester is best according to my initial testing)

Let me know if there's anything else to check.
@ChrisRackauckas

I rebased onto master to fix threads

Continue optimizing in new PRs.


gephi: Update to version 0.9.3, fix autoupdate

Relates to Excavator unable to autoupdate: https://github.com/ScoopInstaller/Extras/runs/5864968342?check_suite_focus=true#step:3:220

[x] I have read the Contributing Guide.

/verify

The -x64 might mean that it needs an architecture 64bit block now

No it looks like it still ships 32-bit and 64-bit binaries. But I need to fix the post_install script as they now bundle the JRE, so no need to edit the conf to point to JAVA_HOME

Fixed now, I have tested updating from 0.9.2 to 0.9.3 and installing from scratch.


[WIP] Tweak glossary entry for Static Pod

Prompted by a comment on #13831, I wonder if this change will help the glossary entry come out right.
Using glossary tooltips in glossary entries seems both:

helpful to readers
a bit fragile, because I have seen some implementation snags that surprised me

The date was wrong too: https://github.com/kubernetes/website/commit/e682f1d331d70ff5690e7dd47c2f02bbd222325b#diff-c5154bb7feb1eb1e27a9265dff2c1257R4

lgtm

Superseded by #15752


Revisit purpose

The original purpose of this repository was to offer reasonable default images for supporting Ruby on Rails builds (CI) and production deployments.
These images were originally supported with rails-build and rails-run, providing a common base that required little or no modification for conventional Ruby on Rails applications.
However, times have changed, and Ruby on Rails now provides some great support of Docker out of the box (via devcontainers, Dockerfile and Kamal deployment).
With that said, it is time to revisit these images and decide which are relevant to maintain going forward and what the specific context will be.

Context:

Node based javascript support (not that this would preclude importmaps, it would just be overkill)
Postgres or sqlite support (maybe a tag in the future)
GitHub Actions for CI (previously a motivator was Azure DevOps, however, this is no longer the case for Harled Inc.)

Initial thoughts:

rails-run can go away (replaced with Dockerfile from rails new)
rails-build can also go away (other good options exist combined with GitHub actions)
rails-dev is new an actually helpful as the base image to use for devcontainers with docker-compose (vs image + features)


[Datepicker]: option to select year first

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

taken from @3upzorz 's fork. Any reason this wasn't merged to master previously?

#6420 wasn't merged as we though it would cover more use-cases by making the displayed view controllable throw a property and a callback.

@chrisjbrown Thank you

@oliviertassinari no rush, but is there a planned release date for 0.18.7? I'll submit a PR to upgrade the version in mbrookes/formsy-material-ui when it's released so this option is available :)

We have 8 pending commits, would be good to do it before the end of the week. We will see.

Is there option to select year only ?


Update readme

Is it possible to remove 'Test, lint and docker' prefix, and leave only services names?


Update config to enable docfx v3

AB#294688
This Pull Request is for docfxv3 migration, after the Pull Request merged, the repository will be built with docfxv3 instead of docfxv2.

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

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

signalrjs/breadcrumb/toc.yml
:white_check_mark:Succeeded

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


Django doesn't run if you remove a rq job on app.ready

How do you use Sentry?
Sentry Saas (sentry.io)
Version
2.3.0
Steps to Reproduce

You can simply clone https://github.com/MHM5000/sentry_bug and follow the instructions on readme
or create a django project and an example_app app
install and configure sentry, rq, redis, django-rq, django-scheduler, rq-scheduler
add the following to your example_app/apps.py

from datetime import datetime

import django_rq
from django.apps import AppConfig
from rq.job import Job

from example_app.defaults import JOB_ID
from example_app.tasks import something

class ExampleAppConfig(AppConfig):
    default_auto_field = "django.db.models.BigAutoField"
    name = "example_app"

    def ready(self) -> None:
        scheduler = django_rq.get_scheduler()

        job = scheduler.schedule(
            scheduled_time=datetime.now(),
            func=something,
            id=JOB_ID,
            interval=10 * 60,
        )
        print("job", job)

        connection = django_rq.get_connection()

        job = Job.fetch(JOB_ID, connection=connection)
        job.delete()

create example_app/defaults.py and add a JOB_ID='job_id' there.
create example_app/tasks.py and a dummy something method

I'd recommend going with the first option: clone the test repo
Expected Result
your project running smoothly.
this issue didn't exist in 2.1.1
Actual Result
Traceback (most recent call last):
  File "/Users/mojtahedi/.pyenv/versions/3.11.7/lib/python3.11/threading.py", line 1045, in _bootstrap_inner
    self.run()
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/sentry_sdk/integrations/threading.py", line 99, in run
    return _run_old_run_func()
           ^^^^^^^^^^^^^^^^^^^
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/sentry_sdk/integrations/threading.py", line 94, in _run_old_run_func
    reraise(*_capture_exception())
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/sentry_sdk/utils.py", line 1640, in reraise
    raise value
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/sentry_sdk/integrations/threading.py", line 92, in _run_old_run_func
    return old_run_func(self, *a, **kw)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/mojtahedi/.pyenv/versions/3.11.7/lib/python3.11/threading.py", line 982, in run
    self._target(*self._args, **self._kwargs)
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/django/utils/autoreload.py", line 64, in wrapper
    fn(*args, **kwargs)
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/django/core/management/commands/runserver.py", line 125, in inner_run
    autoreload.raise_last_exception()
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/django/utils/autoreload.py", line 87, in raise_last_exception
    raise _exception[1]
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/django/core/management/__init__.py", line 394, in execute
    autoreload.check_errors(django.setup)()
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/django/utils/autoreload.py", line 64, in wrapper
    fn(*args, **kwargs)
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/django/__init__.py", line 24, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/django/apps/registry.py", line 124, in populate
    app_config.ready()
  File "/Users/mojtahedi/sandbox/test_sentry_bug/example_app/apps.py", line 29, in ready
    job.delete()
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/rq/job.py", line 1251, in delete
    connection.delete(self.key, self.dependents_key, self.dependencies_key)
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/redis/commands/core.py", line 1713, in delete
    return self.execute_command("DEL", *names)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/sentry_sdk/integrations/redis/_sync_common.py", line 72, in sentry_patched_execute_command
    cache_properties = _compile_cache_span_properties(
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/sentry_sdk/integrations/redis/modules/caches.py", line 32, in _compile_cache_span_properties
    key = _get_safe_key(redis_command, args, kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/mojtahedi/.local/share/virtualenvs/test_sentry_bug-gPib43ih/lib/python3.11/site-packages/sentry_sdk/integrations/redis/utils.py", line 56, in _get_safe_key
    key = ", ".join(args)
          ^^^^^^^^^^^^^^^
TypeError: sequence item 0: expected str instance, bytes found

Hey @MHM5000 ! Thanks for the bug report!
I think this was introduced in 2.3.0. Can you try to use 2.2.1 and confirm that it is working there?

I didn't even have time to test 2.2.1
thanks for the quick fix

We ran into this.  Our workflow is using the redis broker with celery and flask and happens on a task.get()

2.2.1 does not have the error
2.3.0 does have the error


Update ROADMAP.md

Made updates to the roadmap to reflect our latest thinking.

Some of the items listed have issues created for them, should roadmap link them?


Building with cmake

Hello :-)! I've added these CMakeLists.txts and a note in README.md. Now it builds on Linux without any problem. When this PR will be accepted, I'll add next one with Travis CI configuration.
I didn't manage to use these CMakeLists.txt files in CLion under Windows, but I think it's matter of a proper IDE configuration (path to Boost and path to SFML). You can try ;-).
Let me know, if I made any mistake in README.md, please.

This looks good so far. There are some more libraries to add; they may have been undetected because I don't include them via NuGet:

rapidjson is required
libnoise will become a dependency once #15 is implemented (which is my top priority at the moment)

I'll add a note to the end of README.md describing the usage of Wangview.

Oh, ok, good to know, I'll add them.

Finally I've got it 😄! I've:

added RapidJSON library to CMakeLists.txt for Wangscape
added CMakeLists.txt for WangscapeTest and proper dependencies
made static library from common Wangscape and WangscapeTest code. It links with Wangscape and WangscapeTest (no need to compile it twice)
and, of course, updated README.md.

Great work! Thanks again :)

Great! Now I can dive into your code if you don't mind ;).

Go ahead! :D


How to prevent deadlocks when reload_on_save is enabled

@randy3k Randy, hi there, nice to meet you. Yesterday I was facing a nasty bug while reloading some code of mine using your package and after a lot of researching I've discovered in some edge-case a deadlock will be created. I've come up with a little reproducer and added some details here.
Right now I'd like to come up with some way to reproduce the deadlock much faster... I was thinking maybe spawning "Package reloading" in a loop intensively would do, I'll test it out later.
Anyway, in case you're also interested, please let me know your thoughts, advices, ...
Thx in advance!

Do you mean saving the document while the package is reloading?

Yeah, put the focus on the start.py view and start pressing ctrl+s as fast as possible... I've already made the test of doing [window.run_command("save") for i in range(100)] on the console but unfortunately the deadlock won't show up this way.
Just for the record, with larger code using a similar pattern than the one exposed in my mcve (ie: global variables using sublime settings function) I won't need to press ctrl+s as fast as possible cos the deadlock shows up much more easily, tricky... I'll try to make a video to show you how I'm testing it right now

@randy3k Here's the slow manual way I'm testing it right now... if you know a faster way to raise the deadlock I'd be glad to hear it :)

I guess the lesson to learn is to wait for the reloaded while reloading in progress. ... That sounds wise, but... not really ;)
With my above snippet is difficult to reproduce, that's why I think not waiting much time between savings but with real larger code the deadlock will show up even if i save it in much slower pace (ie: i wait till the progress bar has finished and the message "package whatever reloaded" appears...
Tricky stuff :/ ... What do you mean by "it takes some time for the reloaded to kick in" ?  Certainly the message "package whatever reloaded" in the status bar doesn't mean the package has kicked in ... So... :) . Asking you this cos if we knew the condition that a module has been "kicked in" not allowing to the users reloading would be cool

More relevant info, here's a little snapshot once the deadlock happens:
2018-07-19 16:50:15.786994

# ThreadID: 4120
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Installed Packages\AutomaticPackageReloader.sublime-package\package_reloader.py", line 73, in <lambda>
  sublime.set_timeout_async(lambda: self.run_async(pkg_name))
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Installed Packages\AutomaticPackageReloader.sublime-package\package_reloader.py", line 92, in run_async
  reload_package(pkg_name, verbose=pr_settings.get('verbose'))
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Installed Packages\AutomaticPackageReloader.sublime-package\reloader/reloader.py", line 47, in reload_package
  reload_plugin(pkg_name)
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Installed Packages\AutomaticPackageReloader.sublime-package\reloader/reloader.py", line 118, in reload_plugin
  sublime_plugin.reload_plugin(plugin)
File: "D:\testcase\Sublime Text Build 3176 x64\sublime_plugin.py", line 116, in reload_plugin
  m = importlib.import_module(modulename)
File: "./python3.3/importlib/__init__.py", line 90, in import_module
File: "<frozen importlib._bootstrap>", line 1584, in _gcd_import
File: "<frozen importlib._bootstrap>", line 1565, in _find_and_load
File: "<frozen importlib._bootstrap>", line 1532, in _find_and_load_unlocked
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Installed Packages\AutomaticPackageReloader.sublime-package\reloader/reloader.py", line 175, in load_module
  return module.__loader__.load_module(name)
File: "<frozen importlib._bootstrap>", line 584, in _check_name_wrapper
File: "<frozen importlib._bootstrap>", line 1022, in load_module
File: "<frozen importlib._bootstrap>", line 1003, in load_module
File: "<frozen importlib._bootstrap>", line 560, in module_for_loader_wrapper
File: "<frozen importlib._bootstrap>", line 868, in _load_module
File: "<frozen importlib._bootstrap>", line 313, in _call_with_frames_removed
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Packages\foo\a.py", line 14, in <module>
  global_a = A()
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Packages\foo\a.py", line 8, in __init__
  somekey = global_b.load().get("somekey", [])
File: "D:\testcase\Sublime Text Build 3176 x64\sublime.py", line 1161, in get
  return sublime_api.settings_get_default(self.settings_id, key, default)

# ThreadID: 5592
File: "D:\testcase\Sublime Text Build 3176 x64\sublime_plugin.py", line 116, in reload_plugin
  m = importlib.import_module(modulename)
File: "./python3.3/importlib/__init__.py", line 90, in import_module
File: "<frozen importlib._bootstrap>", line 1584, in _gcd_import
File: "<frozen importlib._bootstrap>", line 1565, in _find_and_load
File: "<frozen importlib._bootstrap>", line 1532, in _find_and_load_unlocked
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Installed Packages\AutomaticPackageReloader.sublime-package\reloader/reloader.py", line 175, in load_module
  return module.__loader__.load_module(name)
File: "<frozen importlib._bootstrap>", line 584, in _check_name_wrapper
File: "<frozen importlib._bootstrap>", line 1022, in load_module
File: "<frozen importlib._bootstrap>", line 1003, in load_module
File: "<frozen importlib._bootstrap>", line 560, in module_for_loader_wrapper
File: "<frozen importlib._bootstrap>", line 868, in _load_module
File: "<frozen importlib._bootstrap>", line 313, in _call_with_frames_removed
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Packages\foo\start.py", line 1, in <module>
  from foo.a import A
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Installed Packages\AutomaticPackageReloader.sublime-package\reloader/reloader.py", line 138, in __import__
  module = orig___import__(name, globals, locals, fromlist, level)
File: "<frozen importlib._bootstrap>", line 295, in _lock_unlock_module
File: "<frozen importlib._bootstrap>", line 221, in acquire

# ThreadID: 7620
File: "./python3.3/threading.py", line 878, in _bootstrap
File: "./python3.3/threading.py", line 901, in _bootstrap_inner
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Packages\deadlocks\commands.py", line 56, in run
  self.stacktraces()
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Packages\deadlocks\commands.py", line 69, in stacktraces
  f.write(stacktraces())
File: "D:\testcase\Sublime Text Build 3176 x64\Data\Packages\deadlocks\commands.py", line 22, in stacktraces
  for filename, lineno, name, line in traceback.extract_stack(stack):

What do you mean by "it takes some time for the reloaded to kick in" ?

if you save the file in a row 10 times without a pause in between, the on_post_save hook won’t be triggered.

I didn’t test this, but try
[sublime.set_timeout(lambda: window.run_command("save"), i) for i in range(10)]

Thx, let me try, right now I was playing with the below one and I was getting +/- consistent crashes after spawning it 1 or 2 times:
class SaveAutomaticallyCommand(sublime_plugin.WindowCommand):

    def run(self, **kwargs):
        for i in range(50):
            sublime.set_timeout(lambda: self.window.run_command("save"), 100*i)

If you run the command [window.run_command("save") for i in range(10)], you don’t give the event handler enough time to respond. Note that the event handler runs on a different thread that the sublime main thread.

You're absolutely right... btw, I'd also tried with set_timeout_async and it wasn't making any difference, just for the record, the below with the hardcoded values seems to crash ST quite consistently \o/ (although sometimes you need to spawn it couple of times):
[sublime.set_timeout(lambda: window.run_command("save"), i*100) for i in range(50)]

That'd be indeed a great fix, but I guess the question here is... is there any way to know whether the loading has been completed (including async code) or not?
Maybe this one https://github.com/python/cpython/blob/master/Lib/importlib/_bootstrap.py#L194 could help? dunno... :/

We can tell when the plugin has finish reloading https://github.com/randy3k/AutomaticPackageReloader/blob/master/package_reloader.py#L99. It would be the developer responsibility to handle the loading of asynchronous code.

Fair enough, sounds like an easy and decent solution to me. I think that'd be a good default behaviour of the plugin... On the other hand, being able to stress test and reloading a package could be also quite interesting to check packages are robust enough and find possible issues. So I guess a settings bool variable such as reload_on_package_ready with true as a default (or a more descriptive name) could be a more versatile option.
Btw, I see a lot of hardcoded numbers in this piece of code, guess coming up with a more robust solution wouldn't be straightforward?
Regards


latest ae2wtl doesn't support latest ae2

there appears to be a hard requirement for 8.2.0-alpha3 and not able to be used with latest ae2

I currently maintain two versions: 1.0.x-xxx versions which work for ae2 8.2.0-alpha.3 and
1.1.x-xxx versions which work for ae2 8.3.0-alpha.1 and higher
this is due internal changes in ae2.
I still primarily maintain the 8.2.0-alpha.3 version since I am not quite sure how stable the new ones are.
ae2 8.3.0-alpha.1 came with a big warning sign to probably not use (yet)
ae2 8.3.0-alpha.2 fixed some bugs, but will still support 8.2.0-alpha.3 (for now)


docs: contributing guide

Adds basic contributing guides.
Simplifies Python development with a Makefile.

@gagan-bhullar-tech @sayandipdutta You both recently worked on some good first issue PRs in Python. I'm trying to improve the developer documentation for LanceDB Python. Would welcome any feedback you have on this PR.


make page_size configurable

Thanks for this gem of a gem, it makes using prawn so much more reasonable.
is there a way to add page_size as a configurable?
as it is in the initialize function, i'm not sure how to override or configure it best. if you could give me some hints, i might be able to come up with a pr.

We probably need to change this
    def initialize(attributes = {})
      super(page_size: "LETTER")

To:
super(page_size: attributes.delete(:page_size) || "LETTER")

haha, you're too reactive. i had hoped to twiddle together a nice naive pr :D
thanks.


No color

Description
Added simple NoColor for disabling coloring as requested in #38
This code:
func printNoColor() {
	opts := &devslog.Options{
		NoColor: true,
	}

	l := slog.New(devslog.NewHandler(os.Stdout, opts))
	l.Info("msg",
		slog.Any("integer", 1),
		slog.Any("float", 2.2),
		slog.Any("string", "someString"),
		slog.Any("map", map[int]string{3: "three", 4: "four"}),
	)
}

Produce this:

Checklist

[x] Code compiles correctly
[x] Created tests which fail without the change (if possible)
[x] All tests passing
[x] Extended the README / documentation, if necessary

@david-littlefarmer : Thats I think perfect. =)

@david-littlefarmer : Cool stuff. Right away using it here:
https://gitlab.com/data-custodian/custodian/-/blob/main/tools/ci-tool/pkg/log/log.go?ref_type=heads


Bad state: No element

$ protoc --version
libprotoc 24.1
$ protoc --dart_out=. {xxx}.proto
Unhandled exception:
Bad state: No element
#0      List.last (dart:core-patch/growable_array.dart:348:5)
#1      toDartComment (package:protoc_plugin/src/shared.dart:52:16)
#2      FileDescriptorProtoExt.commentBlock (package:protoc_plugin/src/shared.dart:24:14)
#3      MessageGenerator.generateFieldAccessorsMutators (package:protoc_plugin/src/message_generator.dart:539:34)
#4      MessageGenerator.generateFieldsAccessorsMutators (package:protoc_plugin/src/message_generator.dart:521:7)
#5      MessageGenerator.generate. (package:protoc_plugin/src/message_generator.dart:428:7)
#6      IndentingWriter._addBlockBodyAndEnd (package:protoc_plugin/indenting_writer.dart:101:9)
#7      IndentingWriter.addAnnotatedBlock (package:protoc_plugin/indenting_writer.dart:94:5)
#8      MessageGenerator.generate (package:protoc_plugin/src/message_generator.dart:327:9)
#9      FileGenerator.generateMainFile (package:protoc_plugin/src/file_generator.dart:275:9)
#10     FileGenerator.generateFiles (package:protoc_plugin/src/file_generator.dart:234:24)
#11     CodeGenerator.generate. (package:protoc_plugin/src/code_generator.dart:131:36)

seems about comments
after removed all comments, no errors

I'm seeing the same issue as well. I can't remove comments from the protos as I don't own them (I'm using buf to grab the proto definitions).
Downgrading from 21.1.x back down to 21.0.2 works for now.


Create datafusion-physical-optimizer crate

Which issue does this PR close?

Part of https://github.com/apache/datafusion/issues/11502.
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

I like the idea of moving the physical optimizer into its own crate, thank you


chore: Adding auto_delete to ecr repositories

Dependencies
Modules must be updated to aws-cdk-lib=2.70.0 to use auto_delete_images
Description of changes:
Adding auto_delete to ecr repositories
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@dgraeber @srinivasreddych We'll need to get these modules to >=2.70.0 before merging this in.

@malachi-constant Pls check the linting errors above. Sure, i will be bringing in the version upgrades we've made internally (2.70.0) and then its safe to merge this PR. Until then, i will be converting the PR to draft

@malachi-constant Pls check the linting errors. Sure, i will be bringing in the version upgrades we've made internally (2.70.0) and then its safe to merge this PR. Until then, i will be converting the PR to draft

The linting errors are directly due to mypy checks which is caused by the lower version of the CDK. So those will resolve once upgraded.

@malachi-constant Pls check the linting errors. Sure, i will be bringing in the version upgrades we've made internally (2.70.0) and then its safe to merge this PR. Until then, i will be converting the PR to draft

The linting errors are directly due to mypy checks which is caused by the lower version of the CDK. So those will resolve once upgraded.

Makes complete sense. Thanks

Thanks for the PR!


ng update @angular/cli fails with npm link'ed module

Versions
Angular CLI: 6.0.0
Node: 9.5.0
OS: darwin x64
Angular: 5.2.5
... animations, cdk, common, compiler, compiler-cli, core, forms
... http, language-service, material, platform-browser
... platform-browser-dynamic, platform-server, router

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.6.0
@angular-devkit/core         0.6.0
@angular-devkit/schematics   0.6.0
@angular/cli                 6.0.0
@schematics/angular          0.6.0
@schematics/update           0.6.0
rxjs                         5.5.6
typescript                   2.5.3

I have a project which uses npm link to pull in a shared library "@ teachtown/shared"^, which is TS source code, not transpiled / packaged as JS. The intention is that this library will be used in multiple projects.
^  space after "@" so that github doesn't try to parse as user/project
I'm trying to upgrade the consuming project, Angular 5.2.5 => 6, following the instructions provided on https://update.angular.io/.
I reached the following steps, and got an error:
npm install -g @angular/cli
npm install @angular/cli
ng update @angular/cli

> Not found : @teachtown/shared

(Aside: I had to update the second command to npm install @angular/cli --save-dev for it to properly update CLI in my project.)
Note that @ teachtown/shared does exist:
$ ls node_modules/@teachtown
> shared

Repro steps
see above description
Observed behavior
see above description
Desired behavior
One of the following:

Angular CLI provides support for shared projects in source form.
Update process recognizes the shared project (by detection of package.json?) and offers option to include as / convert to a library, since CLI now supports ng generate library.

Mention any other details that might be useful (optional)

We are using libraries in a private repo these fail with "not found"
Can we have a way to ignore these and carry on?

I'm sorry, but we can't reproduce the problem following the instructions you provided.
Remember that we have a large number of issues to resolve, and have only a limited amount of time to reproduce your issue.
Short, explicit instructions make it much more likely we'll be able to reproduce the problem so we can fix it.
If the problem persists, please open a new issue following our submission guidelines.
A good way to make a minimal repro is to create a new app via ng new repro-app and add the minimum possible code to show the problem. Then you can push this repository to github and link it here.


fix extension points link in api.md file

Notes for Reviewers
This PR fixes #7135
I modified "extension points" link on API page to direct to its correct address ( served and tested locally )
Signed-off-by: Vivek Vishal<EMAIL_ADDRESS>Signed commits

[x] Yes, I signed my commits.

🚀 Preview for commit e007a6cd38ee380ab01a71aa5ae33ae611cf89ae at: https://63f487a478d73c2dc5741afd--meshery-docs-preview.netlify.app

This is the PR I was talking about @leecalcote @Chadha93

@vishalvivekm Let's discuss this on the Meshery Dev call. Please add this as an agenda item in the meeting minutes if you would. :)

Yes, sure! @Chadha93


Feature: Terminal filetype + show current process

This modifies the terminal to show the current active process, and show a file icon (as well as be set to terminal filetype):
Before:

After:

This triggers a bunch of warnings for unused variables and unbound record labels. How did this get through CI? Did you change the build command?

@glennsl - hmm, looking into it. I'm not getting any warnings with esy build, esy '@test' build or esy '@integrationtest' build. Which command did you run that shows the warnings?

esy b dune build --watch --only-packages Oni2 is what I usually use. Submitting PR with fixes now.

Ah, I see. Thanks @glennsl !
I'm able to get the warnings running esy b dune build @check  as well. I think we should add this to the CI, as it seems the current set of build commands we run aren't catching this.


Can't use the module

I got the following error after installing with npm:
/node_modules/sharp/build/Release/sharp.node'
0|RunOn_AP | was compiled against a different Node.js version using
0|RunOn_AP | NODE_MODULE_VERSION 48. This version of Node.js requires
0|RunOn_AP | NODE_MODULE_VERSION 57. Please try re-compiling or re-installing
0|RunOn_AP | the module (for instance, using `npm rebuild` or `npm install`).

Running npm rebuild or npm install didn't help. Any suggestion?
PS:I'm using node v8.9.1

The error message says the version of Node used at npm install time is different to the version being used at run time.
NODE_MODULE_VERSION 48 is Node 5 and NODE_MODULE_VERSION 57 is Node 8 - see https://nodejs.org/en/download/releases/
There's probably an old version of Node 5 on your machine that npm is erroneously using.

@sbatururimi Were you able to make progress with this?


[BUG] RuntimeError: a leaf Variable that requires grad is being used in an in-place operation

Describe the bug
https://github.com/lifeiteng/vall-e/pull/19/files#diff-389db6acad3c5ae1d09617e4e94e434e6f0a17e4878dac378d7d42cc94e43888R896
[2023-02-13 00:21:09,543] [INFO] [comm.py:657:init_distributed] Initializing TorchBackend in DeepSpeed with backend gloo
2023-02-13 00:21:09,544 INFO [distributed_c10d.py:319] Added key: store_based_barrier_key:1 to store for rank: 0
2023-02-13 00:21:09,544 INFO [distributed_c10d.py:353] Rank 0: Completed store-based barrier for key:store_based_barrier_key:1 with 1 nodes.
[2023-02-13 00:21:09,544] [INFO] [logging.py:68:log_dist] [Rank 0] DeepSpeed info: version=0.8.0, git-hash=unknown, git-branch=unknown
2023-02-13 00:21:09,603 INFO [distributed_c10d.py:319] Added key: store_based_barrier_key:2 to store for rank: 0
2023-02-13 00:21:09,603 INFO [distributed_c10d.py:353] Rank 0: Completed store-based barrier for key:store_based_barrier_key:2 with 1 nodes.
Traceback (most recent call last):
  File "bin/trainer.py", line 1082, in <module>
    main()
  File "bin/trainer.py", line 1075, in main
    run(rank=0, world_size=1, args=args)
  File "bin/trainer.py", line 899, in run
    model, optimizer, _, scheduler = deepspeed.initialize(
  File "/home/feiteng/.local/lib/python3.8/site-packages/deepspeed/__init__.py", line 125, in initialize
    engine = DeepSpeedEngine(args=args,
  File "/home/feiteng/.local/lib/python3.8/site-packages/deepspeed/runtime/engine.py", line 301, in __init__
    self._configure_distributed_model(model)
  File "/home/feiteng/.local/lib/python3.8/site-packages/deepspeed/runtime/engine.py", line 1187, in _configure_distributed_model
    self._broadcast_model()
  File "/home/feiteng/.local/lib/python3.8/site-packages/deepspeed/runtime/engine.py", line 1102, in _broadcast_model
    dist.broadcast(p,
  File "/home/feiteng/.local/lib/python3.8/site-packages/deepspeed/comm/comm.py", line 127, in log_wrapper
    return func(*args, **kwargs)
  File "/home/feiteng/.local/lib/python3.8/site-packages/deepspeed/comm/comm.py", line 232, in broadcast
    return cdb.broadcast(tensor=tensor, src=src, group=group, async_op=async_op)
  File "/home/feiteng/.local/lib/python3.8/site-packages/deepspeed/comm/torch.py", line 70, in broadcast
    return torch.distributed.broadcast(tensor=tensor,
  File "/home/feiteng/.local/lib/python3.8/site-packages/torch/distributed/distributed_c10d.py", line 1408, in broadcast
    work.wait()
RuntimeError: a leaf Variable that requires grad is being used in an in-place operation.

error at: 'text_embedding.word_embeddings.weight'
https://github.com/lifeiteng/vall-e/blob/deepspeed/valle/modules/model.py#L66
self.text_embedding = TokenEmbedding(d_model, NUM_TEXT_TOKENS)

To Reproduce
git clone -b deepspeed https://github.com/lifeiteng/vall-e.git

cd egs/libritts

export PYTHONPATH=YOUR_PATH/k2-fsa/icefall:$PYTHONPATH
export PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python

deepspeed bin/trainer.py \
    --decoder-dim 512 --nhead 8 --num-decoder-layers 8 \
    --deepspeed --deepspeed_config configs/ds_zero2.config \
    --exp-dir exp/valle_mini

install reference: https://github.com/lifeiteng/vall-e/tree/deepspeed#installation

Expected behavior
Figure out the error RuntimeError: a leaf Variable that requires grad is being used in an in-place operation.
ds_report output
--------------------------------------------------
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
 [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
 [WARNING]  async_io: please install the libaio-dev package with apt
 [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
async_io ............... [NO] ....... [NO]
cpu_adagrad ............ [NO] ....... [OKAY]
cpu_adam ............... [NO] ....... [OKAY]
fused_adam ............. [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
random_ltd ............. [NO] ....... [OKAY]
 [WARNING]  please install triton==1.0.0 if you want to use sparse attention
sparse_attn ............ [NO] ....... [NO]
spatial_inference ...... [NO] ....... [OKAY]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
transformer_inference .. [NO] ....... [OKAY]
utils .................. [NO] ....... [OKAY]
--------------------------------------------------
DeepSpeed general environment info:
torch install path ............... ['/home/feiteng/.local/lib/python3.8/site-packages/torch']
torch version .................... 1.13.0+cu116
deepspeed install path ........... ['/home/feiteng/.local/lib/python3.8/site-packages/deepspeed']
deepspeed info ................... 0.8.0, unknown, unknown
torch cuda version ............... 11.6
torch hip version ................ None
nvcc version ..................... 11.6
deepspeed wheel compiled w. ...... torch 1.13, cuda 11.6

System info (please complete the following information):

OS: [e.g. Ubuntu 22.04]
GPU count and types GTX 3060
Python version 3.8
Any other relevant info about your setup

Launcher context
the deepspeed launcher
Docker context
Ubuntu 20.04 python3.8
Additional context

deepspeed.init_distributed(dist_backend="nccl")

Thanks @lifeiteng - just to clarify, you were only seeing thsi issue with gloo not nccl?

I think so, also a small change in ds.config

What if you can't use nccl when on windows for example?

gloo fails with the same issue, nccl works perfect

gloo fails:
RuntimeError: a leaf Variable that requires grad is being used in an in-place operation.

def sync_params(params) -> None:
    with torch.no_grad():
        for i, p in enumerate(params):
            p_copy = p.detach()
            dist.broadcast(p_copy, 0)
            p.copy_(p_copy)

This seems to work for gloo. This could cause other issues, if anyone sees why this may be a bad workaround then let me know.

Hi @thorinf - do you want to PR that and we can review it that way?

Hi @thorinf - do you want to PR that and we can review it that way?

I've not actually been working on DeepSpeed. Had the same issue with gloo, so I went back and posted my workaround once I'd found something.

deepspeed.init_distributed(dist_backend="nccl")

Where to add this line of code?


Cleanup and upgrade

replace some old fabric idemix deps
remove legacy zookeeper/kafka from integration test suite
remove dep pin for go-kit since we use a pretty old version
use latest fabric protos
use latest fabric (this is just for testing ... see if it works or explodes)

@mffrench Can you please have a look at this? I've tried to upgrade the fabric deps to a recent version of Fabric. As you are currently working with Fabric 2.2.x it would be good to know if the changes in this PR would work for you as well. Thanks

Hello @mbrandenburger ,
in our roadmap, we plan to move our HLF version to last v2.4.4 before our next FSC/FTS migration :
https://github.com/hyperledger/fabric/tree/v2.4.4
So if FSC/FTS doesn't require new commits from master, I would suggest to use the commit ids from that tag to synchronise versioning from HLF to FSC applications.
HLF v2.4.4 commit : 1473ecae6451d82a068aa943f8df8cf1a7ce4864. Currently this PR use github.com/hyperledger/fabric v1.4.0-rc1.0.20220610170530-4d4dac7947db
HLF v2.4.4 use following proto-go : github.com/hyperledger/fabric-protos-go v0.0.0-20220315113721-7dc293e117f7. Currently this PR use github.com/hyperledger/fabric-protos-go v0.0.0-20220613214546-bf864f01d75e
Anyway, if FSC/FTS require very last commits from HLF, then I will match our HLF target move to the commit id FSC/FTS requires.


i guess it is possible to run in docker to prevent access from anyone to anyone's source

Yes it is possible, you can try it by using new runner https://github.com/ayufan/gitlab-ci-multi-runner


Create guide for SQL => GCS operator

It is not necessary. Let's do it later.

https://issues.apache.org/jira/browse/AIRFLOW-6275?jql=project %3D AIRFLOW AND component %3D documentation


Reintroduce support for ZLIB_CONST in compat mode.

In compat mode, the default should be next_in and msg without const qualified in zstream.

Fixes #703.

Isn't ZLIB_CONST set to const ? So maybe these should be like ZLIB_CONST unsigned int x = 0?

@nmoinvaz z_const is set to const when ZLIB_CONST is defined to any value... Value of ZLIB_CONST is ignored.

Maybe we should be using z_const instead of #ifdef ZLIB_CONST.. what do you think?

ZLIB_CONST and z_const were deprecated in our own API, so z_const is not defined anymore ever, but instead is implicitly assumed to equal to const, not empty string, so using z_const wouldn't work correctly in non-compat mode.

Maybe we need a #define in zbuild.h for internal const. Maybe like a PREFIX() but form CONST().. The only thing I don't like is all the #if else scattered throughout.

@nmoinvaz using something akin PREFIX() would get ugly as sometimes the cast needs to be unsigned char * and sometimes char *... I could perhaps add two macros to hide the casts...

#define CONST(x) const x
Else
#define CONST(x) x
..

Non-compat version would need to no-op the cast completely...

@nmoinvaz Now it's somewhat cleaner... I used three macros to avoid cases when macros would be used inside parentheses as that  is not supported on all compilers...

That does look better. I was thinking more like this that can be used for any type..
#ifdef ..
#define CONST(x) const x
#else
#define CONST(x) x
#endif
...
stream.next_in = (CONST(unsigned char*))source;
...
CONST(unsigned char) in;                /* local strm->next_in */

At least that way the type is visible in the variable declaration.. thoughts?

@nmoinvaz Like I said above, preprocessor macros don't work inside (). This is because some preprocessors pass through text inside () verbatim to compiler instead of parsing it... Developer can use the feature to disambiguate between preprocessor macro and function name.

Ok I understand now that is the reason for the extra macros. But in my example x is the variable type not the variable name. I think it should still be possible to change it to pass in the variable type instead of name..

You can't pass in variable type as it would make using the macro in casts impossible... It would essentially only work in declaration of variables or struct members where it is always surrounded by just white-space.

Looks pretty good, but as far as I can tell, this removes const from zlib-ng native as well.
I think each #ifdef should also check whether compat is enabled, as we do not want to support non-const in the native mode, only for compat mode. This also avoids problems when someone compiles the source without using our cmake/makefiles.
I am not sure I like the names of the macros though, they do not seem to tell me what they do and what their difference is, and I actually mistook one for the other during my review of the code and misremembered another, so this can easily be confused.
I'd like to see more descriptive names used.
These are from the PR currently:
#define CONSTU(x) (const unsigned char *) x
#define CONSTUP(x) const unsigned char * x
#define CONST(x)  (const char *) x

The below suggestion is meant to provoke thought and discussion, not names I really want, but these contain more information in the name, making it easier to remember what they actually mean and do.
#define C_CONST_UCP(x) (const unsigned char *) x
#define T_CONST_UCP(x)  const unsigned char * x
#define C_CONST_CP(x)  (const char *) x
// C_ / T_ = Cast / Type
// U = Unsigned
// CP = Char Pointer

@Dead2 This shouldn't remove "const" from native builds, it should do the opposite... it forces the types to have "const" qualifier...

@mtl1979 It looks to me like it depends on ZLIB_CONST being set, and it never gets set anywhere in our current code/buildsystem and it does not get set in this PR either as far as I can see.. Am I overlooking something?

It only depends on ZLIB_CONST in compatibility mode due to order of the preprocessor tests...

You are right, I overlooked the above compat test, and the fact that we have a separate zconf-ng.h.in file. Good 👍

I'm still open for suggestions for the final names of the macros.... It was just a quick hack to test how much code needed to be adapted...

I ran into this as well, when trying to use zlib-ng in zlib-compat mode. I'd like to see this change. Thanks for the fix!

Also, on what platforms can you not write (z_const unsigned char *) as a cast? I've never seen a preprocessor that wouldn't do a substitution there.

@joshtriplett I mainly use gcc on Ubuntu Linux and Visual C++ on Windows...
Only place where "(" works correctly is right-hand side of macro definition. This is because "(" acts in preprocessor input like double quotes on compiler, it starts string literal in preprocessor that ends with ")" and is parsed as single token. Only difference is that you can put "(" inside the string literal to start another string literal and the result can be passed to another preprocessor macro as input.

@mtl1979 I'm not talking about a macro that takes arguments, just a simple #define with no arguments:
/tmp$ cat test.h
#define z_const const

x = (z_const unsigned char *)y;
void func(z_const unsigned char *arg);
/tmp$ gcc -E test.h
# 1 "test.h"
# 1 "<built-in>"
# 1 "<command-line>"
# 31 "<command-line>"
# 1 "/usr/include/stdc-predef.h" 1 3 4
# 32 "<command-line>" 2
# 1 "test.h"

x = (const unsigned char *)y;
void func(const unsigned char *arg);

Regarding the macro names, can we get a show of hands for/against the current ones or any suggestions for other naming schemes?

@joshtriplett By default, gcc uses GNU extensions, which might alter the way preprocessor behaves. When we build zlib-ng, we ask it to compile using specific standard and that disables GNU extensions.

@Dead2 Obviously we can't use macro names that would possibly conflict with already defined macros... If there is no more suggestions for names, I will not change the current ones to random ones just for the sake of experimenting...

@mtl1979 Here's the same test again in C89 mode:
/tmp$ cat test.h
#define z_const const

x = (z_const unsigned char *)y;
void func(z_const unsigned char *arg);
/tmp$ gcc -std=c89 -E test.h
# 1 "test.h"
# 1 "<built-in>"
# 1 "<command-line>"
# 31 "<command-line>"
# 1 "/usr/include/stdc-predef.h" 1 3 4
# 32 "<command-line>" 2
# 1 "test.h"

x = (const unsigned char *)y;
void func(const unsigned char *arg);

@joshtriplett I tested the code on Ubuntu only and got weird errors until I changed to the current style... There was no point in testing on other operating systems, because it already failed on Linux with default gcc version available on 18.04 (x86_64).
Obviously CI tests on all other operating systems and compilers to make sure the code that works on Linux and default gcc version doesn't break on other compilers and operating systems.

@mtl1979 I checked via godbolt, and it works with ancient GCC as well, and with other compilers. I don't think the problems you were seeing were related to an interaction between parentheses and the C preprocessor, unless there was something more going on. Is it possible that there was a file using z_const that didn't include the definition of z_const?
(In any case, the fix is much more important than the naming and style of the fix, and it'd always be possible to CI-test further improvements later. Just mystified because I've never heard of a preprocessor issue like what you're describing.)

@joshtriplett I don't know what the preprocessor did, but compiler did throw an error. I've been programmer for over 30 years but never seen error like that... Getting the patch to work was back then more important than trying to capture the preprocessor output and figure out what went wrong inside the preprocessor...

@Dead2 I'm not that keen about the macro names.
@mtl1979 What if we did a typedef instead of a macro? Something like zng_const?

@nmoinvaz Using typedef would not be much cleaner as it would still require three versions.

How about just an #ifdef ZNG_CONST const?

@nmoinvaz Because this patch has nothing to do with zlib-ng API, it's about zlib compatibility API, so it would be confusing...

I think I figured out one of the weird errors I was getting... Prototype of in_func for inflateBack() was still incorrect in zlib.h... It also needed z_const instead of normal const.

I'm not understanding why the full type needs to be in the preprocessor definition. It seems like "const" is the only difference and that can be specified as a #define. Is there something I'm missing?

@nmoinvaz We don't want to introduce simple macro in non-compat mode because that would suggest that using it is optional when it is mandatory. We also don't want to use anything that leaks to the binary as a symbol.

Ok, I thought about this, and figured we should try to stay as close to stock zlib as possible if there is no tangible gain.
So I checked, and zlib just uses z_const, example from zlib/deflate.c:415:
 strm->next_in = (z_const Bytef *)dictionary;
Also zlib does this in zutil.h, a little different from how this PR does it.
extern z_const char * const z_errmsg[10]; /* indexed by 2-zlib_error */
/* (size given to avoid silly warnings with Visual C++) */

#define ERR_MSG(err) z_errmsg[Z_NEED_DICT-(err)]

So I suggest just using z_const, that is a lot simpler in any case and it stays close to stock zlib.
And if someone reports a problem caused by it, we will have a better idea of exactly what needs to be fixed and document it as such.
@mtl1979 Would you mind making a similar PR using z_const that we can test with and better decide between the two?

@Dead2 I already tried with simple z_const and it failed to compile, because implicit conversion of pointers to const are not allowed like I already explained earlier.

Added it as separate commit to test on CI...


Consider enabling "Apply" button in Watch dialog when no events are selected

Description
If you click "Watch" > "Custom" on a repo, you can select specific events to be notified about (rather than "everything", "nothing", or the default "only mentions/when participating"). However, if you uncheck all the options in that dialog, the apply button becomes disabled:

I find it moderately frustrating that this is the case; IMO, clicking apply in this state should just set the watching state to "Participating and @mentions", given the "Custom" option is described as "events you want to be notified of in addition to participating and @mentions."
Example URLs
https://github.com/refined-github/refined-github

I think the current behavior is correct.

You open a dialog that lets you choose specific events to follow
You close the dialog, cancelling your intent to choose events

Changing a setting outside this dialog isn't right, it should stay whatever was selected before opening the "custom" dialog.

I'm not a fan of the Follow dropdown as a whole, but that's a different story. See:

https://github.com/refined-github/refined-github/issues/6090

if you uncheck all the options in that dialog

If that's your intent, why are you in that dialog in the first place? You made 4-8 clicks to make an action that can be made in 2. 🤷♂

for example, I am getting a painful number of release notifications for a repository, and wish to unsubscribe from those, but I don't remember what (if any) other types of notifications I'm subscribed to.


Any way to get this to work on shared hosting server?

I would love to be able to run this on a shared hosting server. But AFAIK you need sudo privileges to install selenium.
Maybe with GhostDriver or PhantomJS?

Do you have docker on your server? I run mine from a docker container and it works great.

I'll close this as it should be possible with Docker. Thanks for the question and answer!


tests: Reduce flakiness of test_nullable_properties

Codecov Report

Merging #398 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #398      +/-   ##
==========================================
- Coverage   99.77%   99.77%   -0.01%
==========================================
  Files          25       25
  Lines        1805     1795      -10
  Branches      287      287
==========================================
- Hits         1801     1791      -10
  Misses          2        2
  Partials        2        2

Flag
Coverage Δ

#unittests
99.77% <ø> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

src/schemathesis/runner/__init__.py
99.15% <0%> (-0.01%)
:arrow_down:

src/schemathesis/extra/pytest_plugin.py
100% <0%> (ø)
:arrow_up:

src/schemathesis/models.py
100% <0%> (ø)
:arrow_up:

src/schemathesis/runner/events.py
100% <0%> (ø)
:arrow_up:

src/schemathesis/lazy.py
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Add a JSON "pseudo-API"

This commit fixes #22, although not precisely as stated.
Instead of /json/[tool] to return all the data about a specified tool as JSON, I've opted for /api/[tool]/[releaseCycle].json
The reasons are:

/api/[something].json seems like a more 'standard' format for an API URL
Using /api instead of /json means other data formats can be returned in future using the same pattern
/api/[tool]/[releaseCycle].json enables users to automate a check for the end of life date of whichever version of a tool they are using

The last point is key IMO, because it enables endoflife.date to be integrated into build pipelines.
Problems
Data Format
The format in which people have supplied 'releaseCycle' is not always consistent, e.g.:

releaseCycle: "v3.9" (alpine)
releaseCycle: "CentOS 6" (centos)
releaseCycle: 'Debian 6 "Squeeze" (LTS)' (debian)
releaseCycle: 6 (java)

For use in a build pipeline, it would be better to enforce consistency, limiting the values to [major].[minor] (i.e =~ /^\d+\.\d+$/)
Right now, users of the API would need to know the format of the data for their specific tool before they could check it, which makes the API less useful.
Build process
By adding a 'compilation' stage, using make, it is no longer possible to create a new tool entry solely using the github web interface.
This could be fixed by adding a build pipeline like this, i.e. where the build process aborts if the change which triggered the build is a commit to the 'api' directory (otherwise the build process would go into an endless loop, since every build would result in a commit, which triggers a build).

Can you look at running this from a Jekyll hook instead?
The :after_init hook is the first to run, before files are read from disk, and we can use this to generate the files. There is documentation at https://jekyllrb.com/docs/plugins/hooks/
I was planning to use the symlink approach from https://github.com/jekyll/jekyll/issues/3041#issuecomment-267730851, but since your design calls for an unknown number of templates, this might be hard to setup with symlinks.
I still think it makes sense to provide a unified API per tool as well (alongside the per-release cycle), which is a JSON version of the complete page contents for any given tool. We can keep that for later though?

It seems all that's necessary is a ruby script in _plugins/, rather than using a hook (which is just as well, because I couldn't find any useful information on how to use hooks).
This builds all the api/*.json files whenever jekyll runs.

Thanks a lot :+1:
Will review this :soon:

This is brilliant. I found this after looking into whether the site had an API. I didn't see any indication it had an API from the site itself (like no foot note at the bottom etc). Tried it with https://endoflife.date/api/nodejs/12.json and it works perfectly. My use case is that I want to set up automation where we get a Slack message or something if some version we're using is going to pass EOL date soon. This will work perfectly.

Great. I'm glad it helps. That's exactly the kind of use case I had in
mind.
On Mon, May 31, 2021, 13:56 Matt Welke @.***> wrote:

This is brilliant. I found this after looking into whether the site had an
API. I didn't see any indication it had an API from the site itself (like
no foot note at the bottom etc). Tried it with
https://endoflife.date/api/nodejs/12.json and it works perfectly. My use
case is that I want to set up automation where we get a Slack message or
something if some version we're using is going to pass EOL date soon. This
will work perfectly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/endoflife-date/endoflife.date/pull/61#issuecomment-851171694,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAASIXPAQLAXLCSU72TII3TQMJJXANCNFSM4H2Y4IJQ
.


Toggle Ribbon Icon

Right now, removing the trash icon from the ribbon via the Obsidian->Appearance->Ribbon Menu option doesn't work. Upon restarting, the icon re-appears. Since we also have the icon in the menu above the file pane, is there a way to disable the ribbon icon?

Sounds annoying for sure ☹
I can't reproduce this issue on desktop or mobile - the ribbon icon stays hidden after a restart. If you open the hidden .obsidian/workspace.json file in your vault it should contain something like this:
  "left-ribbon": {
    "hiddenItems": {
      "obsidian-trash-explorer:Open trash explorer": true
    }
  },

Is this the case?


1.8: Test: Circumvented a pip-check-reqs issue by excluding its version 2.5.0

Rolls back PR #455 into 1.8.1

coverage: 33.944%. first build when pulling f88b7609eee4fee0285efc82255c4fb483c30705 on 1.8/andy/fix-pip-check-reqs-issue into 63327a096de2b1ace245a7c4e4a6431dacf83415 on stable_1.8.


poor performance on lodash flow check

I found that #1696 (better handling null/undefined) introduced bad performance to flow checking
tested with flow version 0.63, 0.64
tested script
// @flow

import _ from 'lodash';

_.map([], () => 0);

comparison
file
time spent

before
before pr #1696
~2 seconds

after
current master
~45 seconds

Could we do anything to improve this?

Removing all the individual module declarations (introduced here) solved this for me.

@Zmetser Individual module declarations were introduced after this issue was actually opened, so I'm not sure they are root cause of the issue

@maxmalov You're right, I'm sorry. You just added the fp exports and I removed all.
Still, removing all the individual exports speeds up flow. Here's a test repo where flow only reads the lodash libdef and does nothing else when you run yarn flow and there's almost a minute difference. https://github.com/Zmetser/lodash_flow_test

I retest this issue with flow version 0.69, it takes ~2sec, seem this issue has been resolved.
Thanks.


fix(health): false positive when checking for packer, plugged, paq

Not sure if it's worth it to make it any more robust, it still matches paths if the username is exactly packer, plugged or paq, but at least it's not matching at the substring level
Fixes https://github.com/folke/lazy.nvim/issues/798

This may fail on Windows


I want to add github stats section as well

Hi, I reviewed the application by setting up successfully and running it. The app looks nice, but I want to add github stats for the users as well: for e.g. how many stars they've received, how many number of commits they've pushed, etc.
How about that? Coulf you please assign me the feature request in order to begin the work?
Thanks in advance

@theterrificm any progress?

hello @Ahsankhalid618 i would like to work on these!

@theterrificm any progress?

Hi Ahsan, I hope you are doing great. Please expect an update by tomorrow or Wednesday hopefully.

Hello Ahsan, since you asked for the screenshot first, here's the screenshot from ft section:

Let me know if can proceed to push?
Thanks in advance

@theterrificm Did you pick these Stats containers from Readme? if yes, These are, not aligned with the Project or its concept, It's just a single line of markdown to be added which is not needed in the Production project. GitHub Stats are a good thing to add in a project but not like that, Either create a react bases component (you can even choose any library like NextUI or ShadCN, etc)for stats and then render the stats in such a manner that it should align with the UI of the Project.


I encountered a problem during installation.

Please explain the issue you're experiencing (with as much detail as possible):
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error
× Preparing metadata (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [6 lines of output]
  Cargo, the Rust package manager, is not installed or is not on PATH.
  This package requires Rust and Cargo to compile extensions. Install it through
  the system's package manager or via https://rustup.rs/

  Checking for Rust toolchain....
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Hello @hcq11419, thanks for posting your question!
An important part of the error message is missing and I cannot help without knowing more understand.
However, I have a strong feeling that your error is related to the package rtoml, see #398. I will soon publish a temporary fix (#432), but you should be able to fix it by yourself by following the hints in #398.
Can you confirm if that is the same issue? If not, can you please give more details, with the full error traceback?


Update to v6.0.9 of wakatime

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Use interface for avoid error with instance passed

Avoid this error:
Argument 1 passed to Bukashk0zzz\FilterBundle\Service\Filter::__construct() must be an instance of Doctrine\Common\Annotations\CachedReader, instance of Doctrine\Common\Annotations\PsrCachedReader !!     given
Appeared when upgrading components to Symfony 4.4.24

Thanks.


Sort Thunderstore mod browser by outdated first

Right now there's not an easy way in FlightCore to see which mods are outdated. The optimal way would be to update the local mods view to show outdated Thunderstore mods.
Until this is done (I'm rather busy atm) we could also update the sort function in the Thunderstore mod browser view to sort by outdated first and then by upload date.
This way opening Thunderstore mod browser would instantly show all outdated mods ^^

@Alystrasz thoughts? ^^

I don't think we should show Thunderstore mods in local mods view.
More than putting outdated mods first, we could also display a badge on the "Online mods" menu item, showing how many mods are outdated.

I don't think we should show Thunderstore mods in local mods view.

I meant as in have a way in local mods to see which (Thunderstore) mods are outdated ^^

More than putting outdated mods first, we could also display a badge on the "Online mods" menu item, showing how many mods are outdated.

A badge has been on my todo list for a while. From the badge the user needs a way to see the outdated mods though. Kinda annoying otherwise if it tells you how many mods are outdated but no easy way to update them ;)

Actually we could also do Installed as a sort option to quickly see which Thunderstore mods are installed. In general in FlightCore it's currently super difficult to see which Thunderstore mods are installed.


[search] Keyboard appears to have a black accessory view, which hides results

There’s an extra black view above the keyboard, which makes it look like there are no more search results behind the keyboard. E.g.

When in fact, these are all the results when the keyboard is dismissed:

Need to check if this is still a problem when implementing the new search UI.

Could be that it's got a constraint that was made for small phones that was never updated

What device is this on? just tested on 6 and 6 plus and it looks fine

The accessory view is constrained to reach 20px above they keyboard, which is more obvious in the first image. in the second image, that 20px just happens to fall between two search results. Neither looks like the image in the original issue though.

A 4S, where the accessory view is much bigger. Nonetheless, that accessory view in your first screenshot doesn’t look nice either. Why is there an accessory view at all?

Fixed by #569.


Simple Java Mail Wishlist -- email.setMessagePriority

I recently became acquainted with SimpleJavaMail.    Thank you very much for making it, and sharing it with us!
On your website, you asked for suggestions for how it could be improved.  I have a few "wishlist" items for it.  I'll put them in separate tickets so you can evaluate and track them individually.

Please consider adding a setMessagePriority(int iMsgPriority) method:
email.setMessagePriority(___);

email.setReturnReceiptRequested(boolean b)  // default = false

msg.addHeader("X-Priority", ("" + iMsgPriority));  // 1 - 5

Values: 1 = High, 3 = Normal, 5 = Low

Yes, we could set it with a custom header, but it would be nice if we didn't have to program it ourselves -- especially so people don't need to learn the intricacies of mail headers.

Is the priority a standardized field or otherwise defacto standard? I know Outlook maintains its own flag for example, I'm not aware of any standardization in this sense. I'd have to look through the RFC to be sure though.
If not, I'm not sure who the target audience would be with "X-Priority".
On a sidenote, setReturnReceiptRequested was a copy/paste mistake I assume?

Thank you for considering this.  I believe the X-Priority values are standard, although it can be any number from 1 - 5, with 1 = High, 2 = Medium High, 3 = Normal, 4 = Medium Low, 5 = Low.  If I've ever read the RFC, it's been many years...
And yes, the "setReturnReceiptRequested" was a copy/paste mistake.  Please forgive me.

This field is non-standard: https://people.dsv.su.se/~jpalme/ietf/mail-headers/mail-headers.html
I don't think it is a good idea to include this in the API. I think the nest best approach is by setting a header on the builder:
Email email = new EmailBuilder()
   .addHeader("X-Priority", 2)
   .build();


links containing _ broken in html

all the links containing _ are broken in the html because they are directly copied as \_ from the bib somehow.

Thank you for reporting! Sorry I just saw this.
I'm still trying to figure out a good workflow to convert to HTML and will try to fix this next.


--whitelist-domain doesn't respect protocol on redirect

I'm using oauth2_proxy with AWS Cognito. Previously i was using bitly/OAuth2_Proxy and multiple oauth2_proxy pods in k8s to protect all the internal services, now i'm trying to replace those multiples pods with the --whitelist-domain setting available in v3.1.0 of this fork.
The problem i'm having is that oauth_proxy is setting HTTP as protocol on the redirect URL, ignoring the callbacks defined in Cognito, which all have HTTPS as protocol
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  labels:
    k8s-app: oauth2-proxy
  name: oauth2-proxy
  namespace: kube-system
spec:
  replicas: 1
  selector:
    matchLabels:
      k8s-app: oauth2-proxy
  template:
    metadata:
      labels:
        k8s-app: oauth2-proxy
    spec:
      containers:
      - args:
        - --provider=oidc
        - --email-domain=*
        - --upstream=file:///dev/null
        - --http-address=<IP_ADDRESS>:4180
        - --scope=openid
        - --cookie-secure=false
        - --oidc-issuer-url=https://cognito-idp.us-east-1.amazonaws.com/POOL_ID
        - --whitelist-domain=.mydomain.com
        - --login-url=https://oauth.mydomain.com/oauth2/authorize
        - --profile-url=https://oauth.mydomain.com/oauth2/userInfo
        - --redeem-url=https://oauth.mydomain.com/oauth2/token
        env:
           .....
        image: quay.io/pusher/oauth2_proxy:v3.1.0
        imagePullPolicy: Always
        name: oauth2-proxy
        ports:
        - containerPort: 4180
          protocol: TCP

Version used:

3.1.0

http vs https is selected for automatic redirect-url based on the cookie-secure option, so if you enable cookie-secure you should get https
https://github.com/pusher/oauth2_proxy/blob/v3.1.0/oauthproxy.go#L256-L257

Enabling the flag --cookie-secure  worked, but it requires users to have 3th-party cookies enabled in the browser, otherwise they get an error. There is no way to enable HTTPS without having to set cookie-secure set to true?

Enabling the flag --cookie-secure worked, but it requires users to have 3th-party cookies enabled

I find this to be a surprising requirement.

There is no way to enable HTTPS on the redirect url without having to set cookie-secure set to true?

Besides a single hard-coded redirect url, no, sorry ... fastest way at this point would be to edit the code and re-build. Or maybe some nginx rules could rewrite the location header.

I may have jumped into conclusions too quickly. There was something on my firefox installation causing problems, but seems like it's not related to 3th party cookies, i couldn't reproduce the problem with chrome and 3th party cookies disabled.
After clearing cache and cookies in firefox it started to work just fine. Thanks for the help @ploxiln ! i'm closing the issue.


ReferenceError: exports is not defined in ES module scope

Thanks for the great work on this module - we use it everyday in our product and I much appreciate all the effort that goes in 🙏
Describe the bug
After upgrading to the latest version, the widget creates an unrecoverable error. Before upgrading everything seems to work fine.
Expected behavior
The widget works as before.
Code / screenshots
file:///Users/FOLDER/node_modules/@uploadcare/react-widget/dist/cjs/index.js:3
Object.defineProperty(exports, '__esModule', { value: true });
                      ^

ReferenceError: exports is not defined in ES module scope
This file is being treated as an ES module because it has a '.js' file extension and<EMAIL_ADDRESS>contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.
    at file:///Users/FOLDER/node_modules/@uploadcare/react-widget/dist/cjs/index.js:3:23
    at ModuleJob.run (node:internal/modules/esm/module_job:185:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:281:24)
    at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15)

Environment

Library version:  2.1.3
Language/framework version: BlitzJS 0.45.4
OS version: macOS 12.4

Might this be related to the changes in #333?

Hey @chartgerink,
please try v2.1.4 and tell me if it works for you

@nd0ut ahh perfect, thank you!
dependabot hadn't upgraded to this one - sorry to hassle you and much appreciated for the very rapid response on here!


Interaction event deserialization problem

I managed to fix deserialization of interaction events with non-empty data field mentioned in #50 . Please take a look.

Closes #50


[P2] string related tests contained in soletta/src/test-fbp/ failed to run in Galileo board G2.

soletta v1_beta2 sha1: 3baae03daa72e6c0587a17c7750a463c813b4e55
The following tests failed to run:
string-compare.fbp
string-lower-upper.fbp
string-concat.fbp
string-regexp-search.fbp
string-length.fbp
A complete list of returned errors is founded in the following link:
http://pastebin.com/hCVRyJZY
Thank you.

string tests right now were maybe to stress the use of ICU. When compiling to galileo and edison, a priori you don't have ICU, so the default backend is used and thus those tests don't work. We will release a set of tests to exercise both backends soon.

@dborquez can you confirm that this is solved? We now have ascii tests but the icu tests are still supposed to fail if you dont have icu.

I have tested the V1 Beta 6 (a1adfd1699fffae01e6ec0beda44bc7865923766) and it works.


[BUG] Multi-signature unexpected failure (tx_bad_auth_extra while all signers are legit)

Description
When a transaction is signed by more legit signers than required, it will be rejected with 'tx_bad_auth_extra' error.
Expected behavior
The transaction should be validated and each legit signer should be recorded into the blockchain; Or at least the transaction should get validaded. (to be done in Stellar horizon?)
The rationale for including all the signatures is that there's usage cases where it does matters who signed, beyond the fact that the threshold have been met. For instance: voting system, legal contracts, proof of presence. Those are commons use of blockchain systems that could easily and cheaply get supported by Stellar. (to be done in Stellar core?)
Consequences
In the current state of affairs wallets/authenticator multisig implementors have to implement additional routines to remove valid signatures from transaction so that the transaction get validated.
Steps to reproduce
StellarSdk.Network.useTestNetwork()
var server = new StellarSdk.Server('https://horizon-testnet.stellar.org')
var account1 = StellarSdk.Keypair.random()
var account2 = StellarSdk.Keypair.random()

function fundAccount (publicKey) {
  return new Promise(function (resolve, reject) {
    const xhr = new XMLHttpRequest()
    xhr.open('GET', 'https://friendbot.stellar.org/?addr=' + publicKey, true)
    xhr.send()
    xhr.onloadend = function () {
      if (xhr.readyState === 4 && xhr.status === 200) resolve()
      else reject()
    }
  })
}

console.log('Fund account1')
fundAccount(account1.publicKey())
  .then(function() {
    console.log('Fund account2')
    return fundAccount(account2.publicKey())
  })
  .then(function() {
    console.log('Set account2 as signer for account1')
    return server.loadAccount(account1.publicKey())
  })
  .then(function(account) {
    var tx = new StellarSdk.TransactionBuilder(account)
      .addOperation(StellarSdk.Operation.setOptions({
        signer: { weight: 1, ed25519PublicKey: account2.publicKey() }
      }))
      .build()
    tx.sign(account1)
    return server.submitTransaction(tx)
  })
  .then(function() {
    console.log('Sign a transaction with both account1 & account2 and send')
    return server.loadAccount(account1.publicKey())
  })
  .then(function(account) {
    console.log(account)
    var tx = new StellarSdk.TransactionBuilder(account)
      .addOperation(StellarSdk.Operation.setOptions({}))
      .build()
    tx.sign(account1)
    tx.sign(account2)
    return server.submitTransaction(tx)
  })
  .then(console.log)
  .catch(console.log)

This can't be changed in this repository, move the issue to https://github.com/stellar/stellar-core.

Horizon is not accepting any transactions, it's passing them to core. This this is solely connected to core.

[deleted my previous comment]
I don't think horizon should modify submitted transactions in any way. I'll wait for others's opinion and then we can decide whether to reopen this or not.