Dio is a robust and flexible HTTP client for Flutter with support for interceptors, timeouts, and transformers.
Master Flutter API integration with Dio and learn best practices for error handling. Improve app performance and stability with clean, scalable networking code.
If I can get some support from the maintainere, sure. I think they are all unavailable these days though. The review queue is now 200+ PRs deep. I'll probably make a fork for myself until this gets prioritized.
On many occasions, I've opened up requests for support in the form of a Github pull request. This way, I am telling the author: I have found a potential problem with your library, here is how I fixed it for my circumstance, here is the code I used for reference. You get extra internet points if you open the pull request with: "I don't expect this pull request to get merged, but I wanted to you show you what I did".
Not everyone has time to adhere to the specific coding styles for a project, so if you can't do a full blown pull-request, there is NOTHING wrong with opening a pull-request that only has the intention of showing the author how you solved the problem.
Don't assume that because you opened up a pull request, that the author will accept it. There are many reasons that a maintainer might choose to not merge in your specific patch, many of which have nothing to do with you. If your patch isn't accepted, try to assume it's for a valid technical reason and not because the author hates you.
Don't get upset, rejection is normal
(This isn't a duplicate because it's explicitly seeking a workaround given certain constraints, not just asking for direct replacement.)
The companies behind six of the 11 apps, including Southwest Airlines and Twitter, were not sharing how many requests they’d received and honored. Twitter said it plans to add the information.
or were left with no idea whether it worked
name =
This part of the annotation should be put in the metadata for future versions of the exporter
Is the column a boolean column? (i.e. what does User.columns_hash[:admin_created].type return?)
A de
ما یه چیز دیگه هم داریم به نام @before_request که اونم خیلی جالبه
)
یه سری چیز دیگه هم هست use_reloader انگار پس از هر تغییری خودش restart می کنه threaded یعنی هر request را به یک thread بسپاری
.
ما یه سری چیز جالب دیگه هم داریم که اینجا نیورده request.json request.data
Cookies
اینا تو درس Cookie توضیح می دهم
method
از همین استفاده می کرد که بتونه بفهمه الان با Method به نام Request یا Response
Form
این داخلش اطلاعاتی که به وسیله POST و در داخل Form در سمت View درست شده است را میفرستن تو این Object که انگار یک Dictionary هم هست. خیلی بهتر در این سایت برات نوشتم. https://www.digitalocean.com/community/tutorials/processing-incoming-request-data-in-flask
request.cookies.get
اینم نحوه get کردن که مثل همیشه از طریق request این کار را می کنه
ven belo
اقا دقت کن که من form در یک جلسه قبل گفتم حالا اومده تو صفحه student.html یک فرم گذاشته که تو فرمش گفته بفرس به result (البته من تو digital occean خوندم که باید بفرسته به همون جایی که ازش form را گرفته و این برام عحیبه) به هر حال در result گفته با post بگیر و اطلاعات را از طریق request.form بگیر و حالا با صفحه result اون اطلاعات را به کاربر نشون بده. خیلی ساده و قشنگ
If the JSON o
نکته خیلی مهمی که میگه اینه که حتما باید Value ها حاوی کلید باشند مگرنه به مشکل میخوره
request.get_json()
چه تابع جالبی که میاد اطلاعات JSON را به Python تبدیل می کند
s:
قوانین تبدیل JSON به Python dict: اولا اگر در Json حالت Key و Value داشته باشد، در پایتون به صورت Dictionary است. دوما آرایه در Json به List در پایتون تبدیل می شود. سوما Value هایی که داخل " " باشد به Sting در پایتون تبدیل می شود. چهارما باحاله نگاه کن :) پنجما اعدادی که " " نداشته باشد به اعداد تبدیل می شود.
In P
هر وقت اسم JSON پیش می اید نام POSTMAN می درخشد
Usin
حالا رفت سراغ Json چون خیلی بهتر از Query String و Form Data براد اطلاعات را میفرسته. برای اطلاعات پیچیده تر بهتر است.
Inside
شاهکارش برای Handle کردن FORM. خیلی خووبه یاد بیگیر
The most important thing to know about this form is that it performs a POST request to the same route that generated the form.
این فرم POST Request را میفرسته به همون URL که این Form را Generate کرده. دقتم داشته باش که این فیلد ها را بعدا میشه در Object به نام Form گرفت و اسمشم همونایی که در Attribute به نام name گذاشتیم که اینجا language و Framework است
To de
جالبه برای درست کردن Form اومده هر دو تابع GET و POST را گذاشته و اینجوری تو موقع Get که فرم را میفرسته
Form data
از اینجا در مورد object به نام Form توزیح می دهد که اطلاعاتی که تو اطلاعاتی که در From و در تابع POST میفرستی میاد در Object به نام Form
reques
دو جورمیاد اون Query String را میگیره request.args.get request.args حس می کنم که این args یک Array است دقت داشته باش که language یک کلید است و با این دستور میاد محتوا را میگیره. در صورتی request.args.get که حتی اگر language هم خالی باشه بازم مشکلی در اجرای برنامه پیش نمیاد، البته اگه برنامه تو اینا Handle کنه و مقدار خروجی اش برابر None است. در صورتی که request.args بخوای بری اگر نداشته باشه بهت خطای 400 میده.
A query string
اینجا داره query string هاشا درست میکنه
This tutoria
اینجا که برات پیش نیازها را نوشته
Our test raises an ActiveRecord::RecordNotFound exception. We know that Rails has special handling to return a 404 status code in this case. However, the request spec still raises the exception.
This will no longer be necessary if this MR is merged #101
If this MR had been merged it would have saved us a lot of time and trouble.
Not trying to be presumptuous, but thought this proposal would be best served with a PR.
let's not mix code changes with prettier. This is a bad practise which complicates code review and history review. Let's apply prettier in a separate PR/commit.
Formalize your Pull Request etiquette.
Between each run, you will need to delete the bisectNNNN.coverage files, otherwise the report will contain information from those previous runs:
I'm surprised this operation is not done via some dune task. I'd expect the "plugin" for dune to add high-level commands to reset the test coverage; or to perform the reset automatically at each execution of a test.
Request For Information (RFI) https://en.itpedia.nl/2017/02/18/sisp-3-3-request-for-information-rfi/ Request_For_Information (RFI)" is the questionnaire with questions about all musthave criteria, general company_information about the supplier and degree of penetration of the software in the industry. SaaS.
When you are using postman they are not restricted by this policy. Quoted from Cross-Origin XMLHttpRequest: Regular web pages can use the XMLHttpRequest object to send and receive data from remote servers, but they're limited by the same origin policy. Extensions aren't so limited. An extension can talk to remote servers outside of its origin, as long as it first requests cross-origin permissions.
Sending body/payload in a GET request may cause some existing implementations to reject the request — while not prohibited by the specification, the semantics are undefined. It is better to just avoid sending payloads in GET requests.
Requests using GET should only be used to request data (they shouldn't include data).
Has the Linux Mint team decided whether it might please add this sorely missed feature? I'm keeping Nautilus around in addition to Nemo just for this one feature. This feature is so much more efficient than other methods when you have a giant folder of many files and want to organize it into subfolders (which you can then easily move or rename afterwards — but at least this helps with the first step, which is to get the correct files into a folder together). P.S. This was also requested in #560.
If you do need to passthrough your mydomain.com cookies to a thirdparty.com domain, you can technically already do that now by implementing it as an endpoint and calling fetch('/my-endpoint')
No it doesn't. I've simply told SvelteKit to ignore the type error from credentials missing. If there's some other issue or missing feature it's not blocked by this. That being said, I wouldn't mind getting this change in
If you would like to make a code change, go ahead. Fork the repository, open a pull request. Do this early, and talk about the change you want to make. Maybe we can work together on it.
Cross-site scripting (XSS) vulnerabilities (even in other applications running on the same domain) allow attackers to bypass essentially all CSRF preventions.
Sure sometimes my changes get rejected, but it almost always comes with a reason why and I can work together with the maintainer to come up with a sensible solution to my issue.
Any idea @AaronLasseigne if this is mergeable?
Take 3, Previously attempted in 2012 (#8189) and 2015 (#19709). This new version uses ActiveModel Attributes API.
When your digital news feed doesn’t contain links, when it cannot be linked to, when it can’t be indexed, when you can’t copy a paragraph and paste it into another application: when this happens your news feed is not flawed or backwards looking or frustrating. It is broken.
If your news feed doesn't contain links, can't be linked to, indexed, or copied and pasted, it is broken.
How can this be tied into the five R's of Open Education Resources: Retain, Reuse, Revise, Remix and/or Redistribute content (and perhaps my Revise/Request update ideas: https://boffosocko.com/2018/08/30/the-sixth-r-of-open-educational-resources-oer/)
You can afford to make a proper PR to upstream.
No more waiting around for pull requests to be merged and published. No more forking repos just to fix that one tiny thing preventing your app from working.
This could be both good and bad.
potential downside: If people only fix things locally, then they may be less inclined/likely to actually/also submit a merge request, and therefore it may be less likely that this actually (ever) gets fixed upstream. Which is kind of ironic, considering the stated goal "No more waiting around for pull requests to be merged and published." But if this obviates the need to create a pull request (does it), then this could backfire / work against that goal.
Requiring someone to fork a repo and push up a fix commit -- although a little extra work compared to just fixing locally -- is actually a good thing overall, for the community/ecosystem.
Ah, good, I see they touched on some of these points in the sections:
Can this be merged please, this fixes a problem I have
Better community building: At the moment, MDN content edits are published instantly, and then reverted if they are not suitable. This is really bad for community relations. With a PR model, we can review edits and provide feedback, actually having conversations with contributors, building relationships with them, and helping them learn.
Better contribution workflow: We will be using GitHub’s contribution tools and features, essentially moving MDN from a Wiki model to a pull request (PR) model. This is so much better for contribution, allowing for intelligent linting, mass edits, and inclusion of MDN docs in whatever workflows you want to add it to (you can edit MDN source files directly in your favorite code editor).
So before using GET with Body parameter, you must first ensure the servers are supporting it. It is possible that some servers might ignore the body of GET request or behavior like caching GET/HEAD requests might cause issues.
A payload within a GET request message has no defined semantics; sending a payload body on a GET request might cause some existing implementations to reject the request.
When you email me, please include a minimal bash script that demonstrates the problem in the body of the email (not as an attachment). Also very clearly state what the desired output or effect should be, and what error or failure you are getting instead. You are much more likely to get a response if your script isn't some giant monster with obtuse identifiers that I would have to spend all afternoon parsing.
req
HTTP request argument to the middleware function, called "req" by convention.
Request - User's incoming data. Response - Your outgoing data.
‘Bus drivers didn’t have adequate PPE even though they requested it’ – Edinburgh University’s Dr Gwenetta Curry. (2020, October 19). Channel 4 News. https://www.channel4.com/news/bus-drivers-didnt-have-adequate-ppe-even-though-they-requested-it-edinburgh-universitys-dr-gwenetta-curry
Don’t fetch stuff unless you actually need it Judging from the response to our 503 errors, much of the software requesting DTDs and schemata from our site doesn’t even need them in the first place, so requesting them just wastes bandwidth and slows down the application. If you don’t need it, don’t fetch it!
Use ponyfill.com for linking here.
Art by O’Hare and Bell highlight - both visually and conceptually - the dialogic quality of annotation expressing power.
While I'm reading this, I can't help but wishing that Hypothes.is would add a redaction functionality to their product. They could potentially effect it by using the highlighter functionality, but changing the CSS to have the color shown be the same as that of the (body) text instead of being yellow.
(Note sure if this is a feature request or a bug...)
But maybe this PR should still be merged until he finds time for that?
Sorry this sat for so long!
Wow, no answers to this question. That's too bad. Did you ever find the solution?
I wonder at what point Svelte would add this feature if, for example, a majority of their users ended up migrating to a fork that added this missing feature (like this one)?
Would they then concede and give in to popular demand in order to avoid a schism of the community?
Kind of like Rails swallowed / consolidated with Merb after they saw how great its ideas were?
TBH It is a bit disheartening to see this issue closed when all proposed solutions do not sufficiently solve the issue at hand, I really like svelte but if this is how feature requests are handled I am probably not going to use it in the future.
Maria Sundaram PhD on Twitter. (n.d.). Twitter. Retrieved September 14, 2020, from https://twitter.com/mariasundaram/status/1304453386914402304
Peter Slattery on Twitter: “Are you, or is anyone you know, researching how COVID-19 has affected behaviour and behavioural drivers in Victoria and Australia, in particular behaviours that related to topics such as ‘active transport’, ‘service provision’, ‘working from home’ and ‘car usage’?” / Twitter. (n.d.). Twitter. Retrieved June 23, 2020, from https://twitter.com/peterslattery1/status/1274874801174179840
COVID-19 Symptom Survey—Request for Data Access. (n.d.). Facebook Data for Good. Retrieved May 29, 2020, from https://dataforgood.fb.com/docs/covid-19-symptom-survey-request-for-data-access/
What We Know About College Students to Help Manage COVID-19 – Center for Social & Behavioral Science. (n.d.). Retrieved August 26, 2020, from https://csbs.research.illinois.edu/2020/08/16/what-we-know-about-college-students-to-help-manage-covid-19/
The collection of changes to fix the issues we want to address would be probably of the same size, but it would make easier to review and merge if we could break this PR in many steps. I find it really hard to believe we need to change 170 lines in a single commit to be able to fix this issue. We probably could break the first commit in many commits, test the class better and that would give more confidence over what is being changed. Right now I see a huge diff, with a few assertions changes and no real reason why all those lines had to change.
New information that would be useful toward the future usage or troubleshooting of GitLab should not be written directly in a forum or other messaging system, but added to a docs MR and then referenced, as described above.
When you encounter new information not available in GitLab’s documentation (for example, when working on a support case or testing a feature), your first step should be to create a merge request (MR) to add this information to the docs. You can then share the MR in order to communicate this information.
Andia, T., Mantilla, C., Rodriguez-Lesmes, P., Criado, L., Gomez, J. S., Ortiz, S., Quintero, A., Rincón, H., & Romero, S. (2020). Mentioning anosmia improves how community pharmacies handle phone call requests during the COVID-19 pandemic: An audit study in Colombia [Preprint]. SocArXiv. https://doi.org/10.31235/osf.io/s2z47
Problem is, everyone's busy, so it can be days or even weeks before even a small PR is merged. So I'm stashing my stuff here as I write it. I'll still try to keep the PRs in motion, to gradually get some of this merged.
Sometimes, the line between 'bug' and 'feature' is a hard one to draw. Generally, a feature is anything that adds new behavior, while a bug is anything that causes incorrect behavior. Sometimes, the core team will have to make a judgment call.
Please don't put "feature request" items into GitHub Issues. If there's a new feature that you want to see added to Ruby on Rails, you'll need to write the code yourself - or convince someone else to partner with you to write the code. Later in this guide, you'll find detailed instructions for proposing a patch to Ruby on Rails. If you enter a wish list item in GitHub Issues with no code, you can expect it to be marked "invalid" as soon as it's reviewed.
We iterate to deliver features, so we often don't have functionality that people expect. For this reason, 'people could reasonably expect this functionality' does not make it a bug.
If people care about a missing feature, then ideally the issue should be marked as ~"Accepting merge requests"
With single-commit MRs I often can copy the commit message directly into the MR description, which is convenient.
Unfortunately, the WordPress.org plugin repository doesn’t provide a way to maintain your plugin with Git.
Some months ago, I wrote about using Git and Github with the wordpress.org plugin repository.
I wish Mozilla would recognize the importance of built-in translation that Google Chrome and Microsoft Edge have.
The Authenticity Token is a countermeasure to Cross-Site Request Forgery (CSRF). What is CSRF, you ask? It's a way that an attacker can potentially hijack sessions without even knowing session tokens.
Rails does not issue the same stored token with every form. Neither does it generate and store a different token every time. It generates and stores a cryptographic hash in a session and issues new cryptographic tokens, which can be matched against the stored one, every time a page is rendered.
Since the authenticity token is stored in the session, the client cannot know its value. This prevents people from submitting forms to a Rails app without viewing the form within that app itself. Imagine that you are using service A, you logged into the service and everything is ok. Now imagine that you went to use service B, and you saw a picture you like, and pressed on the picture to view a larger size of it. Now, if some evil code was there at service B, it might send a request to service A (which you are logged into), and ask to delete your account, by sending a request to http://serviceA.com/close_account. This is what is known as CSRF (Cross Site Request Forgery). If service A is using authenticity tokens, this attack vector is no longer applicable, since the request from service B would not contain the correct authenticity token, and will not be allowed to continue.
[link](url){:target="_blank"} Works for jekyll or more specifically kramdown, which is a superset of markdown, as part of Jekyll's (default) configuration. But not for plain markdown. ^_^
For ghost markdown use: [Google](https://google.com" target="_blank) Found it here: https://cmatskas.com/open-external-links-in-a-new-window-ghost/
since mobile Chrome still doesn't support extensions (Google plz)
This API uses request body in GET requests. For a long time this was prohibited in RFC2616 HTTP specification, but since RFCs 7230-7237, it is only discouraged, since older implementations could reject such requests. However, given that major APIs such as ElasticSearch's already implement GET with request bodies, there is precedence to such implementation.
My first sighting of the sending a request body with get request.
Maybe you could provide a patch with tests and we could discuss on top of it?
descriptive study of a large develop-ment team—roughly 450 people producing about 9,000 annotationson about 1,250 documents over 10 months—using a Web-based anno-tation system.
“But, if you’re unsure or haven’t mapped out entirely your processing activities,” he said, “it’s impossible to accurately reflect what your users or clients are consenting to when they complete a consent request.”
An example of an extended consent form that allows users to give consent in a more granular manner – i.e. selectively for a number of processing purposes (analytics, remarketing or content personalization)
A single consent form is useful when consent is requested for a single purpose. Here: analytics
This seems like an important distinction:  Probably (?) you can only use a simple Agree/Disagree consent request if you only have a single purpose/category that you are obtaining consent for.
As soon as your site has multiple categories to need consent, then you must allow individual consent/refusal of consent for each individual category/purpose.
This is alluded to just a little bit further on:
Consent should also be granular; users must be allowed to selectively decide what types of tracking, analytics and other activities their data can be used for.
Don't be discouraged when you get feedback about a method that isn't all sunshine and roses. Facets has been around long enough now that it needs to maintain a certain degree of quality control, and that means serious discernment about what goes into the library. That includes having in depth discussions the merits of methods, even about the best name for a method --even if the functionality has been accepted the name may not.
about: merits
Cool idea how they show which ideas they are considering, planning, and have already launched.
Request features
it is worth opening a merge request with the minimal viable change instead of opening an issue encouraging open feedback on the problem without proposing any specific change directly.
Although unexpected, a high-3He/4He source dominating the isotope ratio could explain why the R/Ra values are higher than those found for MORBs. This would be most visible in rocks that have low helium concentrations and low U-Th-Sm contents, such as recycled pelagic sediments strongly depleted in almost all their helium and U-Th during subduction
Could use further explanation
[8 ± 1 R/Ra (SD)]
What does this mean? Needs some translation
Feature requests are great, but they usually end up lying around the issue tracker indefinitely. Sending a pull request is a much better way of getting a particular feature into Capybara.
For every question you might have, please create a discussion thread, not a single comment. This makes it a bit easier to see and reply to the question, instead of questions and answers getting mixed together:
Watch the Video Request Quote
Can we get a third button where customers can ask for a demo.
Two great Mother Earth defenders were present on the last day of COP 21 in the public area.
Is there any way of finding he transcripts for this day?
Annotate
Nice to see hypothes.is off the ground. One thing that genius has that would be welcome is the ability to up/downvote comments. A casual glance at the annotations on this page and you'll see a lot of cruft that should be hidden by default, perhaps the way reddit hides posts below a certain threshold.
n
werden ... werfen
oder
wenden, dann aber ohne werfen.
are
to be deleted
As far as I know, the major concerns of Zotero are: Storing and searching items in a library Assigning user-supplied metadata to these items Exporting the metada in some common bibliogaphic formats Additional, it appears Zotero allows to store notes. So what's the relationship to h? To the extent notes in Zotero can accommodate the richness of an annotation, it could be a storage backend for h. Notes are page-level annotations, at least. We could allow Zotero users with existing libraries to import their notes as annotations.
The question "So what's the relationship to h?" is a good one here; in particular, where does h end and other services/apps begin? I have quite a few thoughts in this area, including possible h spin-off companies, but my first interest in thinking about integrating it with other services is more from a strategic engineering perspective: what are the best places to focus h development so that it fits that composable unix-y philosophy of "do one thing well"; and I translate that thinking from tool to person... how can h help me do one thing well? As an end-user, even though I am admittedly a power-user with a lot of tools, I actually want to use as few tools as possible. The browser-extension part of h is the single most important part of the project from my end-user perspective-- the back-end infrastructure is there to support the browser-extension doing one thing well.
The one thing I want h to do for me that I can't do with any other tool that I know of is to allow me to rapidly track my reading and thinking and note-taking habits together. I want to be able to quickly select multiple portions of text and apply commentary and tags to the text within particular activity-based or goal-based contexts. The last part of that thought is the essential element I need that is missing. Speeding up the text selection would be very helpful in making it a tool I want to use on a daily basis for everything I do, but the contexts feature is what will make h a killer app for me.
Ho w to R ead a Judicia l Opin ion: A G uid e for N ew L aw Stu den ts Professor Orin S. Kerr George Washington University Law School Washington, DC Version 2.0 (August 2005) This essay is desig ned to help entering law students understand ho w to read cas es for class. It explains what judicial opinions are, how they are structured, and what you should look for when you read them. Part I explains the various ingredients found in a typical judicial opinion, and is the most essential section of the essay . Par t II discusses what you should look for when you re ad an opinion for class. Part II I con clu des with a brief discussion of why law schools use the case method.
I need a way to add tags to a document that will apply to all annotations in a particular document (except where explicitly canceled).
The problem is that I often want to query all annotations related to a specific document, collection of documents, or type of activity.
Type of activity requires further explanation: Given a document or collection of documents I may annotate the document for different reasons at different times.
For example, while annotating the reading materials, video transcripts, and related documents for the CopyrightX course there are certain types of annotations that may be "bundled together" so that when I search for those things later I can easily narrow my searches to just that subset of annotations; but at the same time I need a way to globally group things together.
While reading judicial opinions the first activity/mode of interaction with a particular document may be to identify the structure of the judicial opinion (the document attached to this annotation describes the parts of the judicial opinion I might want to identify: *caption, case citation, author, facts of the case, law of the case, disposition, concurring and/or dissenting opinions, etc).
The above-described mode I may use for multiple documents in one session related to the course syllabus for the week.
To connect each of these documents together I might add the tags: copyx (my shorthand for the name of the course, CopyrightX), week 1 (how far into the course syllabus), foundations (the subject matter in the syllabus which may span week 1, week 2, etc), judicial opinions (the specific topic I am focused on learning at the moment (may or may not be related to the syllabus).
Later on another day I might update my existing annotations or add new ones when I am preparing to study for an exam. I might add tags like to study, on midterm, on final to mark areas I need to review.
After the exam I might add more tags based on my test score, especially focusing on areas that received a poor score so I can study that section more or, if I missed some sections so didn't study and it resulted in a poor score in that area, add tags to study for later if necessary.
I have many more examples and modes of interaction in mind that I can explain more later, but it all hinges on a rich and flexible tagging system that: