Comments (4)
@rnowling-memphis I looked into the memphis/memphis file on my local machine and after running the pylint test the given error is found on the following lines:
bug.py:478:21: E1101: Instance of 'FileDescriptorSet' has no 'file' member (no-member)
bug.py:479:23: E1101: Instance of 'FileDescriptorSet' has no 'file' member (no-member)
bug.py:482:27: E1101: Instance of 'FileDescriptorSet' has no 'file' member (no-member)
Here's the code snippet, Please have a look into this :
- After adding
# pylint: disable-next=no-member
, on line 478,479,482, The error got fixed!
from memphis.py.
Thanks @Adarsh-jaiss ! I'm not sure that disabling the linting error is the right move here without first checking that the code works. In the previous instance, it made sense to disable the error because we explicitly check that the member exists and have an alternative code path if not. Here, we absolutely depend on the file
attribute existing. This one will require more work on your end to debug. In particular, it seems like you would need to:
- Set up Memphis locally using Docker
- Create a station with a protocol buffer-based schemaverse attachment
- Modify the memphis.py code to add some print statements or something so you can verify that this code block is run, the file field exists, etc.
- Install the SDK into a local virtual environment
- Write a simple producer that produces messages in protocol buffer format.
I think this is going to be a fair amount of work. If you don't want to take that on quite yet, I think there is other work that needs to be done that would be much easier. For example, it would be nice to add examples to the function documentation like those for Consumer.fetch()
so that we can eventually generate useful API docs. What do you think?
Either way, we value your contributions and thank you!
from memphis.py.
- In which issue, is that function reffered to?
- I would love to work on that issue
from memphis.py.
Thanks @Adarsh-jaiss ! I'm not sure that disabling the linting error is the right move here without first checking that the code works. In the previous instance, it made sense to disable the error because we explicitly check that the member exists and have an alternative code path if not. Here, we absolutely depend on the
file
attribute existing. This one will require more work on your end to debug. In particular, it seems like you would need to:
- Set up Memphis locally using Docker
- Create a station with a protocol buffer-based schemaverse attachment
- Modify the memphis.py code to add some print statements or something so you can verify that this code block is run, the file field exists, etc.
- Install the SDK into a local virtual environment
- Write a simple producer that produces messages in protocol buffer format.
I think this is going to be a fair amount of work. If you don't want to take that on quite yet, I think there is other work that needs to be done that would be much easier. For example, it would be nice to add examples to the function documentation like those for
Consumer.fetch()
so that we can eventually generate useful API docs. What do you think?Either way, we value your contributions and thank you!
- I have locally installed the memphsis and now i'm trying to understand the issue and would love to work on this issue!
- And in the meantime , I'll also be working on the another issues including the one which you talked above
- please explain the issue you mentioned above in detail, so that i can work on that
from memphis.py.
Related Issues (20)
- [Discussion] Typing, tests, formatting, pre-commit HOT 4
- Stop consume functionality HOT 7
- Create formal documentation HOT 3
- Bug: Improve error description HOT 6
- Bug: Tries to access property of None instance HOT 2
- Bug: Missing method HOT 2
- Setup automated tests for PRs
- Bug: Review no-member error for Exception status_code member HOT 6
- Re-enable E1101 message from Pylint
- Raise MemphisSchemaError rather then MemphisError HOT 1
- lint project using Ruff HOT 3
- Use separate connections for producers, consumers, etc.
- Inconsistent consumer name HOT 1
- Add examples to docstrings for consumer methods HOT 6
- Add task count limit to async produce
- Add error handling for async produce
- Drain or cancel waiting tasks when the producer is destroyed
- Support destroying existing consumers
- Change name of async producer parameter to "non-blocking"
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from memphis.py.