Hi! I just want to ask if there's a mapping from TextMate scopes to Pygments tokens? I can't find any question about it, and Pygments tokens seem to differ from TextMate scopes.
@AshwinPhadke A lot of tools and even more features aren't made with programatic usage in mind. Anything that specifies a specific, parseable output format isn't a stable information source to begin with.
@MisterMiyagi Git has an interesting approach here. 'But because Git was initially a toolkit for a version control system rather than a full user-friendly VCS, it has a number of subcommands that do low-level work and were designed to be chained together UNIX-style or called from scripts. These commands are generally referred to as Git’s “plumbing” commands, while the more user-friendly commands are called “porcelain” commands.'
I think it's generally a problem in the UNIX world how much of it is de facto parsing of string outputs. At least have a --json flag, or even better, pass around objects as with PowerShell, but of course that isn't possible across different programming languages.
I would like to do the following:
Build triton Python (which run from Python script):
Into specific directory
Build all cpp files with debug symbol
LLVM which used by triton should also be built with debug symbols
Run a Python file to debug:
Related Python script
Called cpp functions or obje...
yeah, or the project shouldn't create a situation where that nonsensical looking instruction is part of the process
they could have amended it to -e ./python to make it clearer that it's the one in the current directory
still, point is when people ask "I try to install the thing and I don't know how someone please give me instructions" while don't tell people that 1) they've followed the standard instruction and it doesn't work and 2) worse, they actually skipped a pretty critical step and now nothing works and 3) they don't note any of this down
Have I just teleported to an alternate universe? This comment seems ridiculous. Of course SO is about implementation so why dump some theoretical and then cause the OP to raise another question?
anyone able to help me figure out why my flask+CORS works on HTTP but not HTTPS? I have a feeling this has smething to do with it, but I do need a grownup to help
requests.post(...) from localhost works just fine on the HTTPS endpoint. But if I attempt a fetch(...) in the browser's dev console, I get Cross-Origin Request Blocked
I'll gladly give as much context as I can, within the limits of not divulging work things. Also, standing up APIs isn't exactly my strongest suit, so please bear with me
Everything you've said has no real bearing on the problem you have
It's almost certainly the browser that is blocking you, not AWS. Your fetch() is trying to hit a HTTP resource from a site served over HTTPS. That's a paddlin'
I just tried text/plain and it failed in the exact same way. But even if it /were/ that issue, shouldn't my requests.post(...) have failed as well?
The dev console in firefox says Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api.sub.domain.com/ep. (Reason: CORS request did not succeed). Status code: (null).
@roganjosh it isn't but a good starting point that if Flask is not the issue the request lifecycle is and this issue is at higher level than here
@inspectorG4dget yes, but you have to make sure that request is allwed from CORs for where the request hits your API and not the flask app like @roganjosh said and without knowing what your request goes through this is difficult and can only be solved internally
I am 99.99% sure Flask has nothing to do with this. I think it's an AWS thing that's stopping your site page sending requests. That said, I've exceeded my knowledge base here
The error suggests to me that AWS refuses to recognise its own domain from a web page. It's a conflict between the browser and your server, not flask itself
Flask is dumb here, right? It just sits on 5000 waiting to be given work. It's nginx that sits in front of it that chooses whether to forward requests on and then post the answers back. That's too late for a CORS error so it's the browser intervening
I think I have seen this in the past with AWS but my memory is too hazy :( I think you need to actively open this option but I could just be making it up, sorry
@roganjosh ah I must have missed reading that he can make independent requests. , then disable extensions, disable same origin policy in browser and then make those requests. At the end slap a brand new certificate and see if that changes.
@roganjosh yes it is, but we can't really know how to guide them through AWS if we don't know what we are looking at, so changing these browser settings will either confirm or eliminate that and they will have to then look at AWS
@roganjosh yes this is true, because it is not easy to do that but that's all we got
and the docs you shared
let me share some wisdom that I always use before coming to the internet " seek help internally(within your team) first ". They are your best resource, people on internet can only guess
@MisterMiyagi I have a video clip in the back of my mind but I can't fully formulate it. Along the lines of "I have some amazing thing <extols the virtues>" --> "can I see it?" --> "no"
Arrg, There's definitely a reference to be had but I think I need to switch off for a bit