Error Removing Claims

Thanks again for your hard work on this project (and for all those that contribute as well).
This is the same error as the OP in #340
Unfortunately, that issue was closed, however the issue did not seem to be resolved for the OP ... @julianpaulozzi sortof hijacked the issue and it was closed. (Please no offense meant).
So, back to the issue if you don't want to read #340 ... when deleting a claim (with latest EF and MR from NuGet), I receive the following error:
System.InvalidOperationException was caught
  _HResult=-2146233079
  _message=The operation failed: The relationship could not be changed because one or more of the foreign-key properties is non-nullable. When a change is made to a relationship, the related foreign-key property is set to a null value. If the foreign-key does not support null values, a new relationship must be defined, the foreign-key property must be assigned another non-null value, or the unrelated object must be deleted.
  HResult=-2146233079
  IsTransient=false
  Message=The operation failed: The relationship could not be changed because one or more of the foreign-key properties is non-nullable. When a change is made to a relationship, the related foreign-key property is set to a null value. If the foreign-key does not support null values, a new relationship must be defined, the foreign-key property must be assigned another non-null value, or the unrelated object must be deleted.
  Source=EntityFramework
  StackTrace:
       at System.Data.Entity.Core.Objects.ObjectContext.PrepareToSaveChanges(SaveOptions options)
       at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesInternal(SaveOptions options, Boolean executeInExistingTransaction)
       at System.Data.Entity.Core.Objects.ObjectContext.SaveChanges(SaveOptions options)
       at System.Data.Entity.Internal.InternalContext.SaveChanges()
       at System.Data.Entity.Internal.LazyInternalContext.SaveChanges()
       at System.Data.Entity.DbContext.SaveChanges()
       at E_Tabs.Dashboards.Infrastructure.Data.EtdsContext.SaveChanges(Int32 userAccountKey) in c:\01 Development\Dashboard System\Source Code\02 Infrastructure\E-Tabs.Dashboards.Infrastructure\Data\EtdsContext.cs:line 442
       at E_Tabs.Dashboards.Infrastructure.Data.EtdsContext.SaveChanges() in c:\01 Development\Dashboard System\Source Code\02 Infrastructure\E-Tabs.Dashboards.Infrastructure\Data\EtdsContext.cs:line 417
       at BrockAllen.MembershipReboot.Ef.DbContextUserAccountRepository`2.SaveChanges() in c:\ballen\github\BrockAllen.MembershipReboot\src\BrockAllen.MembershipReboot.Ef\DbContextUserAccountRepository.cs:line 62
       at BrockAllen.MembershipReboot.Ef.DbContextUserAccountRepository`2.Update(TAccount item) in c:\ballen\github\BrockAllen.MembershipReboot\src\BrockAllen.MembershipReboot.Ef\DbContextUserAccountRepository.cs:line 95
       at BrockAllen.MembershipReboot.EventBusUserAccountRepository`1.Update(TAccount item) in c:\ballen\github\BrockAllen.MembershipReboot\src\BrockAllen.MembershipReboot\Repository\EventBusUserAccountRepository.cs:line 71
       at BrockAllen.MembershipReboot.UserAccountService`1.UpdateInternal(TAccount account) in c:\ballen\github\BrockAllen.MembershipReboot\src\BrockAllen.MembershipReboot\AccountService\UserAccountService.cs:line 174
       at BrockAllen.MembershipReboot.UserAccountService`1.Update(TAccount account) in c:\ballen\github\BrockAllen.MembershipReboot\src\BrockAllen.MembershipReboot\AccountService\UserAccountService.cs:line 161
       at BrockAllen.MembershipReboot.UserAccountService`1.RemoveClaim(Guid accountID, String type) in c:\ballen\github\BrockAllen.MembershipReboot\src\BrockAllen.MembershipReboot\AccountService\UserAccountService.cs:line 2395
       at E_Tabs.Dashboards.Web.Code.Helpers.MembershipHelper.ChangeAlternateEmail(UserAccountService accountService, Guid id, String address) in c:\01 Development\Dashboard System\Source Code\03 Web Applications\E-Tabs.Dashboards.Web\Code\Helpers\MembershipHelper.cs:line 131
  InnerException:

Now, I have in fact called
this.RegisterUserAccountChildTablesForDelete<EtdsUserAccount>();

in my DBContext constructor. This does not do anything for the issue. Any other suggestions? And ... I do not believe this is related to Thinktecture.IdentityManager.

@AlonCG I know it has been a lot of time since you asked your question. But in case you are still interested - ensure that you define all the properties of your custom UserAccount-derived type with the virtual keyword. This was the case for me.


Updating Keywords, Negative Keywords, Targets and Negative Targets to Version 3

Adding the new endpoints to Version 3 of SP API.
Updating Keywords, Negative Keywords, Targets and Negative Targets to Version 3.
Please check to make sure I didn't forget to add anything in docs.
By the way, I've seen that Product Targeting already implements some endpoints but not all, so I added the new ones in the extra product_targeting_v3. Be sure to check it out.
In case something needs to be changed just let me know!
Thank you ;)

No worries, just take your time.
On Mon, Apr 3, 2023, 16:16 Daniel @.***> wrote:

@.**** commented on this pull request.
Hi Hamza, will need some time to check but I will let you know later.
—
Reply to this email directly, view it on GitHub
https://github.com/denisneuf/python-amazon-ad-api/pull/133#pullrequestreview-1369370763,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ3MXETO2MYXCFBH7RPRTTDW7LZU5ANCNFSM6AAAAAAWRQ6MPU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thank you! Let me know if you need any help with anything, I'd be glad to assit :)

Hi Hamza,
Could you have a look at sp3:

InitialBudgetRecommendation

ad_api/api/sp/budget_initial_recommendation.py
InitialBudgetRecommendation
I am not able to make it work using no matter 3+4 or 3 or 4
json_version = 'application/vnd.spinitialbudgetrecommendation.v3.4+json'
Always get 'status_code': 403 not a valid key=value pair (missing equal-sign) in Authorization header:

CampaignsRecommendations

ad_api/api/sp/campaign_consolidated_recommendations.py
I only have access to EU marketplaces and always get
{
"code":400,
"responseHeaders":null,
"responseBody":null,
"message":"Marketplace is not supported"
}
Can you test in US or JP accounts?
Thank you in advance,
Daniel

El 8 abr 2023, a las 7:51, Hamza @.***> escribió:
Thank you! Let me know if you need any help with anything, I'd be glad to assit :)
—
Reply to this email directly, view it on GitHub https://github.com/denisneuf/python-amazon-ad-api/pull/133#issuecomment-1500727359, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD4ENUSZOHFDJE4JT5WMRKTXACR7FANCNFSM6AAAAAAWRQ6MPU.
You are receiving this because you modified the open/close state.

Hi Daniel,
I'll have a look at it and let you know. Unfortunatly I don't have US or JP accounts im using an EU one for the testing.
I'll keep in touch.
Best,
Hamza


Resolve LoggerService Import Issue in Truffle Configuration

Resolve LoggerService Import Issue in Truffle Configuration
Bug Report: LoggerService Import Error
Problem Statement
The LoggerService is not being imported correctly in the Truffle configuration file, causing runtime errors or misbehavior when logging events during the deployment process. This disrupts the workflow and requires immediate attention to ensure smooth deployments.

Steps to Reproduce

Attempt to run a deployment using the current Truffle configuration.
Observe the error related to the missing or incorrect LoggerService import.
Verify that the LoggerService is correctly implemented and available in the project.

Expected Behavior
The LoggerService should import correctly and function as intended, logging deployment events without any issues.

Proposed Solution

Investigate the root cause of the import issue.
Ensure the LoggerService file path and module exports are correct.
Update the Truffle configuration to correctly import and use LoggerService.
Test the deployment process to confirm the logger is working as expected.

Tasks Checklist

[x] Verify the availability and correctness of the LoggerService module.
[x] Check the import statement in the Truffle configuration file.
[x] Fix any path or export issues causing the import error.
[x] Validate the functionality of the logger during deployment.
[x] Write or update tests to cover the LoggerService usage in Truffle.
[x] Update documentation if any changes to the logger usage are required.

Expected Benefits

Resolves the import issue, ensuring the logger works seamlessly during deployments.
Improves the reliability and traceability of deployment logs.
Reduces debugging time for deployment-related errors.

References

Truffle Configuration Documentation
Node.js Module System Documentation

Truffle Logging Configuration in DocuChain Backend
Problem Statement
During the implementation of a blockchain-based document ownership platform, we encountered challenges integrating a centralized logging mechanism with Truffle's configuration and compilation process.
Detailed Issue Description
When attempting to implement a custom logger in the Truffle configuration, multiple compatibility issues arose:

ES Module vs CommonJS Compatibility

Initial implementation used ES Module syntax (import/export)
Truffle's configuration loader was incompatible with ES Module imports

Module Resolution Errors

Incorrect module path resolution
Challenges in requiring custom logger modules

Solution Approach
Key Implementation Steps

Logger Configuration

Utilized Winston for robust logging capabilities
Implemented a CommonJS-compatible logger

Truffle Configuration Modification

Added Dependencies to truffle configuration module  "dependencies": {
    "winston": "^3.17.0",
    "winston-daily-rotate-file": "^4.7.1"
  }

Dependencies
Required Packages

winston: ^3.17.0
winston-daily-rotate-file: ^4.7.1

Installation
npm install winston winston-daily-rotate-file

Best Practices

Module Compatibility

Prefer CommonJS (require) for Truffle configurations
Use absolute or explicit relative paths for module imports

Logging Configuration

Implement flexible logging with multiple transports
Include both console and file-based logging
Use environment-specific logging levels

Potential Pitfalls to Avoid

❌ Using ES Module syntax in Truffle config
❌ Incorrect module path resolution
❌ Overcomplicating logger implementation

Benefits of Implemented Solution
✅ Consistent logging across Truffle and backend
✅ Flexible logging configuration
✅ Improved debugging capabilities
✅ Minimal configuration overhead
Code Locations

Logger Configuration: truffle/truffleLogger.js
Truffle Config: truffle/truffle-config.js

Would you like me to modify or refine any part of this documentation?


Add grammar for char, string, byte, and raw literals

Part of #84.

Now that underscores are accepted in unicode escapes in Rust 1.22, should the UNICODE_ESCAPE production include underscores?  Maybe something like this?
UNICODE_ESCAPE :
    \u{ HEX_DIGIT _* }
  | \u{ HEX_DIGIT _* HEX_DIGIT _* }
  | \u{ HEX_DIGIT _* HEX_DIGIT _* HEX_DIGIT _* }
  | \u{ HEX_DIGIT _* HEX_DIGIT _* HEX_DIGIT _* HEX_DIGIT _* }
  | \u{ HEX_DIGIT _* HEX_DIGIT _* HEX_DIGIT _* HEX_DIGIT _* HEX_DIGIT _* }
  | \u{ HEX_DIGIT _* HEX_DIGIT _* HEX_DIGIT _* HEX_DIGIT _* HEX_DIGIT _* HEX_DIGIT _* }

should the UNICODE_ESCAPE production include underscores?  Maybe something like this?

Cool! I wasn't aware of that :). Yes, that would be the way I would include it in the grammar.
So... I am against including this right now. The problem in including this change is that I'm testing the grammar on stable to avoid having such a fast moving target and to avoid including in it things that maybe will took too long or never reach stable at all (since in my understanding lots of things on nightly are experimental).
Also, correct me if I am wrong: the Rust 1.22 you talk about is actually nightly, right? It doesn't mean this will be released on Rust 1.22, right? The underscore in Unicode escapes isn't available even in beta yet (Rust 1.21.beta3).

Rust 1.22 you talk about is actually nightly, right?

Nightly, yes.
BTW, do you want some help on this?  I'd be willing to help if you could point me to things to add/fix.  I also might have some questions about the grammar you have so far, and am curious how you're testing it.

The underscores in Unicode escapes is insta-stable (there's no feature gate) and the reference rides the release trains, so it should be included in this grammar. It can be done in a separate PR if that would help.

@Havvy

LGTM, minus the underscores from other comments

I've added them. Shouldn't they already be on beta, then? Or is it too soon?
@ehuss

BTW, do you want some help on this? I'd be willing to help if you could point me to things to add/fix.

Yeah, that would be great. But I have too many things half done... I  will need to take a look at what I have and commit it.

I also might have some questions about the grammar you have so far

I'm on IRC sometimes, on #rust-docs .

and am curious how you're testing it.

I'm reading the rustc's parser/lexer, making an Antlr4 grammar out of it, and making some test cases and testing them against my grammar and rustc.

Now it is a little too long. I didn't want to use {n, m} notation but maybe

\u{ ( HEX_DIGIT _* ){1,6} }

would be a better way to do this? Or even

\u{ ( HEX_DIGIT _* )1..6 }

Yeah. It's literally one character too long when I render it, and spilling onto the next line in a confusing way. 😕 I don't care whether it's {n,m} or n..m, or even 1 to 6 repetitions just as long as it conveys what is going on. It might be useful to describe the notation used by the grammar in lexical-structure.html including any interesting things you use.

💟 Thanks.


barcode text is not sharp

Hi,
The text below the barcode is not sharp. The demo online with the same options looks fine.
UPC barcode:
<canvas id="barcode"><canvas>

JsBarcode("#barcode", "123456789012", {
  format: "UPC",
  width:1,
  height:50,
  fontSize:14
});

The text is vague. What is missing?  Does the font of web page affect the font of barcode within the page?
For code128, the font of text is shown differently from other code such as UPC or EAN13 with the same options, much bigger.
Thanks.
UPC code:

Code128:

Test to render on a SVG element instead. Canvas might give problems on for example high DPI screens

Thanks for quick help. SVG works better than canvas. But for the same font size, the font will be bigger if the barcode is flat such as code128, ean8.

The font size will be limited on EAN-13 to not clip the barcode lines.

Thanks.


KAFKA-16104: Enable additional PlaintextConsumerTest tests for new consumer

We reevaluated the integration tests that were disabled for the new consumer group protocol which should be supported. The evaluation was to run the PlaintextConsumerTest suite ten times and see which tests passed and which failed.
Based on that evaluation, the following test can now be enabled:

testAutoCommitOnClose
testAutoCommitOnCloseAfterWakeup
testAutoCommitOnRebalance
testExpandingTopicSubscriptions
testMultiConsumerSessionTimeoutOnClose
testMultiConsumerSessionTimeoutOnStopPolling
testShrinkingTopicSubscriptions

There are three tests which consistently failed. For each, a dedicated Jira was created to track and fix. Those that failed:

testPerPartitionLagMetricsCleanUpWithSubscribe (failure rate 100%, KAFKA-16150)
testPerPartitionLeadMetricsCleanUpWithSubscribe (failure rate: 70%, KAFKA-16151)
testStaticConsumerDetectsNewPartitionCreatedAfterRestart (failure rate: 100%, KAFKA-16152)

See KAFKA-16104 for more details.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Closing and reopening to kick off another test run

Closing and reopening to kick off another test run


Request Entity Too Large

We've currently got Aqua Helm chart running console and a scanner, but when scanning a particular image locally from my Mac command line, we're getting the error
"twirp error unknown: Error from intermediary with HTTP status code 413 "Request Entity Too Large""
The image is 1.4gb.
The confusing factor in this, is that when scanning the same image from the console, it works fine.

I had a similar issue, - this was due to a ingress controller not allowing "large" payloads.
Our nginx ingress controller reads annotations and could be set via our helm install with set commands:
--set web.ingress.annotations."nginx.ingress.kubernetes.io/client-body-buffer-size"=""
--set web.ingress.annotations."nginx.ingress.kubernetes.io/proxy-body-size"="" \
it most likely depends on your loadbalancer/ingress
more here:
https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md
and heres more info :
https://github.com/kubernetes/ingress-nginx/issues/1824


It appears that move to voteview.com has broke in the Rapi !!!

Search and download functions of the Rapi are currently broken (all requests hang).

They no longer seem to be hanging.


try cicd on specific image to narrow down issue

Reference Issues or PRs
image tag comes from this build

What does this implement/fix?
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[ ] Did you test the pull request locally?
[ ] Did you add new tests?

Any other comments?

Issue resolved elsewhere, closing


Refactor Job.FileStore into fileStore.py (resolves #1028)

resolves #1028

Jenkins, test this please.

@hannes-ucsc this is ready!

Just that tiny inspection thing. And can you confirm for all eternity that you didn't touch the actual FileStore code in this PR?

i updated 2 docstrings.... is that a problem?

No

@hannes-ucsc this is ready!


Fix markdown numbered list handling of blank lines between blocks

If you write
1. first
1. second

Zulip's auto-numbering thing works and turns it into 1/2.  However,
1. first

1. second

apparently that just results in two 1.s in their own paragraphs.

@zulipbot claim

(Read our "markdown" subsystem docs, and AutoNumberOListPreprocessor in particular, for working on this).

(Read our "markdown" subsystem docs, and AutoNumberOListPreprocessor in particular, for working on this).

Tim, thanks, I'll look :)


Syft does not log warnings when no tty is present

What happened:
Important WARN logs like
[0000]  WARN file could not be unarchived: unable to create tempdir for archive processing: stat /tmp: no such file or directory

Are not visible  / not logged, when no TTY is present. This happens especially in my GitLab pipelines where jobs do not have a tty.
What you expected to happen:
I expect that all logs, especially with Level >= WARN are being logged when /dev/stdout and /dev/stderr are present. A missing (pseudo)tty should not cause missing logs.
Steps to reproduce the issue:
Build a container with a broken environment where no temp dir exists and try to scan a test artifact (in my case containerimage.tar) in this container. 1 Try with a pseudo tty and one time without a tty. You'll see the warnings only, when a pseudo tty has been allocated. I verified, that even without the pseudo tty, /dev/stdout and /dev/stderr are there and work as intended.
Test container:
FROM scratch
COPY syft /
COPY containerimage.tar /
ENTRYPOINT ["/syft"]

Run without tty:
❯ podman run -i syft scan /containerimage.tar
No packages discovered

Run with pseudo tty:
❯ podman run -ti syft scan /containerimage.tar
 ✔ Indexed file system                                                                                /
 ✔ Cataloged contents                                                                                ccf875aa8af6073319964e9d36823bf7337a7ca8caf5c386c818452a7307c45f
   ├── ✔ Packages                        [0 packages]
   └── ✔ Executables                     [0 executables]
[0000]  WARN file could not be unarchived: unable to create tempdir for archive processing: stat /tmp: no such file or directory
[0001]  WARN unable to determine GOPATH or user home dir: %!w(string=exec: "getent": executable file not found in $PATH)
[0001]  WARN unable to determine GOPATH or user home dir: %!w(string=exec: "getent": executable file not found in $PATH)
No packages discovered

Anything else we need to know?:
I assume that the logs are missing, because when no TTY is there some special terminal tricks like animations don't work.
Environment:

Syft 1.9.0
OCI-Container of all kind

I have the same problem with Grype.
Adding --verbose helps to see warnings. But stuff like ✔ Indexed file system would still not be printed.

Thanks @devfbe for filing the issue! When we have some cycles we can take a look and see where the creation of the logger is failing/dependent on the presence of the tty. We do agree that this should just work sans tty detection.
PRs are also welcome and we can help get those merged if you happen to find where this might be failing in syft.
Thanks!

I did a little more work understanding what's happening over on the related Grype issue: https://github.com/anchore/grype/issues/2180#issuecomment-2416559398
I think it might be a clio fix, but I think, in general, when we have a noUI setup in clio, we should still make a stderr logger set at WARN.

I did some experiments and proved a couple for things:

We discard log.Warn incorrectly when there's no TTY present, because the lack of TTY makes us not initiate the terminal UI, and the lack of --verbose makes us not initiate the stderr logger.
The same issue affects grype (see link above)
The bug is in clio (see below)

https://github.com/anchore/clio/blob/f538a9016e10cb9563c9fb40f0d3345ba12e6c70/logging.go#L44  is incorrect, because it assumes that there's nothing to log if there's verbosity=0, but verbosity=0 is log.Warn, so we should still initiate stderr logging here, even if there's no TTY.


Scaling ol.style.Circle - Ugly Result

Hi,
in my example at https://codepen.io/gott18/pen/WNyvprQ I created an ellipsis by scaling ol.style.Circle and recognized that the result looks very ugly (pixelated, different stroke width between top/bottom and left/right).
Is there any chance to make an ellipsis used in a style more beautiful (without using an image file as icon)?
Thanks,
Thomas

When scaling RegularShape and Circle styles pixelation can be avoided by setting a larger radius then scaling down:
  radius: 80,
  scale: [1, 0.25],

To avoid scaling the stroke set the style geometry as an ellipse https://codepen.io/mike-000/pen/ExRjmvB

You could use a custom symbol, like shown in https://openlayers.org/en/latest/examples/earthquake-custom-symbol.html. In your example, it could look like this: https://codepen.io/ahocevar/pen/MWXwmqx
const canvas = document.createElement('canvas');
canvas.width = 200;
canvas.height = 50;
const ctx = canvas.getContext('2d');

// Draw the ellipse
ctx.beginPath();
ctx.ellipse(100, 25, 24, 98, Math.PI / 2, 0, 2 * Math.PI);
ctx.strokeStyle = 'red';
ctx.lineWidth = 2;
ctx.stroke();

var stylefn = function() {
  return new ol.style.Style({
    image: new ol.style.Icon({
      img: canvas,
      imgSize: [canvas.width, canvas.height]
    })
  });
};


Cannot install under OSX

When installing ztag under OSX I get the following error:
Installed /usr/local/lib/python2.7/site-packages/ztag-1.0.0-py2.7.egg Processing dependencies for ztag==1.0.0 error: protobuf 3.0.0 is installed but protobuf>=3.2.0 is required by set(['grpcio'])
I have protobuf3.2.0 in my site packages folder but somehow the install process always creates the 3.0.0 folder on which it then relies

We accidentally created a set of impossible to satisfy dependencies earlier this week. We're working on sorting it out.

This should be resolved.


Remove winston logger dependency

Closed via https://github.com/microsoft/vscode-python/pull/17919


Set specialisation as default

Describe the feature request
There should be an option to make a specific specialisation boot by default.
I've tried boot.loader.grub.extraEntriesBeforeNixOS option, but it ignores specialisations.
Expected behavior
Probably specialisation.<name>.makeDefault option?
Additional context
https://github.com/NixOS/nixpkgs/blob/13fad0f/nixos/modules/system/boot/loader/grub/install-grub.pl#L518
https://github.com/NixOS/nixpkgs/blob/13fad0f/nixos/modules/system/boot/loader/systemd-boot/systemd-boot-builder.py#L271

Declaring interest.


Add support for json_agg_strict (PostgreSQL only)

Add support for json_agg_strict (PostgreSQL only) - this function is just like json_agg, but skips null (see https://www.postgresql.org/docs/current/functions-aggregate.html)
A few notes:

I've duplicated all json_agg tests and changed them to use json_agg_strict, but I'm not sure if:

Should we test all cases for both json_agg and json_agg_strict?
If we want to fully test both, do you prefer duplicating the code, using a loop, or using a function?

json_agg might return null (for example, when using left join and there is nothing to join with), but the types ignore that.. I guess fixing it is a breaking change, so I did not include it in this PR

Thanks for this awesome package! :)

When using it with left join every field becomes nullable (I think that left join changes DB[table] to a "nullable version"), which is not true with json_agg_strict (which unlike json_agg will reply with [] for "empty join").
I'm not too sure if this will be easy to solve.. any help will be appreciated :)


Laravel 10 / Jetstream / Inertia support

$ composer require druc/laravel-langscanner
./composer.json has been updated
Running composer update druc/laravel-langscanner
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - druc/laravel-langscanner[0.0.0, ..., 0.3.0, 1.0.0] require illuminate/contracts ^8.0 -> found illuminate/contracts[v8.0.0, ..., v8.83.27] but these were not loaded, likely because it conflicts with another require.
    - druc/laravel-langscanner 1.1.0 requires illuminate/contracts ^8.0|^9.0 -> found illuminate/contracts[v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.4] but these were not loaded, likely because it conflicts with another require.
    - druc/laravel-langscanner[v2.0.0, ..., v2.0.1] require illuminate/contracts ^9.0 -> found illuminate/contracts[v9.0.0, ..., v9.52.4] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires druc/laravel-langscanner * -> satisfiable by druc/laravel-langscanner[0.0.0, 0.1.0, 0.2.0, 0.3.0, 1.0.0, 1.1.0, v2.0.0, v2.0.1].

You can also try re-running composer require with an explicit version constraint, e.g. "composer require druc/laravel-langscanner:*" to figure out if any version is installable, or "composer require druc/laravel-langscanner:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

Thanks in advance!

@druc  - created a PR for this https://github.com/druc/laravel-langscanner/pull/15


API Key exposed by OnchainKit provider

Describe the bug and the steps to reproduce it
Follow the OnchainKit Getting Started guide: https://onchainkit.xyz/getting-started
This necessitates exposing a Coinbase API key in a client component, meaning any users of the web app implementing OnchainKit can access the key.
GitGuardian reports this as a critical security vulnerability.

What's the expected behavior?
OnchainKit does not require an API key to be exposed to end users.
What version of the libraries are you using?
0.23.4

It also does not appear to be possible to revoke or rotate this API key.

Hello! We recommend you put the API key in an .env file and do something like this:
<OnchainKitProvider
          apiKey={NEXT_PUBLIC_CDP_API_KEY}
          chain={base}
          schemaId={SCHEMA_ID}
        >

Putting the API key in an .env file will not resolve the issue. Because this a client component, the key will still be exposed in client side code at runtime.

Hey @richardrauser, here a few points around API Key developer experience so far:

What you get from Coinbase Developer Portal is a Public API Key, in a very similar form other provider have those public key, those are meant to be used in frontend code.

We documented a bit more on what's a good practice on how to use this Public API Key with the .env file, which with any provider like Vercel gives you the ability to change the enviroment variable at any time without pushing new code.

The Coinbase Developer Portal is working on keep polishing the developer experience on how to use those Public API Keys, and you will see coming up in the future way to better control them.

Stay tuned for coming up improvements, and thank you for sharing your experience.

@Zizzamia thanks for the explanation. I always question the benefit of services that require public API keys of the nature you describe. Presumably these are used for things like access control, rate limiting, etc (but not for access to sensitive data or functionality), but if a bad actor can so easily rip off some other app's public key to circumvent a key revoke or rate limiting that their own key has become subject to, what's the point?
In the worst case, a competing app or business might take another app's key and intentionally induce a key revoke or rate limiting to disrupt their business.

I think, it's important for OnchainKit in the next few months give both options of running API in the frontend or decide to use your own backend proxy APIs.
I can keep this Issue open as we ship more things towards supporting both.


bug: 414 Request-URI Too Long

Hello.
After editing a field (for example 'description') with a lot of text 414 error appear.

414 Request-URI Too Long
The requested URL's length exceeds the capacity
limit for this server.

Plugin last commit is e74286667c3dc385a21816c27a557baaf519abc0
Plugin version | 0.6.1
Server | Apache/2.4.18 (Ubuntu)
Redmine | 3.2.3.stable
Ruby | 2.3.1-p112 (2016-04-26) [x86_64-linux-gnu]
Rails | 4.2.8
Database adapter | SQLite
User-Agent | Mozilla/5.0 (X11; Ubuntu; Linu…) Gecko/20100101 Firefox/58.0

Hello @ParisDakar
Thank you for your message. The last commit may resolve your problem. I edited the way I send the data and you won't get any 414 errors anymore.
Don't hesitate to send me a feedback here if you find any issue concerning this last commit.
If you find the plugin helpful, please take a minute to star it on Github and rate it on http://www.redmine.org/plugins/redmine_issue_dynamic_edit 👍 Thank you for your help

Hello @ParisDakar
Thank you for the help about your second issue.
I updated the JS code but I wasn't able to reproduce the problem (i tried with different browser without success, which one do you use ? Chrome, Firefox Quantum & Safari worked well). Do you use any specific Redmine plugin for your date inputs ?
Could you please upgrade to the last version and tell me if the last commit resolve your issue ?

I use Firefox 58.0.2 on Ubuntu 16.04.3 LTS - as the client.
And Ubuntu 16.10 as the server.
There are plugins that I install:

redhopper/
redmine_hamster/
redmine_issue_detailed_tabs_time/
redmine_issue_dynamic_edit/
redmine_user_specific_theme/
scrum2b/

OK, this plugin collection is bad for test purposes. I remove redhopper and check your plugin again and bingo! No more "Loading..." after page is load.
@Ilogeek everything work fine!

I'd like to close issue as completed well.

Hello @ParisDakar thank you for your analysis.
I'll check the redhopper plugin if it may create conflict with my plugin.
I'm happy for you if everything works great !
If you find the plugin helpful, please take a minute to star it on Github and rate it on http://www.redmine.org/plugins/redmine_issue_dynamic_edit 👍

...star it on Github and rate it
Done!


chore(master): release 0.16.0-alpha

:robot: I have created a release beep boop
0.16.0-alpha (2024-01-17)
Features

fix (71c29f7)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/mafqla/yalis-blog/releases/tag/v0.16.0-alpha :sunflower:


Fail snapshot diffs on test, update snapshots from command line

Ref: https://github.com/commodityvectors/scalatest-snapshot-matchers/issues/7

Fail on test, makes it CI compatible if someone pushes without testing
Explicitly update snapshots on command line updateSnapshots=true sbt test
No hanging in IntelliJ when there is a diff

This is similar behaviour to jest: https://jestjs.io/docs/en/snapshot-testing
With command: sbt test
[info] Done compiling.
[info] HelloWorldSpec:
[info] - should match HelloWorld *** FAILED ***
[info]   Text Did not match:
[info]   --- Original Snapshot
[info]   +++ New Snapshot
[info]   @@ -1,1 +1,1 @@
[info]   -"Hello, World!"
[info]   +"Hello, World!!"
[info]
[info]   End Diff; (HelloWorldSpec.scala:12)
[info] - should return say Hello, World!
[info] Run completed in 326 milliseconds.
[info] Total number of tests run: 2
[info] Suites: completed 1, aborted 0
[info] Tests: succeeded 1, failed 1, canceled 0, ignored 0, pending 0
[info] *** 1 TEST FAILED ***

With command: updateSnapshots=true sbt test
 ### Updating Snapshots: should match HelloWorld ###
[info] HelloWorldSpec:
[info] - should match HelloWorld
[info] - should return say Hello, World!
[info] Run completed in 315 milliseconds.
[info] Total number of tests run: 2
[info] Suites: completed 1, aborted 0
[info] Tests: succeeded 2, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.
[success] Total time: 2 s, completed 13-Sep-2018 21:37:38

Hi @sterowney ! Thanks for the pull request. I'll review it today.

On another point, are you using IDEA's test runner? If so, there is a way to connect the prompt inputs with it: https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000556544-Why-can-t-I-input-anything-from-console-when-i-run-unit-test-with-JUNIT (I never tested never tested)

To randomly jump in on this pull request, while this is a manual step, it seems like it would be pretty beneficial to be able to run the tests in bulk with sbt test and update them at the same time. Personally I'd rather not get prompted at every juncture for something like adding a new parameter, especially with there possibly being a larger number of tests.
Additionally, while not harmful, when tests are run in some ci system prompting is pretty unnecessary. As it stands now the PREVENT_SNAPSHOT=t option to not generate snapshots does not explicitly detail what is failing when passing that option. When the snapshot doesn't match the current instance, the output remains Snapshot [myspec-should-mutate-state-properly-1] was not generated due to Environment flag. (MyTests.scala:20) while the test could be legitimately failing due to differing snapshots.
It seems like this contributor may not but very active, but I'd be willing to take this over if we could work out the best course of action here.

One suggestion I would have is only to suppress the prompt when this value is set, not remove it completely, which allows for both workflows.

I will close this as #10 will supercede


Auto declare Angular 2.0 components when moving components

When moving angular components from one folder to the other, the wrapper module does not change the declarations array to use the component.
Also, as known from other issues, moving a few folders/files in one shot will cause imports problems, so I need to use this extension to move the files without breaking the files.
Like in this video:
https://user-images.githubusercontent.com/77183871/141810610-06b4b4cf-8bd2-42ce-a514-784ddfea479d.mov

As for the angular declarations, video here:
https://user-images.githubusercontent.com/77183871/141809765-64f5a1b5-e579-4b01-b172-61678cd70a59.mov

Please file this feature request against the angular extension

How about the imports fixes problem as described above?


Testnet 43: Leda

Testnet Release
Testnet name: Leda
Release date: 2023-02-06
Testnet release manager: @conorsch
Testnet Release Manager Checklist
Preceding Friday (sprint planning day):

[x] Create GitHub project column, work with team to populate the milestone with tickets targeted for the release.

Tuesday (or after release of previous testnet):

[x] Construct the genesis data for the release: https://github.com/penumbra-zone/penumbra/pull/1921

[x] Create new testnet directory with initial genesis allocations for this testnet by running cd testnets && ./new-testnet.sh

This genesis data will be used for testnet-preview with a randomized version of the future testnet's chain ID.

Thursday:

[x] Check in with team again in a release meeting and update the GitHub milestone to ensure it represents what will make it into the testnet.
[x] Draft an announcement for peer review to ensure major changes included are comprehensive.

Following Monday (release day):

[x] Verify that testnet-preview.penumbra.zone is operational; it is redeployed on every push to main, and is an exact preview of what is about to be deployed.
[x] Create new git tag e.g. 006-orthosie on main (tags created on any other branches will not transfer when merged in) and push to shared remote: git tag -a <tag_name> - must be annotated tag, i.e. git tag -a for Vergen build. This will create a Waiting GitHub Action for deployment.
[x] You must manually review the Waiting deployment in the GitHub Action UI before the deployment will begin. Monitor the GitHub action to ensure it completes after it is approved.
[x] Update the User Guide to mention the newly created git tag.
[ ] Delegate to the Penumbra Labs CI validator
[x] Make GitHub release object and include the announcement
[x] Make the announcement to Discord! 🎉🎉🎉

Updated Galileo (https://github.com/penumbra-zone/galileo/issues/25) and faucet is flowing. :sunglasses:


Welcome to The-Complete-FAANG-Preparation Discussions!

Discussed in https://github.com/AkashSingh3031/The-Complete-FAANG-Preparation/discussions/13

Originally posted by AkashSingh3031 June 16, 2021

👋 Welcome!
We’re using Discussions as a place to connect with other members of our community. We hope that you:

Ask questions you’re wondering about.
Share ideas.
Engage with other community members.
Welcome others and are open-minded. Remember that this is a community we
build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

If you force to open the file you will be liable for any damages

You already open it ! But not the full node core! The project is intentionally hide to the public.

You already open it ! But not the full node core! The project is intentionally hide to the public.

Can you explain to me in detail what you want to say?

Iam the developer of the project I already block your account

Your not allowed to share the code


Suggestion: Add travis status image to Readme.md

I would suggest to add the embedding travis status image to Readme.md so that visitors would get this information.
I just cloned this repository to begin my code review journey as I believe there is much for me to learn from this popular project, however I just find one of the unittests failed :(
It's not a big deal but I would submit this suggestion with low priority.

Thanks for your consideration. I just synced latest code from jsoup and run all the tests, there is one and only one failed.

org.junit.ComparisonFailure:
Expected :43963
Actual   :43972

at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at org.jsoup.integration.ConnectTest.postFiles(ConnectTest.java:304)

So that must mean in your checkout, the newlines in the test HTML file where converted from LF to CRLF, and so the file posted does not match its expected file size. I thought I had fixed .gitattributes (in 47a7f5ab2a22a2ce526f96e0cf9f2c46511c56d9) to correct for that, but I guess not. I'll have another shot at it.


WIP - Nuxt 3

Originally, this PR description contained information on how to deploy Nuxt 3 to staging. This was incorporated in the PR. To view them, look at the history of this comment.
Note: this is a draft, I (@obulat) will update it tomorrow
Information described here:

the most important items to review in this PR
the large changes in patterns and structures
smallish changes that were required to migrate to Nuxt 3
enhancements that were not necessary for Nuxt 3 migration, but were useful and easy to make here

The most important items to review

/server directory contains the server routes (healthcheck and robots), as well as the server-side Sentry and server-side logger that uses Consola.
/data/api-service - the API client (data services) code.
app.vue - the single entry point to the frontend app.
nuxt.config.ts - point where the app, plugins and modules are set up.
Pages: search.vue, image/[id]/index.vue and audio/[id]/index.vue
Middleware: search, collection and single-result
Dockerfile

Infra-related questions:

We need to provide the env variables to the process when starting the app that was built for production. How do we do that?

Changed code patterns and structures
API service
All the various services were replaced with a single api-service that has only the methods that we use. The extra methods that were not used by the frontend (e.g., put, update, delete) were removed.
The API service uses useRuntimeConfig for the API URL, and uses the API token from useNuxtApp.
Fetching data in pages
The useFetch from @nuxtjs/composition-api was replaced with Nuxt 3 function  useAsyncData in the search, collection and single-result pages use the for fetching the data.
All of the server-side fetching for search, collection and single result pages is done in the middleware.
I tried moving the fetching to the useAsyncData to unify and simplify it. However, this causes client-server mismatch because the fetching is done in the sub-page, after the surrounding components such as header and footer have already been rendered. This means that the result count is always set to 0 in the header.
When hydrating, the client expects it to be the real number because the store has the updated data, and the header is being rendered with that. We could wrap the changing items with <ClientOnly> to prevent the mismatch, but it's much easier to fetch the data in the middleware, before the app starts rendering, and have the correct data rendered on the server everywhere.
Single entry point, app.vue
Nuxt 3 introduces a new single entry point, app.vue. This is used to add the functionality that should work whenever a user gets a server-rendered page, wether it's a homepage, a search page, a single result page or a static page.
Previously, we used the global middleware for the functions that do not require the app to be mounted and do not require a window access. For the functions that need the app to be mounted (such as updating the layout values with the cookies or syncing values with local storage), we added them to every layout file.
Layout files became much simpler because most functionality was moved to app.vue
Note: the only page that does not use the app.vue is error.vue. We have to duplicate the i18n properties and the layout update from cookies there.
Modals
Vue 3 and Nuxt 3 natively support teleports, so the modals were updated to use the native support. We no longer need a modal target because Nuxt automatically creates a #teleports element.
Smaller changes required for Nuxt 3
Plausible types don't allow null
The new Plausible plugin uses plausible-tracker JS library, and the event properties can only be string, number or boolean there. So, all the null values in analytics events were replaced with the string "null" in this PR.
import.meta
process.* was replaced with import.meta Link to Nuxt docs and JS docs
i18n keys
i18n now checks for the correctness of the keys. So, if there are strings with non-ASCII keys (e.g., "text of the {translated keys containing non-ascii letters}"), the build fails. This is why I added a quick fix for this. It should be improved later (and the translations need to be updated in GlotPress)
script setup for pages
All pages were converted to script setup because it's impossible to set the layout and the middleware in a component that uses defineComponent imported from vue.
runtimeConfig
env properties were moved to the public runtimeConfig.
SVG sprite
SVG sprite module was vendored in because it did not work with our folder structure, where we have a /src top folder.
ua-parse
ua-parse was removed because the library it uses does not have ESM, and we don't use UA anywhere.
splitting attrs to classes and other attrs
In Vue 2, the class and style were not passed to the child component as part of $attrs, but instead were added to the outermost element of the child component. This broke the styles of the components that used inheritAttrs: false (VSearchBar, VSelectField, VItem).
Enhancements (not-necessary but useful)
Media item preprocessing
We already pre-process the API responses to add necessary properties (frontendMediaType) or to fix encoding/decoding problems.
I added the extraction of the filetype from the main media URL. This way, we don't have to replace the filetype on the client-side after the image/audio have been loaded. This removes the flickering and also the occasional client-server mismatch.
UUID check
Added a validateUUID check to the single result page to directly show an error page if the path id parameter is not a valid UUID instead of attempting to fetch it.
DevEx improvement
The server API requests are logged in the console to simplify debugging.
Replacing ad-hoc implementations with Vueuse
use-window-scroll composable was replaced by the composable from vueuse
Homepage images issue
Fixed the issue when the image on a single result page was not updated if you selected one from the homepage, went back and selected another one.
v-for keys
In v-for elements I replaced indexes with a better key option.
Disabled or not working items

Storybook (waiting for module update)
Prometheus
ua-parse
Storybook tests

We need to provide the env variables to the process when starting the app that was built for production. How do we do that?

@obulat can you clarify what you mean? Do you mean that we need to define production variables at build time? Or that we need to add new environment variables to the production execution environment?

We could wrap the changing items with  to prevent the mismatch, but it's much easier to fetch the data in the middleware, before the app starts rendering, and have the correct data rendered on the server everywhere

That sounds great to me, I agree it's a better architecture. There are many different parts of our app that rely on the same data, and for the search pages it makes sense for that to go top-down, from the abstract "start of the request" to the real rendering of the page.

Vue 3 and Nuxt 3 natively support teleports, so the modals were updated to use the native support. We no longer need a modal target because Nuxt automatically creates a #teleports element.

Awesome!

@obulat I've had the opportunity to review this for several hours and I've made some suggestions. I think the homepage animation and robots.txt concerns are worth blocking over. I've also provided fixes for both :smile:
This is phenomenal work, and once my comments have been addressed we should push to our nuxt preview domain once more. Then, on Monday or a bit later we can conduct a lengthy test wherein a large percentage or all traffic is routed to the Nuxt 3 code. That would give us much assurance about merging and finally deploying this PR.
I am confident the work here will give us a stable foundation for iterating on the frontend, cleaning up legacy code patterns, and migrating to Nuxt 4. Amazing work!


Enable -race flag in unit tests

Motivation
Closes #2226
There're some data races left after merging https://github.com/spacemeshos/go-spacemesh/pull/2608. I cannot reproduce them locally but in CI only. Therefore, I'm creating this PR to be able to check what's left to be fixed.
Changes

Enable -race flag in unit tests

Test Plan

Unit tests

DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

On hold until https://github.com/spacemeshos/go-spacemesh/issues/3066 and https://github.com/spacemeshos/go-spacemesh/issues/3067 are closed.

bors try

do we need to merge any other changes?

@dshulyak we need to fix https://github.com/spacemeshos/go-spacemesh/issues/3100, to check if https://github.com/spacemeshos/go-spacemesh/issues/3066 is reproducible and then to check if any other data races appear

@dshulyak https://github.com/spacemeshos/go-spacemesh/pull/3095 should fix a mesh data race and I think it's still not merged here

bors try

I hate being a buzz-kill, but there are still some races left 🙁. Check the Windows unittests. At least some of them fail because of data races. The macOS tests seem to fail because of timing issues at least.
Also libgpu-setup.dynlib seems to have been built on a newer version of macOS than we are currently using in our go-spacemesh CI. I should double check this, so that we can support most macOS versions.

 Check the Windows unittests. At least some of them fail because of data races. The macOS tests seem to fail because of timing issues at least.
Also libgpu-setup.dynlib seems to have been built on a newer version of macOS than we are currently using in our go-spacemesh CI. I should double check our CI for go-spacemesh and gpu-post, so that we can support at all macOS versions since at least 11.0 (Big Sur).

I'm aware there are still data races in the code. The goal of this PR is to only fix failing tests and to enable -race so that no new data races are merged.
Regarding windows unit tests - I'm surprised as I was pretty sure I removed the allow-failure: true for windows some time ago 🤔 .

bors merge


Fix leaking zip file when appending boxes to an executable

Remove the zip file after usage.

Looks like the CI build wasn't even started. Does anyone have the rights/powers to start it?

I tried to pull your change in on #87 but I had some other wercker build issue on that.  :eyes:

Strange about the failing build, but this seems to work fine.

Actually, wouldn't it be better to put a defer tmpZipFile.Close() before that statement so we're sure our program has released the file pointer?

Good point. I've seen this happen on Linux, where unlinking an open file works fine. But on Windows that won't work indeed. I'll add that to be sure.

 I've opened a new PR.


21: Reorders sections on state page

Moves OPOs servicing [state] above News & Notes
Also deletes some commented out code (for future feature with bar charts) because I love to delete commented out code! It exists in history if we want to implement later

 Reorder sections on state page


Multiple Clients cannot connect to same CAN Agent

The use of CAN bus as transport suggests that there can be more than two participants on the network, this ought to be possible per XRCE-DDS spec, however trying to add a second client results in failure where the initial client gets deleted when a session was already initialized.
The result is that name of second client is shown at ros2 host but none of the topics list up.

Please share the Micro XRCE-DDS Agent as text and using the -v6 flag. Indicate when are you connecting the first and the second CAN XRCE Client

Here we go...
CanAgent-Client-Drop.txt
Thanks

it seems it's not an agent issue. I got it working now, the issue was that on my test code can frame ID was always the same number, thus causing a conflict since the ID sets the endpoint at session manager CanEndPoint(can_id) which sets a map at https://github.com/eProsima/Micro-XRCE-DDS-Agent/blob/40954c2379dfcb2bfa9f6ba22146c57c6742b5b7/include/uxr/agent/transport/SessionManager.hpp#L62
So using individual can ID separated the sessions and now agents handles both clients simultaneously.

Nice to hear that, should I close the issue as solved?

I think so, there is still an issue with sequencing of the initialization, if both clients start simultaneously, only one starts correctly, the other has to reset to get initialized. But this might be not related to this.

Ok, please open a new issue if you find that this init error is related to XRCE.
Thanks!


[IMPROVEMENT] search api full-text-search

What would you like to share?
Currently, pages/api/search/[[...slug]].js we have been filter users by JavaScript, that's not efficient for performance. Instead it would be better to perform that logic by MongoDB full-text-search.
Additional information
No response

This would be a great improvement 👍

Can I work on it

Can I work on it

@ArnabChatterjee20k I have assigned this to you

One question I have, full text search wont search for substrings in the slug. So we have to enter the full name to get the results.
So will it be be good to implement this?

Can you five an example of what you mean? But if I think I understand, partial search keyword match should return results

Full text search example
My name - ArnabChatterjee20k
Now if I search for Arnab or arnab , it will not return results
I have to search for ArnabChatterjee20k to get the result
Partial searching or pattern searching will give the result by getting the pattern
But the issue is asking for full text search.
So I asked this question

Can you five an example of what you mean? But if I think I understand, partial search keyword match should return results

Yes partial or pattern searching is the ideal one here

Yes fulltext search is designed for partial matches, similar to google search, here from the mongo docs...

Full-text search refers to searching some text inside extensive text data stored electronically and returning results that contain some or all of the words from the query. In contrast, traditional search would return exact matches.

https://www.mongodb.com/basics/full-text-search

I am currently facing this issue and not getting any solution. I am trying it from the last 2days.
Here is solution and the approch and exactly what issue is coming
https://stackoverflow.com/questions/76773218/constructing-a-mongodb-query-to-emulate-javascript-filtering-logic-filterevery?noredirect=1#comment135348552_76773218

I am currently facing this issue and not getting any solution. I am trying it from the last 2days.
Here is solution and the approch and exactly what issue is coming
https://stackoverflow.com/questions/76773218/constructing-a-mongodb-query-to-emulate-javascript-filtering-logic-filterevery?noredirect=1#comment135348552_76773218

I think trying to replicate javascript is not the correct approach, mongo has full text search which we should move to, here is an official example from their docs with features like scoring, fuzzy search etc https://www.mongodb.com/developer/products/atlas/build-movie-search-application/

Hi everyone, is this issue still being worked on? or is it abandonded? Could I still work this? Thanks!

Hi everyone, is this issue still being worked on? or is it abandonded? Could I still work this? Thanks!

@ArnabChatterjee20k ?

Hi everyone, is this issue still being worked on? or is it abandonded? Could I still work this? Thanks!

@ArnabChatterjee20k ?

No I am going to work on it now only. I told in the discord. Actually I was suffering from some health issues. And my sister met an accident. So I was inactive. I am going to work on it right now

I am actually confused about whether this issue is closed or not. I made a pr some hours ago. Actually I am working on it.

@ArnabChatterjee20k as there has been no activity for some time I have unassigned you from this issue, but we look forward to you contributing when you can on another issue.

Hi there, can this issue be assigned to me so I can start working on it?

Sorry @SaraJaoude this is partly my fault, we were undecided about having 2 types of searches because locally we cannot have fulltext search like we do on Monog Atlas.
Thank you @ArnabChatterjee20k for your efforts on this issue and pull request.
But I will close this issue for now until we can think of a better way to have our local dev environment the same as production for search


Transaction Pool - State Consistency

I didn't want to make too many modifications to the state while Luke was reviewing everything (though there are a handful), but the transaction pool has some perfectly overlapping code with the state that I've merely duplicated for the time being (it deals with verifying transactions).
Some of the verification code in the state needs to be broken down a bit more and exported. Overall, it should be a pretty simple change. Then I can remove the duplicated code that appears in the transaction pool.

also trips

I looked at it, and it doesn't seem to bad. I don't see an easy way to fix it. I imagine I'll get to it when me move the state to being its own module.


Magnet Slot 57 fails for certain geometry

Dear all,
I tried using Slot 57 for a machine and it doesn't work with femm. The problem is the position of the "material properties point" of the "Rotor Iron". In my case it ends up inside the shaft.

I would be willing to fix this myself and already found the class HoleM57.py but honestly I was not able to find the definition of the geometry there. I am aware I should watch the webinar 3 and do the corresponding tutorials first before attempting to change slot geometries. So once I did this and nobody was faster I will try to implement a better position. My suggestion would be 1µm outside of one of the magnets so for example from "HoleMagnet_Rotor_Parallel_N_R0_T1_S0" just H2*0.5+1µm in direction of the magnetization:

Hello,
Thank you for noticing that :)
The geometry modeller of pyleecan create a list of surfaces corresponding to the different objects of the machine. Then the "rotor iron" is not Hole related but lamination related. So the definition of this point is made here:
https://github.com/Eomys/pyleecan/blob/master/pyleecan/Methods/Machine/LamHole/build_geometry.py line 54
The issue seems to be that the "yoke mid radius" is wrong and the definition is here:
https://github.com/Eomys/pyleecan/blob/master/pyleecan/Methods/Machine/LamHole/comp_radius_mid_yoke.py
Can you check that you set rotor.is_internal = True ? Otherwise, the error can be in Hole.comp_radius: the point of this method is to get the minimum and maximum radius of the points of the Hole. To define the position of the reference point we need to take into account that we can have several holes (and also vents that are not taken into account but they should also have the comp_radius method). The point of comp_radius_mid_yoke is to find a radius where we know there are no holes.
Looking forward for your PR, don't hesitate if you need any further assistance ;)
(by the way it make me realized that I forgot to correct the reference point in my latest PR, thanks :) )
Best regards,
Pierre

I have fixed a typo in #435 that should correct it (to check)

Hello,
In fact the error was in Hole57.comp_radius. It will be corrected in #431

Thak you for spoting this error :)
Best regards,
Pierre


Python 3 compatibility

Hi, Gooey is a great idea, I was wondering is it possible to add Python 3 compatibility for this project?

Unfortunatly, that is probably not going to happen before wxPython gets Python3 support. There is currently a project called Phoenix that attempt to do just that.
I tried to get Gooey working with the svn-builds of Phoenix and it kind of works:

I had to remove wx.animate and do some python3-porting. As soon as Phoenix is stable, making a py3 compatible version should not be too difficult.

Another option, which is what Gooey is heading towards (so that it works with more than just Python), would be to run the actual GUI side of things as an isolated executable -- something packaged with, say, PyInstaller. Then python 3 compatibility with Wx would be moot, as client code would never interact with that side. The only Python code that clients would interact with would be (what I call), the "bindings," which is what generates the JSON that Gooey needs to run. And those would be crazy easy to port.
Whenever Phoenix is stable, Gooey will migrate. In the mean time, it'll be (eventually) optionally served as an executable so people can still use whatever python version they please.

@chriskiehl That sounds awesome!

In the meantime, Gooey is written in a Python3 incompatible manner (the biggest example is the print statement as opposed to the print() fuction).  Gooey could be modified to use python-version agnostic code so that the only thing preventing it from running on Python3 is the libraries, not the syntax.

There is basically only one place where we cannot have the same code for 2
and 3, and thats for opening a JSON file for parsing. In every other place
I've managed to do smaller changes to make the code valid in both py 2 and
3. But what is the point of doing that change when we may not even be able
to port it to python 3? I can commit the changes if Chris wants them.
On Sat, Feb 21, 2015 at 8:56 PM, Seth Morton<EMAIL_ADDRESS>wrote:

In the meantime, Gooey is written in a Python3 incompatible manner (the
biggest example is the print statement as opposed to the print()
fuction). Gooey could be modified to use python-version agnostic code so
that the only thing preventing it from running on Python3 is the libraries,
not the syntax.
—
Reply to this email directly or view it on GitHub
https://github.com/chriskiehl/Gooey/issues/65#issuecomment-75389526.

i just wonder if there is any progress on this issue?
thanks!

@shelper Unfortunately not. : (
Noticing that the last time I commented on this issue was February (oy..), I figure I'll at least explain the slow output on Gooey: In short, I (briefly!) thought I liked money more than I liked free time. So, I accepted some side contract work. This has left little time for leisure programming on Gooey.
There's still a giant list of things to be done, but alas! Currently a bit bogged down...

I guess at least the changes for Py3 compatibility that @piksel proposed to PR would be a good idea in the meantime? This will be needed anyway, and will maybe even help with any subsequent changes like refactoring the GUI side, or starting testing with Phoenix snapshots (which seems to be available nowadays).

I plan to sometime soon take a shot at converting the codebase to py2+py3 using future, if that would be a welcome change? I think it's necessary at some point in the future, anyway, and hopefully it eases the transition away from a wxwidgets/Phoenix-only solution.

RFC PR for py2/py3 compatibility is here: #131

+1 for Python 3

Since wxPython for Python 3.x is (still!) nowhere in sight...
What about using Tkinter as the GUI? Not as good as wxPython, but:

Included with all versions of Python, removing an external dependency
Supports Python 2.x and 3.x

There seems to be some movement lately, with a pledged bounty for the developer upon release of Phoenix, so I'm, hopeful.
However, using Tkinter as the (default) GUI, maybe with options for other packages, sounds good to me. Don't know what effort that would entail, though, that's a question for @chriskiehl.
I'm prepared to re-do the work of #131 (preparation for py3 compatibility) to move towards that goal, should this go forward and be welcomed/merged.

I really wish projects that only supported Python2 would say so up front. Like, instead of "Turns a Python Script into.." it would say "Turns a Python 2 Script into..". :/

Just here to formally express interest in a Python 3 compatible version :-)

Same here. All the code that I have already done is in python 3, so I wish I could use this amazing extension!

+1 for python3.
Great tool! Just fiddled around some scripts for friends, but had many unicode issues again from py2. Don't want to suffer that anymore. I would be glad to help to port Gooey to py3.

Made some porting jobs, trying to pass all the tests.
  This is also good for making GUI
        method calls from non-GUI threads.  Any extra positional or
        keyword args are passed on to the callable when it is called.

        :param PyObject callableObj: the callable object
        :param args: arguments to be passed to the callable object
        :param kw: keywords to be passed to the callable object

        .. seealso::
            :class:`CallLater`
        """
        assert callable(callableObj), "callableObj is not callable"
        app = wx.GetApp()
>       assert app is not None, 'No wx.App created yet'
E       AssertionError: No wx.App created yet

c:\python34\lib\site-packages\wx\core.py:2903: AssertionError

Gui window showed fine, but when you click on the Start button on footer, console logs error:
C:\dev\gooey-future\Gooey (master)
> example.py
C:\dev\gooey-future\Gooey\gooey\gui\imageutil.py:24: wxPyDeprecationWarning: Call to deprecated item ImageFromBitmap. Use bitmap.ConvertToImage instead.
  image = wx.ImageFromBitmap(_bitmap)
C:\dev\gooey-future\Gooey\gooey\gui\imageutil.py:30: wxPyDeprecationWarning: Call to deprecated item BitmapFromImage. Use :class:`Bitmap` instead
  return wx.StaticBitmap(parent, -1, wx.BitmapFromImage(image))
Traceback (most recent call last):
  File "C:\dev\gooey-future\Gooey\gooey\gui\windows\footer.py", line 104, in dispatch_click
    pub.send_message(str(event.GetId()))
  File "C:\dev\gooey-future\Gooey\gooey\gui\pubsub.py", line 23, in send_message
    event_handler(**kwargs)
  File "C:\dev\gooey-future\Gooey\gooey\gui\presenter.py", line 111, in on_start
    self.client_runner.run(command)
  File "C:\dev\gooey-future\Gooey\gooey\gui\processor.py", line 45, in run
    stderr=subprocess.STDOUT, shell=True, env=env)
  File "C:\Python34\lib\subprocess.py", line 858, in __init__
    restore_signals, start_new_session)
  File "C:\Python34\lib\subprocess.py", line 1085, in _execute_child
    args = list2cmdline(args)
  File "C:\Python34\lib\subprocess.py", line 663, in list2cmdline
    needquote = (" " in arg) or ("\t" in arg) or not arg
TypeError: argument of type 'int' is not iterable

I have done from builtins import str , but it didn't work.

@bosbyj have you seen #131, especially the PR description and the commit messages explaining what I did to get all test running (this was before Phoenix was available, though).
Btw, what version of W´xPython Phoenix are you running?

@bilderbuchi Hi! Didn't read that page but I pretty much followed the same way to get the GUI showed up under py3. I am using a quite old version:
VERSION
    3.0.3.dev1830+0b5f910

@chriskiehl now that wxpython phoenix seems to be available, would you welcome contributions towards integrating wxpython and python 3 compatibility? I am asking because in TODO.md in the 2.0 branch I see "Deprecate WxPython" - does that mean you will remove it (soon), in which case it doesn't make sense to invest the effort of porting?

@bilderbuchi Seems that the owner is pretty busy nowadays. I will be available if this project starts to move to 2.0 with pyqt. It is just a matter of changing the frontend stuff.

Busy indeed :( However I did spend last weekend chipping away at it. I've got a local branch with all of the Gooey widgets (choosers, dropdowns, etc..) re-implemented in PyQt5. The old wx code is the hottest of garbage, so I've been rebuilding from scratch versus just swapping out wx components for Qt ones and duct taping it together.
I'll push what I have in a few days of so!

Great news! :+1:

...By "push what I have in a few days", I apparently meant "push what I have in several days to a few weeks". I got pulled away on other things for most of the week/weekend. But I did manage to get Gooey running in a basic form on Python3 with Pyqt5 tonight 😄
"I'll push what I have over the next few weeks...."
Looks more or less the same, but... Pyqt!

Looks more or less the same, but... Pyqt!

Well that's much of the way there already, right? 😁 That's the frustrating thing about refactoring, in the end you don't see a difference...

Great progress! Congrats!!!!

Guys check this out ->
https://pypi.python.org/pypi/wxPython/4.0.0a1
Just discovered that wxpython now has py3k support.

Sorry to break silence, any news in July?

@bosbyj https://www.youtube.com/watch?v=0d6yBHDvKUw 😁
You can track commit progress on this branch: https://github.com/chriskiehl/Gooey/commits/2.0. Currently runs via beep_boop.py in the new_hotness directory if ya wanted to play around with it. Still a bit rough at the moment (runs from a hard-coded json file), but the main pieces have been completed.
Remaining:

[ ] final post-run screen
[ ] Other stuff (progress bars, translations, polish, etc..)
[ ] done

:grin: lmao man, and thanks for the feedback! saludos cariñosos

@everyone 2.0 branch is officially in a previewable/runnable state. It's missing the progress bar and the radio widget, but most everything else is there. If you're running Python >= 3.5, you should be able to just pip install it and be on your way. All deps should auto resolve.
pip install -U<EMAIL_ADDRESS>Note! if you get a failure and a super weird exit code when you try to run anything using the Gooey decorator, it's most likely PyQt silently and violently barfing. It seems to get corrupted when its installed as part of Gooey's setup.py. Haven't figure that piece out yet. However, If you just manually re-install it with the -U flag it seems to fix everything. pip install -U PyQt5
Comments, hate, bug reports, or requests from anyone willing to give it a spin would be super awesome! 😁

Awesome! Those commits tho :D

@piksel lol! Don't judge me! I follow the spam commits and rebase later methodology

@chriskiehl You depend on v5.7 of PyQt5 which seems broken. My PyQt5 dependent code worked before installing gooey2 and stopped working until I upgraded it to 5.9 (latest). Do you want pull requests?
Also on another note, PyQt5 is GPL but Gooey is MIT, is that going to be a problem? I'm not sure about how GPL "linking clause" works with PIP and python...

Using pyside bindings instead could work around the license issue, it's MIT or LGPL if I remember correctly.

@piksel @bilderbuchi
😩 I finally worked up the energy to explore this topic. It's pretty demoralizing, as there doesn't seem to be a clear path forward.
Library Options for keeping MIT License:
Pyside doesn't look viable at the moment. It's current stable build doesn't have python 3 support, and its next version, Pyside2, is in such a state that it still needs to be build from source, which would make Gooey super hard to actually use. Further, the exact knowledge of how to actually build the project on all the major platforms seems lacking, to say the least. So, that's yet another hurdle for people who want to use Gooey. GPL aside, one of the things I really dig about PyQt is that it's published as a wheel. So, Gooey can actually be pip installed without any separate out-of-band steps required (which is awesome).
WxPhoenix To stick with the current license, I'm pretty much still stuck waiting for WxPhoenix, which has the same problem as Pyside2: building from source. It also means abandoning all of the 2.0 work which, well, kinda kills my motivation.
Alternative Licensing
1. Gooey moves to GPL / dual license
Downstream effects:

all projects that use Gooey now have the same licensing woes.
packaging a gooey project now requires a commercial PyQt license

If I went this route, based on this stackexchange question, making the move will involve getting an OK from all 41 Gooey contributors. If one of them doesn't respond, or if one disagrees, it can't be re-licensed.
Although, from reading the contributions section on github all contributions are made under the same license as the projects. So, maybe that means the license can be changed without tracking down permission from each person..?
Adding to the complexity, it's actually need to be approval for two different licenses. A dual license would be needed so that people who are willing to pay for a copy of Qt can also use a Gooey license that allows them to package things free from GPL restrictions.
I buy a Qt license, Gooey's core internals become closed source, and only binaries and bindings are distributed
This is what the PyQt folks suggested in an email. A commercial license allows you to distribute binaries. All Qt code would be moved to a separate project and, somehow, probably through magic, the MIT licensed source along with pre-built binaries are delivered via pip.
3. something else
Plz halp.

@chriskiehl awesome that you've got some momentum!
Regarding relicensing: ianal, but I'm pretty sure you still have to get permissions from every contributor. They licensed their contribution under the license of the repo at the time of the contribution, so if some of their code is still in the repo, of course you have to ask if you want to change the license for their contribution.
Licensing option 3: one suggestion would be to merge the wxpython stuff and achieve py3 compatibility. Then, considering your limited time available for this project, you could invest any spare energy you have (after bug fixes and or reviews, I guess) into slowly abstracting away and generalizing the GUI toolkit interface, with the current/planned interface of pyside2. This is gonna take quite some time, so hopefully by the time that is finished, pyside2 will be polished enough that you can start using it. Does that sound reasonable? :-)

@chriskiehl Yeah, dealing with GPL can be tough. I hate it whenever I realized a library I've used isn't LGPL as I thought but rather GPL and impossible to license (reasonably).
Using wxpython4 seems to be the least painful way to go. Maybe the current 2.0 branch could be kept for a future pyside fork?


Enabled strict-inference and enabled stricter type checks.

Enabled strict inference to identify type issues during static analysis (compile-time) rather than at runtime
Enabled stricter type checks that highlight dynamic to identify opportunities to apply stronger type checking
Strictness does not apply to example code; it applies pedantic rules, but otherwise consistent with typical usage
Added missing parameter types to FormBuilderLocalizations methods
Added missing type declarations to a few parameterized type declarations
Added missing return types for some Function variables
Revised value type of FormBuilderTouchSpin to match underlying TouchSpin

Codecov Report

Merging #549 (352610b) into version_4 (0015626) will decrease coverage by 0.10%.
The diff coverage is 59.45%.

@@              Coverage Diff              @@
##           version_4     #549      +/-   ##
=============================================
- Coverage      30.91%   30.81%   -0.11%
=============================================
  Files             37       37
  Lines           1504     1509       +5
=============================================
  Hits             465      465
- Misses          1039     1044       +5

Impacted Files
Coverage Δ

lib/src/fields/form_builder_checkbox.dart
100.00% <ø> (ø)

lib/src/fields/form_builder_checkbox_group.dart
92.30% <ø> (ø)

lib/src/fields/form_builder_chips_input.dart
0.00% <ø> (ø)

lib/src/fields/form_builder_choice_chips.dart
100.00% <ø> (ø)

lib/src/fields/form_builder_color_picker.dart
1.25% <ø> (ø)

lib/src/fields/form_builder_date_range_picker.dart
0.00% <ø> (ø)

lib/src/fields/form_builder_date_time_picker.dart
1.60% <ø> (ø)

lib/src/fields/form_builder_file_picker.dart
0.00% <ø> (ø)

lib/src/fields/form_builder_filter_chips.dart
0.00% <ø> (ø)

lib/src/fields/form_builder_image_picker.dart
0.00% <0.00%> (ø)

... and 19 more

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 0015626...352610b. Read the comment docs.

See https://github.com/dart-lang/linter/issues/2339


math-classes : switch to the external Bignums library

In prevision for Coq 8.7, where the bignums library is going to be an external package, you might want to push the following commit in a v8.7 branch of math-classes. See PR #498
The external bignum package is already available this way (an opam package is underway) :
 git clone https://github.com/coq/bignums.git && cd bignums && make && make install

The above command is for the trunk-compatible version of bignum, there is also a v8.6 branch there.

The bignum OPAM package has been created a while ago.
There shouldn't be anything preventing this PR to be merged: normally, this is a backward compatible fix with 8.6 (not with 8.5 but is there really a will to keep compatibility with 8.5 as the README tends to suggest?).
@spitters Can you merge this then?

@Zimmi48, @letouzey Sorry for the late response.
We could drop the 8.5 branch. Is that the recommended way forward?
Do we need to make an 8.7 branch?
Travis is currently not set up properly, so I am going to ignore it's error messages for now.

Yes, I would suggest dropping the v8.5 branch.

Do we need a 8.7 branch?

In most libraries that we are tracking on our Travis, there is the will to provide a unique version of the library that is compatible with 8.6, 8.7 and 8.8 (= master) at the same time. This is quite doable given the focus on compatibility which was put during the 8.7 release. So trying to achieve this would be a possible solution.
@spitters BTW What is the status of math-classes? Should it be considered as a stable library that is only going to receive light fixes?

Concretely, that would mean deleting the 8.5 branch, but not necessarily
making a 8.7 branch, as master will be compatible with both ?
Yes, math-classes is fairly stable at the moment. However, there is
occasional development and current work on including it in HoTT.
On Tue, Sep 26, 2017 at 5:25 PM, Théo Zimmermann<EMAIL_ADDRESS>wrote:

Yes, I would suggest dropping the v8.5 branch.
Do we need a 8.7 branch?
In most libraries that we are tracking on our Travis, there is the will to
provide a unique version of the library that is compatible with 8.6, 8.7
and 8.8 (= master) at the same time. This is quite doable given the focus
on compatibility which was put during the 8.7 release. So trying to achieve
this would be a possible solution.
@spitters https://github.com/spitters BTW What is the status of
math-classes? Should it be considered as a stable library that is only
going to receive light fixes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/math-classes/math-classes/pull/41#issuecomment-332235400,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM2zoDD0oGp7LY-scTwy-51KmF4Z0Xiks5smReEgaJpZM4N3prp
.

Concretely, that would mean deleting the 8.5 branch, but not necessarily making a 8.7 branch, as master will be compatible with both ?

Yes, but in fact, given the little difference between v8.6 and master (in this repo), I'm pretty sure the right way forward would be to drop the v8.5 and the v8.6 branches and just make sure that master works with 8.6-8.8 (integrating relevant commits from v8.6). I can't test this right now but I'll try to see if I can tomorrow afternoon.
Then if this can be achieved, the next step would be to properly set up Travis so that any incoming PR is tested against all three versions of Coq.

For the record, I have just tested Pierre's branch on 8.6.1, 8.7+beta1 and 8.8+alpha (i.e. Coq master branch) and it compiles fine with all of these versions without any change.
I then proceeded to merge math-classes master branch into this branch and it still compiles with these three versions.

I don't see any reason to delete branches. It actually seems harmful for
posterity.
There will always be developments that would never be ported to newer
versions of Coq.
Concretely, I think I have some developments that depend on an 8.5 version
of MathClasses. I really don't have time to port them.
-- Abhishek
http://www.cs.cornell.edu/~aa755/
On Fri, Sep 29, 2017 at 1:38 PM, Théo Zimmermann<EMAIL_ADDRESS>wrote:

For the record, I have just tested Pierre's branch on 8.6.1, 8.7+beta1 and
8.8+alpha (i.e. Coq master branch) and it compiles fine with all of these
versions without any change.
I then proceeded to merge math-classes master branch into this branch and
it still compiles with these three versions.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/math-classes/math-classes/pull/41#issuecomment-333190881,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAeeci-5mnDEL-2su-wLIhpr7JA4Q84Oks5snSsPgaJpZM4N3prp
.

I don't especially advocate for deleting any branch but rather for freezing them and have all the development happen on master.
In particular, I find it harmful that the current default branch is v8.5.
So @spitters, I suggest merging this PR, then merging v8.6 in master, setting master as the default branch and updating the README to mention that this library is compatible with Coq 8.6 and later versions.

@spitters Thanks a lot. I see you have updated the README and made master the default branch. However I see #43 which is a merge of master into v8.6. Didn't you mean to do the opposite (merging v8.6 in master) so that the master branch actually compiles with 8.6 and later versions?

I reverted it in #44  and created #45. However, it does not look quite right to me.
@Zimmi48 Did I make a mistake?

It looks strange to me as well and this may be due to the reverted merge that you are now merging back. I suggest that you close #45 and I'll propose an alternative PR merging only the required changes in master.

Thanks.
I've closed #45


Need Permission for production Ready app

Dear Sir I like your washing machine flutter design and wish to get it in production ,i wish you to give me content permission

Hello,
This project was created to demonstrate the possibilities that flutter offers. The whole UI design was drawn by Dimest and thanks to his kindness I was able to use it in this project.
You are free to use technical aspects of this project, but unfortunately I can't decide if it can be used in such a form in production- I don't have ownership rights to the graphic design, on which the application was based.

Dimest is super cool designer ,and if you don't have ownership rights to the graphic design then you can suggest me the graphic designer name so  that i can ask him/her . For case of production level i will do  changements and give it a better look and also custom backend the main reason for adopting this design was its super cool UI and i wish you can make me learn about those kind of animation (wishing you will share these type of awesome source code  in your repo>


Add support for new London region

See https://github.com/oracle/oci-flexvolume-driver/blob/master/pkg/oci/client/config.go#L31
var ociRegions = map[string]string{
	"phx": "us-phoenix-1",
	"iad": "us-ashburn-1",
	"fra": "eu-frankfurt-1",
}

Need SDK update to v1.0.0


DriftNettyServerConfig with assumeClientsSupportOutOfOrderResponses=false is processing requests out of order

Summary
When DriftNettyServerConfig is configured with ```assumeClientsSupportOutOfOrderResponses = false`` then writing 2 messages should cause polling for the 2nd message to return null instead of an object.
This is causing unit test failures in the Drift project of Presto, see https://github.com/prestodb/drift/issues/15, and happens after changing the Netty version to >= 4.1.38
See https://github.com/prestodb/drift/pull/22
Expected behavior
Netty server should only process the second message after we are done with the first request.
Actual behavior
Netty server starts processing the second message (its state is PENDING) even though the first request is not done.
Steps to reproduce
See PR https://github.com/prestodb/drift/pull/22 on repro-steps
Install JDK 8 and mvn 3.5.0
git clone git@github.com:prestodb/drift.git
cd drift/drift-transport-netty
mvn clean test -Dtest=TestDriftNettyServerTransport

Minimal yet complete reproducer code (or URL to code)
Netty version
4.1.38.Final
JVM version (e.g. java -version)
1.8.0_261
OS version (e.g. uname -a)
Mac OS Catalina 10.15.5 -  Darwin Kernel Version 19.5.0

Hi, @trustin ,  @normanmaurer , just checking if this was on your radar to see if it's indeed a bug and introduced in v. 4.1.38. Thank you

I will have a look this week. So yes on my radar

@afernandez so basically you say you can reproduce this starting 4.1.38.Final (and also in the latest release) right ?

@afernandez ^^

I suspect the change in behaviour was introduced by https://github.com/netty/netty/commit/6b6475fb565551c36f372fe37683d98df6674161 ... But to better understand if this is a bug or not I would need to get some more details about what you try to do.  Can you give some more pointers in what you try to do with your code and how you do it ? Like for example point me to the right places in your code ?

Also I tried to run the test but it failed as the snapshot was missing:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  14.758 s
[INFO] Finished at: 2020-08-18T14:05:59+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project drift-transport-netty: Could not resolve dependencies for project com.facebook.drift:drift-transport-netty:jar:1.28-SNAPSHOT: The following artifacts could not be resolved: com.facebook.drift:drift-api:jar:1.28-SNAPSHOT, com.facebook.drift:drift-codec:jar:1.28-SNAPSHOT, com.facebook.drift:drift-protocol:jar:1.28-SNAPSHOT, com.facebook.drift:drift-transport-spi:jar:1.28-SNAPSHOT: Could not find artifact com.facebook.drift:drift-api:jar:1.28-SNAPSHOT in sonatype-nexus-snapshots (https://oss.sonatype.org/content/repositories/snapshots) -> [Help 1]
[ERROR]

Do I need to add some snapshot repository ?

@afernandez ping... sorry but I need some help here to help you :)

@normanmaurer , Answering the questions you had about this issue.

@afernandez so basically you say you can reproduce this starting 4.1.38.Final (and also in the latest release) right ?

yup.

I suspect the change in behaviour was introduced by 6b6475f ... But to better understand if this is a bug or not I would need to get some more details about what you try to do. Can you give some more pointers in what you try to do with your code and how you do it ? Like for example point me to the right places in your code ?

That is indeed our analysis as well. https://github.com/prestodb/drift/issues/15 mentions about the failing test and same suspected commit.
The way we are using this is something like this. from ResponseOrderingHandler
public class ResponseOrderingHandler
        extends ChannelDuplexHandler
{
    @Override
    public void channelRead(ChannelHandlerContext context, Object message)
    {
        if (message instanceof ThriftFrame) {
            ThriftFrame thriftFrame = (ThriftFrame) message;
            if (!thriftFrame.isSupportOutOfOrderResponse()) {
                context.channel().config().setAutoRead(false);
            }
        }
        context.fireChannelRead(message);
    }

If out of order responses are not supported then channel's autoRead is set to false. However since 6b6475f changes the behavior to not completely depend on the autoread flag the semantics have changed.

Also I tried to run the test but it failed as the snapshot was missing:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  14.758 s
[INFO] Finished at: 2020-08-18T14:05:59+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project drift-transport-netty: Could not resolve dependencies for project com.facebook.drift:drift-transport-netty:jar:1.28-SNAPSHOT: The following artifacts could not be resolved: com.facebook.drift:drift-api:jar:1.28-SNAPSHOT, com.facebook.drift:drift-codec:jar:1.28-SNAPSHOT, com.facebook.drift:drift-protocol:jar:1.28-SNAPSHOT, com.facebook.drift:drift-transport-spi:jar:1.28-SNAPSHOT: Could not find artifact com.facebook.drift:drift-api:jar:1.28-SNAPSHOT in sonatype-nexus-snapshots (https://oss.sonatype.org/content/repositories/snapshots) -> [Help 1]
[ERROR]

Do I need to add some snapshot repository ?

The dependent libraries (drift-api / drift-codec .. ) can be built locally to resolve the snapshot issues.
If you prefer working off snapshot dependencies please use one of the release branches. Latest being 1.32 https://github.com/prestodb/drift/tree/1.32

@normanmaurer any chance we can get this back on the radar? https://github.com/prestodb/presto/issues/16210

Yes... I will have a look next week

Hey @normanmaurer! Did you ever get a change to look into this?

@normanmaurer Wondering if you had a chance to look at this.

@normanmaurer We are trying to add a FlowControlHandler in the pipeline to work around this so that when autoRead is set as false in ResponseOrderingHandler the FlowControlHandler ensures that we are still reading one at a time. Let us know if you are seeing any concerns with this approach.


C_CPP_Operating System- CPU Scheduling Algorithms

Description
Detailed, documented code with preemptive, time gap and edge-case handling
Domain
C/CPP
Type of Contribution
Documentation, Others
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

/assign


[BEAM-13746] Fix deserialization of SSECustomerKey for AWS Sdk v2

Fix deserialization of SSECustomerKey to allow all fields to be nullable and add missing tests for serialization / deserialization.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @aromanenko-dev
R: @mattrudary


More $schema tests needed

There needs to be some more semantic tests written for $schema.

Turns out there's already #244, but this ensures there are $schema tests.

#210 was relevant for this, but GH isn't allowing reopening it after however it was originally closed.

#587 resurrected #210 and was just merged, so we're good here at least for some combinations. New tickets for any missing tests are of course still welcome.


examples/c: Add TC example

Add a TC example to showcase the libbpf TC APIs.
Also serve as an answer to question raised in this discussion (0).
Signed-off-by: Hengqi Chen<EMAIL_ADDRESS>

@borkmann, can you review this TC example?
@chenhengqi can you also please update README?

@borkmann, can you review this TC example?
@chenhengqi can you also please update README?

Updated.

@borkmann, can you review this TC example?
@chenhengqi can you also please update README?

Updated.

Looks good to me overall, the code could probably be further stripped down, e.g. to remove it to the absolute min (e.g. stripping signal handling, etc).

Greeting, thanks for the great work.
Just curious, is it possible to also demonstrate how to leverage Layer 2 information in this example? (by struct ethhdr)?

Greeting, thanks for the great work. Just curious, is it possible to also demonstrate how to leverage Layer 2 information in this example? (by struct ethhdr)?

Users can easily retrieve these information and are expected to play with it themselves.

@borkmann, can you review this TC example?
@chenhengqi can you also please update README?

Updated.

Looks good to me overall, the code could probably be further stripped down, e.g. to remove it to the absolute min (e.g. removing signal handling, etc).

Thanks. Daniel.

@chenhengqi thanks a lot for this contribution! And thanks @borkmann for review.


Android Java: 02.20 TimePicker in android

Description :scroll:

Give a step-by-step tutorial of TimePicker in Android (Java).
Required Documentation or Video or Audio.

Domain of Contribution :bar_chart:

[x] Android Dev (java)

References :
https://www.tutorialspoint.com/android/android_timepicker_control.htm

Please Read it Carefully Before Contributing

Changes should be made in Android_Development_With_Java/ directory under Android_Development_With_Java branch.
Inside Android_Development_With_Java directory/ creates a directory and names it according to the topic
Inside Topic Name directory/ add your task with subtopic number and name and make changes accordingly.
You have to push your PR to the Android_Development_With_Java branch only.
You can take help to the references but don't simply try to copy it. Just explain in your own word.
This issue is for GWOC'21 contributors only.
You need to push in a single commit. If there exists more than one commit then you need to squash your commits into one commit.
Will assign you on a first come first serve basis.
Please try to complete your assigned task within 7 days. If you need some more time then, please inform mentors and supervisors.
If you have two previously assigned issues on Android-Java pending then please first complete them.

Supervisor @VikasPandey121

I would like to work on this @sitamadex11 @VikasPandey121 Sir.


Removing otel-collector from public staging (for now)

Also some minor YAML formatting fixes

It looks like there's something not quite right with the staging and prod overlays.
Error: no matches for Id ApplicationSet.v1alpha1.argoproj.io/tracing-workload-otel-collector.[noNs]; failed to find unique target for patch ApplicationSet.v1alpha1.argoproj.io/tracing-workload-otel-collector.[noNs]

It looks like there's something not quite right with the staging and prod overlays.
Error: no matches for Id ApplicationSet.v1alpha1.argoproj.io/tracing-workload-otel-collector.[noNs]; failed to find unique target for patch ApplicationSet.v1alpha1.argoproj.io/tracing-workload-otel-collector.[noNs]

See reason in https://github.com/redhat-appstudio/infra-deployments/pull/3845#discussion_r1626501312